Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stack traceback with :Telescope frecency #119

Closed
jyuan0 opened this issue Aug 10, 2023 · 2 comments · Fixed by #120
Closed

Stack traceback with :Telescope frecency #119

jyuan0 opened this issue Aug 10, 2023 · 2 comments · Fixed by #120

Comments

@jyuan0
Copy link

jyuan0 commented Aug 10, 2023

After the recent OO refactor, running :Telescope frecency gives me the following error:

Error executing Lua callback: ...im/lazy/telescope-frecency.nvim/lua/frecency/recency.lua:30: bad argument #1 to 'ipairs' (table expected, got nil)
stack traceback:
	[C]: in function 'ipairs'
	...im/lazy/telescope-frecency.nvim/lua/frecency/recency.lua:30: in function 'calculate'
	...vim/lazy/telescope-frecency.nvim/lua/frecency/picker.lua:205: in function 'fetch_results'
	...vim/lazy/telescope-frecency.nvim/lua/frecency/picker.lua:83: in function 'start'
	...m/lazy/telescope-frecency.nvim/lua/frecency/frecency.lua:104: in function 'start'
	.../nvim/lazy/telescope-frecency.nvim/lua/frecency/init.lua:13: in function <.../nvim/lazy/telescope-frecency.nvim/lua/frecency/init.lua:11>
	...share/nvim/lazy/telescope.nvim/lua/telescope/command.lua:193: in function 'run_command'
	...share/nvim/lazy/telescope.nvim/lua/telescope/command.lua:253: in function 'load_command'
	...ocal/share/nvim/lazy/telescope.nvim/plugin/telescope.lua:108: in function <...ocal/share/nvim/lazy/telescope.nvim/plugin/telescope.lua:107>

This is with a nightly Neovim build (v0.10.0-dev-766+gef44e5972). Please feel free to close this if it's just a bug on nightly, and if you need more info, please let me know. Thanks!

@delphinus
Copy link
Member

It seems your DB has file entries that have no related timestamps. I did a fix for those cases in #120.

@jyuan0
Copy link
Author

jyuan0 commented Aug 11, 2023

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants