Can't get Meli to run #1

New Issue

yomo · 2019-07-12T10:39:57+03:00

yomo commented

2019-07-12 10:39:57 +03:00

Hi! I know this is a very early pre-release but I thought maybe my report could help.

I'm running Meli inside tmux, on Arch Linux, compiled from source using cargo build. I have encountered several issues:

Upon launching Meli, my screen gets filled with with thousands of messages like this:

40535738292 in 7784043842235995642 map
                                                                   ["parsing \"Archive\""] melib/src/backends/maildir.rs:69_9:       looking for 5489885004938820455 in 7784043842235995642 map
                                                                                          ["parsing \"Archive\""] melib/src/backends/maildir.rs:69_9:        looking for 5489885004938820455 in 7784043842235995642 map

It seems impossible to stop the flow of messages, and it takes a couple of minutes before it stops.

When the messages stop, only resizing the terminal (using tmux) or pressing one of the binded keys (e.g. J or K) reveals the application interface, with my folders on the left and a text saying Loading. below the contact list button.
After pressing return on some email, Meli crashes with this error: thread 'thread 'thread '<unnamed><unnamed>' panicked at '<unnamed>' panicked at 'cannot access stderr during shutdown' panicked at 'cannot access stderr during shutdown', cannot access stderr during shutdown', src/libcore/option.rssrc/libcore/option.rs::', %

I do have a little more than 15,000 emails in my maildir, but Meli seems to handle that amount quite amazingly fast, when listing the emails in the different directories.

Thank you for Meli, it looks like has a tremendous potential!

Hi! I know this is a very early pre-release but I thought maybe my report could help. I'm running Meli inside tmux, on Arch Linux, compiled from source using `cargo build`. I have encountered several issues: 1. Upon launching Meli, my screen gets filled with with thousands of messages like this: ``` 40535738292 in 7784043842235995642 map ["parsing \"Archive\""] melib/src/backends/maildir.rs:69_9: looking for 5489885004938820455 in 7784043842235995642 map ["parsing \"Archive\""] melib/src/backends/maildir.rs:69_9: looking for 5489885004938820455 in 7784043842235995642 map ``` It seems impossible to stop the flow of messages, and it takes a couple of minutes before it stops. 2. When the messages stop, only resizing the terminal (using tmux) or pressing one of the binded keys (e.g. J or K) reveals the application interface, with my folders on the left and a text saying `Loading.` below the `contact list` button. 3. After pressing `return` on some email, Meli crashes with this error: `thread 'thread 'thread '<unnamed><unnamed>' panicked at '<unnamed>' panicked at 'cannot access stderr during shutdown' panicked at 'cannot access stderr during shutdown', cannot access stderr during shutdown', src/libcore/option.rssrc/libcore/option.rs::', %` I do have a little more than 15,000 emails in my maildir, but Meli seems to handle that amount quite amazingly fast, when listing the emails in the different directories. Thank you for Meli, it looks like has a tremendous potential!

❤️ 1

Manos Pitsidianakis commented

2019-07-12 12:52:05 +03:00

Thank you for your kind words :D

Upon launching Meli, my screen gets filled with with thousands of messages like this:

I've mentioned it in the README but it's really not understandable without knowing what it's talking about:

builds with debug print logs on stderr

So you have to launch the debug builds as

cargo run 2> debug.log # or /dev/null

For non-dev purposes, one should use the release build which is optimized by the compiler and faster. It

cargo run --release

The README must change to make this understandable and also add information for running and building.

Meli crashes with this error: thread 'thread 'thread '' panicked at '' panicked at 'cannot access stderr during shutdown

This happens because threads can't access stdin after the main process dies, I haven't had time to investigate why because it was a low hanging fruit.

EDIT: Regarding 3. The real panic should be above the 'cannot access stderr during shutdown' message.

Thank you for your kind words :D > Upon launching Meli, my screen gets filled with with thousands of messages like this: I've mentioned it in the README but it's really not understandable without knowing what it's talking about: > builds with debug print logs on stderr So you have to launch the debug builds as > cargo run 2> debug.log # or /dev/null For non-dev purposes, one should use the release build which is optimized by the compiler and faster. It > cargo run --release The README must change to make this understandable and also add information for running and building. > Meli crashes with this error: thread 'thread 'thread '<unnamed><unnamed>' panicked at '<unnamed>' panicked at 'cannot access stderr during shutdown This happens because threads can't access stdin after the main process dies, I haven't had time to investigate why because it was a low hanging fruit. EDIT: Regarding 3. The real panic should be above the 'cannot access stderr during shutdown' message.

yomo commented

2019-07-15 14:29:28 +03:00

Poster

Thanks @epilys! Didn't realize I was opening issue #1 here 🥳

Sorry for missing those parts in the README. It makes more sense now and I managed to run a --release version.

I'll keep following the project then. Thank you!

Thanks @epilys! Didn't realize I was opening issue #1 here 🥳 Sorry for missing those parts in the README. It makes more sense now and I managed to run a --release version. I'll keep following the project then. Thank you!

🎉 1

Manos Pitsidianakis closed this issue

2019-07-15 14:38:53 +03:00

Sign in to join this conversation.