Vitor

It seems like this is a known issue that's not going to be corrected. See MicrosoftDocs/azure-docs#38427. As an alternative, I made a provider that assumes no OpenID Connect support. E.g....

I have the same issue. You can see what's going on by taking a look at postgres' logs: ``` nix launchd.user.agents.postgresql.serviceConfig = { StandardErrorPath = "/Users/vitor/postgres.error.log"; StandardOutPath = "/Users/vitor/postgres.log"; };...

I'd suggest keeping the issue open. We solved it but the default behavior is broken.

For reference, which are these "Good Parts", @shicks?

Just had this exact same issue. I commented everything I was adding to `$PATH` and managed to go through with the installation. No idea what was actually breaking it.

In case someone finds this useful, I ended up doing: ```elisp (defun vsp/emmet-expand () (let ((bounds (bounds-of-thing-at-point 'symbol))) (list (car bounds) (cdr bounds) (lambda (str pred action) (emmet-transform str)) :exclusive...

For anyone, like myself, who stumbles on this issue, you can do this: ``` sh nix-shell -p "ruby_3_0" -p "bundix" --run "bundle lock && bundix --ruby=ruby_3_0" ```