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

Panic when selecting text (assertion failed: self.is_char_boundary(at)) #750

Closed
TehPers opened this issue Feb 9, 2024 · 4 comments · Fixed by #751
Closed

Panic when selecting text (assertion failed: self.is_char_boundary(at)) #750

TehPers opened this issue Feb 9, 2024 · 4 comments · Fixed by #751

Comments

@TehPers
Copy link

TehPers commented Feb 9, 2024

Describe the bug

Nushell seems to panic when selecting text that includes a hyphen.

How to reproduce

  1. Type git checkout abc-123
  2. ctrl + left to place cursor after the last hyphen (right before the 1)
  3. shift + ctrl + left to attempt to select abc-

Attempting to ctrl+select -123 using ctrl + shift + right also triggers it.

Expected behavior

It should select abc- (or -123 going the other direction) without any panics.

Screenshots

Windows Terminal:
image

vscode:
image

With RUST_BACKTRACE = "full" after cargo install --profile dev nu:
image

(Relevant part of path in error: reedline-0.29.0\src\painting\styled_text.rs:61:58)

Configuration

key value
version 0.90.1
branch
commit_hash
build_os windows-x86_64
build_target x86_64-pc-windows-msvc
rust_version rustc 1.76.0 (07dca489a 2024-02-04)
rust_channel stable-x86_64-pc-windows-msvc
cargo_version cargo 1.76.0 (c84b36747 2024-01-18)
build_time 2024-02-08 22:43:24 -08:00
build_rust_channel release
allocator mimalloc
features dataframe, default, extra, sqlite, trash, which, zip
installed_plugins

Additional context

OS: Win 11 Pro
Terminal: Windows Terminal

Also, I'm using starship and carapace, if that's relevant. Was able to reproduce in vscode using ctrl+shift+right to attempt to select -123.

@fdncred
Copy link
Collaborator

fdncred commented Feb 9, 2024

Thanks for the issue. I think this is the same as what I mentioned here (but not a duplicate) #689 (comment)

@TehPers
Copy link
Author

TehPers commented Feb 9, 2024

@fdncred It looks like it may be the same issue. When I created this issue, I didn't see that this was an error with reedline until I reinstalled nu with the dev profile.

I can reopen this issue on the reedline repository instead if that would be better.

@fdncred
Copy link
Collaborator

fdncred commented Feb 9, 2024

I'll just move this one.

@fdncred fdncred transferred this issue from nushell/nushell Feb 9, 2024
@maxomatic458
Copy link
Contributor

yea so i could only replicate this in a buffer with multiple colors
cargo run --example completion type "abc-123" then from the right side: CTRL+LEFT, CTRL+SHIFT+LEFT nothing happens.

cargo run --example demo type "test abc-123" (test will be colored), then do the same as above, this will crash.

so i think somewhere buffer bytes and the char width of the buffer is mixed up and that leads to a panic right here:

let after_range = in_range.split_off(to - current_idx - from);

fdncred added a commit to nushell/nushell that referenced this issue Feb 12, 2024
# Description

This fixes a panic with the text selection.

Reference
nushell/reedline#751
nushell/reedline#750
nushell/reedline#689 (comment)


# 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` to
check that you're using the standard code style
- `cargo test --workspace` to check that all tests pass (on Windows make
sure to [enable developer
mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging))
- `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.
-->
dmatos2012 pushed a commit to dmatos2012/nushell that referenced this issue Feb 20, 2024
# Description

This fixes a panic with the text selection.

Reference
nushell/reedline#751
nushell/reedline#750
nushell/reedline#689 (comment)


# 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` to
check that you're using the standard code style
- `cargo test --workspace` to check that all tests pass (on Windows make
sure to [enable developer
mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging))
- `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.
-->
kik4444 pushed a commit to kik4444/nushell-fork that referenced this issue Feb 28, 2024
# Description

This fixes a panic with the text selection.

Reference
nushell/reedline#751
nushell/reedline#750
nushell/reedline#689 (comment)


# 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` to
check that you're using the standard code style
- `cargo test --workspace` to check that all tests pass (on Windows make
sure to [enable developer
mode](https://learn.microsoft.com/en-us/windows/apps/get-started/developer-mode-features-and-debugging))
- `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.
-->
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.

3 participants