luaPackages, vimPlugins: update on 2024-09-24 #343814
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ofborg
bot
added
8.has: clean-up
8.has: package (new)
khaneliman
force-pushed
the
lua
branch
3 times, most recently
from
6c52fb3 to
8012fb4
Compare
|
Result of 11 packages marked as broken and skipped:
310 packages built:
|
|
Result of 12 packages marked as broken and skipped:
310 packages built:
|
ofborg
bot
requested review from
mrcjkb,
PhotonQuantum,
teto,
callumio and
figsoda
|
Result of 11 packages marked as broken and skipped:
10 packages failed to build:
300 packages built:
|
|
x86 darwin neotest error with test. Fail || integrated strategy stops the job
...kiz-lua5.1-nvim-nio-1.10.0-1/share/lua/5.1/nio/tests.lua:48: Test task failed with message:
The coroutine failed with this message:
.../source/tests/unit/client/strategies/integrated_spec.lua:45: Expected objects to not be equal.
Passed in:
(number) 0
Did not expect:
(number) 0
stack traceback:
[C]: in function 'error'
...y.nvim-scm-1-unstable-2024-09-17/lua/luassert/assert.lua:51: in function 'equal'
.../source/tests/unit/client/strategies/integrated_spec.lua:45: in function <.../source/tests/unit/client/strategies/integrated_spec.lua:35>
stack traceback:
...kiz-lua5.1-nvim-nio-1.10.0-1/share/lua/5.1/nio/tests.lua:48: in function <...kiz-lua5.1-nvim-nio-1.10.0-1/share/lua/5.1/nio/tests.lua:31> |
|
Seems like using luaAttr just causes it to skip building neotest... Result of 13 packages marked as broken and skipped:
309 packages built:
|
khaneliman
force-pushed
the
lua
branch
2 times, most recently
from
8012fb4 to
58ad7ed
Compare
|
Pulling neotest update out, plugin stopped working for me on linux, too. |
|
Result of 12 packages marked as broken and skipped:
310 packages built:
|
|
Result of 11 packages marked as broken and skipped:
310 packages built:
|
mrcjkb
approved these changes
Sep 23, 2024
We might want to investigate why. |
This error reported upstream looked familiar to what I saw nvim-neotest/neotest#452 but that mentions on nightly. EDIT: Went back to logs and it looks different. ERROR | 2024-09-23T10:28:10Z-0500 | ...NeovimPackages/start/neotest/lua/neotest/client/init.lua:0 | Couldn't find positions in path /home/khaneliman/Documents/azure/**.cs ...d-0.10.1/share/nvim/runtime/lua/vim/treesitter/query.lua:0: bad argument #3 to '_create_ts_querycursor' (number expected, got boolean)
stack traceback:
[C]: in function '_create_ts_querycursor'
...d-0.10.1/share/nvim/runtime/lua/vim/treesitter/query.lua: in function 'iter_matches'
...ckages/start/neotest/lua/neotest/lib/treesitter/init.lua: in function ''
...ckages/start/neotest/lua/neotest/lib/treesitter/init.lua: in function 'parse_positions_from_string'
...ckages/start/neotest/lua/neotest/lib/treesitter/init.lua: in function 'parse_positions'
...ackages/start/neotest-dotnet/lua/neotest-dotnet/init.lua: in function 'discover_positions'
...NeovimPackages/start/neotest/lua/neotest/client/init.lua: in function <...NeovimPackages/start/neotest/lua/neotest/client/init.lua:0>
[C]: in function 'xpcall'
...NeovimPackages/start/neotest/lua/neotest/client/init.lua: in function '_update_positions'
...NeovimPackages/start/neotest/lua/neotest/client/init.lua: in function <...NeovimPackages/start/neotest/lua/neotest/client/init.lua:0> |
|
And that error isn't thrown by neotest 5.4.1 with this package set update? |
|
Not sure why the org treesitter queries just stopped working... it wasn't even in this update |
Revisiting this again today. C# project fails with those errors, a java project I opened works fine. Both work fine if I only pull out the vimPlugins.neotest update. Still haven't found what broke the |
khaneliman
changed the title
In that case I suppose this is an issue with the neotest-dotnet adapter (if that's the one you're using?). |
I'll hold back on the plugin update this cycle and create the issue. It sounded like the developer was busy, so I might try and see if I can figure out the issue and upstream a fix if they can't do it soon enough. |
Where can I find the output? |
|
Looks like I'm getting that treesitter check failure on master, too Checking zig injections (2.63ms)
::endgroup::
Check failed!
Errors:
(x) Invalid capture @OrgStars1 in highlights for org.
(x) Invalid capture @OrgHeadlineLevel1 in highlights for org.
(x) Invalid capture @OrgStars2 in highlights for org.
(x) Invalid capture @OrgHeadlineLevel2 in highlights for org.
(x) Invalid capture @OrgStars3 in highlights for org.
(x) Invalid capture @OrgHeadlineLevel3 in highlights for org.
(x) Invalid capture @OrgKeywordTodo in highlights for org.
(x) Invalid capture @OrgKeywordDone in highlights for org.
(x) Invalid capture @OrgPriority in highlights for org.
(x) Invalid capture @OrgPriorityCookie in highlights for org.
(x) Invalid capture @OrgTag in highlights for org.
(x) Invalid capture @OrgTagList in highlights for org.
(x) Invalid capture @OrgPropertyDrawer in highlights for org.
(x) Invalid capture @OrgPropertyName in highlights for org.
(x) Invalid capture @OrgPropertyValue in highlights for org.
(x) Invalid capture @OrgProperty in highlights for org.
(x) Invalid capture @OrgTimestampInactive in highlights for org.
(x) Invalid capture @OrgTimestampDay in highlights for org.
(x) Invalid capture @OrgTimestampDate in highlights for org.
(x) Invalid capture @OrgTimestampTime in highlights for org.
(x) Invalid capture @OrgTimestampRepeat in highlights for org.
(x) Invalid capture @OrgTimestampDelay in highlights for org.
(x) Invalid capture @OrgTimestampActive in highlights for org.
(x) Invalid capture @OrgFootnoteLabel in highlights for org.
(x) Invalid capture @OrgFootnoteDescription in highlights for org.
(x) Invalid capture @OrgFootnoteDefinition in highlights for org.
(x) Invalid capture @OrgDirectiveName in highlights for org.
(x) Invalid capture @OrgDirectiveValue in highlights for org.
(x) Invalid capture @OrgDirective in highlights for org.
(x) Invalid capture @OrgComment in highlights for org.
(x) Invalid capture @OrgDrawerName in highlights for org.
(x) Invalid capture @OrgDrawerContents in highlights for org.
(x) Invalid capture @OrgDrawer in highlights for org.
(x) Invalid capture @OrgBlockName in highlights for org.
(x) Invalid capture @OrgBlockContents in highlights for org.
(x) Invalid capture @OrgBlock in highlights for org.
(x) Invalid capture @OrgDynamicBlockName in highlights for org.
(x) Invalid capture @OrgDynamicBlockContents in highlights for org.
(x) Invalid capture @OrgDynamicBlock in highlights for org.
(x) Invalid capture @OrgListBullet in highlights for org.
(x) Invalid capture @OrgCheckbox in highlights for org.
(x) Invalid capture @OrgCheckInProgress in highlights for org.
(x) Invalid capture @OrgCheckDone in highlights for org.
(x) Invalid capture @Error in highlights for org.
(x) Invalid capture @OrgTableHorizontalRuler in highlights for org.
(x) Invalid capture @OrgCellFormula in highlights for org.
(x) Invalid capture @OrgCellNumber in highlights for org.
(x) Invalid capture @property in locals for qmljs.
(x) Invalid capture @reference._let in locals for racket.
(x) Invalid capture @reference._def in locals for racket. |
|
Result of 12 packages marked as broken and skipped:
336 packages built:
|
|
Result of 13 packages marked as broken and skipped:
336 packages built:
|
|
the tree-sitter org failures are not a regression |
mrcjkb
approved these changes
Sep 24, 2024
mrcjkb
approved these changes
Sep 24, 2024
|
Are you getting that neotest test failure? I am working on fixing the deno package for x86 darwin so we stop seeing those deno related failures... |
Only on lua 5.1: I would suggest to disable tests on darwin... This is more annoying than useful. |
|
|
Marking deno as broken for x86 darwin in #343868 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes
Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Add a 👍 reaction to pull requests you find important.