-
-
Notifications
You must be signed in to change notification settings - Fork 963
Fixes for #331 and #332 #333
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
Conversation
I haven't been able to test it out with new changes because my local getUpdates test bot returns error on dev branch now: But following the logic in new ServerResponse it should be fine... |
No I didn't look so far. @jacklul we need to align this with the new develop to fix the travis fail |
All should be good now! |
yessss |
There seems to be another issue with this. Will need to find out the underlying issue here, pin point if-else exceptions aren't so super-duper-awesome...
|
That's because we don't have I'll PR it! |
Those are fixes I applied to my bots.
Fixes #331
Addresses latest API update causing library to throw exceptions (channel messages), mentioned #332