Gerrit Kieffer

For me this happened after I updated tmux recently. I solved it by updating `tmux-fzf` via `tpm` (`prefix` + U (uppercase!))

I think we're hitting the same issue. Any ideas on what exact limit is hit, causing the request to fail? I was first thinking about the parameter count, but prisma...

So I've logged one of the "offending" queries in our case, which resulted in a ~1.2MB sql file. I then manually executed it on our postgresql server. It took a...

Sorry, forgot about this issue and didn't post my latest update here. We stumbled upon [this discussion](https://github.com/prisma/prisma/discussions/8840) and [this issue](https://github.com/prisma/prisma/issues/6693), which seemed related. In our case, I got thrown off...

Same here, trying to use the Azure CLI task in combination with a service connection that uses a managed identity on subscription level. I've set up the service connection as...

First of all thanks for all the effort in making this an even better plugin! One suggestion I would like to propose: autosuggested scopes based on git history. Background/details: Our...

@lppedd thanks for the swift reply! > This is similar to what I already do with the subject token. Yes, exactly that, but for scopes. Totally forgot about checking the...

According to #126 this service shouldn't even be created by the chart in the first place. Additionally there already was a PR with a lot of discussion on that, but...

Wow okay, I would _not_ have expected that. Thanks for the detailed response! This definitely explains the behavior I was experiencing. I still think that it's quite counterintuitive to have...

Might be related to the gitlab agent after all, see [gitlab-agent/issues/255](https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent/-/issues/255). I'll keep an eye on that and close this issue here if they are able to fix it there.