-
Notifications
You must be signed in to change notification settings - Fork 8
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
Race condition in file sync w/ spinner #160
Comments
Note that simply re-running the desired command is usually ok and avoids this issue since it is a race condition. |
I am able to semi-reliably reproduce this error with these steps:
i generally then run |
I think I found it: slok/gospinner#3 |
Believe this fixed with #173 which should be out with the 2.2.0 release which is now available as an RC |
Looks like the firx with gospinner hasn't been completely successful in resolving this issue. I just received the following on a
|
Just to add...I have also gotten this seg fault in the rc2 version. |
Problem
A race condition in the spinner logging around the rig sync initialization is causing a panic. I've seen this once during rig development where I'd been triggering sync dozens of times, and there has been one other reported case.
Solution
Figure out why this is happening and fix that? Failing this, find the right spot to drop a recover statement to re-start the sync since most runs don't hit this problem.
The text was updated successfully, but these errors were encountered: