Constantine Peresypkin

It was true by default not a long time ago.

You can add try/catch to untrusted code. I suspect that await runs amok after exception ```js const untrusted = ` (async function execute() { try { ${untrustedSource} } catch (e)...

Doesn't work too, healthcheck just continues to run and spam logs with: ``` db_1 | 2023-08-18 20:24:37.733 UTC [362/1] [[unknown]:[unknown]] LOG: connection received: host=127.0.0.1 port=45668 db_1 | 2023-08-18 20:24:37.734 UTC...

Ok, solution for somebody who needs healthcheck for dependencies only: ```yaml tmpfs: - /run healthcheck: test: [ "CMD-SHELL", "[ -r /var/run/postgresql/ready ] || ( pg_isready && touch /var/run/postgresql/ready)" ] ```...

Just FYI, for people who are stuck in 2001. `access-control-allow-origin: *` in 2023 doesn't really work. As most browsers will expect a real Origin mapping there for secure credentials. So,...

@Acidherr > [#234 (comment)](https://github.com/yaml/pyyaml/issues/234#issuecomment-765894586) > > This worked for me. It is quite easy to implement also. What in the words `indent=4` is so hard to understand? No it doesn't...

For people getting here, just add to spec: ```python a = Analysis([....], binaries=[('/usr/local/lib/libcrypt.so.2', '.')], ..., ) ```

@bwoodsend I suppose you haven't read the thread? TL;DR libpython doesn't really use libcrypt, it's a bogus dependency that [will be completely removed in 3.11/3.12 ](https://bugs.python.org/issue45433)

@andreicristianpetcu @devsnek there is no case for async source map consumer other than problems of specific ill-thought implementation by Mozilla. Like: await in stack trace handler? Are they nuts?

Oh, god, finally somebody with a common sense