Skip to content

Fix reset lost-response test failure timing - #201

Merged
SaladDay merged 1 commit into
codex/qualified-release-promotion-20260928from
codex/web-reset-read-timing-20260929
Sep 28, 2026
Merged

SaladDay merged 1 commit into
codex/qualified-release-promotion-20260928from
codex/web-reset-read-timing-20260929

Conversation

@SaladDay

@SaladDay SaladDay commented Sep 28, 2026 •

Copy link
Copy Markdown
Collaborator

The lost-response reset test enabled deployment read failures before submitting the reset. A refresh could therefore correctly disable the reset button, preventing the test from reaching the scenario it intended to verify.

Enable failed reconciliation reads only after the fixture accepts the reset POST, then drop its response. Keep the existing assertions for disabled controls, exactly one reset write, and recovery after a successful read. No product code changes.

Validation: the focused Playwright case passed (15.8 seconds); git diff --check passed. The run reported font serving warnings from shared dependency paths; this is behavioral evidence, not visual acceptance. Final combined checks remain with the integration owner.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith with what you need. Autofix is disabled.

@SaladDay
SaladDay merged commit b3a2aec into codex/qualified-release-promotion-20260928 Sep 28, 2026
2 checks passed
@SaladDay
SaladDay deleted the codex/web-reset-read-timing-20260929 branch October 10, 2026 05:06
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.

1 participant