Change:
); }); }); <ins> test('getBracketsInRange', () => { disposeOnReturn(store => { const doc = new AnnotatedDocument(`¹ { [ ( [ [ (  ) ] ] ) ] } { } ²`); const model = createTextModelWithColorizedBracketPairs(store, doc.text); assert.deepStrictEqual( model.bracketPairs .getBracketsInRange(doc.range(1, 2)) .map(b => ({ level: b.nestingLevel, levelEqualBracketType: b.nestingLevelOfEqualBracketType, range: b.range.toString() })) .toArray(), [ { level: 0, levelEqualBracketType: 0, range: "[1,2 -> 1,3]" }, { level: 1, levelEqualBracketType: 0, range: "[1,4 -> 1,5]" }, { level: 2, levelEqualBracketType: 0, range: "[1,6 -> 1,7]" }, { level: 3, levelEqualBracketType: 1, range: "[1,8 -> 1,9]" }, { level: 4, levelEqualBracketType: 2, range: "[1,10 -> 1,11]" }, { level: 5, levelEqualBracketType: 1, range: "[1,12 -> 1,13]" }, { level: 5, levelEqualBracketType: 1, range: "[1,15 -> 1,16]" }, { level: 4, levelEqualBracketType: 2, range: "[1,17 -> 1,18]" }, { level: 3, levelEqualBracketType: 1, range: "[1,19 -> 1,20]" }, { level: 2, levelEqualBracketType: 0, range: "[1,21 -> 1,22]" }, { level: 1, levelEqualBracketType: 0, range: "[1,23 -> 1,24]" }, { level: 0, levelEqualBracketType: 0, range: "[1,25 -> 1,26]" }, { level: 0, levelEqualBracketType: 0, range: "[1,27 -> 1,28]" }, { level: 0, levelEqualBracketType: 0, range: "[1,29 -> 1,30]" }, ] ); }); }); </ins> }); function bracketPairToJSON(pair: BracketPairInfo): unknown {

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.71.0 OS Version: Ubuntu 20.04, Linux x64 5.15.0-46-generic snap Steps to Reproduce: VSC (possibly with extensions disabled) any C++ workspace or any folder with C++ files. "editor.bracketPairColorization.independentColorPoolPerBracketType": true pair colorization stopped working - all brackets are yellow regardless of the nesting level or bracket type. Version: 1.71.0 Commit: Date: 2022-09-01T07:25:10.472Z Electron: 19.0.12 Chromium: 102.0.5005.167 16.14.2 V8: 10.2.154.15-electron.0 OS: Linux x64 5.15.0-46-generic snap Sandboxed: No
This is weird, we didn't change anything there. It works if you downgrade to the previous version of VS Code?
Yse, I have met the same problem after updating to 1.71.0
Same problem here on 1.71.0 on Windows 10.
Same issue here with both typescript and html templates.... All brackets regardless of nesting are all yellow after auto-updating to 1.71.0 Reverting to 1.70.2 and restoring synced settings from 1wk ago resolved my issue.
On an interesting note for me at least, the bracket colors are all yellow, but if I enable the guide lines they have the correct color !

I'm having the same issue... If I set to all brackets will always have the color defined for regardless of nesting.
Turning on or off doesn't make a difference for me, though it does change how the indentation is colored. I've messed around with , , , setting different brackets, etc, nothing changes the outcome, all brackets are . The indentation lines have the correct color, though. <details<summary"editor.bracketPairColorization.independentColorPoolPerBracketType": true</summary<img width="621" alt="image" src="https://user-"</details<details<summary"editor.bracketPairColorization.independentColorPoolPerBracketType": false</summary<img width="623" alt="image" src="https://user-"</details
Anyone up for a bugfix PR? Unfortunately, I was very busy with the merge editor this milestone.
vscode 1.72 still has this problem
I have the same issue.
same problem in
Sorry for the inconvenience. I fixed the bug and some tests to prevent future regressions. Verification steps: !