-
Notifications
You must be signed in to change notification settings - Fork 50
wrap this update call in a retry that ignores conflict errors #452
Comments
@exdx we reviewed this in the Issue Triage meeting. One concern that was raised focused on the fact that:
@joelanford recommended:
Could you comment why it makes sense to retry and ignore error conflicts. |
I think this was created because updating the configmap could hit conflict errors, so it might be safer to wrap it in a retry (like we do in other places in the codebase). If we delete all this code, sure it will be obsolete. |
Yeah, I think we can handle that conflict error at any call site though, so adding explicit wrapping logic to retry on conflict outside of the driver code may be the wrong implementation. |
Sure. I didn't really expect an issue to be created regarding this, I can go ahead and remove the TODO to close this one. |
@exdx Sounds good to me. I think automation will close this once the TODO comment is deleted too, which is nice. |
Hmm yeah that's cool, let's see if it does. Opened #465 |
Didn't auto-close, I'll just clean this up manually. |
Yeah, it looks like the action silently failed sadly. |
rukpak/internal/source/local.go
Line 67 in 10bea78
The text was updated successfully, but these errors were encountered: