You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think that since the hooks were changed to use flatpak-builder-lint for doing the build validation, /build/:id/check/:check/job endpoints became completely broken.
~/d/f/flat-manager master• [1] https -x -A bearer -a $flattoken hub.flathub.org/api/v1/build/57602/check/flathub-hooks/job Content-Type:application/json
HTTP/1.1 400 Bad Request
Connection: keep-alive
Content-Length: 68
Content-Type: text/plain; charset=utf-8
Date: Sun, 22 Oct 2023 21:05:19 GMT
Server: nginx/1.18.0 (Ubuntu)
Json deserialize error: EOF while parsing a value at line 1 column 0
f-b-l returns errors, if any, as JSON. I suspect the nested JSON confuses flat-manager, as it somehow works for /extended, but is double escaped:
get_check_job takes a JSON argument for the log offset (which is wrong for a GET request, but that's what the other job endpoint does...). Is that the issue?
I think that since the hooks were changed to use flatpak-builder-lint for doing the build validation,
/build/:id/check/:check/job
endpoints became completely broken.f-b-l returns errors, if any, as JSON. I suspect the nested JSON confuses flat-manager, as it somehow works for
/extended
, but is double escaped:The text was updated successfully, but these errors were encountered: