Are concurrent pushes and fetches to the same repository via HTTP supported?

I'm facing a situation where multiple users are fetching from and pushing 
to remote repositories in a server running Apache and git-http-backend 
(clients and server version 2.1.1).

When concurrent pushes and fetches are happening on the same repository, 
the clients report this error:

To https://username:password <at> host.com/projectrepos/project.git
+ 3711f16...0bdfbc5 master -> master (forced update)
error: RPC failed; result=52, HTTP code = 0
fatal: The remote end hung up unexpectedly

remote: error: failed to lock refs/heads/master
To https://username:password <at> host.com/projectrepos/project.git
! [remote rejected] master -> master (failed to lock)
error: failed to push some refs to
'https://username:password <at> host.com/projectrepos/project.git'

The server logs show errors like these:

error: Ref refs/heads/master is at f38a8a79752eac8a53fd195bc37fc56c0faf5cfa 
but expected a586117cd41604b8b2cb9776a98715c591071ad1
error: Ref refs/heads/master is at 6e1108c108ae464a37cbb3ccc84db934656cbcb4 
but expected f38a8a79752eac8a53fd195bc37fc56c0faf5cfa
fatal: git upload-pack: not our ref f38a8a79752eac8a53fd195bc37fc56c0faf5cfa
error: Ref refs/heads/master is at 6e1108c108ae464a37cbb3ccc84db934656cbcb4 
but expected f38a8a79752eac8a53fd195bc37fc56c0faf5cfa
error: Ref refs/heads/master is at cc853c06962b3562e46cfefb3986abef914809b5 
but expected 6e1108c108ae464a37cbb3ccc84db934656cbcb4

These errors don't happen when accessing a repository on the filesystem 
instead of via HTTP transport.

Does git support concurrent fetch and push operations?

Are there any restrictions to doing that via the HTTP backend?

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to