2024-04-09 23:15:21 2024-04-09T21:15:21.795312Z ERROR windmill_queue::jobs: job 018ec4b7-2443-6ae2-4971-8a8854098925 did not succeed: {"error":{"message":"ExitCode: 1, last log lines:\n.0.3 in /usr/local/lib/python3.11/site-packages (from playwright==1.42.0) (3.0.3)\nRequirement already satisfied: pyee==11.0.1 in /usr/local/lib/python3.11/site-packages (from playwright==1.42.0) (11.0.1)\nRequirement already satisfied: typing-extensions in /usr/local/lib/python3.11/site-packages (from pyee==11.0.1->playwright==1.42.0) (4.11.0)\nWARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv\nerror: unknown command 'install\r'","name":"ExecutionErr"}}2024-04-09 23:15:21 2024-04-09T21:15:21.795312Z ERROR windmill_queue::jobs: job 018ec4b7-2443-6ae2-4971-8a8854098925 did not succeed: {"error":{"message":"ExitCode: 1, last log lines:\n.0.3 in /usr/local/lib/python3.11/site-packages (from playwright==1.42.0) (3.0.3)\nRequirement already satisfied: pyee==11.0.1 in /usr/local/lib/python3.11/site-packages (from playwright==1.42.0) (11.0.1)\nRequirement already satisfied: typing-extensions in /usr/local/lib/python3.11/site-packages (from pyee==11.0.1->playwright==1.42.0) (4.11.0)\nWARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv\nerror: unknown command 'install\r'","name":"ExecutionErr"}}We lost the habit of putting everything here but we still have many great features that have been merged recently and a few very big ones coming soon. ⚠️ ⚠️ semi-breaking change in Postgres TIMESTAMP return However, want to take the opportunity to warn about a semi breaking change in the way our native Postgres runtime return TIMESTAMP . it used to be in this format: "2026-05-08 17:54:03.348891 UTC" . but they are have been standardized to (ISO 8601): "2026-05-08T17:54:03.348891+00:00" in recent releases. If you relied critically on the specific format, be advised you will need to adapt to this change. It was mistakenly in the UTC format prior which is non standard, not consistent with pg behavior and not even consistent with what format taken as input by our pg runtime as valid TIMESTAMP. Sorry about this, we realized a bit late that by doing a batch of runtime improvement on pg, it induced this change and it's now too late to revert or make fully back-compatible.
rubenf · 2w ago
We're live showcasing this week's work on https://discord.com/channels/930051556043276338/1278977038430240813 🙂
henri-c · 2mo ago
@everyone Launch Week — That's a wrap
Fratera · 2mo ago