-
Notifications
You must be signed in to change notification settings - Fork 28
fix(#142): HTMLResponse Content-Type, noargs cache, future annotations #143
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
Open
justrach
wants to merge
1
commit into
release/1.0.32
Choose a base branch
from
fix/issue-142-html-and-future-annotations
base: release/1.0.32
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Incomplete PEP 563 fix: UploadFile annotation checks in create_enhanced_handler still use raw param.annotation
The PR fixes PEP 563
from __future__ import annotationsforbytes/bytearray/TurboRequestchecks (request_handler.py:854) by using the_ann()resolver, but misses three UploadFile annotation checks in the same function that still useparam.annotationdirectly. Under PEP 563,param.annotationis a string like'UploadFile', soparam.annotation is _UploadFileevaluates toFalseandisinstance(param.annotation, type)also fails. This causes barefile: UploadFileparameters (without explicit= File()default) to not be detected as form params.Notably,
classify_handlerinzig_integration.py:232WAS correctly updated to use the resolvedann, creating an inconsistency: Zig dispatch may classify the handler as "file_sync" butcreate_enhanced_handlerwon't populate the UploadFile parameter at runtime.Affected locations (3 identical patterns)
_has_form_paramsAll use
param.annotation is _UploadFileinstead of the resolved_ann(pname, param) is _UploadFile.(Refers to lines 882-886)
Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.