rust-bitcoin / rust-bitcoin/rust-miniscript
wasm descriptor .address() panic
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 426
- Forks
- 200
- Avg merge
- 7d 17h
- Merged PRs (30d)
- 8
Description
howdy,
hit a panic on calling .address on a Descriptor<XOnly> in WASM, can't reproduce outside of WASM.
I don't have time (before TAB) to make a good repro, but opening an issue so I don't forget / if anyone else wants to poke at it.
the offending descriptor: https://gist.github.com/JeremyRubin/761d4c97a69a96ec51e4a9f729d6835c
issue comes up if I do it with the raw AST or if i to_string / from_str it first.
target is wasm32-unknown-unknown running in wasmer
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 reproducing the panic on wasm32-unknown-unknown under Wasmer with the linked Descriptor and compare .address() on the raw AST versus after the to_string/from_str round trip. Trace the .address() path to identify the WASM-specific failure, then add a regression test showing that the descriptor no longer panics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100