Attachment ts field is sometimes a string about slack

[finack]

Funny I just ran into this as well. It showed up when I @ mentioned the bot in a channel it was not subscribed to, and then instructed slack to send them a message to the mention. The response has "ts":"1469909830.000018" in the attachment section.

I changed the json serializer to a string and this fixed the issue. Tests pass as well. But not sure what this breaks in reality.

It looks like the slack docs do call for an integer but now they are returning a string (as well?).

To replicate follow the NewRTM example, connect to slack, @ mention the bot, then have slackbot send them a link to your message.

The other thing of interest that I have not figured out is after this happens restarting the bot causes ConnectingEventErrors and then you get throttled. It goes away but not sure if it was because of time passing or me messing with /inviting and /kicking the bot.

[pendowski]

I changed to to string as well but it crashed in some other place, not sure if in different person's DM or @yourownnick. Will have to check it tomorrow but I think that changing the type doesn't solve the underlying issue. Is there a way to decode to int even if it's string (or from int to string)? Some custom dynamic mapping in go?

[mlabouardy]

use interface{} as data type
see https://github.com/nlopes/slack/issues/115