Skip to content

Fix some internal fatal errors not logged by forcing display_errors=1 in the bootstrap process #267

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mnapoli merged 1 commit into from
Jun 25, 2025
Merged

Fix some internal fatal errors not logged by forcing display_errors=1 in the bootstrap process #267

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions layers/bootstrap.php
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,11 @@
<?php declare(strict_types=1);

// Force errors to be logged to stdout so that they end up in CloudWatch.
// In the `function` runtime this is already `1`, but in the `fpm` runtime it is `0` by default.
// Here we are forcing it to `1` in the bootstrap process, it will not impact the application code
// as it runs in different processes (FPM worker) and those will have `display_errors=0`.
ini_set('display_errors', '1');

$appRoot = getenv('LAMBDA_TASK_ROOT');

$autoloadPath = $_SERVER['BREF_AUTOLOAD_PATH'] ?? null;
Expand Down