Releases: RoguedBear/codezinger-due-date-scraper
v2.0.4 - (minor bug fix) improve snowflake id validation
This minor release fixes message id not being saved due to snowflake id being longer than was expected.
Improved its detection, so that hopefully shouldn't break in the future.
Full Changelog: v2.0.3...v2.0.4
v2.0.3: (bug fix) fix occassional chromium freezes causing 100% CPU usage
This release fixes the chromium freeze which caused 100% CPU usage unless you restarted the container. This used to be an issue till v2.0.2 but testing out the v2.0.3-rc release candidate for 25 days the CPU usage issue hasn't been popping up, so i it looks like #8 has fixed it
What's Changed
- cpu usage fix by @RoguedBear in #8
Full Changelog: v2.0.2...v2.0.3
v2.0.3-rc: reduce chromium CPU usage & potentially fix #6
- added
--disable-gpu
parameter for chromium which greatly reduces the max CPU usage I observed. from 30% to maximum 10% - potentially also fixes #6
v2.0.2: (bug fix) handle exception when another instance has already deleted an event
This bug fix release handles an exception which occurs when one instance tries to delete an event which has already been deleted by another instance
Full Changelog: v2.0.1...v2.0.2
v2.0.1: proper support for multiple containers with different accounts sharing the same database
What's Changed
- multiple instances run concurrently without sending duplicate event webhooks by @RoguedBear in #5
if you configure multiple containers running different accounts but sharing the same database (useful when both accounts overlap in some codezinger classes), this release then now prevents duplicates being sent by utilising locks
Full Changelog: v2.0.0...v2.0.1
(kinda) First release v2.0.0
first release, starting from v2.0.0
because previous fork is v1.0.0
and most likely dead.