Conversation
Author
|
@goatrocks not sure if im missing anything, mind taking a quick peek? 🙏 |
goatrocks
reviewed
Jan 13, 2026
| { | ||
| Status = SubmissionStatus.FAILED | ||
| }; | ||
| var failedSubmissions = await _submissionsClient.ListAsync(new List<int> { submissionId }, new List<int> { _workflowId }, filters, 0, 10); |
Contributor
There was a problem hiding this comment.
shouldn't filter submissionId here
Author
|
IndicoV2.StrawberryShake/Generated/IndicoGqlClient.StrawberryShake.cs does this need to be regenerated? |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
|
Total Coverage: 0.00% Coverage Report
|
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
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.
Note
Medium Risk
Introduces a new client-facing API path that triggers server-side retries and parses status enums/retry metadata, which could break consumers if the API shape/status values differ. CI changes are low risk but may affect coverage visibility if filtering is too aggressive.
Overview
Adds a new submissions client operation,
RetrySubmissionsAsync, to trigger retries for failed submissions, including input validation for null/empty id lists and mapping of retry details onto returnedSubmissionobjects.Expands integration tests to cover the new retry behavior (validation, single/multiple ids, and presence of retry metadata).
Updates PR CI coverage reporting by filtering
lcov.infoto exclude generated/build outputs and enabling changed-files filtering in the lcov reporter; also adds coverage outputs to.gitignoreand introduces a repo-wideCODEOWNERSentry.Written by Cursor Bugbot for commit e2adc70. This will update automatically on new commits. Configure here.