You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Well, I know there is clearly ways to work around this, but it's not really safe in my opinion to print out the private key in the logs.
I know. I can change the logging level to something higher than info for the module, but I just don't think, in any cases, the key should be printed in any type of loggings (maybe debug)
Talking about debug. I don't think a query should be logged at the "info" level but the "debug" INFO:pyxivapi.client:200 from https://xivapi.com/search?language=en&private_key=
The text was updated successfully, but these errors were encountered:
Hello!
Well, I know there is clearly ways to work around this, but it's not really safe in my opinion to print out the private key in the logs.
I know. I can change the logging level to something higher than info for the module, but I just don't think, in any cases, the key should be printed in any type of loggings (maybe debug)
Talking about debug. I don't think a query should be logged at the "info" level but the "debug"
INFO:pyxivapi.client:200 from https://xivapi.com/search?language=en&private_key=
The text was updated successfully, but these errors were encountered: