-
Notifications
You must be signed in to change notification settings - Fork 481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As a user, I'd like to know when an update check triggered by me fails #2086
Labels
Milestone
Comments
pinussilvestrus
pushed a commit
that referenced
this issue
Apr 16, 2021
bpmn-io-tasks
bot
added
in progress
Currently worked on
and removed
backlog
Queued in backlog
labels
Apr 16, 2021
bpmn-io-tasks
bot
added
needs review
Review pending
and removed
in progress
Currently worked on
labels
Apr 16, 2021
As a user I'd expect that background update checks do not disturb be, cf. #2216 (comment). So my expectation is exactly the opposite of what you expect 😉. |
pinussilvestrus
pushed a commit
that referenced
this issue
Apr 16, 2021
I totally agree with you. Not sure why I did not specify it in the issue that I meant only the checks triggered by the user. |
barmac
changed the title
As a user, I'd like to know when update check fails
As a user, I'd like to know when an update check triggered by the user fails
Apr 16, 2021
barmac
changed the title
As a user, I'd like to know when an update check triggered by the user fails
As a user, I'd like to know when an update check triggered by me fails
Apr 16, 2021
Closed via #2216 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is your feature request related to a problem? Please describe.
When I trigger update check and there are network problems or the update server responds with anything but 200, it fails silently and the user can only notice it via console.
Describe the solution you'd like
Show a notification on such problems.
Describe alternatives you've considered
Leave it as it is.
The text was updated successfully, but these errors were encountered: