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.

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

Crash with unmarshallable json... #5

Closed
tcolgate opened this issue Feb 16, 2015 · 1 comment
Closed

Crash with unmarshallable json... #5

tcolgate opened this issue Feb 16, 2015 · 1 comment

Comments

@tcolgate
Copy link
Contributor

First off, thanks for the pkg. I was originally using hal, but have moved over to using your api and a tiny custom framework, and it's a real pleasure so far.

My bot is periodically dying, I suspect possibly due to something int he latency response code, I'll take a look soon, but thought I'd report it here just incase:

json: cannot unmarshal number into Go value of type slack.JSONTimeString

I've not got a definitive way of triggering the problem yet. Will send a PR if I work it out.

@nlopes
Copy link
Collaborator

nlopes commented Feb 16, 2015

Thank you for the report @tcolgate . SetDebug(true) might help. This will print out all events being received. The api is a bit inconsistent and sometimes slack returns a unix timestamp, other times it returns a string so I may have missed one of those cases.

Also, are you using the latest code in here? That bug definitely existed before I corrected some code last week.

@tcolgate tcolgate closed this as completed Mar 2, 2015
zchee pushed a commit to zchee/slack that referenced this issue Oct 16, 2019
kanata2 pushed a commit that referenced this issue Jun 14, 2022
…m-id

Added GetUsersOptionTeamID so that a team ID can be passed in for use
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants