![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/bf725965-aca1-4305-8cfa-45e19b60f636.png)
3·
11 months agoshow EXPLAIN
for the query, maybe also EXPLAIN (ANALYZE, BUFFERS)
with say LIMIT 1000
so that it finishes some day
show EXPLAIN
for the query, maybe also EXPLAIN (ANALYZE, BUFFERS)
with say LIMIT 1000
so that it finishes some day
I somehow feel like there’s an allergy of sort towards classes in general in JavaScript/TypeScript. Many projects I’ve worked on gravitate towards more functional/plain-old-objects sort of paradigm and it feels like classes are avoided just because they don’t feel like idiomatic JS.
A developer had force pushed changes to remove some secrets from the repo. Then another developer who had missed the part about the cleanup saw the errors during git push
and proceeded to just merge the changes. Cue absolutely fucked commit history where you had all commits twice with individual change commits sprinkled between both.
If the value is still passed as an environment variable in the end, it can be read via
/proc/:pid/environ
from another container or from the host if they are both using the same UID (or has--cap-add SYS_PTRACE
)