https://www.dendron.so/ logo
Join Discord
Powered by
Any ideas why Dendron isn't initializing properly?
# questions
p
Any ideas why Dendron isn't initializing properly?
Copy code
info: {"ctx":"WSUtils.handleServerProcess","msg":"subprocess running","pid":31032}
info: {"ctx":"startServerProcess","msg":"post-start-server","port":22755,"durationStartServer":1039}
info: {"ctx":"dendron.reloadIndex:run","msg":"pre-execute"}
info: {"ctx":"ReloadIndex.execute","msg":"enter"}
info: {"ctx":"ReloadIndex.execute","durationEngineInit":200}
info: {"ctx":"ReloadIndex.execute","msg":"exit"}
info: {"ctx":"dendron.reloadIndex:run","msg":"post-execute"}
info: {"ctx":"reloadWorkspace","msg":"post-ws.reloadWorkspace"}
info: {"ctx":"reloadWorkspace","msg":"exit"}
info: {"ctx":"postReloadWorkspace","msg":"same wsVersion"}
info: {"ctx":"postReloadWorkspace","msg":"exit"}
debug: {"ctx":"TreeView:getChildren"}
info: {"ctx":"TreeView:getChildren","msg":"reconstructing tree: enter"}
info: {"ctx":"setupViews","msg":"init:treeViewV2"}
info: {"ctx":"setupBacklinkTreeView","msg":"init:backlinks"}
info: {"ctx":"TreeView:getChildren","msg":"reconstructing tree: exit"}
info: {"ctx":"activateWorkspace","stage":"prod","msg":"enter"}
info: {"ctx":"togglePluginActiveContext","state":"togglePluginActiveContext: true"}
info: {"ctx":"_activate","msg":"fin startClient","durationReloadWorkspace":1250}
error: {"line":1,"column":0}
error: {"ctx":"showInitProgress","msg":"issue initializing Dendron"}
info: {"ctx":"updateDecorations","payload":{"error":null,"decorationsLength":2,"diagnosticsLength":0}}
debug: {"msg":"Note opened","fname":"kubernetes.pods.md.git"}
debug: {"msg":"Note opened","fname":"settings.json"}
@User any thoughts?
s
Hmmm is this when initializing a new workspace, or when opening an existing workspace where the extension is loading up?
p
Opening an existing workspace
k
tried cloning in the workspace but it didn't seem to have all the notes that you had in your logs
the problem might be from 
kubernetes.pods.md.git
- dendron currently has an issue parsing 
.md
(this will be fixed in next weeks release)
p
Oh I forgot to commit the pending changes
I pushed the pending changes, so you can see that file. I probably created the file manually, rather than using the "correct" method of doing a Dendron lookup. Is there some kind of linting or "health check" command I can run to ensure the files in my "vault" are using the correct syntax? @User
k
dendron should warn you about badly formatted files, the 
.md
was an edge case that @User fixed and will be landing next week. i'm able to load the workspace now - has this solved your problem?
s
As an added note about other markdown files in general, outside of the 
*.md.*
edgecase: - 
Dendron: Doctor
commands can be helpful if having plain markdown files in your vault that need front matter taken care of, with commands such as `fixFrontmatter`: https://wiki.dendron.so/notes/ZeC74FYVECsf9bpyngVMU/#fixfrontmatter - If you have many markdown files you'd like to import into your vault, you can also follow the Markdown Import Pod directions: https://wiki.dendron.so/notes/f23a6290-2dec-45dc-b616-c218ee53db6b/
p
Nope, I'm still seeing that obscure error.
I tried deleting the 
.dendron.cache.json
, and reloading, but that didn't change anything either.
I just disabled a bunch of extensions, and still doing the same thing
s
I'll test out your repo in about 20min, see if I can notice anything weird
Looks like Dendron might be tripping up on 
Cloud Storage.md
. Try: - Rename 
Cloud Storage.md
to 
cloud-storage.md
- Delete 
.dendron.cache.json
- Reload Window (Command Pallet -> 
Developer: Reload Window
)
At least, for some reason, that seemed to fix the problem for me with the reload index failures that kept coming up
p
The same error occurs when I launch VSCode even without opening a workspace @User
s
I can't seem to replicate the error. Questions: - You said you tried disabling other extensions. If Dendron is disabled, and you Reload Window, does it still appear? - If it doesn't appear, does it start appearing once Dendron is enabled again, after a Reload Window (by itself as the only extension)? - If so: what is the VSCode version you are running, and what OS?
p
Copy code
info: {"ctx":"Logger:configure","msg":"exit","logLevel":"info"}
info: {"ctx":"_activate","stage":"prod","isDebug":false,"logLevel":"info","logPath":"c:\\Users\\TrevorSullivan\\scoop\\apps\\vscode\\1.64.2\\data\\user-data\\logs\\20220215T124139\\exthost4\\dendron.dendron","extensionPath":"c:\\Users\\TrevorSullivan\\scoop\\apps\\vscode\\1.64.2\\data\\extensions\\dendron.dendron-0.82.0","extensionUri":"c:\\Users\\TrevorSullivan\\scoop\\apps\\vscode\\1.64.2\\data\\extensions\\dendron.dendron-0.82.0"}
info: {"ctx":"DendronExtension","msg":"initialized"}
info: {"ctx":"_activate","msg":"initializeWorkspace","wsType":"NONE","currentVersion":"0.82.0","previousWorkspaceVersion":"0.0.0","previousGlobalVersion":"0.80.2","extensionInstallStatus":"UPGRADED"}
info: {"ctx":"_activate","msg":"dendron not active"}
error: {"line":1,"column":0}
Error disappears when Dendron extension is disabled. @User Just tested now.
s
Ah, yeah, definite Dendron error output
p
As soon as I re-enabled the extension (without reloading) the error appears.
No workspace opened
Let me uninstall it and see if it resets anything
s
Yeah, I was about to ask about reinstalling the extension, since it seems to be trying to throw an upgraded message
p
Nope, as soon as I install it, same error
s
Looks like you're on Windows with latest VS Code, I'll pop open a VM to see if I can get it
I've just tried on a VM, and am unable to replicate your error :\ (I tested via scoop install and also a manual install, with current release of VS Code) - You get the same log output when opening a directory that isn't related to Dendron? - And when reinstalling it, is it still attempting to throw upgrade information?
And to add to those questions: - If other extensions are enabled/active, but not Dendron, is the error also not appearing?
Side note: I asked another Windows user who had difficulty getting up and running initially, and for whatever reason, uninstalling and reinstalling VS Code entirely fixed his problems.
p
Correct, I re-enabled a bunch of extensions, and disabled Dendron. C#, Gitpod, Jupyter, AWS Toolkit, Code Runner, Kubernetes, Python. The error does not appear when Dendron is disabled.
I don't even need to open a directory. Dendron just throws the error message in an empty VSCode window.
s
The only thing I can think of as a last check is to have VS Code Insiders or VSCodium installed alongside your current VS Code setup, and then configure the new app with only Dendron. This would isolate configs in a way that would show whether there is any difference (because that error output looks like a config error, like a JSON config problem).
If Dendron is in a fresh install, working, would help in pointing out something weird in configurations somewhere. Have you always been getting the error, since you installed Dendron itself?
Could be an error somewhere in 
keybindings.json
, maybe?
p
I don't have VSCode Insiders or VSCodium installed on my system.
Oh, but you're suggesting trying it out. I see 🙂
I didn't get it initially when I first learned about and installed the Dendron extension. The extension used to initialize properly, when I first installed it and created a vault. I took a look at my VSCode key bindings, and don't see any problems with it. In fact, the file is empty. 🙂
I just wiped out my VSCode Settings JSON file and reloaded the window. The error from the Dendron extension changed very slightly. See screenshot.
k
what happens when you add 
{}
to your keybindings file?
p
@User same behavior
Is there any way to enable debug logging on the extension to see where the error is occurring? @User
k
p
That didn't provide any additional detail beyond the logs I already sent.
Should I file a bug for this?
k
yes please. apologies, haven’t had much time to look into this this week so will set aside some time tomorrow. in the ticket, can you paste the output of diagnostics report?
hey @User , instead of 
{}
can you add 
[]
to your 
keybindings.json
?
p
Sure I'll try
Same problem
Want to hop in the General voice chat @User ?
k
lets do it
for bystanders - this issue is fixed in the latest 0.83 version of dendron that will be coming out later today
4 Views
PreviousNext
Powered by