4e7acd9091
feat(GODT-2509): Migrate TLS cert from v1/v2 location during upgrade to v3
2023-03-22 10:26:22 +01:00
3ca5d0af71
fix(GODT-2516): log error when the vault key cannot be created/loaded from the keychain.
2023-03-21 17:25:35 +01:00
b1ad0ab6dc
test: Add 503 request test for message create event
...
Simulate 503 status during a message create event when the message
data is being downloaded.
2023-03-21 14:37:20 +01:00
7c232b1331
fix(GODT-2469): Fix sentry revision hash for cmake on windows.
2023-03-09 14:50:34 +01:00
7be46a4740
fix(GODT-2467): elide long email adresses in 'bad event' QML notification dialog.
2023-03-09 12:16:26 +01:00
c3454360fc
fix(GODT-2442): Remove unnecessary call to go-sync
...
This is not required in this call since address mode changes are always
proceeded by the removal of the IMAP user and then the creation of a new
IMAP user which will trigger the sync again.
2023-03-08 17:39:08 +01:00
182dab18a6
fix(GODT-2442): Handle event poll not starting after resync
...
It is possible, on slower machines, that the new event poll task is not
yet registered and attempts to cancel have nothing to cancel.
In this case, we need the refresh event to cancel the task, at that
point it is guaranteed that the task exists.
2023-03-08 17:39:04 +01:00
05a2c9d254
fix(GODT-2442): cli error
2023-03-08 15:32:25 +01:00
d926dd3806
chore: refactor: error cause type.
2023-03-08 11:57:19 +01:00
7cc2f3361d
feat(GODT-2444): added queue system for UserBadEvent from different accounts.
2023-03-08 09:50:38 +01:00
c496d6c71c
fix(GODT-2442): GUI changes for new bad event dialog.
2023-03-07 20:39:15 +01:00
7fc907a874
fix(GODT-2442): must publish loggedOut event.
2023-03-07 18:56:06 +01:00
b953468af2
fix(GODT-2419): avoid context canceled reports
2023-03-07 18:32:33 +01:00
9f4caa4948
feat(GODT-2442): add notification and feedback to CLI.
2023-03-07 17:59:04 +01:00
86630ce137
chore(GODT-2442): improve naming, remove unrelated changes
2023-03-07 17:59:04 +01:00
2c9477d65c
fix(GODT-2442): WIP: bad events just aborts polls, feedback processed in separete channel.
2023-03-07 17:59:04 +01:00
34c002ff68
test(GODT-2442): test bad event feedback and clean-up.
2023-03-07 17:59:04 +01:00
f03688ba72
feat(GODT-2442): add gRPC interface to send feedback.
2023-03-07 17:59:04 +01:00
8c0bb22de3
feat(GODT-2442): handle bad event resync resolution.
2023-03-07 17:59:04 +01:00
53c2cbcaee
test(GODT-2442): test refresh event
2023-03-07 17:59:04 +01:00
3ca56cfab3
fix(GODT-2458): Wait for both bridge and bridge-gui to be ended before restarting on crash.
2023-03-07 15:44:58 +00:00
70950e0048
fix(GODT-2457): Include address if GetPublickKeys() error message
2023-03-07 12:58:12 +01:00
2aa4e7c9da
feat(GODT-2446): Attach logs to sentry reports for relevant bridge-gui exceptions.
2023-03-06 18:36:40 +01:00
227bbf1c03
fix(GODT-2425): Out of sync messages and read status
...
Apply fix required for gluon update.
Update Gluon to include revision where the fix was made. Includes:
* https://github.com/ProtonMail/gluon/pull/313
* https://github.com/ProtonMail/gluon/pull/316
* https://github.com/ProtonMail/gluon/pull/317
2023-03-06 12:18:03 +00:00
1d426e621c
fix(GODT-2449): fix bug in Bridge-GUI's Exception::what().
2023-03-06 12:01:56 +00:00
6e4dcdb93b
feat(GODT-2435): Group report exception by message if exception message looks corrupted.
2023-03-06 09:33:20 +01:00
20f35edc83
chore: fix missing import after cherry-pick.
2023-03-06 08:25:24 +00:00
26cf684fb8
chore: fill sentry user.id with hostname.
2023-03-06 08:25:24 +00:00
2a4cb6a916
chore: fix sentry tag for dev and release on GUI side.
2023-03-06 08:25:24 +00:00
caa4a5cbdb
feat(GODT-2356): unify sentry release description and add more context to it.
2023-03-06 08:25:24 +00:00
91900a7942
feat(GODT-2357): Hide DSN_SENTRY and use single setting point for DSN_SENTRY.
2023-03-06 08:25:24 +00:00
04a7a81e27
chore(GODT-2444): Bad event info
2023-03-03 13:02:09 +00:00
53d5619c51
fix(GODT-2447): Don't assume timestamp exists in log filename
2023-03-03 10:27:21 +01:00
69aa784d32
fix(GODT-2426): Fix crash on user delete
...
Ensure we are always acquiring a write lock when modifying the user's
`updateCh` contents.
2023-03-01 12:02:12 +01:00
9e4310712c
fix(GODT-2419): Use connector.ErrOperationNotAllowed
...
Return this error when we detect operations that we know are not allowed
so that gluon does not report them to sentry.
Includes Gluon update for the connector error
(https://github.com/ProtonMail/gluon/pull/309 )
2023-02-28 17:02:35 +01:00
0b35b275d3
fix(GODT-2333): Do not allow modifications to All Mail label
...
Rather than waiting for API to reply, prevent these operations from
taking place in the first place.
2023-02-28 16:51:23 +01:00
82af4e01bc
feat(GODT-2364): wait and retry once if the gRPC service config file exists but cannot be opened.
2023-02-28 06:21:36 +01:00
9ad5f74409
feat(GODT-2364): added optional details to C++ exceptions.
2023-02-28 06:21:25 +01:00
10cf153678
fix(GODT-2413): use qEnvironmentVariable() instead of qgetenv().
2023-02-27 15:41:26 +01:00
ad0d4ebd36
fix(GODT-2412): Don't treat context cancellation as BadEvent
2023-02-27 14:34:35 +01:00
9f3c14ab1e
fix(GODT-2404): Handle unexpected EOF
...
When fetching too many attachment bodies at once, the read can fail with
io.ErrUnexpectedEOF. In that case, we returun an error so the fetch is retried.
2023-02-27 14:33:44 +01:00
74cf5d422b
fix(GODT-2390): Missing changes from pervious commit
...
Always reports error type to sentry.
Add error checks for get event as well.
2023-02-27 14:33:38 +01:00
dcf694588c
fix(GODT-2390): Add reports for uncaught json and net.opErr
...
Report to sentry if we see some uncaught network err, but don't force
the user logout.
If we catch an uncaught json parser error we report the error to sentry
and let the user be logged out later.
Finally this patch also prints the error type in UserBadEvent sentry
report to further help diagnose issues.
2023-02-27 14:33:21 +01:00
94ed09b437
feat(GODT-2366): Handle failed message updates as creates
...
This handles the following case:
- event says message was created
- we try to fetch the message but API says the doesn’t exist yet — we skip applying the “message created” update
- event then says message was updated at some point in the future
- we try to handle it but fail because we don’t have the message — we should treat it as a creation
2023-02-21 16:07:27 +01:00
57962e5757
chore: Bump gluon to create missing messages during MessageUpdated
2023-02-21 16:07:27 +01:00
2faeebe9e7
chore: Bridge Perth Narrows 3.0.16/17
2023-02-16 17:46:31 +01:00
f6727a56d2
fix(GODT-2371): Continue, not return, when handling draft
2023-02-16 17:46:24 +01:00
b4b66f94ec
feat(GODT-2355): improve wording and actions on bad event
2023-02-13 14:27:34 +01:00
cbd36184bd
feat(GODT-2354): report failed to load users.
2023-02-10 11:53:05 +00:00
465f754803
feat(GODT-2353): show popup only after 3.0.16
2023-02-09 17:00:58 +01:00
