Adam Vollrath

> Correct link: > > ``` > https://deployment-6716-ufzi-on-ufzi-cp-internal-x0vlpg.app.uffizzi.com/github.com/DbpUffizziTest/quickstart/pull/16 > ``` Thanks for noticing this. I've updated the `deprecate_set-output` branch. Use it for testing. https://github.com/UffizziCloud/preview-action/commit/58704a26979ac4f855262a777f612026c902d970 and #35

brief discussion https://uffizzi-internal.slack.com/archives/CN8MKSAQ5/p1654877496005399

If this is not crazy, I may have time to work on it later this year.

This is fine, just change `provider` to `node-selector` and change `gke` to `gvisor`. Don't bother with `vanilla`, just leave null as the default.

This may justify a `v3` version bump for the reusable workflow. Don't forget documentation! Examples will be critical to prepare the input value within end users' workflows.

I'm also seeing this kind of error. `socket.c setsockopt(20, IP_RECVTOS) failed: Protocol not available`

@kiselev-dv is working on this here https://github.com/EndPointCorp/lg_ros_nodes/tree/sv_persist_browsers

This is now deployed to the client system that was using the most Maps API calls. It seems to work fine, and the number of API calls has drastically diminished....

I think this ticket can be closed.

@mvollrath can the existing ad-hoc browser node handle the browser bits? Or does this deserve a new node to launch the browser?