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
I am currently creating an application which embeds proxy.py with a custom plugin.
Due to requiring custom flags within the custom plugin I am having to use the workaround detailed in #871 in order for them to parse correctly.
I have noticed that since implementing this workaround that I am no longer getting any logs/stdout from the proxy.
I do not see the message from logging.info in stdout. However, I do see the print. I have tried specifying a log-file which seems to parse correctly into p.flags but it does not get written to.
However, when I run the following I see the regular logging/stdout.
@klmunday Thanks for reporting, this needs little investigation. I don't think we have enough test coverage for custom plugin "flags", so this may have gone rogue. Give me some time, will look into it and #871
I am currently creating an application which embeds proxy.py with a custom plugin.
Due to requiring custom flags within the custom plugin I am having to use the workaround detailed in #871 in order for them to parse correctly.
I have noticed that since implementing this workaround that I am no longer getting any logs/stdout from the proxy.
Simplified version of my code below.
I do not see the message from
logging.info
in stdout. However, I do see the print. I have tried specifying a log-file which seems to parse correctly into p.flags but it does not get written to.However, when I run the following I see the regular logging/stdout.
This however breaks the parsing of the custom plugins flags (as detailed in #871) so this is not a solution.
I have also tried using
proxy.main
instead, then specifying my args via command line but that has not worked.The text was updated successfully, but these errors were encountered: