-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Extra newline at end of "dag get" result #3503
Copy link
Copy link
Closed
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upkind/bugA bug in existing code (including security flaws)A bug in existing code (including security flaws)status/readyReady to be workedReady to be worked
Metadata
Metadata
Assignees
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upkind/bugA bug in existing code (including security flaws)A bug in existing code (including security flaws)status/readyReady to be workedReady to be worked
Version information:
go-ipfs version: 0.4.5-dev-4cb236c
Repo version: 4
System version: amd64/linux
Golang version: go1.7.1
Type:
Bug
Priority:
P1 (for me)
Description:
Using either the cli or http api the dag get command seems to add an extra newline 0x0A on the end of the raw data.
To reproduce using cli:
then
ipfs dag get zdpuAs3whHmb9T1NkHSLGF45ykcKrEBxSLiEx6YpLzmKbQLEB | wc -cshould give 13, but gives 14, and the extra byte on the end is a newline
The same JSON through the http api results in the same extra byte. The JSON is not special, similar JSON with more/different elements does the same.