search

jan-dolejsi / vscode-pddl

Planning Domain Description Language (PDDL) grammar, syntax highlighting, code snippets, parser and planner integration for Visual Studio Code.
MIT License
84 stars 22 forks source link

Using solver.planning.domains/solve from plugin gets 400 error; hangs against paas-uom.org #182

Open rpgoldman opened 4 months ago

rpgoldman commented 4 months ago

I was learning the VS Code plugin, so I downloaded the vscode-pddl-samples and per the instructions tried to generate a plan for Airport/1plane.pddl using Airport/domain.pddl. I expected the planning to fail, since there's an intentionally-introduced error in that file. But instead of failing, I get a 400 error from the solver.planning.domains server:

image

I uploaded those files interactively to the planning editor at planning.domains, and tried to generate a plan using LAMA. Planning failed, as expected, but there was no error.

Here's my configuration:

image

Tried using paas-uom.org:5001 as the planner instead and the planning attempt hangs with this:

image

Any idea what I am doing wrong?

haz commented 4 months ago

The plugin needs to be updated for the modern era solver.planning.domains (uses PaasS now). You can add a new planning engine, select the planning-as-a-service option, and configure like so:

image

@jan-dolejsi : ya still with us, bud?

wikssss commented 1 month ago

I had a similar issue and haz's recommendation fixed things for a while but now when I've configured planning as a service as: https://solver.planning.domains:5001/package and the extension is stuck loading here: image. Please could you help :) @jan-dolejsi

jan-dolejsi commented 1 month ago

I need bit more info, @wikssss Just tested using the currently published version of the extension and all seems to work.

Can you try the following?

  1. Test using the out-of-the-box planner configuration (the last one in the list): image

  2. Please invoke the VS Code command Preferences: Open User Settings (JSON), find the "pddl.planners": [...] section and paste the content here (especially the entry related to the Planning-as-a-service entry). It should look like this:

        {
            "kind": "PLANNING_AS_A_SERVICE",
            "url": "https://solver.planning.domains:5001/package",
            "title": "https://solver.planning.domains:5001/package",
            "canConfigure": true
        }

  1. In VS Code invoke the Developer: Toggle Developer Tools command and look for an error in the Console tab that could be related to the planner HTTP call or related...

  2. You should also see a valid JSON response if you put the https://solver.planning.domains:5001/package address directly to your browser.

Thx. Jan