|
Repo Added
|
Files
146
|
Badge
README BADGES
|
gitlab-ci
fix: Make sure to only stop event loop once in ReaderFromAsyncReader::Read() The handler passed to the asynchronous reader can be called multiple times after adding a call to `AsyncRead()` to the event loop, not only once when there is data available, but also if the asynchronous reader encounters an error. Since the event loop is only run recursively **once** per ReaderFromAsyncReader::Read() call, we need to make sure it's also stopped only once. Otherwise it may stop the event loop for good. Ticket: MEN-9954 Changelog: None Signed-off-by: Vratislav Podzimek <vratislav.podzimek+auto-signed@northern.tech> (cherry picked from commit 4c2c5246d)
25 of 29 new or added lines in 3 files covered. (86.21%)
8488 of 10433 relevant lines covered (81.36%)
21663.72 hits per line
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|
| Builds | Branch | Commit | Type | Ran | Committer | Via | Coverage |
|---|---|---|---|---|---|---|---|
| 2702669750 | pr_1997 | fix: Make sure to only stop event loop once in ReaderFromAsyncReader::Read() The handler passed to the asynchronous reader can be called multiple times after adding a call to `AsyncRead()` to the event loop, not only once when there is data avail... | Pull #1997 | gitlab-ci |
81.36 |