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
The task here can be a str sometimes, which causes a ValueError. I think it needs to be wrapped into AsyncResult here.
Bug 2:
return {"solve": solve.packages}
There's no .packages in Solve anymore. This was introduced when the DB schema was refactored, way before I was even part of the project. The new proper name is package_builds.
Expected behavior
The endpoint returns some data instead of raising an error.
How to Reproduce the problem?
Just call the endpoint. Some tests call it as well, which is how I noticed, but maybe those tests expect status codes 500 or 400, so they all pass. Those tests need to be looked at.
Describe the bug
The
api_get_specification
HTTP endpoint seems to be completely broken. There are two bugs here:Bug 1:
The task here can be a
str
sometimes, which causes aValueError
. I think it needs to be wrapped intoAsyncResult
here.Bug 2:
There's no
.packages
inSolve
anymore. This was introduced when the DB schema was refactored, way before I was even part of the project. The new proper name ispackage_builds
.Expected behavior
The endpoint
return
s some data instead of raising an error.How to Reproduce the problem?
Just call the endpoint. Some tests call it as well, which is how I noticed, but maybe those tests expect status codes 500 or 400, so they all pass. Those tests need to be looked at.
Output
This is printed to the terminal:
Versions and dependencies used.
Current main (988445b).
Anything else?
No response
The text was updated successfully, but these errors were encountered: