-
Notifications
You must be signed in to change notification settings - Fork 1
fix(semantic): preserve graph fact source provenance #632
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
Merged
Merged
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
Some comments aren't visible on the classic Files Changed page.
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
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.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: ContextualWisdomLab/LineageWeave
Length of output: 19443
🌐 Web query:
Fetch standard CORS response-header safelist Retry-After Access-Control-Expose-Headers💡 Result:
Answer (standard CORS / Fetch safelist): 1) Retry-After is a CORS-safelisted response header? No. Browsers expose only the Fetch “CORS-safelisted response headers” by default; any other response headers require listing via Access-Control-Expose-Headers [1][2]. 2) Access-Control-Expose-Headers works as follows: to make non-safelisted response headers readable by browser JavaScript in a CORS response, the server includes Access-Control-Expose-Headers in that response, listing the header names the client is allowed to access [2][3]. 3) Specifically for the header you asked about: - Retry-After is not included in the default CORS-safelisted response header set [1][4]. - Therefore, if you want response.headers.get('Retry-After') (or equivalent) in the browser, you must include it in Access-Control-Expose-Headers, e.g.: Access-Control-Expose-Headers: Retry-After 4) Fetch Standard backing: the Fetch spec defines “CORS-exposed header-name list” derived from the Access-Control-Expose-Headers header; a CORS filtered response exposes only headers whose names are in that exposed list and also qualify as CORS-safelisted response-header names [5]. So: Retry-After is not part of the standard CORS response-header safelist; expose it explicitly using Access-Control-Expose-Headers.
Citations:
CORS에
Retry-After를 노출하십시오.McpRetryAfterHeaderApp는 quota 초과 응답에Retry-After를 추가합니다. 그러나CORSMiddleware의expose_headers목록에는 이 헤더가 없습니다. 따라서 교차 출처 브라우저 클라이언트는response.headers.get("retry-after")로 값을 읽을 수 없습니다.expose_headers에"Retry-After"를 추가하십시오.🤖 Prompt for AI Agents