Can't Connect to Peers + Broken Discord Invite

[ShrektacularSwamp]

I have everything set up correctly, it just won't add peers or sync / connect to the network. I have my port properly forwarded.

The discord links everywhere are broken, and there's no twitter activity.

Is this just a dead fork?

[WarutaShinken]

Check your logs, are you getting an entry that reads TypeError: object of type 'NoneType' has no len()? This issue has recently been reported by other users and I have attempted to fix this under the null_waiters_quickfix branch. If you are installing STAI from source, could you try reinstalling it from this branch?

[WarutaShinken]

As for the Discord server invite being broken, I will have to contact a server admin in charge of it to fix that. Here's an alternative invite for now: https://discord.gg/vgf6XUFYnr

[Yamanipanuchi]

I installed the branch and ended up with the same error unfortunately.

[WarutaShinken]

Are you sure it installed that branch? Please run git rev-parse --abbrev-ref HEAD in stai-blockchain and make sure it prints null_waiters_quickfix. If the error message still shows that the error is happening at line 112 of full_node_api.py, it means the branch hasn't been checked out:

Traceback (most recent call last):
  File "/.../stai-blockchain/stai/server/server.py", line 605, in wrapped_coroutine
    result = await coroutine
  File "/.../stai-blockchain/stai/full_node/full_node_api.py", line 112, in new_peak
    waiter_count = len(self.full_node.new_peak_sem._waiters)
TypeError: object of type 'NoneType' has no len()

[Yamanipanuchi]

[Yamanipanuchi]

This is what I am getting. I just capture my own node trying to connect to my secondary node.

[WarutaShinken]

Hmm, that's a pretty useless log entry, it doesn't even tell us the line it happened at.

Anyway, so I made some pushes to main that include a more thorough version of null_waiters_quickfix (there's another part of the code that's vulnerable to this issue, and I suspect that's why my quickfix didn't work for everyone). Could you pull it and:

• Delete cache and run under mainnet.
• Test it with your current copy of the database.
• If the above doesn't work, test without an existing database.

EDIT: STAI 1.3.1 is out now, which features the relevant bugfix.