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
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:
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:
Tried using paas-uom.org:5001 as the planner instead and the planning attempt hangs with this:
Any idea what I am doing wrong?
The text was updated successfully, but these errors were encountered:
rpgoldman
changed the title
Using solver.planning.domains/solve from plugin gets 404 error
Using solver.planning.domains/solve from plugin gets 400 error; hangs against paas-uom.org
Apr 24, 2024
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:
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
usingAirport/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: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:
Tried using
paas-uom.org:5001
as the planner instead and the planning attempt hangs with this:Any idea what I am doing wrong?
The text was updated successfully, but these errors were encountered: