-
Notifications
You must be signed in to change notification settings - Fork 3
Delete node causes error #235
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
Comments
Good catch! Fixing now. |
Sorry for the typo in the name.
…----
(from my iPhone)
Joshua Danish
http://www.joshuadanish.com
On Mar 30, 2022, at 8:00 PM, benloh ***@***.***> wrote:
Good catch! Fixing now.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.
|
@jdanish I believe 93bc853 should fix this. Just pushed. Should be fixed in #217 This was a side effect of our separating the core "raw" data from the "working" filtered data that was necessary to get import/export working. We ended up with a few straggling references to the deprecated data format. I think all the old references are now chased down as well. |
Looks good thanks! |
benloh
pushed a commit
that referenced
this issue
Sep 5, 2024
hotfix-for-234: use POSIX dot command for Digital Ocean compatibility.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To reproduce, open a network, select a node, click delete (happens with and without merging). There appears to be no change. Check the console and see the error below. Reload and change becomes visible. Note that other viewers don't see a change unless they reload as well.
The text was updated successfully, but these errors were encountered: