You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Views. Dendron Preview, Tree View, Side Panels in the UI
Schema. Dendron Schemas
Pod. Data import from / export to Dendron
Publish. External Site Publish
Markdown. Markdown features, such as syntax support and features
Describe the bug
Certain operations take on the order of 2-3 minutes when the system dendron is installed on does not have a network connection. Renaming a dendron note is just one example. It also happens when I try to create a new note.
If I disconnect from VPN and networking is reestablished with WSL then Dendron returns to behaving as expected.
To Reproduce
I use Dendron on WSL2/Ubuntu_20.04. It is well known that WSL2 looses network connectivity when the host Windows machine connects to a VPN. Once connected, certain operations take 2-3+ minutes for Dendron to execute. Renaming a note is just one example. There is a more fundemental issue at play here. If a network is not available... Dendron should not take 2-3+ minutes to timeout. Moreover, operations that are not network related (like renaming a file) should not be waiting on the network at all.
Expected behavior
File gets renamed/created immediately. These operations should not depend on the network.
Desktop (please complete the following information)
Please select the area your bug applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)
Describe the bug
Certain operations take on the order of 2-3 minutes when the system dendron is installed on does not have a network connection. Renaming a dendron note is just one example. It also happens when I try to create a new note.
If I disconnect from VPN and networking is reestablished with WSL then Dendron returns to behaving as expected.
To Reproduce
I use Dendron on WSL2/Ubuntu_20.04. It is well known that WSL2 looses network connectivity when the host Windows machine connects to a VPN. Once connected, certain operations take 2-3+ minutes for Dendron to execute. Renaming a note is just one example. There is a more fundemental issue at play here. If a network is not available... Dendron should not take 2-3+ minutes to timeout. Moreover, operations that are not network related (like renaming a file) should not be waiting on the network at all.
Expected behavior
File gets renamed/created immediately. These operations should not depend on the network.
Desktop (please complete the following information)
OS:
Windows 10, WSL2, Ubuntu_20.04
Versions (all that apply to bug):
v0.124.0
Dendron Log file
Please attach the output of
> Dendron:Dev: Open Logs
hereThe text was updated successfully, but these errors were encountered: