Repository navigation
Conversation
AirKorea updates some stations after an hour's nationwide dataset is out. server2 acquired the current hour once, when it was not stored, so those stations answered the previous hour until the next hour's acquisition: on EC2 둔산동 and 월영동 stayed an hour behind for about 50 minutes. Legacy collected every 10 minutes. The observation fold now marks the current hour as lagging when its newest stored dataset has a station one hour behind, and the 10-minute capture acquires that hour again, with one key per capture interval so the per-key retry throttle keeps the cadence. Stations further behind are out of service and never count, so the refreshes stop once every live station is current. Requests answer as before. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 6, 2026
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
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
AirKorea updates some stations after an hour's nationwide dataset is out. server2 acquired the current hour once, when it was not stored, so those stations answered the previous hour until the next hour's acquisition. On EC2 (2026-11-07) the 02:00 dataset acquired at 02:10 had 둔산동 (Daejeon) and 월영동 (Masan) still at 01:00, and they answered 01:00 until 03:00, about 50 minutes. Legacy collected the real-time observations every 10 minutes.
The observation fold now marks the current hour as lagging when its newest stored dataset has a station one hour behind. The 10-minute capture acquires that hour again, with one key per capture interval so the per-key retry throttle (600 s from the end of the previous acquisition) keeps the cadence. Stations further behind are out of service and never count, so the refreshes stop once every live station is current. Requests answer as before and never wait for a refresh.
Changes
air_input.rs:Capture.lagging;observation_foldsets or clears it from the newest dataset of the current hour; the capture loop acquires a lagging hour again withnationwide-{hour}-refresh-{window}.intent/,specs/,plans/issue-2614-kma-air-refresh.md; declarationserver2/config/tasks/KMA-AIR-REFRESH.json.Verification
the_capture_acquires_the_current_hour_again_while_a_station_lags(stub with 용산구 an hour behind once and a station out of service): Red on master (no refresh in 30 s); 4 of 4 mutations caught (never marked, same key throttled, older rows count, mark never cleared).air_s3suite 20 passed; fullcargo test --locked --workspace1,214 passed, 0 failed, 7 ignored;cargo fmt --check,cargo clippy -D warnings, placement gate and artifact policy pass.Daily nationwide calls stay within the legacy cadence's 144 (at most six an hour, only while a station lags). Not in this change: the request path, the AirKorea key quota, and the other fixes of the EC2 report (#2866 is fix 1).
🤖 Generated with Claude Code