New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression: Zero length input using --stdin-line not handled properly #1302
Comments
Are you able to check with the fixes branch? There was a -l related fix there already. I'm on holiday right now so it's tricky to check myself at the moment. |
A fix is in the |
Sorry, must have missed the first email. Is there anything you'd still like
tested?
…On Thu, Jun 6, 2019, 4:22 PM Roger Light ***@***.***> wrote:
A fix is in the fixes branch now, I'm not entirely sure about other
behaviour though.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1302?email_source=notifications&email_token=AA2YJDNRFLLODDA2ZCWZ3NLPZGEZDA5CNFSM4HSDSM6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXEKQVY#issuecomment-499689559>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AA2YJDM7JEDVOJYKSJDZONDPZGEZDANCNFSM4HSDSM6A>
.
|
The fix is related to a previous commit that was fixing some -l messages not being sent at QoS > 0. I think it was just the final message not being sent. It all looks fine to me, but if you are able to confirm you get the behaviour you expect it would be nice to hear. |
Closes eclipse#1302. Thanks to Marcus Watkins.
Closes #1302. Thanks to Marcus Watkins.
Looks like #676 has cropped back up. It works fine with 1.5.3 but not 1.6.2:
Here's with 1.5.3:
The text was updated successfully, but these errors were encountered: