Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Bug] driver stderr does not get forwarded (DEBUG=pw:api does not work)
See original GitHub issueI used to do…
var playwright = await Playwright.CreateAsync(playwrightLogger, debug: "pw:api");
…however now that doesn’t work anymore, as far as I can tell.
I’ve tried setting the DEBUG env var to pw:api both for the user and the machine, but that didn’t seem to help. What am I doing wrong?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:5 (3 by maintainers)
Top Results From Across the Web
why stderr fails to be redirected using the 2>&1 instruction? ...
Solution: swap the order of the redirections. Reading left to right, you want to redirect stdout to test2. log , and then redirect...
Read more >How do I debug why stderr is being suppressed?
I want to debug this, but I have no idea how to start. How can I check where stderr is redirected to? Doing...
Read more >Redirect worker logs to the driver - Monitoring & Debugging
The stderr/stdout forwarded from the workers to my instance are jumbled together and difficult to parse. There is no easy way to know...
Read more >Redirecting error from Command Prompt - Visual C++
In order to redirect STDERR, you have to specify 2> for the redirection symbol. This selects the second output stream that is STDERR....
Read more >How to redirect standard (stderr) error in bash
I am trying to redirect bash message into file named output.log. But, it is not getting redirected. How do I redirect both standard...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I missed the fact that simply specifying DEBUG=pw:api environment variable does not log into stderr. We’ll fix this.
Hi @pavelfeldman, I believe so, yes. To provide a bit of context, I’m using Playwright via Specflow, and debugging Specflow is a fairly horrible experience since, short of putting breakpoints everywhere, most times the debugger will stop on the step from the BDD feature file rather than the line of code that actually threw the exception. Being able to inspect the verbose Playwright API logs again would be incredibly helpful.