Skip to content

Conversation

@mnapoli
Copy link
Member

@mnapoli mnapoli commented Jun 25, 2025

In the fpm runtime, fatal errors in the bootstrap process don't have their details logged.

Reported in Slack: https://brefworkspace.slack.com/archives/C057S6G4Z9N/p1750813674579189?thread_ts=1750740077.495139&cid=C057S6G4Z9N

Here is to illustrate:

  • FPM runtime (no error details)

Screen-002934

  • Function runtime

Screen-002936

The reason is that display_errors=0 in the FPM runtime because we don't want errors in the application to be logged to stdout (because stdout is the HTTP response). However this is an issue in the bootstrap process: errors are then not logged (some errors, not all of them).

This PR forces display_errors=1 in the bootstrap process regardless of the runtime.

@mnapoli mnapoli changed the title Force display_errors=1 in the bootstrap process Fix some internal fatal errors not logged by forcing display_errors=1 in the bootstrap process Jun 25, 2025
@mnapoli mnapoli merged commit dbe220a into main Jun 25, 2025
11 checks passed
@mnapoli mnapoli deleted the force-error-logging-fpm branch June 25, 2025 09:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants