-
-
Notifications
You must be signed in to change notification settings - Fork 414
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
Server Errors(HTTP 5XX) not handled in UI #124
Comments
I think that's actually just what the website did as well at the time; this is what happens when a server is completely off the Internet unexpectedly. |
@timabbott yes you are right , but in electron app this screen appears literally after a minute ,while in browser you can see the loading icon spinning , they at least know something is wrong server side , but in electron app user is completely clueless for that span of time due to the blank screen, I think we should add support in UI to handle this because our ultimate aim is a rich user experience by proper error handling too. I hope I am clear @timabbott @akashnimare |
Ahh, I see what you mean; yeah we should have some sort of loading indicator ... |
@timabbott I think we can handle this error by keeping a check on server response status code (especially 5XX errors)and adding a loading indicator. I would like to work on this @zulipbot claim |
Congratulations, @Lplenka, you've successfully claimed your first issue! Since you're a new contributor, you now have pull (read-only) access to this repository. Please review our code contribution guidelines and sign the Dropbox Contributor License Agreement before opening any pull requests for any issues that you're working on. Also, if you haven't done so already, please join us on the Zulip development server at chat.zulip.org! Our community of developers use chat.zulip.org as our primary communication forum for developing Zulip; you can read more about the chat.zulip.org community in our documentation. Note: Depending on your notification settings, granting you the permission in GitHub's model that allows you to be assigned issues by zulipbot may result in making you a "watcher" on this repository, which means that you'll get notifications for every issue and pull request in this repository; for a large repository like zulip/zulip, that means receiving over 100 emails per day. If you don't want to receive notifications unless you're actually involved with the issue (which is usually the right choice for large projects), you should unwatch this repository. |
@akashnimare @timabbott a loader page is possible till the main window completely loads but |
Hello @Lplenka, you claimed this issue to work on it, but this issue hasn't been updated for a week. Are you still working on this issue? If so, please update this issue by leaving a comment on this issue to let me know that you're still working on this issue within 3 days, or else I'll automatically remove your assignment from this issue. If you've decided to stop working on this issue, simply comment Thank you for your understanding and your valuable contributions to Zulip! |
@akashnimare I have added a function which checks for server status code every time some one connects or switches to a new server. If the server status is 5XX user gets the error dialog box informing about error, so he/she doesn't have to see a clueless white screen. I think this much fixes this issue. |
Check if zulip server is down Fixes Issue #124
Since today(06/03/2017) we witnessed the server(chat.zulip.org) was down
![screenshot from 2017-03-06 23-23-57](https://cloud.githubusercontent.com/assets/13533873/23624134/aba9250c-02ca-11e7-8fdc-9ac452516f72.png)
Currently in electron app there is no support to display 5XX HTTP status code i.e. server errors , so if server is down currently it just shows a clueless blank screen.After around a minute this is shown
This error page was shown very late,there should be support to show such error as soon as user clicks the connect button.
-
Operating System
: Linux Mint 18.1-
Zulip-Version
: 1.4.15The text was updated successfully, but these errors were encountered: