Skip to content

fix(windows): close skill-markdown graph clients to avoid sqlite EBUSY - #53

Draft
Roarpeng wants to merge 1 commit into
mainfrom
cursor/fix-skill-md-windows-ebusy-aad7
Draft

Roarpeng wants to merge 1 commit into
mainfrom
cursor/fix-skill-md-windows-ebusy-aad7

Conversation

@Roarpeng

Copy link
Copy Markdown
Owner

Why

main @ 4cda297 (v1.24.0) failed validate-platforms (windows-latest):

tests/skill-markdown-progressive.test.ts
  EBUSY: resource busy or locked, unlink
  ...\graphflow-out\graphflow-graph.sqlite

Default graphPolicy.transport is auto (sqlite when better-sqlite3 is present). Skill markdown import/export opened a client and never close()’d it, so afterEach rmSync could not delete the temp dir on Windows.

Changes

  • importSkillsFromMarkdownRuntime / exportSkillsToMarkdownRuntime / extractDialogueKnowledgeRuntime close the graph client in finally.
  • Test cleanup swallows leftover unlink errors.

Validation

npx vitest run tests/skill-markdown-progressive.test.ts tests/skill-markdown-interop.test.ts — 12 passed (Linux). Windows coverage is the CI job this unblocks.

Open in Web Open in Cursor 

…sqlite

Default auto transport opens better-sqlite3. Import/export left the
handle open, so afterEach rmSync hit EBUSY on Windows validate.
Close the client in finally and ignore leftover unlink errors.
@Roarpeng
Roarpeng force-pushed the cursor/fix-skill-md-windows-ebusy-aad7 branch from 161e2fe to 57dfe58 Compare October 1, 2026 01:13
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