Disable warnings not working properly?
Harm10 opened this issue · comments
I am using version 0.9.4 on RF 4.1.3.
I have weird behavior of disable_warnings=1.
I set this option on create session together with max_retries=5.
To check if I have a proper connection I execute a valid command on get on session.
If the connection is bad I get 5 warnings on console before the keyword fails.
I can suppress these warnings if I add disable_warnings=1 on get on session!
If the connection is OK I get an error:
TypeError: request() got an unexpected keyword argument 'disable_warnings'
Looking at the documentation disable_warnings is not allowed on get on session.
But I do not want those warnings displayed on console for a bad connection and can successfully suppress them by using this parm on get on session.
Following the documentation apparently the disable_warnings set on create session is not inherited for the get on session?
Is this a bug?
Can I please get some response on my report?
@lucagiove Can you please give me some reply on my issue report?
To be honest I don't like how it has been implemented the disable_warnings parameter.
I think I'll remove it in next versions, you could reduce the logging level on your own directly in robot without the needs of this parameter that does also other not straight forward things.
I totally missed your reply. I will experiment with log level of RF and report back.