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
Node 16485 corresponds to line 227. Node 1 I don't know, but I suspect it is thrown somewhere. Nodes 15052438 is line 225 whereas 15052299 and 15052441 are the result of a virtual dispatch on line 226. This looks good, until...
selectp.package_name, pv.version, pv.created_at, m.namespace, c.fasten_urifrom packages p
join package_versions pv onp.id=pv.package_idjoin modules m onpv.id=m.package_version_idjoin callables c onc.module_id=m.idwherec.id=15052299;
org.neo4j.neo4j-graph-algo | 3.3.0-alpha06 | 2017-08-1710:12:43 | /org.neo4j.graphalgo.impl.shortestpath/DijkstraPriorityQueueImpl | /org.neo4j.graphalgo.impl.shortestpath/DijkstraPriorityQueueImpl.insertValue(%2Forg.neo4j.graphdb%2FNode,%2Fjava.lang%2FObject)%2Fjava.lang%2FVoidType
The version of the function the callgraph points to is different (older).
I suspect this is because during upsert we only query the uniquness of a FASTEN URI that does not include a version number. So I 'd like to suggest that we change the uniqueness constraint to include the field module_id, which is already versioned.
The text was updated successfully, but these errors were encountered:
I think the uniqueness constraints for table
callables
is wrong. Let's takecallable 331721314 (current Java database) and see some info for it:
This corresponds to the following code: https://github.com/neo4j/neo4j/blob/3.5/community/graph-algo/src/main/java/org/neo4j/graphalgo/impl/shortestpath/Dijkstra.java#L223
Then, we take the edges:
Node 16485 corresponds to line 227. Node 1 I don't know, but I suspect it is thrown somewhere. Nodes 15052438 is line 225 whereas 15052299 and 15052441 are the result of a virtual dispatch on line 226. This looks good, until...
The version of the function the callgraph points to is different (older).
I suspect this is because during upsert we only query the uniquness of a FASTEN URI that does not include a version number. So I 'd like to suggest that we change the uniqueness constraint to include the field
module_id
, which is already versioned.The text was updated successfully, but these errors were encountered: