-
Notifications
You must be signed in to change notification settings - Fork 33
fix(codexmate): harden bridge retries and OpenClaw UX #207
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
+872
−295
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
7628878
fix(openai-bridge): avoid duplicate error headers
awsl233777 25d4f27
fix(openai-bridge): close failed post-header responses
awsl233777 563d3bf
fix(openai-bridge): retry transient HTTP statuses
awsl233777 4372218
fix(openai-bridge): retry transient responses streams
awsl233777 6431495
fix(web-ui): expand main area when sidebar collapses
ymkiux 187a747
fix(openai-bridge): hide retry counts and keep retrying
awsl233777 5c9c66d
fix(openai-bridge): align transient retries with maxx
awsl233777 f1429fa
feat(openclaw): enrich config tab diagnostics
awsl233777 3c684cb
style(openclaw): tighten workspace editor copy
awsl233777 c8496d3
style(openclaw): align workspace file cards
awsl233777 c34d962
style(openclaw): remove redundant workspace input
awsl233777 de46497
style(openclaw): simplify workspace card labels
awsl233777 aec7088
chore(release): bump version to 0.1.2
awsl233777 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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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 | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: SakuraByteCore/codexmate
Length of output: 997
🏁 Script executed:
Repository: SakuraByteCore/codexmate
Length of output: 17661
🏁 Script executed:
Repository: SakuraByteCore/codexmate
Length of output: 18992
🌐 Web query:
OpenAI Responses streaming schema response.created sequence_number required response.in_progress💡 Result:
In the OpenAI Responses API, streaming events follow a structured schema that includes both type and sequence_number fields [1][2]. Key Event Types: - response.created: Emitted immediately after a response is created. It includes the response object and the sequence_number [2][3]. - response.in_progress: Emitted while the response is being generated. Like other lifecycle events, it includes the response object and the sequence_number [2][3]. Sequence Number: The sequence_number is a required integer field for streaming events in the Responses API [1][4][5]. It is monotonically increasing for each stream and is used by clients to enforce correct event ordering and to ignore duplicate events [6]. Documentation and Implementation: Official OpenAI documentation defines these events with a specific schema [1]. Client libraries, such as the official Node.js SDK, define these events in their type definitions (e.g., ResponseCreatedEvent and ResponseInProgressEvent) as requiring both a type and a sequence_number [7][2]. While the API specification mandates these fields, developers have noted that implementation behavior can occasionally deviate from the spec in specific scenarios (such as error events), requiring robust handling in client implementations [5]. Note: This structure specifically applies to the Responses API (often used in the context of the Assistants API/Realtime capabilities) and differs from the traditional Chat Completions streaming API, which utilizes a different chunk-based structure (chat.completion.chunk) [8][9][10].
Citations:
🏁 Script executed:
Repository: SakuraByteCore/codexmate
Length of output: 4152
Add
sequence_numbertoresponse.created. This lifecycle event is missing the top-level ordering field, so it doesn’t match the Responses streaming schema;response.in_progressshould keep the next sequence value.Proposed fix
created_at: state.createdAt, status: 'in_progress', output: [] - } + }, + sequence_number: state.nextSeq() });📝 Committable suggestion
🤖 Prompt for AI Agents
Source: MCP tools