Repository navigation
fix: return 400 for invalid webhook configuration - #463
Merged
Merged
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
WebhookConfigExceptionwas storingdetailsasNone, soPOST /v2/jobswith an invalid webhook (for example a localhost URL) crashed in the exception handler and returned 500UnknownExceptioninstead of 400.detailsthrough toKnowhereException, and readretry_afterfromexc.details or {}so a missing details dict cannot turn a client error into a server error.INVALID_ARGUMENT.Test plan
uv run pytest tests/contract/test_exception_handlers_contract.py::test_invalid_webhook_config_returns_client_errorPOST /v2/jobswith a localhost webhook returns 400Invalid webhook URLand does not emitUnknownExceptionin Logfire.Made with Cursor