Describe the bug
isStarted flag inherited between vscode session when "terminal.integrated.enablePersistentSessions": true
Therefore dashboard gui shows 'stop server' at start time.
To Reproduce
set vscode config "terminal.integrated.enablePersistentSessions": true
start server via frontmatter dashboard
stop vscode
restart vscode
Expected behavior
isStarted flag should be false when vscode starts.
Desktop (please complete the following information):
**Describe the bug**
isStarted flag inherited between vscode session when `"terminal.integrated.enablePersistentSessions": true`
Therefore dashboard gui shows 'stop server' at start time.
**To Reproduce**
- set `vscode` config `"terminal.integrated.enablePersistentSessions": true`
- start server via frontmatter dashboard
- stop `vscode`
- restart `vscode`
**Expected behavior**
isStarted flag should be `false` when `vscode` starts.
**Desktop (please complete the following information):**
- OS: Ubuntu2304
**Additional context**
frontmatter: v9.3.0
VSCODE: 1.83.1
<!-- github-sync-id:1962486009 -->
By default, the isStarted flag is false, but it will check if the VSCode FM server terminal window is open. We might need to implement a check on the extension startup to close this terminal window if still opened on restart.
I'm unsure if I'm doing it right, so I want to ensure how to reproduce the issue you are facing. Is this the flow:
https://github.com/estruyf/vscode-front-matter/assets/2900833/d8973921-1ddb-4929-a89e-783d4bec9bd6
By default, the `isStarted` flag is false, but it will check if the VSCode FM server terminal window is open. We might need to implement a check on the extension startup to close this terminal window if still opened on restart.
<!-- github-comment-id:1780530463 -->
My screen shot just after restart VScode and open frontmatter dashboard.
"* History Retorted" may do some something tricky.

My screen shot just after restart VScode and open frontmatter dashboard.
"* History Retorted" may do some something tricky.
<!-- github-comment-id:1780617006 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Describe the bug
isStarted flag inherited between vscode session when
"terminal.integrated.enablePersistentSessions": trueTherefore dashboard gui shows 'stop server' at start time.
To Reproduce
vscodeconfig"terminal.integrated.enablePersistentSessions": truevscodevscodeExpected behavior
isStarted flag should be
falsewhenvscodestarts.Desktop (please complete the following information):
Additional context
frontmatter: v9.3.0
VSCODE: 1.83.1
I'm unsure if I'm doing it right, so I want to ensure how to reproduce the issue you are facing. Is this the flow:
https://github.com/estruyf/vscode-front-matter/assets/2900833/d8973921-1ddb-4929-a89e-783d4bec9bd6
By default, the
isStartedflag is false, but it will check if the VSCode FM server terminal window is open. We might need to implement a check on the extension startup to close this terminal window if still opened on restart.Implemented the fix for this and it is testable in the latest beta version.
My screen shot just after restart VScode and open frontmatter dashboard.
"* History Retorted" may do some something tricky.
Thanks, this will indeed be handled by this change in the beta version.