Azure / Azure/bicep

Investigate options for logging LanguageServer stderr/stout/exit codes

Open
#10,172 1 comment 0 reactions 0 assignees View on GitHub
enhancement tech debt
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 21m
Merged PRs (30d)
79

Description

We don't have anything from the logs captured for #10113 to figure out the root cause. Having the stderr + exit code might enable us to better troubleshoot activation failures.

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by tracing how LanguageServer activation failures are currently logged and compare the available information with the failure reported in #10113. Done means documenting viable options for capturing stderr, stdout, and exit codes so activation failures can be investigated.

Written by the indexing model from the issue text.

Assessment

Domain
devtools, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.