#1438 File transfer fails near the end when using epoll
Reporter
Link Mauve
Owner
Zash
Created
Updated
Stars
★ (1)
Tags
Status-Fixed
Milestone-0.12
Type-Defect
Priority-Medium
Link Mauve
on
What steps will reproduce the problem?
1. Enable network_backend = "epoll"
2. Send a file through XEP-0234 using an XEP-0260 candidate selecting Prosody’s mod_proxy65.
3. Observe the file arriving on the other end.
What is the expected output?
The file arrives in full on the other end.
What do you see instead?
The file transfer stops at like 99%.
What version of the product are you using? On what operating system?
Prosody trunk commit 10276:4e4ce7400b39, on ArchLinux.
Please provide any additional information below.
A file smaller than 4 KiB goes through, smaller than 8 doesn’t, smaller than 12 does, etc.
This sounds like the bug where LuaSocket and Prosody have different buffer sizes and the buffer then never gets flushed if it isn’t in the right window.
Zash
on
Discussed in the chatroom. Some additional debug logging added. Detailed logs and possibly a packet capture would be helpful in figuring it out.
Changes
tags Status-NeedInfo
owner Zash
Zash
on
Has this happened again since adding that debug logging?
Zash
on
No updates, assuming it fixed itself at some point.
What steps will reproduce the problem? 1. Enable network_backend = "epoll" 2. Send a file through XEP-0234 using an XEP-0260 candidate selecting Prosody’s mod_proxy65. 3. Observe the file arriving on the other end. What is the expected output? The file arrives in full on the other end. What do you see instead? The file transfer stops at like 99%. What version of the product are you using? On what operating system? Prosody trunk commit 10276:4e4ce7400b39, on ArchLinux. Please provide any additional information below. A file smaller than 4 KiB goes through, smaller than 8 doesn’t, smaller than 12 does, etc. This sounds like the bug where LuaSocket and Prosody have different buffer sizes and the buffer then never gets flushed if it isn’t in the right window.
Discussed in the chatroom. Some additional debug logging added. Detailed logs and possibly a packet capture would be helpful in figuring it out.
ChangesHas this happened again since adding that debug logging?
No updates, assuming it fixed itself at some point.
Changes