Repository: mylar3/mylar3

Issue #1006: More Descriptive/Accurate Notifications
Created: 2022-01-23T08:29:44Z
Describe the request
A clear and concise description of what the request is.
Currently notifications are barebones and lack some key information, failing to convey partial failures of post-processing (file moved, but failed to convert, for example). More verbose discord messages that trigger on various conditions/states could be helpful for identifying these. This would be especially useful when identifying bad downloads, when a file failed to convert, it's likely because it was a bad file to begin with.
As a minor nit, it would also be more correct to state post-processing is completed without mentioning downloads due to manual post-processing, but this is a wording nit.
How did you come up with the idea?
Have you seen this request implemented somewhere else? An example or two might speed along development
I was observing the logs while simultaneously watching discord for notifications, and noticed a notification get sent (both in logs and discord, then conversion attempted and failed. The message I got via discord was about an issue being downloaded and post-processed correctly.
It made me wonder how many comics were marked as "post processed" that are actually bad files in my library. Having an alert about a potential error would be massively helpful.
Environment (please complete the following information):

OS: [e.g. Windows10] MacOS
Branch / commit: [e.g. Dev/38aksi1] Dev/07180d18e98e9c6160a1603798168b595b95b25e

Additional information
Add any other information about the request here.
Link to a log output showing this error in action can be found in the discord at https://discord.com/channels/826493118106697758/826498038885122149/933926471188230165

Duplicate issue #1007: Discord notification cards display incorrect date and time.
Created: 2022-01-23T11:28:54Z
Describe the bug
The new Discord notification cards added in 1003 do not display the proper system time.
CarePackage
Logs do not appear to yield anything useful, the lines related to the postprocessing are below:
23-Jan-2022 02:50:59 - INFO    :: mylar.foundsearch.1017 : ThreadPoolExecutor-0_0 : [POST-PROCESSING][UPDATER] Updating Status (Post-Processed) now completed for Daredevil/Punisher: Seventh Circle Infinite Comic issue: 1
23-Jan-2022 02:50:59 - INFO    :: mylar.search_results.354 : SEARCH-QUEUE : There are 0 results
23-Jan-2022 02:50:59 - DEBUG   :: mylar.Process_next.3010 : ThreadPoolExecutor-0_0 : [annchk:no] issue to update: #1
23-Jan-2022 02:50:59 - INFO    :: mylar.search.250 : SEARCH-QUEUE : resultset: []
23-Jan-2022 02:50:59 - DEBUG   :: mylar.search.258 : SEARCH-QUEUE : sleep...15s
23-Jan-2022 02:50:59 - DEBUG   :: mylar.Process_next.3017 : ThreadPoolExecutor-0_0 : writing: {'Status': 'Downloaded', 'Location': 'Daredevil-Punisher Seventh Circle Infinite Comic 01 (2016).cbz'} -- {'IssueID': '517966'}
23-Jan-2022 02:50:59 - INFO    :: mylar.notify.592 : ThreadPoolExecutor-0_0 : [POST-PROCESSING][NOTIFIER]Discord notifications sent.
23-Jan-2022 02:50:59 - INFO    :: mylar.Process_next.3150 : ThreadPoolExecutor-0_0 : [POST-PROCESSING] Post-Processing completed for: Daredevil/Punisher: Seventh Circle Infinite Comic #1
23-Jan-2022 02:50:59 - INFO    :: mylar.Process.1972 : ThreadPoolExecutor-0_0 : [POST-PROCESSING] Manual post-processing completed for 1 issues.

This screenshot of the notification for the same issue should show the issue more clearly:

Here you can see both the actual time the message was received (2:50 am), and the timestamp on the new notification card (yesterday at 6:50 pm).
Environment (please complete the following information):

OS: [e.g. Windows10] MacOS
Branch / commit: [e.g. Dev/38aksi1] Dev/07180d18e98e9c6160a1603798168b595b95b25e

Additional information
Add any other information about the problem here.
It is worth noting that my timezone is UTC-8. The likeliest culprit is that the notification is assuming my system time is UTC, and then adding my timezone conversion to generate a timestamp for the card, as that would lead to it thinking it happened 8 hours in the past.

Closing comment (2022-01-23T16:26:15Z): Similar to #1006 - @misleadingrhino given that was your PR, can you take a crack at addressing it please?