Adding policy requires a restart of vs code to apply

[joshspicer]

Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version: 1.99
• OS Version: macOS/windows

Similar to microsoft/vscode-policy-watcher#47 but the issue is in core instead of this policy-watcher.

Steps to Reproduce:

1. Ensure you have NO configuration profiles installed for VS Code
2. Open Insiders
3. Add a configuration profile with any policy that is currently supported
4. 🐛 policy is not applied until a relaunch of VS Code

[vs-code-engineering]

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.98.2. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

[sandy081]

Seems to be a regression caused by MultiplexePolicyService

[joshspicer]

I thought i'd noticed this behavior earlier in the month (before the multiplex changes landed).

When the change lands it is probably worth testing on linux (where we wouldn't instantiate a multiplexpolicyservice, just an accountpolicyservice)

[joshspicer]

Demo of this repro'ing on macOS in today's insiders (ff52a0d):

Screen.Recording.2025-03-27.at.2.44.09.PM.mov

The underlying native policy watcher does pick up changes instantly, so the issue appears to be in vscode itself:

Screen.Recording.2025-03-27.at.2.46.38.PM.mov

[sandy081]

@joshspicer It is not easy to follow the video. Can you please share the steps to reproduce? Please also share the trace logs from main and window which contain information about policy changes.

Also, looks like chat related policies will be always overridden by the account policy right?

[joshspicer]

1. Ensure you have NO configuration profiles installed for VS Code
2. Open Insiders
3. Add a configuration profile with any policy that is currently supported (I randomly chose the chat-related policies, any policy will do and the ones I chose are not relevant)
4. 🐛 policy is not applied until a relaunch of VS Code

[joshspicer]

This issue does not repro when using the FilePolicyService in place of NativePolicyService

Screen.Recording.2025-03-28.at.10.08.30.AM.mov

[joshspicer]

Fix: #244996

This bug has been here for a while, but I think it went under the radar due to the lack of policies that existed. This month we have many more policies contributed from many places, and therefore the bug is more pronounced.

---

This is consistently the final "update" I've observed under the debugger, therefore (before the fix) only that one policy would have been watched by the native policy watcher

[TylerLeonhardt]

/closedWith 99c9c6c