Gate compilation config debug logs behind ENABLE_COMPILE_CONFIG_LOGGING

[Copilot]

LSP was emitting debug messages on every compilation (~every keystroke), cluttering the console with messages like "main file found using client provided entrypoint" and config resolution details.

Changes

• Added ENABLE_COMPILE_CONFIG_LOGGING environment variable following existing patterns (ENABLE_SERVER_COMPILE_LOGGING, ENABLE_UPDATE_MANAGER_LOGGING)
• Gated debug logs in:
  • entrypoint-resolver.ts - entrypoint discovery messages (4 callsites)
  • compile-service.ts - config resolution messages (5 callsites)
  • serverlib.ts - YAML completion path (passes conditional logger to yaml-resolver.ts)

Usage

Debug logs are suppressed by default. Enable when troubleshooting:

ENABLE_COMPILE_CONFIG_LOGGING=true

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• telemetry.astro.build
  • Triggering command: /usr/local/bin/node node /home/REDACTED/work/typespec/typespec/website/node_modules/.bin/../astro/astro.js build sh -c ebsite/src/content/docs/docs/emitters/openapi3/reference node p/node_modules/.bin/node -p . st/node-gyp-bin/tspd doc . --enable-experimental --output-dir ../../website/src/content/docs/docs/emitters/servers/http-server-csharp/reference --skip-js sed p/no�� uild.js node _modules/pnpm/dist/node-gyp-bin/sh /library-linter sh sh node tp/reference (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>LSP spamming irrelevent debug message in console</issue_title>
<issue_description>

Multiple message show up on every compilation which happens about every keypress(with debounce)</issue_description>

<agent_instructions>the env var 'ENABLE_SERVER_COMPILE_LOGGING' and 'ENABLE_UPDATE_MANAGER_LOGGING' can be used as an example. use the same way to control the log around the configuration of server compile</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@RodgeFu Consider disabling them by default and have an env var (ENABLE_COMPILE_CONFIG_LOGGING) to enable it when needed (i.e. when troubleshooting compile related issues). Just like what we do with 'ENABLE_UPDATE_MANAGER_LOGGING'

• Fixes LSP spamming irrelevent debug message in console #9310

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.