Fix avert error that comes up when there is a swap file

[jam1015]

The change is in `lua/flatten/core.lua

I find that without using pcall here, if from the terminal inside of neovim, if you open multiple files at once and a swap file is found in one of them, and you cycle through buffers and return to the terminal, you get error messages.

Error detected while processing BufEnter Autocommands for "*":                                                                    
    
Error executing lua callback: Vim:Error invoking 'nvim_exec_lua' on channel 3:                                                    
    
Error executing lua: ....local/share/nvim/lazy/flatten.nvim/lua/flatten/core.lua:327: Vim:E325: ATTENTION                         
    
stack traceback:                                                                                                                  
    
        [C]: in function 'nvim_set_current_buf'                                                                                   
    
        ....local/share/nvim/lazy/flatten.nvim/lua/flatten/core.lua:327: in function <....local/share/nvim/lazy/flatten.nvim/lua/f
latt
en/core.lua:137>                                                                                                                  
    
stack traceback:                                                                                                                  
    
        [C]: in function 'req'                                                                                                    
    
        .../.local/share/nvim/lazy/flatten.nvim/lua/flatten/rpc.lua:36: in function 'exec_on_host'                                
    
        ...local/share/nvim/lazy/flatten.nvim/lua/flatten/guest.lua:64: in function 'send_files'                                  
    
        ...local/share/nvim/lazy/flatten.nvim/lua/flatten/guest.lua:202: in function <...local/share/nvim/lazy/flatten.nvim/lua/fl
atte
n/guest.lua:127>                                                                                                                  

The other changes seem to be part of the CI process that you have in this repo.

[willothy]

Thanks for the PR! I'll try this out today.

Do you have a script that can reproduce the issue programmatically? I used to encounter this but haven't in a long time so I figured it was fixed.