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

[BUG] Incorrect Notification State When Server Fails to Start #220

Open
midays opened this issue Jan 20, 2025 · 0 comments
Open

[BUG] Incorrect Notification State When Server Fails to Start #220

midays opened this issue Jan 20, 2025 · 0 comments

Comments

@midays
Copy link

midays commented Jan 20, 2025

Description:

When the server fails to start, the notification Initializing Kai: Sending 'initialize' request to RPC Server continues to indicate that the server is initializing. However, the output console correctly logs that the server failed to start due to a ModuleNotFoundError or other issues.

Steps to Reproduce:

  1. Attempt to start the server.
  2. Observe the notification state and the output console.

Expected Behavior:
The notification should reflect the server failure immediately upon detecting the error.

Actual Behavior:
The notification misleadingly shows that the server is still initializing, even though the console logs the failure.

Environment:

OS: Windows
Plugin Version: 0.0.4

Additional Info:
this behavior is noticed when the startup failed due to this bug: [BUG] Binaries Generated in the Release Do Not Work on Windows

Image

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

No branches or pull requests

1 participant