Unable to avoid registry refresh issue on first start

[baco]

I have the following configuration:

local pylsp = require("mason-registry").get_package("python-lsp-server")
pylsp:on("install:success", function()
  local mason_package_path = function(package)
    local path = vim.fn.resolve(vim.fn.stdpath("data") .. "/mason/packages/" .. package)
    return path
  end

  local path = mason_package_path("python-lsp-server")
  local command = path .. "/venv/bin/python"
...
end)

The idea is that I use command to run pip with it and install non-standard plugins for the package python-lsp-server. I've got that recipe from #908

That works well, except in combination with mason-lspconfig + ensured_installed the first time Neovim is run with that configuration, raising the following error:

Error in /home/baco/src/dotfiles_vendor/nvim/init.vim[49]../home/baco/src/dotfiles_vendor/nvim/lua/lsp/init.lua:
E5113: Lua chunk: ...te/pack/lsp/start/mason.nvim/lua/mason-registry/init.lua:32: Cannot find package "python-lsp-server".

The error goes away in the next launch or if I previously run something like nvim --headless +"MasonUpdate" +"qall", prior to launching Neovim the first time.

The thing is I'd like to provide a cleaner experience when using my config files, and not needing to ask the user to manually run MasonUpdate or to wait a second launch for error to go away.

Any ideas on how could I achieve that? I've read something, here in this forum (#1133 (comment)), like calling require("mason-registry").refresh() inside of my configs, but I couldn't get it to work.

[ZingyAwesome]

I think the issue is #1645.
As suggested by one of the comments there, I was able to work around this by adding require("mason").setup() before doing any mason-registry operations.
This is not a perfect workaround as it can lead to you doing a duplicate call to setup if you have a setup call to mason elsewhere. And doing so prevents you from entering the mason UI with the error "ambiguous use of user-defined command" when executing :Mason, but the other mason commands seem to work fine. This workaround was acceptable to me since the duplicate setup call only occurs during the first nvim initialisation and never again with my config.