orphan nodes about django-netjsongraph HOT 6 CLOSED

@acoul I can't load the graph. The size of your data is so huge that it's hard to debug.
The best approach when working on bugs is to isolate it. Do you have an idea of how to replicate the bug in a controlled environment?

PS: what happens if you isolate only that cluster of 2 nodes and the nodes/links they are connected to? Does the problem remain?

from django-netjsongraph.

I created a smaller subset of NetJSON nodes. The orphan issue does not appear in this smaller subset, but the issue on #58 remains.

can you perhaps test this smaller subset and see if you get similar behavior?

from django-netjsongraph.

Using that subset I don't see any orphan, regarding the issue in #58, that's a different matter, let's discuss it there so it's easier to track the discussion.

from django-netjsongraph.

Let me know if #62 resolves this too.

from django-netjsongraph.

I followed the patch update steps as explained in #58 and I deleted the orphan nodes from the admin panel. I then updated the db and now those nodes are totally missing at the graph, while appearing in the json file. Here is an example of such a node: "grep -w nios -B 2 -A 2 awmn.json"

  "source": "ncksm", 
  "cost": 1.0, 
  "target": "nios", 
  "cost_text": "", 
  "properties": {}

    "rawAs": "15716"
  }, 
  "id": "nios", 
  "label": "nios"
}, 
{

from django-netjsongraph.

Closed by #79

from django-netjsongraph.