Skip to content
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.

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

Warn when sending bare 404 response #2410

Merged
merged 1 commit into from
Apr 3, 2024

Conversation

itowlson
Copy link
Contributor

@itowlson itowlson commented Apr 1, 2024

Fixes #1132

Copy link
Member

@vdice vdice left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. I see the logic is set up to warn only once on the first 404. I had a thought that we might perhaps want to log on every 404 if running in a verbose mode (perhaps log level 'trace' or some such?) but not sure if it is worth the complication and in any case, perhaps premature; seems a fine idea to get this in as-is and revisit if needed.

@itowlson itowlson merged commit 4987d49 into fermyon:main Apr 3, 2024
14 checks passed
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.

Nicer errors when no component route matches
2 participants