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
Additional context
A workaround i found was checking if DescribeGraphResponse.nodes and DescribeGraphResponse.nodes[0] were null. It feels like a patch over the root issue though, cause the last response i captured has only .nodes[0] populated.
Describe the bug
Most of the time, the
DescribeGraphResponse.nodes
response ends up being filled withnull
values instead of the proper node info.Environment (please complete the following information):
To Reproduce
Steps to reproduce the behavior:
Screenshots or Log Output
Additional context
A workaround i found was checking if
DescribeGraphResponse.nodes
andDescribeGraphResponse.nodes[0]
were null. It feels like a patch over the root issue though, cause the last response i captured has only.nodes[0]
populated.lncli
returned the graph just fine.The text was updated successfully, but these errors were encountered: