fix(agent-core-v2): skip stray non-directory entries during session index scans - #3618
Merged
sailist merged 1 commit intoSep 7, 2026
Merged
Conversation
🦋 Changeset detectedLatest commit: 11ecb54 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
Merged
5 tasks
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.
Related Issue
No linked issue — the bug was reported directly from a Canary build.
Problem
Recent sessions disappeared from the session list when the sessions directory contained any stray non-directory entry (e.g. a
.DS_Storefile or a legacyworkspace.jsonfile left by an old version). The session index scan stats<entry>/state.jsonfor every entry under a workspace's sessions directory; for a plain file that stat fails with ENOTDIR, which surfaced as a genericstorage.io_failed("unrecognized I/O error") and aborted the whole index re-projection. The index then stayed on its previous generation, so all recent sessions vanished from the list, and the error message gave no hint about the real cause.What changed
Checklist
/approve).gen-changesetsskill, or this PR needs no changeset.gen-docsskill, or this PR needs no doc update.