lcurse
lcurse copied to clipboard
ephraim
Any way to get debug output?
Reinstalled my system (now debian10) and can't get it to work anymore ... probably a missing dependency. I have installed those mentioned in the readme and I also have nodejs but still ... Is there a way to get debugging info? The python back trace? Trigger a log? There was a log in 2016 but I haven't seen it for years now. @timwienk maybe?
I don't think I used any debugging flags/modes or log files. It does log some things to console, but not much. When something went seriously wrong, it does log (with trace) as expected and exit.
In case it helps, I have installed (on Debian 10) the following debian packages:
- python3
- python3-bs4
- python3-lxml
- python3-pip
- python3-pyqt5
And through pip3 (being the python3 pip, since Debian defaults to python2.7) I have cfscrape installed.
I have not run lcurse in a pipenv environment.
I have everything you mentioned except pip which I would like to avoid because of its developer dependencies. I had a look at them and installed python3-crypto/keyring/entrypoints but no change. lcurse runs without errors but doesn't do anything. There's something wrong with the web requests.
Everything worked fine until 2 weeks ago (Debian 9).
I don't see why it wouldn't work then, assuming you do have cfscrape (+ dependencies) installed [edit: for python3 of course] (which is what I used pip for).
cfscrape was introduced as a dependency recently to work around Curse/Twitch adding (more?) CloudFlare protection to the addon pages (see https://github.com/ephraim/lcurse/issues/81#issuecomment-538663338). That's the only real change regarding web requests, I think.
I believe this is only used in the OpenWithRetry in modules/waitdlg.py. Does that help?
I've managed to get debug output and opened this issue: https://github.com/ephraim/lcurse/issues/87