Grout crash when api is not responsive

[yodatak]

Describe the bug
On rocknix with a large library i got some slow response then when i try to download a file it crash with any message
or fetching tasks: AxiosError: Request aborted
LA https://XXXX/assets/index-C3VQmLN3.js:66
onabort https://XXXX/assets/index-C3VQmLN3.js:68
EventHandlerNonNull*x$</< https://XXXX/assets/index-C3VQmLN3.js:68

Reproduction Steps
Steps to reproduce the behavior:

1. slow request room server with 44138 games and 1,5 TO of roms
2. sometime it crash

Expected Behavior
Have at least a retry button or something to know what append

Information

• CFW: rocknix
• CFW Version: nightly-20260426
• Handheld Device: retroid pocket flip 2
• Grout Version: v4.8.1.1-beta.5 and it also try the stable
• RomM Version: 4.8.1

[BrandonKowalski]

The error message you have provided does not make any sense. Grout is written in Go and you are providing an Axios timeout which is a frontend Javascript library from the browser.

Can you please enable debug logging and provide the contents of grout.log?

[yodatak]

thanks here the logs i got with setting to debug in grout ( the logs from axis was from the web )

grout.log

app.log

[BrandonKowalski]

Since you likely can't make it into settings you could try adding the following to your config.json.

"api_timeout": 300

This longer timeout might help Grout get everything cached.

This is something that has been on our radar with other users who have extremely large libraries. The most meaningful change will have to happen in the RomM backend itself but just haven't had the time to look into it.

[gozes]

Since you likely can't make it into settings you could try adding the following to your config.json.

"api_timeout": 300

This longer timeout might help Grout get everything cached.

This is something that has been on our radar with other users who have extremely large libraries. The most meaningful change will have to happen in the RomM backend itself but just haven't had the time to look into it.

So far for me that didn't work. After 300 second the catch will stay at 0%. then trying to open any platform will cause a similar problem

I don't mind waiting the first time so it would be nice if the time value could be any number rather then being limited to no more then 300

[gozes]

Side question, if I just copy over some roms to the sdcard would the save sync still work even when grout was not the one to put dose games there and the catch not being build?

I don't mind having to copy roms to the sdcard by hand to get around the timeouts for now but I would hope that the save sync still works.