You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 7, 2024. It is now read-only.
I think probably what we should do is change the GC invocation we make as part of the upgrader to be "best effort, log but don't propagate errors". But I think we also should at least in the unit tests actually make GC errors there fatal to ensure we catch bugs reliably.
The text was updated successfully, but these errors were encountered:
See #404 (comment)
I think probably what we should do is change the GC invocation we make as part of the upgrader to be "best effort, log but don't propagate errors". But I think we also should at least in the unit tests actually make GC errors there fatal to ensure we catch bugs reliably.
The text was updated successfully, but these errors were encountered: