Fix WebAssembly transport timeout crash - #30
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe tool adds ChangesTool time API
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to This change addresses the WASM timing compatibility issue without an established regression or merge-blocking risk. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The browser tool crashes during its initial protocol read because
std::time::Instantis unsupported onwasm32-unknown-unknown.Use
web-timefor the shared transport timeout bookkeeping so browser builds use a supported monotonic clock while native behavior remains unchanged.Pin OSS CAD Suite to the last known working release so unrelated nightly Yosys changes do not break the Verilog CI job.