Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Provisioning a node that was previously deleted.
See original GitHub issueHello, I am trying to figure out the networkExclusions object that gets populated after a node is removed. When I remove a node, I see that it’s address is added to the list. If I try to provision that same node again on the same network, I am unable to send messages to it to start the provisioning process.
How can I clear the networkExclusions list when I want to re-provision an unprovisioned/reset/deleted node? Is that even the right approach? I’ve combed over the example app and could not find any examples of things clearing up. What if I have just one node that I want to unprovision (the proxy node) and re-provision. Should I reset the entire network after that?
I see some things about updating the network IV, but I cant find any APIs/methods to do that.
Any advice would be appreciated. Thanks.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hello @Cplantijn . From my understanding you should not try to reuse the addresses that are in network exclusions. You should assign a new address, getting it via
nextAvailableUnicastAddressmethod (you will need to know the number of elements your node has)Thanks for the help, all! It was an issue with my app code. Once I removed the node I still had it marked for removal, so when it was added the second time it was instantly wiped out. Thanks for all the help!