[Bug 2130810] [NEW] base64 unable to decode some file

[Skia]

Public bug reported:

`base64` provided by rust-coreutils/0.3.0-0ubuntu2 (resolute-proposed)
is unable to decode the attached `base64_core` file.

❯ base64 -d base64_core >/dev/null

thread 'main' panicked at src/uu/base32/src/base_common.rs:615:22:
called `Result::unwrap()` on an `Err` value: USimpleError { code: 1, message: "error: invalid input" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
zsh: IOT instruction  base64 -d base64_core > /dev/null

❯ echo $?
134

❯ gnubase64 -d base64_core >/dev/null
❯ echo $?
0

The current commit of the upstream repo (ccc6233fba5281880cf01517755a594e7c47156c) doesn't have the issue anymore, so I'm fairly confident the issue is actually already fixed and will reach resolute at some point.
I'm opening the bug to actually track the issue and refer to it wherever I need to work around it.

Just in case anyone is wondering, the attached file is a base64(gzip(coredump file)) from the `cat` utility coming from https://code.launchpad.net/~daisy-pluckers/+recipe/apport-test-crashes
The following shows some details:
❯ gnubase64 -d base64_core | gzip -d | file -
/dev/stdin: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style, from '/usr/bin/cat'

** Affects: rust-coreutils (Ubuntu)
     Importance: Low
         Status: New

** Attachment added: "base64_core"
   https://bugs.launchpad.net/bugs/2130810/+attachment/5924747/+files/base64_core

** Summary changed:

- base64 unable to decode
+ base64 unable to decode some file

** Description changed:

  `base64` provided by rust-coreutils/0.3.0-0ubuntu2 (resolute-proposed)
  is unable to decode the attached `base64_core` file attached.
  
  ❯ base64 -d base64_core >/dev/null
  
  thread 'main' panicked at src/uu/base32/src/base_common.rs:615:22:
  called `Result::unwrap()` on an `Err` value: USimpleError { code: 1, message: "error: invalid input" }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
  zsh: IOT instruction  base64 -d base64_core > /dev/null
  
  ❯ echo $?
  134
  
- 
  ❯ gnubase64 -d base64_core >/dev/null
  ❯ echo $?
  0
  
  The current commit of the upstream repo (ccc6233fba5281880cf01517755a594e7c47156c) doesn't have the issue anymore, so I'm fairly confident the issue is actually already fixed and will reach resolute at some point.
  I'm opening the bug to actually track the issue and refer to it wherever I need to work around it.
  
- Just in case anyone is wondering, the attached file is a
- base64(gzip(coredump file)) from the `cat` utility coming from
- https://code.launchpad.net/~daisy-pluckers/+recipe/apport-test-crashes
+ Just in case anyone is wondering, the attached file is a base64(gzip(coredump file)) from the `cat` utility coming from https://code.launchpad.net/~daisy-pluckers/+recipe/apport-test-crashes
+ The following shows some details:
+ ❯ gnubase64 -d base64_core | gzip -d | file -
+ /dev/stdin: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style, from '/usr/bin/cat'

** Description changed:

  `base64` provided by rust-coreutils/0.3.0-0ubuntu2 (resolute-proposed)
- is unable to decode the attached `base64_core` file attached.
+ is unable to decode the attached `base64_core` file.
  
  ❯ base64 -d base64_core >/dev/null
  
  thread 'main' panicked at src/uu/base32/src/base_common.rs:615:22:
  called `Result::unwrap()` on an `Err` value: USimpleError { code: 1, message: "error: invalid input" }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
  zsh: IOT instruction  base64 -d base64_core > /dev/null
  
  ❯ echo $?
  134
  
  ❯ gnubase64 -d base64_core >/dev/null
  ❯ echo $?
  0
  
  The current commit of the upstream repo (ccc6233fba5281880cf01517755a594e7c47156c) doesn't have the issue anymore, so I'm fairly confident the issue is actually already fixed and will reach resolute at some point.
  I'm opening the bug to actually track the issue and refer to it wherever I need to work around it.
  
  Just in case anyone is wondering, the attached file is a base64(gzip(coredump file)) from the `cat` utility coming from https://code.launchpad.net/~daisy-pluckers/+recipe/apport-test-crashes
  The following shows some details:
  ❯ gnubase64 -d base64_core | gzip -d | file -
  /dev/stdin: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style, from '/usr/bin/cat'

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rust-coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/2130810

Title:
  base64 unable to decode some file

Status in rust-coreutils package in Ubuntu:
  New

Bug description:
  `base64` provided by rust-coreutils/0.3.0-0ubuntu2 (resolute-proposed)
  is unable to decode the attached `base64_core` file.

  ❯ base64 -d base64_core >/dev/null

  thread 'main' panicked at src/uu/base32/src/base_common.rs:615:22:
  called `Result::unwrap()` on an `Err` value: USimpleError { code: 1, message: "error: invalid input" }
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
  zsh: IOT instruction  base64 -d base64_core > /dev/null

  ❯ echo $?
  134

  ❯ gnubase64 -d base64_core >/dev/null
  ❯ echo $?
  0

  The current commit of the upstream repo (ccc6233fba5281880cf01517755a594e7c47156c) doesn't have the issue anymore, so I'm fairly confident the issue is actually already fixed and will reach resolute at some point.
  I'm opening the bug to actually track the issue and refer to it wherever I need to work around it.

  Just in case anyone is wondering, the attached file is a base64(gzip(coredump file)) from the `cat` utility coming from https://code.launchpad.net/~daisy-pluckers/+recipe/apport-test-crashes
  The following shows some details:
  ❯ gnubase64 -d base64_core | gzip -d | file -
  /dev/stdin: ELF 64-bit LSB core file, x86-64, version 1 (SYSV), SVR4-style, from '/usr/bin/cat'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rust-coreutils/+bug/2130810/+subscriptions