You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems like the neweset version breaks everything, all dependencies, options,everything.
Can you make a new branch associated to previous version before the breaking changes ??
It's so pain in the ass to re adjusting my configuration, like I dont have time.
Hey, I'm very sorry that everything broke, but it was for improvement and it was necessary, nothing will break again!
Could you send your keybind setup? I'm busy right now so I can't help much, but as soon as I can I'll take a look. Also thanks @8uff3r for helping there! :)
Hey, I'm very sorry that everything broke, but it was for improvement and it was necessary, nothing will break again!
Could you send your keybind setup? I'm busy right now so I can't help much, but as soon as I can I'll take a look. Also thanks @8uff3r for helping there! :)
It's okay for breaking changes, I like a new result preview, however it is better to make a stable release for the previous version that doesn't break, because I needed to search to the whole commit history just to make everything works as the previous one again.
I leave this comment here, just in case anyone else that want to revert to previous version.
This is latest commit that works 91badd46c60df6bd9800c809056af2d80d33da4c
Reacted by Alejandro, Simanga Khoza, jream, Shahbaz Siddiqui and pepe-cadena
Hey, I'm very sorry that everything broke, but it was for improvement and it was necessary, nothing will break again!
Could you send your keybind setup? I'm busy right now so I can't help much, but as soon as I can I'll take a look. Also thanks @8uff3r for helping there! :)
It's okay for breaking changes, I like a new result preview, however it is better to make a stable release for the previous version that doesn't break, because I needed to search to the whole commit history just to make everything works as the previous one again.
however it is better to make a stable release for the previous version that doesn't break, because I needed to search to the whole commit history just to make everything works as the previous one again.
In the repository there are tags and semantic releases that you can use in your plugin manager to rollback to the previous stable release :)
Now, that bug is a little weird, I'll definitely take a look at it as soon as I get home, thanks for reporting it and also for providing a commit in case someone wants to rollback that way, that is appreciated.
however it is better to make a stable release for the previous version that doesn't break, because I needed to search to the whole commit history just to make everything works as the previous one again.
In the repository there are tags and semantic releases that you can use in your plugin manager to rollback to the previous stable release :)
Now, that bug is a little weird, I'll definitely take a look at it as soon as I get home, thanks for reporting it and also for providing a commit in case someone wants to rollback that way, that is appreciated.
Oh, my bad, I didn't check the release tags, haha. Sorry for that
Hey @mesa123123, just noticed I had to modify the build.lua script to adopt some breaking changes in the luarocks.nvim plugin, could you please try again? Let's hope this one does the trick and my apologies for the inconveniences :)
Basically I've added paths to my package path so nvim knows where to look for my paths:
-- Package Path Upgrade------------ Rocks installed through luarocks.nvimpackage.path=package.path..";" ..plugin_path.."/luarocks.nvim/.rocks/share/lua/6.1/?.lua;"package.path=package.path..";" ..plugin_path.."/luarocks.nvim/.rocks/share/lua/5.1/?/?.lua;"-- Rocks installed through local luarockspackage.path=package.path..";" ..fn.expand("$HOME") .."/.luarocks/share/lua/5.1/?/init.lua;"package.path=package.path..";" ..fn.expand("$HOME") .."/.luarocks/share/lua/5.1/?.lua;"----------
And it seems to work now! Or at least my errors are all about treesitter!
19:49:02 msg_show e http.http Error executing lua callback: /usr/share/nvim/runtime/filetype.lua:24: Error executing lua: /usr/share/nvim/runtime/filetype.lua:25: BufNewFile Autocommands for "*"..FileType Autocommands for "http"..FileType Autocommands for "*": Vim(append):Error executing lua callback: /usr/share/nvim/runtime/lua/vim/treesitter/query.lua:259: query: invalid node type at position 229 for language http
stack traceback:
[C]: in function '_ts_parse_query'
/usr/share/nvim/runtime/lua/vim/treesitter/query.lua:259: in function 'get'
/usr/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:114: in function 'new'
/usr/share/nvim/runtime/lua/vim/treesitter.lua:61: in function '_create_parser'
/usr/share/nvim/runtime/lua/vim/treesitter.lua:131: in function 'get_parser'
/usr/share/nvim/runtime/lua/vim/treesitter.lua:460: in function 'start'
...m/lazy/nvim-treesitter/lua/nvim-treesitter/highlight.lua:20: in function 'attach'
...vim/lazy/nvim-treesitter/lua/nvim-treesitter/configs.lua:509: in function 'attach_module'
...vim/lazy/nvim-treesitter/lua/nvim-treesitter/configs.lua:532: in function 'reattach_module'
...vim/lazy/nvim-treesitter/lua/nvim-treesitter/configs.lua:133: in function <...vim/lazy/nvim-treesitter/lua/nvim-treesitter/configs.lua:132>
[C]: in function 'nvim_exec_autocmds'
...hare/nvim/lazy/lazy.nvim/lua/lazy/core/handler/event.lua:157: in function <...hare/nvim/lazy/lazy.nvim/lua/lazy/core/handler/event.lua:156>
[C]: in function 'xpcall'
.../.local/share/nvim/lazy/lazy.nvim/lua/lazy/core/util.lua:113: in function 'try'
...hare/nvim/lazy/lazy.nvim/lua/lazy/core/handler/event.lua:156: in function 'trigger'
...hare/nvim/lazy/lazy.nvim/lua/lazy/core/handler/event.lua:87: in function <...hare/nvim/lazy/lazy.nvim/lua/lazy/core/handler/event.lua:72>
[C]: in function 'nvim_cmd'
/usr/share/nvim/runtime/filetype.lua:25: in function </usr/share/nvim/runtime/filetype.lua:24>
[C]: in function 'nvim_buf_call'
/usr/share/nvim/runtime/filetype.lua:24: in function </usr/share/nvim/runtime/filetype.lua:10>
stack traceback:
[C]: in function 'nvim_cmd'
/usr/share/nvim/runtime/filetype.lua:25: in function </usr/share/nvim/runtime/filetype.lua:24>
[C]: in function 'nvim_buf_call'
/usr/share/nvim/runtime/filetype.lua:24: in function </usr/share/nvim/runtime/filetype.lua:10>
stack traceback:
[C]: in function 'nvim_buf_call'
/usr/share/nvim/runtime/filetype.lua:24: in function </usr/share/nvim/runtime/filetype.lua:10>
I arrive a little later, but I figure out a way to make it works on macOS using previous comments and advice.
(the config is based on Lazy.nvim)
{
"vhyrro/luarocks.nvim”,-- explicit tell Lazy the module name due to error on calling-- the module with the suffix ‘.nvim’; in this way Lazy will call < require “luarocks”.setup({}) >name="luarocks”,config=true
},
{
"rest-nvim/rest.nvim",
dependencies= { "luarocks" },
ft= { "http", "https" },
config=function(_, o)
require"rest-nvim".setup(o)
end
}
With this config all the build and installation is done correctly.
I seem to be getting an error as well. Not sure if it's related to this new release but sharing just in case. I am also stuck trying to get past it.
Here is the error message. It seems to be a tree-sitter parsing issue but cannot for the life of me get passed this.
Happens when running :Rest run while hilghighting the request line in a HTTP file.
[rest.nvim] ERROR: The tree-sitter node at the range [0:0 - 25] has a syntax error and cannot be parsed
Error executing Lua callback: .../share/nvim/lazy/rest.nvim/lua/rest-nvim/parser/init.lua:114: attempt to index local 'req_node' (a nil value)
stack traceback:
.../share/nvim/lazy/rest.nvim/lua/rest-nvim/parser/init.lua:114: in function 'traverse_request'
.../share/nvim/lazy/rest.nvim/lua/rest-nvim/parser/init.lua:432: in function 'parse'
...al/share/nvim/lazy/rest.nvim/lua/rest-nvim/functions.lua:61: in function 'exec'
...cal/share/nvim/lazy/rest.nvim/lua/rest-nvim/commands.lua:44: in function 'impl'
...cal/share/nvim/lazy/rest.nvim/lua/rest-nvim/commands.lua:182: in function <...cal/share/nvim/lazy/rest.nvim/lua/rest-nvim/commands.lua:165>
I seem to be getting an error as well. Not sure if it's related to this new release but sharing just in case. I am also stuck trying to get past it.
Here is the error message. It seems to be a tree-sitter parsing issue but cannot for the life of me get passed this. Happens when running :Rest run while hilghighting the request line in a HTTP file.
[rest.nvim] ERROR: The tree-sitter node at the range [0:0 - 25] has a syntax error and cannot be parsed
Error executing Lua callback: .../share/nvim/lazy/rest.nvim/lua/rest-nvim/parser/init.lua:114: attempt to index local 'req_node' (a nil value)
stack traceback:
.../share/nvim/lazy/rest.nvim/lua/rest-nvim/parser/init.lua:114: in function 'traverse_request'
.../share/nvim/lazy/rest.nvim/lua/rest-nvim/parser/init.lua:432: in function 'parse'
...al/share/nvim/lazy/rest.nvim/lua/rest-nvim/functions.lua:61: in function 'exec'
...cal/share/nvim/lazy/rest.nvim/lua/rest-nvim/commands.lua:44: in function 'impl'
...cal/share/nvim/lazy/rest.nvim/lua/rest-nvim/commands.lua:182: in function <...cal/share/nvim/lazy/rest.nvim/lua/rest-nvim/commands.lua:165>
I should say that I've also tried several other iterations of configs setup that have been suggested in this thread, all with the same result.
Check trailing spaces in your http file, delete them even in --{% and --%} lines if you're using script variables. I struggled with the same issue until I realized that removing trailing spaces solves many of the treesitter's errors. Same with JSONs, make sure they are well formatted too.
I seem to be getting an error as well. Not sure if it's related to this new release but sharing just in case. I am also stuck trying to get past it.
Here is the error message. It seems to be a tree-sitter parsing issue but cannot for the life of me get passed this. Happens when running :Rest run while hilghighting the request line in a HTTP file.
[rest.nvim] ERROR: The tree-sitter node at the range [0:0 - 25] has a syntax error and cannot be parsed
Error executing Lua callback: .../share/nvim/lazy/rest.nvim/lua/rest-nvim/parser/init.lua:114: attempt to index local 'req_node' (a nil value)
stack traceback:
.../share/nvim/lazy/rest.nvim/lua/rest-nvim/parser/init.lua:114: in function 'traverse_request'
.../share/nvim/lazy/rest.nvim/lua/rest-nvim/parser/init.lua:432: in function 'parse'
...al/share/nvim/lazy/rest.nvim/lua/rest-nvim/functions.lua:61: in function 'exec'
...cal/share/nvim/lazy/rest.nvim/lua/rest-nvim/commands.lua:44: in function 'impl'
...cal/share/nvim/lazy/rest.nvim/lua/rest-nvim/commands.lua:182: in function <...cal/share/nvim/lazy/rest.nvim/lua/rest-nvim/commands.lua:165>
I should say that I've also tried several other iterations of configs setup that have been suggested in this thread, all with the same result.
Check trailing spaces in your http file, delete them even in --{% and --%} lines if you're using script variables. I struggled with the same issue until I realized that removing trailing spaces solves many of the treesitter's errors. Same with JSONs, make sure they are well formatted too.
@cyaconi I have made sure that all of the white space has been cleared, there were none so unfortunately that isn't the issue :/
Before reloading this config, in the Lazy dashboard go over luarocks.nvim and rest.nvim and press x to remove the plugins and clean their directories.
After that close and reopen Neovim !
If this is not working, try to send here the content of the file you’re trying to run via rest.nvim
Activity
radvil commentedon Mar 18, 2024
Also I got these errors
8uff3r commentedon Mar 18, 2024
I added the dependencies to luarocks.nvim and it's working, I use lazy.nvim so this is my config:
{ "vhyrro/luarocks.nvim", opts = { rocks = { "lua-curl", "nvim-nio", "mimetypes", "xml2lua" }, -- Specify LuaRocks packages to install }, }radvil commentedon Mar 18, 2024
Thanks, I ll try that. This should be clarified in the documentation.
radvil commentedon Mar 18, 2024
This works, but the keybinds options seems like still broken. still have that error message, but it's fine, gotta setup them manually for now
NTBBloodbath commentedon Mar 18, 2024
Hey, I'm very sorry that everything broke, but it was for improvement and it was necessary, nothing will break again!
Could you send your keybind setup? I'm busy right now so I can't help much, but as soon as I can I'll take a look. Also thanks @8uff3r for helping there! :)
radvil commentedon Mar 18, 2024
It's okay for breaking changes, I like a new result preview, however it is better to make a stable release for the previous version that doesn't break, because I needed to search to the whole commit history just to make everything works as the previous one again.
Anyway, here is my config options:
I just pasted everything from the default config based on the new README.
radvil commentedon Mar 18, 2024
I leave this comment here, just in case anyone else that want to revert to previous version.
This is latest commit that works
91badd46c60df6bd9800c809056af2d80d33da4c8uff3r commentedon Mar 18, 2024
You can use lazy.nvim to setup your keybinds with
keys:{ "rest-nvim/rest.nvim", keys = { { "<leader>rr", "<cmd>Rest run<cr>", desc = "Run REST request" }, }, },NTBBloodbath commentedon Mar 18, 2024
In the repository there are tags and semantic releases that you can use in your plugin manager to rollback to the previous stable release :)
Now, that bug is a little weird, I'll definitely take a look at it as soon as I get home, thanks for reporting it and also for providing a commit in case someone wants to rollback that way, that is appreciated.
radvil commentedon Mar 18, 2024
Oh, my bad, I didn't check the release tags, haha. Sorry for that
fix(config): proper checking for the keybinds configuration table cor…
NTBBloodbath commentedon Mar 18, 2024
@radvil I think I fixed the
keybindsconfiguration table issue, could you please update and check if the issue persists in your end?29 remaining items
bowmanpete123 commentedon Mar 23, 2024
Heres what pops up for me:
I'm not sure what the go is sadly :/
bowmanpete123 commentedon Mar 23, 2024
Tried to install luarocks on its own and then rest and still same error popping up :/
NTBBloodbath commentedon Mar 23, 2024
Hey @mesa123123, just noticed I had to modify the
build.luascript to adopt some breaking changes in theluarocks.nvimplugin, could you please try again? Let's hope this one does the trick and my apologies for the inconveniences :)bowmanpete123 commentedon Mar 23, 2024
No dice sorry :/
Maybe its my config?
bowmanpete123 commentedon Mar 23, 2024
Also no need to apologise! This is part of being in open source! All part of it :D
bowmanpete123 commentedon Mar 25, 2024
OK so I think I got it working:
Basically I've added paths to my package path so nvim knows where to look for my paths:
And it seems to work now! Or at least my errors are all about treesitter!
Thats the output I get when I open a .http file
kevinm6 commentedon Mar 26, 2024
I arrive a little later, but I figure out a way to make it works on macOS using previous comments and advice.
(the config is based on Lazy.nvim)
{ "vhyrro/luarocks.nvim”, -- explicit tell Lazy the module name due to error on calling -- the module with the suffix ‘.nvim’; in this way Lazy will call < require “luarocks”.setup({}) > name = "luarocks”, config = true }, { "rest-nvim/rest.nvim", dependencies = { "luarocks" }, ft = { "http", "https" }, config = function(_, o) require "rest-nvim".setup(o) end }With this config all the build and installation is done correctly.
caenrique commentedon Mar 27, 2024
with all the breaking changes, it would be nice to have documentation on how to migrate from the previous setup
nezudevv commentedon Apr 2, 2024
I seem to be getting an error as well. Not sure if it's related to this new release but sharing just in case. I am also stuck trying to get past it.
Here is the error message. It seems to be a tree-sitter parsing issue but cannot for the life of me get passed this.
Happens when running :Rest run while hilghighting the request line in a HTTP file.
I should say that I've also tried several other iterations of configs setup that have been suggested in this thread, all with the same result.
cyaconi commentedon Apr 2, 2024
Check trailing spaces in your http file, delete them even in
--{%and--%}lines if you're using script variables. I struggled with the same issue until I realized that removing trailing spaces solves many of the treesitter's errors. Same with JSONs, make sure they are well formatted too.nezudevv commentedon Apr 3, 2024
@cyaconi I have made sure that all of the white space has been cleared, there were none so unfortunately that isn't the issue :/
kevinm6 commentedon Apr 3, 2024
@nezudevv try to change
luarocks.nvimto{ "vhyrro/luarocks.nvim”, name = ‘luarocks’, opts = { rocks = { "lua-curl", "nvim-nio", "mimetypes", "xml2lua" } } }Before reloading this config, in the
Lazydashboard go overluarocks.nvimandrest.nvimand pressxto remove the plugins and clean their directories.After that close and reopen Neovim !
If this is not working, try to send here the content of the file you’re trying to run via
rest.nvim