Automated submission seems to have started failing
$ kubectl logs anti-linkrot-manual-47mnc
https://www.bentasker.co.uk/posts/blog/house-stuff/converting-a-zafiras-boot-to-a-dog-transportation-area.html?utm_source=rss: 83b1fb45f3018ccc338addc19b250347229fffd9
seen https://www.bentasker.co.uk/posts/blog/house-stuff/converting-a-zafiras-boot-to-a-dog-transportation-area.html?utm_source=rss
Found collection
Err, failed to submit https://en.wikipedia.org/wiki/Opel_Zafira
Err, failed to submit https://www.carmagazine.co.uk/car-news/industry-news/the-death-of-the-mpv/
Err, failed to submit https://www.forcesnews.com/technology/black-nasty-what-do-you-use-it
https://www.bentasker.co.uk/posts/documentation/kubernetes/deploying-imaginary-onto-kubernetes-for-thumbnailing.html?utm_source=rss: 5df74221665bcf35c52ebf6931276aba17be5425
Reached last seen entry
[{'feed_url': 'https://www.bentasker.co.uk/rss.xml', 'stats': {'entries': 1, 'links': 3, 'duplicates': 0, 'failed_submissions': 4, 'runtime': 718037657}, 'mean_submission_time': 32296097.0}]
Successfully submitted stats
I deleted the hash and re-ran whilst running a packet capture to see the full response
POST /api/v1/links HTTP/1.1
Host: linkwarden.linkwarden.svc.cluster.local:8085
User-Agent: python-requests/2.32.3
Accept-Encoding: gzip, deflate
Accept: */*
Connection: keep-alive
Authorization: Bearer <redacted>
Content-Length: 494
Content-Type: application/json
{"name": "", "url": "https://www.bentasker.co.uk/posts/blog/house-stuff/converting-a-zafiras-boot-to-a-dog-transportation-area.html?utm_source=rss", "description": "", "type": "url", "tags": [{"name": "SiteLinks"}, {"name": "anti-link-rot"}, {"name": "blog"}, {"name": "cars"}, {"name": "dogs"}, {"name": "house stuff"}, {"name": "vehicles"}], "preview": "", "image": "", "pdf": "", "readable": "", "monolith": "", "textContent": "", "collection": {"id": 2, "name": "Site Links", "ownerId": 1}}HTTP/1.1 400 Bad Request
content-type: application/json; charset=utf-8
etag: "bbff35ts2n2e"
content-length: 86
vary: Accept-Encoding
date: Sat, 19 Apr 2025 07:29:18 GMT
connection: close
{"response":"Error: Invalid enum value. Expected 'jpeg' | 'png', received '' [image]"}
It looks like it's now not happy with image
being empty.
Activity
19-Apr-25 07:33
assigned to @btasker
19-Apr-25 07:34
The linkwarden image is
ghcr.io/linkwarden/linkwarden:v2.9.3
There's been a release since then 2.10.0. I don't see any obvious mentions of this in the commit history between releases, but some of the commit messages are literally "wip" and "bug fixed" so who knows.
I'm going to upgrade to that and then check that it still repros.
19-Apr-25 07:40
mentioned in commit sysconfigs/bumblebee-kubernetes-charts@d5975135c844cc02cc07248a1f6185a1b3935349
Message
chore: upgrade linkwarden for utilities/auto-blog-link-preserver#22
19-Apr-25 07:52
Yup, same deal
I think this commit is where the change came.
Which makes sense, tags show that it was introduced in 2.9.0 and
git log
shows that I previously updated from2.7.1
to2.9.3
The API docs appear to have been updated, but no longer mention the
image
attribute.So, for reference, the docs currently say that we only need the following:
19-Apr-25 07:54
mentioned in commit b8921be4a2a37cd65d0ce70a5ddfb4220ecc15f4
Message
fix: remove unneeded attributes from link submit (utilities/auto-blog-link-preserver#22)
From v2.9.0 onwards, Linkwarden will reject requests which contain these with empty values.
19-Apr-25 08:00
mentioned in commit sysconfigs/bumblebee-kubernetes-charts@dfa228ebf6004c874dc6d80d471a835a841baff6
Message
chore: upgrade image used for cronjob - need the bugfix in utilities/auto-blog-link-preserver#22