Repository navigation
Unable to stop a build using the Python SDK #343
Description
When using the python SDK (but it looks like its not limited to the Python SDK alone), the stop build functionality no longer works as expected. When comparing the calls between what frontend sends and what the SDK sends, I noticed following difference:
UI:
Sends a PATCH call to /builds with body: {"isRunning":false}
SDK:
Sends a PATCH call to /builds with body: {}
The SDK call seems to work with older versions, but it looks like the {"isRunning":false} is now required?
Notes:
I noticed the Python SDK is outdated, but looking at other SDK's at least some other more up-to-date SDK's seem to do the same.
Activity
mokhtardziri commentedon Aug 14, 2026
I opened a PR in the Python SDK repository for this issue : Visual-Regression-Tracker/sdk-python#37
fix: send isRunning=false in stop()
fix(builds): stop build on PATCH with empty or missing body (#410)
pashidlos commentedon Oct 24, 2026
Fixed in #410.
Root cause: all released SDKs (sdk-js / agent-cypress, sdk-python, sdk-java) stop a build with
PATCH /builds/:idand an empty body. The NestJS 11 / Express 5 upgrade (#336, api 5.1.0) dropped the fallback that treated an empty body asisRunning: false, so{}became a no-op and a missing body returned 500. #410 restores it, so existing SDK versions can stop builds again once you run the next api release.The SDKs now also send
isRunning: falseexplicitly: sdk-python in Visual-Regression-Tracker/sdk-python#40 (merged), sdk-js in Visual-Regression-Tracker/sdk-js#345, sdk-java in Visual-Regression-Tracker/sdk-java#118.