FedML-AI/FedML

Web 3 Storage program is stuck

Open

#1,338 opened on Sep 14, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (743 forks)batch import
bughelp wanted

Repository metrics

Stars
 (3,930 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

i have confige ipfs token, number worker as 2 but when i run : bash run_server.sh 1 , bash run_client.sh 1 11 , bash run_client 2 22.

After server get connection from 2 client and it stuck at this log :

[FedML-Server @device-id-0] [Thu, 14 Sep 2023 19:35:22] [INFO] [mqtt_manager.py:93:send_message] FedMLDebug - Send: topic (fedml_1_0_2), message ({"msg_type": 6, "sender": 0, "receiver": 2, "client_idx": "859"}) [FedML-Server @device-id-0] [Thu, 14 Sep 2023 19:35:22] [INFO] [fedml_server_manager.py:107:handle_message_connection_ready] Connection ready for client2

at client side it stuck

[FedML-Client @device-id-1] [Thu, 14 Sep 2023 19:36:40] [INFO] [mqtt_manager.py:93:send_message] FedMLDebug - Send: topic (fedml_11_1), message ({"msg_type": 5, "sender": 1, "receiver": 0, "client_status": "ONLINE", "client_os": "Linux"})

Contributor guide

Research direction
Trace the MQTT message flow between server and clients. Check the server handler for message type 6 (msg type=6) and why it doesn't proceed after sending the connection ready message. Inspect the client's handling of message type 5 and check for missing responses or timeouts.
Tech stack
python
Domain
backenddistributed systems
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
PythonMQTT
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60