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

Panicked (out of range) - tokio-runtime-worker #8571

Closed
spe888 opened this issue Oct 19, 2023 · 6 comments
Closed

Panicked (out of range) - tokio-runtime-worker #8571

spe888 opened this issue Oct 19, 2023 · 6 comments
Labels
C-bug Category: This is a bug

Comments

@spe888
Copy link

spe888 commented Oct 19, 2023

Summary

When changing some text I get a panick error, maybe it has something to do with the current macOS Update (14.0), not sure.

thread 'tokio-runtime-worker' panicked at 'range end index 18446744073709551615 out of range for slice of length 0', /Users/brew/Library/Caches/Homebrew/cargo_cache/registry/src/index.crates.io-6f17d22bba15001f/ropey-1.6.0/src/tree/node_children.rs:312:21
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Reproduction Steps

I tried this:

  1. hx
  2. toggling comments or inserting text (happens only sometimes)

I expected this to happen:
changing text

Instead, this happened:
thread tokio-runtime-worker panicked as explained

Helix log

~/.cache/helix/helix.log
the file `~/.cache/helix/helix.log` does not have any recent errors/messages

Platform

macOS 14.0

Terminal Emulator

default terminal, bash, zsh, warp

Helix Version

helix 23.05 (7f5940b)

@spe888 spe888 added the C-bug Category: This is a bug label Oct 19, 2023
@spe888
Copy link
Author

spe888 commented Oct 19, 2023

Seems like the same problem: #8415

If I remove the .git folder then everything works on macOS 14. I never had the problem on macOS 13.

@pascalkuthe
Copy link
Member

It's because you are compilig with a too new version of rust. The problem has been fixes on master for a lang time.

@pascalkuthe pascalkuthe closed this as not planned Won't fix, can't repro, duplicate, stale Oct 19, 2023
@spe888
Copy link
Author

spe888 commented Oct 19, 2023

@pascalkuthe I used brew install helix, I didn't do a manual compilation to get this bug/behavior.

But I did compile it manually now and it works, but for some reason the target build does not read the configuration and languages properly, even when I use the --config flag /Users/<username>/Projects/helix/target/release/hx --config ~/.config/helix/config.toml

@pascalkuthe
Copy link
Member

yeah the brew package is broken. We don't maintain that, so you will need to report that to them and not us

@spe888
Copy link
Author

spe888 commented Oct 19, 2023

@pascalkuthe okay thanks, I'll forward it to them.

@spe888
Copy link
Author

spe888 commented Oct 20, 2023

I've opened a issue on homebrew. The only workaround I've found (for now) is to install the latest version brew install --HEAD helix

[EDIT] They immediately closed the ticket, they seem not to really care, someone would need to push a PR, but I've no knowledge of writing homebrew ruby formulas.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug
Projects
None yet
Development

No branches or pull requests

2 participants