-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Object [hash] already has a mark" on pushing #16
Comments
Do you have a series of steps to reproduce this? |
I am also having this issue hg version 2.4.1 and git 1.8.1.4.. however I can not push changes. as it promptly rejects the change claiming it's a non-fast-forward push? and that my branch is behind,.. however it is not.. it's the same as the remote.. |
On our private repo at work, it happens on just about every push. I'm not sure how I'd go about getting it to be reproducible on a fresh repo, though. |
same here, any solution? git 2.3 hg 2.8.2 |
@dfens to everybody who runs into this: If you have a way to reproduce it, I can look into it. Otherwise, this is just stabbing in the dark :-/ |
@fingolfin For what it's worth, I'm not using the bridge anymore; I just decided to never work on a Mercurial project again. ;-) More seriously, I think @felipec has abandoned the project; your fork seems to be active, and should probably be the first stop for people trying to get this working. |
I actually just realized that I found a reproducible example for this... :) See fingolfin#2 @tomxtobin Yeah, it seems this is abandoned -- unfortunely, it still seems to be the number 1 hit on Google for |
@felipec I don't know if you're reading, but any thoughts to giving official blessing to @fingolfin's fork? If you're willing, an official pointer in the README would go a long way. :-) |
@fingolfin
|
@sayadyan Thanks, that is quite helpful. This suggests that at least one source of this bug is a concurrency issue. It might also suggest a way to easily reproduce the issue. E.g. instead of cloning a big repo, one could insert an artificial delay into But I can't promise I'll get to work on this anytime soon. |
Concurrency is not supported. Only one command should be run at a time. |
Unfortunately, I may be working on a Mercurial repo in the near future, so I have a renewed interest in seeing this bug fixed. ;-) @felipec, if you're back to working on the project, it's great timing! For what it's worth, the original issue I reported was not a result of my running concurrent operations. |
Yeah, I thought so. The concurrency issue is a different thing. |
If anybody is still experiencing this, feel free to comment and I'll reopen, in the meantime. |
This looks similar to felipec/git#48, but I'm getting this on the latest version of standard Git (2.1) and the latest git-remote-hg:
The text was updated successfully, but these errors were encountered: