text:
copy/paste issue over SSH connection

Windows Terminal (Preview)
Version: 0.7.3451.0

I can copy/paste using ctrl-c & ctrl-v before i connect to SSH session.
My question here:
can i enable the same over ssh session ? or to copy on select via mouse ?
waiting for your feedback ASAP
Regards,

I am able to copy-paste over an SSH connection using WT and use mouse selection. Are you asking whether or not this is possible or are you unable to perform this yourself?

@mkitzan thanks for your response. here on my end, I can only copy/paste using right click.
How can i enable Mouse selection ? and what do you mean by WT.

Take a look at my comment here about enabling Ctrl+C and Ctrl+V copy-paste.
Mouse selection should be there by default by performing the steps listed. If those don't work, let me know what happens when you perform those steps.

left click at the point you want to start selecting text
then drag the mouse over the text you want to select

Also, WT just stands for Windows Terminal.

@mkitzan now it's works via Ctrl+C Ctrl+V. how about if i want to use mouse copy on selection ?

From SettingsSchema.md

Globals
Properties listed below affect the entire window, regardless of the profile settings.

Property
Necessity
Type
Default
Description

copyOnSelect
Optional
Boolean
false
When set to true, a selection is immediately copied to your clipboard upon creation. When set to false, the selection persists and awaits further action.

@zadjii-msft  thanks for your response. could you please advise me where i should put this ?
I'm now inside profiles.json, i try to insert "copyOnSelect": true under keybindings but VScode telling me it's incorrect Property copyOnSelect is not allowed.

You can put it right in the root object of profiles.json:
{
    "$schema": "file:///c:/Users/migrie/dev/private/OpenConsole/doc/cascadia/profiles.schema.json",

    "alwaysShowTabs": false,
    "defaultProfile": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
    "copyOnSelect": true,
	...
}

@zadjii-msft thank you very very much. it's works!

source: gharchive/issue

authors: AmericanY mkitzan zadjii-msft

repo: microsoft/terminal

license: MIT

license_type: permissive

license_source: github-api


text:
Open a new Terminal tab from command line (instead of a new console window)

The Windows Terminal now has brilliant support for command line arguments like:

wt.exe -d . Open a new wt instance in the current working directory
wt.exe -p <profile name> Create a wt instance running the given profile, to unblock
wt.exe ; new-tab ; split-pane -V Launch the terminal with multiple tabs, splits, to unblock

What's missing for me is, that every time I run wt.exe with arguments, a new console window appears which - of course - only hosts one single tab. I use tabs to manage multiple sessions in one single console window, so it would be huge, if wt.exe command lines could be written to reuse existing windows by "just" adding (and focusing) a new tab.
To avoid misunderstandings: There's an argument new-tab but as far as I know, this can be used to force a new console window to open one or more further new tab(s). This is not what I want: I meant to reuse an existing console window (if available) and open a new tab in there.
I posted this idea on Twitter here. Please read the thread for more information.
In gif below, I use a tool git tool called RepoZ to jump to the directory of a chosen git repository.

However, for each "Open In Windows Terminall", a new window is opened where a tab would have been more convenient.

Proposed technical implementation details
I have no implementation idea how this works in the Windows Terminal process itself.
However, on the command line side, this could be the new default behavior for wt.exe-commands in my opinion. To keep things downwards compatible, we could add a new argument option like wt.exe -d . reuse-window to make sure that Windows Terminal should try to use an existing process if available. If not, I'd suggest that a new Window appears which can be used by subsequent calls with the optiom reuse-window.

Thanks for the request! This is actually captured in /dup #4472.

authors: DHowett-MSFT awaescher


text:
Default input method is ALWAYS Chinese IME

Environment
Windows build number: [Environment]::OSVersion
Windows Terminal version (if applicable): 1.4.3243.0

Any other software?
* Windows 10 Simpified Chinese version
* Default IME is "Simpified Chinese (US Keyboard)", with "using language bar" on and "different programs using different IME" on. (Shown in figure 1)

Figure 1,  Language bar (with Simpified Chinese (US Keyboard) selected)
Steps to reproduce

Open the windows terminal in enviroment discribed above.
Input from keyboard.

Expected behavior
Input and echo characters directly if current input method is "Chinese (US Keyboard)" instead of using any Chinese IME, just like any other programs (i.e.  cmd.exe, PowerShell),

Figure 2. The way it expected to be
Actual behavior
When pressing keyboard, the character is under an IME (Probably "Microsoft Pinying IME", shown in figure 3), and after pressing space on keyboard, the input string become Chinese characters (shown in figure 4), although current input method is "US Keyboard".

Figure 3 When input from keyboard without manually pressing SHIFT key

Figure 4 Then pressing SPACE

I think it's cause by "搜狗输入法(Sogou IME)". See https://github.com/microsoft/terminal/issues/1304#issuecomment-705682131

Okay yea, this sounds a lot like what's going on in that thread. I'm not gonna close it as a duplicate - it seems like that thread is mainly about another issue. But I am going to close this issue as answered. Thanks @skyline75489!

I think it's cause by "搜狗输入法(Sogou IME)". See #1304 (comment)

It may not caused by  Sougou IME, I have tested in another enviroment without Sougou IME installed, but the problem is still. (Shown  in figure 1)

Figure 1.
And I replace the Simpifed Chinese (US Keyboard) to English (US Keyboard), it works (but also need to switch between languages instead of just between IMEs). Maybe because Windows 10 does not natively add US Keyboard to Simpified Chinese  IME list  in Settings?

@ElizabethEmilia Check your system input language. You need to add EN/US input method keyboard

Exactly the same issue in my ARM-based Windows 11 24H2 running on Snapdragon(R) X Elite in year 2024.
OS: Windows 11 Home, 24H2, 26100.1457
IME: Microsoft Traditional Chinese IME,
Windows Terminal: 1.20.11781.0
No matter what kind of settings, it always automatically changes to Chinese input mode instead of "Chinese(English Keyboard) mode" when I switch from other Apps back to Windows terminal.

@robeyang Please try Windows Terminal Preview (v1.21) as it has a new IME implementation. If the problem still occurs then, please open a new issue where we can discuss this.
v1.21 will be the new stable Windows Terminal version later this week.

authors: ElizabethEmilia JryChn acane77 lhecker robeyang skyline75489 zadjii-msft


text:
atlas: only enable continuous redraw if the shader needs it

We do this by detecting whether the shader is using variable 0 in
constant buffer 0 (typically "time", but it can go by many names.)
Closes #13901

I've tested this with the Animate shaders; GPU usage jumps up to 40% for me when continuous redraw is enabled.

@msftbot merge this in 2 minutes

source: gharchive/pull-request


text:
doc: Add logos to README

Summary of the Pull Request
Let's add our logos to our README to spice it up.

I rather agree! I'd love to have a Windows Terminal banner :smile:

I honestly like this version already and we can always improve on it later on.
But I'm also quite intrigued now in how a LOGO "Windows Terminal" version would look like as a comparison.
Either way: Nice!

authors: DHowett cinnamon-msft lhecker


text:
Remove pinned version of typedoc 0.25.2 - Regression in 0.25.3

Filled issue here https://github.com/TypeStrong/typedoc/issues/2437
We should remove the pinned version when the bug is fixed.

This has been updated

repo: microsoft/typespec


text:
VLMO training speed

Describe
Model I am using (UniLM, MiniLM, LayoutLM ...): VLMO
I am training VLMO in 8 V100 32GB GPU, and I find out the speed is extremely slow compared to the paper, could you offer some help about the potential problems?
(1% of epoch 0 after 5 hours🙃)

Could you provide your training command?

I have already tried profiling, strangely the bottleneck seems to be the ConcatDataset(). When I train single COCO dataset the speed seems normal. Could you provide some train logs for me to check out some settings(like how many steps per batch, how long for a single step)? Thx~

The bottleneck seems to be disk IO instead of the training code.

Confused. I followed the instructions to process four pre-training datasets. But I found out every training epoch needs 166k steps (8 gpus, per batch size is 16), seems like the total training data is 166k x 8 x 16, which is obviously false. Could you provide some training logs for me?

Hi @det-tu, the total training data of four datasets is about 10M. If the total batch size is 16*8=128, I think the training steps of a epoch is 78k.

authors: det-tu donglixp wenhui0924

repo: microsoft/unilm


text:
bazel build system

Is Bazel supported by vcpkg ports?

If I recall correctly the tensorflow-cc port uses Bazel.

It used as a program see https://github.com/microsoft/vcpkg/blob/5deea3b975fe62990973d73a102de818d83ba20c/scripts/cmake/vcpkg_find_acquire_program.cmake#L272
and https://github.com/microsoft/vcpkg/blob/73e55002f1e3e8093431bc1b506d907396bfbf2f/ports/tensorflow-cc/portfile.cmake#L21

@kreuzerkrieg, does this still be a problem for you?

Nope. I think I can handle it. Thanks for the assistance

authors: PhoebeHui kreuzerkrieg vicroms

repo: microsoft/vcpkg


text:
[podofo] Fails to protect PDF file

Describe the bug
PoDoFo up to now was capable (for several months) of protecting/encrypting PDF files programmatically. Today I performed vcpkg update and received various updates for podofo dependencies and my application now crashes while protecting the pdf with podofo. As the problem is related to crypto I think that the latest openssl updates may be causing the problem with podofo.
The relevant podofo code that triggers the issue is:
doc.SetEncrypted("",
                             "passwordstring",
                             PoDoFo::PdfEncrypt::ePdfPermissions_Print |
                             PoDoFo::PdfEncrypt::ePdfPermissions_Accessible |
                             PoDoFo::PdfEncrypt::ePdfPermissions_HighPrint,
                             PoDoFo::PdfEncrypt::ePdfEncryptAlgorithm_AESV2,
                             PoDoFo::PdfEncrypt::ePdfKeyLength_128);

Disabling this instruction disables pdf protection and podofo successfully creates a pdf again.
The bug occurs both on windows and macOS.
EDIT: Updated the PoC and the resulting error message.
Environment

OS: Windows 10 21H2 and macOS 12.3.1 Apple Silicon
Compiler: Apple Xcode 13.3.1 clang; Visual Studio 2019 latest update

To Reproduce
Steps to reproduce the behavior:

./vcpkg install podofo[fontconfig]

Run test code:
#include <iostream>
#include <podofo/podofo.h>

int main() {
    try {
        PoDoFo::PdfMemDocument doc;
        // you must provide orig.pdf
        doc.Load("orig.pdf");
        // enabling .SetEncrypted will cause the exception
        doc.SetEncrypted("",
                         "ownerPassword",
                         PoDoFo::PdfEncrypt::ePdfPermissions_Print |
                         PoDoFo::PdfEncrypt::ePdfPermissions_Accessible |
                         PoDoFo::PdfEncrypt::ePdfPermissions_HighPrint,
                         PoDoFo::PdfEncrypt::ePdfEncryptAlgorithm_AESV2,
                         PoDoFo::PdfEncrypt::ePdfKeyLength_128);
        //will be created when no error
        doc.Write("protected.pdf");
    }
    catch (PoDoFo::PdfError &e) {
        e.PrintErrorMsg();
    }

    return 0;
}

No compilation errors.

Expected behavior
A protected PDF should be created.
Failure logs
PoDoFo encountered an error. Error: 8 ePdfError_InternalLogic 	Error Description: An internal error occurred. 	Callstack: 	#0 Error Source: /Users/xxx/vcpkg/buildtrees/podofo/src/0e699739c2-e7dcab1c3c.clean/src/podofo/base/PdfEncrypt.cpp:985 		Information: Error initializing RC4 encryption engine
Additional context
The problem occurs both on Windows and on macOS.

The error points towards openssl:
int status = EVP_EncryptInit_ex(rc4, EVP_rc4(), NULL, NULL, NULL);
    if(status != 1)
        PODOFO_RAISE_ERROR_INFO( ePdfError_InternalLogic, "Error initializing RC4 encryption engine" );

I couldn´t get it to work by modifying the CMakeLists.txt but instead modified portfile.cmake:
vcpkg_configure_cmake(
    SOURCE_PATH ${SOURCE_PATH}
    PREFER_NINJA
    OPTIONS
        -DPODOFO_BUILD_LIB_ONLY=1
        -DPODOFO_BUILD_SHARED=${PODOFO_BUILD_SHARED}
        -DPODOFO_BUILD_STATIC=${PODOFO_BUILD_STATIC}
        -DPODOFO_NO_FONTMANAGER=${PODOFO_NO_FONTMANAGER}
        -DCMAKE_DISABLE_FIND_PACKAGE_FONTCONFIG=${PODOFO_NO_FONTMANAGER}
        -DCMAKE_DISABLE_FIND_PACKAGE_LIBCRYPTO=${IS_WIN32}
        -DCMAKE_DISABLE_FIND_PACKAGE_LIBIDN=ON
        -DCMAKE_DISABLE_FIND_PACKAGE_CppUnit=ON
        -DCMAKE_DISABLE_FIND_PACKAGE_Boost=ON
        -DPODOFO_HAVE_OPENSSL_NO_RC4=ON
)

The PoC now does not throw an exception anymore BUT it does NOT work as expected. It is still broken. Generated PDFs opened with Acrobat Reader ask for a password which is always incorrect even if all password are specified as empty in the code. PoDoFo and/or the PDF spec need RC4 legacy to function properly.

@derreisende77   could you please provide your CMakeLists.txt in VS.

cmake_minimum_required(VERSION 3.21)
project(pdf_test)

find_package(Fontconfig REQUIRED)
find_package(Freetype REQUIRED)
find_package(OpenSSL REQUIRED)
find_package(JPEG REQUIRED)
find_package(expat CONFIG REQUIRED)

add_executable(pdf_test main.cpp)

target_link_libraries(pdf_test PRIVATE /Users/XXX/vcpkg/installed/arm64-osx/lib/libpodofo.a)
target_link_libraries(pdf_test PRIVATE OpenSSL::Crypto)
target_link_libraries(pdf_test PRIVATE ${FREETYPE_LIBRARIES})
target_link_libraries(pdf_test PRIVATE ${Fontconfig_LIBRARIES})
target_link_libraries(pdf_test PRIVATE ${JPEG_LIBRARIES})
target_link_libraries(pdf_test PRIVATE /Users/XXX/vcpkg/installed/arm64-osx/lib/libunistring.a)
target_link_libraries(pdf_test PRIVATE expat::expat)

I am using CLion both on windows and macOS and CMAKE_TOOLCHAIN_FILE is set in the project.

Unfortunately, I haven't been able to reproduce this problem. Has it been solved now？@derreisende77

No. I opened a ticket with the library creators. And I am going to open a ticket for weak cypher support option for openssl.

BTW they released version 0.9.8 of PoDoFo. Also now available on github as they are migrating to it.


text:
[openssl] Build error

Host Environment

OS: Windows wsl 1 ubuntu 20
Compiler: revision

To Reproduce
Steps to reproduce the behavior:
./vcpkg install xxxx
Failure logs
error: building openssl:x64-linux failed with: BUILD_FAILED
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+openssl
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[openssl]+Build+error
Include '[openssl] 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-06-17-9268e366206712e38102b28dbd1617697a99ff2e
vcpkg-scripts version: e6c8c2bc0 2022-07-07 (15 hours ago)
You can also use the prefilled template from /home/shortlegdog/Desktop/OpentelemetryTry/OpenCpp/tools/vcpkg/installed/vcpkg/issue_body.md.
Additional context
./vcpkg  install opentelemetry-cpp
sudo ./vcpkg  install opentelemetry-cpp

Can you please provide the failure logs which mentioned in the output first?
Thanks.

We don't have enough information to solve this issue, unfortunately; if you have any more information to help us solve this, please reopen!


text:
[minizip] unzGetCurrentFileInfo not working

Describe the bug
For some reason, unzGetCurrentFileInfo is not working when linking against vcpkg build of minizip.
The function returns that it was successful, however the info and filename params are not filled in.
Strangely, if using unzGetCurrentFileInfo64, then the filename param is filled in, but info struct still isn't.
The miniunz binary that gets built with vcpkg still works, this is because it does not query the info.uncompressed_size to get file size, instead it loops over unzReadCurrentFile until all data is read. Also, it uses the func64 functions, which is why the filename can still be read.
I have built the same minizip version from source and linked against it, and it works (same for older / later version).
Environment

OS: Linux (fedora)
Compiler: g++ (GCC) 12.1.1 20220507 (Red Hat 12.1.1-1)

To Reproduce
Steps to reproduce the behavior:
https://gist.github.com/ITotalJustice/906268cfa1980ec37722f6208824d9a0
Expected behavior
info.uncompressed_size and filename params should be filled.
Failure logs
-(please attached failure logs)
Additional context
I haven't tried on windows or mac

i have updated the gist to ensure that the src build of minizip is the exact same version used in vcpkg.
i have also tried using src-minizip along with vcpkg-zlib, just to rule out zlib being the culprit, that isn't the case though.
only thing i havent tried is applying those patches https://github.com/microsoft/vcpkg/tree/master/ports/minizip but none of those seem to apply to the linux build anyway.

Update vcpkg to the latest version, use the test reproduction steps you provided to compile the code, and the compilation result is normal. Unable to reproduce this error.

@ITotalJustice did you resolve this? I'm seeing the same.
@jimwang118 The problem was a run-time issue, not a compile-time issue. After compiling it, you'll need to run the program and provide it a zip file to see the issue.

authors: ITotalJustice jeaye jimwang118


text:
[pkgconf] build failure

Host Environment

OS: Linux (Ubuntu 18.04.6)
Compiler: g++ (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0

To Reproduce
Steps to reproduce the behavior:
./vcpkg install pkgconf
Failure logs
ssoroosh@bionic:~/vcpkg$ ./vcpkg install pkgconf
Computing installation plan...
The following packages will be built and installed:
    pkgconf[core]:x64-linux -> 1.8.0#5
Detecting compiler hash for triplet x64-linux...
Restored 0 package(s) from /home/ssoroosh/.cache/vcpkg/archives in 3.7 us. Use --debug to see more details.
Installing 1/1 pkgconf:x64-linux...
Building pkgconf[core]:x64-linux...
-- Using cached pkgconf-pkgconf-cef30268e1a3f79efd607c26abcf556aa314c9c4.tar.gz.
-- Cleaning sources at /home/ssoroosh/vcpkg/buildtrees/pkgconf/src/6aa314c9c4-8bd74a463d.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /home/ssoroosh/vcpkg/downloads/pkgconf-pkgconf-cef30268e1a3f79efd607c26abcf556aa314c9c4.tar.gz
-- Using source at /home/ssoroosh/vcpkg/buildtrees/pkgconf/src/6aa314c9c4-8bd74a463d.clean
-- Getting CMake variables for x64-linux-dbg
-- Getting CMake variables for x64-linux-rel
-- Configuring x64-linux-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
    Command failed: /usr/bin/python3 /home/ssoroosh/vcpkg/installed/x64-linux/tools/meson/meson.py -Dtests=false --buildtype plain --backend ninja --wrap-mode nodownload --libdir lib --native /home/ssoroosh/vcpkg/buildtrees/pkgconf/meson-x64-linux-dbg.log -Ddebug=true --prefix /home/ssoroosh/vcpkg/packages/pkgconf_x64-linux/debug --includedir ../include -Dcmake_prefix_path=['/home/ssoroosh/vcpkg/installed/x64-linux/debug','/home/ssoroosh/vcpkg/installed/x64-linux'] /home/ssoroosh/vcpkg/buildtrees/pkgconf/src/6aa314c9c4-8bd74a463d.clean
    Working Directory: /home/ssoroosh/vcpkg/buildtrees/pkgconf/x64-linux-dbg
    Error code: 1
    See logs for more information:
      /home/ssoroosh/vcpkg/buildtrees/pkgconf/config-x64-linux-dbg-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_meson.cmake:433 (vcpkg_execute_required_process)
  ports/pkgconf/portfile.cmake:9 (vcpkg_configure_meson)
  scripts/ports.cmake:147 (include)

error: building pkgconf:x64-linux 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+pkgconf
You can submit a new issue at:
    https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[pkgconf]+Build+error
Include '[pkgconf] 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: 2023-01-24-8a88d63f241d391772fbde69af9cab96c3c64c75
    vcpkg-scripts version: 54cc53c43 2023-02-23 (8 hours ago)

/home/ssoroosh/vcpkg/buildtrees/pkgconf/config-x64-linux-dbg-err.log
Traceback (most recent call last):
  File "/home/ssoroosh/vcpkg/installed/x64-linux/tools/meson/meson.py", line 26, in <module>
    from mesonbuild import mesonmain
  File "/home/ssoroosh/vcpkg/installed/x64-linux/tools/meson/mesonbuild/mesonmain.py", line 28, in <module>
    from . import mesonlib
  File "/home/ssoroosh/vcpkg/installed/x64-linux/tools/meson/mesonbuild/mesonlib/__init__.py", line 21, in <module>
    from .universal import *
  File "/home/ssoroosh/vcpkg/installed/x64-linux/tools/meson/mesonbuild/mesonlib/universal.py", line 17
    from __future__ import annotations
    ^
SyntaxError: future feature annotations is not defined

Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.

related to https://github.com/tmakkonen/sipcmd/issues/83

You need a more recent python3 for any port which builds with meson.
The python3 from port python is good enough.

You need a more recent python3 for any port which builds with meson.

This should really be checked as part of the meson build scripts in vcpkg.

I have default bionic python, and I think vcpkg must be work with official live ubuntu LTS
ssoroosh@bionic:~/vcpkg$ python3 --version
Python 3.6.9

Ubuntu 18.04 is five years old, so there were at least two more recent LTS release.... (Written on an 18.04 installation.)

@dg0yt But it is still live and official supported.
https://endoflife.software/operating-systems/linux/ubuntu
https://ubuntu.com/about/release-cycle

i.e. Ubuntu gives certain promises. Obviously, these don't include offering new versions of python. Ubuntu 18.04 also lacks modern compilers.

@dg0yt Ok, I say vcpkg must use python version that support on bionic. (or download itself like cmake)

@Cheney-W Why add question tag? I think it is bug


text:
Unable to install openblas with vcpkg

Describe the bug
I am using vcpkg in manifest mode to install mlpack. Below is the log:
C:\Users\user\source\repos\ml-trails>vcpkg install
Fetching registry information from https://github.com/microsoft/vcpkg (HEAD)...
Detecting compiler hash for triplet x64-windows...
The following packages will be built and installed:
  * armadillo:x64-windows -> 12.0.1 -- C:\Users\user\AppData\Local\vcpkg\registries\git-trees\8e222a2972a96da2fbb07a76585574e9512b107f
  * blas:x64-windows -> 2023-03-25 -- C:\Users\user\AppData\Local\vcpkg\registries\git-trees\0fe7611c8bb3098083440074a6c59f35bfee4f99
  * cereal:x64-windows -> 1.3.2#1 -- C:\Users\user\AppData\Local\vcpkg\registries\git-trees\075869fcf5302c6dd11d564286d0dfa1d2d4d7a1
  * ensmallen:x64-windows -> 2.19.0 -- C:\Users\user\AppData\Local\vcpkg\registries\git-trees\00de3f8f709bd51bba23d6aa8f01636a1e99f298
  * lapack:x64-windows -> 2022-02-22#2 -- C:\Users\user\AppData\Local\vcpkg\registries\git-trees\7c892b58c70ebc7d83444c4e727272cad40e28c2
  * lapack-reference[blas-select,core,noblas]:x64-windows -> 3.11.0#1 -- C:\Users\user\AppData\Local\vcpkg\registries\git-trees\d71a74d50d88f3cf337d7cefccadcb192e7d12ab
    mlpack[core,openmp]:x64-windows -> 4.0.1 -- C:\Users\user\AppData\Local\vcpkg\registries\git-trees\274dd7a42860f7c70f7b94d5f8e3ad9083fa6e0d
  * openblas:x64-windows -> 0.3.23 -- C:\Users\user\AppData\Local\vcpkg\registries\git-trees\716c00140c032ec22773130b006af542e011f00e
  * stb:x64-windows -> 2023-04-11#1 -- C:\Users\user\AppData\Local\vcpkg\registries\git-trees\acd9c2bf96a3e32fbf629b1bfd6cba4827761069
  * vcpkg-cmake:x64-windows -> 2023-05-04 -- C:\Users\user\AppData\Local\vcpkg\registries\git-trees\88a7058fc7fa73a9c4c99cfcae9d79e2abf87a5a
  * vcpkg-cmake-config:x64-windows -> 2022-02-06#1 -- C:\Users\user\AppData\Local\vcpkg\registries\git-trees\8d54cc4f487d51b655abec5f9c9c3f86ca83311f
  * vcpkg-gfortran:x64-windows -> 3#3 -- C:\Users\user\AppData\Local\vcpkg\registries\git-trees\1af46bd54a9156a9f24fc7c8715488699522b382
Additional packages (*) will be modified to complete this operation.
Restored 2 package(s) from C:\Users\user\AppData\Local\vcpkg\archives in 50 ms. Use --debug to see more details.
Installing 1/12 vcpkg-cmake-config:x64-windows...
Elapsed time to handle vcpkg-cmake-config:x64-windows: 10.5 ms
Installing 2/12 vcpkg-cmake:x64-windows...
Elapsed time to handle vcpkg-cmake:x64-windows: 12.6 ms
Installing 3/12 stb:x64-windows...
Building stb:x64-windows...
-- Installing port from location: C:\Users\user\AppData\Local\vcpkg\registries\git-trees\acd9c2bf96a3e32fbf629b1bfd6cba4827761069
-- Using cached nothings-stb-5736b15f7ea0ffb08dd38af21067c314d6a3aae9.tar.gz.
-- Extracting source C:/Users/user/AppData/Local/vcpkg/downloads/nothings-stb-5736b15f7ea0ffb08dd38af21067c314d6a3aae9.tar.gz
-- Using source at C:/Users/user/source/repos/ml-trails/vcpkg_installed/vcpkg/blds/stb/src/14d6a3aae9-dc9b68ccde.clean
-- Installing: C:/Users/user/source/repos/ml-trails/vcpkg_installed/vcpkg/pkgs/stb_x64-windows/share/stb/FindStb.cmake
-- Installing: C:/Users/user/source/repos/ml-trails/vcpkg_installed/vcpkg/pkgs/stb_x64-windows/share/stb/vcpkg-cmake-wrapper.cmake
-- Installing: C:/Users/user/source/repos/ml-trails/vcpkg_installed/vcpkg/pkgs/stb_x64-windows/share/stb/usage
-- Installing: C:/Users/user/source/repos/ml-trails/vcpkg_installed/vcpkg/pkgs/stb_x64-windows/share/stb/copyright
-- Performing post-build validation
Stored binaries in 1 destinations in 108 ms.
Elapsed time to handle stb:x64-windows: 775 ms
Installing 4/12 openblas:x64-windows...
Building openblas:x64-windows...
-- Installing port from location: C:\Users\user\AppData\Local\vcpkg\registries\git-trees\716c00140c032ec22773130b006af542e011f00e
-- Using cached xianyi-OpenBLAS-394a9fbafe9010b76a2615c562204277a956eb52.tar.gz.
-- Extracting source C:/Users/user/AppData/Local/vcpkg/downloads/xianyi-OpenBLAS-394a9fbafe9010b76a2615c562204277a956eb52.tar.gz
-- Applying patch uwp.patch
-- Applying patch fix-redefinition-function.patch
-- Applying patch fix-uwp-build.patch
-- Applying patch install-tools.patch
-- Using source at C:/Users/user/source/repos/ml-trails/vcpkg_installed/vcpkg/blds/openblas/src/77a956eb52-e24e9a6e76.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows

And it gets stuck there.
Environment

OS: Windows
Compiler: MSVC. I also have Intel's Fortran compiler.

To Reproduce
Steps to reproduce the behavior:

Attempt installing mlpack in manifest mode with Windows 10 SDK. Intel's Fortran compiler also needs to be installed.

Expected behavior
The installation should finish successfully.

vcpkg.json:
"builtin-baseline": "638b1588be3a265a9c7ad5b212cef72a1cad336a",
"dependencies": [
  {
    "name": "mlpack",
    "default-features": true,
    "features": [ "openmp" ]
  }
]

I'm not able to repro this issue.

I uninstalled Intel compilers (and the whole Intel oneAPI) and reinstalled Visual Studio Community edition (v17.8.0). Looks like Intel was not the problem because I am still getting stuck at installing openblas. I also launched vcpkg with --debug option. Still, the last message I get is Configuring x64-windows and then nothing. In fact, I have to completely restart my PC to free up some of the files that vcpkg was writing to. The logs with --debug option is attached. Is there a way to make the logs more verbose?
vcpkg_error.log

Looks like my antivirus (Avast) was interfering with it. Taking shield controls down for a bit did the job.

Turning off zscaler Internet Security fixed this for me as well


text:
Panda 3D

Panda is a game engine framework for both c++ and python.
https://github.com/panda3d/panda3d
Please consider it, Thanks

We can’t reopen this issue until a PR is opened, unfortunately, consider making a pull request!

authors: JackBoosY ThinkalVB


text:
[boost-headers] Build error on x64-windows

Package: boost-headers:x64-windows@1.85.0#1
Host Environment

Host: x64-windows
Compiler: MSVC 19.40.33811.0
vcpkg-tool version: 2024-06-10-02590c430e4ed9215d27870138c2e579cc338772
vcpkg-scripts version: 576379156 2024-07-05 (21 hours ago)

To Reproduce
vcpkg install boost
Failure logs
-- Downloading https://github.com/boostorg/headers/archive/boost-1.85.0.tar.gz -> boostorg-headers-boost-1.85.0.tar.gz...
-- Extracting source F:/gitlab/vcpkg/downloads/boostorg-headers-boost-1.85.0.tar.gz
-- Using source at F:/gitlab/vcpkg/buildtrees/boost-headers/src/ost-1.85.0-f4cb877742.clean
CMake Error at installed/x64-windows/share/vcpkg-boost/boost-install.cmake:29 (file):
  file RENAME failed to rename

    F:/gitlab/vcpkg/buildtrees/boost-headers/src/ost-1.85.0-f4cb877742.clean/

  to

    F:/gitlab/vcpkg/buildtrees/boost-headers/src/ost-1.85.0-f4cb877742.clean.tmp/

  because: �ܾ����ʡ�

Call Stack (most recent call first):
  ports/boost-headers/portfile.cmake:12 (boost_configure_and_install)
  scripts/ports.cmake:192 (include)

Using the latest version of vcpkg for local installation does not reproduce the issue.
Please try with latest vcpkg.
If the issue persists, please see #30604 for how to report a build failure.


text:
[open62541] build failure (pip hash changed)

The hash for pip has changed.  I think there is another port that also installs pip.  The quick fix that can be done right away is to update the hash with the value below.  After that we should look into making this stable so the hash won't change underneath us.
Starting package 594/1077: open62541:x86-windows
Building package open62541[core]:x86-windows...
Could not locate cached archive: C:\vsts\_work\3\s\archives\ad\ada37b8a48511121a87bcedf00a4309196f8ad4a.zip
-- Using cached C:/vsts/_work/3/s/downloads/open62541-open62541-v0.3.0.tar.gz
-- Extracting source C:/vsts/_work/3/s/downloads/open62541-open62541-v0.3.0.tar.gz
-- Using source at C:/vsts/_work/3/s/buildtrees/open62541/src/v0.3.0-a3fe33fd2f
-- Downloading https://bootstrap.pypa.io/get-pip.py...
CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:96 (message):

  File does not have expected hash:

          File path: [ C:/vsts/_work/3/s/downloads/temp/tools/python/python-3.7.3/get-pip.py ]
      Expected hash: [ 99520d223819708b8f6e4b839d1fa215e4e8adc7fcd0db6c25a0399cf2fa10034b35673cf450609303646d12497f301ef53b7e7cc65c78e7bce4af0c673555ad ]
        Actual hash: [ 5af99e9ccfcf3db2c97880448e9e92424b9b2af2cd0c888fb31107555809caf03fde28eec6f17f125bd3eca77bec2e353bcc7116525c17c8bdf85abe8973cc44 ]

  The file may have been corrupted in transit.  This can be caused by
  proxies.  If you use a proxy, please set the HTTPS_PROXY and HTTP_PROXY
  environment variables to
  "https://user:password@your-proxy-ip-address:port/".

Call Stack (most recent call first):
  scripts/cmake/vcpkg_download_distfile.cmake:179 (test_hash)
  ports/open62541/portfile.cmake:39 (vcpkg_download_distfile)

This issue has been fixed. So I am closing this issue for now.


text:
[azure-iot-sdk-c] Fixed the CMake config export.

The azure-iot-sdk-c port seems not to be really usable by using CMake config files.
When one tries to consume the library by the following block:
find_package(azure_iot_sdks CONFIG REQUIRED)
# Note: 7 target(s) were omitted.
target_link_libraries(main PRIVATE serializer iothub_client prov_auth_client digitaltwin_client)

Soon one will see this error when running CMake:
CMake Error: The following variables are used in this project, but they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake files:
IOTHUB_CLIENT_INCLUDES

From my end, the problem is that iothub_client target is not exported from its CMake configs, but only ${provisioning_libs} get exported.
This patch is attempting to correct this behavior.

cc @ewertons

@NancyLi1013 Thanks for the feedback. I updated the recipe accordingly.
@ewertons Let me know if my patch makes sense or not. Hope the patch can be folded back to the upstream.

/azp run

/azp run

include(vcpkg_common_functions) is no longer needed.
Could you please remove this line?
Sorry, I didn't notice this before.

@NancyLi1013 updated. Thanks for the feedback.

/azp run

/azp run

All features have passed on the following triplets:

x86-windows
x64-windows
x64-windows-static

Cool, thanks @seanyen :D


text:
[directxtk12][directxtex] Update to latest version

https://github.com/microsoft/DirectXTK12/releases/tag/jun2020b
https://github.com/microsoft/DirectXTex/releases/tag/jun2020b

Thanks for the PR!


text:
[meson|scripts] update scripts

use native/cross files for meson and make crossbuilds on windows work
depends

[x] https://github.com/mesonbuild/meson/issues/7977

seems like a merged the wrong branch here once. The expat changes shouldn't be in here.

Current error:
Traceback (most recent call last):
  File "E:\vcpkg_cache\downloads\tools\meson\meson-0.56.0\mesonbuild\mesonmain.py", line 140, in run
    return options.run_func(options)
  File "E:\vcpkg_cache\downloads\tools\meson\meson-0.56.0\mesonbuild\msetup.py", line 253, in run
    app.generate()
  File "E:\vcpkg_cache\downloads\tools\meson\meson-0.56.0\mesonbuild\msetup.py", line 161, in generate
    self._generate(env)
  File "E:\vcpkg_cache\downloads\tools\meson\meson-0.56.0\mesonbuild\msetup.py", line 223, in _generate
    intr.backend.generate()
  File "E:\vcpkg_cache\downloads\tools\meson\meson-0.56.0\mesonbuild\backend\ninjabackend.py", line 533, in generate
    self.write_rules(outfile)
  File "E:\vcpkg_cache\downloads\tools\meson\meson-0.56.0\mesonbuild\backend\ninjabackend.py", line 1122, in write_rules
    b.count_rule_references()
  File "E:\vcpkg_cache\downloads\tools\meson\meson-0.56.0\mesonbuild\backend\ninjabackend.py", line 342, in count_rule_references
    if self._should_use_rspfile():
  File "E:\vcpkg_cache\downloads\tools\meson\meson-0.56.0\mesonbuild\backend\ninjabackend.py", line 336, in _should_use_rspfile
    return self.rule.length_estimate(infilenames,
  File "E:\vcpkg_cache\downloads\tools\meson\meson-0.56.0\mesonbuild\backend\ninjabackend.py", line 273, in length_estimate
    if chunk[1] == '{':
IndexError: string index out of range

waiting for upstream comment

something is strange here:
without the  changes the following compiles:
[1/5] cc -Imunit_example.p -I. -I../src/3a51af77fd-8670ab3989.clean -Xclang -fcolor-diagnostics -pipe -Wall -Winvalid-pch -std=c99 -fPIC -MD -MQ munit_example.p/example.c.o -MF munit_example.p/example.c.o.d -o munit_example.p/example.c.o -c ../src/3a51af77fd-8670ab3989.clean/example.c
with these changes there is an error:
[1/5] /Library/Developer/CommandLineTools/usr/bin/cc -Imunit_example.p -I. -I../src/3a51af77fd-8670ab3989.clean -I/Users/vagrant/Data/installed/x64-osx/include -Xclang -fcolor-diagnostics -pipe -Wall -Winvalid-pch -std=c99 -fPIC -O3 -DNDEBUG -MD -MQ munit_example.p/example.c.o -MF munit_example.p/example.c.o.d -o munit_example.p/example.c.o -c ../src/3a51af77fd-8670ab3989.clean/example.c
FAILED: munit_example.p/example.c.o
/Library/Developer/CommandLineTools/usr/bin/cc -Imunit_example.p -I. -I../src/3a51af77fd-8670ab3989.clean -I/Users/vagrant/Data/installed/x64-osx/include -Xclang -fcolor-diagnostics -pipe -Wall -Winvalid-pch -std=c99 -fPIC -O3 -DNDEBUG -MD -MQ munit_example.p/example.c.o -MF munit_example.p/example.c.o.d -o munit_example.p/example.c.o -c ../src/3a51af77fd-8670ab3989.clean/example.c
In file included from ../src/3a51af77fd-8670ab3989.clean/example.c:11:
../src/3a51af77fd-8670ab3989.clean/munit.h:29:10: fatal error: 'stdlib.h' file not found
#include <stdlib.h>
         ^~~~~~~~~~
1 error generated.

for me the cmd line looks virtually the same except that instead of only cc the full path to /Library/Developer/CommandLineTools/usr/bin/cc is used (and the extra compiler flags and includes). Can somebody with access to a OSX debug this? I don't understand what is happening here and the osx failure is the only thing blocking this PR. @JackBoosY @strega-nil @BillyONeal

@Neumann-A Trying...

Same error on osx machine by manually run that command:
vcpkg@vcpkg x64-osx-rel %  /Library/Developer/CommandLineTools/usr/bin/cc -Imunit_example.p -I. -I../src/3a51af77fd-8670ab3989.clean -I/Users/vcpkg/Documents/vcpkg/12945/vcpkg/installed/x64-osx/include -Xclang -fcolor-diagnostics -pipe -Wall -Winvalid-pch -std=c99 -fPIC -O3 -DNDEBUG -MD -MQ munit_example.p/example.c.o -MF munit_example.p/example.c.o.d -o munit_example.p/example.c.o -c ../src/3a51af77fd-8670ab3989.clean/example.c
In file included from ../src/3a51af77fd-8670ab3989.clean/example.c:11:
../src/3a51af77fd-8670ab3989.clean/munit.h:29:10: fatal error: 'stdlib.h' file not found
#include <stdlib.h>
         ^~~~~~~~~~
1 error generated.

@strega-nil Can you please take a look?

Thanks so much @Neumann-A ! You've put a ton of work into making this a better experience and we really appreciate it 😄

Just for the records:
The meson version used in vcpkg is now at this commit of the master branch:
https://github.com/mesonbuild/meson/commit/91876b40316962620c1705ae14075ab46f8dd644

@c72578 yeah I had to restore to using some fixed commit of meson/master since meson seems to be horribly unstable and I did not want to wait for 0.61 for this to be merged .... I also considered to somehow add patches to vcpkg_find_acquire_program to patch the mess meson sometimes is.....

authors: JackBoosY Neumann-A c72578 strega-nil


text:
[vcpkg] Fix uploading to Azure DevOps Artifacts

Fixes regression caused by #14202.
While ADO Artifacts supports downloading without an ApiKey, it does not support uploading. This PR detects the error message emitted by NuGet when attempting to upload to ADO and retries with the given dummy ApiKey (AzureDevOps). Users using other servers can specify ApiKeys via the nugetconfig provider or the SetApiKey CLI command of nuget.exe.
As a drive by, the documentation on how to specify credentials for NuGet has been greatly expanded.

What does your PR fix?

Fixes #14304. Fixes #14840.
@thomas-t1 @photex I'd appreciate it if you could confirm that this change fixes your respective issues :)

Thanks for your contribution!


text:
[mujs] Missing fixes

Follow-up from #29543:

Fix name of unofficial cmake config.
Fix version information of cmake config.
Add and document official usage: mujs.pc (as in upstream makefile)
Link libm when available  (as in upstream makefile)
Enable shared linkage for non-windows  (as in upstream makefile)
Cleanup

Extras remarks (not adressed):

The unofficial cmake config is fairly obsolete with the official pc file.
The official downloads are at https://mujs.com/downloads/
There is also a GH organization matching the company's name, but it seems less popular:
https://github.com/ArtifexSoftware/mujs
The licensing might be more complex:
https://tracker.debian.org/media/packages/m/mujs/copyright-1.3.2-1

[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.

Thanks for the fix @dg0yt. This looks much better.

Why all those changes I was not aware of?

Why all those changes I was not aware of? Are those new requirements for all future ports?

Some changes are identical to what I requested for mupdf, your other PR.
Some changes are for old port shortcomings with regard to upstream.
Some changes are pure cleanup.
It is all based on the current maintainer guidelines.
To discuss all those issues, it needs fair time for review and constructive communication.

authors: JavierMatosD as-shura dg0yt


text:
[dv-processing] 1.7.8 update

Update the dv-processing package to its latest 1.7.8 release.

[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.

@microsoft-github-policy-service agree company="iniVation AG"


text:
[cachelib] add new unofficial facebook cachelib port

[x] Changes comply with the maintainer guide
[ ] 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.

The cachelib on https://repology.org/ does not match, which is a python package.

[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] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[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 cachelib on https://repology.org/ does not match, which is a python package.

https://repology.org/projects/?search=cachelib
The python package is a separate one for most repositories: python:cachelib
cachelib is the facebook lib for the Fedora repository. Debian, Ubuntu, Kali and Raspian are listed with the python package but I assume it is an error. https://github.com/repology/repology-rules/issues/684

I have the following error when installing and testing, please fix the installation error.
/data/cache/vcpkg/buildtrees/cachelib/src/3.02.27.00-fc5b057a08.clean/cachelib/../cachelib/shm/ShmCommon.h:18:10: fatal error: numa.h: No such file or directory
 #include <numa.h>
          ^~~~~~~~
compilation terminated.

The usage has been tested successfully locally.
find_package()
target_link_library()


text:
Nanojson

@microsoft-github-policy-service agree [company="Open Source Patterns"]
@microsoft-github-policy-service agree
@microsoft-github-policy-service agree company="Microsoft"

@microsoft-github-policy-service agree company="Open Source Patterns"

@microsoft-github-policy-service agree company="Open Source Patterns"


text:
Update CMake to 3.29.2

Since CMake version 3.29.2 reverted Kitware -CMake - 9390 in Kitware - CMake - 9420, update it.
Fix #37968. Take the place of #38017.
See Kitware - CMake - 25873 and Kitware - CMake - 25827

/azp run


text:
autopep8 incorrectly skips sources as standard library files

Symptoms: Trying to format a source with autopep8 v2023.6.0 doesn't do anything. The code is on a Debian-based system.
Output>autopep8:
2023-07-13 12:20:40.266 [info] [Trace - 12:20:40 PM] Sending request 'textDocument/formatting - (3)'.
2023-07-13 12:20:40.268 [info] [Trace - 12:20:40 PM] Received notification 'window/logMessage'.
2023-07-13 12:20:40.268 [info] [Warn  - 12:20:40 PM] Skipping standard library file: /usr/local/home/username/code/foo.py
2023-07-13 12:20:40.269 [info] [Trace - 12:20:40 PM] Received response 'textDocument/formatting - (3)' in 2ms.

Likely culprit is #103 - _site_paths were changed to include paths from sysconfig
https://github.com/microsoft/vscode-autopep8/blob/96c1d850cd3a0ef3ca302a518861cd077d64be1c/bundled/tool/lsp_utils.py#L32-L39
These paths are then used as prefixes to detect standard library files.
https://github.com/microsoft/vscode-autopep8/blob/96c1d850cd3a0ef3ca302a518861cd077d64be1c/bundled/tool/lsp_utils.py#L57-L60
These files are skipped here:
https://github.com/microsoft/vscode-autopep8/blob/96c1d850cd3a0ef3ca302a518861cd077d64be1c/bundled/tool/lsp_server.py#L349-L351
Output from python:
Python 3.11.4 (main, Jun  7 2023, 10:13:09) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_default_scheme()
'posix_local'
>>> sysconfig.get_paths()
{'stdlib': '/usr/lib/python3.11', 'platstdlib': '/usr/lib/python3.11', 'purelib': '/usr/local/lib/python3.11/dist-packages', 'platlib':
'/usr/local/lib/python3.11/dist-packages', 'include': '/usr/include/python3.11', 'platinclude': '/usr/include/python3.11', 'scripts':
'/usr/local/bin', 'data': '/usr/local'}

'data' : '/usr/local' is a directory for data files (doc), but here it is also a base folder for the user's home folder. So the source file, which in our example is /usr/local/home/username/code/foo.py, gets skipped. I believe data shouldn't be added to _site_paths.

Can you try build 2023.7.11941910 and let me know if it works?

Just checked, can confirm that it works now. Thanks for fixing it so quickly!

authors: karthiknadig nputikhin


text:
Fail to create a containerized function app after signing in with Azure China account

OS: All
Build Version: vscode-azurefunctions-1.13.5-alpha.0
Repro Steps:

Sign in to Azure China account.
Create a containerized function project and open in VS Code.
Create a containerized function app.
Check whether succeeds to create a containerized function app.

Expect:
Succeed to create a containerized function app.
Actual:
Fail to create a containerized function app.

This is failing due to log analytics workspace not creating properly. We should do two things

Check for other supported locations if it's not available

Don't throw an error if this fails since it is optional

authors: nturinski v-xinda

repo: microsoft/vscode-azurefunctions


text:
Need to know how frequently users hit not supported features (e.g. opening large blobs)

If you try to open a large file in storage explorer,  it will give an error saying that's not supported, and give you an option to open it in Storage Explorer. I'd like to add telemetry:

How often users hit this type of limitation and why (too large, what size, not block blob, etc)
This should be recorded in the telemetry as an error for the specific action taking place
Whether the user chooses to open in Storage Explorer or not
Lower priority, probably needs to be a separate telemetry action, or maybe an additional attribute of the attempted action.
Size of blobs users are successfully dealing with

TODO: Check is the second item is supported

authors: StephenWeatherford wwlorey

repo: microsoft/vscode-azurestorage


text:
Hangs on scanning for kits

Brief Issue Summary
I have a Windows 10 VM with VS 2019, VSC and OpenSSH so I can use remote development tools.
But I can't use the plugin bc it keeps scanning for kits.
Scanning for kits: Checking Visual Studio Community 2019 Release - amd64_arm64
Source: Cmake Tools (Extension)

This happens when running from ssh and directly on VSC on the VM
Host is Linux
Expected:
Cmake targets of the project show in the plugin window
Apparent Behavior:
Hangs on scanning for kits.
CMake Tools Log
[variant] Loaded new set of variants
[kit] Successfully loaded 0 kits from C:\Users\s7c\AppData\Local\CMakeTools\cmake-tools-kits.json
[kit] Detected kits definition version change from undefined to 2. Silently scanning for kits.

Platform and Versions

Operating System: Arch Linux (Host), Windows 10 Workstation (Guest)
CMake Version: 3.20.2 (installed with chocolatey)
VSCode Version: 1.56 (stable) on Host, 1.57 (insiders) on Guest
CMake Tools Extension Version: 1.7.2 on both
Compiler/Toolchain: gcc10.2 (Host), Visual Studio 2019 (Guest)

Other Notes/Information
SSH remote development seems to not be related

The VM was fresh install, so no never worked, first time.
Waiting to arrive home to test

@andreeis in my home directory on Windows, inside .vscode-insiders folder I don't have a settings.json

[main] Safe constructing new CMakeTools instance
[variant] Constructing VariantManager
[main] Constructing new CMakeTools instance
[main] Starting CMakeTools second-phase init
[variant] Loaded new set of variants
[main] CMakeTools instance initialization complete.
[kit] Reading kits file C:\Users\s7c\AppData\Local\CMakeTools\cmake-tools-kits.json
[kit] Successfully loaded 0 kits from C:\Users\s7c\AppData\Local\CMakeTools\cmake-tools-kits.json
[kit] Not reading non-existent kits file: c:\Users\s7c\Desktop\Projects\SO2-2021\.vscode\cmake-kits.json
[extension] Configuring workspace on open file:///c%3A/Users/s7c/Desktop/Projects/SO2-2021
[kitsController] Rescanning for kits
[kit] Scanning for Kits on system
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\\Extensions\Microsoft\IntelliCode\CLI for compilers
[kit] Scanning directory c:\Users\s7c\.vscode-server\bin\e713fe9b05fc24facbec8f34fb1017133858842b\bin for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\VC\VCPackages for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\TestWindow for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Team Tools\Performance Tools\x64 for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\bin\Roslyn for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Team Tools\Performance Tools for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\Shared\Common\VSPerfCollectionTools\vs2019\\x64 for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\Shared\Common\VSPerfCollectionTools\vs2019\ for compilers
[kit] Scanning directory C:\Program Files (x86)\HTML Help Workshop for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.8 Tools\x64\ for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\Tools\devinit for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\FSharp\ for compilers
[kit] Scanning directory C:\Program Files (x86)\Windows Kits\10\bin\x64 for compilers
[kit] Scanning directory C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64 for compilers
[kit] Scanning directory C:\Windows\Microsoft.NET\Framework64\v4.0.30319 for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\\MSBuild\Current\Bin for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\ for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\Tools\ for compilers
[kit] Scanning directory C:\Windows\system32 for compilers
[kit] Scanning directory C:\Windows for compilers
[kit] Scanning directory C:\Windows\System32\Wbem for compilers
[kit] Scanning directory C:\Windows\System32\WindowsPowerShell\v1.0\ for compilers
[kit] Scanning directory C:\Windows\System32\OpenSSH\ for compilers
[kit] Scanning directory C:\ProgramData\chocolatey\bin for compilers
[kit] Scanning directory C:\Program Files\dotnet\ for compilers
[kit] Scanning directory C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\ for compilers
[kit] Scanning directory C:\Program Files\Microsoft SQL Server\130\Tools\Binn\ for compilers
[kit] Scanning directory C:\Program Files\CMake\bin for compilers
[kit] Scanning directory C:\Program Files\Git\cmd for compilers
[kit] Skipping scan of not existing path C:\Users\s7c\.dotnet\tools
[kit] Found 0 kits in directory C:\Users\s7c\.dotnet\tools
[kit] Scanning directory C:\Users\s7c\AppData\Local\Microsoft\WindowsApps for compilers
[kit] Skipping scan of not existing path C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\WindowsApps
[kit] Found 0 kits in directory C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\WindowsApps
[kit] Scanning directory C:\Users\s7c\AppData\Local\Programs\Microsoft VS Code Insiders\bin for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\VC\Linux\bin\ConnectionManagerExe for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.28.29910\bin\HostX64\x64 for compilers
[kit] Skipping scan of not existing path C:\Program Files\LLVM\bin
[kit] Found 0 kits in directory C:\Program Files\LLVM\bin
[kit] Skipping scan of not existing path C:\Program Files (x86)\LLVM\bin
[kit] Found 0 kits in directory C:\Program Files (x86)\LLVM\bin
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\\Extensions\Microsoft\IntelliCode\CLI
[kit] Found 0 kits in directory c:\Users\s7c\.vscode-server\bin\e713fe9b05fc24facbec8f34fb1017133858842b\bin
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\VC\VCPackages
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\TestWindow
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Team Tools\Performance Tools\x64
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Team Tools\Performance Tools
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\bin\Roslyn
[kit] Found 0 kits in directory C:\Program Files (x86)\HTML Help Workshop
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio\Shared\Common\VSPerfCollectionTools\vs2019\
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio\Shared\Common\VSPerfCollectionTools\vs2019\\x64
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\Tools\devinit
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.8 Tools\x64\
[kit] Found 0 kits in directory C:\Program Files (x86)\Windows Kits\10\bin\x64
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\FSharp\
[kit] Found 0 kits in directory C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\\MSBuild\Current\Bin
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\Tools\
[kit] Found 0 kits in directory C:\Windows\Microsoft.NET\Framework64\v4.0.30319
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\
[kit] Found 0 kits in directory C:\Windows
[kit] Found 0 kits in directory C:\Windows\System32\WindowsPowerShell\v1.0\
[kit] Found 0 kits in directory C:\Windows\System32\OpenSSH\
[kit] Found 0 kits in directory C:\Windows\System32\Wbem
[kit] Found 0 kits in directory C:\ProgramData\chocolatey\bin
[kit] Found 0 kits in directory C:\Program Files\dotnet\
[kit] Found 0 kits in directory C:\Program Files\Microsoft SQL Server\130\Tools\Binn\
[kit] Found 0 kits in directory C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\
[kit] Found 0 kits in directory C:\Program Files\CMake\bin
[kit] Found 0 kits in directory C:\Program Files\Git\cmd
[kit] Found 0 kits in directory C:\Users\s7c\AppData\Local\Programs\Microsoft VS Code Insiders\bin
[kit] Found 0 kits in directory C:\Users\s7c\AppData\Local\Microsoft\WindowsApps
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\VC\Linux\bin\ConnectionManagerExe
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer
[kit] Found 0 kits in directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.28.29910\bin\HostX64\x64
[kit] Found 0 kits in directory C:\Windows\system32
[kit] Checking for kit: Visual Studio Community 2019 Release - x86
[kit] Checking for kit: Visual Studio Community 2019 Release - x86_amd64
[kit] Checking for kit: Visual Studio Community 2019 Release - x86_arm
[kit] Checking for kit: Visual Studio Community 2019 Release - x86_arm64
[kit] Checking for kit: Visual Studio Community 2019 Release - amd64_x86
[kit] Checking for kit: Visual Studio Community 2019 Release - amd64
[kit] Checking for kit: Visual Studio Community 2019 Release - amd64_arm
[kit] Checking for kit: Visual Studio Community 2019 Release - amd64_arm64
[kit] Skipping scan of not existing path C:\Program Files\LLVM\bin
[kit] Scanning directory c:\Users\s7c\.vscode-server\bin\e713fe9b05fc24facbec8f34fb1017133858842b\bin for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\\Extensions\Microsoft\IntelliCode\CLI for compilers
[kit] Skipping scan of not existing path C:\Program Files (x86)\LLVM\bin
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.28.29910\bin\HostX64\x64 for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\VC\VCPackages for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\TestWindow for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\bin\Roslyn for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Team Tools\Performance Tools\x64 for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Team Tools\Performance Tools for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\Shared\Common\VSPerfCollectionTools\vs2019\\x64 for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\Shared\Common\VSPerfCollectionTools\vs2019\ for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.8 Tools\x64\ for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\FSharp\ for compilers
[kit] Scanning directory C:\Program Files (x86)\HTML Help Workshop for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\Tools\devinit for compilers
[kit] Scanning directory C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64 for compilers
[kit] Scanning directory C:\Program Files (x86)\Windows Kits\10\bin\x64 for compilers
[kit] Scanning directory C:\Windows\Microsoft.NET\Framework64\v4.0.30319 for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\\MSBuild\Current\Bin for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\ for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\Tools\ for compilers
[kit] Scanning directory C:\Windows\system32 for compilers
[kit] Scanning directory C:\Windows\System32\WindowsPowerShell\v1.0\ for compilers
[kit] Scanning directory C:\Windows for compilers
[kit] Scanning directory C:\Windows\System32\Wbem for compilers
[kit] Scanning directory C:\Windows\System32\OpenSSH\ for compilers
[kit] Scanning directory C:\ProgramData\chocolatey\bin for compilers
[kit] Scanning directory C:\Program Files\dotnet\ for compilers
[kit] Scanning directory C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\170\Tools\Binn\ for compilers
[kit] Scanning directory C:\Program Files\Microsoft SQL Server\130\Tools\Binn\ for compilers
[kit] Scanning directory C:\Program Files\CMake\bin for compilers
[kit] Scanning directory C:\Program Files\Git\cmd for compilers
[kit] Scanning directory C:\Users\s7c\AppData\Local\Microsoft\WindowsApps for compilers
[kit] Skipping scan of not existing path C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\WindowsApps
[kit] Skipping scan of not existing path C:\Users\s7c\.dotnet\tools
[kit] Scanning directory C:\Users\s7c\AppData\Local\Programs\Microsoft VS Code Insiders\bin for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\CMake\Ninja for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\VC\Linux\bin\ConnectionManagerExe for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\Llvm\bin for compilers
[kit] Scanning directory C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\Llvm\x64\bin for compilers
[main] Not starting CMake driver: no kits defined
[main] Not starting CMake driver: no kits defined

Still no idea why it's stuck

@Samega7Cattac, do you have any compilers under ...2019\Community\VC\Tools\MSVC...? Search for "cl.exe /s" for example from within your VS installation. I wonder if you have a very limited install, without the compilers.
Then, an idea that may unblock you. Just write manually a kit definition, anything, in your cmake-tools-kits.json or locally in your project subfolder .vscode/cmake-kits.json. You can point this manually written kit to wherever you find cl.exe on your system.

@andreeis On that dir theres other dirs with versions of the several compilers, targets, archs, includes, etc.
cl.exe is in  C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.28.29910\bin\Hostx64\x64\.

Ok, thanks for confirming. Also, don't forget to try to write manually a kit which maybe might cause scan for kits to not be run at all or at least not hang.

Curiosity, is the search recursive? bc if it is then something is wrong, it should have found the compiler in that directory I posted previously. If not, then idk if it's my dir structure that is diff from the normal (doubt, fresh install...nothing out of normal) or something wrong that we don't know yet.

@andreeis can u give me an example of where and what would be in the file?

Of course. And this is only to unblock you. We will investigate this mysterious scenario and fix the root cause.
You can add the below json fragment either in the central kits file (which you can open by running the command "CMake: Edit User-Local CMake Kits" from the palette) so that all your projects see it or if you want to keep such workaround as local as possible, you can add the same fragment in your project subfolder  #.vscode/cmake-kits.json.
For example, this is what I have for Enterprise 2019. Replace Enterprise with Community and very important, run vswhere.exe (usually from "c:\Program Files (x86)\Microsoft Visual Studio\Installer") to grab the correct "instanceId" from the output of "vswhere.exe" and copy the value in the "visualStudio" keyword in the json file.
{
"name": "Visual Studio Enterprise 2019 Release - amd64",
"visualStudio": "c5421408",
"visualStudioArchitecture": "x64",
"preferredGenerator": {
"name": "Visual Studio 16 2019",
"platform": "x64",
"toolset": "host=x64"
}
},
{
"name": "Visual Studio Enterprise 2019 Release - amd64_x86",
"visualStudio": "c5421408",
"visualStudioArchitecture": "x64",
"preferredGenerator": {
"name": "Visual Studio 16 2019",
"platform": "win32",
"toolset": "host=x64"
}
},
{
"name": "Visual Studio Enterprise 2019 Release - x86",
"visualStudio": "c5421408",
"visualStudioArchitecture": "x86",
"preferredGenerator": {
"name": "Visual Studio 16 2019",
"platform": "win32",
"toolset": "host=x86"
}
},
{
"name": "My Custom Visual Studio Enterprise 2019 Release - x86",
"visualStudio": "c5421408",
"visualStudioArchitecture": "x86",
"environmentVariables": {"MY_TEST_VAR": "MYTEST"},
"preferredGenerator": {
"name": "Ninja"
}
},
{
"name": "Visual Studio Enterprise 2019 Release - x86_amd64",
"visualStudio": "c5421408",
"visualStudioArchitecture": "x86",
"preferredGenerator": {
"name": "Visual Studio 16 2019",
"platform": "x64",
"toolset": "host=x86"
}
},

did that and selected "Visual Studio Community 2019 Release - amd64" as kit, the notification saying that is searching for kits it's still there.
And then clicked on "Configure all projects" it gets stuck on another notification saying "Configuring project: Saving open files" (all files are closed) and with the log:
[main] Configuring folder: SO2-2021
[main] Saving open files before configure/build
[main] Starting new CMake driver
[main] Starting CMake driver
[cmakefileapi-driver] Creating instance of CMakeFileApiDriver
[driver] Initializating base driver using kit
[driver] CMakeDriver Kit set to Visual Studio Community 2019 Release - amd64

Forgot to say, it still gets stuck searching for kits but this time this errors [main] Not starting CMake driver: no kits defined are gone (bc I have the manual one selected), but still stuck

@andreeis yap still doesn't work

Ok, please share all your "cmake.*" settings from your .vscode/settings.json and from the global user settings.json. I have another suspicion.

@andreeis
my user settings:
{
    "cmake.configureOnEdit": false,
    "cmake.loggingLevel": "debug",
    "cmake.configureOnOpen": true,
    "C_Cpp.updateChannel": "Insiders",
    "cmake.mingwSearchDirs": [
        "C:\\msys64\\mingw64",
        "C:\\msys64\\mingw32"
    ]
}

on my .vscode-insiders folder there's only a argv.json and a folder for extentions and inside the cmake extention I can't find the settings.json if there is any

Made GCC to work and somehow seems VS compiler is also working now, I will test for a few time

seems everything is working fine now, somehow making it find the mingw gcc compiler made the rest to work, still need to have the manual kits so I hope this gets fixed.
For now I will close this issue.

repo: microsoft/vscode-cmake-tools


text:
It kept prompting that there was no response during the generation. It took about 40 seconds for feedback to start.

It kept prompting that there was no response during the generation. It took about 40 seconds for feedback to start.
https://github.com/microsoft/vscode-copilot-release/assets/122137647/c8cb568f-f7cb-4a99-b2cd-020a54f59c56

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

authors: VSCodeTriageBot laterdayi

repo: microsoft/vscode-copilot-release


text:
Language model unavailable

Type: Bug
The only response from GitHub Copilot chat is "Language model unavailable", with absolutely no other feedback or information which might help debug the issue.
Extension version: 0.22.4
VS Code version: Code 1.95.3 (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Remote OS version: Linux x64 5.15.167.4-microsoft-standard-WSL2
Remote OS version: Linux x64 5.15.167.4-microsoft-standard-WSL2

System Info

Item
Value

CPUs
Intel(R) Core(TM) Ultra 7 165H (22 x 3072)

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_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
31.45GB (8.11GB free)

Process Argv

Screen Reader
no

VM
0%

Item
Value

Remote
WSL: Ubuntu-22.04

OS
Linux x64 5.15.167.4-microsoft-standard-WSL2

CPUs
Intel(R) Core(TM) Ultra 7 165H (22 x 0)

Memory (System)
15.35GB (8.59GB free)

VM
0%

Item
Value

Remote
WSL: Ubuntu-22.04

OS
Linux x64 5.15.167.4-microsoft-standard-WSL2

CPUs
Intel(R) Core(TM) Ultra 7 165H (22 x 0)

Memory (System)
15.35GB (8.59GB free)

VM
0%

Likely a firewall please follow the steps in this issue and add a comment with information https://github.com/microsoft/vscode-copilot-release/issues/2116#issue-2624506695


text:
Soft word wrap for code blocks

I am using the GitHub Copilot chat for some code generation tasks and it's actually annoying that the generated codes often have exceeding length making it inconvenient to read.
I have found no way to toggle a soft word wrap in the session, and I have asked the chat itself if it can do soft word wrap. It responded positively but the result is not really that.

I believe it has something to do with the VScode rendering overriding the markdown syntax but I am not sure. Again an optional soft word wrap would greatly improve the experience.

I also seemed to experience this issue, forcing me to expand the window to see the entire line. This seems to only effect code blocks as everything else wraps fine.

Duplicate of #75

authors: Daryubel adman44532 digitarald


text:
Extension issue

Issue Type: Bug
Extension Name: docs-preview
Extension Version: 0.3.47
OS Version: Windows_NT x64 10.0.18363
VSCode version: 1.44.2

Not sure why this is happening

{
	"messages": [],
	"activationTimes": {
		"codeLoadingTime": 778,
		"activateCallTime": 1,
		"activateResolvedTime": 3054,
		"activationReason": {
			"startup": true,
			"extensionId": {
				"value": "ms-vsliveshare.vsliveshare",
				"_lower": "ms-vsliveshare.vsliveshare"
			},
			"activationEvent": "*"
		}
	},
	"runtimeErrors": [
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		},
		{
			"name": "Error",
			"message": "Request failed with status code 503"
		}
	]
}

AB#239471
AB#239500

@IEvangelist - I cannot reproduce this. Do you know how you may have gotten it?

@IEvangelist - I cannot reproduce this. Do you know how you may have gotten it?

I selected Extensions > @installed and navigated to the docs-preview - I noticed it was reporting these errors. I have no idea. They are cleared up now, I wonder if it wasn't due to an internet connectivity issue - if that was the case, it would imply that the docs-preview makes an assumption that there is always the internet, and doesn't cleanly handle when there is not.

I do believe docs-preview needs a connection for xref: and :::code::: tags. We should look into handling the exception and posting a warning message to the user rather than having an unhandled exception.

sync

Hi @IEvangelist , unfortunately we couldn't repro this.  Closing this issue but please ping us if you run into again.  Thanks

authors: IEvangelist adunndevster bharney0 jamarw lamebrain

repo: microsoft/vscode-docs-authoring


text:
I am not able to run my code

Environment (please complete the following information):

OS (e.g., Windows 10):
Extension version (e.g., 1.2.3):

Describe the bug:

Repro steps:

Expected behavior:

Additional context:

Closing as incomplete. Please feel free to add more information if you have any and we can re-open the issue.

repo: microsoft/vscode-edge-devtools


text:
eslint.codeActionsOnSave.mode silently overrides eslint.codeActionsOnSave.rules

Using dbaeumer.vscode-eslint v2.2.2 w/ eslint v8.4.1
.vscode/settings.json:
{
	"eslint.codeActionsOnSave.mode": "problems",
	"eslint.codeActionsOnSave.rules": [],
	"eslint.useESLintClass": true,
}

.eslintrc.yaml:
parserOptions:
  ecmaVersion: latest
  sourceType: module
rules:
  no-multiple-empty-lines: [ warn, { max: 1, maxEOF: 0 } ]
  prefer-const: warn

package.json:
{
  "name": "eslint-test",
  "version": "1.0.0",
  "dependencies": {
    "eslint": "^8.4.1"
  }
}

When saving a file all fixes are applied even though the rules are explicitly set to an empty array. It's ok that these two options are mutually exclusive but the interaction between them is surprising without any kind of runtime warning or documentation of this invariant.
Additionally the documentation around eslint.codeActionsOnSave.rules is a little confusing. It's stated "This setting is only honored if either ESLint version 8 or greater is used or ESLint version 7 is used and the setting eslint.useESLintClass is set to true." which I mentally parsed as: version >= 8 || (version == 7.x && useESLintClass). Consider: "This setting requires ESLint 7 or higher and that the eslint.useESLintClass option is enabled".

Thanks for reporting this. I will improve the documentation around this, but "eslint.codeActionsOnSave.mode": "problems" will win over "eslint.codeActionsOnSave.rules" since otherwise the whole purpose of the mode setting is superfluous.

This setting requires ESLint 7 or higher and that the eslint.useESLintClass option is enabled

This is not fully correct. If you use version >= 8 then the setting of eslint.useESLintClass is irrelevant since version 8 only ships with a ESLint Class API.

This is not fully correct. If you use version >= 8 then the setting of eslint.useESLintClass is irrelevant since version 8 only ships with a ESLint Class API.

This is not the behavior I'm observing. If "eslint.useESLintClass": true is omitted from settings.json then "eslint.codeActionsOnSave.rules": [] has no effect. I'm attaching a short screen recording https://imgur.com/a/fhDqpvX

You are correct (see https://github.com/microsoft/vscode-eslint/blob/7568b4ce8413e890e5f7d99b18845ccd00fd3d1a/server/src/eslintServer.ts#L392) However this is a bug and shouldn't be necessary

Actually above comment is wrong. The whole code creates a ESLint class as a default at the end.

Looking at the code I do think I fixed this, but not yet available in a new version. Do you have a repro I can clone that demos what you are seeing to ensure it works now.

Sure, I made a repo which demonstrates the issue clearly:
https://github.com/laverdet/eslint-test
I've tested this on a clean installation of VS Code v1.63.1 with no user settings, and vscode-eslint v2.2.2. If you open the project and save the file index.js the content should not change. If you then open .vscode/settings.json, remove the line with content 	"eslint.useESLintClass": true, and then save index.js once more the let will turn into a const.

Is fixed in main

authors: dbaeumer laverdet

repo: microsoft/vscode-eslint


text:
Saving file to local filesystem results in NoPermissions error

When I generate an image in a Python session on a remote connection, I typically want to save these images locally. However, I am now getting a NoPermissions error when I do so:
Error exporting image: NoPermissions (FileSystemError): Unable to write file 'vscode-remote://ssh-remote+7b22686f73744e616d65223a224e5959415753227d/Users/cfonnesbeck/Downloads/no_clusters.png' (NoPermissions (FileSystemError): Error: EACCES: permission denied, mkdir '/Users')

This is being saved in a subdirectory of my personal account, so there should be no permissions error. I have tried other subdirs, but with similar effect.

VSCode Version: 1.54.3
Local OS Version: macOS 11.3
Remote OS Version: Ubuntu
Remote Extension/Connection Type: SSH

Steps to Reproduce:

Generate image in Python
Open image in plots tab
Select save icon
Select local filesystem from file browser
Save to local folder (e.g. Downloads or Desktop)

Dupe of #5269

authors: fonnesbeck rchiodo

repo: microsoft/vscode-jupyter


text:
How to move custom language server CompletionItems to top of suggestion list?

Using https://github.com/Microsoft/vscode-extension-samples/tree/main/completions-sample as a template, I created some custom CompletionItems as an extension of JavaScript.
However, these custom CompletionItems show up last in the suggestions dropdown. How do I move them to the top?
Setting item.sortText = 'A'; in connection.onCompletionResolve( (item: CompletionItem): CompletionItem => { doesn't seem to push my custom CompletionItems to the top of the suggestions list.
https://user-images.githubusercontent.com/43425812/144787820-03894eb3-2a7a-4ff8-898e-1aa28929256b.mov

There is no way that servers can control this. The reason is that every extensions thinks that its completion item will be the most important once. A server can only control the sorting for his own items.
VS Code has some ways to control this, but only on the general provider level. It mostly depends on the document selector passed in when registering the completion provider. I assume that in your example you didn't specify a language in the document selector hence VS Code thinks these items are of less importance than the items contributed for the javascript language. See https://code.visualstudio.com/api/references/document-selector for more information.

There is no way that servers can control this. The reason is that every extensions thinks that its completion item will be the most important once. A server can only control the sorting for his own items.
VS Code has some ways to control this, but only on the general provider level. It mostly depends on the document selector passed in when registering the completion provider.

I understand. I think we will try to adjust settings in extension.ts, then, because we really want our language's suggestions to show up at the top of the list, and not all the way at the bottom.

I assume that in your example you didn't specify a language in the document selector hence VS Code thinks these items are of less importance than the items contributed for the javascript language.

@dbaeumer Actually, the first parameter I passed to vscode.languages.registerCompletionItemProvider( is 'javascript'. Is that what you're referring to?
We get the same behavior regardless of whether we make the first parameter to vscode.languages.registerCompletionItemProvider( be 'javascript' or
{
	scheme: 'file',
	language: 'javascript'
}

Our full example extension.ts file is
/*---------------------------------------------------------
 * Copyright (C) Microsoft Corporation. All rights reserved.
 *--------------------------------------------------------*/

import * as vscode from 'vscode';

export function activate(context: vscode.ExtensionContext) {
	const selector: vscode.DocumentSelector = {
		scheme: 'file',
		language: 'javascript'
	};
	const provider2 = vscode.languages.registerCompletionItemProvider(
		'javascript',
		{
			provideCompletionItems(
				document: vscode.TextDocument,
				position: vscode.Position
			) {
				// get all text until the `position` and check if it reads `console.`
				// and if so then complete if `log`, `warn`, and `error`
				const linePrefix = document.lineAt(position).text.substr(0, position.character);
				console.log(
					'linePrefix',
					linePrefix,
					new Date().toLocaleTimeString()
				);
				if (!linePrefix.endsWith('console.')) {
					return undefined;
				}

				return [
					new vscode.CompletionItem('this should be at the top of the list, not near the bottom', vscode.CompletionItemKind.Method),
					new vscode.CompletionItem('this should be closer to the top', vscode.CompletionItemKind.Method),
					new vscode.CompletionItem('this should not be at the bottom of the list', vscode.CompletionItemKind.Method),
				];
			}
		},
		'.' // triggered whenever a '.' is being typed
	);

	context.subscriptions.push(provider2);
}

It's very similar to completions-sample/src/extension.ts.
https://user-images.githubusercontent.com/43425812/144938520-6e725a04-e65c-49f1-a7cd-a192b490bd41.mov

Yes, you are passing the javascript selector which is correct. Since the other items come from a provider for javascript as well it is up to VS Code to decide which one it takes first. To my knowledge there is not way you can influence this. As said it is by design in VS Code since otherwise everyone would fight about being at the top.

Ah, I see. I notice that our language's keywords even show up after all the abc suggestions, i.e., the order seems to be

JavaScript keywords
All the words in the source file
Our language's keywords

I understand that we can't move our language's keywords into the 1 position, but can we maybe at least move it into the 2 position, above all the words in the source file, @dbaeumer? It would be nice if developers didn't have to scroll down past every word in the file before arriving at our language's keywords.
https://user-images.githubusercontent.com/43425812/145081425-e2573b7e-4638-4977-b090-0a85ec481aba.mov
We made our language very similar to JavaScript, by design, so that it's more familiar to new developers. I think we want to keep letting VSCode auto-detect our source files as JavaScript, since we get a lot of nice functionality like variable renaming that way, but it would be nice if we could layer features specific to our language on top of JavaScript's language server, and do things like give priority to our language's keywords in the CompletionItem suggestions dropdown list.

All I can recommend is to open a request against VS Code itself since this is not under the control of the LSP libraray.

Okay, I appreciate the information. Thank you for your responses!

authors: dbaeumer hamirmahal

repo: microsoft/vscode-languageserver-node

license: mit

license_source: bigquery


text:
I am stuck in a PR that I am not on

My setup:

multi root workspace
first folder: vscode
second folder: vscode-docs (checked out to vnext)

From https://github.com/microsoft/vscode-docs/pull/4423

Similar experience for me.

In the below screen shot, the pr that I'm "stuck" on is closed. It's merging from one protected branch into another.

This might be the same I was experiencing here: https://github.com/microsoft/vscode-pull-request-github/issues/2356

Because the branch vnext is associated with a pull request we show the pull request view. We now have https://github.com/microsoft/vscode-pull-request-github/issues/3009, which will not use the associated PR if the PR is closed (not merged, just closed).

authors: AlCalzone alexr00 bpasero ryanaklein

repo: microsoft/vscode-pull-request-github


text:
Seeing partial files when exploring a pull request

Given the PR is from another branch in the same repository, could we not fetch from it as needed?

I duplicated this with https://github.com/microsoft/vscode-pull-request-github/issues/2070, this should now be fixed

authors: RMacfarlane alexdima


text:
Make PRs and Issues views have same commands

Fixes #1744

@RMacfarlane, while I was doing this I noticed that the Sign in isn't working right now. Steps:
Sign out from User icon near gear
Sign in through "Sign in" in Pull Requests vew
See that the view isn't updated.

@alexr00 ah, I see the problem - This only happens when logging out and back in again. In the credential store reset method, I always just set the API to undefined, this.initialize() should be called after that

I'll push a commit here to fix it


text:
'Debug Python File' does nothing

Open Python file in a folder that doesn't have a launch config defined
Set breakpoint
From editor title run menu, choose 'Debug Python File'
:bug: nothing happens

Note that if I go into the Run/Debug view and choose the Python Debugger launch config, then F5 to debug, that works

I am having a similar issue here. I am developing in a docker container with Python 3.6.9. The Python Debugger Extension version is v2023.1.12492010
When I open the "Run and Debug" panel on the left side and hit the green button for "Debugpy: Python File" or "Debugpy: Current File", I can debug my python file and stop at the breakpoint. As below:

However, if I click the small "run and debug" button on the top right corner, it seems that it still uses the "Python Extension" (rather than Debugger Extension) so that I get the error of Python version less than 3.7 is not supported.

My host machine and VS Code version:

Version: 1.83.0
Commit: e7e037083ff4455cf320e344325dacb480062c3c
Date: 2023-10-03T16:11:49.843Z
Electron: 25.8.4
ElectronBuildId: 24154031
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Linux x64 6.2.0-26-generic snap

Python version: 3.6.9
Dev Container version: v0.315.0
Python extension version: v2023.16.0
Python Debugger Extension version: v2023.1.12492010

Duplicated: https://github.com/microsoft/vscode-python-debugger/issues/137

authors: XuShenLZ joyceerhl paulacamargo25

repo: microsoft/vscode-python-debugger