Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

exists() hangs when it should return false

Open
#563 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
lua
Domain
tooling

Research direction

Reproduce the issue from the two Lua commands in the report, comparing find_upwards('node_modules'):exists() with find_upwards('red_herring'):exists(). Trace the find_upwards and exists entry points, then verify that a missing upward match returns false without hanging.

Written by the indexing model from the issue text.

Description

You'd expect this to echo true, and this is what happens:

:lua print(require('plenary.path'):new('.'):find_upwards('node_modules'):exists())

You'd expect this to echo false, but instead it just hangs:

:lua print(require('plenary.path'):new('.'):find_upwards('red_herring'):exists())
Dominant language
Lua
Stars
3.5k
Forks
340
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nvim-lua/plenary.nvim

All issues in nvim-lua/plenary.nvim

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.