Replay API behavior verification #107
Closed
Conversation
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
Co-authored-by: danny <danny@onkernel.com>
|
Cursor Agent can help with this pull request. Just |
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.
This PR contains no code changes, serving as a record of the verification of
replays.stopandreplays.downloadAPI behavior against thekernelserver's OpenAPI spec and implementation.The verification confirmed that
replays.downloaduses 200/202 withRetry-Afteras a readiness gate, but clarified thatreplays.stopreturns 200 even on errors andreplays.download's 202 response is specifically for recordings still in progress and not a general "processing not done yet" signal. The "S3 first, then live download" andfinished_atmerge precedence explanations from the initial query do not apply to this repo's implementation.