.qmllint.ini not being respected by VSCode Problems tab

[jmfrullo]

Describe the Bug I see in the extension description that there should be support for a .qmllint.ini configuration file (for PySide6 >= 6.3.0); however, I have included a .qmllint.ini file in the root of my project, and I still see linting errors that should be ignored in my Problems tab of VSCode. See the screenshots below, but I have set the Unqualified access warning to "disable". When I run qmllint via the CLI (ie. pyside6-qmllint) I do not see any unqualified access errors, as expected, but I do continue to see them in the Problems tab. I also do not see anything in the Settings of the extension that allow us to pass that configuration file path to qmllint or pass additional CLI parameters to it or anything. Please advise.

To Reproduce Steps to reproduce the behavior:

1. Installed the extension
2. Saw "unqualified access" warnings in the Problems tab
3. Added a .qmllint.ini file (by running the pyside6-qmllint --write-defaults command)
4. Modified the .qmllint.ini file to have "unqualified access" as "disable"
5. Continued to see the warnings in Problems tab; however, running pyside6-qmllint on a file does not show these unqualified warnings

Expected Behavior A clear and concise description of what you expected to
happen.

Screenshots If applicable, add screenshots to help explain your problem.
You can see the VSCode Warnings showing up for the Unqualified Access issue:

But running the same command via CLI does not show the Unqualified Access issue:

Environment

• OS: Windows 10
• Visual Studio Code version: 1.85.2
• PySide version: 6.5.3
• Python version: 3.11.1
• Qt for Python version: 7.6.0

Extension Configurations
Default configuration.

Additional context N/A

[jtc42]

This seems to be an upstream issue, see https://bugreports.qt.io/browse/QTBUG-127602