nbN
Convex Community•2y ago•
14 replies
nb

Hand-rolled python client getting blocked from connecting?

Hey folks, I wrote my own python client because I wanted realtime updates. This has been working for the past few months, but recently stopped working and unfortunately triggered an unfortunate reconnect loop in a spot where I missed adding backoff. Sorry about that!

I changed the version number for my connection from 0.3 -> 1.1, and that got it working again before I added the backoff (might have bypassed whatever block you folks put into place), but it stopped working again today.

Now, I've added the backoff, but it seems I may have been manually blocked. It appears the connection initially happens, but then is immediately closed w error 1005 (internal) from websockets, which apparently is the error that comes from the websocket library when a connection is closed w out data sent.

If you folks are manually blocking me, any chance I can get unblocked now that I've added exponential backoff (min 100ms, up to 10s per retry)?

  File "/Users/nick/code/py-code/server/nickconvex.py", line 151, in recv
    async for message in self.ws:
  File "/Users/nick/.local/share/virtualenvs/py-code-a850zYJQ/lib/python3.11/site-packages/websockets/legacy/protocol.py", line 497, in __aiter__
    yield await self.recv()
          ^^^^^^^^^^^^^^^^^
  File "/Users/nick/.local/share/virtualenvs/py-code-a850zYJQ/lib/python3.11/site-packages/websockets/legacy/protocol.py", line 568, in recv
    await self.ensure_open()
  File "/Users/nick/.local/share/virtualenvs/py-code-a850zYJQ/lib/python3.11/site-packages/websockets/legacy/protocol.py", line 944, in ensure_open
    raise self.connection_closed_exc()
websockets.exceptions.ConnectionClosedError: received 1005 (no status code [internal]); then sent 1005 (no status code [internal])
Was this page helpful?