Runtime panic from default status-bar plugin in 0.36.0 #2505
Labels
Comments
|
Deleting |
|
Yeah, this can sometimes happen when the status bar cache gets corrupted. Next version we'll handle this more graciously (apologies for the experience now anyhow!) |
|
I just saw something similar: This happened when starting zellij after powercycling my laptop, so orderly shutdown. Here is |
|
@jaeheonji - do you think we can make the status bar tips caching a little more resilient? I'm not sure why this is happening, but I think something like:
wdyt? I'm asking because I think this will take you ~2 seconds to do if you have the time :) Anyway: from next version this will no longer crash zellij, just the status bar, so at least it's an improvement! |
Yes I can. I don't know the exact reason for users, but depending on the environment, I/O to the /tmp folder doesn't seem to work.
Therefore, if I create a flow naturally with step 2 to 3, it seems that stability will increase more. Note: // zellij/default-plugins/status-bar/src/tip/cache.rs
...
pub fn new(path: PathBuf) -> LocalCacheResult {
match OpenOptions::new()
.read(true)
.create(true)
.open(path.as_path())
{
Ok(mut file) => {
let mut json_cache = String::new();
file.read_to_string(&mut json_cache)
.map_err(LocalCacheError::Io)?;
let metadata = LocalCache::from_json(&json_cache)?;
Ok(LocalCache { path, metadata })
},
Err(e) => Err(LocalCacheError::IoPath(e, path)),
}
}
... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looks like there is a WASM runtime panic for the status bar default plugin, please refer to the stdout below. I deleted my custom plugin configuration, reinstalled with homebrew, and used a different terminal emulator. More information below.
Log from stdout:
Further information
I have not tried but I believe this is version 0.36.0 specific. Happy to provide any more information necessary. Thanks!
The text was updated successfully, but these errors were encountered: