35 karma · joined April 19, 2023
We also want homogeneity in tech when possible (we already heavily use kubernetes, we don't want to keep docker hosts anymore).
Teams of testers need to be accounted in terms of resource quotas and RBAC.
What exactly do you see as an overkill in wanting to run short-lived containers in kubernetes rather than in docker (if we already have kubernetes and "cook" it ourselves)?
Looks like just a fzf that is able to traverse across branches, but it is not obvious which branch the selected file is in until you switch to it.
I think it would be best to illustrate the readme with a problem it tries to solve: currently I don't understand why a simple set of INSERT operations wouldn't suffice.
Also, the phrase "ingest data into Postgres" sounds wrong: it would be postgres, not your tool that would ingest data (if it could), your tool should be described as the one "putting data into Postgres". And thus you probably have named your tool wrong...
How to do that?
Or did it just have to perform a non-cached search and thus not only excluded said domains, but could also reorder the other results based on the current relevance, rather than cached relevance from the past that is being served to everyone else who doesn't exclude said domains?
I hope they go broke, but they already aren't relevant anymore.
Then it stopped being extensible at first, then the management went "woke" with all LGBTC++ inclusiveness and other CoC bullshit, fired/made go lots of good core developers and then it all went to shit in accelerated mode.