git ssb

39+

cel / git-ssb



When trying to push:

%eMpJ1c8/iJaKE6n/7FCBr3qMbpjDrNL0fqD5qEJgdn8=.sha256
OpenMatt McKegg opened this issue on 10/9/2016, 2:10:27 PM

When trying to push:

/home/dev/.nvm/versions/node/v6.7.0/lib/node_modules/git-ssb/node_modules/git-remote-ssb/git-remote-ssb:58
        if (err) throw err
                 ^

Error: git index-pack returned 128
    at ChildProcess.<anonymous> (/home/dev/.nvm/versions/node/v6.7.0/lib/node_modules/git-ssb/node_modules/pull-git-pack/lib/index-pack.js:19:24)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:877:16)
    at Socket.<anonymous> (internal/child_process.js:334:11)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at Pipe._handle.close [as _onclose] (net.js:493:12)

I had just amended a commit message prior to the push.

%UKjQ2Dy4XDrt2EAv7Q0RqRefHid5DpSDJE6jYBNlT7I=.sha256 Matt McKegg · 10/9/2016, 2:12:43 PM

Whoops I missed the top off that message

fatal: pack has 3 unresolved deltas
%Jgez9cazdPnm9bDJbDlUbdJd/mOKm1ug17wdWvXUT5w=.sha256 cel · 10/9/2016, 9:32:45 PM

I'm not able to reproduce this, but I have an idea why it might be happening. I will push a possible fix soon.

%NQSCj7wYA2D1dKmAB3FaPUAx79ISfdrM2r0U8M+DXsk=.sha256 cel · 10/9/2016, 9:59:08 PM

@matt

I attempted a fix in pull-git-remote-helper v1.4.0, which fixes setting the no-thin git capability which should tell the client to not send packs with unresolved deltas.

npm i -g git-ssb to update

%UAsmmIHXE0kBhSBH8L76rpqaXNARLes/L5yFtqTWL5Y=.sha256 Matt McKegg · 10/9/2016, 10:44:35 PM

Unfortunately I can't test this because I trashed the broken tree and recloned. Sorry about that, should have kept it for science :boom:

But I'm now I'm getting a new error on a different machine on all repos I try to push to. May have happened after upgrading sbot, but not entirely sure.

/usr/local/lib/node_modules/git-ssb/node_modules/git-remote-ssb/git-remote-ssb:58
        if (err) throw err
                 ^

Error: write EPIPE
    at exports._errnoException (util.js:1026:11)
    at WriteWrap.afterWrite (net.js:794:14)
error: failed to push some refs to 'ssb://%t3XQv5Gk/dzJQM1fWFnMlaTlTvmtd3BHYCTIzhT/7G8=.sha256'

Any ideas?

%sEFoo9g42Ewj/CKOdBx33RoWYk5M3mQAw+Cf5VIgMp8=.sha256 cel · 10/9/2016, 10:56:34 PM

@matt what happens if you add -vv to the push command?

%DasxDM202R/qDQap4eolsacwWMv5g30VUyK645Kdtuo=.sha256 Matt McKegg · 10/9/2016, 11:13:46 PM
Matts-MacBook-Pro:mutant matt$ git push ssb -vv
< "ok\n"
Pushing to ssb://%/Mvtvbf2G8AZC+nZb/aRl12VDvrhcBU7QMmuGYjGt/8=.sha256
command: connect git-receive-pack
< "\n"
< "00764c9ff2e15d10208c68d4ce7a98c9f26019f94439 refs/heads/master\u0000agent=pull-git-remote-helper/1.4.0 delete-refs no-thin\n"
< "003efe534beadaf10fda089b41261ca41124eff58fdd refs/tags/v1.0.0\n"
< "003e37f0d83c41d2fe873f23e2975d46467209b8692c refs/tags/v1.0.1\n"
< "003e9f51e0d852fbfa30547253af970027acdd6381ea refs/tags/v1.0.2\n"
< "003e76b6f69f5360020ee4236cb2105afa43997db120 refs/tags/v2.0.0\n"
< "003efda9ace09305f29e70fdfef94a30097ced96f5ba refs/tags/v2.0.1\n"
< "003eaf584da71367f01a02b39b474a09cd732bf89391 refs/tags/v2.1.0\n"
< "003ed70983725df9fae3df012bfa2ffbba8dbdbd327f refs/tags/v2.2.0\n"
< "003e043f3158dc7fc78d8a4164d57e678c3f91ffa475 refs/tags/v2.2.1\n"
< "003e2600a2a26fa7b1c43eea8a16ee631ea1caddd281 refs/tags/v3.0.0\n"
< "003e72c3f81f686f4ab9ffe485524ad82114cd6d7fcd refs/tags/v3.1.0\n"
< "003e0ed2b17cc02ac0b2ff9a483081ec56565e1d0bab refs/tags/v3.1.1\n"
< "003e7161b2d4f41bcc88e898da07f8612ff6669be142 refs/tags/v3.2.0\n"
< "003e4dbdb1a0f4600434bad3bcd12c48ef86bd41710c refs/tags/v3.2.1\n"
< "003e99c90769ab5e9015ef0a2d801ee1dea4372833bf refs/tags/v3.2.2\n"
< "003ece0118bd16ea00adfe3a9e97ce1bc3dc8428ab85 refs/tags/v3.3.0\n"
< "003e0e5bd2c56723a679c06eeaf1e859ca2becdf2b7b refs/tags/v3.3.1\n"
< "003e67f1bc6d8e3b08318faf679232e6854d25b1729f refs/tags/v3.3.2\n"
< "003e469451e53f1d563d87c76cf6b6a8b42da8a8a537 refs/tags/v3.3.3\n"
< "003efd7509f294af0d10fb32ad1373bf308d2df6d5ab refs/tags/v3.4.0\n"
< "003eb11d76238bfcf37fcbca11cfb27cac70d0dda580 refs/tags/v3.4.1\n"
< "003e5023ca146c63b47a3648086bf52821ee9647ca6f refs/tags/v3.5.0\n"
< "003edec24ba58e8ea029f0dde05c3d41a179abc9b618 refs/tags/v3.5.1\n"
< "003e18e37c1a524ed32a2d7a223e465844b7e9837239 refs/tags/v3.5.2\n"
< "0000"
line 
< "000eunpack ok\n"
/usr/local/lib/node_modules/git-ssb/node_modules/git-remote-ssb/git-remote-ssb:58
        if (err) throw err
                 ^

Error: write EPIPE
    at exports._errnoException (util.js:1026:11)
    at WriteWrap.afterWrite (net.js:794:14)
To ssb://%/Mvtvbf2G8AZC+nZb/aRl12VDvrhcBU7QMmuGYjGt/8=.sha256
 = [up to date]      master -> master
updating local tracking ref 'refs/remotes/ssb/master'
error: failed to push some refs to 'ssb://%/Mvtvbf2G8AZC+nZb/aRl12VDvrhcBU7QMmuGYjGt/8=.sha256'
%0v3eNYctrNyX+b7kRhIDB2UENkkt8kB6ekU1x05Eauk=.sha256 Matt McKegg · 10/10/2016, 12:16:59 AM

@cel Just noticed it only throws this error when there is nothing to push. If I run it on a repo with changes it works fine.

%v0L0vxVuVlfzh+pIgQOlMWRRlYy7V/huIkQdRi93VfI=.sha256 cel · 10/10/2016, 12:32:35 AM

ok. I'm not able to reproduce EPIPE right now. It probably has to do with pull-git-remote-helper not properly handling the stream closing early when there is nothing being pushed. What node and git versions are you using?

%bVAPa9Zihy22l5ivmsc5jw1ysJ6cnC9yOYHfrG7ko1Q=.sha256 Matt McKegg · 10/10/2016, 12:34:27 AM

git 2.8.4 (will try updating and see if it helps) node 6.4.0

Built with git-ssb-web