Skip to content

fix(playerbots): retain timings across log rotation - #21

Merged
Mathih13 merged 1 commit into
mainfrom
fix/pb012-observer-log-rotation-004
Sep 13, 2026
Merged

Mathih13 merged 1 commit into
mainfrom
fix/pb012-observer-log-rotation-004

Conversation

@Mathih13

Copy link
Copy Markdown
Contributor

A one-hour playerbots observation that crossed midnight lost every pre-midnight decision timing. SpacetimeDB rotates Module logs by UTC date, while the observer fetched only the current log file after measurement.

Start a bounded following log capture before the subscription clock begins, keep it alive through the final measured frame, and correlate the same exact decision identities after all required rows arrive. The observer also saves the exact measurement bounds before aggregation, so a later failure keeps the transaction clipping window.

Validation:

  • cargo +1.93.0 fmt --manifest-path adapters/lyracore/playerbots/Cargo.toml --check
  • cargo +1.93.0 test --manifest-path adapters/lyracore/playerbots/Cargo.toml --locked (36 passed)
  • cargo +1.93.0 clippy --manifest-path adapters/lyracore/playerbots/Cargo.toml --all-targets --locked -- -D warnings
  • cargo +1.93.0 build --manifest-path adapters/lyracore/playerbots/Cargo.toml --release --locked

OpenAI Codex with the wire-harness native test setup prepared this change.

@Mathih13
Mathih13 marked this pull request as ready for review September 13, 2026 01:15
@Mathih13
Mathih13 merged commit 4043a3c into main Sep 13, 2026
3 checks passed
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