Avoid 0ms interval rescheduling in configuration service

[Copilot]

Fixes #259517

This change prevents an infinite loop of immediate scheduler execution when ASSIGNMENT_REFETCH_INTERVAL is set to 0 (meaning no polling should occur).

Problem

The ConfigurationDefaultOverridesContribution class was unconditionally rescheduling its experimental settings scheduler, even when ASSIGNMENT_REFETCH_INTERVAL was set to 0. This caused:

• Infinite loop of immediate scheduler execution
• Potential performance issues
• Unbounded queuing of experimental settings processing

Solution

Added a conditional check before rescheduling the scheduler:

this.autoRefetchExperimentalSettingsScheduler = new RunOnceScheduler(() => {
    this.processExperimentalSettings(this.autoRefetchExperimentalSettings, true);
    if (ASSIGNMENT_REFETCH_INTERVAL !== 0) {
        // TODO@sandy081 wait for the promise returned by processExperimentalSettings to avoid unbounded queuing
        this.autoRefetchExperimentalSettingsScheduler.schedule();
    }
}, ASSIGNMENT_REFETCH_INTERVAL);

When ASSIGNMENT_REFETCH_INTERVAL is 0, the scheduler will run once but won't reschedule itself, properly implementing the "no polling" behavior.

Cherry-picked from commit d38eb0f by @hediet.

Warning

Firewall rules blocked me from connecting to one or more addresses

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

• electronjs.org
  • Triggering command: node-gyp (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)

---

💡 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.