TX does not send message after notification #28

Closed
opened 2026-02-25 18:42:29 +00:00 by sebgab · 2 comments
Owner

A notification is sent to the TX handler, but it never responds with sending the data.

 INFO  elevator::system_state_controller::setup_state > Elevator IP: 10.100.23.24
 DEBUG elevator::system_state_controller::setup_state > Creating channels
 DEBUG elevator::system_state_controller::setup_state > Creating state
 DEBUG neli::router::synchronous                      > Processing thread signaled to exit; exiting
 INFO  elevator                                       > Elevator started:
Elevator {
    socket: Mutex {
        data: TcpStream {
            addr: 127.0.0.1:60044,
            peer: 127.0.0.1:15657,
            fd: 11,
        },
        poisoned: false,
        ..
    },
    num_floors: 4,
}
 INFO  elevator                                       > Spawning tasks
 INFO  elevator                                       > Sucessfully initialized elevator
 INFO  elevator::network::tx_handler                  > Starting TX handler
 TRACE elevator::system_state_controller::obstruction_handler > Recieved form the obstruction. Obstruction: true
 DEBUG elevator::system_state_controller                      > Sent notification to TX ()
 INFO  elevator::system_state_controller::obstruction_handler > System is obstructed. Updated the system state. Obstructed: true.
 DEBUG elevator::network::tx_handler                          > Waiting on notification
 TRACE elevator::network::tx_handler                          > Reading system state
 TRACE elevator::network::tx_handler                          > Serializing data
 TRACE elevator::network::tx_handler                          > Sending 38 bytes of data
 DEBUG elevator::network::tx_handler                          > Transmitted 38 sucessfully
 DEBUG elevator::network::tx_handler                          > Waiting on notification
 TRACE elevator::system_state_controller::obstruction_handler > Recieved form the obstruction. Obstruction: false
 DEBUG elevator::system_state_controller                      > Sent notification to TX ()
 INFO  elevator::system_state_controller::obstruction_handler > INFO:System is not obstructed. Updated the system state. Obstructed: false.
 TRACE elevator::system_state_controller::obstruction_handler > Recieved form the obstruction. Obstruction: true
 DEBUG elevator::system_state_controller                      > Sent notification to TX ()
 INFO  elevator::system_state_controller::obstruction_handler > System is obstructed. Updated the system state. Obstructed: true.

Reopens #1 #3

A notification is sent to the TX handler, but it never responds with sending the data. ``` INFO elevator::system_state_controller::setup_state > Elevator IP: 10.100.23.24 DEBUG elevator::system_state_controller::setup_state > Creating channels DEBUG elevator::system_state_controller::setup_state > Creating state DEBUG neli::router::synchronous > Processing thread signaled to exit; exiting INFO elevator > Elevator started: Elevator { socket: Mutex { data: TcpStream { addr: 127.0.0.1:60044, peer: 127.0.0.1:15657, fd: 11, }, poisoned: false, .. }, num_floors: 4, } INFO elevator > Spawning tasks INFO elevator > Sucessfully initialized elevator INFO elevator::network::tx_handler > Starting TX handler TRACE elevator::system_state_controller::obstruction_handler > Recieved form the obstruction. Obstruction: true DEBUG elevator::system_state_controller > Sent notification to TX () INFO elevator::system_state_controller::obstruction_handler > System is obstructed. Updated the system state. Obstructed: true. DEBUG elevator::network::tx_handler > Waiting on notification TRACE elevator::network::tx_handler > Reading system state TRACE elevator::network::tx_handler > Serializing data TRACE elevator::network::tx_handler > Sending 38 bytes of data DEBUG elevator::network::tx_handler > Transmitted 38 sucessfully DEBUG elevator::network::tx_handler > Waiting on notification TRACE elevator::system_state_controller::obstruction_handler > Recieved form the obstruction. Obstruction: false DEBUG elevator::system_state_controller > Sent notification to TX () INFO elevator::system_state_controller::obstruction_handler > INFO:System is not obstructed. Updated the system state. Obstructed: false. TRACE elevator::system_state_controller::obstruction_handler > Recieved form the obstruction. Obstruction: true DEBUG elevator::system_state_controller > Sent notification to TX () INFO elevator::system_state_controller::obstruction_handler > System is obstructed. Updated the system state. Obstructed: true. ``` Reopens #1 #3
sebgab self-assigned this 2026-02-25 18:42:29 +00:00
sebgab added this to the Networking project 2026-02-25 18:42:29 +00:00
Author
Owner

Is the obstruction handler or door handler task not properly sharing the mutex?

Is the obstruction handler or door handler task not properly sharing the mutex?
Author
Owner

Closed by #32

Closed by #32
sebgab changed title from TX does send message after notification to TX does not send message after notification 2026-03-08 12:13:15 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
TTK4145/elevator#28
No description provided.