Missing cancellation/abort mechanism in protocol #101

Closed
opened 2026-07-21 16:20:04 +02:00 by TapTap · 1 comment
Owner

Description

If the client needs to abort mid-transfer, there is no way to tell the server. The client just disconnects, leaving the server to potentially hang on a read or write.

Location

src/shared/protocol.h (NEED STATUS enum)
src/shared/protocol.c
src/server/server.c

Suggested Fix

Add STATUS_CANCEL message. Client sends it before disconnecting. Server receives it and aborts the transfer gracefully (closes files, sends STATUS_OK, exits).

Severity

high

Category

feature

Sub-Agent

feature-scout (FS-7)


This issue was automatically generated by the issue-creator agent.

## Description If the client needs to abort mid-transfer, there is no way to tell the server. The client just disconnects, leaving the server to potentially hang on a read or write. ## Location src/shared/protocol.h (NEED STATUS enum) src/shared/protocol.c src/server/server.c ## Suggested Fix Add `STATUS_CANCEL` message. Client sends it before disconnecting. Server receives it and aborts the transfer gracefully (closes files, sends STATUS_OK, exits). ## Severity high ## Category feature ## Sub-Agent feature-scout (FS-7) --- _This issue was automatically generated by the issue-creator agent._
Author
Owner

Fixed in PR #148 — merged into main on 2026-07-29.

Fixed in PR #148 — merged into main on 2026-07-29.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: TapTap/FastSync#101