You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As I mentioned in #3243 (comment), I found that only UDP has the weird edge-triggered epoll behavior in the output buffer like the one of the input buffer I mentioned in #2673 and fixed in #3243.
That is, if the file is already writable and someone writes more bytes to it, it will be writable again.
This thing happens only in UDP, but not other file types (TCP, Unix, Pipe, etc.). I don't know why, but it's better to file an issue here. I have some Linux tests for this issue as shown below.
To Reproduce
Note that, from the tests below, only UDP has trigger_writable set to be true.
Describe the issue
As I mentioned in #3243 (comment), I found that only UDP has the weird edge-triggered epoll behavior in the output buffer like the one of the input buffer I mentioned in #2673 and fixed in #3243.
That is, if the file is already writable and someone writes more bytes to it, it will be writable again.
This thing happens only in UDP, but not other file types (TCP, Unix, Pipe, etc.). I don't know why, but it's better to file an issue here. I have some Linux tests for this issue as shown below.
To Reproduce
Note that, from the tests below, only UDP has
trigger_writable
set to be true.Operating System (please complete the following information):
Shadow (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: