Closed rizzini closed 1 year ago
Systemd service status(on the terminal, it crashes with no output whatsoever)
That's expected because, in this mode, all the output is directed towards the systemd's journal instead of the standard output.
This is a Pip installation, I guess?
I used to regularly upgrade Pip dependencies and also check them by debugging both modes of operation but I suppose that I forgot to debug the background mode during the last upgrade.
Watchdog authors removed one parameter about 10 months ago in this commit. Arch still uses a pretty old Watchdog's release branch in which that parameter still exists.
I've opened a relevant bug a long time ago but it's still unresolved.
Basically, this issue is caused by a library version mismatch between the AUR and Pip dependencies. I cannot amend the source code because that would break the AUR package, obviously. All that I can do is downgrade the Pip dependency but that's not currently possible because my Arch installation broke apart fairly recently and I still can't find the time to perform a fresh installation.
I could have downgraded it myself but, like I said, I forgot to debug it before pushing the new version to PyPI...
It's not a lot of work, perhaps you could give it a try?
I'm sorry for the late reply.
Sorry for the delay.. For some reason, my Google Chrome Github extension that handle notifications wasn't working.
It's not a lot of work, perhaps you could give it a try?
I'd love to, but this is something over my head, since I don't know python at all. I can handle some simple troubleshooting, but it stops there. Sorry, man.. I really wish I could help.
@rizzini
I somehow managed to downgrade the "watchdog" dependency on a Windows machine (what a pain). A new version has been pushed to PyPI. Try installing it and see if it fixed the issue.
Are you still having issues with your Linux system? That I can help. Anyway, I'm getting the same msg about positional arguments. Exactly the same. It almost seems I didn't update, but I did. I was suspicious of something going wrong in the first time, so I did it twice.
Are you still having issues with your Linux system?
Yep, still broken. I can't find the time for a fresh install.
My guess is that pip didn't downgrade the "watchdog" package after upgrading refind-btrfs. You could try running:
pip install --force-reinstall watchdog==2.1.6
or
pip install --upgrade watchdog==2.1.6
I checked the source code of that exact release and both parameters were present (I don't count "self" as a parameter).
My guess is that pip didn't downgrade the "watchdog" package after upgrading refind-btrfs. You could try running:
Oh yeah.. That was it! It's working now. Keep it up, man. 🤘
My guess is that pip didn't downgrade the "watchdog" package after upgrading refind-btrfs. You could try running:
Oh yeah.. That was it! It's working now. Keep it up, man. 🤘
Great, please close the issue if it's not too much to ask. 👍🏼
--run-mode one-time
works fine. I'm on Gentoo. I tested with Python 3.9 an 3.10.Edit: I guess I can schedule the "one time" some other way, but I'm trying to keep scheduled stuff organized with systemd. Anyway, that error is odd. Probably something on my environment.
Systemd service status(on the terminal, it crashes with no output whatsoever): Python 3.10:
3.9: