New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Foam Graph is blank #499
Comments
Not on M1, but graph is also blank.
VS Code
Foam 0.10.2 |
Same issue here on Windows 10 64bit, was working a couple days ago. Version: 1.53.0 (user setup) |
Also just updated to vscode 1.53.2, same issue. |
Can you see if anything shows up in the Foam log? https://github.com/foambubble/foam/blob/master/docs/features/foam-logging-in-vscode.md |
|
@ValentinTrinque |
I'm not getting anything in the Foam logs when the Graph is blank. If I reload the window and then try to view the graph then it becomes visible. BUT if I delete a link/node, then the graph isn't refreshing and I'm seeing the below logs:
Link to Repo: https://github.com/iamtherealgd/BrainTemp |
I found the issue, it was related to how wikilinks were being resolved when in presence of a definition. |
* improved resolution for direct links and wikilink with definition * if the definition of a wikilink points to a non-existing file, create a placeholder for the full path instead * if a link doesn't point to a valid resource, create a placeholder for the full path instead * commented out test-data.js import in dataviz.html * moved test to more appropriate group
this has now been fixed as of 0.10.3 - can you confirm? |
Confirmed - thank you |
Unfortunately the foam graph intermittently stops updating again, and when I close it and re-open, it is blank. I just upgraded to the latest version of Big Sur. (But it was working sometimes after the upgrade) |
Looks like I can repro:
|
Open Foam Graph
opens the panel, but it is blank. My best guess is this is because I am on the VSCode for Insiders build in order to get native M1 Apple Silicon support. (Foam Graph worked fine on previous Intel laptop using standard VSCode)The text was updated successfully, but these errors were encountered: