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
I'm sometimes experiencing panics like this when calling BackgroundSession::join:
called `Result::unwrap()` on an `Err` value: Os { code: 103, kind: ConnectionAborted, message: "Software caused connection abort" }
It seems that what triggers it is when the session is being joined and the mounted filesystem is being accessed more or less concurrently. I'm not sure whether this is a bug or not. I can imagine the error simply means the sending half of the internal channel has been closed, but I'm not sure. If that was the case, then this error should probably be handled inside Session::run. Or at least propagated to the caller of join so they can decide what to do with it.
The text was updated successfully, but these errors were encountered:
I'm sometimes experiencing panics like this when calling
BackgroundSession::join
:It seems that what triggers it is when the session is being joined and the mounted filesystem is being accessed more or less concurrently. I'm not sure whether this is a bug or not. I can imagine the error simply means the sending half of the internal channel has been closed, but I'm not sure. If that was the case, then this error should probably be handled inside
Session::run
. Or at least propagated to the caller ofjoin
so they can decide what to do with it.The text was updated successfully, but these errors were encountered: