Both of these started some time after we upgraded ...
# general
d
Both of these started some time after we upgraded to python3, and before we upgraded to
1.20.0.dev1
(so... May? ish? I can probably nail that down a bit.)
a
this should be enough to go off of
could i ask you to do a huge favor and copy/paste the exact text of your slack messages into separate issues on github? if you don't have the bandwidth right now i will follow up later today
d
For sure 🙂
a
thanks!!!
w
@dry-analyst-73584: are you by any chance editing your plugin code?
editing your plugin code triggers a pantsd restart
d
In this case I am iterating on some totally unrelated tests.
I did see the same error while working on a new rule, but it doesn't seem to be specific to that.
a
when this happened inside twitter the user was not editing a pants plugin, just checking since we're not sure of the cause of this second issue yet
w
i mean, it will happen anytime the daemon restarts. including the log from the daemon is the relevant bit.
but yea, if you are editing plugin code, restarts are expected... making them more graceful would be good though.
d
Issues opened.
w
@dry-analyst-73584: are you able to include the
.pants.d/pantsd/pantsd.log
?
☝️ 1
that should explain a bit more about why the service went down
d
Sure 🙂
👍 1
a
thanks again!
d
np 🙂
My logs are full of "bad file descriptor" and I'm having trouble finding something relevant for the other error. Will add it when I find it.
w
That same exception message (service shutting down) should have been rendered in the log... so yea, if you see another, the nearby log is the relevant bit