Go to file
Dominik Csapak d3dd84ee70 fix generating 'extjs' response with exceptions/blessed errors
when an api call with the 'extjs' formatter fails, the intention is that
the api call succeeds but contains the error in the inner structure
('error'/'status' property). When the api call fails with a raised
exception (e.g. PVE::APIClient::Exception), the '$res->{message}' field
is an object instead of a string.

Currently we directly assign the message to the resulting struct, which
we then try to convert to json. Since the message was an object,
`to_json` fails with 'encountered object` and the whole api call returns
a 501 error (since `handle_api2_request` returns that by default if
anything dies there, which is IMHO not correct but a different issue.)

By 'stringifying' the message, we avoid the error in `to_json` and the
api call can succeed.

partially fixes #6051: It improves the error message in PDM when trying
to remote migrate and the source cannot correctly resolve the target
remote. (We use PVE::APIClient there to query the remote).

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
2025-01-24 09:38:34 +01:00
debian bump version to 5.1.2 2024-10-04 14:03:00 +02:00
src fix generating 'extjs' response with exceptions/blessed errors 2025-01-24 09:38:34 +01:00
.gitignore fixup no newline at end of .gitignore 2018-05-25 16:42:05 +02:00
Makefile fixup! buildsys: add sbuild target for convenience 2023-05-17 07:31:38 +02:00