WebSocket Connection Interrupted on LabGraph Monitor

[fzchriha]

🐛 Bug

WebSocket connection is interrupted when trying to display the real-time messages on Labgraph Monitor (frontend)

To Reproduce

Steps to reproduce the behavior:

1. python3 labgraph/examples/labgraph_monitor_example.py
2. cd extensions/prototypes/labgraph_monitor
3. yarn start
4. Click on RandomMessage Node
   Demo
   

Expected behavior

After a few seconds the real-time data freezes, check the terminal where the WebSocket is running it will display the following error:
- WS_SERVER_NODE: Raised an exception: RuntimeError("Task <Task pending name='Task-162949' coro=<WSAPIServerNode.ws_server_publisher() running at /Users/fatimazahra.chriha/Desktop/mlh/spring2022/labgraph/labgraph/websockets/ws_server/ws_api_node_server.py:125>> got Future <Future pending> attached to a different loop")

Environment

 - LabGraph Version:
 - OS: Mac
 - Python version: Python 3.8.13

[dtemir]

@fzchriha can you send a screenshot of the error you're getting? i'm trying understand the behavior from the gif, but it loops too fast I can't see what's written in the terminal

[fzchriha]

Hi @dtemir It's in the description above:
- WS_SERVER_NODE: Raised an exception: RuntimeError("Task <Task pending name='Task-162949' coro=<WSAPIServerNode.ws_server_publisher() running at /Users/fatimazahra.chriha/Desktop/mlh/spring2022/labgraph/labgraph/websockets/ws_server/ws_api_node_server.py:125>> got Future <Future pending> attached to a different loop")

Here is the screenshot of the terminal

[dtemir]

@fzchriha yeah I see! I was just wondering if there something useful in the Python traceback that shows what parts of the code the error breaks

[dtemir]

@fzchriha thank you! looking into that

[dtemir]

@fzchriha just to be sure, this has been resolved?

#63 (comment)

[fzchriha]

No it hasn't that comment was for realtime data sync with frontend

[bennaaym]

@fzchriha could you update PR #63 to use the last version of Labgraph Monitor and see if that solves the issue. I tried it and it looks like working fine

[fzchriha]

@bennaaym Hi Aymen I used the last version of labgraph monitor and for some reason when I try to connect using the latest changing @dtemir made (they work on my current PR) the status stays in IS CONNECTING and it never connects with the graph

[bennaaym]

@fzchriha, be sure that there is .env.local that has the following key: REACT_APP_WS_API="ws://127.0.0.1:9000"

[fzchriha]

I have it there, but it still does not work

[bennaaym]

could you send another screenshot of both the server console and the frontend?

[fzchriha]

Frontend

Backend

[bennaaym]

Could you try to restart the app, that's essential to pick up the changes in the .env variables

[fzchriha]

Yes it won't work :(

[dtemir]

hey guys, just commenting to see if you want this issue closed as it now works in #71 ?