Python doesn't fire environment changed when creating a new environment

Environment data

Language Server version: 2023.4.10
OS and version: win32 x64 22621.1413
Python version (and distribution if applicable, e.g. Anaconda): 3.10.10
python.analysis.indexing: true
python.analysis.typeCheckingMode: off

Code Snippet
import pip
import github

Repro Steps

Create an empty folder and open it in vscode.
Run Python: Create Environment... -> Venv.
After the environment is ready and python extension has selected it, install any package in the environment, e.g. pip install github.
Create a new python file in the folder and add 2 imports into it: import pip and import github.

Expected behavior
Pylance uses the newly created environment.
Pressing F12 (Go To Definition) on pip opens pip's __init__.py from the venv. Pylance doesn't show Import "github" could not be resolved error.
Actual behavior
Pylance continues to use global environment, even though after creating the environment python extension shows We have selected the following environment: \path\to\venv notification and the status bar shows that the venv interpreter is selected.
Pressing F12 (Go To Definition) on pip opens pip's __init__.py from the global environment. Pylance shows Import "github" could not be resolved error because (according to logs) it still tries to find the package in the global environment.
To make pylance actually use the created environment, the user have to do one of the following:

Run Python: Restart Language Server.
Run Developer: Reload Window.
Reselect the interpreter used.
Change any pylance setting.

Logs

I've had to remove 'add' and 'change' evens between [Info  - 4:28:17 PM] and [Info  - 4:28:50 PM] because github limits body to 65536 characters. These events were triggered by Python: Create Environment....
(Client) New Client enabled
[Info  - 4:28:14 PM] (7940) Pylance language server 2023.4.10 (pyright d7616109) starting
[Info  - 4:28:14 PM] (7940) Server root directory: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist
[Info  - 4:28:14 PM] (7940) Starting service instance "issue"
[Info  - 4:28:14 PM] (7940) Auto-indent enabled
(7940) No configuration file found.
(7940) No pyproject.toml file found.
[Warn  - 4:28:14 PM] (7940) stubPath c:\Users\mpekurin\Downloads\issue\typings is not a valid directory.
(7940) Assuming Python platform Windows
[Info  - 4:28:14 PM] (7940) Search paths for c:\Users\mpekurin\Downloads\issue
[Info  - 4:28:14 PM] (7940)   c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib
[Info  - 4:28:14 PM] (7940)   c:\Users\mpekurin\Downloads\issue
[Info  - 4:28:14 PM] (7940)   c:\Users\mpekurin\Downloads\issue\typings
[Info  - 4:28:14 PM] (7940)   c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stubs\...
[Info  - 4:28:14 PM] (7940)   c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\bundled\stubs
[Info  - 4:28:14 PM] (7940)   c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\DLLs
[Info  - 4:28:14 PM] (7940)   c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib
[Info  - 4:28:14 PM] (7940)   c:\Users\mpekurin\AppData\Local\Programs\Python\Python310
[Info  - 4:28:14 PM] (7940)   c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\site-packages
[Info  - 4:28:14 PM] (7940) Adding fs watcher for library directories:
 C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\DLLs
C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\lib
C:\Users\mpekurin\AppData\Local\Programs\Python\Python310
C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\lib\site-packages
[Info  - 4:28:14 PM] (7940) Adding fs watcher for directories:
 c:\Users\mpekurin\Downloads\issue
(7940) Searching for source files
[Info  - 4:28:14 PM] (7940) No source files found.
[Info  - 4:28:15 PM] (7940) Background analysis(1) root directory: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist
[Info  - 4:28:15 PM] (7940) Background analysis(1) started
(7940) Background analysis message: setConfigOptions
(7940) Background analysis message: setImportResolver
(7940) Background analysis message: ensurePartialStubPackages
(7940) Background analysis message: setConfigOptions
(7940) Background analysis message: setTrackedFiles
(7940) Background analysis message: markAllFilesDirty
(7940) Background analysis message: analyze
[Info  - 4:28:17 PM] (7940) SourceFile: Received fs event 'add' for path 'c:\Users\mpekurin\Downloads\issue\.venv\Lib\site-packages\distutils-precedence.pth'
[Info  - 4:28:50 PM] (7940) SourceFile: Received fs event 'change' for path 'c:\Users\mpekurin\Downloads\issue\.venv\Lib\site-packages\aiohttp-3.8.1.dist-info\RECORD'
(7940) Background analysis message: setFileOpened
(7940) [FG] parsing: c:\Users\mpekurin\Downloads\issue\issue.py (106ms)
(7940) [FG] parsing: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\builtins.pyi [fs read 16ms] (423ms)
(7940) [FG] binding: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\builtins.pyi (120ms)
(7940) [FG] binding: c:\Users\mpekurin\Downloads\issue\issue.py (0ms)
(7940) Background analysis message: analyze
(7940) [BG(1)] analyzing: c:\Users\mpekurin\Downloads\issue\issue.py ...
(7940) [BG(1)]   parsing: c:\Users\mpekurin\Downloads\issue\issue.py (196ms)
(7940) [BG(1)]   parsing: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\builtins.pyi [fs read 21ms] (350ms)
[Info  - 4:29:05 PM] (7940) SourceFile: Received fs event 'add' for path 'c:\Users\mpekurin\Downloads\issue\issue.py'
(7940) Searching for source files
[Info  - 4:29:05 PM] (7940) Found 1 source file
(7940) [BG(1)]   binding: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\builtins.pyi (112ms)
(7940) [BG(1)]   binding: c:\Users\mpekurin\Downloads\issue\issue.py (0ms)
(7940) [BG(1)]   checking: c:\Users\mpekurin\Downloads\issue\issue.py (9ms)
(7940) [BG(1)] analyzing: c:\Users\mpekurin\Downloads\issue\issue.py (705ms)
(7940) Background analysis message: getSemanticTokens full
(7940) [BG(1)] getSemanticTokens full at c:\Users\mpekurin\Downloads\issue\issue.py (1ms)
(7940) Background analysis message: invalidateAndForceReanalysis
(7940) Background analysis message: setConfigOptions
(7940) Background analysis message: setTrackedFiles
(7940) Background analysis message: markAllFilesDirty
(7940) Background analysis message: analyze
(7940) [BG(1)] analyzing: c:\Users\mpekurin\Downloads\issue\issue.py ...
(7940) [BG(1)]   parsing: c:\Users\mpekurin\Downloads\issue\issue.py (123ms)
(7940) [BG(1)]   parsing: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\builtins.pyi [fs read 3ms] (134ms)
[Info  - 4:29:05 PM] (7940) Indexer background runner(2) root directory: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist (index)
[Info  - 4:29:05 PM] (7940) Indexing(2) started
(7940) [BG(1)]   binding: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\builtins.pyi (80ms)
(7940) [BG(1)]   binding: c:\Users\mpekurin\Downloads\issue\issue.py (0ms)
(7940) [BG(1)]   checking: c:\Users\mpekurin\Downloads\issue\issue.py (24ms)
(7940) [BG(1)] analyzing: c:\Users\mpekurin\Downloads\issue\issue.py (363ms)
(7940) Background analysis message: resumeAnalysis
(7940) [BG(1)] indexing: c:\Users\mpekurin\Downloads\issue\issue.py (1ms)
(7940) Background analysis message: resumeAnalysis
(7940) [IDX(2)] scan packages c:\Users\mpekurin\Downloads\issue ...
(7940) [IDX(2)]   read stdlib indices (336ms)
(7940) Background analysis message: getSemanticTokens range
(7940) [BG(1)] getSemanticTokens range 0:0 - 0:0 at c:\Users\mpekurin\Downloads\issue\issue.py (0ms)
(7940) [FG] parsing: c:\Users\mpekurin\Downloads\issue\issue.py (104ms)
(7940) [FG] parsing: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\builtins.pyi [fs read 3ms] (172ms)
(7940) [FG] binding: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\builtins.pyi (27ms)
(7940) [FG] binding: c:\Users\mpekurin\Downloads\issue\issue.py (0ms)
(7940) [IDX(2)] scan packages c:\Users\mpekurin\Downloads\issue (1552ms)
[Info  - 4:29:06 PM] (7940) scanned(2) 14 files over 1 exec env
(7940) IntelliCode model c:\Users\mpekurin\.vscode\extensions\visualstudioexptteam.vscodeintellicode-1.2.30\dist\bundledModels\python_intellisense-members-lstm-pylance
(7940) [IDX(2)] index packages c:\Users\mpekurin\Downloads\issue ...
(7940) [IDX(2)]   index execution environment c:\Users\mpekurin\Downloads\issue ...
(7940) [IDX(2)]     parsing: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stubs\setuptools\setuptools\__init__.pyi [fs read 1ms] (147ms)
(7940) [IDX(2)]     parsing: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\builtins.pyi [fs read 3ms] (112ms)
(7940) [IDX(2)]     binding: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\builtins.pyi (26ms)
(7940) [IDX(2)]     binding: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stubs\setuptools\setuptools\__init__.pyi (1ms)
(7940) [IDX(2)]     indexing: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stubs\setuptools\setuptools\__init__.pyi ...
(7940) [IDX(2)]       parsing: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stubs\setuptools\setuptools\_deprecation_warning.pyi [fs read 3ms] (11ms)
(7940) [IDX(2)]       binding: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stubs\setuptools\setuptools\_deprecation_warning.pyi (0ms)
(7940) [IDX(2)]       parsing: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stubs\setuptools\setuptools\depends.pyi [fs read 1ms] (2ms)
(7940) [IDX(2)]       binding: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stubs\setuptools\setuptools\depends.pyi (0ms)
(7940) [IDX(2)]       parsing: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stubs\setuptools\setuptools\dist.pyi [fs read 0ms] (14ms)
(7940) [IDX(2)]       binding: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stubs\setuptools\setuptools\dist.pyi (1ms)
(7940) [IDX(2)]       parsing: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stubs\setuptools\setuptools\extension.pyi [fs read 0ms] (11ms)
(7940) [IDX(2)]       binding: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stubs\setuptools\setuptools\extension.pyi (0ms)
(7940) [IDX(2)]     indexing: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stubs\setuptools\setuptools\__init__.pyi [found 12] (47ms)
(7940) [IDX(2)]     parsing: c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\xml\__init__.py [fs read 0ms] (4ms)
(7940) [IDX(2)]     binding: c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\xml\__init__.py (0ms)
(7940) [IDX(2)]     indexing: c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\xml\__init__.py [found 0] (1ms)
(7940) [IDX(2)]     parsing: c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\site-packages\pip\__init__.py [fs read 0ms] (0ms)
(7940) [IDX(2)]     binding: c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\site-packages\pip\__init__.py (0ms)
(7940) [IDX(2)]     indexing: c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\site-packages\pip\__init__.py [found 2] (17ms)
(7940) [IDX(2)]   index execution environment c:\Users\mpekurin\Downloads\issue [found 94 in 4 files] (380ms)
(7940) [IDX(2)] index packages c:\Users\mpekurin\Downloads\issue [found 94 in 1 exec envs] (396ms)
[Info  - 4:29:06 PM] (7940) indexed(2) 4 files over 1 exec env
[Info  - 4:29:06 PM] (7940) Indexing finished(2).
(7940) Loading ONNX runtime...
(7940) Loaded ONNX runtime. Creating IntelliCode session...
2023-04-06 16:29:08.595877 [I:onnxruntime:, inference_session.cc:263 operator()] Flush-to-zero and denormal-as-zero are off
2023-04-06 16:29:08.597049 [I:onnxruntime:, inference_session.cc:271 ConstructorCommon] Creating and using per session threadpools since use_per_session_threads_ is true
2023-04-06 16:29:08.597738 [I:onnxruntime:, inference_session.cc:292 ConstructorCommon] Dynamic block base set to 0
2023-04-06 16:29:08.681408 [I:onnxruntime:, inference_session.cc:1222 Initialize] Initializing session.
2023-04-06 16:29:08.681598 [I:onnxruntime:, inference_session.cc:1259 Initialize] Adding default CPU execution provider.
2023-04-06 16:29:08.687679 [I:onnxruntime:, reshape_fusion.cc:42 ApplyImpl] Total fused reshape node count: 0
2023-04-06 16:29:08.689250 [I:onnxruntime:, graph.cc:3553 CleanUnusedInitializersAndNodeArgs] Removing NodeArg 'rnn/transpose'. It is no longer used by any node.
2023-04-06 16:29:08.689428 [I:onnxruntime:, graph.cc:3553 CleanUnusedInitializersAndNodeArgs] Removing NodeArg 'Gather_out0'. It is no longer used by any node.
2023-04-06 16:29:08.689573 [I:onnxruntime:, graph.cc:3553 CleanUnusedInitializersAndNodeArgs] Removing NodeArg 'Transpose_out0'. It is no longer used by any node.
2023-04-06 16:29:08.690099 [I:onnxruntime:, reshape_fusion.cc:42 ApplyImpl] Total fused reshape node count: 0
2023-04-06 16:29:08.710533 [V:onnxruntime:, session_state.cc:1010 VerifyEachNodeIsAssignedToAnEp] Node placements
2023-04-06 16:29:08.710725 [V:onnxruntime:, session_state.cc:1013 VerifyEachNodeIsAssignedToAnEp]  All nodes placed on [CPUExecutionProvider]. Number of nodes: 59
2023-04-06 16:29:08.711195 [V:onnxruntime:, session_state.cc:66 CreateGraphInfo] SaveMLValueNameIndexMapping
2023-04-06 16:29:08.711358 [V:onnxruntime:, session_state.cc:112 CreateGraphInfo] Done saving OrtValue mappings.
2023-04-06 16:29:08.711881 [I:onnxruntime:, session_state_utils.cc:199 SaveInitializedTensors] Saving initialized tensors.
2023-04-06 16:29:08.795936 [I:onnxruntime:, session_state_utils.cc:342 SaveInitializedTensors] Done saving initialized tensors
2023-04-06 16:29:08.797329 [I:onnxruntime:, inference_session.cc:1488 Initialize] Session successfully initialized.
(7940) Created IntelliCode session.
(7940) Initialize deeplearning succeeded
(7940) Background analysis message: setFileOpened
(7940) Background analysis message: markFilesDirty
(7940) [FG] parsing: c:\Users\mpekurin\Downloads\issue\issue.py (15ms)
(7940) [FG] binding: c:\Users\mpekurin\Downloads\issue\issue.py (1ms)
(7940) Background analysis message: analyze
(7940) [BG(1)] analyzing: c:\Users\mpekurin\Downloads\issue\issue.py ...
(7940) [BG(1)]   parsing: c:\Users\mpekurin\Downloads\issue\issue.py (15ms)
(7940) [BG(1)]   binding: c:\Users\mpekurin\Downloads\issue\issue.py (0ms)
(7940) [BG(1)]   checking: c:\Users\mpekurin\Downloads\issue\issue.py ...
(7940) [BG(1)]     parsing: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\typing.pyi [fs read 1ms] (22ms)
(7940) [BG(1)]     binding: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\typing.pyi (11ms)
(7940) [BG(1)]     parsing: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\typing_extensions.pyi [fs read 1ms] (6ms)
(7940) [BG(1)]     binding: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\typing_extensions.pyi (3ms)
(7940) [BG(1)]     parsing: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\_typeshed\__init__.pyi [fs read 1ms] (38ms)
(7940) [BG(1)]     binding: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\_typeshed\__init__.pyi (8ms)
(7940) [BG(1)]     parsing: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\types.pyi [fs read 1ms] (57ms)
(7940) [BG(1)]     binding: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\types.pyi (10ms)
(7940) [BG(1)]     parsing: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\abc.pyi [fs read 0ms] (1ms)
(7940) [BG(1)]     binding: c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib\abc.pyi (0ms)
(7940) [BG(1)]     parsing: c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\site-packages\pip\__init__.py [fs read 0ms] (4ms)
(7940) [BG(1)]     binding: c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\site-packages\pip\__init__.py (1ms)
(7940) [BG(1)]   checking: c:\Users\mpekurin\Downloads\issue\issue.py (235ms)
(7940) [BG(1)] analyzing: c:\Users\mpekurin\Downloads\issue\issue.py (251ms)
(7940) Background analysis message: resumeAnalysis
(7940) [BG(1)] indexing: c:\Users\mpekurin\Downloads\issue\issue.py [found 0] (0ms)
(7940) Indexing Done: c:\Users\mpekurin\Downloads\issue\issue.py
(7940) Background analysis message: getSemanticTokens delta
(7940) [BG(1)] getSemanticTokens delta previousResultId:1680787744244 at c:\Users\mpekurin\Downloads\issue\issue.py (1ms)
(7940) Background analysis message: setFileOpened
(7940) Background analysis message: markFilesDirty
(7940) [FG] parsing: c:\Users\mpekurin\Downloads\issue\issue.py (2ms)
[Info  - 4:29:22 PM] (7940) Could not import 'github' in file 'c:\Users\mpekurin\Downloads\issue\issue.py'
[Info  - 4:29:22 PM] (7940)   Looking in stubPath 'c:\Users\mpekurin\Downloads\issue\typings'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\Downloads\issue\typings'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\Downloads\issue\typings'
[Info  - 4:29:22 PM] (7940)   Looking in root directory of execution environment 'c:\Users\mpekurin\Downloads\issue'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\Downloads\issue'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\Downloads\issue'
[Info  - 4:29:22 PM] (7940)   Finding python search paths
[Info  - 4:29:22 PM] (7940)   Executing interpreter: 'python'
[Info  - 4:29:22 PM] (7940)   Skipping 'C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\python310.zip' because it is not a valid directory
[Info  - 4:29:22 PM] (7940)   Received 4 paths from interpreter
[Info  - 4:29:22 PM] (7940)     C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\DLLs
[Info  - 4:29:22 PM] (7940)     C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\lib
[Info  - 4:29:22 PM] (7940)     C:\Users\mpekurin\AppData\Local\Programs\Python\Python310
[Info  - 4:29:22 PM] (7940)     C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\lib\site-packages
[Info  - 4:29:22 PM] (7940)   Looking in python search path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 4:29:22 PM] (7940)   Looking in python search path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 4:29:22 PM] (7940)   Looking in python search path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310'
[Info  - 4:29:22 PM] (7940)   Looking in python search path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 4:29:22 PM] (7940)   Looking in bundled stubs path 'c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\bundled\stubs'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\bundled\stubs'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\bundled\stubs'
[Info  - 4:29:22 PM] (7940)   Looking for typeshed stdlib path
[Info  - 4:29:22 PM] (7940)   Looking for typeshed stdlib path
[Info  - 4:29:22 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib'
[Info  - 4:29:22 PM] (7940)   Typeshed path not found
[Info  - 4:29:22 PM] (7940)   Looking for typeshed third-party path
[Info  - 4:29:22 PM] (7940)   Looking for typeshed stubs path
[Info  - 4:29:22 PM] (7940)   Typeshed path not found
(7940) [FG] binding: c:\Users\mpekurin\Downloads\issue\issue.py (0ms)
(7940) Background analysis message: analyze
(7940) [BG(1)] analyzing: c:\Users\mpekurin\Downloads\issue\issue.py ...
(7940) [BG(1)]   parsing: c:\Users\mpekurin\Downloads\issue\issue.py (1ms)
[Info  - 4:29:22 PM] (7940) Could not import 'github' in file 'c:\Users\mpekurin\Downloads\issue\issue.py'
[Info  - 4:29:22 PM] (7940)   Looking in stubPath 'c:\Users\mpekurin\Downloads\issue\typings'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\Downloads\issue\typings'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\Downloads\issue\typings'
[Info  - 4:29:22 PM] (7940)   Looking in root directory of execution environment 'c:\Users\mpekurin\Downloads\issue'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\Downloads\issue'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\Downloads\issue'
[Info  - 4:29:22 PM] (7940)   Finding python search paths
[Info  - 4:29:22 PM] (7940)   Executing interpreter: 'python'
[Info  - 4:29:22 PM] (7940)   Skipping 'C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\python310.zip' because it is not a valid directory
[Info  - 4:29:22 PM] (7940)   Received 4 paths from interpreter
[Info  - 4:29:22 PM] (7940)     C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\DLLs
[Info  - 4:29:22 PM] (7940)     C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\lib
[Info  - 4:29:22 PM] (7940)     C:\Users\mpekurin\AppData\Local\Programs\Python\Python310
[Info  - 4:29:22 PM] (7940)     C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\lib\site-packages
[Info  - 4:29:22 PM] (7940)   Looking in python search path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 4:29:22 PM] (7940)   Looking in python search path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 4:29:22 PM] (7940)   Looking in python search path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310'
[Info  - 4:29:22 PM] (7940)   Looking in python search path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 4:29:22 PM] (7940)   Looking in bundled stubs path 'c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\bundled\stubs'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\bundled\stubs'
[Info  - 4:29:22 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\bundled\stubs'
[Info  - 4:29:22 PM] (7940)   Looking for typeshed stdlib path
[Info  - 4:29:22 PM] (7940)   Looking for typeshed stdlib path
[Info  - 4:29:22 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib'
[Info  - 4:29:22 PM] (7940)   Typeshed path not found
[Info  - 4:29:22 PM] (7940)   Looking for typeshed third-party path
[Info  - 4:29:22 PM] (7940)   Looking for typeshed stubs path
[Info  - 4:29:22 PM] (7940)   Typeshed path not found
(7940) [BG(1)]   binding: c:\Users\mpekurin\Downloads\issue\issue.py (1ms)
(7940) [BG(1)]   checking: c:\Users\mpekurin\Downloads\issue\issue.py (24ms)
(7940) [BG(1)] analyzing: c:\Users\mpekurin\Downloads\issue\issue.py (27ms)
(7940) Background analysis message: getDiagnosticsForRange
(7940) Background analysis message: resumeAnalysis
(7940) [BG(1)] indexing: c:\Users\mpekurin\Downloads\issue\issue.py [found 0] (0ms)
(7940) Indexing Done: c:\Users\mpekurin\Downloads\issue\issue.py
(7940) Background analysis message: getDiagnosticsForRange
(7940) Background analysis message: getDiagnosticsForRange
(7940) Background analysis message: getDiagnosticsForRange
(7940) Background analysis message: getSemanticTokens delta
(7940) [BG(1)] getSemanticTokens delta previousResultId:1680787755158 at c:\Users\mpekurin\Downloads\issue\issue.py (1ms)
(7940) Background analysis message: setFileOpened
(7940) Background analysis message: markFilesDirty
(7940) [FG] parsing: c:\Users\mpekurin\Downloads\issue\issue.py (0ms)
[Info  - 4:29:34 PM] (7940) Could not import 'github' in file 'c:\Users\mpekurin\Downloads\issue\issue.py'
[Info  - 4:29:34 PM] (7940)   Looking in stubPath 'c:\Users\mpekurin\Downloads\issue\typings'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\Downloads\issue\typings'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\Downloads\issue\typings'
[Info  - 4:29:34 PM] (7940)   Looking in root directory of execution environment 'c:\Users\mpekurin\Downloads\issue'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\Downloads\issue'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\Downloads\issue'
[Info  - 4:29:34 PM] (7940)   Finding python search paths
[Info  - 4:29:34 PM] (7940)   Executing interpreter: 'python'
[Info  - 4:29:34 PM] (7940)   Skipping 'C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\python310.zip' because it is not a valid directory
[Info  - 4:29:34 PM] (7940)   Received 4 paths from interpreter
[Info  - 4:29:34 PM] (7940)     C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\DLLs
[Info  - 4:29:34 PM] (7940)     C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\lib
[Info  - 4:29:34 PM] (7940)     C:\Users\mpekurin\AppData\Local\Programs\Python\Python310
[Info  - 4:29:34 PM] (7940)     C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\lib\site-packages
[Info  - 4:29:34 PM] (7940)   Looking in python search path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 4:29:34 PM] (7940)   Looking in python search path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 4:29:34 PM] (7940)   Looking in python search path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310'
[Info  - 4:29:34 PM] (7940)   Looking in python search path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 4:29:34 PM] (7940)   Looking in bundled stubs path 'c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\bundled\stubs'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\bundled\stubs'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\bundled\stubs'
[Info  - 4:29:34 PM] (7940)   Looking for typeshed stdlib path
[Info  - 4:29:34 PM] (7940)   Looking for typeshed stdlib path
[Info  - 4:29:34 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib'
[Info  - 4:29:34 PM] (7940)   Typeshed path not found
[Info  - 4:29:34 PM] (7940)   Looking for typeshed third-party path
[Info  - 4:29:34 PM] (7940)   Looking for typeshed stubs path
[Info  - 4:29:34 PM] (7940)   Typeshed path not found
(7940) [FG] binding: c:\Users\mpekurin\Downloads\issue\issue.py (1ms)
(7940) Background analysis message: analyze
(7940) [BG(1)] analyzing: c:\Users\mpekurin\Downloads\issue\issue.py ...
(7940) [BG(1)]   parsing: c:\Users\mpekurin\Downloads\issue\issue.py (2ms)
[Info  - 4:29:34 PM] (7940) Could not import 'github' in file 'c:\Users\mpekurin\Downloads\issue\issue.py'
[Info  - 4:29:34 PM] (7940)   Looking in stubPath 'c:\Users\mpekurin\Downloads\issue\typings'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\Downloads\issue\typings'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\Downloads\issue\typings'
[Info  - 4:29:34 PM] (7940)   Looking in root directory of execution environment 'c:\Users\mpekurin\Downloads\issue'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\Downloads\issue'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\Downloads\issue'
[Info  - 4:29:34 PM] (7940)   Finding python search paths
[Info  - 4:29:34 PM] (7940)   Executing interpreter: 'python'
[Info  - 4:29:34 PM] (7940)   Skipping 'C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\python310.zip' because it is not a valid directory
[Info  - 4:29:34 PM] (7940)   Received 4 paths from interpreter
[Info  - 4:29:34 PM] (7940)     C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\DLLs
[Info  - 4:29:34 PM] (7940)     C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\lib
[Info  - 4:29:34 PM] (7940)     C:\Users\mpekurin\AppData\Local\Programs\Python\Python310
[Info  - 4:29:34 PM] (7940)     C:\Users\mpekurin\AppData\Local\Programs\Python\Python310\lib\site-packages
[Info  - 4:29:34 PM] (7940)   Looking in python search path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\DLLs'
[Info  - 4:29:34 PM] (7940)   Looking in python search path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib'
[Info  - 4:29:34 PM] (7940)   Looking in python search path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310'
[Info  - 4:29:34 PM] (7940)   Looking in python search path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\AppData\Local\Programs\Python\Python310\Lib\site-packages'
[Info  - 4:29:34 PM] (7940)   Looking in bundled stubs path 'c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\bundled\stubs'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve stub package using root path 'c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\bundled\stubs'
[Info  - 4:29:34 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\bundled\stubs'
[Info  - 4:29:34 PM] (7940)   Looking for typeshed stdlib path
[Info  - 4:29:34 PM] (7940)   Looking for typeshed stdlib path
[Info  - 4:29:34 PM] (7940)   Attempting to resolve using root path 'c:\Users\mpekurin\.vscode\extensions\ms-python.vscode-pylance-2023.4.10\dist\typeshed-fallback\stdlib'
[Info  - 4:29:34 PM] (7940)   Typeshed path not found
[Info  - 4:29:34 PM] (7940)   Looking for typeshed third-party path
[Info  - 4:29:34 PM] (7940)   Looking for typeshed stubs path
[Info  - 4:29:34 PM] (7940)   Typeshed path not found
(7940) [BG(1)]   binding: c:\Users\mpekurin\Downloads\issue\issue.py (0ms)
(7940) [BG(1)]   checking: c:\Users\mpekurin\Downloads\issue\issue.py (24ms)
(7940) [BG(1)] analyzing: c:\Users\mpekurin\Downloads\issue\issue.py (29ms)
(7940) Background analysis message: resumeAnalysis
(7940) [BG(1)] indexing: c:\Users\mpekurin\Downloads\issue\issue.py [found 0] (0ms)
(7940) Indexing Done: c:\Users\mpekurin\Downloads\issue\issue.py
[Info  - 4:29:34 PM] (7940) SourceFile: Received fs event 'change' for path 'c:\Users\mpekurin\Downloads\issue\issue.py'
(7940) Background analysis message: markFilesDirty
(7940) Background analysis message: analyze
(7940) Background analysis message: getDiagnosticsForRange
(7940) Background analysis message: getDiagnosticsForRange
(7940) Background analysis message: getSemanticTokens delta
(7940) [BG(1)] getSemanticTokens delta previousResultId:1680787763034 at c:\Users\mpekurin\Downloads\issue\issue.py (1ms)

Python extension is 2023.6.0. I'll check if the issue persist in older versions.

Thanks for the bug report! We investigate issues in order based on priority and severity, which includes the impact it has on your ability to use the extension to do productive work, and the number of people affected. If other users come forward and leave a comment demonstrating they are seeing/reproducing the problem then we will raise this issue's priority. Thanks for understanding and the patience!

Yep. The path wasn't changed according to Python Language Server output but it was changed according to Python output:

Given the path is changed event should be fired. Perhaps language server component doesn't subscribe to it correctly.
Reassigning to LS as things look good from environment side, we've to make sure pythonPath is correctly which probably happens here: https://github.com/microsoft/vscode-python/blob/377067fd67336c9d209f3f82a9def86cceed1f68/src/client/activation/languageClientMiddlewareBase.ts#L90


Release branch diff with upstream trunk

Should not merge it, only for review

/test post-test-infra-test-all

/assign lijie0123

/cc @lijie0123
ignore, only for test

/cc lijie0123

/remove-lifecycle stale

/test ?

/test all


UXTools version updated

[The version of UXTools is updated to UXTools.0.10.0 and there is no BP_ButtonHoloLens2 in it. Can the tutorial get updated? Thanks.]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ba90317f-fc2e-1af2-dee1-b367368ea697
Version Independent ID: 37bfc738-80d9-faba-f75e-0651a7b72b74
Content: 5. Adding a button & resetting piece locations - Mixed Reality
Content Source: mixed-reality-docs/mr-dev-docs/develop/unreal/tutorials/unreal-uxt-ch5.md
Product: mixed-reality
Technology: mr-dev
GitHub Login: @hferrone
Microsoft Alias: v-hferrone

I have tried to combine both UXTools.0.10.0 and UXTools.0.9.0 and put it in the Plugins folder. The BP_ButtonHololens2 blueprint is shown as 'Blueprint Bad' instead of the blue icon shown in the tutorial. Can anyone please advise?

Hi @Eddiechui, we've got an update coming for all our tutorials to use UXTools 0.10. You'll have to hold tight for the moment.
@sw5813 Can you assist in any way?

Sure I can wait. Thanks!

@Eddiechui - the tutorial update to use UXT 0.10 is now live!


Add regkey AlwaysUseMSOAuthForAutoDiscover

HKEY_CURRENT_USER\Software\Microsoft\Exchange AlwaysUseMSOAuthForAutoDiscover 0x1
https://docs.microsoft.com/en-us/outlook/troubleshoot/authentication/outlook-prompt-password-modern-authentication-enabled

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: aac88f29-99a5-317d-2686-cc9534194a19
Version Independent ID: 753c4eff-ddb3-6261-35f9-4a60b65d7147
Content: Enable Modern Authentication for Office 2013 on Windows devices - Microsoft 365 admin
Content Source: microsoft-365/admin/security-and-compliance/enable-modern-authentication.md
Service: o365-administration
GitHub Login: @Sirkkuw
Microsoft Alias: sirkkuw

@trudolf-msft Thank you for the feedback. You are correct, we need to create or enable AlwaysUseMSOAuthForAutoDiscover in some scenarios. I have added this to the related article section via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/3761
Thanks
Sri

@msbemba Thank you very much for the contribution and updating the documentation with PR. @trudolf-msft Hope this update is helpful for you. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


add an ark bug command

This PR adds the ark bug subcommand, which gathers a few bits of information and opens a new browser window with the Github issue template partially populated.

some of this is based on the existing ./hack/update-* and ./hack/verify-* scripts, so hopefully it's not too off base.

The Github issue golang template is stored as a constant in pkg/cmd/cli/bug/bug.go.

I experimented with using a standalone template file, but ran into a backtick escaping nightmare and ETOOCOMPLEX.

The hack/update-generated-issue-template.sh script renders the template (without populating any template vars) to .github/ISSUE_TEMPLATE/bug_report.md, and the hack/verify-generated-issue-template.sh will ensure that the bug_report.md file wasn't updated by hand. This will happen automatically during testing by way of ./hack/verify-all.sh.

This means that changes to the issue template must be made in pkg/cmd/cli/bug/bug.go.

I realize that outside of the ./hack/verify-generated-issue-template.sh script, there isn't any testing. I'm open to suggestions on ways to test this without jumping through too many hoops :-)

I experimented with downloading the template, however I feel as though it's better to embed directly into the binary as the struct or the template itself could change and cause a mismatch between ark client versions. One way around this is to link a particular hosted version, but it seems like overkill. Also, it's hard to submit a PR that depends on a hosted file that's in the same PR :-)

Eventually, this could include an ark server version via #770

see also https://github.com/heptio/ark/pull/713
Closes #578

@carlisia thank you for the insightful review (and on a weekend no less!). Changes pushed.

Awesome, thank you  🎉. Let's get one more 👍 from the team.

troubleshooting.md updated. Thanks for the review @nrb!


Prevents _User lock out when setting ACL on signup or afterwards

When creating and updating a user, ever set R/W on the user.
Ran the test against parse.com to make sure we match behaviours.
fixes: #1390

Current coverage is 92.80%

Merging #1429 into master will not affect coverage as of 1a24b30

@@            master   #1429   diff @@
======================================
  Files           86      86
  Stmts         5460    5464     +4
  Branches      1007    1009     +2
  Methods          0       0
======================================
+ Hit           5067    5071     +4
  Partial         10      10
  Missed         383     383

Review entire Coverage Diff as of 1a24b30

Powered by Codecov. Updated on successful CI builds.


bad doc

The man cannot handle everything on his own. Instead of bringing up this issue here, you should make a correction

Hi, I have a good experience and working long time with w2ui. Can I contribute by correcting the document first. I also can fix some minor error. How can I contribute?

Hi, I have a good experience and working long time with w2ui. Can I contribute by correcting the document first. I also can fix some minor error. How can I contribute? I also can contribute some good example form my work.

My personal opinion is that improvements need to be made regarding the "grid". because people who use this library mostly use it for grid. I think the current search section is bad, you can work on this or anything else that comes to your mind.


Undefined array key "plugStatus" index.php on line 217

Hi there,
I'm using your script for an MeganE, so my config is $zoeph = 2;
It seems like the Plug Status can't be obtained via the cameron API?
My Apache log says:
PHP Warning:  Undefined array key "plugStatus" in /src/index.php on line 217'
Could you look into this?

I have a MeganE as well and for me it's working. Please run the debug.php and post the output here.

I have a MeganE as well and for me it's working. Please run the debug.php and post the output here.

I have another Idea, please let me verify this first. I've received the car on tuesday and it has never been charged after connecting it to myRenault. Even the the myRenault App does not show the plug status at the moment.
I think after the first charge the issue will be gone. I will keep you updated.
Nevertheless I'd like to thank you for the script! It works really good and I like the fact that I can import the data to ABRP without using expensive services like Tronity :)

Yes, this is the problem. It takes several day from activation of the car until all data is present on the Renault server. Therefore you don't see correct status in the My Renault app either.


Fix typo / inconsistency in Msg method

The method SetAttachements is probably a typo: In all other methods it's correctly written "Attachments", so this method should be aligned.

Appreciate the PR @alfa-alex!

Appreciate the PR @alfa-alex!

You're welcome. And thank you for the fast merge of this MR. And, even more, for your great work on this library! :tada:


cmake: toolchain: zephyr-0.9.5: Fix setting of TOOLCHAIN_HAS_NEWLIB

There was an oversight and the Zephyr SDK 0.9.5 toolchain should report
itself as supporting newlib.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

Codecov Report

Merging #13603 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #13603   +/-   ##
=======================================
  Coverage   52.45%   52.45%
=======================================
  Files         322      322
  Lines       46592    46592
  Branches    10768    10768
=======================================
  Hits        24442    24442
  Misses      17247    17247
  Partials     4903     4903

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 80c9a6a...479dfdd. Read the comment docs.


[Core] Upgrading Dependency on System.Diagnostics.DiagnosticSource to 5.0.0

This work upgrades the version dependency on System.Diagnostics.DiagnosticSource from 4.6.0 to 5.0.0. This was previously blocked by concerns about Azure Functions and PowerShell integration. This upgrade doesn't cause any issues when used with Functions V3+ or PowerShell 7. In order to better integrate with older versions of functions, we may want to consider disabling diagnostic tracing entirely if a runtime check reveals that System.Diagnostics.DiagnosticSource has a lower version.
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.


*: add codgen for base deploy/role.yaml

cc/ @hasbro17

Test:
fanmins-MacBook-Pro:operator-framework fanminshi$ operator-sdk new test-operator
Create /Users/fanminshi/work/src/github.com/operator-framework/test-operator/cmd/manager/main.go
Create /Users/fanminshi/work/src/github.com/operator-framework/test-operator/pkg/apis/apis.go
Create /Users/fanminshi/work/src/github.com/operator-framework/test-operator/pkg/controller/controller.go
Create /Users/fanminshi/work/src/github.com/operator-framework/test-operator/pkg/build/Dockerfile
Create /Users/fanminshi/work/src/github.com/operator-framework/test-operator/pkg/build/build.sh
Create /Users/fanminshi/work/src/github.com/operator-framework/test-operator/deploy/role.yaml
Create /Users/fanminshi/work/src/github.com/operator-framework/test-operator/deploy/role_binding.yaml
Run dep ensure ...
could not find project Gopkg.toml, use dep init to initiate a manifest
2018/09/19 13:19:59 failed to exec dep []string{"ensure", "-v"}: exit status 1
fanmins-MacBook-Pro:operator-framework fanminshi$ cat test-operator/deploy/role.yaml
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: test-operator
rules:
- apiGroups:
  - ""
  resources:
  - pods
  - services
  - endpoints
  - persistentvolumeclaims
  - events
  - configmaps
  - secrets
  verbs:
  - "*"
- apiGroups:
  - apps
  resources:
  - deployments
  - daemonsets
  - replicasets
  - statefulsets
  verbs:
  - "*"

LGTM


Questions about reload properties

Describe the bug
Please provide details of the problem, including the version of Spring Cloud that you
are using.
Is not a bug.
I try to reload properties with spring cloud kubernates library.
Here is my configuration
gradle
implementation("org.springframework.cloud:spring-cloud-starter-kubernetes-fabric8-all:3.1.2")

properties
spring:
  config:
    import: 'kubernetes:'
  cloud:
    kubernetes:
      config:
        name: config-name
        namespace: config-name-namespace
        sources:
          - name: test.message
        enabled: true
      reload:
        enabled: true
        strategy: refresh
        mode: event
        namespaces: config-name-namespace

source code
@Configuration
@ConfigurationProperties(prefix = "test")
class SampleProperty {
    var message: String = ""
}

@RefreshScope
@Component
class SampleService(
    private val sampleProperty: SampleProperty
) {
    fun test(): String {
        return "The Message is ${sampleProperty.message}"
    }

    @Scheduled(fixedRate = 5000)
    fun print() {
        println(test())
    }
}

I used kustomize.
k8s manifests
role
apiVersion: v1
kind: ServiceAccount
metadata:
  name: config-service
  namespace: config-name-namespace

---

kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: config-role
rules:
  - apiGroups: [""]
    resources: ["configmaps", "pods", "services", "endpoints", "secrets"]
    verbs: ["get", "list", "watch"]

---

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: config-name
  namespace: config-name-namespace
subjects:
- kind: ServiceAccount
  name: config-service
  apiGroup: ""
roleRef:
  kind: ClusterRole
  name: config-role
  apiGroup: rbac.authorization.k8s.io

I changed a property in the k8s configuration map.
I found this log
2024-06-07T18:52:00.825+09:00 DEBUG 1 --- [-253011924-pool-2-thread-3] o.s.c.k.c.c.reload.ConfigReloadUtil      : findPropertySources : []
2024-06-07T18:52:00.825+09:00 DEBUG 1 --- [-253011924-pool-2-thread-3] o.s.c.k.c.c.reload.ConfigReloadUtil      : left size: 1
2024-06-07T18:52:00.825+09:00 DEBUG 1 --- [-253011924-pool-2-thread-3] o.s.c.k.c.c.reload.ConfigReloadUtil      : Fabric8ConfigMapPropertySource@128468998 {name='configmap.test.message.<namespace>, properties={}}
2024-06-07T18:52:00.825+09:00 DEBUG 1 --- [-253011924-pool-2-thread-3] o.s.c.k.c.c.reload.ConfigReloadUtil      : right size: 0
2024-06-07T18:52:00.825+09:00  WARN 1 --- [-253011924-pool-2-thread-3] o.s.c.k.c.c.reload.ConfigReloadUtil      : The current number of ConfigMap PropertySources does not match the ones loaded from Kubernetes - No reload will take place
2024-06-07T18:52:00.825+09:00 DEBUG 1 --- [-253011924-pool-2-thread-3] o.s.c.k.c.c.reload.ConfigReloadUtil      : No change detected in config maps/secrets, reload will not happen

So I checked the configuration map. I confirmed that it has changed.
It doesn't reload. Is there a problem with the information I set?
Note: I have changed the setup information to be different from what I am currently working with.
Sample
If possible, please provide a test case or sample application that reproduces
the problem. This makes it much easier for us to diagnose the problem and to verify that
we have fixed it.

Can you also provide your configmaps?

Can you also provide your configmaps?

Here is my configmap
overlays/dev/config/application.properties
spring.profiles.active=dev
test.message=here test message

overlays/dev/configmap.yaml
apiVersion: builtin
kind: ConfigMapGenerator
metadata:
  name: config-name
behavior: merge
envs:
  - config/application.properties

base/configmap.yaml
apiVersion: builtin
kind: ConfigMapGenerator
metadata:
  name: config-name
options:
  disableNameSuffixHash: true
envs:
  - config/application.properties

I dont think this is correct
        sources:
          - name: test.message

That is the data in your config map.  The sources.name property should be the name of the config map.

Can you provide a sample that for example is a github repo, with clear instructions how to re-produce the issue, let's say to deploy it in minikube or kind?

Thank you for answer
The sample will probably take some time. (I have other things to do) I used the in-house kubernetes cloud to test it.
If the issue is open for a long time, it would be a good idea to close the issue and prepare the sample before reopening it.

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


FEI-4957.6: Use project references and multiple tsconfig.json files

Summary:
I ran into a number of issues with dts-bundle-generator.  It exports private that weren't exported and it can't handle having multiple types with the same name, e.g. different 'Options' types are defined in multiple places in wonder-stuff-server.
This PR address the issue by using project references which allow us to have multiple tsconfig.json files (one for each package) in a single repo.  Each tsconfig.json defines where the root (source) and output directories are relative to the tsconfig.json file.  The root tsconfig.json doesn't cover any source files and instead only references the other tsconfig.json in the package folders.
https://www.typescriptlang.org/docs/handbook/project-references.html#composite
Issue: FEI-4957
TODO:

[x] update the existing build scripts to not generate a .d.ts file or .flow.js
[x] update CI to run build:types

Test plan:

remove the @ts-expect-error comment from isolate-modules.ts, see that there's an error reported in VSCode
yarn clean
yarn build:types, see the same error reported
yarn typecheck, see the same error
re-add the the @ts-expect-error comment, see the error is gone in VSCode
re-run the yarn commands from above, see that the error is no longer reported by them

@jeresig request re-review due to the non-trivial changes I made to the tsconfig files.


fixes #31: Delete-for-Binomial-Heap

Codecov Report

Merging #39 into master will increase coverage by 1.1%.
The diff coverage is 84.37%.

@@            Coverage Diff            @@
##           master      #39     +/-   ##
=========================================
+ Coverage   84.33%   85.43%   +1.1%
=========================================
  Files           7        7
  Lines         696      728     +32
=========================================
+ Hits          587      622     +35
  Misses         78       78
+ Partials       31       28      -3

Impacted Files
Coverage Δ

binomial/binomial_heap.go
86.33% <84.37%> (+6.89%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cb91ced...7769ac8. Read the comment docs.

@safwan-moha Great. Check my comments. Ta.

@safwan-moha Great. Check my comments. Ta.

@theodesp did you add comments?

Aa sorry I forgot to submit them.

Cool  Thank you!

@all-contributors please add @safwan-moha for tests and code


[Community] Nominating Yuandong Xie (GithubID: xieydd) for Fluid committer

Dear  Fluid TOC members and maintainers,
I am proposing to have Yuandong Xie (GithubID: xieydd) as a new committer.
Yuandong Xie, is a senior engineer of Tencent Cloud. He works in Tencent Kubernetes Engine(TKE) team, focuses on cloud native AI infrastructure and other kubernetes related products. Yuandong also focus on elastic kubernetes service on tencent cloud. He likes to explore and contribute to open source technologies, is also member of kubeflow、Istio and fluid community.
The commit history: https://github.com/fluid-cloudnative/fluid/commits?author=xieydd
Feb 26th, 2022
Contributed to the growth of community , expand the user case of fluid. Add new runtime of fluid – GooseFSRuntime, Provides fluid monitoring、stability enhancements and enterprise-level needs.
Talks/Presentations/Blogs
Talks:
KubeCon 2021 China: Fluid : Kubernetes 原生分布式数据集协调器和加速器
https://www.lfasiallc.com/kubecon-cloudnativecon-open-source-summit-china/program/schedule/
KubeCon 2021 NorthAmerican: Fluid- Build Data Orchestration in Kubernetes.
https://sched.co/lV2U
Fluid Community Meeting talks: Plan Discussion for BigData App Integration for Fluid
https://github.com/fluid-cloudnative/community/wiki/Meeting-Agenda-and-Notes#20210630
Blogs:
https://cloud.tencent.com/developer/article/1868108
Major contributions
v0.3.0:
Support the underlay storage which is configured only with non-root: https://github.com/fluid-cloudnative/fluid/pull/168
v0.4.0:
Support deploying multiple dataset in the same node: https://github.com/fluid-cloudnative/fluid/pull/242
v0.5.0:
Enhance Prometheus monitoring support for AlluxioRuntime: https://github.com/fluid-cloudnative/fluid/pull/466
v0.6.0:
Enhance HA support for cache Runtime: https://github.com/fluid-cloudnative/fluid/pull/781
Support new cache Runtime：GooseFS: https://github.com/fluid-cloudnative/fluid/pull/912
Feel free to +1 or -1, starting with my +1.
Thanks,
Rong

+1

+1, welcome

+1


feat: add google-c2p dependence to DirectPath

DirectPath is migrating to Traffic Director, and we want to setup E2E tests based on TD for Bigtable and Spanner. This PR:

Add the google-c2p resolver dependence to gax-java;
Add an environment variable GOOGLE_CLOUD_ENABLE_DIRECT_PATH_XDS to enable using DirectPath over TD;

Typically this is done through "dependency injection." In fact, the current could have been retrieving directly system environment variables with Boolean.get(), but it's getting the variables through the envProvider instance. What you can do is to pass a custom EnvironmentProvider. For that to work, I see you will need to add a package-private (shouldn't be public) setEnvironmentProvider() to the Builder class, and call the setter while building an instance in the corresponding ...Test.java. You will see examples of creating an instance through the builder.

Thanks for the explanation! I have understood your method and been able to create a unit test, where I when DirectPath XDS is enabled, a URI scheme google-c2p:/// will be added and port number will be removed. In my manual test it failed because ava.lang.IllegalArgumentException: cannot find a NameResolver for google-c2p:///localhost, which I believe is because current gax-java does not have the XDS dependency. Please take another look. Thansk!

I pushed some changes, so be sure to pull before working on this.


feat: api v2beta to api v2

Which Problems Are Solved
The v2beta services are stable but not GA.
How the Problems Are Solved
The v2beta services are copied to v2. The corresponding v1 and v2beta services are deprecated.
Additional Context
Closes #7236

Waiting for #8343


Feature flag for fail fast behavior for Managed Dependent Resources

Currently the behavior in managed dependent resource is the following:
We reconcile all the dependent resources mentioned in the @Dependent annotation in order. So calling reconcile(...) on all dependents, even if one of the fails. If one fails eventually we will throw the exception, but before all others are reconciled.
This is reasonable if the resources are independent of each other. If there is a problem with one that will be retried again (as the result of the exception , that triggers eventually a new reconciliation).
However this behavior is not so nice, if those dependent are interconnected, thus depend on each other. If one fails, and an other depends on it, the "other" will fail too. In this case a desired behavior would be not to reconcile the other.
One way to handle this in general is to give an option to the users, to have a fail fast approach. To have a feature flag to configure the controller to have fail after the first exception occurred. This is more consistent also with the implementation of the reconciler where users don't use dependent resources or use them in standalone mode. The exception is thrown and can be handled by ErrorStatusHandler.

Note that this issue is also related to workflows: https://github.com/java-operator-sdk/java-operator-sdk/issues/1097 we might eventually implement.

In my opinion, it'd be better to focus on implementing simple workflow support than adding a feature flag because this flag will be obsolete with the workflow support.

I agree that should be the primary goal. But can take some time.
Created this to be on the table if we see lots of issues with the current default approach.

Implemented workflows with the  "most complete" approach, this is what @metacosm is preferred (if remember correctly), will close this issue.


Legacy contract class corrupted when deserialized through ContractArtifact

Due to a scientific notation issue, certain legacy (Cairo 0) contract artifacts can be different when deserializing directly and through the ConrtractArtifact enum. This leads to class hash errors, and hence failures on contract declaration.
Details to be updated later. Creating this issue first so that it can be referenced from starkli.

Looks like the switch to raw_value in https://github.com/xJonathanLEI/starknet-rs/commit/c5cf1967d44dd61fb68b36cefed710cc8518b1ab has made this worse. Previously only artifacts with values that can be converted to the scientific notation without precision loss are affected; now it looks like most artifacts are affected.

Added a test case (that's disabled by default to avoid breaking CI) in #644, test_legacy_artifact_deser_from_contract_artifact, specifically to test this issue. A patch to this issue should be able to also remove the ignore attribute on that test case.


Party crash with latest BQ

Crash report? Description? Etc?

Crashes when clicking the party button,
https://pastebin.com/1aJyZk3V

It seems to have a hard requirement on mobends which is not installed

Fallback check added in 1.3.3, mobends patch in config can also just be turned off if not using mobends.


Edits

Pull Request Test Coverage Report for Build<PHONE_NUMBER>7
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 42.624%

Totals

Change from base Build<PHONE_NUMBER>5:
0.0%

Covered Lines:
471

Relevant Lines:
1105

💛  - Coveralls


Add pytest Github Action

Fixes #6
Closes: #8

whoop, added flake8.
do we want to reduce its sensitivity?


[1.4.2] Server doesn't get styles generated by injectGlobal

As now we are using another StyleSheet object to generate injectGlobal styles, the following method doesn't work properly anymore:
import styleSheet from 'styled-components/lib/models/StyleSheet'
...
const styles = styleSheet.rules().map(rule => rule.cssText).join('\n')

Now we need also to import and get rules from GlobalStyleSheet
import styleSheet from 'styled-components/lib/models/StyleSheet'
import globalStyleSheet from 'styled-components/lib/models/GlobalStyleSheet'
...
const styles = styleSheet.rules().map(rule => rule.cssText).join('\n')
const globalStyles = globalStyleSheet.rules().map(rule => rule.cssText).join('\n')

That works, but as some projects are already counting on the first method and we encouraged that, I think we should return global styles in StyleSheet.
The good news is that 1.4.2 also fixes #238 🎉

I can also confirm that concatenating globalStyles + styles doesn't break #238

Ah damn, I totally forgot we'd break this use case! My bad, mind submitting a PR reverting that change and a new PR against the v2 branch with those changes?!

If no one else takes it first, I can work on this on Tuesday. But I would try to keep the changes from 1.4.2 in v1. It's too good and solve big issues in v1 to be left to v2 😣

But I would try to keep the changes from 1.4.2 in v1. It's too good and solve big issues in v1 to be left to v2 😣

It's a breaking change and is thusly going to hurt a lot of people, we can't do that I'm afraid 😕

@diegohaz @mxstbr Sorry about breaking this 😦, totally didn't think about this case.  What properties of the StyleSheet module are "public"?  If it's just .rules(), we can definitely make this work with v1.  I'll put something together tonight.

My plan is to revert to a single StyleSheet module, which handles both global and component styles.  I'd add an global option argument (i.e. { global: true })  to the .insert method which would decide which sheet to insert into.  Then the rules method would just return the concatenation of globalSheet.rules() and componentSheet.rules()

@xcoderzach No problem. We should had tested .rules() properly to make sure it wouldn't break. I love your idea. It would be awesome to have it working in v1. 🎉

That sounds like a nice solution @xcoderzach!

Should be fixed in #440

This is fixed in v2.


Thread 8: signal SIGABRT

swift 4.1 contact picker

swift4.2 datepicker same problem

use self.present(alert, animated: true) instead of alert.show()


Links on Kubernetes-Nodejs documentation are broken

It appears that the renamed directory sdk -> pack on pulumi/pulumi-kubernetes is causing links on the kubernetes-nodejs docs site to break.
For example, this link does not work: https://github.com/pulumi/pulumi-kubernetes/blob/master/sdk/nodejs/types/output.ts
But this one does: https://github.com/pulumi/pulumi-kubernetes/blob/master/pack/nodejs/types/output.ts
Please fix.

We'll get this fixed.
I think the issue here is that our doc generator assumes everything is in a directory named sdk/ (it is for AWS, Azure, Google Cloud, etc). But the Kubernetes repo stores it in pack/.
A simple fix is to just change the Kubernetes repo structure to match the others. @hausdorff , any objections?

This was fixed with https://github.com/pulumi/pulumi-kubernetes/pull/227.


FileSystemConnector GetFile method on webpart files throws error when webpart is added to page

I try to use the FileSystemConnector and use the GetFile method in order to grap a webpart file (exported through the SharePoint UI). When I create a new Page object, add the webpart to the constructor and add the file to the template, the template gets correctly created (when I view the saved xml version of it). If I try and apply the template to a web object, I receive an error that the webpart file is not correct and cannot be imported (default message). When I grap the same webpart file using System.IO.File.ReadAllText and put that string in the contents of the webpart, add it to the page and template, it applies the template correctly.
See below thread for context and repro:
https://www.yammer.com/itpronetwork/#/Threads/show?threadId=550122342

Sorry Robert for way too long reaction times around this issue. We have done significant refactoring of the Core component since this issue and most likely it has been properly fixed. If that's not the case, would ask you to create a new issue in the Core Component repository to avoid issue getting hidden. Core component repository is at https://github.com/OfficeDev/PnP-sites-core.


XeGTAO and Bloom shaders don't compile in opengl games

Every time I tried using these shaders with an OpenGL game, the following error occurred:

In the XeGATAO shaders, the errors come from the CS_Denoise function receiving a uint2 as a parameter instead of a uint3. Changing that resolved the shader compilation issue.
In the Bloom shader, simply changing everything to int instead of bool also seems to solve the problem.

I only ensure my shaders compile and work on ff14, I'm glad you figured out the issue though.


Hello, Someone could explain how the program works? Thanks

It works by first calling setup() function and then calling loop() infinitely.
setup() among other things adds an interrupt handler spinEnc() which is called every time a rotary encoder makes a step, adding those steps up in spindlePos variable.
loop() calculates the stepper position based on spindlePos and compares it to current stepper position. Stepper is moved if needed.

It works by first calling setup() function and then calling loop() infinitely.
setup() among other things adds an interrupt handler spinEnc() which is called every time a rotary encoder makes a step, adding those steps up in spindlePos variable.
loop() calculates the stepper position based on spindlePos and compares it to current stepper position. Stepper is moved if needed.

Thanks, It a good help to start understanding !

Thanks, It a good help to start understanding !


add argo workflow for end to end experiments

Running end to end experiments of the microphysics emulator was not so easy or sweeps across hyper parameters space was not easy.

combined the training/prog run workflows into one yaml

Can still use --entrypoint to select the workflows invidually

add scripts/framework for launching end to end runs

See experiments/default.yaml

launched "production" tests of a recent commit on master

EndToEndJob(name='limited-d6a0ed-v1', fv3fit_image_tag='d6a0ed27eb58dae25782e9c6613774562f2e64f0', image_tag='d6a0ed27eb58dae25782e9c6613774562f2e64f0', bucket='vcm-ml-experiments', project='microphysics-emulation')
EndToEndJob(name='rnn-d6a0ed-v1', fv3fit_image_tag='d6a0ed27eb58dae25782e9c6613774562f2e64f0', image_tag='d6a0ed27eb58dae25782e9c6613774562f2e64f0', bucket='vcm-ml-experiments', project='microphysics-emulation')
to monitor experiments: argo list -lexperiment=d6a0ed27eb58dae25782e9c6613774562f2e64f0-end-to-end

this is ready for re-review.


Use Redis (compatible) storage for caching

Having a memory-backed key-value store can help improve overall performance of zitadel.
Example use cases

Caching of authenticated, static and repetitive responses. Like OIDC introspection and userfinfo.
Easy revocation / deletion of introspection / userinfo when a token gets revoked
Projection of models that are temporary in nature, like auth requests.
Caching of middleware data, such as instance domain, organization data etc.

Considerations
Although Redis has received some scrutiny over their licencing policy recently, the solution itself is still great.  There are now a number of forks of the Redis project and there are a number of solutions that claim Redis protocol compliant. This should give sufficient flexibility to the community the pick the actual Redis compatible storage they wish.
Some examples:

The go-redis client also support connecting to KVRocks.
Valkey is a fully open source sever alternative now backed by the linux foundation
Google Cloud (used by zitadel cloud) offers a Redis compatible memorystore, based on Redis OSS.

Acceptance criteria
This user story is only to provide a base package and structure for Redis interactions. Usage of the new storage will be defined in new user stories.

[ ] Internal go package that sets up an connection
[ ] Health checks
[ ] Runtime configuration in defaults.yaml
[ ] A Redis (compatible) service to be available in the CI pipeline for integration tests
[ ] Devcontainer

Postpone until we further defined how to continue with the field/search/lookup-table


Updated to 21w37a.

Changes:
Minecraft 1.17.1 -> 21w37a
Loom Updated
Mod version number increased

I think setting "minecraft": ">=1.17.x" in fabric.mod.json would be enough

No. Because you need to update the fabric API aswell and yarn. And even when I have "minecraft: >=1.17.x" it complains like a baby and wants "minecraft: >=1.18.x"

without .x work perfectly fine, I tested it


from keyword can get highlighted in import ... from ''; statement

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

VS Code Version: 1.64.0-insider
OS Version: Kubuntu 21.04

Steps to Reproduce:

Have 2 files (2nd file is just to have something to import)

// index.ts
import { hi } from './other';

// other.ts
export const hi = 'hi'

Ctrl+hover between "./other" and from (may have to try multiple times)

// index.ts
import { hi } from './other';
                     ^^^^^^
              ^^^^

// other.ts
export const hi = 'hi'

Expected behavior:
Because the from keyword is normally not defintion-clickable, it should not be clickable as describe above as well.
Video:

https://user-images.githubusercontent.com/30693990/145874967-eaae0e11-e988-457a-82d7-5dbcb3c90bc7.mp4

Thanks @hiaux0
It looks like this happens when hovering over the space immediately after from. Here's an example request and response:
[Trace  - 01:26:30.949] <semantic> Sending request: definitionAndBoundSpan (265). Response expected: yes. Current queue length: 0
Arguments: {
    "file": "/Users/matb/projects/san/x.ts",
    "line": 2,
    "offset": 19
}
[Trace  - 01:26:30.950] <semantic> Response received: definitionAndBoundSpan (265). Request took 1 ms. Success: true
Result: {
    "definitions": [
        {
            "file": "/Users/matb/projects/san/other.ts",
            "start": {
                "line": 1,
                "offset": 1
            },
            "end": {
                "line": 1,
                "offset": 1
            }
        }
    ],
    "textSpan": {
        "start": {
            "line": 2,
            "offset": 15
        },
        "end": {
            "line": 2,
            "offset": 19
        }
    }
}


Update adsim to ophyd_async

The AreaDetector simulator backed by the Epics AreaDetectorSimulator is split into three parts: dodal/src/dodal/devices/adsim.py contains a 5-axis MotorBundle; dodal/src/dodal/devices/areadetector/adsim.py contains a simulated detector; dodal/src/dodal/adsim.py is equivalent to a beamline. Having these maintained and using ophyd_async may enable fast testing of plan behaviour and would give an easily run up simulated beamline for local development.
Acceptance Criteria

Blueapi can be run up with the areadetector simulator devices exposed and connected with ophyd_async signals and an example grid_scan may be run with data being emitted

The simulator is a generic EPICS thing, right? Would this make more sense inside ophyd-async @coretl?

https://github.com/bluesky/ophyd-async/tree/main/src/ophyd_async/epics/adsimdetector
There is an adsimdetector in ophyd-async

As part of this make sure https://github.com/DiamondLightSource/dodal/pull/737#discussion_r1711422672 has coverage


Change debugger type in DebugConfigurationProvider

Currently xmake-vscode uses the vscode.debug.startDebugging function with lldb or cpp tools as debugger extensions.
And for that we have to replace the keybind f5 with a command, I think it is not ideal.
So my idea was to make a custom debug type (xmake) in the package.json, for example like this:
{
	"type": "xmake",
	"configurationAttributes": {
	  "target": {
		"type": "string",
		"description":"the xmake target name"
	  }
	}
}

But after some research I figured out that it's not that easy. It need to implement the Debug Adapter Protocol, but xmake doesn't need it as it's based on the cpp tools or lldb extension.
My request is add the possibility to change to debugger type in the configuration provider, like this:
class XmakeConfigurationProvider implements vscode.DebugConfigurationProvider {

	/**
	 * Massage a debug configuration just before a debug session is being launched,
	 * e.g. add all missing attributes to the debug configuration.
	 */
	resolveDebugConfiguration(folder: WorkspaceFolder | undefined, config: DebugConfiguration, token?: CancellationToken): ProviderResult<DebugConfiguration> {

		const programPath = getProgram(config.target) // Find the program from xmake target

		// Set the config type for platform specific or extension (lldb, cpp tools)
        config.type = 'cppdbg'; // or lldb
        config.name = 'Launch';
        config.request = 'launch';
        config.program = programPath;
        config.stopOnEntry = true;

		return config;
	}
}

This would allow extensions to propose launch.json configurations more adapted to the extension,
without having to implement DAP because it would be the role of another extension.

I think that is possible, isn't it? What's going wrong?

I created a mock extension with a new debugger type (xmake) in package.json, register this debug configuration like this:
const provider = new XmakeConfigurationProvider();
context.subscriptions.push(vscode.debug.registerDebugConfigurationProvider('xmake', provider));

And the resolveDebugConfiguration function is used to change debugger type,like my previous message.
When I start the extension and try to debug the xmake type, I have a error message. But the error message is different between onDebug and onDebugResolve activations events.
With onDebug:

With onDebugResolve:

So it's this feature not implemented or my mock is wrong ?

@roblourens Sorry for the ping, in your last message you seem to say that functionality already exists in code. But I can't get it to work, is it my implementation?

I am closing this because I have received all one answer here https://github.com/microsoft/vscode-discussions/discussions/314.


Implementation of the Lamba_u is not correct

_match *= tf.clip_by_value(tf.cast(self.step, tf.float32) / (warmup_kimg << 10), 0, 1)
here warmup_kimg=1024, that's to say, it should be _match%=step/1048576
Yours:
def linear_rampup(current, rampup_length=16):
if rampup_length == 0:
return 1.0
else:
current = np.clip(current / rampup_length, 0.0, 1.0)
return float(current)

1048576/(64-batch_size * 1024-iteration_per_epoch) = 16-epoch. Am I wrong?

For your batch size, no. However, considering the situation user will give different batch_size. Therefore, your updating strategy is not correct.
Also, please notice google's actual training batch size is also different from you.(See their paper)

OK. I will fix it. But training batch size is always 64 in all experiments.
https://github.com/google-research/mixmatch/blob/master/mixmatch.py#L144


Add scaling factor

Changes
Adds the option to scale the plotted vectors of an LCS
Checks

[x] updated CHANGELOG.md
[x] updated tests
[x] updated doc/
[x] update example/tutorial notebooks

Hello @vhirtham! Thanks for updating this PR.

In the file weldx/transformations/local_cs.py:

Line 839:37: F821 undefined name 'List'


Volume2 initialization delay

Volume2 widget doesn't initialize immediately when using icons

Fix it starting from this branch
https://github.com/frostidaho/qtile/tree/develop_svg_support

Fixed: https://github.com/frostidaho/qtile/commit/9a26a42c787dd6ee14030bd88a0a6a6dbbed90d6


Select columns to Export

Hi,
Can I select which column to export?
Thx.

I discovered you can accomplish this by setting the attributes ... csv-header and csv-column-order....
Fields you don't include wont be exported.


Unable to resume files after deployment

Hi @smatsson ,
We are having an ASP .Net core 3.0 application and using the tusdotnet for the resumable file feature. When running locally using IIS or kestrel it works fine. But when we put this behind nginx reverse proxy, the file resume does not work. It always starts from 0. Not sure if there is any header information being missed when using nginx reverse proxy.
Here is my nginx host configuration

Here are some snippets from startup file

Here is my TusConfigurationFile

I have used the configuration that you provided from demo app
Let me know if we can modify anything there.
Thank you!

Hi,
I am no expert in nginx but I would thing that the problem is that nginx by default caches the entire request before passing it upstream. According to the docs you can disable this by setting proxy_request_buffering to off.
https://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_request_buffering

Hi @smatsson ,
Thank you for a quick response. I tried adding the proxy_request_buffering in my nginx.conf and default.conf file and it worked.
Here is the updated nginx configuration and nginx host configuration filles.


Check if scope is testOnly when copying libs from distribution

Purpose

$title

Fixes #
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, related PRs, TODO items, or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #23927 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #23927   +/-   ##
=======================================
  Coverage   14.59%   14.59%
=======================================
  Files          51       51
  Lines        1411     1411
  Branches      219      219
=======================================
  Hits          206      206
  Misses       1189     1189
  Partials       16       16

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 67256c9...ae82647. Read the comment docs.


README.md image path fix #167

fixes #167
There was a error in the path of a image in README.md.

@lasse-offerzen Can you please add hacktoberfest-accepted label to this PR
_> YOUR PR/MRS MUST BE IN A REPO TAGGED WITH THE “HACKTOBERFEST” TOPIC, OR BE LABELED “HACKTOBERFEST-ACCEPTED.”

Hacktoberfest is now opt-in for maintainers, so only contribute to projects that indicate they’re looking for Hacktoberfest PR/MRs.
Once your PR/MR has passed this check, we won’t check this again (unless your PR/MR fails a check before this, such as it being marked as spammy)._


Remove post-link script and install faiss-cpu via Conda

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hm, looks like pip check is failing because we declare faiss-cpu as a dependency in pyproject.toml, since that is the easiest way to install faiss via PyPI. However,installing faiss-cpu via Conda Forge only installs the faiss package and does not include a wheel for faiss-cpu, which results in pip check failing. Probably won't have time to look into this, but I'm documenting this error here for now.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.
Here's what I've got...
For recipe/meta.yaml:

requirements: run: faiss-cpu>=1.8.0,<2 must contain a space between the name and the pin, i.e. faiss-cpu >=1.8.0,<2

For recipe/meta.yaml:

noarch: python recipes should almost always follow the syntax in our documentation. For the host section of the recipe, you should almost always use python {{ python_min }} for the python entry. For the run section of the recipe, you should almost always use python >={{ python_min }} for the python entry. For the test.requires section of the recipe, you should almost always use python {{ python_min }} for the python entry. You may need to override the python_min variable in the conda_build_config.yaml/variants.yaml if the package requires a newer Python version than the currently supported minimum version on conda-forge.
PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

This probably can be fixed by simply removing the pip check call in the recipe, but this may cause downstream issues in CI pipelines that install Jupyter AI via Conda Forge and run pip check. I'll see if there's a safer solution to this.

There is an existing issue for ignoring packages in pip check: https://github.com/pypa/pip/issues/11157
However, progress had halted months ago. It may be better just to remove pip check from the recipe, as recommended here by a member of PyPA: https://github.com/pypa/pip/pull/11159#issuecomment-1933051895

I've taken all conceivable user concerns about this issue into account, and have reached a conclusion on the best path forward.
It seems best to remove the post-link script and install faiss-cpu directly from Conda Forge to fix Conda Forge installs for Jupyter AI. This will break pip check when Jupyter AI is installed via Conda Forge, but this is an existing issue for other Conda packages with no clear path to remediation currently. While it's unfortunate we have to remove this check, removing this check is a better alternative to Jupyter AI being unavailable on Conda Forge.
Users should open an issue on this feedstock if they have a use-case where this is unacceptable. If this occurs and we find a better solution to this issue, we can re-build the affected releases of Jupyter AI on Conda Forge.

Technically, this requires a patch release in Jupyter AI first to fix the version specifier declared for faiss-cpu, which currently is set to faiss-cpu<=1.8.0. I'll do that, cut the patch release on PyPI, then update & merge this PR to cut the patch release on Conda Forge.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe/meta.yaml:

ℹ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.

For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
For the run section of the recipe, you should usually use python >={{ python_min }} for the python entry.
For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

ℹ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

@conda-forge-admin please rerun bot


tooltips: added a tooltip to display the name of status-emoji

 This commit will add a tooltip whenever the user hovers on the status-emoji in the user card popover.
The tooltip will display the name of status-emoji.
Fixes:  #19821

Screenshots and screen captures:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

I think we should use tippy tooltip here rather than the default html title attribute since we are changing the existing title attributes to tippy tooltips. Would be good to discuss it once on https://chat.zulip.org/#narrow/stream/101-design.
Also, a note for the commit message, the first letter should be capital in added for tooltip: added a tooltip... line.

I have posted a discussion on the above stream channel implementing a customised tippy tooltip design. Can you suggest me the necessary improvements in the design.
Also, Sure! I will update the commit message when the design will be final.

To be clear, I did not have any design improvements in my mind. I was just thinking of using just the simple tippy tooltip instead to maintain consistency with other tooltips in the app.

I have done the necessary improvements. PTAL

I have posted about some previous discussions related to this on the stream. And I think you would want to update the commit message and PR description to remove the Fixes .. part since #19821 requires emoji name to shown as tooltip in right sidebar and not in the popover.
Though you can mention that this proposal came in when working on #19821.

After reading the discussions in previous PRs on this issue I found that adding a status-emoji tooltip on right sidebar would not be a great idea as two tooltips on a single component seems a lil bit weird. So, after considering https://github.com/zulip/zulip/pull/24976#issuecomment-1497157777 I came up with this proposal.
Should I then change the commit message Fixes.. to Partially Fixes ?

I have added a tippy tooltip on hovering over the status-emoji in user profile popover instead of the regular HTML title.
New improvements looks like -

@shashank-23002 I notice this doesn't use our typical patterns in tippy.js for tooltips; is there a reason for that? If not I'd appreciate your reworking it to match existing patterns.

@shashank-23002 what Tim said--we've got built-in, class- and data-attribute-backed logic for adding tooltips like this. Note too that there are two different types of status-emoji that this needs to cover. Something like:

                 {{#if status_emoji_info}}
                     {{#if status_emoji_info.emoji_alt_code}}

 :{{status_emoji_info.emoji_name}}:

                     {{else if status_emoji_info.url}}
-
+
                     {{else}}
-

+

                     {{/if}}
                 {{/if}}

You should have a look at the web/src/tippyjs.js file, especially the comments that talk about the tippy-zulip-tooltip and it's delayed counterpart, and the use of the data-tippy-content attribute.

@karlstolley I have updated the tooltips to match with the standard tippy zulip tooltip.
Please let me know more improvements if any.

Thanks @shameondev for suggesting the solution to remove background transparency.
I have done the necessary changes PTAL .

@shashank-23002, great job!
The change you made in tippy.js isn't directly related to the main purpose of this PR, which is adding a tooltip. So, I suggest you move this change to a separate commit. It'll keep things nice and tidy!
You can learn more about this approach in the commit discipline documentation.

@shashank-23002, I've updated the commit messages to more clearly explain what we're changing and why.

Thanks @shameondev I will try to maintain the above format of writing clear commit message in future.

@shashank-23002 please update the commit messages for sentences to add with a period as Aman also suggested above. Also would be better to shorten the commit message length so that it is easy to read in git log in a normal terminal. You can read the commit message guidelines for reference.

@sahil839 PTAL

@amanagr @shameondev It's been quite a while since this PR was opened.
If you could please look up if some other improvements are needed so that I can claim some other issues as well.

It looks like this only adds the tooltip to the status emoji when it appears in the popover, which we want -- but it does not add code to do so when they are displayed directly in the right sidebar, which is certainly called for in the issue. Can you fix that?
I think basically anywhere we display the status emoji, we want this to work.

After reading previous PRs comments there were some suggestions that right sidebar already has a tippy tooltip showing users activity status and if one more tooltip of status-emoji was added to it, it would make things weird.
That's the reason I didn't add the tooltips elsewhere.

Thanks @shashank-23002. If you'd like to join the discussion, we're talking about this further over on CZO.


Add artifact v0.9.0.

Artifact is a design document tool for developers. I figured it would fit the main bucket well because it's a standalone tool with a single executable. I can submit the manifest on the extras repo instead if it doesn't belong here though!

I don't understand what it does, but sure why not :grin:


Fixed Case Reference tests failing occasionally and few typos

Fixed Case Reference tests failing occasionally in 8.8 and few typos.
Embedded Data tests are still failing since "Table" is having issues in 8.8.

My testing shows CaseReference test now passing on 8.8.0. Looks good to me.

Exactly, the fix was for Case Reference tests failing on 8.8.0. Thanks!


Register GPX.jl to General registry

Following https://github.com/scls19fr/GPX.jl/issues/4#issuecomment-650821158
GPX.jl should be registered

Hi @scls19fr  Would love to use this package for a new project of mine: https://github.com/Wikunia/EverySingleStreet.jl
For this it needs to be registered. Would it be okay for you to register your package? Thanks in advance and let me know if you have any concerns or anything I can help you with.

I'm quite busy and I'm not using this anymore.
Feel free to fork this repository and register it.


Fix restricted elements bug

Fixes #649
Describe the changes you have made in this pr -
Removed extra parameter restriction line in assignments controller. This bug was much easier to fix than expected.
GCI task

Coverage decreased (-0.02%) to 82.491% when pulling bab8ffe533b4f6743701805a7f5ad45b98f0139a on junron:649restricted_element_bug into d64e1a0c3db31871160b4af3f98946a7ae934242 on CircuitVerse:master.

The decrease in coverage is due to the removal of a line that was tested.

@shubhankarsharma00 Please review

Nice work

Thanks


Cut a new release

Tried doing some prototyping with this earlier today, and congress.votes.VotesClient.recent wasn't available when I used the version on PyPI.
Turns out what's published there (v0.3.5) is missing all of this subsequent development: https://github.com/eyeseast/propublica-congress/compare/v0.3.5...e13a62baadc3ac4ff5968b9e21a93d4d4947ed2f
Perhaps worth a v0.3.6?

I guess I could. Haven't actually touched this code in a few years. Let me see what I can do.

Thanks—and no huge rush, since I was able to pip install -e from here. Just figured it might be helpful for others coming fresh to this.

I very nearly archived this repo a couple months ago. If someone wanted to take it over, I'd be happy to hand over the keys.

Will defer to the folks at ProPublica, since the data still does appear to be flowing properly. I was just using it during an internal hack day, fwiw, so I'm not sure I'd be all that much more helpful.


Error threshold

ERROR THRESHOLD
Added a limit to the amount of errors that can occur in validator, and decreased the threshold in reader. Now bumping to release the 6.0.0 version of validator.

Good stuff :)


Reset previous preferred controller affinity when new controller is preferred

Currently when switching from local to remote, local kernel might still be set as preferred even when we have a new preferred remote controller. This PR ensures that the affinity of old preferred controller is reset.

[x] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[x] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for feature-requests.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).

Codecov Report

Merging #11701 (1cf41e7) into main (93c9c9e) will increase coverage by 12%.
The diff coverage is 30%.

@@           Coverage Diff            @@
##            main   #11701     +/-   ##
========================================
+ Coverage     47%      60%    +12%
========================================
  Files        483      483
  Lines      34447    34457     +10
  Branches    5601     5606      +5
========================================
+ Hits       16520    20684   +4164
+ Misses     16715    11618   -5097
- Partials    1212     2155    +943

Impacted Files
Coverage Δ

.../notebooks/controllers/controllerDefaultService.ts
38% <22%> (+5%)
:arrow_up:

...otebooks/controllers/controllerPreferredService.ts
70% <100%> (+8%)
:arrow_up:

src/kernels/raw/session/rawSession.node.ts
6% <0%> (-56%)
:arrow_down:

src/kernels/raw/session/rawJupyterSession.node.ts
12% <0%> (-44%)
:arrow_down:

...ls/raw/session/rawNotebookSupportedService.node.ts
56% <0%> (-35%)
:arrow_down:

...ernels/raw/session/hostRawNotebookProvider.node.ts
52% <0%> (-33%)
:arrow_down:

src/kernels/raw/session/rawKernel.node.ts
31% <0%> (-23%)
:arrow_down:

src/kernels/raw/session/rawSocket.node.ts
52% <0%> (-17%)
:arrow_down:

...one/intellisense/notebookPythonPathService.node.ts
34% <0%> (-6%)
:arrow_down:

src/kernels/serviceRegistry.node.ts
98% <0%> (-2%)
:arrow_down:

... and 244 more


Ability to add colors to $theme-colors which generates all classes (button variants etc.)

Hi guys, first of all, thank you for this awesome framework. We really love it!
Now we want to extend the standard theme for some own colors with all variants.
Only adding it to the $theme-colors / $colors map doesn't work and we don't want to generate all by ourselves manually, like stated here: https://getbootstrap.com/docs/4.3/getting-started/theming/#modifiers
So it would be nice, if there is a color in the map, which is not standard, all classes for all components are generated.
Example:
If we add color hotpink: rgba(255,105,180 ,1) to the map, we expect to use btn btn-hotpink after that, without the need to manually generate (and therefore know which variants are existing).
Is the possible or planned?

This is currently possible with a Sass compiler and is documented at https://getbootstrap.com/docs/4.3/getting-started/theming/#maps-and-loops.

This is currently possible with a Sass compiler and is documented at https://getbootstrap.com/docs/4.3/getting-started/theming/#maps-and-loops.