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

Session manager takes a lot of time to list sessions for a new zellij instance #2946

Closed
inmny opened this issue Nov 16, 2023 · 4 comments · Fixed by #2951
Closed

Session manager takes a lot of time to list sessions for a new zellij instance #2946

inmny opened this issue Nov 16, 2023 · 4 comments · Fixed by #2951
Assignees

Comments

@inmny
Copy link

inmny commented Nov 16, 2023

I open alacritty with zellij. It is attached to an active session. But it takes too long to list sessions for Session Manager(about a minute).

It is normal for the instance which has searched sessions before.

image

Any more information needed?

@imsnif
Copy link
Member

imsnif commented Nov 16, 2023

Thanks for reporting this! I just noticed this myself. It's a bug in 0.39.1 that I'll make a patch for probably next week.

For now, to get around this you can increase the frequency of the session_serialization in the config. eg. session_serialization 1 will make it happen every 1 second and should solve this.

@imsnif imsnif self-assigned this Nov 16, 2023
@inmny
Copy link
Author

inmny commented Nov 16, 2023

session_serialization true? It's the default value and it's boolean type. And I cannot find such a config item to increase the frequency of the session_serialization.

I attempted to set session_serialization 1. But it crashes Zellij with

 Failed to parse Zellij configuration
     ╭─[/home/inmny/.config/zellij/config.kdl:241:1]
 241 │ //
 242 │ session_serialization 1
     · ───────────┬───────────
     ·            ╰── Property session_serialization must be true or false, found 1
 243 │
     ╰────

@imsnif
Copy link
Member

imsnif commented Nov 16, 2023

serialization_interval 1 - sorry, my bad

@inmny inmny closed this as completed Nov 16, 2023
@imsnif
Copy link
Member

imsnif commented Nov 16, 2023

Sorry, I'm going to keep this open because while there is a workaround, this is still a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants