Commit 69a37cb <https://github.com/weewx/weewx/commit/69a37cb6cb46e09c60a930c92cfa09c897def807> changes it back to V3.x behavior.
-tk On Sat, May 9, 2020 at 2:08 PM Vince Skahan <[email protected]> wrote: > On Saturday, May 9, 2020 at 11:31:12 AM UTC-7, John Kline wrote: >> >> I can’t figure out why you care about this. It does reveal what was >> happening on the thread when WeeWX was shut down. While usually not >> interesting, sometimes it might be useful. >> >> > Because it is inherently confusing to see a stack trace in your syslog if > that is 'normal' behavior. Others have already reported the same thing and > show pretty clearly to me that this is confusing multiple people. > > I would agree that it's also useful sometimes. Just not always. > > Personally, I like the suggested patch if it works. If you dial up > debugging see more information. If you run typical debug=1 information > (ie, monitor normal operation) this one probably shouldn't be visible for a > normal stop/restart that folks do all the time. > > -- > You received this message because you are subscribed to the Google Groups > "weewx-development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-development/2b126fee-159c-450a-a22d-81f876103903%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-development/2b126fee-159c-450a-a22d-81f876103903%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/CAPq0zECXcYj1gzBsfbdfWYP%2BaURoSGNoATAV%3DLrtHdzetzvoow%40mail.gmail.com.
