Skip to content

Conversation

backportbot-nextcloud[bot]
Copy link

@backportbot-nextcloud backportbot-nextcloud bot commented Oct 1, 2020

⚠️ This backport had conflicts and is incomplete ⚠️

backport of #758

So before this PR, we tried to act on 400 errors already,
but I didn't know that they throw an exception on the `post()`,
so instead of performing on the response body,
we `continue;` after we logged an info 😯

This is of course not what was intended. Further more,
since the notifications are grouped and the proxy had an error
which would immediately bail out with a 400 when there was 1 broken notification,
instead of sending the rest, 1 broken notification was enough to not
send any notification anymore. And since we never deleted the broken
device the instance didn't "heal" itself, but always broke like this.

Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
Signed-off-by: Joas Schilling <coding@schilljs.com>
@nickvergessen nickvergessen force-pushed the backport/758/stable19 branch from d4015bb to 938c005 Compare October 1, 2020 12:13
@nickvergessen nickvergessen merged commit bf8574a into stable19 Oct 1, 2020
@nickvergessen nickvergessen deleted the backport/758/stable19 branch October 1, 2020 13:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant