Repository navigation
fix(errors): keep layer guidance at raise sites - #221
Merged
Merged
Conversation
Restore the vendored FunctionLayerError catalog entry to the generated registry source. Keep Python-specific timeout guidance and scenario-specific retryability on each runtime exception instead of editing the cross-language generated catalog.
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
dashscope/_error_registry.pyFunctionLayerError text to the generated error-registry sourceallow_retryfor create rejection, local input failure, build failure, status-query failure, missing status, and timeoutValidation
pytest -q tests/test_error_registry.py tests/test_errors.py tests/legacy_1x/unit/test_agentic_rl_layer_status.py tests/test_finetune_rl_shim.py tests/test_rl.py275 passed