Skip to main content
zcutlip
Apr 28, 2022 2:23 AM UTC
Question

op 2.x appends a newline to end of document bytes

It appears op version 2 (2.1.0 in my testing) appends a \x0a or ASCII newline character to the end of the byte stream when calling op document get.
I've run a few tests with versions 1.12.4 and 2.1.0. In each case I get the errant byte on the end with version 2, and not with version 1. I've attached a few screenshots. In the screenshots are two example documents each being retrieved by op version 1.12.4 and version 2.1.0. In each the bytes are piped to hexdump to show the errant \x0a byte on the end (or the absence of the byte).

Example 1:

Example 2:


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided

6 replies

zcutlip
zcutlipAuthor
Apr 28, 2022 2:26 AM UTC

I guess technically it's the ASCII "linefeed" not "newline"

Apr 28, 2022 6:12 PM UTC

Thanks for reporting this @zcutlip ,

I've created an internal issue to fix this bug!

zcutlip
zcutlipAuthor
Apr 29, 2022 12:44 AM UTC

Awesome. Thank you!

May 13, 2022 11:16 AM UTC

Glad to help, @zcutlip! Let us know if you encounter any other bugs/have any feedback on the CLI, overall!

zcutlip
zcutlipAuthor
May 23, 2022 1:34 AM UTC

This appears fixed in v2.3.0. Thanks!

1Password Employee
May 23, 2022 12:33 PM UTC

Thanks for the valuable feedback!