atoo•9mo ago

VS code extension returns an error when pushing changes

I have a little issue when trying to use the Windmill extension on VS Code. When I pull, everything works fine. I modify a script, but when I use the command wmill sync push, I get the following error:

Server failed. Unprocessable Entity: Failed to deserialize the JSON body into the target type: lock: invalid type: string "certifi==2024.2.2\ncharset-normalizer==3.3.2\nidna==3.6\nrequests==2.31.0\nurllib3==2.2.1", expected a sequence at line 1 column 1816
Error details of: Generic Error
{
    "url": "https://windmill.xxxxxx.fr/api/w/integrations/scripts/create",
    "status": 422,
    "statusText": "Unprocessable Entity",
    "body": "Failed to deserialize the JSON body into the target type: lock: invalid type: string \"certifi==2024.2.2\\ncharset-normalizer==3.3.2\\nidna==3.6\\nrequests==2.31.0\\nurllib3==2.2.1\", expected a sequence at line 1 column 1816",
    "request": {
        "method": "POST",
        "url": "/w/{workspace}/scripts/create",
        "path": {
            "workspace": "integrations"
...

Server failed. Unprocessable Entity: Failed to deserialize the JSON body into the target type: lock: invalid type: string "certifi==2024.2.2\ncharset-normalizer==3.3.2\nidna==3.6\nrequests==2.31.0\nurllib3==2.2.1", expected a sequence at line 1 column 1816
Error details of: Generic Error
{
    "url": "https://windmill.xxxxxx.fr/api/w/integrations/scripts/create",
    "status": 422,
    "statusText": "Unprocessable Entity",
    "body": "Failed to deserialize the JSON body into the target type: lock: invalid type: string \"certifi==2024.2.2\\ncharset-normalizer==3.3.2\\nidna==3.6\\nrequests==2.31.0\\nurllib3==2.2.1\", expected a sequence at line 1 column 1816",
    "request": {
        "method": "POST",
        "url": "/w/{workspace}/scripts/create",
        "path": {
            "workspace": "integrations"
...

I get this error even when trying to simply add a variable like index=1 in a Python script. I've searched on Discord but didn't see anyone with the same issue. Any idea where this might be coming from? Thanks!

2 Replies

rubenf•9mo ago

would recommend updating backend to latest and try again

atooOP•9mo ago

will try, thanks