Drupal bootstrap failures should throw debuggable exception #9616
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated Description
Suppose one is submitting a request to a backend entry-point (such as
rest.php
orcv
). If the system an incompatible/incomplete configuration, it could produce a hard exit with the error likeSorry, could not locate bootstrap.inc
. However, tracing this error was often difficult because the hard exit did not report a backtrace. This makes the error condition more debuggable.Original Description
As discussed with @totten in the chat.
I'd like to fix that
error_reporting
call too but need some guidance first.