Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Client Should parse Server Broadcast messages #14

Closed
hawkerm opened this issue May 3, 2015 · 1 comment
Closed

Client Should parse Server Broadcast messages #14

hawkerm opened this issue May 3, 2015 · 1 comment
Assignees
@hawkerm
Labels
bug client

Comments

@hawkerm
Copy link
Member

hawkerm commented May 3, 2015

This currently should only occur when the server gets gracefully terminated. It just causes a big exception stack to show in the client, but it should be handled a bit more gracefully in general in the client.

This is due to the fact that the json is sending [0,null](server -> all), but the client is explicitly expecting [int, int] and doesn't seem to parse 'null' as an integer.
@hawkerm hawkerm added the bug label May 3, 2015
@hawkerm
Copy link
Member Author

hawkerm commented May 5, 2015

Will open new bug for terminating. Resolving this one on push.

@hawkerm hawkerm assigned hawkerm and unassigned wortzmanb May 5, 2015
@hawkerm hawkerm mentioned this issue May 5, 2015
Closed
@hawkerm hawkerm added the client label May 5, 2015
@hawkerm hawkerm closed this as completed in bbfeb1d May 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hawkerm hawkerm

Labels
bug client
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wortzmanb @hawkerm