lots of logging when resolving
See original GitHub issueWe are still noticing a lot of logging in ensime when using coursier. I’ll dig out some details of the exact strings later, but to see it yourelf just run sbt ensimeConfig
on ensime-server
itself and see a few pages of logging.
Also, the logs are really messing inside emacs. When the INSIDE_EMACS
environment variable is defined, the console should be assumed to be a dumb console.
Issue Analytics
- State:
- Created 7 years ago
- Comments:18 (6 by maintainers)
Top Results From Across the Web
Top 4 Logging Problems You Have Probably Faced and how ...
Logging Problem#4 – Data Normalization at Collection stage. A lot of log data is unstructured or maybe if you are lucky, is somewhat...
Read more >Log files and resolving upgrade errors - Windows Deployment
Several log files are created during each phase of the upgrade process. These log files are essential for troubleshooting upgrade problems.
Read more >How to know when there's too much logging messages?
How to know when is too much logging? When you know that the logged information isn't important in the long term, ...
Read more >Log Everything All the Time - High Scalability -
Instead, you need to log everything all the time so you can solve problems that have already happened across a potentially huge range...
Read more >Logging Best Practices: The 13 You Should Know - DataSet
When you search for things on the internet, sometimes you find treasures like this post on logging, e.g. creating meaningful logs.
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
actually I came here since we are trying to use coursier inside our CI. however the logging make’s our CI system also way slower. So it would be great to just have a way to say: Download Dependencies -> Done / Failure. Without the explicit dependencies in between. That would be really great.
Edit: at least the DI resolution is 100% faster than plain SBT which speeds up our build already but I guess without the whole logging it would be even faster.
I’ll see what I can do for the extra logging. Maybe lower the default verbosity level under some conditions.