Logging has stopped working
Arcanemagus opened this issue · comments
Prerequisites
- Put an X between the brackets on this line if you have done all of the following:
- Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
- Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
- Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
- Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
- Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages
Description
Diagnostic logging seems to have stopped working.
Steps to Reproduce
- Enable diagnostic logging by setting the following environment variables to file paths within a folder that exists on your system:
WATCHER_LOG_MAIN
WATCHER_LOG_WORKER
WATCHER_LOG_POLLING
- Start Atom in any file watching mode that uses
atom/watcher
- Note that only the initialization entry is logged, nothing further
Expected behavior:
Debug logs to be written to the file past the startup line.
Actual behavior:
Each file only contains the following:
[ ..\src\log.cpp: 53] FileLogger opened.
Reproduces how often:
100% of the time
Versions
OS: Windows 10 x64
Atom : 1.31.0-nightly9
Electron: 2.0.7
Chrome : 61.0.3163.100
Node : 8.9.3
apm 2.1.0
npm 6.2.0
node 8.9.3 x64
atom 1.31.0-nightly9
python 2.7.15
git 2.18.0.windows.1
visual studio 2015
Additional Information
I tried opening folders on a network share and local disk with the same result, including changing the working directory. Log files were set to:
$Env:WATCHER_LOG_MAIN="C:\temp\watcher_logs\main.log"
$Env:WATCHER_LOG_WORKER="C:\temp\watcher_logs\worker.log"
$Env:WATCHER_LOG_POLLING="C:\temp\watcher_logs\polling.log"