Skip to content

fix(tui): guard metadata background races - #62

Merged
patricksmill merged 1 commit into
mainfrom
cursor/critical-bug-management-2bf5
Sep 28, 2026
Merged

patricksmill merged 1 commit into
mainfrom
cursor/critical-bug-management-2bf5

Conversation

@cursor

@cursor cursor Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Summary

Prevent stale metadata-search completions and overlapping metadata match/unmatch writes from corrupting the active TUI metadata flow for a ROM. Metadata picker sessions now use a generation guard, and metadata writes block duplicate writes for the same ROM until completion.

Crate(s)

  • romm-api
  • romm-cli
  • romm-tui
  • docs / CI only

Checklist

  • cargo fmt --check passes
  • Both cargo clippy runs pass (--all-features and --no-default-features, -D warnings)
  • cargo test --workspace passes (or scoped tests with reason)
  • PR title uses Conventional Commits with the right scope for the changelog
  • No secrets, tokens, or personal config in the diff
  • User-facing changes documented in the relevant docs/*.md if needed

Scoped test reason: changes are limited to romm-tui; ran cargo +stable test -p romm-tui. Used cargo +stable because the default Cargo 1.83 cannot parse the current rpassword edition-2024 manifest.

Open in Web View Automation 

Co-authored-by: Patrick Mill <patricksmill@users.noreply.github.com>
@patricksmill
patricksmill marked this pull request as ready for review September 28, 2026 20:29
@patricksmill
patricksmill force-pushed the cursor/critical-bug-management-2bf5 branch from f9241d1 to 1de572f Compare September 28, 2026 20:29
@patricksmill
patricksmill merged commit 651f7f5 into main Sep 28, 2026
@patricksmill
patricksmill deleted the cursor/critical-bug-management-2bf5 branch September 28, 2026 20:29
@github-actions github-actions Bot mentioned this pull request Sep 28, 2026
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.

2 participants