Yeah I agree, this seems like a pretty critical feature to the Aurora product itself. We saw a similar behavior recently where we had a connection pooler in between which indicates something wrong with how they propagate DNS changes during the failover. wtf aws

Whenever we have to do any type of AWS Aurora or RDS cluster modification in prod we always have the entire emergency response crew standing by right outside the door.

Their docs are not good and things frequently don't behave how you expect them to.

Oh, well, it’s always DNS!

Yeah, this setup is both nice and insane. If you don't need much extra customization it's great. But I have a setup where I needed both postBuild and postRenderer's + actual kustomization layering and it was awful trying to figure out the order of execution to get the right final output.

In hindsight it would have been much faster to write the resources myself.

Love ambitious projects like this!

I wonder why the Unix standard doesn't start dropping old syscalls and standards? Does it have to be strictly backwards compatible?

Even if the standard dropped them, Linux would likely retain them.

https://linuxreviews.org/WE_DO_NOT_BREAK_USERSPACE

This has a similar flavor to xata.io's SimplyBlock based storage system * https://xata.io/blog/xata-postgres-with-data-branching-and-p... * https://www.simplyblock.io/

It's a great way to mix copy on write and effectively logical splitting of physical nodes. It's something I've wanted to build at a previous role.

Yeah this has been my experience as well. The Claude Code UI is still so much better, and the permissioning policy system is much better. Though I'm working on closing that gap by writing a custom policy https://github.com/openai/codex/blob/main/codex-rs/execpolic...

Kinda sick of Codex asking for approval to run tests for each test instance

Ah the tension between cybersecurity best practices and productivity is brutal right now.

lol yeah, but mostly just want to allow more types of reads for getting context, and primarily for test running / linting etc. I shouldn't have to approve every invocation of `pytest` or `bazel test`.

--dangerously-bypass-approvals-and-sandbox isn't enough for you?

I don't want unlimited writes. I basically want to unlock nearly everything but approve writes in some scenarios.

Where do unix permissions and a different user and extended attributes fall short for that?

You don't have to use Codex in its terminal UI - e.g. you can use it in the Zed IDE out-the-box:

https://zed.dev/blog/codex-is-live-in-zed

And also in emacs or neovim

https://xenodium.com/introducing-acpel

It's both context and memory. If an LLM could keep the entire git history in memory, and each of those git commits had enough context, it could take a new feature and understand the context in which it should live by looking up the history of the feature area in it's memory.

Yeah, this is absolutely true. It can be configured to do anything, which means you really need to make sure you've configured everything correctly.

huh, I don't seem to have this enabled at all. My cd in fish only shows the current directory choices

These would be great for outdoor running to keep tabs on your pace, HR, time etc. Paired with the new airpods 3, you could be phone free and watch free.

The one downside to nix that I've found is that nix rebuilds with flakes are incredibly slow. I'm using determinate nix too on nixos and it's still sooo slow