Isitha Subasinghe

@HumairAK will continue on this when I get the chance

@terrytangyuan and @agilgur5 I know exactly what is going on here, it is speculative execution on the DAG section of the code. It most likely is looking for the boundaryNode...

> So if the node was not initialized yet, then there shouldn't be a call to Nodes.Get at all. The previous code already did that though, meaning the previous code...

I suspect this arises from the dag as mentioned previously, I am now going to find out why we can ignore the error and I will document this. If we...

I don't really know how to fix this without rewriting the dag.go logic, the core problem is that the dag logic is entirely speculative, this means that it is impossible...

@drawlerr the DAG code will always produce this logging unfortunately

@agilgur5 The dependency isn't really installed in Nix via a `npm install -g` equivalent, so `npm list -g` will fail (I tested this out), so the Makefile will have to...

> > @agilgur5 The dependency isn't really installed in Nix via a `npm install -g` equivalent, so `npm list -g` will fail (I tested this out) > > Thanks for...

@juliev0 I am comfortable merging this, but I don't have write access yet I think?

Yeah I have the same problem unfortunately, just posting here for more attention on this issue