Imaginary request produce HTTP 400 error code

[jsalort]

Describe the bug

Preview generation with imaginary used to work fine for me. I understand that is it not recommanded because it may have bugs with GIF and HEIC. But, on my RPi setup, imagemagick does not have support for HEIC at all. So I configured Preview to use a remote Imaginary instance instead, and it used to work fine.

Now, the requests produce a HTTP 400 error code on the Imaginary instance, and I haven't been able to figure out how to debug this problem. So I don't know if it is a bug in Preview/Memory, a misconfiguration on the Imaginary instance, or an edge case because of a broken file...

Here is an example of the requests on the Imaginary instance:

imaginary_1  | 192.168.112.1 - - [23/Dec/2024 08:50:33] "POST /pipeline?operations=%5B%7B%22operation%22%3A%22fit%22%2C%22params%22%3A%7B%22width%22%3A2048%2C%22height%22%3A2048%2C%22stripmeta%22%3A%22true%22%2C%22type%22%3A%22jpeg%22%2C%22norotation%22%3A%22true%22%2C%22quality%22%3A%2260%22%7D%7D%5D&key=**REDACTED*** HTTP/1.1" 400 168 0.2713

My understanding is that code 400 means malformed request. Did anything change in recent versions of Memories?
This used to work like a charm a few weeks ago.

Thanks,

Steps To Reproduce

No response

Platform

- Browser: Safari and Firefox
- Memories Version: 7.4.1
- Nextcloud Version: 30.0.4
- PHP Version: 8.2

Screenshots

No response

Additional context

• Any errors in the JS console?

Yes:

Failed to load XImg Error fetching single preview: {"message":"No provider successfully handled the preview generation"} 3 [XImg.vue:95](webpack:///memories/components/frame/XImg.vue)
    loadImage XImg.vue:95
    mounted XImg.vue:50
    VueJS 19
    processDays Timeline.vue:873
    fetchDays Timeline.vue:774
    createState Timeline.vue:370
    refresh Timeline.vue:394
    routeChange Timeline.vue:300
    mounted Timeline.vue:212
    VueJS 11

• Any errors in the Nextcloud server logs?
  No

[jsalort]

Addition: I have checked that this is not a bug introduced by newer versions of imaginary. I downgraded imaginary to the container of several weeks ago, and the error is the same.
It seems that the URL is somehow malformed now. I did update NC and Memories in the meantime. So, possibly something was changed?

[pulsejet]

Memories does not deal with preview generation at all, so this would be an upstream bug (nextcloud/server)

[jsalort]

Memories does not deal with preview generation at all, so this would be an upstream bug (nextcloud/server)

Ok. Thanks for you reply. I was confused because the only GUI that allows to switch Imaginary ON/OFF is actually the Memories administration pane.
I have opened a ticket upstream.
nextcloud/server#49963