-
Notifications
You must be signed in to change notification settings - Fork 22
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
in Replace: id matched 2 resources
error can still be reached
#754
Comments
Ah I looked a bit closer at the logs and I think this is #707. So I think after that error happens flux-local just doesn't exit cleanly. |
Hum, but you checked in a fix for this (#734), so this should not be happening anymore? |
Yeah, i think your assessment looks right. Yeah, thought that was fixed. What version of flux-local are you running? (I saw you had a fork and your own images so just want to make sure its not a version that is behind) |
I'll do another clean repro tomorrow using known-bad hashes from my repo (I've applied a workaround since reporting), but I am reasonably sure I reproduced with the above docker command, which pulls from your repo. But maybe the |
Yep, i see you're right in your example above. Will have to take a closer look, thanks. |
I've updated the reproduction steps to use stable tags for this issue. |
RuntimeError: Event loop is closed
when diffing in my repoin Replace: id matched 2 resources
error can still be reached
Summary
My repo somehow still reproduces the
in Replace: id matched 2 resources
error originally reported in #707:This issue was originally filed about the
RuntimeError: Event loop is closed
error, which is a separate problem where flux does not exit cleanly after reporting an earlier error.Reproduction
The text was updated successfully, but these errors were encountered: