RuntimeException: The project 'drupal' can not be updated because its status is in Drupal\package_manager\ProjectInfo->getInstallableReleases() (line 111 of modules/contrib/automatic_updates/package_manager/src/ProjectInfo.php).

Created on 8 March 2023, over 1 year ago
Updated 9 March 2023, over 1 year ago

The website encountered an unexpected error. Please try again later.

RuntimeException: The project 'drupal' can not be updated because its status is in Drupal\package_manager\ProjectInfo->getInstallableReleases() (line 111 of modules/contrib/automatic_updates/package_manager/src/ProjectInfo.php).

Drupal\automatic_updates\Validator\VersionPolicyValidator->getAvailableReleases(Object) (Line: 119)
Drupal\automatic_updates\Validator\VersionPolicyValidator->validateVersion(Object, NULL) (Line: 151)
Drupal\automatic_updates\Validator\VersionPolicyValidator->checkVersion(Object, 'Drupal\package_manager\Event\StatusCheckEvent', Object)
call_user_func(Array, Object, 'Drupal\package_manager\Event\StatusCheckEvent', Object) (Line: 111)
Drupal\Component\EventDispatcher\ContainerAwareEventDispatcher->dispatch(Object) (Line: 49)
Drupal\automatic_updates\Validation\StatusChecker->runStatusCheck(Object, Object, 1) (Line: 105)
Drupal\automatic_updates\Validation\StatusChecker->run() (Line: 90)
Drupal\automatic_updates\Controller\StatusCheckController->run()
call_user_func_array(Array, Array) (Line: 123)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 580)
Drupal\Core\Render\Renderer->executeInRenderContext(Object, Object) (Line: 124)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->wrapControllerExecutionInRenderContext(Array, Array) (Line: 97)
Drupal\Core\EventSubscriber\EarlyRenderingControllerWrapperSubscriber->Drupal\Core\EventSubscriber\{closure}() (Line: 163)
Symfony\Component\HttpKernel\HttpKernel->handleRaw(Object, 1) (Line: 74)
Symfony\Component\HttpKernel\HttpKernel->handle(Object, 1, 1) (Line: 58)
Drupal\Core\StackMiddleware\Session->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\KernelPreHandle->handle(Object, 1, 1) (Line: 106)
Drupal\page_cache\StackMiddleware\PageCache->pass(Object, 1, 1) (Line: 85)
Drupal\page_cache\StackMiddleware\PageCache->handle(Object, 1, 1) (Line: 50)
Drupal\ban\BanMiddleware->handle(Object, 1, 1) (Line: 48)
Drupal\Core\StackMiddleware\ReverseProxyMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\NegotiationMiddleware->handle(Object, 1, 1) (Line: 51)
Drupal\Core\StackMiddleware\StackedHttpKernel->handle(Object, 1, 1) (Line: 686)
Drupal\Core\DrupalKernel->handle(Object) (Line: 19)

πŸ› Bug report
Status

Closed: cannot reproduce

Version

2.7

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @romulasry
  • I just set it to sftp mode and I get this when I try to rerun readiness checks.

  • πŸ‡§πŸ‡ͺBelgium wim leers Ghent πŸ‡§πŸ‡ͺπŸ‡ͺπŸ‡Ί

    What version of Drupal are you on?

  • Status changed to Postponed: needs info over 1 year ago
  • πŸ‡ΊπŸ‡ΈUnited States phenaproxima Massachusetts

    This could use a little more detail to help us debug it. Examples:

    • What is the exact version of Drupal you're on? (Like...10.0.3? 10.1.x?)
    • What operating system/PHP version?
    • Can you describe the sequence of steps you took to arrive at this result? What pages you went to, what you clicked on, etc. Screenshots or a video are great, if possible. What was the URL where you got this error?
    • You said "I just set it to sftp mode" -- what does this mean? Automatic Updates doesn't use SFTP or have any opinion about that.
  • Now it is working: says

    Your site does not pass some readiness checks for automatic updates. It cannot be automatically updated until further action is performed.

    The active directory at "/code" contains symlinks, which is not supported. The first one is "/code/vendor/pantheon-upstreams/upstream-configuration". See the help page for information on how to resolve the problem.

    Rerun readiness checks now.

  • Status changed to Closed: cannot reproduce over 1 year ago
Production build 0.71.5 2024