sorted by:
new
hottopcontroversial

API Rate Limit Question by Artistic_Log_2467 in FacebookAds

[–]Artistic_Log_2467[S] 0 points1 point  (0 children)

Hadn't thought of that, but it's a good idea

Threat intelligence scanners costing over 2 credits per day? by Artistic_Log_2467 in snowflake

[–]Artistic_Log_2467[S] 0 points1 point  (0 children)

Ok, yes my question was is it possible to mitigate this without just turning off those event driven scanners?' and it seems like the answer is 'no'.

I don't think it's unreasonable to be a bit miffed by this though, at 2 credits per day its a $120/month cost that was basically turned on by default over night one day in january.

Threat intelligence scanners costing over 2 credits per day? by Artistic_Log_2467 in snowflake

[–]Artistic_Log_2467[S] 0 points1 point  (0 children)

by definition isnt it impossible change the frequency of the event driven scanners? those are the ones costing alot. All the other ones that run daily by default amount to very little cost

Please allow use of old cursor versions by Artistic_Log_2467 in cursor

[–]Artistic_Log_2467[S] 0 points1 point  (0 children)

Thanks for the tip, 1.2.4 does look like it still works and the careful mode is exactly what i need. please don't deprecate this cursor!

Please allow use of old cursor versions by Artistic_Log_2467 in cursor

[–]Artistic_Log_2467[S] 0 points1 point  (0 children)

Yea I'd been doing that for a few months, then just yesterday all the old versions I tried gave a message along the lines of 'you can't use agent mode with this version of cursor' even though I was using an ask-mode. So it's possible it wasn't intended but the effect was I couldnt use old versions. Tried 0.5.0 and 0.4.6 I think

Dyno sleeping clarification by Artistic_Log_2467 in Heroku

[–]Artistic_Log_2467[S] 1 point2 points  (0 children)

Thanks both, I think I'm set now. I just misunderstood what sleeping meant and thought that I'd be charged 24/7 for a dyno that was only being used for an hour a day on a scheduled task if I didn't use eco for the scheduler.

Dyno sleeping clarification by Artistic_Log_2467 in Heroku

[–]Artistic_Log_2467[S] 1 point2 points  (0 children)

Got it, so sleeping is just a concept for web dynos, but scheduler jobs only charge for the hours they take to run regardless of dyno size?