Skip to content

Conversation

Shivs11
Copy link
Member

@Shivs11 Shivs11 commented Sep 16, 2025

READ BEFORE MERGING: All PRs require approval by both Server AND SDK teams before merging! This is why the number of required approvals is "2" and not "1"--two reviewers from the same team is NOT sufficient. If your PR is not approved by someone in BOTH teams, it may be summarily reverted.

  • The main aim of this PR is to add an enum in the RoutingConfig.
  • To allow users to have a peek at the exact stage where an update, scheduled by a worker-versioning write API, has reached.
  • None

Server PR

  • WIP right now.

@Shivs11 Shivs11 marked this pull request as ready for review September 18, 2025 15:03
@Shivs11 Shivs11 requested review from a team as code owners September 18, 2025 15:03
// Update to the RoutingConfig has completed successfully.
ROUTING_CONFIG_UPDATE_STATE_COMPLETED = 2;
// Update to the RoutingConfig has failed.
ROUTING_CONFIG_UPDATE_STATE_FAILED = 3;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if we do keep an internal timeout (such as 10m or 5m) and the update times out, would that cause it to be in failed state?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants