Same configuration in debug and run mode acts differently
Answered
Running integration tests in `Debug` mode causes error where same configuration in 'Run' mode executes correct. Test fails on the step of making request to local NAT server (with help of https://github.com/nats-io/nats.py).
Any thoughts about reasons? I see logs in NAT with incoming msgs, but in the middle of request NAT response with error msg.
What does differ 'Debug' mode from 'Run'?
Please sign in to leave a comment.
The only difference between Run and Debug is that debugger is using helpers to establish the connection and interact with runtime.
Do you have any modules that shadow standard packages (like string.py, socket.py, etc)?
Would it be possible to share the whole Traceback?
Sergey Karpov, thanks for your response! I can't say for sure about modules which could shadow some standard packages - there're a lot of stuff, that why I create a ticket to have a clue what to search.
I see such error in logs:
`ValueError: <Token var=<ContextVar name='token_name'> was created in a different Context.`
Could debug mode afflict ContextVar anyhow?