Repository navigation
Conversation
This branch was successfully deployed
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
Issue #6 reports that two IDEs corrupt the shared task history. Both IDEs write to one
~/.zoo-code/globalStorage.The upstream fix is merged (Zoo-Code#1261). This PR adds an end-to-end test so the fix stays in place. The test runs two real IDEs against one history store. Each IDE runs a parent task that delegates to a subtask.
This PR is partial work for #6. It does not close the issue. See "Not covered".
What the test does
newTaskmessage.new_taskat the same time.check_history_store.pychecks the shared store.The driver uses no keyboard in this test. On Windows, a second IDE opens behind the first and gets no native focus.
What the checker verifies
_index.jsonfile is written.history_item.jsonis valid JSON and has a real title.sizeabove zero.completed. No parent still waits on a subtask.Changes
streaming_fixture.py: newhistory-racescenario withnew_taskdelegation and a barrier.HarnessDriver.java: new history mode. It starts tasks withnewTask, records task order in the page, and does no focus checks.check_history_store.py: new store checker, with unit tests.run-windows.ps1: new-HistoryRaceswitch and-ExpectExtensionVersion.windows-chat-focus.yml: new step inwindows-e2e. The extension version is now one workflow-level value.run-windows.ps1fails when the extension inside the plugin ZIP has an unexpected version. The ZIP name does not set that version.Evidence
These are one-time local runs on Linux with Xvfb. They used
run-history-race.sh, which is no longer in the repo, so they cannot be reproduced from it. The reproducible evidence is the Windows CI artifactwindows-history-race-*from run 43562237505 (see "Windows CI"). IDEA IU 2026.2.1 (build 262.9437.185, archive SHA-256dac2021204c8bf3bd8d66567a1ae36a341da0050b6006c32d42006c6577eb29a).tasks/_index.jsonwas written.The plugin ZIP names do not match their contents.
ZooCode-3.78.0.zipandZooCode-3.96.0.zipboth bundle extension 3.84.0 in the local build. The first negative control used them and was invalid. The version check prevents this mistake.Unit tests run without an IDE:
python3 -m unittest test_streaming_fixture test_check_history_store. 20 tests pass in the two history test files.Windows CI
Commit
5a494cf: the history step passed on IDEA 2026.1.5.1 and 2026.2.1 (4 tasks, no failures, both IDEsPASS). The real parent and child items from that run are fixtures intest_check_history_store.py. The first run failed once in the older focus step on 2026.1.5.1 (No loaded, mounted chat browser after indexing). It passed on rerun, andlive-solheimpassed after approval.Not verified
Not covered from #6
ui_message.jsoncorruption is not tested.Next steps
Refs #6