| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
- Most people leave the logs out so add a section for them in the issue template. - Remove the VS Code logs because those get sent to stdout now and will show up in our logs. - Separate browser console and network.
Codecov Report
@@ Coverage Diff @@
## main #3224 +/- ##
=======================================
Coverage 46.81% 46.81%
=======================================
Files 23 23
Lines 1194 1194
Branches 237 237
=======================================
Hits 559 559
Misses 451 451
Partials 184 184 Continue to review full report at Codecov.
|
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good, but I'm confused about the minor inconsistency with ~/.local/share/code-server/logs
Sorry, something went wrong.
| information from the following places: | ||
|
|
||
| 1. The most recent files from `~/.local/share/code-server/coder-logs`. | ||
| 2. The most recently created directory in the `~/.local/share/code-server/logs` directory. |
There was a problem hiding this comment.
Line removed here, but still present in the issue template;
Sorry, something went wrong.
| Once this is done, replicate the issue you're having then collect logging | ||
| information from the following places: | ||
|
|
||
| 1. The most recent files from ~/.local/share/code-server/coder-logs. |
There was a problem hiding this comment.
Line added here, but removed from the debugging FAQ;
Sorry, something went wrong.
|
Ah yeah it looks a bit confusing because we have the unfortunate names of logs and coder-logs. ~/.local/share/code-server/logs < was removed |
Sorry, something went wrong.
|
Oh lordy - I can't believe I missed the coder- in there! My bad. |
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good!
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
template.
show up in our logs.