-
Type:
Bug
-
Resolution: Not a bug
-
Priority:
Medium
-
None
-
Affects Version/s: 8.4.1, 8.19.0
-
Component/s: Git Hosting, Mesh
-
None
-
Severity 2 - Major
Issue Summary
A Git push via SSH to a new branch/repository using go-git fails with non-zero exit code -1001. Consequently, the logs show the push did not complete, and post-receive hooks are not triggered, causing issues.
This is reproducible on Data Center: Yes
Steps to Reproduce
- Push a commit using a sample GO program to a new branch or repository over SSH
- The commit doesn't appear in push log or webhooks aren't triggered. (one of the cases)
Expected Results
Push operation is expected to be successful triggering post receive hooks.
Actual Results
Bitbucket access logs show
0:0:0:0:0:0:0:1 | ssh | i@1CJ9Z48x1428x435x0 | admin | 2025-11-13 23:48:53,341 | SSH - git-receive-pack '/project_1/rep_1.git' | "SSH-2.0-Go" | - | - | - | - | - | qskz4s | 0:0:0:0:0:0:0:1 | ssh | o@1CJ9Z48x1428x435x0 | admin | 2025-11-13 23:48:53,603 | SSH - git-receive-pack '/project_1/rep_1.git' | "SSH-2.0-Go" | -1001 | 830 | 667 | ssh:user:id:2 | 262 | qskz4s |
Mesh logs show push did not complete and interactive client has canceled messages.
2025-11-13 23:48:53,603 DEBUG [grpc-server:thread-11] - c.a.b.mesh.git.LoggingGrpcPushTracer [a514989796f76dc740fa-1] Push did not complete as expected; {
request: "0086632751dff4bee5251a59dbe86f1dc49557d07720 66ef0edb1a0c9f27954941828197afec65c262dc refs/heads/masteragent=go-git/5.x report-status
0000",
pre-receive: {exit: 0},
post-receive: not called,
stdout: "000eunpack ok
0019ok refs/heads/master
0000",
stderr: ""}
2025-11-13 23:48:53,603 DEBUG [grpc-server:thread-12] admin 5EB34HIIx1428x53x2 @1CJ9Z48x1428x435x0 127.0.0.1 "HostingService/ReceivePack" (>9 <5) c.a.b.m.g.BidirectionalFragmentRequestObserver The interactive client has canceled the request
Workaround
Use HTTPS when pushing to Bitbucket using go-git.