Nexus schedule to start and start to close timeouts (with fixes) #9033
Conversation
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
pdoerner
approved these changes
Jan 15, 2026
bergundy
force-pushed
the
fix-nexus-new-timeouts-logic
branch
2 times, most recently
from
758b03d to
9d4a35c
Compare
bergundy
force-pushed
the
fix-nexus-new-timeouts-logic
branch
from
880c153 to
2f4c0eb
Compare
bergundy
changed the title
bergundy
changed the title
5 tasks
simvlad
added a commit
that referenced
this pull request
Jan 17, 2026
…s) (#9033) (#9072) This reverts commit 58449b9. ## What changed? This reverts Nexus schedule to start and start to close timeouts (with fixes) (#9033) ## Why? Causes failures in nightly pipeline ## How did you test it? - [X] built - [ ] run locally and tested manually - [ ] covered by existing tests - [ ] added new unit test(s) - [ ] added new functional test(s)
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.
What changed?
Reapplied #9010.
The original PR that introduced these timeouts did not populate the operation-timeout header or set the call context timeout correctly. This PR fixes the logic.