The following minimal config

require 'visimp' {
  lsp = {
    nulls = {
      'code_actions.gitsigns'
    }
  }
}

throws this error on startup when opening/creating most files with visimp:

[null-ls] failed to start null-ls client with config: {
  cmd = <function 1>,
  filetypes = {},
  flags = {
    debounce_text_changes = 250
  },
  name = "null-ls",
  on_attach = <function 2>,
  on_exit = <function 3>,
  on_init = <function 4>,
  root_dir = "/home/foxy"
}

Actually, none-ls starts anyway. Perhaps we are accidentally trying to start it twice?

Other null-ls sources also have the same problem. This is not an upstream problem, because the corresponding config for LazyVim works. Our null-ls logic in the lsp layer must have something off.