David Rio

@AkaFletch , @mlr3000, are you running your merge statement in a transaction? If you don't, you won't see any changes in your db. I don't think that is a bug.

@jasonlyu123 > Finally got neovim to work for me. Do you mind sharing your neovim config? I have almost everything working but I can't get `` to do proper highlighting.

> @drio can we help with completing this? Just had an issue with a user requesting beta access to tags because the readme says it is still in beta... 😢...

Thank you for the reply @greenpau. > I am not sure what you mean by separate keys. When I look at the metadata (xml file) that I use to configure...

@billksun I ended up bulding my [own thing](https://github.com/drio/caddy-saml-sso).

@jmcdon03 Tailscaled has [already logic](https://github.com/tailscale/tailscale/blob/main/ipn/ipnlocal/cert.go#L112) to "cache/store" the certs and only renew them when necessary. The certs are cached locally. In your context, you are starting a whole new machine...

@jace-ys I was able to reproduce this locally. The problem is that the acme library [starts a 168hours](https://github.com/tailscale/golang-x-crypto/blob/main/acme/http.go#L43) timer to try again the request. Tailscaled never gets an answer and...

To recap: The `tailscale` client makes a request to `tailscaled` and `tailscaled` uses the [golang-x-crypto](https://github.com/tailscale/golang-x-crypto) lib to make a request to get the cert. If it gets a rate limit...

@DentonGentry Do you mind giving us some guidance when you have a chance?

To sum up were are with this: Be aware `tailscale cert` won't timeout when hitting [rate limits](https://letsencrypt.org/docs/rate-limits/) against letsencrypt. In your scripts, make sure you wrap `tailscale cert` with [`timeout`](https://www.gnu.org/software/coreutils/manual/html_node/timeout-invocation.html#timeout-invocation)....