laststance / laststance/git-gpt-commit
fix error with giant diff
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 36
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
> nsx@0.0.1 clean /Users/ryotamurakami/nsx
> rimraf pnpm-lock.yaml node_modules build server_build storybook-static
~/nsx (main|✚1) $ pnpm i
Scope: all 3 workspace projects
WARN 4 deprecated subdependencies found: @wxt-dev/storage@1.2.5, glob@10.5.0, node-domexception@1.0.0, whatwg-encoding@3.1.1
WARN Issues with peer dependencies found
.
├─┬ storybook 9.1.20
│ └─┬ @vitest/mocker 3.2.4
│ └── ✕ unmet peer vite@"^5.0.0 || ^6.0.0 || ^7.0.0-0": found 8.0.0
├─┬ @storybook/react-vite 9.1.20
│ ├── ✕ unmet peer vite@"^5.0.0 || ^6.0.0 || ^7.0.0": found 8.0.0
│ ├─┬ @storybook/builder-vite 9.1.20
│ │ └── ✕ unmet peer vite@"^5.0.0 || ^6.0.0 || ^7.0.0": found 8.0.0
│ └─┬ @joshwooding/vite-plugin-react-docgen-typescript 0.6.1
│ └── ✕ unmet peer vite@"^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0": found 8.0.0
├─┬ eslint-plugin-import 2.32.0
│ └── ✕ unmet peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8 || ^9": found 10.0.3
├─┬ eslint-config-ts-prefixer 4.1.6
│ └── ✕ unmet peer eslint@^9.0.0: found 10.0.3
├─┬ eslint-plugin-jsx-a11y 6.10.2
│ └── ✕ unmet peer eslint@"^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9": found 10.0.3
├─┬ @chromatic-com/storybook 5.0.1
│ └── ✕ unmet peer storybook@"^0.0.0-0 || ^10.1.0 || ^10.1.0-0 || ^10.2.0-0 || ^10.3.0-0": found 9.1.20
├─┬ eslint-plugin-storybook 10.2.19
│ └── ✕ unmet peer storybook@^10.2.19: found 9.1.20
└─┬ vitest-matchmedia-mock 2.0.3
└─┬ vitest 3.2.4
├── ✕ unmet peer @vitest/ui@3.2.4: found 4.1.0
└── ✕ unmet peer @vitest/browser@3.2.4: found 4.1.0
browser-extension
├─┬ eslint-plugin-import 2.32.0
│ └── ✕ unmet peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8 || ^9": found 10.0.3
├─┬ eslint-config-ts-prefixer 4.1.6
│ └── ✕ unmet peer eslint@^9.0.0: found 10.0.3
├─┬ eslint-plugin-react 7.37.5
│ └── ✕ unmet peer eslint@"^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7": found 10.0.3
└─┬ eslint-plugin-react-hooks 7.0.1
└── ✕ unmet peer eslint@"^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0-0 || ^9.0.0": found 10.0.3
Packages: +1787
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 1795, reused 1614, downloaded 20, added 1787, done
node_modules/core-js: Running postinstall script, done in 199ms
node_modules/msw: Running postinstall script, done in 259ms
node_modules/prisma: Running preinstall script, done in 133ms
browser-extension prepare$ husky
│ .git can't be found
└─ Done in 251ms
. postinstall$ pnpm prisma generate
│ Loaded Prisma config from prisma.config.ts.
│ Prisma schema loaded from prisma/schema.prisma.
│ ✔ Generated Prisma Client (7.5.0) to ./generated/prisma in 23ms
└─ Done in 785ms
. prepare$ husky
└─ Done in 147ms
Done in 13.4s using pnpm v10.31.0
~/nsx (main|✚2) $ git add --all
~/nsx (main|●2) $ git gpt commit
✔ chore: update mock service worker version for better compatibility. … yes
[STARTED] Backing up original state...
[COMPLETED] Backed up original state in git stash (ddd83f77)
[STARTED] Running tasks for staged files...
[STARTED] package.json — 2 files
[STARTED] * — 2 files
[STARTED] *.{js,ts,jsx,tsx,cjs,mjs} — 1 file
[STARTED] prettier --ignore-unknown --write
[STARTED] eslint -c eslint.config.mjs --fix --max-warnings=0 --no-warn-ignored
[COMPLETED] prettier --ignore-unknown --write
[COMPLETED] * — 2 files
[COMPLETED] eslint -c eslint.config.mjs --fix --max-warnings=0 --no-warn-ignored
[COMPLETED] *.{js,ts,jsx,tsx,cjs,mjs} — 1 file
[COMPLETED] package.json — 2 files
[COMPLETED] Running tasks for staged files...
[STARTED] Applying modifications from tasks...
[COMPLETED] Applying modifications from tasks...
[STARTED] Cleaning up temporary files...
[COMPLETED] Cleaning up temporary files...
error: 1Password: Could not connect to socket. Is the agent running?
fatal: failed to write commit object
node:internal/errors:985
const err = new Error(message);
^
Error: Command failed: git commit -m "chore: update mock service worker version for better compatibility"
[STARTED] Backing up original state...
[COMPLETED] Backed up original state in git stash (ddd83f77)
[STARTED] Running tasks for staged files...
[STARTED] package.json — 2 files
[STARTED] * — 2 files
[STARTED] *.{js,ts,jsx,tsx,cjs,mjs} — 1 file
[STARTED] prettier --ignore-unknown --write
[STARTED] eslint -c eslint.config.mjs --fix --max-warnings=0 --no-warn-ignored
[COMPLETED] prettier --ignore-unknown --write
[COMPLETED] * — 2 files
[COMPLETED] eslint -c eslint.config.mjs --fix --max-warnings=0 --no-warn-ignored
[COMPLETED] *.{js,ts,jsx,tsx,cjs,mjs} — 1 file
[COMPLETED] package.json — 2 files
[COMPLETED] Running tasks for staged files...
[STARTED] Applying modifications from tasks...
[COMPLETED] Applying modifications from tasks...
[STARTED] Cleaning up temporary files...
[COMPLETED] Cleaning up temporary files...
error: 1Password: Could not connect to socket. Is the agent running?
fatal: failed to write commit object
at genericNodeError (node:internal/errors:985:15)
at wrappedFn (node:internal/errors:539:14)
at checkExecSyncError (node:child_process:925:11)
at execSync (node:child_process:997:15)
at gptCommit (file:///Users/ryotamurakami/.local/share/mise/installs/node/24.13.0/lib/node_modules/@laststance/git-gpt-commit/index.js:190:5)
at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
at async Command.<anonymous> (file:///Users/ryotamurakami/.local/share/mise/installs/node/24.13.0/lib/node_modules/@laststance/git-gpt-commit/index.js:209:7) {
status: 128,
signal: null,
output: [
null,
Buffer(0) [Uint8Array] [],
Buffer(945) [Uint8Array] [
91, 83, 84, 65, 82, 84, 69, 68, 93, 32, 66, 97,
99, 107, 105, 110, 103, 32, 117, 112, 32, 111, 114, 105,
103, 105, 110, 97, 108, 32, 115, 116, 97, 116, 101, 46,
46, 46, 10, 91, 67, 79, 77, 80, 76, 69, 84, 69,
68, 93, 32, 66, 97, 99, 107, 101, 100, 32, 117, 112,
32, 111, 114, 105, 103, 105, 110, 97, 108, 32, 115, 116,
97, 116, 101, 32, 105, 110, 32, 103, 105, 116, 32, 115,
116, 97, 115, 104, 32, 40, 100, 100, 100, 56, 51, 102,
55, 55, 41, 10,
... 845 more items
]
],
pid: 34015,
stdout: Buffer(0) [Uint8Array] [],
stderr: Buffer(945) [Uint8Array] [
91, 83, 84, 65, 82, 84, 69, 68, 93, 32, 66, 97,
99, 107, 105, 110, 103, 32, 117, 112, 32, 111, 114, 105,
103, 105, 110, 97, 108, 32, 115, 116, 97, 116, 101, 46,
46, 46, 10, 91, 67, 79, 77, 80, 76, 69, 84, 69,
68, 93, 32, 66, 97, 99, 107, 101, 100, 32, 117, 112,
32, 111, 114, 105, 103, 105, 110, 97, 108, 32, 115, 116,
97, 116, 101, 32, 105, 110, 32, 103, 105, 116, 32, 115,
116, 97, 115, 104, 32, 40, 100, 100, 100, 56, 51, 102,
55, 55, 41, 10,
... 845 more items
]
}
Node.js v24.13.0
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with the git gpt commit command after staging the changes. Start at the gptCommit entry point shown in the installed package's index.js and trace the failed Git commit involving the 1Password socket error. Done means the command completes successfully and writes the commit object without losing the staged changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, javascript, nodejs
- Domain
- cli, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100