test: Probe initial flag snapshots before checking configuration sync - #38714
Open
aljoscha wants to merge 1 commit into
Open
test: Probe initial flag snapshots before checking configuration sync#38714aljoscha wants to merge 1 commit into
aljoscha wants to merge 1 commit into
Conversation
aljoscha
marked this pull request as ready for review
September 8, 2026 13:42
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
1 participant
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.
Motivation
SQL-685 reports stale flag values in the configuration-sync integration test. A successful management API update followed by a fixed three-second sleep does not establish SDK visibility. The boot-only assertion cannot converge after reading a stale initial snapshot because its periodic sync loop is disabled.
Changes
Replace the sleep with a bounded readiness probe after targeting changes. Open fresh SDK streams until an initial root snapshot contains at least the environment-specific flag version returned by the management API. Close stale streams rather than waiting for patches, retry transient transport and server failures, and report expected and observed versions on timeout. Allow 120 seconds for the live SQL assertions, including streaming reconnect backoff.
Coverage and limits
The existing launchdarkly workflow retains its boot-only, persisted-value, live-update, kill-switch and scoped-override assertions. The probe uses the same snapshot endpoint as boot, but does not claim a consistency guarantee across separate connections. This is a test-readiness fix, not a demonstrated explanation of every historical failure or the separate production bootstrap/recovery gaps recorded on SQL-685.
Related: SQL-685
Release notes
None.