Bug? or Edge update?

[Boca-NeedM]

Before submitting

• I have searched existing issues to make sure this bug hasn't already been reported
• I have updated to the latest version of the software to verify the issue still exists
• I have cleared cache/cookies/storage or tried in a private/incognito window (if applicable)

Hardware

Other

Connection Type

HTTP

Local or Hosted

https://client.meshtastic.org

Firmware Version

No

Operating System

W11

Browser

Egde

Expected Behavior

A working website ;)

Actual Behavior

This is a little embarrassing...
We are really sorry but an error occurred in the web client that caused it to crash.
This is not supposed to happen, and we are working hard to fix it.

The best way to prevent this from happening again to you or anyone else is to report the issue to us.

Please include the following information in your report:

What you were doing when the error occurred
What you expected to happen
What actually happened
Any other relevant information
You can report the issue to our GitHub

Return to the dashboard

Chirpy the Meshtastic error
Error Details
Error message:
Cannot read properties of undefined (reading 'num')

Stack trace:
TypeError: Cannot read properties of undefined (reading 'num')
at https://client.meshtastic.org/index-9RHnKvRw.js:642:165845
at Object.useMemo (https://client.meshtastic.org/index-9RHnKvRw.js:100:61044)
at Wz.Xe.useMemo (https://client.meshtastic.org/index-9RHnKvRw.js:17:7324)
at sfe (https://client.meshtastic.org/index-9RHnKvRw.js:642:165830)
at Fb (https://client.meshtastic.org/index-9RHnKvRw.js:100:48430)
at cv (https://client.meshtastic.org/index-9RHnKvRw.js:100:71296)
at YA (https://client.meshtastic.org/index-9RHnKvRw.js:100:81687)
at A_ (https://client.meshtastic.org/index-9RHnKvRw.js:100:117553)
at H6 (https://client.meshtastic.org/index-9RHnKvRw.js:100:116593)
at Iv (https://client.meshtastic.org/index-9RHnKvRw.js:100:116423)

Steps to Reproduce

Unknown

Relevant console output

TypeError: Cannot read properties of undefined (reading 'num')
    at https://client.meshtastic.org/index-9RHnKvRw.js:642:165845
    at Object.useMemo (https://client.meshtastic.org/index-9RHnKvRw.js:100:61044)
    at Wz.Xe.useMemo (https://client.meshtastic.org/index-9RHnKvRw.js:17:7324)
    at sfe (https://client.meshtastic.org/index-9RHnKvRw.js:642:165830)
    at Fb (https://client.meshtastic.org/index-9RHnKvRw.js:100:48430)
    at cv (https://client.meshtastic.org/index-9RHnKvRw.js:100:71296)
    at YA (https://client.meshtastic.org/index-9RHnKvRw.js:100:81687)
    at A_ (https://client.meshtastic.org/index-9RHnKvRw.js:100:117553)
    at H6 (https://client.meshtastic.org/index-9RHnKvRw.js:100:116593)
    at Iv (https://client.meshtastic.org/index-9RHnKvRw.js:100:116423)

Screenshots

No response

Additional Context

No response

[danditomaso]

So there was an issue when the UI loads prior to the node num being read. I have addressed in our test environment and I would like you to retry there (https://client-test.meshtastic.org). It should be solved now.