MiGz未能解压缩GZIP压缩数据
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 84
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
下列两组数据分别是GZIP和MiGz压缩二进制数据：
GZIP1：1f8b08000000000000003334323634320400ee129cde06000000
MiGz1：1f8b080400000000020008004d5a0400080000003334323634320400ee129cde06000000
GZIP2：1f8b08000000000000002b4b2c4b492c2b4b4c010071ec6fe909000000
MiGz2：1f8b080400000000020008004d5a04000b0000002b4b2c4b492c2b4b4c010071ec6fe909000000
MIGZ 压缩的数据会多出20008004d5a040008000或者20008004d5a04000b000，请问这10个字节能去掉吗？
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the GZIP1/GZIP2 and MiGz1/MiGz2 byte sequences in the Java library and command-line decompression paths. Determine whether the additional 10 bytes are valid MiGz metadata or should be removed, and verify that the affected MiGz data can be decompressed successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100