Unable to render plantuml previews with picoweb - "Error: 302 Found" with v2.18.0

[alyandon]

I use a local plantuml picoweb instance and have the extension configured to use that and I'm unable to render plantuml previews in VSCode with v.2.18.0 of the extension as it appears to consider anything other than a 200 response as an error. Version 2.17.6 works for me.

Error: 302 Found

GET http://localhost:8080/map/0/...
at ClientRequest.closeCallback (/Users/[REMOVED_FOR_PRIVACY]/.vscode/extensions/jebbs.plantuml-2.18.0/out/src/plantuml/renders/httpWrapper.js:78:27)
at ClientRequest.emit (node:events:514:28)
at ClientRequest.emit (node:domain:489:12)
at Socket.socketCloseListener (node:_http_client:464:9)
at Socket.emit (node:events:526:35)
at Socket.emit (node:domain:489:12)
at TCP. (node:net:323:12)

[rolfmadsen]

Same experience and error message.

Works fine with 2.17.6 using Dot version: dot - graphviz version 2.43.0 (0) and plantuml-gplv2-1.2024.3.

[Zamotic]

Can confirm, I am experiencing the same issue. Downgrading the extension to 2.17.6 resolved the issue for me.

[mawid6]

Same issue here. I was about to blame IT that they are messing with the port security of the machine, but then I checked and pico is running fine.

How do I downgrade btw?
Nevermind, just right click in the UI/extension list sidebar and select "install another version..."
Now its working fine again. Will upgrade when there is a fix.

So to clarify:

• Downgrading to 2.17.6 works. No change to plantuml needed.
• "Local" generation in the extension works in both new and old versions.
  (Plantuml also naturally works locally, plantuml CLI and plantuml UI)
• Plantuml has not been changed/updated. I am running December version of plantuml, 1.2023.12. Works fine with extension version 2.17.6.

(Using external public servers is not an option for me.)

[NenadSteric]

can confirm the issue with a local plantuml server (plantuml-1.2024.3 and plantuml-1.2024.4)
(if you change to plantuml.com as the server it works also with the latest version)
and the workaround by downgrading to 2.17.6

[Zamotic]

Can confirm that upgrading to 2.18.1 resolved the issue. Thanks!