Skip to content

fix(node): enforce hard timeout after continue #964

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
leumor merged 1 commit into from
Feb 5, 2026
+984 −186
Merged

fix(node): enforce hard timeout after continue #964

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 2 additions & 6 deletions src/main/java/network/crypta/node/PeerNodeTransport.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -188,11 +188,7 @@ public void sendSync(Message req, ByteCounter ctr, boolean realTime)
MessageItem item = sendAsync(req, cb, ctr);
cb.waitForSend(MINUTES.toMillis(1));
if (!cb.done) {
LOG.warn(
"Waited too long for a blocking send for {} to {}",
req,
peer.selfPeerNode(),
new Exception(STR_ERROR));
LOG.warn("Waited too long for a blocking send for {} to {}", req, peer.selfPeerNode());
peer.localRejectedOverload("SendSyncTimeout", realTime);
// Try to un-queue it, since it presumably won't be of any use now.
if (!peer.getMessageQueue().removeMessage(item)) {
Expand Down Expand Up @@ -441,7 +437,7 @@ private class SyncMessageCallback implements AsyncMessageCallback {
/** True if completion occurred due to a disconnect. */
private boolean disconnected = false;

/** True once the message has been sent to the socket. */
/** True, once the message has been sent to the socket. */
private boolean sent = false;

/**
Expand Down
Loading
Loading