error on performing goto_definition which jumps to an empty file

Describe the bug

jumping to a file generates a highlight (beacon) on the
first line... when the file or first line is empty, the beacon width
probably gets weirded out and produces an error

Error executing vim.schedule lua callback: ...83/.local/share/nvim/lazy/lspsaga/lua/lspsaga/window.lua:157: 'width' key must be a positive Integer
stack traceback:
        [C]: in function 'nvim_open_win'
        ...83/.local/share/nvim/lazy/lspsaga/lua/lspsaga/window.lua:157: in function 'new_float'
        ...83/.local/share/nvim/lazy/lspsaga/lua/lspsaga/beacon.lua:29: in function 'beacon'
        ...local/share/nvim/lazy/lspsaga/lua/lspsaga/definition.lua:323: in function 'handler'
        /usr/share/nvim/runtime/lua/vim/lsp/client.lua:682: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>

Steps to reproduce

bug reproduced in dartls, bashls and luals

for this example, using luals -

• create an empty file (for a file where line 1 is empty)
• require the empty file from another file
• perform goto_definiton on the require statement
• error occurs (due to jumping to empty file)

video example:

Expected behavior

not error and empty width is handled

Neovim version (nvim -v)

0.11.5

lspsaga commit

branch main commit 8efe00d (from lazy.nvim)

Terminal name/version

windows-terminal 1.23.13503.0 (inside wsl2)

Reproduce the goto_definition case with an empty target file using the stated luals, dartls, or bashls setup. Start in lua/lspsaga/beacon.lua and lua/lspsaga/window.lua around the reported new_float call, then inspect lua/lspsaga/definition.lua; done means the jump no longer errors when the target line is empty and the beacon width is valid.