Repository navigation
fix: BED-10372 bound collection retries and timeouts - #95
Merged
Merged
Conversation
eladshamir
approved these changes
Oct 30, 2026
This branch was successfully deployed
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.
Transient GitHub server and network failures can leave collection silent for many minutes while requests retry. This change uses 10-second connection and 30-second read timeouts and caps transient failures at three attempts. Adaptive GraphQL pagination shares that budget across page sizes instead of restarting HTTP retries at each size.
Exhausted HTTP errors now reach the existing scope handlers so collection can continue rather than treating an error body as resource data. Existing rate-limit and GitHub App token-refresh retry behavior is preserved. Previously emitted records are retained; failed scopes can remain incomplete.
Workflow collection also skips
dynamic/paths and drops unavailable file results before job/step parsing, preventing cascading errors when file requests fail. Regression tests exercise successful and failed workflows through both child transformers.Validation: all 424 tests pass on current upstream/main, including parallel organization/repository/environment continuation, partial pagination, GraphQL recovery and exhaustion, rate limits, token refresh, and enterprise credential exports. Ruff and diff checks pass.
Summary by CodeRabbit