Chris Farhood
efbbfbc299
When waitForJobCompletion threw a transient error (API disconnect, etc.), the code fell through with jobTimedOut=true and returned a result even though the job was still running. This caused the UI to think the run was complete while the job kept running, resulting in concurrency errors. Now when completion throws, we re-check the job's actual state. If still not terminal, we return a k8s_job_state_mismatch error so the UI knows the run is not done. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
50 lines
1.3 KiB
JSON
50 lines
1.3 KiB
JSON
{
|
|
"name": "@farhoodliquor/paperclip-adapter-claude-k8s",
|
|
"version": "0.1.15",
|
|
"description": "Paperclip adapter plugin that runs Claude Code agents as Kubernetes Jobs",
|
|
"license": "MIT",
|
|
"repository": {
|
|
"type": "git",
|
|
"url": "https://github.com/farhoodliquor/paperclip-adapter-claude-k8s"
|
|
},
|
|
"bugs": {
|
|
"url": "https://github.com/farhoodliquor/paperclip-adapter-claude-k8s/issues"
|
|
},
|
|
"homepage": "https://github.com/farhoodliquor/paperclip-adapter-claude-k8s#readme",
|
|
"type": "module",
|
|
"paperclip": {
|
|
"adapterUiParser": "1.0.0"
|
|
},
|
|
"exports": {
|
|
".": "./dist/index.js",
|
|
"./server": "./dist/server/index.js",
|
|
"./ui-parser": "./dist/ui-parser.js",
|
|
"./cli": "./dist/cli/index.js"
|
|
},
|
|
"files": [
|
|
"dist"
|
|
],
|
|
"scripts": {
|
|
"build": "tsc",
|
|
"clean": "rm -rf dist",
|
|
"typecheck": "tsc --noEmit",
|
|
"test": "vitest run",
|
|
"test:watch": "vitest",
|
|
"coverage": "vitest run --coverage"
|
|
},
|
|
"dependencies": {
|
|
"@kubernetes/client-node": "^1.0.0",
|
|
"picocolors": "^1.1.1"
|
|
},
|
|
"peerDependencies": {
|
|
"@paperclipai/adapter-utils": ">=2026.415.0-canary.7"
|
|
},
|
|
"devDependencies": {
|
|
"@paperclipai/adapter-utils": "2026.415.0-canary.7",
|
|
"@types/node": "^24.6.0",
|
|
"@vitest/coverage-v8": "^4.1.4",
|
|
"typescript": "^5.7.3",
|
|
"vitest": "^4.1.4"
|
|
}
|
|
}
|