extcmd based on glibc must respect the on_line() protocol
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PlainBox (Toolkit) |
Fix Released
|
Critical
|
Zygmunt Krynicki |
Bug Description
Old thread based extcmd was doing line-by-line reads with internal buffering. New extcmd is doing block-based reads which are not bound by the end-of-line constraints. This breaks applications that always expect to have at most one line to process.
For example (excuse the translation here), here the rfc822 parser cannot handle a multi-line buffer correctly:
DEBUG plainbox.
Before the interface offers buffer-based events, extcmd must emulate the old behavior.
Related branches
- Daniel Manrique (community): Approve
-
Diff: 68 lines (+39/-5)1 file modifiedplainbox/plainbox/vendor/extcmd/glibc.py (+39/-5)
Changed in plainbox: | |
status: | In Progress → Fix Committed |
Changed in plainbox: | |
status: | Fix Committed → Fix Released |