404 from update cache if mod.io mod deleted

[jieyouxu]

Current Workaround

• Remove deleted/renamed mod from profiles
• Delete the cache directory

[jieyouxu]

Also need to improve the error reporting when this situation does occur.

[LabManCam]

I have been running into this issue for the last several days and I'm wondering if it is an issue with a moved resource or something else, like a rate limit from Mod.io.
I quit out of the app and reload, attempt to update the cache again, and a different mod is throwing the error. Sometimes it is the 5th mod to try the update, other times its the 80th. Are the error messages indicating that the last request is what caused the error? Or is it being caused by a mod that isn't being put into the console? See the attached excerpt of all the different times that it errors with no access.
error logs.txt

[jieyouxu]

Are the error messages indicating that the last request is what caused the error? Or is it being caused by a mod that isn't being put into the console?

Note that the error message isn't particularly helpful here -- the last request might not necessarily be the one causing the 404 error (which is what I meant by the error message needing to be improved). Could you please send the mod list that triggers the 404 error?

[LabManCam]

I opened up each mod's page, by clicking on it from mod integration, and found that one of the mods had been deleted. After removing that mod, the 404's stopped. It looks like I was incorrect, but the error messages weren't helpful in identifying the issue.

[jieyouxu]

how to find the mod causing the 404 error?

We improved the error reporting on master, which will tell you (in a future release) that
https://mod.io/g/drg/m/server-filter-by-region#3134718 was deleted.

ERROR mint::gui::message: failed to fetch mod files for <https://mod.io/g/drg/m/server-filter-by-region#3134718> (mod_id = 3134718): HTTP status client error (404 Not Found): The requested mod id could not be found.