[codex] fix endpoint refresh retry after MQTT outage#1279
Merged
Conversation
copystring
force-pushed
the
codex/fix-endpoint-refresh-mqtt-throttle
branch
from
a7fb7af to
81b0eb2
Compare
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.
Summary
Root cause
efreshEndpoint() recorded the per-device throttle timestamp before
efreshEndpointInternal() checked MQTT availability. If MQTT was temporarily unavailable, the refresh returned early but still blocked the next retry for 60 seconds.
Validation
ode_modules is absent in the Codex worktree, so local
pm test execution was not available