[Bug]: Language Server unresponsive after including a cyclic dependency

[malinthar]

Description

$subject as depicted below

Steps to Reproduce

No response

Affected Version(s)

No response

OS, DB, other environment details and versions

No response

Related area

-> Compilation

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

[azinneera]

When there is a cyclic dependency, the compilation cannot be continued, so it is a crashed state. Hence this behavior is expected. The diagnostic is issued to indicate the cyclic dependency which can be used to resolve the error.

[malinthar]

When there is a cyclic dependency, the compilation cannot be continued, so it is a crashed state. Hence this behavior is expected. The diagnostic is issued to indicate the cyclic dependency which can be used to resolve the error.

I see. However, the VSCode user might not know about the crashed state unless they look at the problems tab. The LS may seem unresponsive because features such as completion, code-action will not work without the compilation. To avoid the confusion we can send a notification from the LS side when the compilation is in a crashed state specifying a user error.