Spoolman integration search function Broken on Brave browser

[Ntrondle]

Mainsail Version:

v2.12.0

Browser:

Other (Please tell us below)

Device:

Desktop PC

Operating System:

macOS

What happened?

When trying to use the search function in mainsail the interface locks up and will not let the user browse through the different pages of spool, the search function will also not fetch the filament that was entered in the search window.

The issue is fixed by reloading the entier page.

What did you expect to happen instead?

search function should work and not freeze the spoolman spool selection page.

How to reproduce this bug?

Reported not working on Brave :
Version 1.71.121 Chromium: 130.0.6723.91 (arm64)

sppolman :
Version 0.20.0 (4f8d5ab)

Additional information:

let me know if additional information should be given. happy to give anything else.

[Ntrondle]

Additional testing with Safari, Firefox, and Chrome shows the same behavior as observed with Brave.

[meteyou]

@Ntrondle thx for your report. i updated spoolman right now to v0.20.0 and cannot find any issues. pls upload your moonraker.log. maybe i can find any issue in it.

[Ntrondle]

sorry for the late reply...

here's my moonraker log hopefully you can find the reason behind my problem as it is quite odd...

moonraker.log

I also tried pinging from the klipper to the spoolman host and it's also working...

absak@helios:~ $ ping 192.168.2.24
PING 192.168.2.24 (192.168.2.24) 56(84) bytes of data.
64 bytes from 192.168.2.24: icmp_seq=1 ttl=64 time=0.464 ms
64 bytes from 192.168.2.24: icmp_seq=2 ttl=64 time=0.423 ms
64 bytes from 192.168.2.24: icmp_seq=3 ttl=64 time=0.455 ms
64 bytes from 192.168.2.24: icmp_seq=4 ttl=64 time=0.503 ms
64 bytes from 192.168.2.24: icmp_seq=5 ttl=64 time=0.490 ms
64 bytes from 192.168.2.24: icmp_seq=6 ttl=64 time=0.378 ms
64 bytes from 192.168.2.24: icmp_seq=7 ttl=64 time=0.508 ms
64 bytes from 192.168.2.24: icmp_seq=8 ttl=64 time=0.530 ms
^C
--- 192.168.2.24 ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 7174ms

[meteyou]

i checked your moonraker.log and found this:

2024-11-27 13:18:27,844 [spoolman.py:_connect_websocket()] - Connecting To Spoolman: ws://192.168.2.24:7912/api/v1/spool
2024-11-27 13:18:27,850 [server.py:add_log_rollover_item()] - Failed to Connect to spoolman: [Errno 101] Network is unreachable

I also found this issue in your log:

2024-11-27 13:18:31,875 [announcements.py:_fetch_moonlight()] - Failed to update subscription 'klipper': [Errno -3] Temporary failure in name resolution
2024-11-27 13:18:33,889 [announcements.py:_fetch_moonlight()] - Failed to update subscription 'spoolman': [Errno -3] Temporary failure in name resolution

This have nothing todo with the spoolman issue itself, but it looks like a generic "network setting issue" here.

But i should check if i can catch "network issues" when using the spoolman API via moonraker.