nulink-network / nulink-core Goto Github PK

When creating policy with a large shares, the system could not find enough worker nodes. Can add a backup route to provide stable nodes for selection. Could shift to the backup route when wait enough time(say 20 secs or more).

Describe the Bug
TypeError: argument of type 'NoneType' is not iterable

To Reproduce
nulink ursula run --config-file /home/ubuntu/nulink-1/ursula.json --rest-port 9151 --no-block-until-ready

Traceback or Screenshots (Optional)
OperatorBondedTracker: ✓ Operator 0xE9Dbe1B2D0207FB542C76a10c9686A67fb619F4c is bonded to staking provider 0xE9Dbe1B2D0207FB542C76a10c9686A67fb61
9F4c
_start_ursula
Restarting services
x [Operator 0xE9Dbe1B2D0207FB542C76a10c9686A67fb619F4c is no longer bonded to any staking provider] - Commencing auto-shutdown sequence...
OperatorNoLongerBonded
finally _shutdown_ursula
OperatorBondedTracker run exception: Traceback (most recent call last):
File "/home/ubuntu/.local/lib/python3.8/site-packages/nulink/network/trackers.py", line 74, in run
self._start_ursula(start_service=False)
File "/home/ubuntu/.local/lib/python3.8/site-packages/nulink/network/trackers.py", line 104, in _start_ursula
restart_run_arg_add('--start-service', str(start_service))
File "/home/ubuntu/.local/lib/python3.8/site-packages/nulink/network/trackers.py", line 92, in restart_run_arg_add
if option_str in self._restart_run_args and (origin_option_index := self._restart_run_args.index(option_str)) >= 0:
TypeError: argument of type 'NoneType' is not iterable

System (please complete the following information):

• OS Version: Ubuntu 20.04.3 LTS
• NULINK Version: 0.1.0
• Ethereum Node Version:

Hi, after I bond the worker address, I found the following output. Am I doing something wrong? what should I do?

Describe the Bug
The version check mechanism is missing when ping a node. This would cause uncompatible version would interrupt each other.

To Reproduce
When ping a node with an old version which is not compatible with the current version, it does not report any warning.

Suggestion to fix
Maybe it could add a version check mechanism while handshare or ping. And only those nodes with compatible versions could discover each other.

can you help me to see how the following error is caused? I'm already bound.

Some times it will return an error(says cFrag is not enough to decrypt data) when downloading the data. Need to fix this issue.

Describe the Bug
In current version, when bonding a worker node, it will only check if the node uri is online, and the current node uri has been used or not. But if the node uri is online and not been used before, it can be used for bonding neglect the real status of the worker nodes.

To Reproduce
If you can ping a false node with xxx:9151 URI, and use it to bond any fresh worker account to a fresh staker account. You will succeed. But this nodes is not runing at all.

Suggestion to fix it
Add a checking mechanism: when the backend server ping the node, the node need to return a signature which is signed by the worker account, the message is the node uri. Then when server check the signature, it can check if this worker is running with specific URI. This is one suggestion, maybe we can discuss it with other possibility to fix it.