-
Notifications
You must be signed in to change notification settings - Fork 207
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(iroh-net-report): Support wasm32 building & running #3139
Conversation
Documentation for this PR has been generated and is available at: https://n0-computer.github.io/iroh/pr/3139/docs/iroh/ Last updated: 2025-02-14T09:30:33Z |
2b9f228
to
942d4ac
Compare
The only thing that iroh-net-report would be doing in Wasm is running HTTPS probes. I have a browser version of iroh working that doesn't depend on iroh-net-report at all. This makes stuff a lot simpler. So, I'm going to close this. |
Hm, what I wrote above is incorrect. We do need the relay latencies to decide which relay to connect to. |
19fc5ba
to
4a84051
Compare
4a84051
to
5191a9c
Compare
5286020
to
d4149ba
Compare
13b0ae0
to
3fd7585
Compare
3fd7585
to
f9a3720
Compare
f9a3720
to
059ec18
Compare
059ec18
to
85ea312
Compare
Description
This makes iroh-net-report compile to Wasm. We make sure it's likely to work by grepping the generated Wasm file for "env" imports (which would make it not work in browsers).
Mostly this will disable functionality in iroh-net-report for the browser target - specifically, it disables STUN, QAD, ICMP and all other probes besides HTTPS to relays.
I've experimentally verified this code works with an integration test, it's really hard to come up with a good strategy for automating this testing due to requiring running cross-languages.
I'd like to do that as a follow-up once #3145 is merged.
Change checklist