[I] [rust] Lost wakeup in LogFetchBuffer::await_not_empty causes empty poll [fluss]

["fresh-borzoni (via GitHub)" <gi...@apache.org>]

fresh-borzoni opened a new issue, #3713:
URL: https://github.com/apache/fluss/issues/3713

   ### Search before asking
   
   - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar.
   
   
   ### Fluss version
   
   0.9.0 (latest release)
   
   ### Please describe the bug 🐞
   
   `await_not_empty` builds its `notified()` future after the `is_empty()` check, and the buffer signals via `notify_waiters()`, so a fetch landing in that window is lost and `poll()` blocks to its timeout, returning empty with data available. 
   Root cause of the flaky `test_poll_batches` (#3694).
   
   ### Solution
   
   arm the waiter with `enable()` before the check (tokio's documented `notified()`/`enable()` pattern).
   
   ### Are you willing to submit a PR?
   
   - [x] I'm willing to submit a PR!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] [rust] Lost wakeup in LogFetchBuffer::await_not_empty causes empty poll [fluss]

["fresh-borzoni (via GitHub)" <gi...@apache.org>]

fresh-borzoni closed issue #3713: [rust] Lost wakeup in LogFetchBuffer::await_not_empty causes empty poll
URL: https://github.com/apache/fluss/issues/3713


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@fluss.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org