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 "byte index 3236 is not a char boundary" on latest available release and first run. #60

Closed
aqilc opened this issue Oct 23, 2020 · 6 comments
Labels
C-bug Category: bugs ILE (Internal Linter Error) A panic from the linter T-Parser This issue primarily relates to rslint_parser

Comments

@aqilc
Copy link

aqilc commented Oct 23, 2020

Code

Not relevant, needed code is below.

Meta

rslint -V: 0.2.1

Error Output

current_dir> rslint_cli-windows d:/projects/nodejs/someproject
The linter panicked unexpectedly. This is a bug.

We would appreciate a bug report: https://github.com/RDambrosio016/RSLint/issues/new?labels=ILE%2C+bug&template=internal-linter-error.md

Please include the following info:

message: byte index 3236 is not a char boundary; it is inside '™' (bytes 3234..3237) of `
// Filesystem modules
import { existsSync } from "fs"; import { project, messages } from "../config.js";

// Creates random strings for re-importing
import { list, trim } from "./f.js";

// This is the command(singular) handler, which imports comma`[...]
location: crates\rslint_parser\src\lossless_tree_sink.rs:74:28
@aqilc aqilc added the ILE (Internal Linter Error) A panic from the linter label Oct 23, 2020
@RDambrosio016
Copy link
Collaborator

This is a known issue, its quite obscure so i dont know the root cause of it yet but i am looking into it 🙂

@RDambrosio016 RDambrosio016 added C-bug Category: bugs T-Parser This issue primarily relates to rslint_parser labels Oct 23, 2020
@aqilc
Copy link
Author

aqilc commented Oct 23, 2020

Ohh ok thanks! Looking forward to using it after it is fixed. Loved this project because eslint is a bloated pain to me sometimes 😄

@Stupremee
Copy link
Member

Stupremee commented Oct 26, 2020

@AqilCont This will be fixed in my next PR.

Edit: Fixed in 6dc363b

Edit2: My "fix" caused more issues than it fixed, so it will take some time until this is fixed.

@Stupremee Stupremee reopened this Oct 26, 2020
@aqilc
Copy link
Author

aqilc commented Oct 27, 2020

Ohhhh I'm really glad you're working on it! From what I've seen, I'm really excited to start using this tool starting from when this issue is fixed :DDD. Thanks a lot for the updates!
I actually really want to help myself, but these are the times I regret not learning much Rust[I miss out on contributing to so many cool projects like this :'(].
Also the embodiment of "1 fix => 10 new bugs" just happened o_O

@RDambrosio016
Copy link
Collaborator

There is always time to learn more rust! https://doc.rust-lang.org/book/

@Stupremee
Copy link
Member

Stupremee commented Oct 28, 2020

Now it's fixed in 8b76fb3 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: bugs ILE (Internal Linter Error) A panic from the linter T-Parser This issue primarily relates to rslint_parser
Projects
None yet
Development

No branches or pull requests

3 participants