croc: problem with decoding: unexpected end of JSON input
Describe the bug
I get problem with decoding: unexpected end of JSON input
when trying to send files.
To Reproduce Steps to reproduce the behavior:
- Get a shell with
croc
in PATH (see below) - Send and receive a file or folder, preferably on the machine itself
Expected behavior It just works
Version croc version v8.1.1-e250eee
Get a shell with that version installed using: NIX_PATH=nixpkgs=https://github.com/nixos/nixpkgs/archive/c4364cdddc421dfdb4a60fda38ed955abce1603a.tar.gz nix-shell -p 'with (import<nixpkgs>{});buildGoModule rec {pname = "croc";version = "8.1.2";src = fetchFromGitHub {owner = "schollz";repo = pname;rev = "v${version}";sha256 = "0m7kgfmdbmz0r0dydz7j9cllp77076qgdcmkw3jnrsj169f5acfa";};vendorSha256 = "1fjv4y7pkwd4wsq3y66r75gr0makhjcdf0i3cpxgv03x5ahkf16b";doCheck = false;subPackages = [ "." ];}'
Additional context
[debug] 21:18:34 tcp.go:421: sending password
[debug] 21:18:34 tcp.go:430: waiting for first ok
[debug] 21:18:34 tcp.go:445: sending room
[debug] 21:18:34 tcp.go:454: waiting for room confirmation
[debug] 21:18:35 tcp.go:467: all set
[debug] 21:18:35 croc.go:540: banner: 9010,9011,9012,9013
[debug] 21:18:35 croc.go:546: receiver connection established: &{connection:0xc0003b4010}
[debug] 21:18:35 croc.go:551: sending ips?
[debug] 21:18:35 croc.go:560: ips data:
[error] 2020/08/31 21:18:35 croc.go:563: ips unmarshal error: invalid character '\x01' looking for beginning of value
[debug] 21:18:35 croc.go:613: exchanged header message
securing channel...[debug] 21:18:35 croc.go:625: ready
[debug] 21:18:35 message.go:46: writing pake message
[error] 2020/08/31 21:18:36 compress.go:46: error copying data: unexpected EOF
[debug] 21:18:36 croc.go:848: problem with decoding: unexpected end of JSON input
[debug] 21:18:36 croc.go:650: got error processing: problem with decoding: unexpected end of JSON input
problem with decoding: unexpected end of JSON input
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 21 (11 by maintainers)
I tried using Nix using your command and still couldn’t reproduce this issue - locally or across the public relay.
The segfault you refer to is only a bug from an error that didn’t propogate (ea781e5). The error was that it didn’t connect. You can try the master version, it will print out the reason it didn’t connect in debugging.