xxx.xxx.xxx.xxx - - [08/Jul/2024:21:13:39 +1000] "GET /api/v2/search?q=https:%2F%2Foutside.ofa.dog%2Fuser%2Ffutzle%2Freview%2F18717%2F&resolve=true&limit=11 HTTP/2.0" 500 925 "https://old.mermaid.town/deck/getting-started" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:127.0) Gecko/20100101 Firefox/127.0"
Which leaves me to believe that the status is being fetched properly from Bookwyrm (200), but Hometown is failing to process it (500).
Specifications
Hometown 1.1.1 4.2.10. Hometown 1.1.1 4.0.6 seems ok and does fetch the review (but only sometimes! wtf?). History on my instance (old.mermaid.town) suggests this has been happening since 4.0.11 (but I can't test that). Four different Hometown admins tested this.
Bookwyrm 0.6.3 and 0.7.1. Two different Bookwyrm admins tested this.
Mainline Mastodon 4.2.10 always fetches the status successfully. Two different Mastodon sites tested this.
Steps to reproduce the problem
Expected behaviour
Review should have been fetched from Bookwyrm instance to Hometown instance and displayed to user
Actual behaviour
500 error in Hometown nginx log, review is not displayed in UI.
Detailed description
If I search this URL:
from the Hometown UI, I see this in the Bookwyrm log:
and this in the Hometown log:
Which leaves me to believe that the status is being fetched properly from Bookwyrm (200), but Hometown is failing to process it (500).
Specifications
Hometown 1.1.1 4.2.10. Hometown 1.1.1 4.0.6 seems ok and does fetch the review (but only sometimes! wtf?). History on my instance (old.mermaid.town) suggests this has been happening since 4.0.11 (but I can't test that). Four different Hometown admins tested this.
Bookwyrm 0.6.3 and 0.7.1. Two different Bookwyrm admins tested this.
Mainline Mastodon 4.2.10 always fetches the status successfully. Two different Mastodon sites tested this.