ShortestPath

?ShortestPath

As can be seen from the usage message above, ShortestPath calls BellmanFord under certain circumstances and therefore the error in BellmanFord affects ShortestPath as well. See the notebook on the BellmanFord bug for more details. Since we have fixed the bug in BellmanFord, ShortestPath also works fine.