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
// TODOM: Think of a better way to handle this. This should usually never happen only if a client disconnects for a longer time while saving.
283
+
// Maybe its ok to crash / enforce a reload in that case.
284
+
// One scenario in which this might happen is when the user disconnects from the internet while having the mutex and later reconnects.
285
+
thrownewError(
286
+
`No longer owner of the annotation mutex. Instead user ${blockedByUser ? `${blockedByUser.firstName}${blockedByUser?.lastName} (${blockedByUser?.id})` : "unknown user"} has the mutex.`,
console.error("Failed to continuously acquire mutex.",error);
294
+
yield*put(setUserHoldingMutexAction(undefined));
295
+
yield*put(setIsMutexAcquiredAction(false));
296
+
Toast.error(
297
+
"Unable to get write-lock needed to update the annotation. Please check your connection to WEBKNOSSOS. See the console for more information. Retrying soon.",
0 commit comments