The hpack test task references fixtures removed from the repository
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 909
- Forks
- 68
- Avg merge
- 6d 8h
- Merged PRs (30d)
- 8
Description
Summary
rake hpack and therefore rake all fail immediately because spec/hpack_test_spec.rb iterates spec/hpack-test-case/raw-data, but spec/hpack-test-case is absent from current main.
Reproduction
On ac8d59014ed282febe5fd096cb3286c32b476db8 with the repository bundle:
bundle exec rake hpack
Errno::ENOENT: No such file or directory .../spec/hpack-test-case/raw-data
0 examples, 0 failures, 1 error occurred outside of examples
The fixture tree existed historically and disappeared in the fresh-version reset (bd74873), while the spec and Rake task remained. The normal rake spec intentionally excludes this file and passes 448 examples.
Suggested follow-up
Either restore/pin the HPACK fixture corpus (ideally with an explicit provenance/version) or remove/replace the stale task and spec. I have not changed test files as part of the dependency audit.
I used an AI coding assistant during source/test-task verification.
Contributor guide
No contributing guide indexed for this repository
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 with spec/hpack_test_spec.rb and the Rake task behind rake hpack; reproduce the missing spec/hpack-test-case/raw-data failure, then inspect the fixture-removal history around bd74873. Decide whether the fixture corpus can be restored with provenance or the stale task and spec should be replaced; done means rake hpack and rake all no longer fail while the existing spec suite remains passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100