Skip to content

FIX: Load scenario results from v0.13 and v0.14 databases after upgrade - #4161

Open
Utkarsh Bahuguna (u7k4rs6) wants to merge 2 commits into
microsoft:mainfrom
u7k4rs6:fix/legacy-scenario-identifier
Open

Utkarsh Bahuguna (u7k4rs6) wants to merge 2 commits into
microsoft:mainfrom
u7k4rs6:fix/legacy-scenario-identifier

Conversation

@u7k4rs6

Copy link
Copy Markdown
Contributor

Scenario rows from v0.13 and v0.14 kept scenario_init_data, which was always JSON null for built-in scenarios, and the rename in d4e6f8a0b2c4 carried that null into scenario_identifier. get_scenario_result then raised TypeError on it, which broke get_scenario_results_async for the whole database. Now a null stored identifier falls back to the row's scenario_name, so the old run loads with its name and attack results.

The new migration test seeds a v0.14-shaped scenario row just before the rename, lets SQLiteMemory upgrade it to head and lists scenario results. It fails on main and passes here.

Fixes #4156

Copilot AI balanced review requested due to automatic review settings November 10, 2026 15:50

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.

This branch has not been deployed

No deployments
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.

BUG: Scenario results from a v0.13 or v0.14 database can't be loaded after upgrading

2 participants