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

Error: Invalid Slack response #110

Open
benoitc opened this issue Oct 8, 2015 · 11 comments · May be fixed by #303
Open

Error: Invalid Slack response #110

benoitc opened this issue Oct 8, 2015 · 11 comments · May be fixed by #303

Comments

@benoitc
Copy link

benoitc commented Oct 8, 2015

I got the following error recently on slackin after days without any problem:

$ /usr/local/bin/slackin --interval 5000 --port 10000 domain xxxx
Thu Oct 08 2015 20:10:52 GMT+0200 (CEST) – fetching
Thu Oct 08 2015 20:10:52 GMT+0200 (CEST) – listening on *:10000
Thu Oct 08 2015 20:10:53 GMT+0200 (CEST) – ready
WARN: no logo configured
Thu Oct 08 2015 20:10:53 GMT+0200 (CEST) – online 6, total 29
Thu Oct 08 2015 20:10:58 GMT+0200 (CEST) – fetching
Thu Oct 08 2015 20:10:59 GMT+0200 (CEST) – Error: Invalid Slack response: 429
at SlackData.onres (/usr/local/lib/node_modules/slackin/node/slack.js:77:22)
at /usr/local/lib/node_modules/slackin/node/slack.js:41:17
at Request.callback (/usr/local/lib/node_modules/slackin/node_modules/superagent/lib/node/index.js:746:30)
at Request. (/usr/local/lib/node_modules/slackin/node_modules/superagent/lib/node/index.js:135:10)
at emitOne (events.js:77:13)
at Request.emit (events.js:169:7)
at IncomingMessage. (/usr/local/lib/node_modules/slackin/node_modules/superagent/lib/node/index.js:938:12)
at emitNone (events.js:72:20)
at IncomingMessage.emit (events.js:166:7)
at endReadableNT (_stream_readable.js:893:12)
Thu Oct 08 2015 20:10:59 GMT+0200 (CEST) – retrying
Thu Oct 08 2015 20:11:09 GMT+0200 (CEST) – fetching
Thu Oct 08 2015 20:11:09 GMT+0200 (CEST) – Error: Invalid Slack response: 429
at SlackData.onres (/usr/local/lib/node_modules/slackin/node/slack.js:77:22)
at /usr/local/lib/node_modules/slackin/node/slack.js:41:17
at Request.callback (/usr/local/lib/node_modules/slackin/node_modules/superagent/lib/node/index.js:746:30)
at Request. (/usr/local/lib/node_modules/slackin/node_modules/superagent/lib/node/index.js:135:10)
at emitOne (events.js:77:13)
at Request.emit (events.js:169:7)
at IncomingMessage. (/usr/local/lib/node_modules/slackin/node_modules/superagent/lib/node/index.js:938:12)
at emitNone (events.js:72:20)
at IncomingMessage.emit (events.js:166:7)
at endReadableNT (_stream_readable.js:893:12)
Thu Oct 08 2015 20:11:09 GMT+0200 (CEST) – retrying
@benoitc benoitc mentioned this issue Oct 8, 2015
Closed
@phazonoverload
Copy link

I'm also getting this issue, seems to be a rate limit thing. Any way to fix this?

@benoitc
Copy link
Author

benoitc commented Oct 13, 2015

I increased the timeout to 5mn and it did the trick. Maybe it should be the default?

@limulus
Copy link
Contributor

limulus commented Oct 13, 2015

Is this with the latest version of slackin? In v0.6.0, there is a patch from a Slack employee that reduces the load on their servers. It may be that Slack has understandably started rate limiting the older, more resource-intensive way of doing things.

@benoitc
Copy link
Author

benoitc commented Oct 13, 2015

@limulus hrm it is the latest version in npm 5 days ago yes

@limulus
Copy link
Contributor

limulus commented Oct 15, 2015

Looks like the version on npm is not v0.6.0, per #114.

@purplelightsaber
Copy link

@benoitc I am getting the same error (Error: Invalid Slack response: 429...) how did you set the timeout to 5mn?

@Xyene
Copy link

Xyene commented Feb 22, 2017

I have the same question as @purplelightsaber — slackin has recently (last two weeks) started getting 429s from Slack. Is there an easy fix for this that we could use on our ends? It's been preventing a number of people from signing up, so it'd be nice if there was a solution or workaround available.

@vgrbr
Copy link

vgrbr commented Feb 24, 2017

@purplelightsaber @Xyene did you tried to increase "interval" from slackin configuration? I had same issue but increasing interval to 10000 fixed problem.

@Xyene
Copy link

Xyene commented Feb 24, 2017

@vgrbr That was one of the things I tried — increasing the interval via -i to 30000, but that didn't resolve the issue. I'm primarily using the SVG badge, so my only idea is that perhaps slackin isn't caching the user count, and instead retrieving it every badge load.

@vgrbr
Copy link

vgrbr commented Feb 24, 2017

Sorry that worked only for my local env... on now.sh I'm getting same error :(

@szkl szkl linked a pull request Mar 23, 2017 that will close this issue
Open
@lvnilesh
Copy link
Contributor

lvnilesh commented Feb 23, 2018 •
edited

this pr #303 resolves #110

@Bhanditz Bhanditz mentioned this issue Nov 25, 2023
Open
@soloinovator soloinovator mentioned this issue Nov 28, 2023
Open
@eistrati eistrati mentioned this issue Dec 2, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Handle too many requests response szkl/slackin
7 participants
@benoitc @lvnilesh @limulus @Xyene @phazonoverload @vgrbr @purplelightsaber