Troubleshooting Missing VeighNa Logs in VS Code

Summary

This community thread discusses missing log output when running VeighNa version 4.10 in a VS Code environment, while version 3.94 reportedly logs normally in the example setup. Participants suggest checking whether the launch directory changed and whether the relevant configuration file in the new working directory is empty. One user reports that lowering the configured log level restored output; another found that commenting out a logger removal call brought output back, but also caused other issues.

The thread does not establish a single confirmed cause or a definitive fix. One participant reports that the log file was created but remained empty, and planned to return to the earlier release while awaiting an update. The different observations suggest that startup paths, logging configuration, and logger setup can all affect the result. This is informal troubleshooting rather than a verified bug report, and the proposed workarounds may have side effects; the discussion provides no reproduction steps or confirmed resolution for every case.

Key ideas

• The thread reports missing log output in VeighNa 4.10 under VS Code while an earlier release worked in the cited setup.
• A changed launch directory may cause the application to read a different configuration file.
• One user reports that reducing the configured log level restored output.
• Commenting out a logger removal call reportedly restored output but introduced other issues.
• The discussion does not confirm one root cause or a universal fix.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.