1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Resolved Exception alerts

Discussion in 'Client & Site Support' started by Defeat3d, Sep 6, 2015.

  1. Defeat3d

    Defeat3d Primate

    Joined:
    Oct 30, 2014
    Messages:
    3,025
    Likes Received:
    1,890
    Can we please have an option disable these? It gets a little annoying when you have a bot you're rewriting and the old version gives you 100+ notifications per day.
    --- Double Post Merged, Sep 6, 2015, Original Post Date: Sep 6, 2015 ---
    Also worth mentioning, most of these exceptions are thrown because someone is stopping the bot during Execution#delayUntil(), and they all give you alerts because they're unique because of the random(?) numbers in lambda references.

    Ex: at productions.celestial.bots.hunter.v2.tasks.general.LayTrap.lambda$execute$396(LayTrap.java:45)

     
  2. Best Answer:
    Post #11 by Arbiter, Sep 6, 2015
  3. Baddest Man on Earth

    Joined:
    Nov 26, 2014
    Messages:
    616
    Likes Received:
    246
    Or just make the bots hidden because they are broken or outdated anyways.
     
  4. Defeat3d

    Defeat3d Primate

    Joined:
    Oct 30, 2014
    Messages:
    3,025
    Likes Received:
    1,890
    Except it's not broken and is one of the most ran bots on here.
     
  5. Baddest Man on Earth

    Joined:
    Nov 26, 2014
    Messages:
    616
    Likes Received:
    246
    Then patch whatever is causing the exceptions.
     
  6. Defeat3d

    Defeat3d Primate

    Joined:
    Oct 30, 2014
    Messages:
    3,025
    Likes Received:
    1,890
    Execution#delayUntil() :^)
     
  7. Exia

    Joined:
    Nov 3, 2013
    Messages:
    609
    Likes Received:
    259
    I've never gotten any errors from people stopping the script bot during Execution delays. And if it is the case where the exception is unavoidable then it is an acceptable time to surround it with a try catch.
     
  8. Arbiter

    Arbiter Mod Automation

    Joined:
    Jul 26, 2013
    Messages:
    2,937
    Likes Received:
    1,266
    @Defeat3d please provide an example to assess.
     
  9. Defeat3d

    Defeat3d Primate

    Joined:
    Oct 30, 2014
    Messages:
    3,025
    Likes Received:
    1,890
    Here's one: [​IMG]
    Here's another: [​IMG]

    The only difference is the numbers after "rm.coN$$Lambda$NUMBERS/NUMBERS.call"
     
  10. Arbiter

    Arbiter Mod Automation

    Joined:
    Jul 26, 2013
    Messages:
    2,937
    Likes Received:
    1,266
    The line below the "Called by" is the relevant one. Check out that line and fix what's actually causing the error. Hiding it is just avoiding the problem.
     
  11. Defeat3d

    Defeat3d Primate

    Joined:
    Oct 30, 2014
    Messages:
    3,025
    Likes Received:
    1,890
    I know, but that has nothing to do with what I'm requesting here, lol.
     
  12. Arbiter

    Arbiter Mod Automation

    Joined:
    Jul 26, 2013
    Messages:
    2,937
    Likes Received:
    1,266
    Adding the ability to turn it off is enabling Bot Authors to ignore bot-breaking bugs. Not exactly something we want to be wasting dev hours on.
     
  13. Defeat3d

    Defeat3d Primate

    Joined:
    Oct 30, 2014
    Messages:
    3,025
    Likes Received:
    1,890
    Fair enough.
     
  14. Cloud

    Cloud Engineer

    Joined:
    Jul 28, 2013
    Messages:
    2,777
    Likes Received:
    1,124
    "most of these exceptions are thrown because someone is stopping the bot during Execution#delayUntil(),".
    delayUntil should never throw an exception itself, instead your condition is likely the source of the error.
     

Share This Page

Loading...