text:
Fast switching between files makes the extension thinks I'm using it in an inappropriate way

Type: Bug

Behaviour
Expected vs. Actual
I was switching my files fast, and the extension failed to start, making it thinks I'm not using in a copy of Visual Studio Code.
Steps to reproduce:

Open VSCode. For example, I've had a ipynb file opened
Click on another ipynb file.
While plugin initialization isn't completed, switch to another ipynb file
Notification shows up, saying I'm using a copy of VSCode, and this plugin isn't licensed for that, while I'm truly using VSCode.
Further modifications to my code isn't assisted by this plugin anymore

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.10.12
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Global
Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

2023-10-29 18:44:08.225 [info] Test server listening.
2023-10-29 18:44:08.225 [info] > conda info --json
2023-10-29 18:44:08.225 [info] > poetry env list --full-path
2023-10-29 18:44:08.225 [info] cwd: .
2023-10-29 18:44:08.225 [info] Python 解譯器路徑: ./.venv/bin/python
2023-10-29 18:44:08.295 [info] Found: /bin/python3 --> /bin/python3.10
2023-10-29 18:44:08.304 [info] Found: /bin/python3.10 --> /bin/python3.10
2023-10-29 18:44:08.598 [info] Found: /usr/bin/python3 --> /usr/bin/python3.10
2023-10-29 18:44:08.608 [info] Found: /usr/bin/python3.10 --> /usr/bin/python3.10
2023-10-29 18:44:08.631 [info] > ./.venv/bin/python -I ~/.vscode-server/extensions/ms-python.python-2023.18.0/pythonFiles/get_output_via_markers.py ~/.vscode-server/extensions/ms-python.python-2023.18.0/pythonFiles/interpreterInfo.py
2023-10-29 18:44:08.645 [info] > . ./.venv/bin/activate && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode-server/extensions/ms-python.python-2023.18.0/pythonFiles/printEnvVariables.py
2023-10-29 18:44:08.645 [info] shell: bash
2023-10-29 18:44:08.652 [info] > . ./.venv/bin/activate && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode-server/extensions/ms-python.python-2023.18.0/pythonFiles/printEnvVariables.py
2023-10-29 18:44:08.652 [info] shell: bash
2023-10-29 18:44:08.660 [info] > . ./.venv/bin/activate && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode-server/extensions/ms-python.python-2023.18.0/pythonFiles/printEnvVariables.py
2023-10-29 18:44:08.660 [info] shell: bash
2023-10-29 18:44:08.972 [info] > /bin/python3 -I ~/.vscode-server/extensions/ms-python.python-2023.18.0/pythonFiles/get_output_via_markers.py ~/.vscode-server/extensions/ms-python.python-2023.18.0/pythonFiles/interpreterInfo.py
2023-10-29 18:44:09.002 [info] > /usr/bin/python3 -I ~/.vscode-server/extensions/ms-python.python-2023.18.0/pythonFiles/get_output_via_markers.py ~/.vscode-server/extensions/ms-python.python-2023.18.0/pythonFiles/interpreterInfo.py
2023-10-29 18:44:09.436 [info] 正在啟動 Pylance 語言伺服器。
2023-10-29 18:44:42.488 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 18:48:13.537 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 18:48:20.978 [info] Python 解譯器路徑: /bin/python3
2023-10-29 18:49:00.275 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 18:50:05.927 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 18:51:49.087 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 18:52:21.181 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 18:52:40.435 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 18:52:41.997 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 18:52:59.905 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 18:53:12.905 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 18:58:52.067 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 18:58:57.998 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 18:59:49.855 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:00:21.198 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:00:25.177 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:00:26.355 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:00:27.688 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:00:32.218 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:00:33.236 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:00:34.061 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:01:12.307 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:01:30.857 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:02:14.165 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:02:21.826 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:02:23.957 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:02:24.698 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:02:58.488 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:03:01.267 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:03:01.807 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:03:02.275 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:03:06.986 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:05:17.264 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:05:18.865 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:05:19.819 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:05:20.375 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:06:30.416 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:06:30.911 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:06:41.465 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:07:00.677 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:07:30.078 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:07:32.976 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:45:11.505 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:45:20.658 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:45:28.233 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:45:28.978 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:45:34.708 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:45:51.109 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:45:57.729 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:45:58.428 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:46:19.453 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:47:53.774 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:48:00.299 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:48:01.157 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:48:01.670 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:50:03.385 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:50:17.080 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:51:03.599 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:51:04.289 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:53:44.958 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:53:58.092 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:55:27.371 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:55:42.630 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:57:38.980 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:57:41.266 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:57:43.267 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:57:46.636 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:58:10.804 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:58:21.390 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:58:37.146 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:58:37.795 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:58:38.689 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:58:40.191 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 19:59:09.759 [info] > . ./.venv/bin/activate && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode-server/extensions/ms-python.python-2023.18.0/pythonFiles/printEnvVariables.py
2023-10-29 19:59:09.759 [info] shell: bash
2023-10-29 19:59:09.789 [info] > . ./.venv/bin/activate && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode-server/extensions/ms-python.python-2023.18.0/pythonFiles/printEnvVariables.py
2023-10-29 19:59:09.789 [info] shell: bash
2023-10-29 20:01:29.449 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 20:03:01.249 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 20:03:06.635 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 20:03:07.230 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 20:03:34.051 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json
2023-10-29 20:04:57.481 [info] Discover tests for workspace name: undefined - uri: c:/Users/timsu/AppData/Roaming/Code/User/settings.json

User Settings

languageServer: "Pylance"

Extension version: 2023.18.0
VS Code version: Code 1.83.1 (f1b07bd25dfad64b0167beb15359ae573aecd2cc, 2023-10-10T23:48:05.904Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Remote OS version: Linux x64 5.15.90.1-microsoft-standard-WSL2

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i7-12700H (14 x 2688)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
31.63GB (15.48GB free)

Process Argv
--folder-uri vscode-remote://wsl%2Bubuntu-22.04/home/tim/1121aicp --crash-reporter-id 76077254-8c7e-4f22-9ca8-d18f2ed5db71

Screen Reader
no

VM
0%

Item
Value

Remote
WSL: Ubuntu-22.04

OS
Linux x64 5.15.90.1-microsoft-standard-WSL2

CPUs
12th Gen Intel(R) Core(TM) i7-12700H (14 x 2688)

Memory (System)
15.44GB (12.87GB free)

VM
0%

The above information saying my Python virtual environment is global is wrong. Actually, I'm using one managed my Poetry.
The above template asks for Python output. However, those information isn't helpful. I guess the output of Python language server helps, so I'm pasting here. But I have no idea why this message seems to be cropped that I'm not able to copy any messages older😢

Output for Python language server in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python language server)

Error: Debug Failure. Unable to find notebook URI for vscode-notebook-cell://wsl%2Bubuntu-22.04/home/tim/1121aicp/%E6%9C%9F%E4%B8%AD%E8%80%83/Q14%20CSV%20file.ipynb#W1sdnNjb2RlLXJlbW90ZQ%3D%3D
    at _0x4f6f08._getNotebookUri (/home/tim/.vscode-server/extensions/ms-python.vscode-pylance-2023.10.50/dist/server.bundle.js:1:377799)
    at _0x4f6f08.getNotebookPathFromCell (/home/tim/.vscode-server/extensions/ms-python.vscode-pylance-2023.10.50/dist/server.bundle.js:1:375944)
    at _0x4f6f08.getNotebookCellPath (/home/tim/.vscode-server/extensions/ms-python.vscode-pylance-2023.10.50/dist/server.bundle.js:1:375163)
    at _0x29682b.decodeTextDocumentUri (/home/tim/.vscode-server/extensions/ms-python.vscode-pylance-2023.10.50/dist/server.bundle.js:1:347323)
    at _0x5e13d0.onDidCloseTextDocument (/home/tim/.vscode-server/extensions/ms-python.vscode-pylance-2023.10.50/dist/server.bundle.js:1:1035718)
    at /home/tim/.vscode-server/extensions/ms-python.vscode-pylance-2023.10.50/dist/pyright.bundle.js:1:1143599
    at /home/tim/.vscode-server/extensions/ms-python.vscode-pylance-2023.10.50/dist/vendor.bundle.js:2:1471770
    at oe (/home/tim/.vscode-server/extensions/ms-python.vscode-pylance-2023.10.50/dist/vendor.bundle.js:2:1471992)
    at /home/tim/.vscode-server/extensions/ms-python.vscode-pylance-2023.10.50/dist/vendor.bundle.js:2:1467932
    at Immediate.<anonymous> (/home/tim/.vscode-server/extensions/ms-python.vscode-pylance-2023.10.50/dist/vendor.bundle.js:2:1467952)
    at processImmediate (node:internal/timers:476:21)

2023-10-29 20:06:18.684 [info] [Info  - 下午8:06:18] Connection to server got closed. Server will restart.
2023-10-29 20:06:18.684 [info] true
2023-10-29 20:06:19.067 [info] [Info  - 下午8:06:19] (22382) Pylance language server 2023.10.50 (pyright cfe56bfb) starting
2023-10-29 20:06:19.067 [info] [Info  - 下午8:06:19] (22382) Server root directory: /home/tim/.vscode-server/extensions/ms-python.vscode-pylance-2023.10.50/dist
2023-10-29 20:06:19.073 [info] [Error - 下午8:06:19] Server initialization failed.
2023-10-29 20:06:19.073 [info]   Message: Request initialize failed with message: You may install and use any number of copies of the software only with Microsoft Visual Studio, Visual Studio for Mac, Visual Studio Code, Azure DevOps, Team Foundation Server, and successor Microsoft products and services (collectively, the “Visual Studio Products and Services”) to develop and test your applications. The software is licensed, not sold. This agreement only gives you some rights to use the software. Microsoft reserves all other rights. You may not: work around any technical limitations in the software that only allow you to use it in certain ways; reverse engineer, decompile or disassemble the software, or otherwise attempt to derive the source code for the software, except and to the extent required by third party licensing terms governing use of certain open source components that may be included in the software; remove, minimize, block, or modify any notices of Microsoft or its suppliers in the software; use the software in any way that is against the law or to create or propagate malware; or share, publish, distribute, or lease the software (except for any distributable code, subject to the terms above), provide the software as a stand-alone offering for others to use, or transfer the software or this agreement to any third party.
  Code: -32603
2023-10-29 20:06:19.073 [info] [Error - 下午8:06:19] Pylance client: couldn't create connection to server.
2023-10-29 20:06:19.073 [info]   Message: Request initialize failed with message: You may install and use any number of copies of the software only with Microsoft Visual Studio, Visual Studio for Mac, Visual Studio Code, Azure DevOps, Team Foundation Server, and successor Microsoft products and services (collectively, the “Visual Studio Products and Services”) to develop and test your applications. The software is licensed, not sold. This agreement only gives you some rights to use the software. Microsoft reserves all other rights. You may not: work around any technical limitations in the software that only allow you to use it in certain ways; reverse engineer, decompile or disassemble the software, or otherwise attempt to derive the source code for the software, except and to the extent required by third party licensing terms governing use of certain open source components that may be included in the software; remove, minimize, block, or modify any notices of Microsoft or its suppliers in the software; use the software in any way that is against the law or to create or propagate malware; or share, publish, distribute, or lease the software (except for any distributable code, subject to the terms above), provide the software as a stand-alone offering for others to use, or transfer the software or this agreement to any third party.
  Code: -32603
2023-10-29 20:06:19.073 [info] [Error - 下午8:06:19] Restarting server failed
2023-10-29 20:06:19.073 [info]   Message: Request initialize failed with message: You may install and use any number of copies of the software only with Microsoft Visual Studio, Visual Studio for Mac, Visual Studio Code, Azure DevOps, Team Foundation Server, and successor Microsoft products and services (collectively, the “Visual Studio Products and Services”) to develop and test your applications. The software is licensed, not sold. This agreement only gives you some rights to use the software. Microsoft reserves all other rights. You may not: work around any technical limitations in the software that only allow you to use it in certain ways; reverse engineer, decompile or disassemble the software, or otherwise attempt to derive the source code for the software, except and to the extent required by third party licensing terms governing use of certain open source components that may be included in the software; remove, minimize, block, or modify any notices of Microsoft or its suppliers in the software; use the software in any way that is against the law or to create or propagate malware; or share, publish, distribute, or lease the software (except for any distributable code, subject to the terms above), provide the software as a stand-alone offering for others to use, or transfer the software or this agreement to any third party.
  Code: -32603

Thanks for the bug. This should be a dupe of #5009 which we fixed in 2023.10.53.

Thanks for transferring this issue and duplication searching! I didn't know that I should search for this in Pylance.


text:
Argument to class must be a base class

[!IMPORTANT]
The app works completely fine in runtime and produces no errors, it's just the linter giving the [TITLE] error

Environment data

Pylance version: v2024.11.2
OS and version: Darwin Kernel Version 24.1.0: arm64 (Sequoia 15.1.1 (24B91))
Python version (& distribution if applicable, e.g. Anaconda): Python 3.11.10 (Conda)

Code Snippet

minimal repro
from enum import Enum
from typing import Generic, TypeVar

T=TypeVar("T")

class A(Generic[T], Enum): pass

class B(A[int]): pass # Argument to class must be a base class Pylance[reportGeneralTypeIssues](https://github.com/microsoft/pyright/blob/main/docs/configuration.md#reportGeneralTypeIssues)

use case
from enum import Enum
from pydantic import BaseModel
from typing import Generic, TypeVar
from abc import ABC, abstractmethod

class Workflow(BaseModel, ABC):
    @property
    @abstractmethod
    def chat_interface(self):
        raise NotImplementedError(
            "Subclasses must implement the 'chat_interface' property")

TEnum = TypeVar("TEnum")

class NamedEnum(Generic[TEnum], Enum):
    """
    Effectively swaps the key with the value in an enum
    """

    def __init__(self, *args, **kwargs):
        self._old: TEnum = self._value_
        self._value_ = self._name_

    @classmethod
    def _missing_(cls, value: str):
        for member in cls:
            if member.name == value:
                return member
        return None

    @property
    def orig(self): return self._old

class ModelFlow(NamedEnum[Workflow]): # Argument to class must be a base class Pylance[reportGeneralTypeIssues](https://github.com/microsoft/pyright/blob/main/docs/configuration.md#reportGeneralTypeIssues)
    """
    Dynamically generated Enum from the `Workflow` subclasses.
    """
    @staticmethod
    def _generate_enum():
        subclasses = Workflow.__subclasses__()
        return {
            subclass.__name__: subclass
            for subclass in subclasses
        }

    locals().update(_generate_enum())

So that I can access .orig from a ModelFlow and use it as if it were a Workflow
Expected behavior
That it not error and that the .orig(...) type be a Workflow
Actual behavior
.orig is (property) orig: (self: Self@NamedEnum[TEnum@NamedEnum]) -> TEnum@NamedEnum
Logs

2024-11-21 18:59:22.850 [info] (23211) Attempting to resolve using local imports: Enum
2024-11-21 18:59:22.851 [info] (23211) Attempting to resolve using root path 'file:///projects/src/langchain/workflows'
2024-11-21 18:59:22.851 [info] (23211) Attempting to resolve using root path 'file:///projects/src/langchain'
2024-11-21 18:59:22.851 [info] (23211) Attempting to resolve using root path 'file:///projects/src'
2024-11-21 18:59:22.931 [info] (23211) [FG] parsing: file:///projects/.conda/lib/python3.11/site-packages/pydantic/_internal/_decorators.py [fs read 1ms] (8ms)
2024-11-21 18:59:22.933 [info] (23211) [FG] binding: file:///projects/.conda/lib/python3.11/site-packages/pydantic/_internal/_decorators.py (1ms)
2024-11-21 18:59:23.243 [info] (23211) [FG] parsing: file:///projects/src/langchain/workflows/__init__.py (1ms)
2024-11-21 18:59:23.243 [info] (23211) [FG] binding: file:///projects/src/langchain/workflows/__init__.py (0ms)
2024-11-21 18:59:23.344 [info] (23211) [BG(1)] SemanticTokens delta previousResultId:1732211959945 at file:///projects/src/langchain/workflows/__init__.py ...
2024-11-21 18:59:23.345 [info] (23211) [BG(1)]   parsing: file:///projects/src/langchain/workflows/__init__.py (0ms)
2024-11-21 18:59:23.345 [info] (23211) [BG(1)]   binding: file:///projects/src/langchain/workflows/__init__.py (1ms)
2024-11-21 18:59:23.412 [info] (23211) [BG(1)] SemanticTokens delta previousResultId:1732211959945 at file:///projects/src/langchain/workflows/__init__.py (68ms)
2024-11-21 18:59:23.727 [info] (23211) [FG] parsing: file:///projects/src/langchain/workflows/__init__.py (0ms)
2024-11-21 18:59:23.727 [info] (23211) [FG] binding: file:///projects/src/langchain/workflows/__init__.py (1ms)
2024-11-21 18:59:23.829 [info] (23211) [BG(1)] SemanticTokens delta previousResultId:1732211963345 at file:///projects/src/langchain/workflows/__init__.py ...
2024-11-21 18:59:23.829 [info] (23211) [BG(1)]   parsing: file:///projects/src/langchain/workflows/__init__.py (0ms)
2024-11-21 18:59:23.829 [info] (23211) [BG(1)]   binding: file:///projects/src/langchain/workflows/__init__.py (1ms)
2024-11-21 18:59:23.896 [info] (23211) [BG(1)] SemanticTokens delta previousResultId:1732211963345 at file:///projects/src/langchain/workflows/__init__.py (68ms)
2024-11-21 18:59:24.029 [info] (23211) [BG(1)] indexing: file:///projects/src/langchain/workflows/__init__.py [found 2] (0ms)
2024-11-21 18:59:24.029 [info] (23211) Workspace indexing done: file:///projects/src/langchain/workflows/__init__.py
2024-11-21 18:59:24.030 [info] [Info  - 18:59:24] (23211) Heap stats: total_memory_size=16384MB, total_free_size=125MB, total_heap_size=188MB, used_heap_size=140MB, cross_worker_used_heap_size=140MB, total_physical_size=188MB, total_available_size=3956MB, heap_size_limit=4096MB
2024-11-21 18:59:24.143 [info] (23211) [BG(1)] analyzing: file:///projects/src/api/routers/collections.py ...
2024-11-21 18:59:24.143 [info] (23211) [BG(1)]   checking: file:///projects/src/api/routers/collections.py (114ms)
2024-11-21 18:59:24.143 [info] (23211) [BG(1)] analyzing: file:///projects/src/api/routers/collections.py (114ms)
2024-11-21 18:59:24.145 [info] (23211) [BG(1)] analyzing: file:///projects/src/langchain/workflows/__init__.py ...
2024-11-21 18:59:24.145 [info] (23211) [BG(1)]   checking: file:///projects/src/langchain/workflows/__init__.py (1ms)
2024-11-21 18:59:24.145 [info] (23211) [BG(1)] analyzing: file:///projects/src/langchain/workflows/__init__.py (1ms)
2024-11-21 18:59:24.147 [info] (23211) [BG(1)] analyzing: file:///Users/brianferri/.vscode/extensions/ms-python.vscode-pylance-2024.11.2/dist/typeshed-fallback/stdlib/builtins.pyi ...
2024-11-21 18:59:24.148 [info] (23211) [BG(1)]   checking: file:///Users/brianferri/.vscode/extensions/ms-python.vscode-pylance-2024.11.2/dist/typeshed-fallback/stdlib/builtins.pyi ...
2024-11-21 18:59:24.148 [info] (23211) [BG(1)]     parsing: file:///Users/brianferri/.vscode/extensions/ms-python.vscode-pylance-2024.11.2/dist/typeshed-fallback/stdlib/_ast.pyi [fs read 1ms] (2ms)
2024-11-21 18:59:24.148 [info] (23211) [BG(1)]     binding: file:///Users/brianferri/.vscode/extensions/ms-python.vscode-pylance-2024.11.2/dist/typeshed-fallback/stdlib/_ast.pyi (1ms)
2024-11-21 18:59:24.152 [info] (23211) [BG(1)]     parsing: file:///Users/brianferri/.vscode/extensions/ms-python.vscode-pylance-2024.11.2/dist/typeshed-fallback/stdlib/sys/__init__.pyi [fs read 0ms] (4ms)
2024-11-21 18:59:24.153 [info] (23211) [BG(1)]     binding: file:///Users/brianferri/.vscode/extensions/ms-python.vscode-pylance-2024.11.2/dist/typeshed-fallback/stdlib/sys/__init__.pyi (1ms)
2024-11-21 18:59:24.156 [info] (23211) [BG(1)]     parsing: file:///projects/.conda/lib/python3.11/types.py [fs read 1ms] (3ms)
2024-11-21 18:59:24.157 [info] (23211) [BG(1)]     binding: file:///projects/.conda/lib/python3.11/types.py (1ms)
2024-11-21 18:59:24.159 [info] (23211) [BG(1)]     parsing: file:///projects/.conda/lib/python3.11/collections/abc.py [fs read 0ms] (0ms)
2024-11-21 18:59:24.159 [info] (23211) [BG(1)]     binding: file:///projects/.conda/lib/python3.11/collections/abc.py (1ms)
2024-11-21 18:59:24.165 [info] (23211) [BG(1)]     parsing: file:///projects/.conda/lib/python3.11/io.py [fs read 0ms] (6ms)
2024-11-21 18:59:24.167 [info] (23211) [BG(1)]     binding: file:///projects/.conda/lib/python3.11/io.py (1ms)
2024-11-21 18:59:24.183 [info] (23211) [BG(1)]     parsing: file:///Users/brianferri/.vscode/extensions/ms-python.vscode-pylance-2024.11.2/dist/typeshed-fallback/stdlib/io.pyi [fs read 0ms] (12ms)
2024-11-21 18:59:24.188 [info] (23211) [BG(1)]     binding: file:///Users/brianferri/.vscode/extensions/ms-python.vscode-pylance-2024.11.2/dist/typeshed-fallback/stdlib/io.pyi (5ms)
2024-11-21 18:59:24.194 [info] (23211) [BG(1)]     parsing: file:///Users/brianferri/.vscode/extensions/ms-python.vscode-pylance-2024.11.2/dist/typeshed-fallback/stdlib/_io.pyi [fs read 3ms] (10ms)
2024-11-21 18:59:24.195 [info] (23211) [BG(1)]     binding: file:///Users/brianferri/.vscode/extensions/ms-python.vscode-pylance-2024.11.2/dist/typeshed-fallback/stdlib/_io.pyi (1ms)
2024-11-21 18:59:24.221 [info] (23211) [BG(1)]     parsing: file:///projects/.conda/lib/python3.11/site-packages/typing_extensions.py [fs read 2ms] (25ms)
2024-11-21 18:59:24.226 [info] (23211) [BG(1)]     binding: file:///projects/.conda/lib/python3.11/site-packages/typing_extensions.py (5ms)
2024-11-21 18:59:24.343 [info] (23211) [BG(1)]     parsing: file:///Users/brianferri/.vscode/extensions/ms-python.vscode-pylance-2024.11.2/dist/typeshed-fallback/stdlib/ast.pyi [fs read 2ms] (9ms)
2024-11-21 18:59:24.346 [info] (23211) [BG(1)]     binding: file:///Users/brianferri/.vscode/extensions/ms-python.vscode-pylance-2024.11.2/dist/typeshed-fallback/stdlib/ast.pyi (3ms)
2024-11-21 18:59:24.414 [info] (23211) [BG(1)]   checking: file:///Users/brianferri/.vscode/extensions/ms-python.vscode-pylance-2024.11.2/dist/typeshed-fallback/stdlib/builtins.pyi (269ms)
2024-11-21 18:59:24.415 [info] (23211) [BG(1)] analyzing: file:///Users/brianferri/.vscode/extensions/ms-python.vscode-pylance-2024.11.2/dist/typeshed-fallback/stdlib/builtins.pyi (269ms)
2024-11-21 18:59:24.419 [info] (23211) [BG(1)] SemanticTokens delta previousResultId:1732211963829 at file:///projects/src/langchain/workflows/__init__.py (0ms)
2024-11-21 18:59:24.419 [info] (23211) [BG(1)] SemanticTokens delta previousResultId:1732211847089 at file:///projects/src/langchain/workflows/Workflow.py (0ms)
2024-11-21 18:59:24.419 [info] (23211) [BG(1)] SemanticTokens delta previousResultId:1732211959946 at file:///projects/src/api/routers/collections.py (0ms)

Could someone from the pylance team please transfer this to the pyright project? Thanks!

source: gharchive/issue

authors: brianferri erictraut

repo: microsoft/pylance-release

license_type: permissive

license_source: github-api


text:
[Responsible AI Dashboard] Cohort deletion from cohort settings

Describe the bug
It is not possible to delete cohorts from cohort settings.
To Reproduce
Steps to reproduce the behavior:

Go to 'Cohort settings'
Click on 'delete button for one of the created cohorts (not all)'

Stack trace
(index):17
   Uncaught TypeError: Cannot read properties of undefined (reading 'cohort')
at Gu.onDeleteCohortClick ((index):17:2829054)
at Uu.onDeleteCohortClick [as onClick] ((index):17:2826443)
at r._onClick ((index):17:315965)
at Object.He ((index):17:8352688)
at Ge ((index):17:8352842)
at (index):17:8370506
at xa ((index):17:8370600)
at _a ((index):17:8371014)
at (index):17:8376583
at Oe ((index):17:8452288)

Expected behavior
Cohort needs to be disappearing from the list and also from the UI of the rest of the components
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: Windows
Browser: Edgecon
Python version: 3.9.13
raiwidgets and responsibleai package versions [e.g. 0.19.0]

To get the package versions please run in your command line:
pip show raiwidgets
pip show responsibleai

Name: raiwidgets
Version: 0.21.0
Name: responsibleai
Version: 0.21.0
Additional context
Add any other context about the problem here.

PR https://github.com/microsoft/responsible-ai-toolbox/pull/1738 should fix this.

authors: gaugup nushib

repo: microsoft/responsible-ai-toolbox

license: MIT


text:
Disable save as new cohort button if nothing is selected in error tree

Description
Disable save as new cohort button if nothing is selected in error tree.
Also adds UI tests for error analysis to validate this button and the clear selection button are working.
Areas changed

npm packages changed:

[ ] responsibleai/causality
[ ] responsibleai/core-ui
[ ] responsibleai/counterfactuals
[ ] responsibleai/dataset-explorer
[ ] responsibleai/fairness
[ ] responsibleai/interpret
[ ] responsibleai/localization
[ ] responsibleai/mlchartlib
[x] responsibleai/model-assessment

Python packages changed:

[ ] erroranalysis
[ ] raiutils
[ ] raiwidgets
[ ] rai_core_flask
[ ] responsibleai

Tests

[ ] No new tests required.
[x] New tests for the added feature are part of this PR.
[ ] I validated the changes manually.

Screenshots (if appropriate):
Documentation:

[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.

Codecov Report

Merging #1327 (53b87a4) into main (db7b68b) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 53b87a4 differs from pull request most recent head eb0b284. Consider uploading reports for the commit eb0b284 to get more accurate results

@@           Coverage Diff           @@
##             main    #1327   +/-   ##
=======================================
  Coverage   89.92%   89.92%
=======================================
  Files          80       80
  Lines        3394     3394
=======================================
  Hits         3052     3052
  Misses        342      342

Flag
Coverage Δ

unittests
89.92% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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 db7b68b...eb0b284. Read the comment docs.

source: gharchive/pull-request

authors: codecov-commenter imatiach-msft


text:
MacOS/Linux Support?

Does this tool support Mac/Linux?
When I compiled the tool and ran the quick-start.py I saw in the error:

python3 restler-quick-start.py --api_spec_path $REDACTED/data/file.json --restler_drop_dir $REDACTED/restler-fuzzer-7.2.0/restler_bin
System.Exception: Platform not supported

The documentation only references Windows, so it would be nice to know if windows is the only intended target.

Please see the main README.md https://github.com/microsoft/restler-fuzzer :
RESTler was designed to run on 64-bit machines with Windows or Linux.

Sure, but all the documentation is for Windows.

Hello,
It should work on Linux, but we have only been testing on Ubuntu (restler-quick-start.py is running in the build pipeline).  Could you please share more about the system and setup you have?
Correct, MacOS isn't supported.
Thanks,
Marina

I was trying on MacOS to start with, I'll switch over to Ubuntu and go from there.
If I did not want to use reslter-quick-start and manually invoke the process separately e.g. compile is there examples of how I may do that for linux?

TutorialDemoServer.md shows the separate phases, though it's currently Windows-specific.  I'll go through it and send a PR in the next day or so to add Linux commands.
I believe the only things that need to be changed in that tutorial for Linux are the path to the executable (./restler/Restler) and the paths in the arguments.

Hi @alexbrahastoll,
This is most likely a failure to find python on the path.  RESTler should issue a different error message for each of the arguments to the file (e.g. if you try with an invalid path to the grammar, you should see an error message rather than a crash).
Can you please check if 'python' is on the path and the right version before you invoke ./Restler?
We have an upcoming feature to specify the full path to python on the command line, which will also help troubleshoot such issues, and we'll improve the error handling as part of implementing that issue.

@alexbrahastoll  - we are working closely with RESTler team to make it easier to integrate RESTler into CI/CD pipelines.
The idea of the project to run RESTler in Azure. But I just merged a PR that will run same configurations locally.
https://github.com/microsoft/rest-api-fuzz-testing/tree/main/cli
raft_local.py - is the file that enables that
Also there is official Microsoft RESTler Docker container that we maintain (using Alpine Linux):
https://hub.docker.com/_/microsoft-restlerfuzzer-restler

Also there is official Microsoft RESTler Docker container that we maintain (using Alpine Linux):
https://hub.docker.com/_/microsoft-restlerfuzzer-restler

I switched from a custom dockerfile to this one (mcr.microsoft.com/restlerfuzzer/restler:v7.2.0), which also consistently raises this error when I invoke restler test <options>, or dotnet <path-to-Restler.dll> test <options>. Interestingly enough, restler compile works just fine in both images (custom and official).

Hello @wuhkuh, thank you for reporting this.  We will investigate.
(The compile step does not invoke python, only the test/fuzz steps, so it is likely a problem with finding python on the path.)

PR #158 should resolve the issue in the official RESTler container and provide a workaround for different Python installations.

@alexbrahastoll @wuhkuh Please let us know if the latest RESTler commit resolves this for you.

Yes! That seemed to have fixed the error. It was indeed caused by an improper installation of Python 3. Thank you!

@stishkin Thanks, I will take a look at the image you have mentioned.
@marina-p I have Python 3.8.2 installed and correctly configured in the PATH. I will check out the updated version of RESTler in a couple days and I let you know if it solved the issue I reported above. Thank you for the fast reply.

Hi All,

@marina-p I have upgraded RESTler and I have also added pip and the libraries requests and applicationinsights as part of the steps of the Dockerfile I am working with. I added pip and the libraries after taking a look at the Dockerfile for the container mentioned by @stishkin. Are these mandatory requirements for RESTler? If so, it would be nice to add them to the list of requirements in the project's documentation.
I was able to run RESTler now, but I am not sure if what solved the issue I was having was the new version, the Python libraries I mentioned or both.
A bit out of topic, but let me make a quick question: which OpenAPI versions are supported by RESTler? I suppose this is mentioned somewhere, but I searched a bit and I was not able to find this information. I had some issues with an OpenAPI 3 spec and was wondering if RESTler supports or not this latest version of the OpenAPI specification.
Thanks!

@marina-p Nevermind my comment about issues with an OpenAPI 3 spec. My specification was missing the openapi key and after I added it, RESTler was able to correctly parse the spec and generate a proper grammar.py.

authors: LewisArdern PatGod alexbrahastoll marina-p stishkin taivnn9 wuhkuh

repo: microsoft/restler-fuzzer


text:
Make cancelation configurable

[Re-filing as I screwed up and converted to a discussion when I did it in the wrong tab. Originally #293]
Offline feedback from the StackOverflow team.
Two cancellation tokens are used when proxying requests, a short one and a long one.
https://github.com/microsoft/reverse-proxy/blob/a3b5e1b9b03fcec8bc764b033b5c066838a8ffe9/src/ReverseProxy/Middleware/ProxyInvokerMiddleware.cs#L76-L87
The short token defaults to a 30 second timeout and is not currently configurable. This tracks the amount of time the destination has to respond with headers (not body). It's also linked to the long token.

This timeout should be configurable globally
Should there be a way to override it per route or cluster?

The long token is actually the HttpContext.RequestAborted token. It's used to track the response body. This tells the destination to abort if the client disconnects.

Does this need to be configurable in any way?
Should there also be a timeout applied to this part of the request? Configurable at what level?
Timeouts on the body don't work well for varying sized responses, or for streaming scenarios.
Middleware could add its own timeouts per request by augmenting RequestAborted.

@scalablecory, @alnikola - why does the 30s timeout seem familiar for something baked into the networking stack?

Should there be a way to override it per route or cluster?

Yes! :). We recently implemented configurability at the Cluster level by adding a top level property ProxyTimeout on ClusterConfig. Being able to set it per route would also be useful. Order of precedence IMHO should be RouteConfig --> ClusterConfig --> Global value.

Related: When retries are implemented, it will be important to further distinguish timeout per attempt, and global timeout for all attempts.
Additional reading: Timeouts in Envoy, per_try_timeout

@scalablecory, @alnikola - why does the 30s timeout seem familiar for something baked into the networking stack?

Doesn't ring any bells to me. Could you be thinking of the ~60 second Socket.Connect() timeout in Windows?

Per-route would be ideal for our use cases, but per-cluster would be sufficient.

Could we start with the global timeout and potentially do the others later on? The static 30 is causing constant issues for us, especially on first request when the app behind the proxy is spinning up.

@NickCraver How about I start by bumping it to 100s to match HttpClient's traditional default?

@Tratcher that would definitely help - practically speaking we wouldn't need to adjust it for the 95% case after that. Until we can configure it, that'd be a very welcomed change! /cc @deanward81

@NickCraver ok, I'll tweak it in https://github.com/microsoft/reverse-proxy/pull/406 for preview5 since I'm about to mess with timeouts anyways.

Fixed in https://github.com/microsoft/reverse-proxy/pull/512

authors: ManickaP NickCraver Tratcher amweiss davidni samsp-msft scalablecory

repo: microsoft/reverse-proxy


text:
align-deps not aware of dependencies of react-native-code-push

What happened?
I just upgraded react-native from 0.70 to 0.71. After making all the required changes to RN template files, I ran rnx-align-deps and inspected the results. It did not tell me my react-native-code-push was incompatible with 0.71. I had to track down a very inscrutable error message until I finally found this issue and realized I needed to update RNCodePush.
If I hadn't had access to rnx-kit align-deps I probably would have checked code-push compatibility before trying to build, because I am aware it's one of the packages that can have this problem. But I was counting on align-deps to find these dependencies, and I would have thought that since code-push is a popular package, and built by (ahem), the same company, that it would be included.
Perhaps I'm misunderstanding what I should be expecting from align-deps?
Affected Package
@rnx-kit/align-deps
Version
2.4.2
Which platforms are you seeing this issue on?

[X] Android
[X] iOS
[ ] macOS
[ ] Windows

System Information
info Fetching system and libraries information...
System:
    OS: macOS 14.3.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 112.56 MB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 18.12.1 - ~/.nodenv/versions/18.12.1/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 8.19.2 - ~/.nodenv/versions/18.12.1/bin/npm
    Watchman: 2022.11.28.00 - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.12.1 - /Users/chet/.rbenv/shims/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 23.2, iOS 17.2, macOS 14.2, tvOS 17.2, visionOS 1.0, watchOS 10.2
    Android SDK: Not Found
  IDEs:
    Android Studio: 2023.2 AI-232.10300.40.2321.11567975
    Xcode: 15.2/15C500b - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.18 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.2.0 => 18.2.0
    react-native: 0.71.18 => 0.71.18
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps to Reproduce
This is my package.json
{
  "name": "MalaMode",
  "version": "3.0.3",
  "license": "UNLICENSED",
  "private": "true",
  "type": "app",
  "description": "Firebase-based counter",
  "bundleId": "io.malamode.MalaMode",
  "scripts": {
    "android": "react-native run-android --appId io.malamode.debug --port 8082",
    "droid": "react-native run-android --variant=releaseStaging --appId io.malamode.staging",
    "ndroid": "react-native run-android --appIdSuffix \"\"",
    "cli-version": "react-native --version",
    "ios": "react-native run-ios",
    "lint": "eslint .",
    "start": "react-native start",
    "version": "react-native-version --never-amend --target ios && git add .",
    "postinstall": "patch-package",
    "clean": "react-native-clean-project",
    "prettier": "prettier --write .",
    "check-dependencies": "rnx-align-deps",
    "fix-dependencies": "rnx-align-deps --write",
    "tests-all": "mocha -u exports -R spec --compilers js:babel/register --require babel-core/external-helpers test",
    "test": "jest"
  },
  "prettier": {
    "singleQuote": true
  },
  "devDependencies": {
    "@babel/core": "^7.20.0",
    "@babel/preset-env": "^7.20.0",
    "@babel/runtime": "^7.20.0",
    "@bugsnag/source-maps": "^2.3.1",
    "@react-native-community/eslint-config": "^3.2.0",
    "@rnx-kit/align-deps": "^2.4.2",
    "@tsconfig/react-native": "^2.0.2",
    "@types/jest": "^29.2.1",
    "@types/react": "^18.0.24",
    "@types/react-test-renderer": "^18.0.0",
    "babel-core": "^6.0.0",
    "babel-jest": "^29.2.1",
    "babel-polyfill": "^6.9.1",
    "babel-preset-es2015": "^6.5.0",
    "babel-preset-react": "^6.5.0",
    "babel-preset-stage-1": "^6.5.0",
    "babelify": "^6.1.3",
    "browserify": "^11.0.1",
    "code-push": "^1.10.0-beta",
    "eslint": "^8.19.0",
    "express": "^4.12.3",
    "jest": "^29.2.1",
    "metro-react-native-babel-preset": "0.73.10",
    "node-libs-browser": "^0.5.2",
    "patch-package": "^6.2.0",
    "postinstall-postinstall": "^2.0.0",
    "prettier": "2.0.5",
    "proxy-middleware": "^0.11.0",
    "react-test-renderer": "18.2.0",
    "require-from": "^0.10.0",
    "source-map": "^0.5.6",
    "typescript": "4.8.4"
  },
  "dependencies": {
    "@bugsnag/react-native": "^7.18.0",
    "@firebase/app-types": "0.x",
    "@react-native-async-storage/async-storage": "1.17.11",
    "@react-native-community/datetimepicker": "^6.7.5",
    "@react-native-community/netinfo": "^9.0.0",
    "@react-native-community/push-notification-ios": "1.10.1",
    "@react-native-community/slider": "^4.3.1",
    "@react-navigation/bottom-tabs": "^6.5.7",
    "@react-navigation/drawer": "^6.x",
    "@react-navigation/native": "^6.1.6",
    "@react-navigation/native-stack": "^6.9.12",
    "@react-navigation/stack": "^6.3.16",
    "@types/alt": "^0.16.39",
    "alt": "=0.17.1",
    "alt-mixins": "chetstone/mixins#chetstone-patch-1",
    "create-react-class": "^15.6.3",
    "debug": "chetstone/debug#no-document",
    "deep-equal": "^1.0.1",
    "deprecated-react-native-prop-types": "^5.0.0",
    "firebase": "10",
    "hoist-non-react-statics": "^3.3.0",
    "localforage": "^1.2.7",
    "markdown-to-react-components": "^0.2.0",
    "moment": "^2.10.6",
    "moment-duration-format": "^2.2.2",
    "prop-types": "^15.7.2",
    "react": "18.2.0",
    "react-bootstrap": "^0.28.3",
    "react-dom": "^18.1.0",
    "react-native": "0.71.18",
    "react-native-button": "^3.0.1",
    "react-native-code-push": "^7.1.0",
    "react-native-device-info": "https://github.com/chetstone/react-native-device-info.git#rn70",
    "react-native-dialog-input": "^1.0.8",
    "react-native-draggable-flatlist": "^4.0.1",
    "react-native-gesture-handler": "^2.9.0",
    "react-native-iap": "^12.3.2",
    "react-native-idle-timer": "^2.1.6",
    "react-native-image-base64": "^0.1.4",
    "react-native-image-picker": "^5.3.1",
    "react-native-image-resizer": "^1.4.5",
    "react-native-mail": "^4.0.0",
    "react-native-modal-datetime-picker": "^11.0.0",
    "react-native-palette": "^1.2.2",
    "react-native-push-notification": "^8.1.1",
    "react-native-radio-buttons": "^1.0.0",
    "react-native-reanimated": "^2.x",
    "react-native-safe-area-context": "^4.5.0",
    "react-native-screens": "^3.20.0",
    "react-native-sortable-list": "gitim/react-native-sortable-list#78c8ec0e66ba792784131065fbeab3f365deb0dc",
    "react-native-sound": "^0.11.0",
    "react-native-spinkit": "^1.5.1",
    "react-native-status-bar-height": "^2.5.0",
    "react-native-swipe-list-view": "^2.5.0",
    "react-native-tableview": "^3.0.0",
    "react-native-tableview-simple": "^3.2.0",
    "react-native-tabs": "^1.0.9",
    "react-native-vector-icons": "^9.2.0",
    "react-native-watch-connectivity": "^1.1.0",
    "react-native-webview": "^11.23.0",
    "react-navigation-props-mapper": "^3.1.0",
    "react-timer-mixin": "^0.13.3"
  },
  "jest": {
    "preset": "react-native"
  },
  "resolutions": {
    "@types/react": "=16.9.0"
  },
  "rnx-kit": {
    "kitType": "app",
    "alignDeps": {
      "presets": [
        "microsoft/react-native"
      ],
      "requirements": [
        "react-native@0.71"
      ],
      "capabilities": [
        "animation",
        "babel-preset-react-native",
        "core",
        "core-android",
        "core-ios",
        "datetime-picker",
        "gestures",
        "jest",
        "navigation/native",
        "navigation/stack",
        "netinfo",
        "react",
        "react-dom",
        "react-test-renderer",
        "safe-area",
        "screens",
        "storage",
        "webview"
      ]
    }
  }
}

Code of Conduct

[X] I agree to follow this project's Code of Conduct

The whole list of packages that are part of the default preset (as mentioned in many places across the documentation) can be found here: https://github.com/microsoft/rnx-kit/tree/main/packages/align-deps#capabilities
As you can see there, codepush is not one of those. That's precisely why we have a way for expanding and customizing the presets.
By the way, keep in mind that:

Visual Studio App Center is scheduled for retirement on March 31, 2025. After that date it will not be possible to sign in with your user account nor make API calls. App Center will continue to be supported until March 31, 2025, with critical bug fixes and technical support.

find more info in the dedicated documentation.

Thanks for the heads up about codepush retirement. Frankly, I haven't actually used it to update production apps for a few years. Maybe I'll just remove it.

authors: chetstone kelset

repo: microsoft/rnx-kit


text:
Unable to label a feature as a different secondary class by selecting it on the side-menu in the labeling tool

Summary
Unable to label a feature as a different secondary class by selecting it on the side-menu in the labeling tool
Overview
In the labeling tool, I selected one of the secondary class properties that I had defined in the project builder and drew a shape around a building. When I saved the labeled task files and loaded them onto the project viewer, the shapes were not labeled as the secondary class property that I selected before drawing them. The secondary class options were 0, 1, 2, 3, 4, and 5, but no matter what I selected each shape remained labeled as 0, which seemed to be the default since it was the first secondary class that I added. The only way I was able to successfully apply a different secondary class in the labeler was to draw the shapes first, click  the rectangle select button, and then click the shapes and edit the secondary class that way (rather than before/as I drew them).
Steps to reproduce

Open the project builder.
On Step 1: Project details, fill in a project name (i.e. “testing”) and click next.
On Step 2: Add layers, keep the default layers and click next.
On Step 3: Create focus area, draw a focus area of the University of Massachusetts Amherst (or anywhere). Adjust the grid size and focus area so that they align with each other.
On Step 4: Define classes, change the Primary class display name and Primary class property name to “building”.
Under primary classes, add the primary class “building” and press the green plus(+) sign to add it.
Click Capture secondary class.
Change the Secondary class display name to “Damage severity” and the Secondary class property name to “damage_severity”.
Under Secondary classes, add the following secondary classes: 0, 1, 2, 3, 4, and 5.
Click next to Step 5: Complete and download the project files.
Open the project labeler.
Under Import data, load one of the task files from your downloaded project files.
Under Damage severity on the right-hand side menu, select “5” as the secondary class.
Select the draw-polygon option and trace one of the buildings.
Select a Damage severity of “3” and trace another building.
Navigate to the Save page and save your labeled task file.
Put the output file that you just saved into the results folder of the project builder output folder and zip the project builder folder.
Open the project viewer.
Load the zipped project builder folder onto the project viewer.
On the left-hand side, change the View to Damage severity.
Notice on the left that two labeled features are listed as having a damage severity of 0.
Click on the labeled buildings.
Notice that the the damage_severity remains at 0 for both buildings.

Expected result:
Before drawing a shape around a building in the labeler, I selected one of the secondary class options that I had previously defined in the project builder to label the building as. Once labeled and loaded into the project viewer, I expected to see the features labeled as the secondary classes that I selected for them.
Actual result:
The features were not labeled as the secondary classes that I selected for them, but instead remained labeled as the default secondary class that was already selected before I changed the selection.
Helpful screenshots
Project builder configuration:

Labeling features with secondary class selected on side-menu:

Results of labeled features in project viewer:

Thank you for the detailed issue report. I'll try and look into this next week.

Found the issue, checked in the fix. A single line of missing code related to the bulk edit functionality that was added a few months back was the source of the issue. Thanks again for highlighting this issue.

No problem, glad it was solved!

authors: lsaloio rbrundritt


text:
Python: No module named 'semantic_kernel.core_skills'

#Describe the bug
When attempting to import TimeSkill from the semantic_kernel.core_skills module, the interpreter throws a ModuleNotFoundError. This error suggests that either the module does not exist within the package or the package structure is not recognized by the interpreter.
##To Reproduce
Steps to reproduce the behavior:
Set up a new environment and install the semantic-kernel package.
Create a new Python file and insert the provided code snippet.
Run the file with the Python interpreter.
The ModuleNotFoundError occurs, stating: "No module named 'semantic_kernel.core_skills'".
##Expected behavior
The expected behavior would be for the TimeSkill class to be successfully imported from semantic_kernel.core_skills, allowing the script to run and execute the main function without import errors.
Platform
OS: Windows 10
IDE: VS Code
Language: Python

Hi @Sarfaraz021, which version of the Python package are you using? As of 0.4.6.dev0, we've renamed all skill instances to plugin.

Please upgrade to the latest package, for example, 0.9.0b1. Closing this as a non-issue. If you need further help, feel free to re-open.

@moonbox3 Thanks for the updates, am using python-3.11.5

repo: microsoft/semantic-kernel


text:
[BUG] - test bug to see if project filter works

Describe the bug
A clear and concise description of what the bug is.
This is a test, this is only a test
Area/Component:
Please mention area or component in Service Fabric where issue was found. Ex: security, monitoring, placement or resource governance, Reliable services, Actors, programming models,SDK,.etc.
To Reproduce
Steps to reproduce the behavior:

Go to '...' 1
Click on '....' 2
Scroll down to '....'3
See error

Expected behavior
A clear and concise description of what you expected to happen.
For this to show up in bug bucket
Observed  behavior:
Screenshots
If applicable, add screenshots to help explain your problem.
Service Fabric Runtime Version:
ex: 7.1., 7.2.
Environment:

Must be one of these values [Standalone OR Azure OR OneBox/Dev cluster]
OS: [e.g. Windows 2019, Ubuntu 18.04]
Version [e.g. 7.1, 7.2 ]

If this is a regression, which version did it regress from?
Additional context
Add any other context about the problem here.

Assignees: /cc @microsoft/service-fabric-triage

@craftyhouse  Closing test issue

authors: athinanthny craftyhouse

repo: microsoft/service-fabric


text:
OpenBSD support

We currently have OpenBSD in CI, but the system is failing to initialise the pagemap.
I believe this is because the pagemap is very large, and OpenBSD does not support overcommit. I could not find a MAP_NORESERVE like flag that could be used.
Given the current design, I do not see a way to support an OS that does not separate the concept of reserve and commit, either explicitly as in Windows, or implicitly as in Linux and FreeBSD.
I am raising this issue to track thoughts on this.
@nwf-msr, @davidchisnall, @devnexen

OpenBSD does not support overcommit nor have any sort of OOM as linux has, instead the memory allocation will just fail.

How did it ever work on OpenBSD? Did it only work on 32-bit systems?

Originally, the pagemap was only 16MiB (i.e. in the paper). So at that point it could have worked reasonably.  I am thinking we should drop OpenBSD from the CI?

IIRC, snmalloc1 also had a tree-based PageMap option... someone very keen on OpenBSD support could reinstate that?  (It should be relatively straightforward as these things go?)

authors: davidchisnall devnexen mjp41 nwf-msr

repo: microsoft/snmalloc


text:
Show the current directory in the Visual Studio Developer Powershell terminal window

When I right-click a project in the Visual Studio Solution Explorer, and choose "Open in Terminal", I get the Powershell window open. However, the title of this window seems to be fixed at "Developer Powershell", and does not seem to be updated the way a regular Powershell window's title is.
My Powershell profile contains the following...
function Prompt {
    $host.UI.RawUI.WindowTitle = Get-Location
    Write-Host ("" + $(get-location) +">") -nonewline -foregroundcolor Yellow
    return " "
}

When in a regular Powershell window (ie not opened from within VS), my command prompt is set correctly, and the window title shows the current directory. However, in the VS Developer Powershell terminal window, whilst the command prompt is set, the title never changes.
I would like the VS Developer Powershell terminal window to change its title to show the current directory (or whatever else I choose in my profile).
Note that whilst this is useful in a regular Powershell window, it's not vital, as you're not usually more than a few lines from a command prompt, so you can easily see the current directory. However, when using the terminal in VS, dotnet watch run produces a lot of output, and your last command prompt quickly scrolls away to the far distance, leaving you with a LOT of scrolling to check which directory you're in. When working with multiple terminals (for multiple projects in a solution), this makes it very difficult to keep track of which terminal window is for which project.

@zadjii-msft I don't have a folder by that name. Here is a list of the folders under C:\Users\MyUserName\AppData\Local\Packages...
1527c705-839a-4832-9118-54d4Bd6a0c89_cw5n1h2txyewy
ActiveSync
c5e2524a-ea46-4f67-841f-6a9465d9d515_cw5n1h2txyewy
chrome.sandbox.xrdevicef5200eafd3ad904629cbb0f87a78a3c7211081fe
cr.sb.cdmf5200eafd3ad904629cbb0f87a78a3c7211081fe
cr.sb.xrf5200eafd3ad904629cbb0f87a78a3c7211081fe
E2A4F912-2574-4A75-9BB0-0D023378592B_cw5n1h2txyewy
F46D4000-FD22-4DB4-AC8E-4E1DDDE828FE_cw5n1h2txyewy
Microsoft.549981C3F5F10_8wekyb3d8bbwe
Microsoft.AAD.BrokerPlugin_cw5n1h2txyewy
Microsoft.AccountsControl_cw5n1h2txyewy
Microsoft.Advertising.Xaml_8wekyb3d8bbwe
Microsoft.AsyncTextService_8wekyb3d8bbwe
Microsoft.BingWeather_8wekyb3d8bbwe
Microsoft.BioEnrollment_cw5n1h2txyewy
Microsoft.CredDialogHost_cw5n1h2txyewy
Microsoft.DesktopAppInstaller_8wekyb3d8bbwe
Microsoft.ECApp_8wekyb3d8bbwe
Microsoft.GetHelp_8wekyb3d8bbwe
Microsoft.Getstarted_8wekyb3d8bbwe
Microsoft.HEIFImageExtension_8wekyb3d8bbwe
Microsoft.LanguageExperiencePacken-GB_8wekyb3d8bbwe
Microsoft.LanguageExperiencePackhe-IL_8wekyb3d8bbwe
Microsoft.LockApp_cw5n1h2txyewy
Microsoft.Microsoft3DViewer_8wekyb3d8bbwe
Microsoft.MicrosoftEdge.Stable_8wekyb3d8bbwe
Microsoft.MicrosoftEdgeDevToolsClient_8wekyb3d8bbwe
Microsoft.MicrosoftEdge_8wekyb3d8bbwe
Microsoft.MicrosoftOfficeHub_8wekyb3d8bbwe
Microsoft.MicrosoftSolitaireCollection_8wekyb3d8bbwe
Microsoft.MicrosoftStickyNotes_8wekyb3d8bbwe
Microsoft.MixedReality.Portal_8wekyb3d8bbwe
Microsoft.MSPaint_8wekyb3d8bbwe
Microsoft.NET.Native.Framework.1.7_8wekyb3d8bbwe
Microsoft.NET.Native.Framework.2.1_8wekyb3d8bbwe
Microsoft.NET.Native.Framework.2.2_8wekyb3d8bbwe
Microsoft.NET.Native.Runtime.1.7_8wekyb3d8bbwe
Microsoft.NET.Native.Runtime.2.1_8wekyb3d8bbwe
Microsoft.NET.Native.Runtime.2.2_8wekyb3d8bbwe
Microsoft.Office.OneNote_8wekyb3d8bbwe
Microsoft.People_8wekyb3d8bbwe
Microsoft.Photos.MediaEngineDLC_8wekyb3d8bbwe
Microsoft.Print3D_8wekyb3d8bbwe
Microsoft.ScreenSketch_8wekyb3d8bbwe
Microsoft.Services.Store.Engagement_8wekyb3d8bbwe
Microsoft.StorePurchaseApp_8wekyb3d8bbwe
Microsoft.Todos_8wekyb3d8bbwe
Microsoft.UI.Xaml.2.0_8wekyb3d8bbwe
Microsoft.UI.Xaml.2.1_8wekyb3d8bbwe
Microsoft.UI.Xaml.2.2_8wekyb3d8bbwe
Microsoft.UI.Xaml.2.3_8wekyb3d8bbwe
Microsoft.UI.Xaml.2.4_8wekyb3d8bbwe
Microsoft.UI.Xaml.2.5_8wekyb3d8bbwe
Microsoft.UI.Xaml.2.6_8wekyb3d8bbwe
Microsoft.UI.Xaml.2.7_8wekyb3d8bbwe
Microsoft.VCLibs.140.00.UWPDesktop_8wekyb3d8bbwe
Microsoft.VCLibs.140.00_8wekyb3d8bbwe
Microsoft.VP9VideoExtensions_8wekyb3d8bbwe
Microsoft.Wallet_8wekyb3d8bbwe
Microsoft.WebMediaExtensions_8wekyb3d8bbwe
Microsoft.WebpImageExtension_8wekyb3d8bbwe
Microsoft.Whiteboard_8wekyb3d8bbwe
Microsoft.Win32WebViewHost_cw5n1h2txyewy
Microsoft.Windows.Apprep.ChxApp_cw5n1h2txyewy
Microsoft.Windows.AssignedAccessLockApp_cw5n1h2txyewy
Microsoft.Windows.CallingShellApp_cw5n1h2txyewy
Microsoft.Windows.CapturePicker_cw5n1h2txyewy
Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy
Microsoft.Windows.ContentDeliveryManager_cw5n1h2txyewy
Microsoft.Windows.NarratorQuickStart_8wekyb3d8bbwe
Microsoft.Windows.OOBENetworkCaptivePortal_cw5n1h2txyewy
Microsoft.Windows.OOBENetworkConnectionFlow_cw5n1h2txyewy
Microsoft.Windows.ParentalControls_cw5n1h2txyewy
Microsoft.Windows.PeopleExperienceHost_cw5n1h2txyewy
Microsoft.Windows.Photos_8wekyb3d8bbwe
Microsoft.Windows.PinningConfirmationDialog_cw5n1h2txyewy
Microsoft.Windows.Search_cw5n1h2txyewy
Microsoft.Windows.SecHealthUI_cw5n1h2txyewy
Microsoft.Windows.SecureAssessmentBrowser_cw5n1h2txyewy
Microsoft.Windows.ShellExperienceHost_cw5n1h2txyewy
Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy
Microsoft.Windows.XGpuEjectDialog_cw5n1h2txyewy
Microsoft.WindowsAlarms_8wekyb3d8bbwe
Microsoft.WindowsCalculator_8wekyb3d8bbwe
Microsoft.WindowsCamera_8wekyb3d8bbwe
microsoft.windowscommunicationsapps_8wekyb3d8bbwe
Microsoft.WindowsFeedbackHub_8wekyb3d8bbwe
Microsoft.WindowsMaps_8wekyb3d8bbwe
Microsoft.WindowsSoundRecorder_8wekyb3d8bbwe
Microsoft.WindowsStore_8wekyb3d8bbwe
Microsoft.Xbox.TCUI_8wekyb3d8bbwe
Microsoft.XboxGameCallableUI_cw5n1h2txyewy
Microsoft.XboxGameOverlay_8wekyb3d8bbwe
Microsoft.XboxGamingOverlay_8wekyb3d8bbwe
Microsoft.XboxIdentityProvider_8wekyb3d8bbwe
Microsoft.XboxSpeechToTextOverlay_8wekyb3d8bbwe
Microsoft.YourPhone_8wekyb3d8bbwe
Microsoft.ZuneMusic_8wekyb3d8bbwe
MicrosoftWindows.Client.CBS_cw5n1h2txyewy
MicrosoftWindows.UndockedDevKit_cw5n1h2txyewy
NcsiUwpApp_8wekyb3d8bbwe
RealtekSemiconductorCorp.RealtekAudioControl_dt26b99r8h8gj
Windows.CBSPreview_cw5n1h2txyewy
windows.immersivecontrolpanel_cw5n1h2txyewy
Windows.PrintDialog_cw5n1h2txyewy
windows_ie_ac_001

Should I have one?
In case it helps, I'm on Windows 10 x64 using Powershell version 5.1.19041.1682 and Visual Studio Community 2022 17.2.0
Thanks

@zadjii-msft Yup, that's exactly what I'm seeing. Thanks for the explanation and link

repo: microsoft/terminal


text:
Hangs  when opening file selection window for command line in new profile

Windows Terminal version
1.20.11781.0
Windows build number
Microsoft Windows [Version 10.0.19045.4894]
Other Software
No response
Steps to reproduce

Open Windows Terminal
click drop down menu
select Settings
select Add new profile (left panel)
choose a different profile to duplicate
click Duplicate (right panel)
click Command Line
don't edit the path in the provided field, instead select Browse...

the file selection window popup appears but freezes and you cannot input anything, select any file, or cancel and close the popup to return to your terminal session, you need to either wait a LOT of minutes (varies, sometimes returns control after closing some other window, some times it does not come back ever)
Expected Behavior
Let you chose a file with your mouse or keyboard navigating in the opened file browser popup or type the path in the "Filename:" input box at the bottom of the opened file selection window.
Actual Behavior
Does not let you type any text in the filename field nor does itlet you choose a file with mouse or keyboard from the file selection window.
The text cursor does blinkbut I cannot type anything.

task manager shows no resources being aggressively consumed

Thanks for filing! Yeah, this is a /dup of #12199

authors: aranapatona carlos-zamora


text:
Fix wrong CommandPallete access

Closes: #17032
We were wrongly calling the Ctor of CommandPalette which led to the creation of an uninitialized winrt command palette object, and then OnCreateAutomationPeer() was called on that. This seems to be the cause of #17032.
Validation Steps Performed

Open WT.
Try to tear off a tab out of the tab headers view.
WT doesn't crash.

Do you by chance know when this regressed?

Do you by chance know when this regressed?

I think it was https://github.com/microsoft/terminal/pull/15313 which reverted some code that used CommandPalette() prior to https://github.com/microsoft/terminal/pull/15203. The latter renamed the command Palette component to its current name.
The timing was just prefect 😅

authors: DHowett tusharsnx


text:
Attempt to clean up PCHs as we build to leave more Hosted Agent disk space

This cleans up PCHs on CI machines only as builds continue to attempt to mitigate the 10GB maximum scratch space limitation.

/azp run

authors: DHowett-MSFT miniksa


text:
"./" to "./*" in packages.json

(node:27404) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at {APPPATH}\node_modules\tslib\package.json.
Update this package.json to use a subpath pattern like "./*".
(Use node --trace-deprecation ... to show where the warning was created)
In my node_modules I changed the above and it works. It has to be fixed

This thread has been repeated many times, it is already fixed. There is only one step we are still waiting. We need that https://github.com/DanielRosenwasser creates a release with current main branch.

Ok, nice. lookig forward to see this be released.

Should be out now.

authors: DanielRosenwasser Neizan93 naushadnizarali oliverkierepka

repo: microsoft/tslib


text:
Improve Localization Support

The work support undocked localization build support has been started but is not complete. The work needs to be finished up and sample onboarded to the CI.

Support for compiling message files has been added, but this just generates EN-US files, and doesn't do any actual localization yet.

repo: microsoft/undocked


text:
[grpc] build failure

Host Environment

OS: Windows
Compiler: VS2017 Community

To Reproduce
Steps to reproduce the behavior:
./vcpkg install grpc --debug
Failure logs
Computing installation plan...
[DEBUG] Found path: C:\cygwin64\bin\cmake.exe
[DEBUG] CreateProcessW("C:\cygwin64\bin\cmake.exe" --version)
[DEBUG] cmd_execute_and_stream_data() returned 0 after    41119 us
[DEBUG] CreateProcessW("C:\cygwin64\bin\cmake.exe"  -P "C:/Users/jgoya/Desktop/vcpkg/buildtrees/0.vcpkg_dep_info.cmake")
[DEBUG] cmd_execute_and_stream_data() returned 0 after    65784 us
[DEBUG] CreateProcessW("C:\cygwin64\bin\cmake.exe"  -P "C:/Users/jgoya/Desktop/vcpkg/buildtrees/0.vcpkg_tags.cmake")
[DEBUG] cmd_execute_and_stream_data() returned 0 after    85427 us
The following packages will be built and installed:

abseil[core]:x86-windows
c-ares[core]:x86-windows
grpc[core]:x86-windows
openssl[core]:x86-windows
openssl-windows[core]:x86-windows
protobuf[core]:x86-windows
upb[core]:x86-windows
zlib[core]:x86-windows
Additional packages (*) will be modified to complete this operation.
[DEBUG]
[DEBUG] fix-lnk2019-error.patch|42eb408cad0cc0619d24dd2de181451279776e49
[DEBUG] portfile.cmake|4a5213f61e2260999f4efc79cc17c6eb045b1f7f
[DEBUG] CONTROL|88cc1cf81a8cf5305c4ead744739219b51ab5a5c
[DEBUG] fix-uwp-build.patch|ce4f60a5ae8c7d469b09f334577759ae14c31c92
[DEBUG] fix-MSVCbuildfail.patch|ed0f6f269f98e3188ba15932dc30a06a2a75dc6d
[DEBUG] cmake|3.14.5
[DEBUG] powershell|ab1effc926b000a6adc12198a1886514ec203621a53b0cd7ec1cd9a8225dccda7e857feaabcfba4004bea73129b986abaad777c4573f44e0af70411226ce08b0
[DEBUG] vcpkg_fixup_cmake_targets|dac334f3bf50b8262be92623168023aa565aa729
[DEBUG] post_build_checks|2
[DEBUG] triplet|e8dc96fd479b53bb0e6748625827c8268017e35a
[DEBUG] features|core
[DEBUG]
[DEBUG]
[DEBUG] CONTROL|91d56ab30c4009204b0303828af8992a28909bc6
[DEBUG] portfile.cmake|9e2ac613e020d8918eeedfdbb4d9d32cdcf2d9f9
[DEBUG] cmake|3.14.5
[DEBUG] powershell|ab1effc926b000a6adc12198a1886514ec203621a53b0cd7ec1cd9a8225dccda7e857feaabcfba4004bea73129b986abaad777c4573f44e0af70411226ce08b0
[DEBUG] vcpkg_fixup_cmake_targets|dac334f3bf50b8262be92623168023aa565aa729
[DEBUG] post_build_checks|2
[DEBUG] triplet|e8dc96fd479b53bb0e6748625827c8268017e35a
[DEBUG] features|core
[DEBUG]
[DEBUG]
[DEBUG] EmbedSymbolsInStaticLibsZ7.patch|2428eddfb693a540a333bddfb6d319bcdb21dd25
[DEBUG] EnableWinARM64.patch|27a461a0eb4fb49cf47c8cbf466a050b99a435cf
[DEBUG] portfile.cmake|7cb86791470389f6e4b8f099b540f17330b10f93
[DEBUG] STRINGIFYPatch.patch|9231d10d38d9ddbe9d18b1923d373ee6ca18fcaf
[DEBUG] ConfigureIncludeQuotesFix.patch|96c7f8950288e78699f6b8fd6ca3cb25f879de62
[DEBUG] CONTROL|9c4d84c3da9fcd80c834afff806ec5fb8359b305
[DEBUG] EnableWinARM32.patch|ce954f1ae04412820b786c3de05ee69447ababfc
[DEBUG] usage|e84689f3fed71c903aaffed65f621b3eee496037
[DEBUG] cmake|3.14.5
[DEBUG] powershell|ab1effc926b000a6adc12198a1886514ec203621a53b0cd7ec1cd9a8225dccda7e857feaabcfba4004bea73129b986abaad777c4573f44e0af70411226ce08b0
[DEBUG] vcpkg_fixup_cmake_targets|dac334f3bf50b8262be92623168023aa565aa729
[DEBUG] post_build_checks|2
[DEBUG] triplet|e8dc96fd479b53bb0e6748625827c8268017e35a
[DEBUG] features|core
[DEBUG]
[DEBUG]
[DEBUG] openssl-windows|981b0046e073f655907283ff4620f690cda9ee05
[DEBUG] CONTROL|1aff4989d36904c26f2c15d566a4076ebfb0b71b
[DEBUG] portfile.cmake|dfcde9a792c20ca586d055247a0613c324dad868
[DEBUG] usage|e84689f3fed71c903aaffed65f621b3eee496037
[DEBUG] cmake|3.14.5
[DEBUG] powershell|ab1effc926b000a6adc12198a1886514ec203621a53b0cd7ec1cd9a8225dccda7e857feaabcfba4004bea73129b986abaad777c4573f44e0af70411226ce08b0
[DEBUG] vcpkg_fixup_cmake_targets|dac334f3bf50b8262be92623168023aa565aa729
[DEBUG] post_build_checks|2
[DEBUG] triplet|e8dc96fd479b53bb0e6748625827c8268017e35a
[DEBUG] features|core
[DEBUG]
[DEBUG]
[DEBUG] CONTROL|9432fa5dc1b439c85a859f8af8f37549fcb76e29
[DEBUG] portfile.cmake|b3c98927285573b3b5b966d8b2bc227fa9297930
[DEBUG] fix-uwp.patch|f0664089570a4c0638dc7a3081208291fec8bfec
[DEBUG] cmake|3.14.5
[DEBUG] powershell|ab1effc926b000a6adc12198a1886514ec203621a53b0cd7ec1cd9a8225dccda7e857feaabcfba4004bea73129b986abaad777c4573f44e0af70411226ce08b0
[DEBUG] vcpkg_fixup_cmake_targets|dac334f3bf50b8262be92623168023aa565aa729
[DEBUG] post_build_checks|2
[DEBUG] triplet|e8dc96fd479b53bb0e6748625827c8268017e35a
[DEBUG] features|core
[DEBUG]
[DEBUG]
[DEBUG] fix-uwp.patch|52576531157869004d6a4d9c166225ad48e85713
[DEBUG] add-cmake-install.patch|95aa37a3df591b7a0bf04fc54bc866d8da7dfa58
[DEBUG] CONTROL|e0158b0d2ff0de2208eb60b4c3f763ff7d8c4e9a
[DEBUG] portfile.cmake|feca576bb208e43eea9f3972a95aeb34631ea608
[DEBUG] cmake|3.14.5
[DEBUG] powershell|ab1effc926b000a6adc12198a1886514ec203621a53b0cd7ec1cd9a8225dccda7e857feaabcfba4004bea73129b986abaad777c4573f44e0af70411226ce08b0
[DEBUG] vcpkg_fixup_cmake_targets|dac334f3bf50b8262be92623168023aa565aa729
[DEBUG] post_build_checks|2
[DEBUG] triplet|e8dc96fd479b53bb0e6748625827c8268017e35a
[DEBUG] features|core
[DEBUG]
[DEBUG]
[DEBUG] portfile.cmake|3480e8cb8c1df66c455820588cf637841a2004a2
[DEBUG] cmake_dont_build_more_than_needed.patch|380b131349bf645f05637612e4a9a04ed8ba6349
[DEBUG] CONTROL|5a745a5fdf7009f92bfadac3b5cfe9685c7e11f7
[DEBUG] usage|b446f7466dead962527355c13bbb617213098938
[DEBUG] LICENSE|e23c6e5f40647ee2f817439d3858531fb0753c9d
[DEBUG] cmake|3.14.5
[DEBUG] powershell|ab1effc926b000a6adc12198a1886514ec203621a53b0cd7ec1cd9a8225dccda7e857feaabcfba4004bea73129b986abaad777c4573f44e0af70411226ce08b0
[DEBUG] vcpkg_fixup_cmake_targets|dac334f3bf50b8262be92623168023aa565aa729
[DEBUG] post_build_checks|2
[DEBUG] triplet|e8dc96fd479b53bb0e6748625827c8268017e35a
[DEBUG] features|core
[DEBUG]
[DEBUG]
[DEBUG] abseil|8cd4445a9fc9ea24dc0d1e11c9f39652a276c3b3
[DEBUG] c-ares|b03d9d9f43651745fcb8e7f4685d9e781d8ec202
[DEBUG] openssl|74b81e263bcd2f49e34b59df81314f05a1456de2
[DEBUG] protobuf|b8282a60103383f01cdfca79279598d8e8774203
[DEBUG] upb|b5e1b2f6c67119d57c6ac5d5c8a036a36dd39a14
[DEBUG] zlib|e5f15da66172f6d7aded00fcf0d80d0028e96ee4
[DEBUG] 00002-static-linking-in-linux.patch|1246adcdd9380fd363c0481afe23c461ae85f75a
[DEBUG] portfile.cmake|1e3e6fe1d37d2bc6ffe2c4d97e336a83c470426b
[DEBUG] CONTROL|625bfe8c1dee92b617e79365d04bd9ec3b50620f
[DEBUG] snprintf.patch|6359f7cdef1e8cc7747793bcece6f12422475682
[DEBUG] 00003-undef-base64-macro.patch|895d8931c76f541a4869a0297f835d5cf7e993af
[DEBUG] 00009-use-system-upb.patch|aaaaddc888d31c1d1d9ead5a449030d6f24b8540
[DEBUG] 00001-fix-uwp.patch|e194048d544691c5560d32b3af9ccce5928be764
[DEBUG] 00005-fix-uwp-error.patch|e6b549a64ae6efa6e970070b5cae3590becd1a64
[DEBUG] 00004-link-gdi32-on-windows.patch|e9e094eeb289eee8f8f9d21c5d16b75c173141e4
[DEBUG] cmake|3.14.5
[DEBUG] powershell|ab1effc926b000a6adc12198a1886514ec203621a53b0cd7ec1cd9a8225dccda7e857feaabcfba4004bea73129b986abaad777c4573f44e0af70411226ce08b0
[DEBUG] vcpkg_fixup_cmake_targets|dac334f3bf50b8262be92623168023aa565aa729
[DEBUG] post_build_checks|2
[DEBUG] triplet|e8dc96fd479b53bb0e6748625827c8268017e35a
[DEBUG] features|core
[DEBUG]
Starting package 1/8: abseil:x86-windows
Building package abseil[core]:x86-windows...
[DEBUG] CreateProcessW("C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" -all -prerelease -legacy -products * -format xml)
[DEBUG] cmd_execute_and_stream_data() returned 0 after    33170 us
[DEBUG] Found path: C:\Program Files\Git\cmd\git.exe
[DEBUG] CreateProcessW("C:\Users\jgoya\Desktop\vcpkg\downloads\tools\git-2.26.2-1-windows\mingw32\bin\git.exe" --version)
[DEBUG] cmd_execute_and_stream_data() returned 0 after    21308 us
[DEBUG] CreateProcessW(cmd /c ""C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\Build\vcvarsall.bat" -vcvars_ver=14.1 amd64_x86   2>&1 <NUL" & echo cdARN4xjKueKScMy9C6H& set)
[DEBUG] cmd_execute_and_stream_data() returned 0 after  2279580 us
[DEBUG] CreateProcessW("C:\cygwin64\bin\cmake.exe" "-DCMD=BUILD" "-DPORT=abseil" "-DCURRENT_PORT_DIR=C:/Users/jgoya/Desktop/vcpkg/ports/abseil" "-DVCPKG_ROOT_PATH=C:/Users/jgoya/Desktop/vcpkg" "-DTARGET_TRIPLET=x86-windows" "-DTARGET_TRIPLET_FILE=C:\Users\jgoya\Desktop\vcpkg\triplets\x86-windows.cmake" "-DVCPKG_PLATFORM_TOOLSET=v141" "-DVCPKG_USE_HEAD_VERSION=0" "-DDOWNLOADS=C:/Users/jgoya/Desktop/vcpkg/downloads" "-D_VCPKG_NO_DOWNLOADS=0" "-D_VCPKG_DOWNLOAD_TOOL=BUILT_IN" "-DFEATURES=core" "-DALL_FEATURES=cxx17;" "-DVCPKG_CONCURRENCY=5" "-DGIT=C:/Users/jgoya/Desktop/vcpkg/downloads/tools/git-2.26.2-1-windows/mingw32/bin/git.exe" -P "C:/Users/jgoya/Desktop/vcpkg/scripts/ports.cmake")
-- Note: abseil only supports static library linkage. Building static library.
CMake Error at C:/Users/jgoya/Desktop/vcpkg/scripts/cmake/vcpkg_download_distfile.cmake:82 (file):
file must be called with at least two arguments.
Call Stack (most recent call first):
C:/Users/jgoya/Desktop/vcpkg/scripts/cmake/vcpkg_from_github.cmake:132 (vcpkg_download_distfile)
C:/Users/jgoya/Desktop/vcpkg/ports/abseil/portfile.cmake:3 (vcpkg_from_github)
C:/Users/jgoya/Desktop/vcpkg/scripts/ports.cmake:90 (include)

[DEBUG] cmd_execute_and_stream_data() returned 1 after   151714 us
Could not copy into file: C:\Users\jgoya\Desktop\vcpkg\packages\abseil_x86-windows\share\abseil\vcpkg_abi_info.txt
[DEBUG] c:\users\jgoya\desktop\vcpkg\toolsrc\src\vcpkg\build.cpp(894)
[DEBUG] Exiting after 2819715 us (2813796 us)
Additional context
vcpkg_abi_info.txt
fix-lnk2019-error.patch 42eb408cad0cc0619d24dd2de181451279776e49
portfile.cmake 4a5213f61e2260999f4efc79cc17c6eb045b1f7f
CONTROL 88cc1cf81a8cf5305c4ead744739219b51ab5a5c
fix-uwp-build.patch ce4f60a5ae8c7d469b09f334577759ae14c31c92
fix-MSVCbuildfail.patch ed0f6f269f98e3188ba15932dc30a06a2a75dc6d
cmake 3.14.5
powershell ab1effc926b000a6adc12198a1886514ec203621a53b0cd7ec1cd9a8225dccda7e857feaabcfba4004bea73129b986abaad777c4573f44e0af70411226ce08b0
vcpkg_fixup_cmake_targets dac334f3bf50b8262be92623168023aa565aa729
post_build_checks 2
triplet e8dc96fd479b53bb0e6748625827c8268017e35a
features core

Solved: Conflict between CMake installed on windows and Cygwin64 CMake. Changed the order of the environment variable to prioritize Windows CMake.

repo: microsoft/vcpkg


text:
[opencv3] Build error

Host Environment

OS: Windows
Compiler: revision
vcpkg-tool version: 2022-10-17-3247920fbdd47d08f36cbd480addd9890d3c2435
vcpkg-scripts version: 7d9775a3c 2022-11-17 (11 hours ago)

To Reproduce
Steps to reproduce the behavior:
./vcpkg.exe install opencv3[tbb] --triplet=x64-windows --recurse
Failure logs
PS D:\wkspaces\vcpkg> ./vcpkg.exe install opencv3[tbb] --triplet=x64-windows --recurse
Computing installation plan...
The following packages will be built and installed:
    opencv3[core,default-features,dnn,flann,jpeg,png,quirc,tbb,tiff,webp]:x64-windows -> 3.4.18#3
Detecting compiler hash for triplet x64-windows...
Restored 0 package(s) from C:\Users\mcmor\AppData\Local\vcpkg\archives in 201.4 us. Use --debug to see more details.
Installing 1/1 opencv3:x64-windows...
Building opencv3[core,default-features,dnn,flann,jpeg,png,quirc,tbb,tiff,webp]:x64-windows...
-- Using cached opencv-opencv-3.4.18.tar.gz.
-- Cleaning sources at D:/wkspaces/vcpkg/buildtrees/opencv3/src/3.4.18-3eaff92c01.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source D:/wkspaces/vcpkg/downloads/opencv-opencv-3.4.18.tar.gz
-- Applying patch 0001-disable-downloading.patch
-- Applying patch 0002-install-options.patch
-- Applying patch 0003-force-package-requirements.patch
-- Applying patch 0004-fix-eigen.patch
-- Applying patch 0005-fix-vtk9.patch
-- Applying patch 0006-fix-uwp.patch
-- Applying patch 0008-devendor-quirc.patch
-- Applying patch 0009-fix-protobuf.patch
-- Applying patch 0010-fix-uwp-tiff-imgcodecs.patch
-- Applying patch 0011-remove-python2.patch
-- Applying patch 0012-fix-zlib.patch
-- Using source at D:/wkspaces/vcpkg/buildtrees/opencv3/src/3.4.18-3eaff92c01.clean
-- Using cached opencv-cache/tiny_dnn/adb1c512e09ca2c7a6faef36f9c53e59-v1.0.0a3.tar.gz.
-- Found external ninja('1.10.2').
-- Configuring x64-windows
-- Building x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:131 (message):
    Command failed: D:/wkspaces/vcpkg/downloads/tools/cmake-3.24.0-windows/cmake-3.24.0-windows-i386/bin/cmake.exe --build . --config Debug --target install -- -v -j13
    Working Directory: D:/wkspaces/vcpkg/buildtrees/opencv3/x64-windows-dbg
    See logs for more information:
      D:\wkspaces\vcpkg\buildtrees\opencv3\install-x64-windows-dbg-out.log

Call Stack (most recent call first):
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_build.cmake:74 (vcpkg_execute_build_process)
  installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_install.cmake:16 (vcpkg_cmake_build)
  ports/opencv3/portfile.cmake:402 (vcpkg_cmake_install)
  scripts/ports.cmake:147 (include)

error: building opencv3:x64-windows failed with: BUILD_FAILED
error: Please ensure you're using the latest port files with `git pull` and `vcpkg update`.
Then check for known issues at:
    https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+opencv3
You can submit a new issue at:
    https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[opencv3]+Build+error
Include '[opencv3] Build error' in your bug report title, the following version information in your bug description, and attach any relevant failure logs from above.
    vcpkg-tool version: 2022-10-17-3247920fbdd47d08f36cbd480addd9890d3c2435
    vcpkg-scripts version: 7d9775a3c 2022-11-17 (11 hours ago)

config-x64-windows-CMakeCache.txt.log
Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.
I did git pull and vcpkg update as suggested. It didn't solve it

See logs for more information:

  D:\wkspaces\vcpkg\buildtrees\opencv3\install-x64-windows-dbg-out.log

Please provide this file

See logs for more information:
D:\wkspaces\vcpkg\buildtrees\opencv3\install-x64-windows-dbg-out.log

Please provide this file

Apologies. I must have dragged the wrong one.
Here is the correct one:
install-x64-windows-dbg-out.log

Comfirmed. I reproduced this bug locally.

Hi, do you have any eta for looking into it?

@mcmorry, please try to test my pr, if it can solve your error.

@JonLiu1993 thank you. It works fine now

authors: JonLiu1993 autoantwort mcmorry


text:
CMake integration stop working when "CMAKE_TOOLCHAIN_FILE" is replaced with "toolchainFile" (as recommended for presets version 3 or above)

Describe the bug
In VSCODE I get the following message when using "CMAKE_TOOLCHAIN_FILE" in a preset file:
Use "toolchainFile" property instead when using presets version 3 or higher. Tne CMake documentation also states about this option for such presets versions.

However, when I do this, the linkage does not work anymore and it's just like passing an empty string.
Environment

OS: Windows 11
Compiler: MSVC vc143

To Reproduce
In a CMake preset file (version higher than 3) replace:
{
    "version": 6,
    "configurePresets": [
        {
            "name": "x64-release",
            "cacheVariables": {
                "CMAKE_TOOLCHAIN_FILE": "<VCPKG_ROOT>/scripts/buildsystems/vcpkg.cmake",
                "CMAKE_BUILD_TYPE": "Release"
            }
        }
    ]
}

With:
{
    "version": 6,
    "toolchainFile": "<VCPKG_ROOT>/scripts/buildsystems/vcpkg.cmake",
    "configurePresets": [
        {
            "name": "x64-release",
            "cacheVariables": {
                "CMAKE_BUILD_TYPE": "Release"
            }
        }
    ]
}

Expected behavior
The same behavior of "CMAKE_TOOLCHAIN_FILE"'.
Failure logs
Even in debug mode, cmake Log does not show anything related to the tool chain file, but the issue is immediately noticeable from plenty of "not found" errors which does not happens when "CMAKE_TOOLCHAIN_FILE" is used.
Additional context
I'm just ignoring and continuing to use "CMAKE_TOOLCHAIN_FILE", but I wanted to report such issue because there must be a valid reason if they recommend to switch from "CMAKE_TOOLCHAIN_FILE" to "toolchainFile" property.

I think vcpkg is the wrong repository to report this VS Code (CMake plugin?) issue.

I was not sure on where to report this, but I decided here because even without Vs code and its CMake plugin, the issue persists. May be vcpkg has not the required implementation to handle a "toolchainFile" property?

vcpkg itself "handles" none of it. AFAICS it is CMake, and the documentation you linked indicates that toolchainFile is a json property which belongs  to the configurePresets array.
So your example should be (untested):
{
    "version": 6,
    "configurePresets": [
        {
            "name": "x64-release",
            "toolchainFile": "<VCPKG_ROOT>/scripts/buildsystems/vcpkg.cmake",
            "cacheVariables": {
                "CMAKE_BUILD_TYPE": "Release"
            }
        }
    ]
}


text:
[New Port Request] virtualgl

Library name
virtualgl
Library description
VirtualGL is a toolkit that allows most Linux/Unix OpenGL applications to be remotely displayed with 3D hardware acceleration to thin clients, regardless of whether the clients have 3D rendering capabilities, and regardless of the size of the 3D data being rendered or the speed of the network.
Source repository URL
https://github.com/VirtualGL/virtualgl
Project homepage (if different from the source repository)
https://virtualgl.org/
Anything else that is useful to know when adding (such as optional features the library may have that should be included)
I'd like to ask for an option to have VirtualGL as vcpkg port. I have created it as port overlay locally already, so creating this issue to ask for feedback if this is OK. VirtualGL will be mostly a runtime dependency, not a build-time dependency, so in a build system such as CMake there will not be linking of libraries but just copying of executables (such as vglrun) and libraries (such as libvglfaker.so) to the output directory bin and lib folder.

Closing this issue as per the response on https://github.com/microsoft/vcpkg/pull/40023


text:
fail to upgrade after getting the latest version

Describe the bug
After fetching the latest version (5c5c9ea) I run
vcpkg.exe update
and then
vcpkg.exe upgrade
and I got the following error message:
Failed at [f:\ucdavis\vcpkg\toolsrc\src\vcpkg\packagespec.cpp(44)] with message:
Contains invalid characters. Only alphanumeric lowercase ASCII characters and dashes are allowed
Environment

OS: Windows

Please run bootstrap-vcpkg.bat and try again.

This seem to work, however the upgrade seem to have screwed up something so that after vcpkg integrate install VS2017 does not find any include file

It is possible that the upgrade failed after purging old files. In that case, you don’t have anymore the old libraries installed and you have to reinstall them

I suspect you are right but I cannot confirm as I decided to delete and start with a fresh clone of vcpkg. Yet I was getting the same issue. The reason is that the vcpkg install boost for example was installing the x86 and my codes  were looking for the x64 include files.
Just for completeness I had to go to Properties->VC++Directories and examine the include directories.

authors: cenit giorgk myd7349


text:
[freetype] Update to 2.10.4

Describe the pull request

What does your PR fix?

Regular port update https://sourceforge.net/projects/freetype/files/freetype2/2.10.4/ with major security vulnerability fix, plus the upstream vtk patch for compatibility with this revision from https://discourse.vtk.org/t/building-opencascade-7-5-0-with-vtk-9-0-1
Closes #14008. I made a new PR due to the changes on master and branched off the last commit that affected freetype and vtk since I could not build anything on HEAD #15332 but I could on 191e01f

Which triplets are supported/not supported? Have you updated the CI baseline?
It should work everywhere but since vtk takes really long to build, I've only tested against x86-windows.

Does your PR follow the maintainer guide? Yes

Behaviour of freetype is fine for me since that was working in the old PR but I cannot really say anything meaningful about vtk since I didn't expect this problem with a seemingly unrelated port.

Thanks for the PR!

authors: kevinlul vicroms


text:
[opencv3] no absolute paths

For https://github.com/microsoft/vcpkg/issues/20469

Thanks for your PR. Could you please also apply these changes for opencv2 and opencv4?

@LilyWangLL See https://github.com/microsoft/vcpkg/pull/28180 and I will create a PR for opencv4

authors: LilyWangLL autoantwort


text:
[vcpkg] Fix VS can still be IntelliSense after disabling vcpkg

Describe the pull request

What does your PR fix?
Fixes https://github.com/microsoft/vcpkg/issues/28200
Note:
After setting Use Vcpkg  to No, the header path of vcpkg installed ports will not be deleted in the External Include Directories.
This is due to the regression triggered by the PR https://github.com/microsoft/vcpkg/pull/21544 without setting conditions.
Problems caused:
The IntelliSense in the VS can still sense the library provided by the currently integrated vcpkg.

/azp run


text:
add port: spatial-hash

[x] Changes comply with the maintainer guide.

[x] The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.

[x] Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx.

[x] The versioning scheme in vcpkg.json matches what upstream says.

[x] The license declaration in vcpkg.json matches what upstream says.

[x] The installed as the "copyright" file matches what upstream says.

[x] The source code of the component installed comes from an authoritative source.

[x] The generated "usage text" is accurate. See adding-usage for context.

[x] Only one version is in the new port's versions file.

[x] Only one version is added to each modified port's versions file.

[ ] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.

I'm not sure I understand this question. So I don't know what the answer should be.

@microsoft-github-policy-service agree

Note: I will be converting your PR to draft status. When you respond, please revert to "ready for review".
That way, I can be aware that you've responded since you can't modify the tags.

The usage has been tested successfully on x64-windows.

/azp run

/azp run

/azp run

/azp run

/azp run

@FrankXie05 @BillyONeal
is there anything I should do? I think Azure's CI process is stuck in the queue.

/azp run

Sorry, been a hectic couple of days. Power has been out for me since Tuesday night

Sorry, been a hectic couple of days. Power has been out for me since Tuesday night

@BillyONeal
There is no problem, but there seems to be a problem with azure bot.

yuppi :) done :) .

@BillyONeal
Is there anything I should do?

Thanks for confirming that the DLL edge cases work out!

authors: BillyONeal FrankXie05 SeanTolstoyevski


text:
[sfml] Update SFML to 3.0.0

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[x] The "supports" clause reflects platforms that may be fixed by this new version.
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

This updates SFML to the recently released 3.0.0 version.
Uncommented the baseline CI ignores to see, if the new version have fixed those. See also #37174

Looks like we need to limit SFML usage to SFML 2.x, until the packages are updated.

SFGUI
Imgui-SFML
Thor

I tried to understand versioning, but don't fully understand it. Can someone give me a hint, how one would for example limit Thor to SFML 2.* (or even better SFML 2.5 and later SFML 2.* versions)?


text:
[Survery] User feedback

VSCode Version: 1.44.0,
Extension Version: 0.5.0,
OS: OSX
1. Overall, how would you rate your experience with the Stream Analytics Visual Studio Code Extension? Please rate us from 1 (poor) to 10 (excellent).
2. What do you like or dislike about the Stream Analytics Visual Studio Code Extension?
3. What improvements do you suggest for Stream Analytics Visual Studio Code Extension?

Hi hpayami,
Thanks for using Stream Analytics tools for VS Code. Do you have some feedback for the tools so that we can keep improving it?
Thanks,
Jie

authors: hpayami su-jie

repo: microsoft/vscode-asa


text:
Reduce number of ingress prompts during createContainerApp

We can probably default most of the ingress prompts and just ask for the target port to simplify the overall create experience.

The create experience now defaults to the quick start image, closing as no longer relevant.

repo: microsoft/vscode-azurecontainerapps


text:
There is no Container Apps option in the list after clicking "Report Issue"

OS: All
Build Version: 20220405.6
Regression: Not a regression
Repro Steps:

Ensure the Azure Container Apps extension is installed.
Navigate to Azure view -> Expand HELP AND FEEDBACK node -> Click "Report Issue".
Check whether there is the Container Apps option in the list.

Expect:
There is the Container Apps option in the list.
Actual:
There is no Container Apps option in the list.

More Info:
This issue also reproduces for "Review Issue".

This won't be fixed until we actually release Resource Groups.  I don't think that including Container Apps in the report issue list is worth a release though.

authors: nturinski v-xinda


text:
Add command updateImage for updating a container image via revision draft

Part 2
Partially addresses #426
This is the new updateImage command implementation.  It can be executed on the ContainerAppItem level or on the RevisionItem level to update the container image.  Any changes will be made to the revision draft instead of automatically executing a deployment like before.
A few things to note:

I've also added a new thing where I append a short random hex value to the container name on draft update.  This is because if you are re-deploying using the exact same image values, the extension will have no easy way to detect that there are changes to deploy.  This was an easy way to fix that and get it to play nicely with our current setup.

One other noteworthy area is the new UpdateRegistryAndSecretsStep.  I've added some deep copy comparison logic to try and see if we can skip credential updates since updating the container app's secrets before deployment can trigger a bit of a wait which feels bad to always do unless we absolutely need it.

Todo:  In a follow-up PR I'm going to build out some sort of draft command information pop-up.  Right now updating the image does get a little lost because we don't yet have the containers section of the tree implemented.  Having a pop-up should help the results appear a bit more prominently and I think will be a nice addition.
Update: Here's the demo
This PR doesn't cover the pop-up part shown in the demo

Just approving ahead of time to not block you


text:
Find previously deployed to managed environment and recommend them

I toyed with the idea of using grouping instead of description. Not sure if we want to go that route though in case we started grouping things by resource group or something.
Also supressedPersistence because the (recently used) description looks kind of silly with recommended.

Also supressedPersistence because the (recently used) description looks kind of silly with recommended.
Lol that's funny I also added this same thing to my PR because it was bothering me too 😂