adam/Remote-Terminal-for-MeshCore
1
0 Fork 0
mirror of https://github.com/jkingsman/Remote-Terminal-for-MeshCore.git synced 2026-11-03 08:02:19 +01:00
Code Issues 26 Packages Projects Releases Wiki Activity

Trace timeout causes multiple retries #251

New Issue
Open
opened 2026-10-05 02:06:01 +02:00 by adam · 1 comment
adam commented 2026-10-05 02:06:01 +02:00
Owner
Copy link
Copy source

When a trace fails, the timeout raises a 408 which causes the trace to be re-tried over and over, with no way to cancel.
https://github.com/jkingsman/Remote-Terminal-for-MeshCore/blame/33b3b8d0236f2aebe045d2fc00b256a06f672e1e/app/routers/radio.py#L682

Returning a 422 (#237) causes the trace timeout to correctly be reported as a failure.

When a trace fails, the timeout raises a 408 which causes the trace to be re-tried over and over, with no way to cancel. https://github.com/jkingsman/Remote-Terminal-for-MeshCore/blame/33b3b8d0236f2aebe045d2fc00b256a06f672e1e/app/routers/radio.py#L682 Returning a 422 (#237) causes the trace timeout to correctly be reported as a failure. <!-- github-sync-id:4994691154 -->
adam commented 2026-10-05 02:06:02 +02:00
Author
Owner
Copy link
Copy source

When a trace fails, the timeout raises a 408 which causes the trace to be re-tried over and over, with no way to cancel. https://github.com/jkingsman/Remote-Terminal-for-MeshCore/blame/33b3b8d0236f2aebe045d2fc00b256a06f672e1e/app/routers/radio.py#L682

Returning a 422 (#237) causes the trace timeout to correctly be reported as a failure.

I just saw the same behavior when requesting a RPT telemetry with flood and without the guest login confirmation.
A seeing the request endless retries flooding the network thru the region observers.

Image Image
> When a trace fails, the timeout raises a 408 which causes the trace to be re-tried over and over, with no way to cancel. https://github.com/jkingsman/Remote-Terminal-for-MeshCore/blame/33b3b8d0236f2aebe045d2fc00b256a06f672e1e/app/routers/radio.py#L682 > > Returning a 422 ([#237](https://github.com/jkingsman/Remote-Terminal-for-MeshCore/pull/237)) causes the trace timeout to correctly be reported as a failure. I just saw the same behavior when requesting a RPT telemetry with flood and without the guest login confirmation. A seeing the request endless retries flooding the network thru the region observers. <img width="1226" height="236" alt="Image" src="https://github.com/user-attachments/assets/a000f8f3-d4ad-48ee-ad29-50461692eab3" /> <img width="1231" height="208" alt="Image" src="https://github.com/user-attachments/assets/86cac5a5-20e9-4cfa-b0a4-3abc8a4b1227" /> <!-- github-comment-id:5122935911 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#251