• Kirill Miazine [2025-10-25 00:22]:
• Kirill Miazine [2025-10-24 16:44]:
I have another edge case, and no idea what could be causing it.
In my Pyng setup, I run quite a few commands, and today I discovered
that one particular configuration just ... disappears.
The command executes once, exits, results are processed and command
is scheduled for re-execution later. But then it just ... hangs. Here
is some output which hopefully shows what happens (and I have no idea
why...)
<output>
will run a1ece83c0a
ran a1ece83c0a
exited!
ended!
got results for a1ece83c0a
will run a1ece83c0a
ran a1ece83c0a
exited!
</output>
I guess this might be something very system-specific... I don't know.
If I change the URL, the problem is gone. If I ask a separate runner
to do the check, it works. If I try the code on different OS, it works.
I would still like to have ideas, though, as could be doing something
in not very Twisted way
I just cleared monitoring state, and here we are with two results for
HTTP checks, which run curl in spawnProcess:
https://uptime.is/mon/check/a1ece83c0a
https://uptime.is/mon/check/b30d2d2106
But TREQ is doing very well: https://uptime.is/mon/check/23854fc527
_______________________________________________
Twisted mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/twisted.python.org/
Message archived at
https://mail.python.org/archives/list/[email protected]/message/EWLUZ6YEI6MTSBZKCPECFH677X6GCRGS/
Code of Conduct: https://twisted.org/conduct
