void-linux / void-linux/void-packages
`fs-repo-migrations`'s `fs-repo-11-to-12` panics
Open
Nobody has claimed this yet.
bug
needs-testing
- Dominant language
- Shell
- Stars
- 3.4k
- Forks
- 2.8k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 299
Description
Is this a new report?
Yes
System Info
Void 6.12.8_1 x86_64 GenuineIntel/VM uptodate rrmFFFFF
Package(s) Affected
fs-repo-migrations-2.0.2+13~14+v1.0.0_2, kubo-0.29.0_1
Does a report exist for this bug with the project's home (upstream) and/or another distro?
No response
Expected behaviour
it runs the repository migration
Actual behaviour
it crashes with:
panic: qtls.ConnectionState doesn't match
goroutine 1 [running]:
github.com/ipfs/fs-repo-migrations/fs-repo-11-to-12/vendor/github.com/marten-seemann/qtls-go1-15.init.0()
/builddir/fs-repo-migrations-2.0.2+13~14+v1.0.0/_build-fs-repo-migrations-xbps/src/github.com/ipfs/fs-repo-migrations/fs-repo-11-to-12/vendor/github.com/marten-seemann/qtls-go1-15/unsafe.go:11 +0x22e
Steps to reproduce
run fs-repo-11-to-12 (or ipfs daemon --migrate from kubo which runs this)
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
Reproduce the failure by running fs-repo-11-to-12, or ipfs daemon --migrate from kubo, and inspect the panic at vendor/github.com/marten-seemann/qtls-go1-15/unsafe.go:11. Trace the fs-repo-11-to-12 package and its qtls dependency to identify the version mismatch; done means the repository migration runs without the qtls.ConnectionState panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100