This repository has been archived by the owner on May 25, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 172
bw sync reports as successful even when server is unreachable #129
Comments
Stumbled upon this again; still present with
|
fredrikekre
added a commit
to fredrikekre/jslib
that referenced
this issue
Nov 20, 2020
…Sync The motivation for this is bitwarden/cli#129 where failed sync's are swallowed by try-catch. By moving the try-catch to the outside it is possible to reuse the already existing allowThrowOnError argument which callers can use to signal whether fullSync should throw or ignore errors silently. This patch is companioned with a patch to the SyncCommand CLI command to pass allowThrowOnError.
fredrikekre
added a commit
to fredrikekre/cli
that referenced
this issue
Nov 20, 2020
This intends to make explicit calls to bw sync throw if the syncing can not be performed, fixes bitwarden#129.
fredrikekre
added a commit
to fredrikekre/jslib
that referenced
this issue
Nov 20, 2020
…Sync The motivation for this is bitwarden/cli#129 where failed sync's are swallowed by try-catch. By moving the try-catch to the outside it is possible to reuse the already existing allowThrowOnError argument which callers can use to signal whether fullSync should throw or ignore errors silently. This patch is companioned with a patch to the SyncCommand CLI command to pass allowThrowOnError.
cscharf
pushed a commit
to bitwarden/jslib
that referenced
this issue
Nov 23, 2020
…Sync (#207) The motivation for this is bitwarden/cli#129 where failed sync's are swallowed by try-catch. By moving the try-catch to the outside it is possible to reuse the already existing allowThrowOnError argument which callers can use to signal whether fullSync should throw or ignore errors silently. This patch is companioned with a patch to the SyncCommand CLI command to pass allowThrowOnError.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
bw sync
reports as successful even when server is unreachable. In contrast, the Firefox browser plugin instead gives an error messageSyncing failed
as expected.Might be the same root cause as #12 but this is for a very different reason so opening a new issue.
Here is a reproducible example (using
bitwarden_rs
as a server, but should be irrelevant).Create a dummy user from the browser and login
Syncing works as expected
Now shut down the server
and yet
bw sync
reports succesful syncing, but checking last sync time verifies that it wasn't actually syncing.Version:
The text was updated successfully, but these errors were encountered: