`hoardy-web serve` fails to parse a submitted WRR, the extension stops archiving as the result

[danilbraun]

The extension stopped archiving reqres, the server prints the following errors:

127.0.0.1 - - [22/Jul/2025 01:12:36] "POST /pwebarc/dump?profile=default HTTP/1.
1" 400 101
127.0.0.1 - - [22/Jul/2025 01:12:39] "GET /hoardy-web/server-info HTTP/1.1" 200
176
Traceback (most recent call last):
  File "C:\Users\Danil\AppData\Local\Programs\Python\Python313\Lib\site-packages
\hoardy_web\__main__.py", line 2744, in dump_wrr
    reqres = wrr_load_cbor_fileobj(cborf)
  File "C:\Users\Danil\AppData\Local\Programs\Python\Python313\Lib\site-packages
\hoardy_web\wrr.py", line 338, in wrr_load_cbor_fileobj
    struct = _cbor2.load(fobj)
_cbor2.CBORDecodeEOF: premature end of stream (expected to read -1 bytes, got 28
5060 instead)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "C:\Users\Danil\AppData\Local\Programs\Python\Python313\Lib\site-packages
\hoardy_web\__main__.py", line 2572, in decorated
    return func(*args, **kwargs)
  File "C:\Users\Danil\AppData\Local\Programs\Python\Python313\Lib\site-packages
\hoardy_web\__main__.py", line 2748, in dump_wrr
    raise Failure("failed to parse content body: %s", str(exc)) from exc
kisstdlib.failure.Failure: failed to parse content body: premature end of stream
 (expected to read -1 bytes, got 285060 instead)

[oxij]

_cbor2.CBORDecodeEOF: premature end of stream (expected to read -1 bytes, got 285060 instead)

This looks like a bug in `cbor2` module to me. Usually, server errors mean disk IO errors, so, normally, the extension stopping on server errors is useful. But in this case it's annoying, I agree. I'll add a toggle to make it temporarily ignore server errors then. Meanwhile, you can probably keep those reqres archived in your browser's local storage and also re-archive them via `saveAs`, just in case. It would be nice to see the offending CBOR to debug this, but neither the extension nor the tool can handle errors that graciously at the moment to allow for this. This will be fixed, but I'm spending most of my time writing the self-tracking article at the moment.

[oxij]

Okay, the toggles are published as a part of https://github.com/Own-Data-Privateer/hoardy-web/releases/tag/extension-v1.22.0

You can use them to archive everything that can be archived, leaving only the offending reqres in the queue/storage, which you can then export via saveAs separately, giving you the minimal reproducible example WRR that breaks the tool, which you can then either send me via email (I won't be publishing it), or debug it yourself.

[oxij]

So, can I have an example WRR for this issue?

[oxij]

Apparently, this is a common issue with cbor2, see #21.