Logger doesn't work anymore
See original GitHub issueFrom the graphql-language-service-server
package (at least, could be shared further).
It used to work before the TS rewrite but now logger emits nothing when connected to say VSCode extension now.
process.stderr.write
seems to work though.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:16 (12 by maintainers)
Top Results From Across the Web
logging - Python Logger not working - Stack Overflow
The problem is that the logger's level is still set to the default. So the logger discards the message before it even gets...
Read more >Logger doesn't seem to work with errors #46 - GitHub
I'm not sure if this is a new thing because I thought it worked before, but it seems whenever I try and log/warn/error...
Read more >Python Logging: A Stroll Through the Source Code
In this step-by-step tutorial, you'll learn about how the Python logging package is designed from an OOP perspective. You'll walk line by line...
Read more >Logging Problems in IBM WebSphere Application Server
Log4J log /trace is not routed to WebSphere Application Server log/trace files, and Log4J loggers don't show up in the WebSphere Application ...
Read more >No logging anymore in Service Center - OutSystems
No logging anymore in Service Center ... since a few weeks we don't have any logging within service center. ... Also daily history...
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 FreeTop 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
Top GitHub Comments
@divyenduz and I had a session and tried to track down what changed in graphql-languagesrver and client from 3.5.1. My guess is that the language server no longer writes to
stderr
as it did before, and somewhere invscode-jsonrpc
this changed over major versions. we decided manually writing tostderr
in theLogger._log()
will fix it for now, but it would be great to know why this regression occurredThis one seems to work because in
graphql-language-service-*
it is aprocess.stderr.write
In 10-20 minutes maybe?