4
70
Fork
You've already forked pay-respects
4

[Bug]: #3

Closed
opened 2024年12月05日 19:15:40 +01:00 by Stenters · 1 comment

What happened?

The main thread panicked while running correction for "sud"

The command and output

enterss@stuart-kub-02:(削除) $ sud
Command 'sud' not found, but there are 15 similar ones.
enterss@stuart-kub-02: (削除ここまで)
$ f
sudo

Execute suggestion?: [Enter] [Ctrl+C]

thread 'main' panicked at /home/enterss/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pay-respects-0.5.14/src/shell.rs:79:76:
index out of bounds: the len is 0 but the index is 0
stack backtrace:
0: 0x610b21c4caac -
1: 0x610b21bee9d3 -
2: 0x610b21c1cde2 -
3: 0x610b21c52b92 -
4: 0x610b21c529fb -
5: 0x610b21c5315c -
6: 0x610b21c52c68 -
7: 0x610b21c52bc9 -
8: 0x610b21c52bbc -
9: 0x610b21b9de5f -
10: 0x610b21b9de31 -
11: 0x610b21bca52e -
12: 0x610b21bca7c5 -
13: 0x610b21be30f9 -
14: 0x610b21ba5fb3 -
15: 0x610b21be9f07 -
16: 0x75b9c0e2a1ca - __libc_start_call_main
at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16
17: 0x75b9c0e2a28b - __libc_start_main_impl
at ./csu/../csu/libc-start.c:360:3
18: 0x610b21ba3a45 -
19: 0x0 -
enterss@stuart-kub-02:~$

Build information

enterss@stuart-kub-02:~$ pay-respects --version
version: 0.5.14
compile features:

  • runtime-rules
  • request-ai
  • libcurl

No similar issue

  • I have searched the issue list and there is no similar issue found
### What happened? The main thread panicked while running correction for "sud" ### The command and output enterss@stuart-kub-02:~$ sud Command 'sud' not found, but there are 15 similar ones. enterss@stuart-kub-02:~$ f sudo Execute suggestion?: [Enter] [Ctrl+C] thread 'main' panicked at /home/enterss/.cargo/registry/src/index.crates.io-6f17d22bba15001f/pay-respects-0.5.14/src/shell.rs:79:76: index out of bounds: the len is 0 but the index is 0 stack backtrace: 0: 0x610b21c4caac - <unknown> 1: 0x610b21bee9d3 - <unknown> 2: 0x610b21c1cde2 - <unknown> 3: 0x610b21c52b92 - <unknown> 4: 0x610b21c529fb - <unknown> 5: 0x610b21c5315c - <unknown> 6: 0x610b21c52c68 - <unknown> 7: 0x610b21c52bc9 - <unknown> 8: 0x610b21c52bbc - <unknown> 9: 0x610b21b9de5f - <unknown> 10: 0x610b21b9de31 - <unknown> 11: 0x610b21bca52e - <unknown> 12: 0x610b21bca7c5 - <unknown> 13: 0x610b21be30f9 - <unknown> 14: 0x610b21ba5fb3 - <unknown> 15: 0x610b21be9f07 - <unknown> 16: 0x75b9c0e2a1ca - __libc_start_call_main at ./csu/../sysdeps/nptl/libc_start_call_main.h:58:16 17: 0x75b9c0e2a28b - __libc_start_main_impl at ./csu/../csu/libc-start.c:360:3 18: 0x610b21ba3a45 - <unknown> 19: 0x0 - <unknown> enterss@stuart-kub-02:~$ ### Build information enterss@stuart-kub-02:~$ pay-respects --version version: 0.5.14 compile features: - runtime-rules - request-ai - libcurl ### No similar issue - [x] I have searched the issue list and there is no similar issue found
Owner
Copy link

Fixed 1de52883e0.

Fixed 1de52883e0.
Sign in to join this conversation.
No Branch/Tag specified
main
dev
nightly
v0.8.8
v0.8.7
v0.8.6
v0.8.5
v0.8.4
v0.8.3
v0.8.2
v0.8.1
v0.8.0
v0.7.13
v0.7.12
v0.7.11
v0.7.10
v0.7.9
v0.7.8
v0.7.7
v0.7.6
v0.7.5
v0.7.4
v0.7.3
v0.7.2
v0.7.1
v0.7.0
v0.6.14
v0.6.13
v0.6.12
v0.6.11
v0.6.10
v0.6.9
v0.6.8
v0.6.7
v0.6.6
v0.6.5
v0.6.4
v0.6.3
v0.6.2
v0.6.1
v0.6.0
v0.5.15
v0.5.14
v0.5.13
v0.5.12
v0.5.11
v0.5.10
v0.5.9
v0.5.8
v0.5.7
v0.5.6
v0.5.5
v0.5.4
v0.5.3
v0.5.2
v0.5.1
v0.5.0
v0.4.18
v0.4.17
v0.4.16
v0.4.15
v0.4.14
v0.4.13
v0.4.12
v0.4.11
v0.4.10
v0.4.9
v0.4.8
v0.4.7
v0.4.6
v0.4.5
v0.4.4
v0.4.3
v0.4.2
v0.4.1
v0.4.0
v0.3.4
v0.3.3
v0.3.2
v0.3.1
v0.3.0
v0.2.1
v0.2.0
v0.1.1
v0.1.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
iff/pay-respects#3
Reference in a new issue
iff/pay-respects
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?