Logs filled with spool_selected event every 5s
Opened this issue · 3 comments
Glad to see someone taking this project on. I'd been avoiding adding it to our farm since the activity died off on it. I'm testing it out again today on our test instance and noticed it's firing the spool_selected event every 5 seconds while the printer is idle.
I don't know if this is hangover from the upstream or new, but thought I'd share. It seems like the selected event should only fire once?
Hi @tideline3d, thank you for the report.
I'll try to first determine whether this is a long standing issue, or a regression introduced by my patches. It may take some time (probably next week) since I have other things to finish right now, so if you'll have more time than me, you could help me out by trying to check that out yourself.
However, I already did a quick check whether my test instance running in a Docker container exhibit this behavior. So far, except for repeated plugin_spoolmanager_spool_selected
event being sent on certain actions (eg. on singular spool selection, I've seen at least 3 events being sent immediately), I haven't observed any repeated behavior like yours.
I looked into this again when your note came through. I'll turn on some deeper logging and see if I can't correlate something else with the 5 second interval. I can repro the 3 immediate events on initial selection as well, you can tell see them all at the exact same timestamp here.
I have a fairly complex OP setup, so I'm going to guess this is another plugin triggering an event that SM is reacting to, based on your comments as to when it's sent. I'll dig deeper and let you know what I come up with. If it's only me seeing it, then I'll find a way around it.
Thanks for the sanity check on your side. I'll post here when I figure out what caused it.