calendar component panics the wasm browser (and the SSR)

Open
#321 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust, wasm
Domain
frontend, web-dev

Research direction

Start by locating the calendar component and its browser and server-side rendering entry points; the issue does not name files or a failing test. Reproduce the panic and trace the time access that fails on wasm, then check whether the same path is used during SSR. Done when the calendar works in both environments without the reported panic.

Written by the indexing model from the issue text.

Description

hi. i have no idea whats the issue here but i cant get the calendar component to work. on a new project.

please let me know how to get more logs and debug if needed.

10:17:27 [dev] Build completed successfully in 31.94s, launching app! 💫 
10:17:27 [server]  INFO Registering: POST /api/echo
10:17:51 [server] [200] / 
10:17:53 [web] panicked at /rustc/58cf8f9c35b355199727627d07ae34a4e2846d67/library/std/src/sys/time/unsupported.rs:35:9:
time not implemented on this platform

Stack:

__wbg_get_imports/__wbg_new_c5078a91ae210258/<@http://127.0.0.1:32835/wasm/web.js:1429:25
logError@http://127.0.0.1:32835/wasm/web.js:2456:18
__wbg_new_c5078a91ae210258@http://127.0.0.1:32835/wasm/web.js:1428:57
@http://127.0.0.1:32835/wasm/web_bg.wasm:wasm-function[29773]:0x44a08a
@http://127.0.0.1:32835/wasm/web_bg.wasm:wasm-function[16627]:0x3c01a3
**** truncated ****
@http://127.0.0.1:32835/wasm/web_bg.wasm:wasm-function[8260]:0x2fe3cc
@http://127.0.0.1:32835/wasm/web_bg.wasm:wasm-function[529]:0x803b8
Dominant language
Rust
Stars
358
Forks
90
Avg merge
54m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DioxusLabs/dioxus-components

All issues in DioxusLabs/dioxus-components

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.