Bug: "another git process seems to be running..." in sync mode

I’m still trying to reproduce the issue myself, since it pops up occasionally in my CI even with it inline.

Right now I’m having doubts as to whether or not “parallel” changes the behavior at all, or with what runners does it change the behavior, or if it only affects certain commands, such as nx run-many.

One possible guess is here:

https://github.com/jscutlery/semver/blob/2d72467f542dc026241114bf3a36e54b234010d5/packages/semver/src/executors/version/version.ts#L86

There might be a race condition with performing concurrent addToStage() since we’re using concatMap, so each project is still being updated in parallel. It’s hard to reproduce though, but if the changes at addToStage were performed sequentially it might help in my case.

In your case, my guess is that the addToStage() from updating the changeLogs and updating the packageJson hit at the same time, since those are also done in parallel:

https://github.com/jscutlery/semver/blob/2d72467f542dc026241114bf3a36e54b234010d5/packages/semver/src/executors/version/version.ts#L54

_Originally posted by @dereekb in https://github.com/jscutlery/semver/issues/500#issuecomment-1129200958_

[dereekb]

Your issue sounds the same as the other person’s here.

https://github.com/jscutlery/semver/issues/500#issuecomment-1126896815

It’s a tricky bug to reproduce, although I guess we know it is still happening for new projects that might not have that big of size. Wasn’t occurring on my machine at home, but was occurring sometimes on CircleCI, until I made a large enough release that it triggered every time. The race condition occurs on the filesystem.

I haven’t checked the e2e tests so I can’t speak to that, but if it isn’t invoking git on the CI machine directly then it won’t catch it.

[nradulaski-godaddy]

This issue happens all the time with affected and run-many unless I use --parallel=1.