-
Notifications
You must be signed in to change notification settings - Fork 91
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
[gsoc22] crash when there are nodes with the same id #164
Comments
@mwarning, I would like to work on this issue. |
@d1vyanshu-kumar feel free to fix it. But I do participate in the current GSOC in any way. |
@mwarning Thank you for your response. I appreciate the opportunity to work on this issue. I am looking for the file or section of code in the netjasongraph.js repository where the network data is stored. I believe this is typically an array of node objects, each with a unique ID. Could you assist me with this? As a beginner, I am a bit confused. If this Is the issue of |
@mwarning please look at line 16 and line 22 it has same id. |
hi @d1vyanshu-kumar, I do not know the netjsongraph.js code. I also no proficient JavaScript developer. I plan to use netjsongraph.js for MeshGraphViewer, but for now that is work in progress. During my tries to integrate netjsongraph.js into MeshGraphViewer, I stumbled over the error I reported above and thought that the netjsongraph.js developers do not want to it to crash even when two nodes entries have the same id. Your two links point to the data that triggers the error. :-) |
While having two nodes with the same id is probably not valid, netjsongraph.js should at least not crash.
This happens with MeshGraphViewer when the map is loaded and then updated with a node list that has two nodes of the same id. When I switch to the topology view, the crash happens.
The text was updated successfully, but these errors were encountered: