sentanos / roblox-js

!!!THIS PROJECT IS NO LONGER MAINTAINED!!! Execute ROBLOX website actions in node.js
MIT License
45 stars 45 forks source link

Is your example broken? #49

Closed checkraisefold closed 7 years ago

checkraisefold commented 7 years ago
    at Async._drainQueues (C:\Users\Dev\Desktop\misc\exileAllFromRank\node_modul
es\bluebird\js\release\async.js:143:10)
    at Immediate.Async.drainQueues (C:\Users\Dev\Desktop\misc\exileAllFromRank\n
ode_modules\bluebird\js\release\async.js:17:14)
    at runCallback (timers.js:666:20)
    at tryOnImmediate (timers.js:639:5)
    at processImmediate [as _immediateCallback] (timers.js:611:5)

The errors come crashing down. https://pastebin.com/4iu0znNY Says time: 0.624 MS and then doesn't do anything to group.

sentanos commented 7 years ago

Are you trying to exile everyone in that rank? If so pages should be null, right now you are only exiling people from exactly page 142

checkraisefold commented 7 years ago

I see. If I set pages to null, I get the horror of errors that are listed. It spams this error over and over. @sentanos

checkraisefold commented 7 years ago

This eventually happens, but no change to group members.

Ran out of tries for 1400
Ran out of tries for 1406
Ran out of tries for 1409
Ran out of tries for 1405
Ran out of tries for 1403
Ran out of tries for 1413
Ran out of tries for 1401
Ran out of tries for 1408
Ran out of tries for 1402
Ran out of tries for 1412
Ran out of tries for 1411
Ran out of tries for 1410
Ran out of tries for 1404
Ran out of tries for 1407
Ran out of tries for 1414
Time: : 449509.918ms
sentanos commented 7 years ago

This is because you are retrieving a lot of pages and your network or machine can't handle the large number of requests at once. You can remedy this by lowering the maxThreads value in the settings.json file.

On Aug 24, 2017, at 12:42, checkraisefold notifications@github.com wrote:

This eventually happens, but no change to group members.

Ran out of tries for 1400 Ran out of tries for 1406 Ran out of tries for 1409 Ran out of tries for 1405 Ran out of tries for 1403 Ran out of tries for 1413 Ran out of tries for 1401 Ran out of tries for 1408 Ran out of tries for 1402 Ran out of tries for 1412 Ran out of tries for 1411 Ran out of tries for 1410 Ran out of tries for 1404 Ran out of tries for 1407 Ran out of tries for 1414 Time: : 449509.918ms — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

checkraisefold commented 7 years ago

Or I can put it on heroku.

checkraisefold commented 7 years ago

Probably going to have to put it on heroku. 1 thread and it still does it.

sentanos commented 7 years ago

It could be due to something else. Are there any other errors at all other than "Ran out of tries"?

On Aug 24, 2017, at 17:08, checkraisefold notifications@github.com wrote:

Probably going to have to put it on heroku. 1 thread and it still does it.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.