Repository navigation
chore: drop stale T0 reference in synchronize comment #72
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
Closed
Closed
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
76019fd
chore: drop stale T0 reference in synchronize comment
bbfbcf1
test: add sync-path finding fixture (WS-3 live test)
a94176c
test: fix finding fixture to trigger error_handling pattern (WS-3 liv…
73f03e0
test: extend finding fixture with sort (WS-3 sync thread-update test)
3628105
test: add delta finding for thread-update verification (WS-3 live test)
ae77ac8
test: final thread-update fixture (WS-3 PATCH verification)
7553117
Merge branch 'main' into ws3-livetest-pr
06df591
test: marker for final PATCH verification sync
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
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 | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: ChonSong/riptide
Length of output: 2228
🏁 Script executed:
Repository: ChonSong/riptide
Length of output: 229
🏁 Script executed:
Repository: ChonSong/riptide
Length of output: 26759
🏁 Script executed:
Repository: ChonSong/riptide
Length of output: 18817
Do not hide fixture parsing exceptions in the sync helpers.
These
_sync_test_helperand_sync_test_helper_deltahelpers catch everyExceptionand drop the item. An unexpecteditem["key"]orstr(item)failure can make the live sync fixture produce fewer expected results while avoiding a visible failure. Catch only malformed-item exceptions that support the WS-3 fixture contract, or re-raise unexpected exceptions and add tests for the contract.Also applies to: 126-129
🧰 Tools
🪛 Ruff (0.16.1)
[error] 116-117:
try-except-passdetected, consider logging the exception(S110)
🤖 Prompt for AI Agents
Source: Linters/SAST tools