-
Notifications
You must be signed in to change notification settings - Fork 152
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
Panic when accepting element from help menu #602
Labels
bug
Something isn't working
Comments
Thanks for the reproducible example and backtrace. This sounds like a variation of nushell/nushell#9627 probably needs to be addressed here in reedline. |
This was referenced Jul 21, 2023
fdncred
pushed a commit
to nushell/nushell
that referenced
this issue
Aug 14, 2023
…the help menu (#9784) <!-- if this PR closes one or more issues, you can automatically link the PR with them by using one of the [*linking keywords*](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword), e.g. - this PR should close #xxxx - fixes #xxxx you can also mention related issues, PRs or discussions! --> # Description <!-- Thank you for improving Nushell. Please, check our [contributing guide](../CONTRIBUTING.md) and talk to the core team before making major changes. Description of your pull request goes here. **Provide examples and/or screenshots** if your changes affect the user experience. --> Fixes #9627 Related nushell/reedline#602 nushell/reedline#612 # User-Facing Changes <!-- List of all changes that impact the user experience here. This helps us keep track of breaking changes. --> # Tests + Formatting <!-- Don't forget to add tests that cover your changes. Make sure you've run and fixed any issues with these commands: - `cargo fmt --all -- --check` to check standard code formatting (`cargo fmt --all` applies these changes) - `cargo clippy --workspace -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect -A clippy::result_large_err` to check that you're using the standard code style - `cargo test --workspace` to check that all tests pass - `cargo run -- -c "use std testing; testing run-tests --path crates/nu-std"` to run the tests for the standard library > **Note** > from `nushell` you can also use the `toolkit` as follows > ```bash > use toolkit.nu # or use an `env_change` hook to activate it automatically > toolkit check pr > ``` --> # After Submitting <!-- If your PR had any user-facing changes, update [the documentation](https://github.com/nushell/nushell.github.io) after the PR is merged, if necessary. This will help us keep the docs up to date. -->
For now closed on the nushell side by #9784 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Platform macOS 13.4
Terminal software kitty 0.29.0
I don't really know in what broader context it occurs, but here's a sequence of input that will consistently make nushell crash. From the trace, it looks like the panic occurs in Reedline.
Steps to reproduce
At this point, nushell panics.
Backtrace
The text was updated successfully, but these errors were encountered: