chore: do not log context timeouts from traversal workers #71
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.
Description
In a parallel BFS traversal, it's possible that some workers are unable to start due to connection slots being unavailable. This can result in a situation where the traversal naturally finishes but because workers are locked into waiting for a connection slot, they surface the context cancellation as a failure.
Motivation and Context
Log noise and better behaved traversal.
Types of changes
Checklist: