Deal with timed out/failed requests

[edditler]

When saving a note, one of the toolbar icons in the editor will turn into a checkmark - indicating success - even if the response was 500 or timeout.

Archivy should handle the responses to fetch calls correctly.

[edditler]

It appears that fetch() times out after more than a minute in Chrome and Firefox, which seems way too long. I included a timeout function in edditler@e156b0a#diff-82dfc4e59d32f549c0c0f2d629c4205952911a4a80a26fb4a55ba7ce94e0f66bR286-R322 and will test this for some time.

[Uzay-G]

Already handling responses where the response wasn't a 200 code is something I should have done already 😅. This is a good idea.

[Uzay-G]

Do you have any code for this? otherwise i'll start working on it. This + hopefully I can build a new archivy-lite docker image (just ripgrep) and we can make a new release.

[edditler]

Already handling responses where the response wasn't a 200 code is something I should have done already

I didn't go through all the functions. I just included it for tags (https://github.com/edditler/archivy/blob/main/archivy/static/component/frontmatter_tags.js#L33-L47) and the content for now (https://github.com/edditler/archivy/blob/main/archivy/templates/dataobjs/show.html#L286-L327
)

Surprisingly, a timeout of 3s was not always long enough, and even with 10s, I get sporadic alerts. It's better to know than to accidentally close the tab, but it's not a great solution for the problem itself (that edits are easily lost).

[Uzay-G]

e429e1c works on this