maia

I've encountered a similar error (not sending invitation mails usinge devise_invitable) and managed to trace it back to my self rolled unique jobs middleware, loosely based on Sidekiq 2.0.4 (before...

@baschtl I've compared the arguments and notices that it's caused by a different handling of ActiveJob and 'native' Sidekiq jobs: When calling a random ActiveJob which is using Sidekiq, this...

I'm also seeing the CPU issue on High Sierra 10.13.4, but in my case it's caused by a massive memory usage, and subsequently the CPU is busy writing RAM to...

In the past weeks I've been seeing the excessive memory (and cpu-load caused by swapping) on a daily basis. Three tabs are usually open all the time: Heroku Dashboard, Scoutapp...

I'm also seeing a rather sudden increase of memory with version 5.2, which is so high that the CPU then spends most of its time swapping ram to disk. Restarting...

I'm still seeing this on 10.13.4 on a daily basis. I saved a spindump and just sent it to the the email address you provided on your github user page,...

heroku-deflater has not been updated in the past two years – is it because it just works, or because people moved on to another solution? I assume heroku is hosting...

As a side note, I have two light sensors, once in a room facing north, one in a room facing west, directly next to the window. I have a template...

The issue still exists. For unavailable sensors a value of zero will be used to calculate the average: ``` - platform: average name: "Outdoor temperature" unique_id: "outdoor_temperature" entities: - sensor.terrasse_eve_weather_temperature...

4 months later, the issue unfortunately still exists. When averaging multiple sensors, any sensor that's unavailable will be used with 0 °C in the average calculation. @Limych is there anything...