Weird issue with splits shrinking then crashing #20

Burb commented 2022年08月11日 11:29:43 +02:00

Hi,

Just found out about this project and so far I like it. Especially a split file that doesn't take trial and error to figure out the formatting for.

I'm having some really weird issues though, unfortunately making it unusable.
After every run, the list of splits will decrease. The splits are still there if you scroll.. just the "bottom" of the area you can scroll with the mouse will creep up by one split.
Eventually it will reach the top and you can't see any splits. At this point mist will crash.

I recorded a video so you can see what it looks like.

https://www.youtube.com/watch?v=wWtnD9QAC8w

The binary from the release page didn't work, so I compiled it myself. Binary just comes up with a window saying
"No such file or directory (os error 2)"

Got this warning at the end of compilation as well.

warning: the following packages contain code that will be rejected by a future version of Rust: allsorts-rental v0.5.6, allsorts_no_std v0.5.2
note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 1`

Report:

> = note: `#[allow(proc_macro_back_compat)]` on by default
> = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
> = note: for more information, see issue #83125 <https://github.com/rust-lang/rust/issues/83125>
> = note: The `procedural-masquerade` crate has been unnecessary since Rust 1.30.0. Versions of this crate below 0.1.7 will eventually stop compiling.
> = note: this warning originates in the macro `rental` (in Nightly builds, run with -Z macro-backtrace for more info)

Not sure if that's related at all, but figured I'd post it.

Fedora 36, Rust 1.62.1, Cargo 1.62.1

Any ideas?

Hi, Just found out about this project and so far I like it. Especially a split file that doesn't take trial and error to figure out the formatting for. I'm having some really weird issues though, unfortunately making it unusable. After every run, the list of splits will decrease. The splits are still there if you scroll.. just the "bottom" of the area you can scroll with the mouse will creep up by one split. Eventually it will reach the top and you can't see any splits. At this point mist will crash. I recorded a video so you can see what it looks like. https://www.youtube.com/watch?v=wWtnD9QAC8w The binary from the release page didn't work, so I compiled it myself. Binary just comes up with a window saying ```"No such file or directory (os error 2)"``` Got this warning at the end of compilation as well. ```Finished release [optimized] target(s) in 15.12s warning: the following packages contain code that will be rejected by a future version of Rust: allsorts-rental v0.5.6, allsorts_no_std v0.5.2 note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 1` ``` Report: ``` > = note: `#[allow(proc_macro_back_compat)]` on by default > = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release! > = note: for more information, see issue #83125 <https://github.com/rust-lang/rust/issues/83125> > = note: The `procedural-masquerade` crate has been unnecessary since Rust 1.30.0. Versions of this crate below 0.1.7 will eventually stop compiling. > = note: this warning originates in the macro `rental` (in Nightly builds, run with -Z macro-backtrace for more info) ``` Not sure if that's related at all, but figured I'd post it. Fedora 36, Rust 1.62.1, Cargo 1.62.1 Any ideas?

periwinkle commented 2022年08月12日 01:50:47 +02:00

1. The split decreasing thing is something that I've also seen before in my own use, but it's pretty rare for me. I don't know what causes it and as such have yet to be able to fix it. I will look into it in more depth now that I have confirmation though. Thanks for the video proof.

2. My bad, shipped a configuration file containing a path from my machine in that one. Should be fixed now.

3. That compile warning was fixed on master as of #15 being merged (11336a7b6e) on July 9th, is your clone outdated?

1. The split decreasing thing is something that I've also seen before in my own use, but it's pretty rare for me. I don't know what causes it and as such have yet to be able to fix it. I will look into it in more depth now that I have confirmation though. Thanks for the video proof. 2. My bad, shipped a configuration file containing a path from my machine in that one. Should be fixed now. 3. That compile warning was fixed on master as of #15 being merged (11336a7b6e) on July 9th, is your clone outdated?

periwinkle commented 2022年08月21日 20:13:55 +02:00

Believe I've fixed the first issue now.

Believe I've fixed the first issue now.

Burb commented 2022年08月21日 23:32:01 +02:00

Nice, just checked out and it indeed seem to be fixed now.

Nice, just checked out and it indeed seem to be fixed now.