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
Following on from a review of #6996, there are a few other places in the UCX communicator backend where we should be catching exceptions on message transfer.
In addition, some of the try catch blocks can have their scope tightened (to avoid hiding other errors).
cc @pentschev, I will self-assign, but don't have privileges to do so.
The text was updated successfully, but these errors were encountered:
Ah, when I said self-assign I meant that I would do it (but you got to it too fast!).
I understood, but I said I would do it when we first discussed, unfortunately it slipped my mind after all the trouble we had to actually get #6996 in. Thanks for the reminder!
Following on from a review of #6996, there are a few other places in the UCX communicator backend where we should be catching exceptions on message transfer.
In addition, some of the try catch blocks can have their scope tightened (to avoid hiding other errors).
cc @pentschev, I will self-assign, but don't have privileges to do so.
The text was updated successfully, but these errors were encountered: