kingToolbox / kingToolbox/WindTerm
session timeout after upgrade
- Dominant language
- C
- Stars
- 32.3k
- Forks
- 2.5k
- PR merge metrics
- No merged PRs in 30d
Description
followed the instruction to upgrade 2.7.0 from 2.6.1.
the .wind folder was moved to new 2.7.0 directory, but some sessions can not be logged in and prompt timeout immediately.
I'm not using master password.
but if I create new session after removed the .wind, the session can work, so I guess there's something in the .wind folder can't work on 2.7.0
how should I handle this?
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the reported upgrade from 2.6.1 to 2.7.0 with the existing .wind folder, then compare it with a newly created session after removing .wind. Trace the session login and timeout behavior using those two configurations. Done means the cause of the persisted-session failure and a verified handling path are identified.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100