Closed leoccyao closed 4 years ago
i think it depends on the logging level that is being set , change logging level to debug in order to get all the logging info .
I'm facing the same issue. As far as I can see, none of the log messages from API.py are logged.
Hmm. logger.warning(and greater: error/critical) are logged (but not in the specified Logger Format with debugLevel) to stdout, but no logger.info messages. Very Strange behavior.
@negswell as you can see in @leoccyao code example the line is logger.info
, so it has nothing to do with log level.
@ohld : Something is inconsistent in the code:
You think it is really necessary to have the logger name including the user_id/username? What about one Logger "[instabot]"?
Logging is fixed with PR #1205 so we could close this issue @ohld
Please follow the guide below
x
into all the boxes [ ] relevant to your issue (like so [x]).Before submitting an issue, make sure you have:
Purpose of your issue?
The following sections requests more details for particular types of issues, you can remove any section (the contents between the triple ---) not applicable to your issue.
For a bug report, you must include the Python version used, code that will reproduce the error, and the error log/traceback.
Paste the output of
python -V
here:Python 3.7.4 Running Instabot 0.73.0 in pipenv 2018.11.26
Code:
Error/Debug Log:
Describe your issue
The line "Checkpoint challenge required" was expected to print to console, but did not print.
This is an issue because: those receiving 400 errors when logging in and therefore "ds_user_id" errors (I received one upon failed login) may not realize that the error is due to a failure to log in.
Can confirm though that checkpoint solving functionality works perfectly (went through it with a successful login!)
Expected output: