Weather plugin excessively calling forecast.io API? about xbar-plugins HOT 5 CLOSED

I'm seeing some craziness on my side as well- what version bitbar are you using? I just recently updated to v1.6 and it seems to be going wild on me as well.

For reference, before updating to v1.6 i'd average around 120+/- a day, with a few manual refreshes here and there.

from xbar-plugins.

Wow, my english sounds terrible, when I'm in a rush - sorry about that.

Yes, I am on the latest BitBar release 1.6, but nothing seems to indicate that the plugins are called more often than what their scheduled time says. I added some simple logging, but didn't see anything out of the ordinary, yet.

Actually, my computer was asleep many of those hours in the last 48 hour period and I would have expected an even lower number of API calls. Checking the Activity Monitor I did notice that BitBar has quite a high "Average Energy Impact". That number is almost 10 x the Safari Number and exactly 10 x my main text editor and both of these applications are open all the time and I would assume are a bit more resources hungry than BitBar ?

I do have 5 Python plugins and I know that "Avg Energy Impact" calculation is probably to be taken with a grain of salt, but I wonder if BitBar plugins are still executed while the Mac is sleeping? (testing that now)

from xbar-plugins.

The first thing I noticed is that BitBar will refresh all plugins as soon as you wake your Mac from sleep. It doesn't matter how much time has passed since the last refresh, it will always do another refresh. Still, this is sort of expected behaviour, as I would be surprised if my computer woke up from sleep more than 20 times a day. I wonder though, if PowerNap or something else on the computer may be able to trigger a refresh as well. Any ideas?

from xbar-plugins.

Alright, I can confirm that BitBar appears to randomly refresh scripts that it is not "supposed" to. I have no idea why, but on this example the weather plugin is set to refresh every 15min. I added a log to see at which times my script would get called.

================ < initial plugin start 
2016-03-06 16:50:52.130957
================ < manual refresh (through BitBar) after 10 min
2016-03-06 17:00:57.696849
================ < another manual refresh after 5 min
2016-03-06 17:05:14.987406
================ < computer went to sleep - this refresh is from waking up again
2016-03-06 17:05:55.888563
================ < another manual refresh 5 min after waking up
2016-03-06 17:10:52.304677
================ < another sleep then wake test to see if BitBar refreshes again
2016-03-06 17:16:44.743760
================ < ARBITRARY refresh 3 min later
2016-03-06 17:19:22.612096
================ < another ARBITRARY refresh 3 min after that
2016-03-06 17:23:40.841455
================ < 1 min (ARBITRARY)
2016-03-06 17:24:21.550339
================ < 4 min (ARBITRARY)
2016-03-06 17:29:17.453129
================ < 2 min (ARBITRARY)
2016-03-06 17:31:52.078755
================ < 3 min (ARBITRARY)
2016-03-06 17:34:28.568005
================ < 4 min (ARBITRARY)
2016-03-06 17:38:44.807051
================ < 1 min (ARBITRARY)
2016-03-06 17:39:25.760066
================ < 5 min (ARBITRARY)
2016-03-06 17:44:21.348986
================ < 2 min (ARBITRARY)
2016-03-06 17:46:55.819093
================ < 3 min (ARBITRARY)
2016-03-06 17:49:32.878901
================ < computer woke up from sleep
2016-03-06 18:35:10.855741

from xbar-plugins.

I believe this is clearly a BitBar Bug: matryer/xbar#263

from xbar-plugins.