Repository navigation
Conversation
Literal lookup failures previously reused the enum error wording. Differentiate in _Lookup_OnMissing and bool-literal paths so enums still report "Invalid enum value" while Literal uses "Invalid value". Fixes msgspec#1009
Codex Review Summary: ❌ FailedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
Summary
Invalid value %Rinstead ofInvalid enum value %Rwhen atyping.Literallookup failsInvalid enum valuefor realenum.Enum/IntEnumtypes (lookup->cls != NULL)Fixes #1009
Test plan
test_json.py,test_convert.py,test_common.py,test_msgpack.py,test_schema.pyInvalid enum value 2forenum.Enum)