We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Here's the scenario that was reported and my guess as to what it was:
Fix:
Don't delete yourself, always make sure the current node is part of the assignments
The text was updated successfully, but these errors were encountered:
Easy money, fix coming soon.
Sorry, something went wrong.
Latching the code to not delete the current node as stale. Closes GH-…
de2fc69
…1116
f52db93
No branches or pull requests
Here's the scenario that was reported and my guess as to what it was:
Fix:
Don't delete yourself, always make sure the current node is part of the assignments
The text was updated successfully, but these errors were encountered: