linkedin / linkedin/migz

IndexOutOfBoundsException

Open
#8 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
84
Forks
12
PR merge metrics
No merged PRs in 30d

Description

Hi!

```
root@wendigo:/data/snc_backups/full/temp# pv stream.gz | /home/ayengar/munzip | mbstream -x -v
Decompressing stdin using 32 threads
Exception in thread "main" java.lang.IndexOutOfBoundsException
at java.base/java.io.BufferedInputStream.read(BufferedInputStream.java:344)
at com.linkedin.migz.MiGzInputStream.readFromInputStream(MiGzInputStream.java:222)
at com.linkedin.migz.MiGzInputStream.decompressorThreadWithInflater(MiGzInputStream.java:172)
at com.linkedin.migz.MiGzInputStream.decompressorThread(MiGzInputStream.java:114)
at com.concurrentli.Interrupted.lambda$ignored$1(Interrupted.java:48)
at java.base/java.lang.Thread.run(Thread.java:829)
72.0KiB 0:00:00 [ 725KiB/s] [> ] 0%
root@wendigo:/data/snc_backups/full/temp#
```

'Nuff said?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with MiGzInputStream.java, especially readFromInputStream and decompressorThreadWithInflater, then reproduce the reported munzip and mbstream command if the input is available. Determine the cause of the IndexOutOfBoundsException and add coverage for the failing decompression case; done means the command no longer terminates with this exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.