Repository navigation
feat: update repo settings for agent - #1
Merged
Merged
Conversation
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
This was referenced Jan 16, 2026
marcusrbrown
added a commit
that referenced
this pull request
Jan 21, 2026
- Only track tokens/cost/artifacts from successful attempts (Issue #1, #2) - Check remaining timeout before retry attempts (Issue #3) - Increase event stream grace period from 1s to 2s (Issue #4) - Add comprehensive tests for retry logic: - Retries on LLM fetch error and succeeds on second attempt - Stops retrying after MAX_LLM_RETRIES attempts - Does not retry on non-LLM errors - Only tracks results from successful attempt - Sends continuation prompt on retry instead of initial prompt
marcusrbrown
added a commit
that referenced
this pull request
Jan 21, 2026
…ors (#111) * fix(agent): wrap entire SDK execution in retry loop for LLM fetch errors - Extract attemptExecution() helper to encapsulate full SDK lifecycle - Retry up to 3 times with 5s delay on recoverable LLM fetch errors - Detect errors from both event stream and caught exceptions - Post error comment to PR/issue on final failure - Exit 0 for recoverable LLM errors (don't fail CI) - Fix PR number extraction using triggerResult.context.target * chore: update build artifacts * fix(agent): reuse session across retries and send continuation prompt Session context is now preserved on LLM fetch error retry: - Create server and session ONCE (outside retry loop) - On retry, send continuation prompt to same session instead of recreating - Agent can resume where it left off with full conversation context - Accumulate token usage, cost, and artifacts across retry attempts * fix(agent): address PR feedback on retry behavior - Only track tokens/cost/artifacts from successful attempts (Issue #1, #2) - Check remaining timeout before retry attempts (Issue #3) - Increase event stream grace period from 1s to 2s (Issue #4) - Add comprehensive tests for retry logic: - Retries on LLM fetch error and succeeds on second attempt - Stops retrying after MAX_LLM_RETRIES attempts - Does not retry on non-LLM errors - Only tracks results from successful attempt - Sends continuation prompt on retry instead of initial prompt
This was referenced May 17, 2026
This was referenced May 29, 2026
Merged
This was referenced Jun 9, 2026
This was referenced Jun 20, 2026
This was referenced Jun 28, 2026
This was referenced Jul 8, 2026
This was referenced Aug 22, 2026
This was referenced Aug 29, 2026
Closed
This was referenced Sep 5, 2026
Merged
Merged
Closed
This was referenced Sep 14, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
No description provided.