text:
[Feature] Make colortool part of cmd

Add a theme tab to the console properties, to allow us to quickly and easily load/change themes. Instead of having to download a seperate tool.
Or.
Ship colortool as part of windows, already in your path.
Thx for the great work as always.

Sorry, we're not going to take additions to CMD and it's not likely that we'll be authorized to add a utility for developer-only scope to the default image. So I'm just going to resolve this. Sorry!

authors: miniksa p-groarke


text:
Incorrect tooltip text when terminal is maximized

Environment
Windows build number: [10.0.18363.778]
Windows Terminal version (if applicable): Current master 44689b93

Any other software? No

Steps to reproduce

Open terminal and maximize the window.
Hover the mouse over the restore button.
Expected behavior
Displays the tooltip Restore Down

Actual behavior

Displays the tooltip Maximize

Yup.

We knew this was a problem when we first added automation text (for accessibility).

Yes, it should be "restore down". I couldn't figure out how to do that.

Is there a possibility that we can use the system default buttons? They come with tooltips.

There is no possibility of us using the system buttons. :(

source: gharchive/issue

authors: Chips1234 DHowett DHowett-MSFT encladeus

repo: microsoft/terminal

license: MIT

license_type: permissive

license_source: github-api


text:
Initialize the VT tab stops when a buffer is created in VT mode

Summary of the Pull Request
If a user has VirtualTerminalLevel set, then SetConsoleMode(ENABLE_VIRTUAL_TERMINAL_PROCESSING) won't set our tab stops, because we're never going from vt off -> on.
So, if VT mode is enabled, construct the VT tab stops when the buffer is created.
PR Checklist

[x] Closes #411
[x] I work here
[x] Tests added/passed

Detailed Description of the Pull Request / Additional comments
Big shout-out to @j4james for basically doing all the work on what I thought was an impossible bug. Thanks!

Huh, this broke the input line tests somehow.

source: gharchive/pull-request

authors: DHowett-MSFT zadjii-msft


text:
Training & Inference examples for RetNet

Could you provide some Training & Inference examples for RetNet?

I found one blog (in Japanese) that might be useful https://zenn.dev/selllous/articles/retnet_tutorial.

authors: donglixp jhl-Det

repo: microsoft/torchscale


text:
Deprecating library operation templates causes derived operations to be marked as deprecated in swagger

When Azure.Core v1 operations were recently deprecated, any operation that suppressed the decoration warning was still marked as deprecated in generated OpenAPI
Need to have a mechanism for marking operation templates as decorated without carrying through the deprecation to derived concrete operations

Closing in favor of #2006 which is more generic

authors: markcowl timotheeguerin

repo: microsoft/typespec


text:
Temporarily pin Node 20 to 20.5 to avoid Babel error

It looks like CI is failing due to an issue with Babel.js conflicting with Node 20.6:
https://github.com/babel/babel/issues/15927
https://github.com/vitejs/vite/issues/14299
For now, let's try pinning Node 20.x to 20.5 until the issue gets fixed in Babel.
Comparable typespec-azure repo PR: https://github.com/Azure/typespec-azure/pull/3502
Issue https://github.com/Azure/typespec-azure/issues/3504 tracks the work to un-pin the Node version.

@mikeharder Can you take a look to see whether I'm pinning the Node version correctly in the 20.x jobs?  We've hit an issue with a dependency conflicting with Node 20.6 so I'm trying to pin it back to 20.5.

This appears to be a regression in Node 20.6.0: https://github.com/nodejs/node/issues/49497.  I agree the best workaround is pinning to 20.5.  Will likely be fixed in 20.6.1.

I have node v 20.5.1 installed on my machine still fails to run...! why..?

authors: daviwil mikeharder mohanvaidya


text:
[x-add-versions] Perform atomic replacement of versioning files

Otherwise, we hit issues like:
$ ./vcpkg x-add-version azure-kinect-sensor-sdk --overwrite-version
error removing file: /home/codespace/workspace/vcpkg/versions/a-/azure-kinect-sensor-sdk.json: No such file or directory

where afterwards the backup file exists and the original file has been removed. This is also just generally more "correct" and guards against process termination during the file write.

/azp run

repo: microsoft/vcpkg-tool


text:
CMAKE_FIND_USE_CMAKE_SYSTEM_PATH and CMAKE_FIND_USE_CMAKE_PATH to OFF blocks CMake from finding vcpkg packages

Describe the bug
When setting CMAKE_FIND_USE_CMAKE_SYSTEM_PATH and CMAKE_FIND_USE_CMAKE_PATH to OFF, it cannot find packages installed by vcpkg. This was my attempt to block CMake from finding system provided libraries.
Environment

OS: Linux Ubuntu 20.04 (docker)
Compiler: GCC 10.0.1

To Reproduce
Steps to reproduce the behavior:

Have a simple manifest file installing a package
Have a CMake file that contains set(CMAKE_FIND_USE_CMAKE_SYSTEM_PATH OFF) and set(CMAKE_FIND_USE_CMAKE_PATH OFF) and try to find the package
Notice that it cannot found the packages located inside build/vcpkg_installed

Expected behavior
This variable is used to disable finding libraries installed in system path. Setting it to OFF when using a package manager is desirable, since it provides better isolation from the system. Not setting it to OFF may induce subtle breakage when trying to compile a project from different machines.

For example, the CMake user could set set(CMAKE_FIND_PACKAGE_PREFER_CONFIG ON) so CMake prioritize config file over its own modules, which can be very benefical for packages like boost. Let's say that our user add a dependency to libA, which provide a CMake find module. libA is installed through vcpkg. find_package(libA) finds our library installed by vcpkg. User is happy.
Then, user install libA through its system package manager. It installs a newer version of libA which exposes a CMake config module. CMake prefers that version instead and on the next cache generation, use the system provided library which introduce subtle breakage. User looses his hairs over hard to reproduce bugs since the build system acted in a surprising way.

If vcpkg already have a mechanism to prevent that, then feel free to close this issue. Otherwise, I would expect CMAKE_FIND_USE_CMAKE_SYSTEM_PATH to work by disallowing system package but still allowing vcpkg installed packages.
Additional context
I usually have a CMake file that contains this:
set(CMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY ON)
set(CMAKE_FIND_USE_CMAKE_SYSTEM_PATH OFF)
set(CMAKE_FIND_PACKAGE_PREFER_CONFIG ON)
set(CMAKE_FIND_USE_CMAKE_PATH OFF)
set(CMAKE_FIND_USE_CMAKE_ENVIRONMENT_PATH OFF)

This makes CMake finding only packages that I intended to use, the ones I added in CMAKE_PREFIX_PATH. Now I want to use vcpkg to manage my packages, but I still want isolation from system packages. Is there something that can offer me this requirement in vcpkg? Many thanks.

This makes CMake finding only packages that I intended to use, the ones I added in CMAKE_PREFIX_PATH

How are you setting CMAKE_PREFIX_PATH? (If you do a simple set there is your error)
Simply check if your CMAKE_PREFIX_PATH contains the vcpkg paths if not you messed something up (assuming you are using the toolchain vcpkg.cmake)

@Neumann-A When I was not using vcpkg, I was setting CMAKE_PREFIX_PATH using a file that configured everything so that find_package would work out of the box. (of course, I used list(APPEND ... ....) for that)
Now that I'm trying to change to vcpkg, I expect not touching this variable at all. I also expect that it's possible enabling vcpkg in a way that CMake won't find packages, executable, files, libraries or any paths from the system.
The situation is I'm trying to move away from my own, home made package manager to vcpkg. The recent addition of manifest file make that move possible and I'm not too fan of conan. It's entirely made CMake and from all the weird error I got, a lot of them was due to CMake picking up system packages for a dependency's dependency in a way I didn't expected.

Uh, it seem my issue is only happening with boost. In the end it might only be a problem with this particular package. Sorry that I didn't researched the problem further before posting.
Here's the project that reproduce the issue:
vcpkg.json
{
    "name": "mypackage",
    "version-string": "0.1.0-dev",
    "dependencies": [
        "boost-mp11"
    ]
}

CMakeLists.txt
cmake_minimum_required(VERSION 3.17)
project(test-vcpkg)

set(CMAKE_FIND_USE_CMAKE_SYSTEM_PATH OFF)
set(CMAKE_FIND_USE_CMAKE_PATH OFF)

find_package(Boost 1.74 REQUIRED COMPONENTS system)

add_executable(test-vcpkg main.cpp)
target_link_libraries(test-vcpkg PRIVATE Boost::system)

main.cpp
#include <iostream>
#include <boost/mp11.hpp>

auto main() -> int {
    std::cout << "hello" << std::endl;
}

Removing either set(CMAKE_FIND_USE_CMAKE_SYSTEM_PATH OFF) or set(CMAKE_FIND_USE_CMAKE_PATH OFF) make the configuration successful.
Here's the CMake output:
build$ rm CMakeCache.txt && cmake .. -DCMAKE_TOOLCHAIN_FILE=/root/build/vcpkg/scripts/buildsystems/vcpkg.cmake -DCMAKE_GENERATOR=Ninja -DCMAKE_MAKE_PROGRAM=/usr/bin/ninja -DCMAKE_CXX_COMPILER=/usr/bin/g++-10 -DCMAKE_C_COMPILER=/usr/bin/gcc-10
-- Running vcpkg install
-- Running vcpkg install - done
-- The C compiler identification is GNU 10.0.1
-- The CXX compiler identification is GNU 10.0.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/gcc-10 - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/g++-10 - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at /opt/cmake/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:165 (message):
  Could NOT find Boost (missing: Boost_INCLUDE_DIR system) (Required is at
  least version "1.74")
Call Stack (most recent call first):
  /opt/cmake/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:458 (_FPHSA_FAILURE_MESSAGE)
  /opt/cmake/share/cmake-3.18/Modules/FindBoost.cmake:2177 (find_package_handle_standard_args)
  /root/build/vcpkg/scripts/buildsystems/vcpkg.cmake:519 (_find_package)
  CMakeLists.txt:10 (find_package)

-- Configuring incomplete, errors occurred!
See also "/workspaces/src4/build/CMakeFiles/CMakeOutput.log".
See also "/workspaces/src4/build/CMakeFiles/CMakeError.log".

according to the find_package documentation you want to remove set(CMAKE_FIND_USE_CMAKE_PATH OFF)

@Neumann-A Why is that? Is it because CMAKE_FIND_USE_CMAKE_PATH will disable find modules that are shipped with CMake and in the case I stated we need those find modules?

@gracicot  disabling CMAKE_FIND_USE_CMAKE_PATH disables usage of CMAKE_PREFIX_PATH which vcpkg uses/sets. It is as simple as that. Please reread https://cmake.org/cmake/help/latest/command/find_package.html

Hmm, you're right. I'll close this issue. Thanks. It seems in my examples I was assuming other things and I overlooked this.

authors: Neumann-A gracicot

repo: microsoft/vcpkg


text:
Unable to compile vcpkg in linux (archlinux) using provided instructions

Describe the bug
Unable to compile vcpkg in linux (archlinux) using provided instructions
Environment

OS: Linux shark 5.9.8-arch1-1 #1 SMP PREEMPT Tue, 10 Nov 2020 22:44:11 +0000 x86_64 GNU/Linux
Compiler: -- The CXX compiler identification is GNU 6.5.0

gcc --version
gcc (GCC) 10.2.0
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

To Reproduce
Steps to reproduce the behavior:

Checkout source code
./vcpkg/bootstrap-vcpkg.sh

Expected behavior
functional vcpkg binary
Failure logs
$ ./vcpkg/bootstrap-vcpkg.sh
-- The CXX compiler identification is GNU 6.5.0
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/g++-6 - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Detecting the C++ compiler in use
-- Detecting the C++ compiler in use - gcc
-- Detecting the C++ standard library
-- Detecting the C++ standard library - libstdc++
-- Detecting how to use the C++ filesystem library
-- Detecting how to use the C++ filesystem library - <experimental/filesystem> with -lstdc++fs
-- Looking for C++ include pthread.h
-- Looking for C++ include pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- Found Threads: TRUE
-- Configuring done
-- Generating done
-- Build files have been written to: /home/tomasz/dev/vcpkg/toolsrc/build.rel
[0/2] Re-checking globbed directories...
[72/83] Building CXX object CMakeFiles/vcpkglib.dir/src/vcpkg/vcpkgcmdarguments.cpp.o
FAILED: CMakeFiles/vcpkglib.dir/src/vcpkg/vcpkgcmdarguments.cpp.o
/usr/bin/g++-6 -DVCPKG_USE_STD_FILESYSTEM=0 -I../include -O3 -DNDEBUG -include /home/tomasz/dev/vcpkg/toolsrc/include/pch.h -pthread -std=c++1z -MD -MT CMakeFiles/vcpkglib.dir/src/vcpkg/vcpkgcmdarguments.cpp.o -MF CMakeFiles/vcpkglib.dir/src/vcpkg/vcpkgcmdarguments.cpp.o.d -o CMakeFiles/vcpkglib.dir/src/vcpkg/vcpkgcmdarguments.cpp.o -c ../src/vcpkg/vcpkgcmdarguments.cpp
../src/vcpkg/vcpkgcmdarguments.cpp:925:48: error: redefinition of 'constexpr const vcpkg::StringLiteral vcpkg::VcpkgCmdArguments::OVERLAY_TRIPLETS_ENV'
     constexpr StringLiteral VcpkgCmdArguments::OVERLAY_TRIPLETS_ENV;
                                                ^~~~~~~~~~~~~~~~~~~~
In file included from ../src/vcpkg/vcpkgcmdarguments.cpp:9:0:
../include/vcpkg/vcpkgcmdarguments.h:145:40: note: 'constexpr const vcpkg::StringLiteral vcpkg::VcpkgCmdArguments::OVERLAY_TRIPLETS_ENV' previously defined here
         constexpr static StringLiteral OVERLAY_TRIPLETS_ENV = "VCPKG_OVERLAY_TRIPLETS";
                                        ^~~~~~~~~~~~~~~~~~~~
[81/83] Building CXX object CMakeFiles/vcpkglib.dir/src/vcpkg/vcpkglib.cpp.o
ninja: build stopped: subcommand failed.

Additional context
Add any other context about the problem here.

You said that you use gcc 10, but actually gcc 6 is picked

Could you run g++ --version? It may be different from gcc --version.

Could you run g++ --version? It may be different from gcc --version.

Could you run g++ --version? It may be different from gcc --version.

How do you install g++-6?

I'm using the official archlinux package manager.
https://wiki.archlinux.org/index.php/GNU_Compiler_Collection
So the command is
pacman -S gcc

I also encountered this problem on mac 10.14

@NancyLi1013  fix it  on #14744 , OVERLAY_TRIPLETS_ENV is defined twice in vcpkgcmdarguments.cpp:923 and vcpkgcmdarguments.cpp:925

Hi @akayami and @davidxiaozhi
Thanks for posting this issue.
Could you please try to rebuild this after removing constexpr StringLiteral VcpkgCmdArguments::OVERLAY_TRIPLETS_ENV in vcpkgcmdarguments.cpp:925?

Problem fixed. Thanks for quick and efficient support !

Thanks for your update @akayami. I'm reopening this issue until this issue is fixed via PR #14744 merged.

Closing since it has been fixed now.

authors: NancyLi1013 akayami davidxiaozhi linquize


text:
[curl] Could not find a configuration file for package "CURL" that is compatible with requested version "".

Is your feature request related to a problem? Please describe.
MSVC
Microsoft (R) C/C++ Optimizing Compiler Version 19.29.30139 for x64
vcpkg @ d15470bb6464a3bb0ce3d98d118190cfd5189080
find_package(CURL CONFIG REQUIRED)

Proposed solution
Install to work without version specification required
Describe alternatives you've considered
FindCurlCustom.cmake
Additional context
The package curl provides CMake targets:

    find_package(CURL CONFIG REQUIRED)
    target_link_libraries(main PRIVATE CURL::libcurl)

-- Running vcpkg install - done
CMake Error at cmake-build-debug/vcpkg_installed/x64-windows/share/curl/vcpkg-cmake-wrapper.cmake:11 (_find_package):
  Could not find a configuration file for package "CURL" that is compatible
  with requested version "".

@SamuelMarks  Thanks for posting this issue, The problem may be because MSVC is arch x64 arch vcpkg is arch x86 by default,
you can call cmake with -DVCPKG_TARGET_TRIPLET=x64-windows, see #9290. :)

@SamuelMarks Is still work for this issue? Please reply me if the problem still exist and I will reopen it.


text:
I installed vcpkg from "https://github.com/heysurfer/EnetProxy", and then tried to install openssl-windows:x64-windows. And i got this message.

C:\Users\myname\OneDrive\Työpöytä\vcpkg-master>vcpkg install openssl-windows:x64-windows
Computing installation plan...
The following packages will be built and installed:

openssl[core]:x64-windows -> 3.0.5#5
openssl-windows[core]:x64-windows -> deprecated
vcpkg-cmake[core]:x64-windows -> 2022-09-26
vcpkg-cmake-config[core]:x64-windows -> 2022-02-06#1
vcpkg-cmake-get-vars[core]:x64-windows -> 2022-09-04
Additional packages (*) will be modified to complete this operation.
Detecting compiler hash for triplet x64-windows...
error: while detecting compiler information:
The log file content at "C:\Users\myname\OneDrive\Työpöytä\vcpkg-master\buildtrees\detect_compiler\stdout-x64-windows.log" is:
-- Found external ninja('1.10.2').
-- Configuring x64-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:96 (message):
Command failed: "C:/Program Files/Microsoft Visual Studio/2022/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v
Working Directory: C:/Users/myname/OneDrive/Työpöytä/vcpkg-master/buildtrees/detect_compiler/x64-windows-rel/vcpkg-parallel-configure
Error code: 1
See logs for more information:
C:\Users\myname\OneDrive\Työpöytä\vcpkg-master\buildtrees\detect_compiler\config-x64-windows-out.log

Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_cmake.cmake:310 (vcpkg_execute_required_process)
scripts/detect_compiler/portfile.cmake:18 (vcpkg_configure_cmake)
scripts/ports.cmake:147 (include)
error: vcpkg was unable to detect the active compiler's information. See above for the CMake failure output.
i tried to fix it by:

reinstall vcpkg.
reinstall virtual studio 2022 after vcpkg deletion.

Please provide the error log file: C:\Users\myname\OneDrive\Työpöytä\vcpkg-master\buildtrees\detect_compiler\config-x64-windows-out.log.

And you could clone vcpkg to a short path and don't include Työpöytä.

@LilyWangLL the "
And you could clone vcpkg to a short path and don't include Työpöytä." worked : D. Thx so much!!


text:
Cairo vcpkg building issue Window 11

Describe the bug
A clear and concise description of what the bug is:
libtool-2.4.6-9 site download not working
I suggest using: https://mirror.msys2.org/msys/x86_64/libtool-2.4.7-3-x86_64.pkg.tar.zst instead.
Environment

OS: [e.g. Windows/Linux etc...]
Compiler: revision
Windows 11 Visual Studio 2022 v7.5

To Reproduce
Steps to reproduce the behavior: .\vcpkg.exe install cairo --triplet x64-windows
Expected behavior
A clear and concise description of what you expected to happen.  Obviously, I expect it to work.
Failure logs
-(please attached failure logs)
-- Downloading https://repo.msys2.org/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz;https://www2.futureware.at/~nickoe/msys2-mirror/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz;https://mirror.yandex.ru/mirrors/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz;https://mirrors.tuna.tsinghua.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz;https://mirrors.ustc.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz;https://mirror.bit.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz;https://mirror.selfnet.de/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz;https://mirrors.sjtug.sjtu.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz -> msys-libtool-2.4.6-9-x86_64.pkg.tar.xz...
[DEBUG] To include the environment variables in debug output, pass --debug-env
[DEBUG] Feature flag 'binarycaching' unset
[DEBUG] Feature flag 'manifests' = off
[DEBUG] Feature flag 'compilertracking' unset
[DEBUG] Feature flag 'registries' unset
[DEBUG] Feature flag 'versions' unset
[DEBUG] Downloading https://repo.msys2.org/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz
[DEBUG] Downloading https://www2.futureware.at/~nickoe/msys2-mirror/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz
[DEBUG] Downloading https://mirror.yandex.ru/mirrors/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz
[DEBUG] Downloading https://mirrors.tuna.tsinghua.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz
[DEBUG] Downloading https://mirrors.ustc.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz
[DEBUG] Downloading https://mirror.bit.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz
[DEBUG] Download failed -- retrying after 1000 ms.
[DEBUG] Download failed -- retrying after 2000 ms.
[DEBUG] Download failed -- retrying after 4000 ms.
[DEBUG] Downloading https://mirror.selfnet.de/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz
[DEBUG] Downloading https://mirrors.sjtug.sjtu.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz
Error: Failed to download from mirror set:
https://repo.msys2.org/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: failed: status code 404
https://www2.futureware.at/~nickoe/msys2-mirror/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: failed: status code 404
https://mirror.yandex.ru/mirrors/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: failed: status code 404
https://mirrors.tuna.tsinghua.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: failed: status code 404
https://mirrors.ustc.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: failed: status code 404
https://mirror.bit.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: WinHttpSendRequest() failed: 12002
https://mirror.bit.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: WinHttpSendRequest() failed: 12002
https://mirror.bit.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: WinHttpSendRequest() failed: 12002
https://mirror.bit.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: WinHttpSendRequest() failed: 12002
https://mirror.selfnet.de/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: failed: status code 404
https://mirrors.sjtug.sjtu.edu.cn/msys2/msys/x86_64/libtool-2.4.6-9-x86_64.pkg.tar.xz: failed: status code 404
Additional context
I am hoping to get python 3.10 module cairosvg to work on Windows 11 and am hoping building a version of Cairo on Windows which doesn't involve loading other libraries might be the solution.  https://github.com/Kozea/CairoSVG/issues/381
This problem has attracted much attention over several years and has not been resolved by installing GTK runtimes, or any of the other suggested remedies.

vcpkg update its libtool URL a few weeeks ago, #28919. Now you must update your vcpkg checkout.

Thanks.


text:
[boost-thread] build failure

Operating system
Linux Debian Sid
Compiler
Emcc 3.1.49
Steps to reproduce the behavior
`./vcpkg install boost-thread --triplet=wasm32-emscripten`

Failure logs
install-wasm32-emscripten-dbg-out.log
Additional context
No response

     trying generator unix.prebuilt ( -> LIB )
         property-requirements are not met: <toolset>unix
     trying generator gcc.prebuilt ( -> LIB )
         property-requirements are not met: <toolset>gcc
     trying generator emscripten.prebuilt ( -> LIB )
       is viable

Build request: object(property-set)@307 <address-model>32 <link>static <threading>multi <toolset-emscripten:version>3.1.49 <toolset>emscripten <variant>debug
It seems that boost does not recognize the tool chain emscripten. It recognizes wasm32-emscripten as toolset-emscripten.
Does boost really support emscripten?🤔
https://github.com/boostorg/boost/pull/110

     trying generator unix.prebuilt ( -> LIB )
         property-requirements are not met: <toolset>unix
     trying generator gcc.prebuilt ( -> LIB )
         property-requirements are not met: <toolset>gcc
     trying generator emscripten.prebuilt ( -> LIB )
       is viable

Build request: object(property-set)@307 <address-model>32 <link>static <threading>multi <toolset-emscripten:version>3.1.49 <toolset>emscripten <variant>debug  It seems that boost does not recognize the tool chain emscripten. It recognizes wasm32-emscripten as toolset-emscripten. Does boost really support emscripten?🤔 boostorg/boost#110

In July, it support. I think maybe some library is built after some fixes? In emscripten, people usually use boost header only...

Is there a corresponding upstream issue or PR? Maybe it’s a problem with the boost version.

Is there a corresponding upstream issue or PR? Maybe it’s a problem with the boost version.

Maybe it's this? Boost-thread seems to be fixed in Feburary...

Are you using the latest vcpkg?

Are you using the latest vcpkg?

I installed fully freshed vcpkg yesterday...

@Pospelove


text:
vcpkg install fails to detect msvc after Visual Studio 2022 build tools upgrade to 17.10.0

Describe the bug
We have been successfully using vcpkg with Visual Studio Build Tools 2022 version 17.9.x. Since upgrading to 17.10.0, installation of packages fails to find a working compiler.
Environment

OS: Windows
Compiler: 19.40.33808 for x64

To Reproduce
The issue is occurring regardless of package chosen. Steps to reproduce the behavior:

Open a Developer Command Prompt for VS2022 (or Powershell, same behavior)
cl (demonstrates that command is in path and has expected version)
./vcpkg install fmt --triplet x64-windows

Expected behavior
As with Visual Studio Build Tools 2022 version 17.9.x, we expect the compiler chosen to be cl (msvc).
Failure logs
stdout-x64-windows.log
CMakeCache.txt

Can you share the error message that you are seeing? I do not see an error in the attached log, but it seems to indicate that MSVC 19.39 was found, I believe you should be seeing 19.40 for VS2022 17.10.0.
I am not entirely sure if it is the same issue, but it sounds like the error message that I got after updating to  VS2022 17.10.1. It occurs when I install anything with from a powershell in the vcpkg folder.

error: in triplet x64-windows: Unable to find a valid Visual Studio instance
Could not locate a complete Visual Studio instance
The following paths were examined for Visual Studio instances:
C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Auxiliary/Build\vcvarsall.bat

Running ./bootstrap.bat in the vcpkg folder solved this issue for me.

Running bootstrap didn't make a difference for me.
The error which seems most relevant to me is:
-- The CXX compiler identification is Clang 17.0.3 with GNU-like command-line
C:\PROGRA~2\MICROS~3\2022\BUILDT~1\VC\Tools\Llvm\x64\bin\CLANG_~1.EXE   /nologo /DWIN32 /D_WINDOWS /W3 /utf-8 /GR /EHsc /MP   /D_DEBUG /MDd /Z7 /Ob0 /Od /RTC1  -D_DEBUG -D_DLL -D_MT -Xclang --dependent-lib=msvcrtd -MD -MT CMakeFiles/cmTC_65363.dir/testCXXCompiler.cxx.obj -MF CMakeFiles\cmTC_65363.dir\testCXXCompiler.cxx.obj.d -o CMakeFiles/cmTC_65363.dir/testCXXCompiler.cxx.obj -c C:/Users/David.Benson/ThirdParty/vcpkg/buildtrees/fmt/x64-windows-static-md-rel/CMakeFiles/CMakeScratch/TryCompile-twve2z/testCXXCompiler.cxx
CLANG_~1: error: no such file or directory: '/nologo'
CLANG_~1: error: no such file or directory: '/DWIN32'
CLANG_~1: error: no such file or directory: '/D_WINDOWS'
CLANG_~1: error: no such file or directory: '/W3'
CLANG_~1: error: no such file or directory: '/utf-8'
Console output:
C:\Users\David.Benson\ThirdParty\vcpkg>vcpkg install fmt --triplet x64-windows-static-md
Computing installation plan...
The following packages will be built and installed:
fmt:x64-windows-static-md -> 10.1.1
Detecting compiler hash for triplet x64-windows-static-md...
Restored 0 package(s) from C:\Users\David.Benson\AppData\Local\vcpkg\archives in 823 us. Use --debug to see more details.
Installing 1/1 fmt:x64-windows-static-md...
Building fmt:x64-windows-static-md...
warning: -- Using community triplet x64-windows-static-md. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: C:\Users\David.Benson\ThirdParty\vcpkg\triplets\community\x64-windows-static-md.cmake
-- Using cached fmtlib-fmt-10.1.1.tar.gz.
-- Cleaning sources at C:/Users/David.Benson/ThirdParty/vcpkg/buildtrees/fmt/src/10.1.1-281bbdd8af.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/Users/David.Benson/ThirdParty/vcpkg/downloads/fmtlib-fmt-10.1.1.tar.gz
-- Applying patch fix-write-batch.patch
-- Applying patch fix-format-conflict.patch
-- Using source at C:/Users/David.Benson/ThirdParty/vcpkg/buildtrees/fmt/src/10.1.1-281bbdd8af.clean
-- Found external ninja('1.11.0').
-- Configuring x64-windows-static-md
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
Command failed: "C:/Program Files (x86)/Microsoft Visual Studio/2022/BuildTools/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v
Working Directory: C:/Users/David.Benson/ThirdParty/vcpkg/buildtrees/fmt/x64-windows-static-md-rel/vcpkg-parallel-configure
Error code: 1
See logs for more information:
C:\Users\David.Benson\ThirdParty\vcpkg\buildtrees\fmt\config-x64-windows-static-md-dbg-CMakeCache.txt.log
C:\Users\David.Benson\ThirdParty\vcpkg\buildtrees\fmt\config-x64-windows-static-md-rel-CMakeCache.txt.log
C:\Users\David.Benson\ThirdParty\vcpkg\buildtrees\fmt\config-x64-windows-static-md-out.log
Call Stack (most recent call first):
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake:252 (vcpkg_execute_required_process)
ports/fmt/portfile.cmake:12 (vcpkg_cmake_configure)
scripts/ports.cmake:170 (include)
error: building fmt:x64-windows-static-md failed with: BUILD_FAILED
Elapsed time to handle fmt:x64-
config-x64-windows-static-md-out.log
windows-static-md: 36 s
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+fmt
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?title=[fmt]+Build+error+on+x64-windows-static-md&body=Copy+issue+body+from+C%3A%2FUsers%2FDavid.Benson%2FThirdParty%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md

You could consider using the link at the bottom of the message to submit an issue here. I believe the process behind that ensures that all relevant details are recorded to help the maintainers help you with the issue.

I am on 17.10.0 too, but I didn't repro it.

Open a Developer Command Prompt for VS2022 (or Powershell, same behavior)
cl (demonstrates that command is in path and has expected version)
./vcpkg install fmt --triplet x64-windows
BTW, the first 2 step is no need. Just run vcpkg install xxx

Deleting the vcpkg directory cleared the issue. Closing.

Deleting the vcpkg directory cleared the issue. Closing.

Delete the vcpkg directory in the vs2022 installation directory?

I fixed this issue with an old version of vcpkg by installing the 14.39 toolset via the Visual Studio Installer.


text:
netcdf-c reports the wrong cmake instructions

Describe the bug
Install netcdf-c
The following packages are already installed:
    netcdf-c[core]:x64-linux
Starting package 1/1: netcdf-c:x64-linux
Package netcdf-c:x64-linux is already installed
Elapsed time for package netcdf-c:x64-linux: 11.03 us

Total elapsed time: 20.57 us

The package netcdf-c:x64-linux provides CMake targets:

    find_package(netcdf-c CONFIG REQUIRED)
    target_link_libraries(main PRIVATE netcdf)

But the appropriate find_package command won't work because:
➜ find . -iname "*netcdf*" | grep cmake
./buildtrees/netcdf-c/x64-linux-dbg/CMakeFiles/Export/share/netcdf/netCDFTargets-debug.cmake
./buildtrees/netcdf-c/x64-linux-dbg/CMakeFiles/Export/share/netcdf/netCDFTargets.cmake
./buildtrees/netcdf-c/x64-linux-dbg/netCDFConfig.cmake
./buildtrees/netcdf-c/x64-linux-dbg/netCDF/netCDFConfigVersion.cmake
./buildtrees/netcdf-c/x64-linux-rel/CMakeFiles/Export/share/netcdf/netCDFTargets.cmake
./buildtrees/netcdf-c/x64-linux-rel/CMakeFiles/Export/share/netcdf/netCDFTargets-release.cmake
./buildtrees/netcdf-c/x64-linux-rel/netCDFConfig.cmake
./buildtrees/netcdf-c/x64-linux-rel/netCDF/netCDFConfigVersion.cmake
./buildtrees/netcdf-c/src/v4.7.0-378dd8d384/netCDFConfig.cmake.in
./buildtrees/netcdf-c/src/netcdf-c-4.4.1.1/netCDFConfig.cmake.in
./buildtrees/netcdf-cxx4/x64-linux-dbg/netCDF/netCDFCxxConfigVersion.cmake
./buildtrees/netcdf-cxx4/x64-linux-rel/netCDF/netCDFCxxConfigVersion.cmake
./packages/netcdf-c_x64-linux/share/netcdf-c/netCDFConfigVersion.cmake
./packages/netcdf-c_x64-linux/share/netcdf-c/netCDFConfig.cmake
./packages/netcdf-c_x64-linux/share/netcdf-c/netCDFTargets-debug.cmake
./packages/netcdf-c_x64-linux/share/netcdf-c/netCDFTargets.cmake
./packages/netcdf-c_x64-linux/share/netcdf-c/netCDFTargets-release.cmake
./installed/x64-linux/share/netcdf-c/netCDFConfigVersion.cmake
./installed/x64-linux/share/netcdf-c/netCDFConfig.cmake
./installed/x64-linux/share/netcdf-c/netCDFTargets-debug.cmake
./installed/x64-linux/share/netcdf-c/netCDFTargets.cmake
./installed/x64-linux/share/netcdf-c/netCDFTargets-release.cmake

Instead, these instructions work:
find_package(netCDF CONFIG REQUIRED)
target_link_libraries(main PRIVATE netcdf)

Environment

OS: linux (arch linux)
Compiler: clang 8.0.1, g++ 9.1.0

To Reproduce
Steps to reproduce the behavior:

./vcpkg install netcdf-c
See logs above

Expected behavior
I would expect the given cmake instructions to just work.

@lakinwecker, the PR has been merged, please get latest vcpkg and try again. Thanks for posting this issue!

authors: PhoebeHui lakinwecker


text:
[taskflow] update port to v2.7.0

Update taskflow to latest release v2.7.0

Awesome, thanks!


text:
[rlottie]: add new port

[x] Changes comply with the maintainer guide.
[x] The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
[x] Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx.
[x] The versioning scheme in vcpkg.json matches what upstream says.
[x] The license declaration in vcpkg.json matches what upstream says.
[x] The installed as the "copyright" file matches what upstream says.
[x] The source code of the component installed comes from an authoritative source.
[x] The generated "usage text" is accurate. See adding-usage for context.
[x] 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.

Network mistake from last night is fixed but there are unrelated failures here so I'm skipping rerunning this one.

/azp run

/Users/vcpkg/Data/b/rlottie/install-arm64-osx-dbg-out.log
Undefined symbols for architecture arm64:
  "_pixman_composite_over_n_8888_asm_neon", referenced from:
      color_SourceOver(unsigned int*, int, unsigned int, unsigned int) in librlottie.a[14](vdrawhelper_neon.cpp.o)
  "_pixman_composite_src_n_8888_asm_neon", referenced from:
      memfill32(unsigned int*, unsigned int, int) in librlottie.a[14](vdrawhelper_neon.cpp.o)
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

/mnt/vcpkg-ci/b/rlottie/install-arm-neon-android-dbg-out.log
ld.lld: error: undefined symbol: pixman_composite_src_n_8888_asm_neon
>>> referenced by vdrawhelper_neon.cpp:17 (/mnt/vcpkg-ci/b/rlottie/src/c864f89a82-832b1c6883.clean/src/vector/vdrawhelper_neon.cpp:17)
>>>               vdrawhelper_neon.cpp.o:(memfill32(unsigned int*, unsigned int, int)) in archive librlottie.a

ld.lld: error: undefined symbol: pixman_composite_over_n_8888_asm_neon
>>> referenced by vdrawhelper_neon.cpp:26 (/mnt/vcpkg-ci/b/rlottie/src/c864f89a82-832b1c6883.clean/src/vector/vdrawhelper_neon.cpp:26)
>>>               vdrawhelper_neon.cpp.o:(color_SourceOver(unsigned int*, int, unsigned int, unsigned int)) in archive librlottie.a
clang++: error: linker command failed with exit code 1 (use -v to see invocation)

All failure logs: https://dev.azure.com/vcpkg/public/_build/results?buildId=108151&view=artifacts&pathAsName=false&type=publishedArtifacts

@Cheney-W I also read the logs and looked for relevant solutions in the community and am trying to fix it.

The error also points to another particular porting problem: vendored dependencies.

@dg0yt The new patch seems to solve the problem with linking rlottie.expmap in CMake files using absolute paths, which is associated with pixman_composite_src_n_8888_asm_neon, pixman_composite_over_n_8888_asm_neon. This has now been replaced with the community solution and the library is no longer linked.
I think it's what you'd expect.

Only rapidjson can be separated from vendor dependencies...

pixman uses the version provided by Nokia for the arm platform, which is completely different from the port provided by vcpkg.

a number of changes have been made to the built-in freetype, including, but not limited to, types, function signatures, structures, and so on. Unless rlottie can rewrite it completely using the original freetype.

Usage test passed with x64-windows triplet.

pixman uses the version provided by Nokia for the arm platform, which is completely different from the port provided by vcpkg.

That implies what this port installs won't be link compatible with other things in the registry, which is a problem for including it.

a number of changes have been made to the built-in freetype, including, but not limited to, types, function signatures, structures, and so on. Unless rlottie can rewrite it completely using the original freetype.

This is similarly a problem :(

I'm also very keen to extract all the dependencies, I packaged rlottie with the intention of driving some new feature implementations in the rmlui project. (According to my practice, the freetype built into rlottie is actually an altered subset, symbol is no conflict).
If we want to fix this completely, the best thing I can think of is to fork the upstream repositories and then modify them specifically for vcpkg, since the amount of modification is not something that can be fixed with a series of patches. But there is the question of whether these changes are considered authoritative source.
I'm certainly willing to make some attempts, but it's not promising.

I've spent some time trying to understand its built-in freetype and have found two types of problems so far:

Older APIs or members used and removed in newer versions, no alternative found.
https://github.com/Samsung/rlottie/blob/e3026b1e1a516fff3c22d2b1b9f26ec864f89a82/src/vector/vraster.cpp#L102
https://github.com/Samsung/rlottie/blob/e3026b1e1a516fff3c22d2b1b9f26ec864f89a82/src/vector/vraster.cpp#L185
https://github.com/Samsung/rlottie/blob/e3026b1e1a516fff3c22d2b1b9f26ec864f89a82/src/vector/vraster.cpp#L356
Uses internal members from freetype and couples to vraster.
https://github.com/Samsung/rlottie/blob/e3026b1e1a516fff3c22d2b1b9f26ec864f89a82/src/vector/vraster.cpp#L369

Here is path to built-in freetype: src/vector/freetype
The built-in library mainly extracts stroke-related functions and differentiates them from the original symbols by starting all symbols with SW_.
Note that the built-in version is very old, and is only a very, very small part of it, mainly the implementation related to strokes. And pixman has actually been removed by me, I just forgot to remove the associated add_subdirectory code.

To add to that, here's a relevant quote from the rlottie creator: https://github.com/Samsung/rlottie/issues/420#issuecomment-683373922

rlottie dosen't keep a copy of the freetype , it only has the sandalone greyraster and stroker code . which compiles down to 20-30KB code against 1MB of freetype library. other reason is rlottie uses multi threaded renderer so we did some change to make it work for that. so it won't be straight forward do directly use the freetype and the library size reduction will not be that much.

This pipeline run failure seems to be due to internal reasons, how to retrigger it?

This pipeline run failure seems to be due to internal reasons, how to retrigger it?

git commit --allow-empty -m CI
git push

@SHIINASAMA My understanding is that you are still working around vendored dependencies. The thing that matters here is that someone can vcpkg install the-vendored-dependency rlottie, and the resulting installed bits need to not conflict with each other.
If/when you believe this problem is resolved, please feel free to un-draft this PR.

rlottie dosen't keep a copy of the freetype , it only has the sandalone greyraster and stroker code.

I believe the situation is clear enough. The developers of rlottie emphasize that this is not a copy of FreeType. The related vendor dependencies have been extracted and replaced with vcpkg ports.
I will un-draft this PR again.


text:
Error

Does this occur consistently? yes
Repro steps:

Action: appService.Deploy
Error type: 404
Error Message: 404 Web Site not found.
You may be seeing this error due to one of the reasons listed below :

Custom domain has not been configured inside Azure. See how to map an existing domain [redacted:url to resolve this.
Client cache is still pointing the domain to old IP address. Clear the cache by running the command ipconfig/flushdns.

Checkout App Service Domain FAQ [redacted:url for more questions.
Version: 0.24.8
OS: win32
OS Release: 10.0.19044
Product: Visual Studio Code
Product Version: 1.76.2
Language: en

Call Stack
new RestError extension.bundle.js:2:1709073
extension.bundle.js:2:1696547extension.bundle.js:2:1696547

Please add repro steps.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!

authors: AzCode-Bot kfarrukh nturinski

repo: microsoft/vscode-azureappservice


text:
Child/parent code lenses and label parent in dependsOn completions

Depends on https://github.com/microsoft/vscode-azurearmtools/pull/959
Fixes #943

@bhsubra Could you approve this one today?  thanks.

repo: microsoft/vscode-azurearmtools


text:
A11y_AzureExtensionsforVSCode_AzureFuction_DefaultScreen_Screenreader : Proper link text for controls such as "Visual studio ...", "installs ..." and "Azure pipelines ..." are not announced for screen reader users.

“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHub Tags:#A11y_Azure Extensions for VS Code;#Azure Tools for VS Code;#A11yTCS;#A11yMAS;#MAC;#FTP;#Benchmark;#Screenreader;#VoiceOver;#A11ySev1;#MAS1.3.1;#MAS4.1.2;#MAS1.1.1;
Environment Details:
Application Name: Azure Extensions for VS Code
Application Version: 1.48.0-insider
Commit: cfbd1999769f4f08dce29629fb92fdc0fac53829
Date: 2020-08-06T05:40:40.871Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.6.0
Operating system: macOS Catalina Version 10.15.6 (19G73)
Screen Reader: VoiceOver
MAS References: MAS1.3.1, MAS4.1.2, MAS1.1.1
Repro Steps:

Open Visual studio code
Click on extension button and search for "Azure Functions"
Click on install and move to the "Azure" button, the "Default Screen" will appear.
Start screen reader and navigate to controls such as controls such as "Visual studio ...", "installs ..." and "Azure pipelines ..." and observe if the visual text is announced or not.

Actual:
When screen reader users navigate to the controls such as controls such as "Visual studio marketplace v0.23.0", "installs 550.21k" and "Azure Pipelines failed" there visual text is not announced properly to the screen reader users which is incorrect. Since these controls are image links the alternative text provided should be descriptive for screen reader users.
Expected:
The controls such as "Visual studio marketplace v0.23.0", "installs 550.21k" and "Azure Pipelines failed" should be announced with the proper name as per its visual appearance on the screen for screen reader users when they navigate to these controls.
User Impact:
If proper name is not announced for the interactive elements on the screen content then the screen reader users will not understand how to interact with these control and this can lead to the confusion for screen reader users.
Attachment link for Reference:
2286_A11y_AzureExtensionsforVSCode_AzureFuction_DefaultScreen_Screenreader Proper link text for controls such as "Visual studio ...", "installs ..." and "Azure pipelines ..." are not announced for screen reader users.zip

Those are not necessary, so I just removed them.

Verified the bug in Visual Studio Code - Insiders application (Version: 1.50.0-insider) and Azure Functions (v0.24.0). The controls such as "Visual studio marketplace v0.23.0", "installs 550.21k" and "Azure Pipelines failed" are now no more available. Hence closing the bug. PFA

authors: EricJizbaMSFT MayuriNaik

repo: microsoft/vscode-azurefunctions


text:
An error occurs when deleting a file for the blob container or file share

OS: Win10
Build Version:  20220619.1
Regression: Previous release
Repro Steps:

Expand a storage account -> Create a blob container -> Create an empty blob.
Delete the above empty blob.
Check whether no error occurs.

Expect:
No error occurs.
Actual:
An error occurs.

More Info:

This issue also reproduces for the file share.
This issue also reproduces for the attached storage account and emulator account.

Does this issue still reproduce?

@alexweininger   Verified this issue with the latest build 20220630.3, it still reproduces now.

authors: alexweininger v-xinda

repo: microsoft/vscode-azurestorage


text:
Use "azure/core-http" to improve ECONNRESET handling

The azure sdks have a systemErrorRetryPolicy that's supposed to automatically retry a request for errors like "ECONNRESET". However, it had a bug where it never retried. I found a PR that fixed the bug in the "core-http" package a while ago, but not the "ms-rest-js" package we had been using. I filed a bug on "ms-rest-js" to get the fix ported over, but not sure when that'll happen and it sounds like "core-http" is the newer/better version of "ms-rest-js", anyways.
Only issue was some build errors around ServiceClientCredentials, but I mitigated that with AzExtServiceClientCredentials.
Related to https://github.com/microsoft/vscode-azurefunctions/issues/2390 and https://github.com/microsoft/vscode-azureappservice/issues/1932

ms-rest-js 2.2.1 has the fix we need for ECONNRESET, so we don't need to use core-http anymore (which only helped for genericClient anyways)
I decided to keep the changes for AzExtServiceClientCredentials because it lets us remove the explicit dependency on "ms-rest-nodeauth" and I have seen typescript errors related to the credentials before.

repo: microsoft/vscode-azuretools


text:
Workspace Button doesn't always show up

Brief Issue Summary
Workspace Button doesn't show up in Statusbar if a second directory is added to a workspace.
workaround
Reopen VS-Code after adding a second directory
Expected:
Workspace Button gets visible
Apparent Behavior:
Workspace Button is hidden.
Reproduction steps

create a new workspace (only one directory)
add a second directory to that workspace
check if the button is visible

Platform and Versions

Operating System:  Windows 10
CMake Version:  3.17.0
VSCode Version: 1.44.2
CMake Tools Extension Version:  0ee9aaf2c972ff231e332f72afc15d67d08abd72 1.3.1

Other Notes/Information
#1200

I am not able to reproduce the missing button. Your description is good and clear, I understand it. I tried several ways that could fit the above steps. Let's figure out if maybe a trigger factor is missing from the repro scenario.

i don't know what i did differently yesterday, but all 3 versions i tried it with work today. (dev/1.3.1/#1200)
i'll try to find the trigger as soon as i'm able to reproduce it myself again.

authors: SchweizS andreeis

repo: microsoft/vscode-cmake-tools


text:
The 'path' member of 'target' or 'source' could be relative

Fix #1504
Refer to https://cmake.org/cmake/help/git-stage/manual/cmake-file-api.7.html#codemodel-version-2-target-object.
The target path and source file path could be relative, so the convertToExtCodeModelFileGroup() must convert the paths to absolute first.

Rebased

@elsonwei, what is the reason for closing this PR?
We are catching up now with reviewing community contributions in CMake Tools.
I reviewed a similar one https://github.com/microsoft/vscode-cmake-tools/pull/1674 and at a first glance yours treats more similar scenarios and also adds tests. We are interested in looking at this more closely. Let us know why you closed it.

authors: andreeis elsonwei


text:
Missing/hidden quoted or wrapped text in co-pilot query response

Type: Bug
Ask Co-pilot any question on VSCode chat extension. Try to ask it something that requires it to put text into quotations or parenthesis. When the answer is generated, the text wrapped in ", ', (, {, [, ` chars displays as a solid white box where the text should be. The text is only made readable when the user selects the text as if to copy or cut it.
My exact query was: "Tak to me about ONL_FULL_GROUP_BY mode, why might someone want to use this in a production environment?"
Extension version: 0.16.0
VS Code version: Code 1.90.0 (89de5a8d4d6205e5b11647eb6a74844ca23d2573, 2024-06-04T19:33:54.889Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (8 x 2803)

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: enabled

Load (avg)
undefined

Memory (System)
15.80GB (1.69GB free)

Process Argv
--crash-reporter-id a445b7dd-0bd0-4ccc-be12-6b82b739ebd6

Screen Reader
no

VM
0%

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pythonmypyd1:30879173
pythoncet0:30885854
2e7ec940:31000449
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
jchc7451:31067544
chatpanelt:31048053
dsvsc021:30996838
f3je6385:31013174
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
pythonprt:31056678
dwnewjupyter:31046869
26j00206:31048877

@BrandonXZ did you use the panel chat or the inline chat widget for your query?

It occurs in the panel chat, even if its expanded in the editor space. Haven't seen it happening inline with code.

@BrandonXZ could you please share any sample prompts to help us repro this issue. Thanks.

issue resolved during previous update, can not reproduce at this point.

authors: BrandonXZ bhavyaus

repo: microsoft/vscode-copilot-release


text:
error al leer el archivo

Type: Bug
No se pudo realizar la solicitud. Notifique el siguiente id. de solicitud e inténtelo de nuevo
Extension version: 0.21.2
VS Code version: Code 1.94.0 (d78a74bcdfad14d5d3b1b782f87255d802b57511, 2024-10-02T13:08:12.626Z)
OS version: Linux x64 6.8.0-45-generic
Modes:

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (12 x 3897)

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: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_offwebnn: disabled_off

Load (avg)
2, 3, 3

Memory (System)
23.32GB (9.91GB free)

Process Argv
--crash-reporter-id f39c3b39-8fd1-4240-a5ef-0f9af498b092

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
wayland

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
da93g388:31013173
dvdeprecation:31068756
dwnewjupytercf:31046870
impr_priority:31102340
nativerepl1:31139838
refactort:31108082
pythonrstrctxt:31112756
wkspc-onlycs-t:31132770
wkspc-ranged-t:31151552
cf971741:31144450
autoexpandse:31146404
iacca2:31156134
notype1:31157159
5fd0e150:31155592
dwcopilotcf:31160501
iconenabled:31158251

There was a server side incident. It has since been resolved


text:
Github Copilot chat use reduced context

Type: Bug
Github Copilot chat only uses part of my python module as context while I ask it to modify the whole file. It has happened many times
Extension version: 0.22.3
VS Code version: Code 1.95.3 (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Linux x64 6.8.0-48-generic snap
Modes:

System Info

Item
Value

CPUs
13th Gen Intel(R) Core(TM) i7-13705H (20 x 400)

GPU Status
2d_canvas: unavailable_softwarecanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: disabled_softwaremultiple_raster_threads: enabled_onopengl: disabled_offrasterization: disabled_softwareraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: unavailable_softwarewebgl2: unavailable_softwarewebgpu: disabled_offwebnn: unavailable_software

Load (avg)
1, 1, 1

Memory (System)
31.09GB (13.82GB free)

Process Argv
--no-sandbox --force-user-env --crash-reporter-id 1c182ff3-4d96-4e37-a9e5-2be08f159692

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
x11

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
724cj586:31013169
dvdeprecation:31068756
dwnewjupyter:31046869
nativerepl1:31139838
pythonrstrctxt:31112756
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530

I can not reproduce this. Can you reproduce with latest version of VS Code Insiders and latest pre-release of Copilot Chat extension?
If yes, can you provide reproducible steps. Until then I will go ahead and close this issue.
Thank you for your understanding

authors: isidorn p-enel


text:
The default status of the function file is confused

OS: Win10/Mac
Build Version: 20200714.9
Repro steps:

Drill down a PostgreSQL server --> Database --> Functions.
Create a function --> Click the function.
Check the status of the opened file.

Expect:
The status of the opened file is saved.
Actual:
The status of the opened file is unsaved.

This is actually by-design.  Because the file is being pulled from Azure remotely, there is no local version of this file saved.  If the user wants to keep it locally, then they would have to save it (which is why we marked it as dirty).

authors: nturinski v-mengwe

repo: microsoft/vscode-cosmosdb


text:
Persist NVM cache

Image: mcr.microsoft.com/vscode/devcontainers/javascript-node:0.202.1-16-buster
Calling nvm install in my postCreateCommand causes a 22 MB download of the same Node.js archive on every container rebuild.
$ nvm cache dir
/usr/local/share/nvm/.cache

I see you're intentionally setting NVM_DIR=/usr/local/share/nvm, and I'm guessing there's probably a good reason for this. Nonetheless, it'd be great if I could persist this cache, ideally even by default, allowing users who want to clear it to nvm cache clear themselves.

@aaronadamsCA Yeah that's so that it works across users.  There's a nvm group and anyone in it gets access. The good news is you can actually do this by adding a volume mount into your devcontainer.json in the right spot.
"mounts": ["source=nvm-cache,target=/usr/local/share/nvm/.cache,type=volume"]

The dockerfile may need to su node -c 'mkdir -p /usr/local/share/nvm/.cache' so that it has the right user privs.
The downside of always doing this is that the volume will stick around even after you delete the container and, if you don't change the volume name, would be reused across containers.  Even docker system prune -a won't remove it... you need to do docker system prune -a --volumes. That's why it's not there by default at the moment.

@Chuxel Ia it precisely correct? The single-node Docker engine is not really multiuser because it has a single storage root and all artifacts are created under this root, including volumes with local driver. Podman, for example, is much more clever because every user has their own persistent root under $XDG_RUNTIME_DIR. All "Podman volumes" are private and can be used as a "private cache". All bind volumes can be used as a "Shared cache" but with big precautions.

FYI: for convinience Manage Podman volumes for remote users :)

@PavelSosin-320 nvm is just installed globally. Each user gets their own home. It gives you the option to run as root or vscode as you see fit. Not really related to PodMan or Docker at all.

@Chuxel The Docker's issue is exactly as you describe it: the docker volumes are not "owned" by the user, they are owned by the root, the Docker engine storage root owner. Every user has to manage his volumes, including bind volumes, even if the source dir is inside the user's home. In Podman volume prune by rootless user deletes user's volumes unused by the user's containers and makes them unavailable to anybody else.

@PavelSosin-320 This discussion is not about Podman vs Docker. This is off-topic. Please evangelize Podman in a different forum.

@Chuxel This is not about Podman vs Docker. This is about the redundancy between Podman and Dev Container features. In the case when Dev Container uses Podman as backend users will get a chance to config the same thing in 2 different places with conflicting results and doubled performance cost. It may surprise him.

I support the Feature request itself but the proposed solution looks problematic: today's Dokerfile spec allows to define volume mounts using VOLUME directive that ensures the existence of mount point inside the container and any configuration of components inside the container can safely reference this mount point. But mount's source depends on many things like OCI backend type, versions, volume persistence possibility, and supported features, like volume drivers ( plain plugins). If this part will be included in dev container definition it will make the definition hardly portable even between 2 Docker engines. I think that it would better to adhere to the OCI concept and separate volume persistence that is runtime option from the mount point definition that can be a part of the container image to achieve container consistency, exactly as defined today by OCI specs.

About implementaton: I suppose that every time when some tool that used cache it makes sense to create corresponding Docker VOLUME documentation in the image but it is completely in the developer's hands and not in VSCode and use it following documentation. The runtime source parameter depends on what developers have in their hands especially when talking about remote engine and the correct selection of backing FS may cost handreds of percents in performance gain/lost and it is not in the VSCode hands too. The cache on WSL disk will use ext4 FS that is very good and on the Windows FS means "P9 FS" and this is very bad. The mount tool used by the engine can vary too and this is in Engine configuration. WSL 2 Kernel supports FUSE adopted by the Docker and Podman as the best choice. Ability of sharing cache between users depends on the cache implementation and if the cache is created under Home directory by the default it is not sharable by design.

@aaronadamsCA , maybe, if you want to add some content to the image statically, like nodejs applications, then to root your problem completely the better approach is to use buildkit buildkit: it is already available to you, requires minimum changes in the projects under development and will provide expected performance gain. Anyway, everything added to the image becomes the image layer and caching of layer source is equivalent of the caching of layers.

authors: Chuxel PavelSosin-320 aaronadamsCA

repo: microsoft/vscode-dev-containers


text:
Lsp-sample building loop

Windows 11
Latest version of Vscode and nodejs
Latest version of typescript
When i try to start Client + server, tcs -b -w infinitly loop and my extension development host not open.  Also, if I put compile instead of watch in launch.json, I get this error when the extension development host open.
[vscode-samples.lsp-sample]: Cannot register 'languageServerExample.trace.server'. This property is already registered.

@frankgigeur I just tested this and I can't reproduce with a fresh clone of the vscode-extension-samples. Any additional information?

I have solved this problem. It consisted in the fact that you have your own extension installed. To avoid such errors, you need to disable your extension if you write the same one, for example, you want to improve it or roll back a new version of the extension.

Windows 11 Latest version of Vscode and nodejs Latest version of typescript
When i try to start Client + server, tcs -b -w infinitly loop and my extension development host not open. Also, if I put compile instead of watch in launch.json, I get this error when the extension development host open.
[vscode-samples.lsp-sample]: Cannot register 'languageServerExample.trace.server'. This property is already registered.

I have solved this problem. It consisted in the fact that you have your own extension installed. To avoid such errors, you need to disable your extension if you write the same one, for example, you want to improve it or roll back a new version of the extension.

Actually if you develop an extension and start it out of VS Code itself it will detect the case and disable the extension you have installed and use the one that runs out of source.
However if you for example copy an extension and don't rename the command ids (they are global in VS Code) then you will get conflicts on those.

authors: E5war5IT dbaeumer frankgigeur

repo: microsoft/vscode-extension-samples


text:
Broken LSP tests

1) VSCode Intellisense Notebook Diagnostics @lsp
       Add cells and make sure errors show up:

      Error: No diagnostics found for vscode-notebook-cell:/tmp/emptyPythonb54b6b0b-c35c-4ec0-b1d9-1d94a5a02ac1..ipynb#W1sZmlsZQ%3D%3D
      + expected - actual

      at Timeout.<anonymous> (src/test/common.ts:66:20)
      at listOnTimeout (node:internal/timers:559:17)
      at processTimers (node:internal/timers:502:7)

  2) VSCode Intellisense Notebook Hover @lsp
       Insert cell and get hover text:

      Error: No hovers found for vscode-notebook-cell:/tmp/emptyPython535824fb-a443-440a-a00e-fb17e3aa8959..ipynb#W1sZmlsZQ%3D%3D
      + expected - actual

      at Timeout.<anonymous> (src/test/common.ts:66:20)
      at listOnTimeout (node:internal/timers:559:17)
      at processTimers (node:internal/timers:502:7)

  3) VSCode semantic token tests @lsp
       Open a notebook and add a bunch of cells:

      TypeError: Cannot read properties of undefined (reading 'startOffset')
      + expected - actual

Closing, as these will be removed.

repo: microsoft/vscode-jupyter


text:
Installer for modules does not surface any errors when checking for if a module is installed

See this bug here:
https://github.com/microsoft/vscode-python/issues/13837
Makes it impossible for a user to diagnose a problem

I believe (based on reading that other issue), @DonJayamanne  has solved this problem. We parse output from the installer and show the user what the problem might be.


text:
Escape unconditionally remove all cursors, selection and focuses cell

Environment data

VS Code version: 1.51.1
Jupyter Extension version: v2020.11.372831992
Python Extension version: v2020.11.371526539
OS: Windows 10 2004
Python and/or Anaconda version: 3.8

Expected behaviour
When pressing Escape while multiple cursors or selection are active, I expect it to return to a single cursor. This is the normal behavior in VSCode.
Rebinding notebook.cell.quitEdit or changing it's 'when' criteria should be possible
Actual behaviour
When pressing ESC while multiple cursors or selection are active, all cursors are lost and the cell is focused. Up/down/home/end moves between cells instead of moving the cursor).
Removing Escape keybinding (notebook.cell.quitEdit) from shortcuts has no effect.
Steps to reproduce:
Create Jupyter notebook. Create 1 or more cells. Edit code in cell, Activate multiple cursors either by Ctrl+D og Ctrl+Alt+Ctrl+Arrow keys. Press Escape to return to single-cursor mode or remove selection.
Removing the Escape keyboard shortcut has no effect. Escape still stop editing and selects the cell.
    {
        "key": "escape",
        "command": "-notebook.cell.quitEdit",
        "when": "inputFocus && notebookEditorFocused && !editorHasSelection && !editorHoverVisible"
    }

Hi @larsch, I am unable to repro this issue at this time. Could you provide a gif showing us what you are seeing? If you need a tool ScreenToGif works pretty well (https://www.screentogif.com/)
Could you also provide us with the VS Code version you are using?

@claudiaregio Updated issue with Code version. Here's demo:

Thanks for the additional info. (This is only reproduced in stable, not insiders)

Thanks for your feedback. This issue will be addressed once VS Code adds native support for editing notebooks. Please see https://github.com/microsoft/vscode/issues/91987. You can experiment by using VS Code insiders, which defaults to the new notebook experience.

authors: claudiaregio greazer larsch


text:
Too much whitespace between text

Environment data

VS Code version: 1.54.3
Jupyter Extension version: v2021.3.619093157
Python Extension version: v2021.3.658691958
OS and version: Windows 10, Build 19041
Python version: Python 3.9.1
Type of virtual environment: venv
Jupyter server running: Local

Expected behaviour
I would expect the header text to be closer to the content it belongs to; the content below. This is how we are used to seeing it in Jupyter lab.

Notice how the rendered header is closer to the paragraph text below than the cell above.
Actual behaviour
And this is how the same notebook looks in VS Code:

In VS Code, the rendered text cells have an extra line above which contains the "Change to code" and "Delete cell" button when the cell is hovered on. This adds some extra whitespace.
The problem is that there is so much whitespace that the header is closer to the cell above than the content it belongs to below; the paragraph. This can be confusing. The same huge whitespace exists between all rendered text.

@Sti2nd Currently we are in the process of moving over to a new notebook UI provided by visual studio. Could you try downloading vs code insiders (it can install safely SxS with vscode stable) and opening the notebook there? This is the how the new UI will look and we won't be going back to fix issues like this with the old views.

Thanks for your feedback. This issue will be addressed once VS Code adds native support for editing notebooks. Please see https://github.com/microsoft/vscode/issues/91987. You can experiment by using VS Code insiders, which defaults to the new notebook experience.

authors: IanMatthewHuff Sti2nd greazer


text:
Extension issue

Issue Type: Bug
Extension Name: jupyter
Extension Version: 2021.8.1054968649
OS Version: Windows_NT x64 10.0.19042
VS Code version: 1.58.2

:warning: We have written the needed data into your clipboard. Please paste! :warning:

Sorry but this isn't enough information to do anything about the problem. What issue are you seeing? Do you have any output in your 'jupyter' output tab?

Your version of VS code is also out of date. The latest is 1.59.

authors: CodeAinz rchiodo


text:
Provide the "globalStorageUri" field

I need globalStorageUri value as the root path of the cache, and I use connection.sendRequest to get it, so I can only initialize it in connection.onInitialized
  connection.onInitialized(async () => {
    await fileCache.ready(connection);
  });

...
    async ready(connection) {
      const uri = await connection.sendRequest(
        VSCodeStorageRequest.GLOBAL_STORAGE_URI
      );
      const globalStorageUri = URI.parse(uri);

      const cacheLocation = join(globalStorageUri.fsPath, "file-cache");
      await mkdir(cacheLocation, { recursive: true });
    },

But  connection.onCompletion starts working before cache initialization was complete.
Is it possible to prevent other methods from working until onInitialized is done, or provide globalStorageUri so that it can initialize my cache utils in connection.onInitialize?

You can put an object as LanguageClientOptions.initializationOptions, it will be in the first argument to the onInitialize event.
https://github.com/microsoft/vscode-languageserver-node/blob/4ee380e66e9d4c0ac64bd84080f723e770c05b25/testbed/client/src/extension.ts#L34
https://github.com/microsoft/vscode-languageserver-node/blob/c53b35e114c9781c60c5a60981045baa677fa311/server/src/common/server.ts#L994
Better to do the join() on the client side instead of in the LSP :)

repo: microsoft/vscode-languageserver-node

license: mit

license_source: bigquery


text:
Docstring not working in Python

Type: Bug
codes:
def function(a: str, b: bool, c: int):
''' the function doc string.
Here is a bit more.
args:
    a:  a random string goes here
    b:  lets describe something binary
    c:  we have a whole number

return:
    gives something back

'''

When hovering over the function definition in VS Code, the description is formatted correctly.
If the type is wrapped in parentheses after the parameter, the description will appear on the one line
def function(a: str, b: bool, c: int):
''' the function doc string.
Here is a bit more.
args:
    a(str):  a random string goes here
    b(bool):  lets describe something binary
    c(int):  we have a whole number

return:
    gives something back

'''

The same issue has been closed in Microsoft/vscode, they believe it is an issue with vscode-Python.
VS Code version: Code 1.78 (https://github.com/microsoft/vscode/commit/5e805b79fcb6ba4c2d23712967df89a089da575b, 2023-03-08T16:32:00.131Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

Related on Stack Overflow: docstring not working in Python on VS Code

repo: microsoft/vscode-python


text:
When debugging a pytest unittest in VSCode, the python debugger detaches after ~60s, and I can't find an overriding timeout setting

Type: Bug

Behaviour
Expected vs. Actual
Expected
When debugging a pytest unittest using the inline right-click debug from a specific test, I can debug for as long as I want; i.e., the debugger stays connected and breaks on breakpoints, etc., without timing out, OR the extension allows me to set a timeout for as long as I want.
Actual
The debugger times out and disconnects after 60 seconds, and I can't seem to find any setting to increase the timeout.
Steps to reproduce:

Set a break point in a pytest unittest in VSCode. Here is the test I am using, with a breakpoint on the 'print(...' line:

def test_set_breakpoint_and_watch_test_timeout():
    """dummy test"""
    print("This test does nothing.")

Right-click on the green "Play" button next to the name of the unittest in the left gutter of the VSCode editor.
Select "Debug Test".
The debugger should break on the breakpoint
Wait for ~70 secs.

Expected
The debugger stays attached and I can keep debugging -- viewing variable data, stepping through code, etc.
Actual
The debugger detatches after ~60s and reports the following error (full DEBUG CONSOLE output below):
...
...
            self.process_internal_commands()
>           time.sleep(0.01)
E           Failed: Timeout >60.0s

../../.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/pydevd.py:2106: Failed
=========================== short test summary info ============================
FAILED tests/operations/test_sequence_to_helm.py::test_set_breakpoint_and_watch_test_timeout
========================= 1 failed in 61.99s (0:01:01) =========================

Diagnostic data

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

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

OUTPUT - Python
2023-08-07 11:59:40.858 [info] Running PYTEST execution for the following test ids: tests/operations/test_sequence_to_helm.py::test_set_breakpoint_and_watch_test_timeout
2023-08-07 11:59:40.858 [info] Server listening on port 37781
2023-08-07 11:59:40.858 [info] Running DEBUG pytest with arguments: --rootdir /home/hawk/projects/cdd_peptide_reg --capture no

2023-08-07 11:59:40.860 [info] Using launch configuration in launch.json file.
2023-08-07 11:59:41.352 [info] DAP Server launched with command: /home/hawk/projects/cdd_peptide_reg/conenv/bin/python /home/hawk/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/adapter
2023-08-07 12:00:44.798 [info] Test server connected to a client.
2023-08-07 12:00:45.596 [info] Client disconnected

DEBUG CONSOLE OUTPUT

CLIENT: Server listening on port 37781...
Received JSON data: ['tests/operations/test_sequence_to_helm.py::test_set_breakpoint_and_watch_test_timeout']
============================= test session starts ==============================
platform linux -- Python 3.9.7, pytest-7.1.2, pluggy-1.0.0
rootdir: /home/hawk/projects/cdd_peptide_reg, configfile: pyproject.toml
plugins: forked-1.3.0, asyncio-0.15.1, cov-3.0.0, datadir-1.4.1, pytest_check-1.0.4, xdist-2.5.0, timeout-1.4.2, anyio-3.5.0
timeout: 60.0s
timeout method: signal
timeout func_only: False
collected 1 item

tests/operations/test_sequence_to_helm.py

~~~~~~~~~~~~~~~~~~~~~ Stack of <unknown> (140534510081600) ~~~~~~~~~~~~~~~~~~~~~
  File "/home/hawk/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydev_bundle/pydev_monkey.py", line 1118, in __call__
    ret = self.original_func(*self.args, **self.kwargs)
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/threading.py", line 930, in _bootstrap
    self._bootstrap_inner()
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/threading.py", line 973, in _bootstrap_inner
    self.run()
  File "/home/hawk/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_daemon_thread.py", line 49, in run
    self._on_run()
  File "/home/hawk/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_timeout.py", line 43, in _on_run
    self._event.wait(wait_time)
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/threading.py", line 574, in wait
    signaled = self._cond.wait(timeout)
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/threading.py", line 312, in wait
    waiter.acquire()

~~~~~~~~~~~~~~~~~~~~~ Stack of <unknown> (140534518474304) ~~~~~~~~~~~~~~~~~~~~~
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/threading.py", line 930, in _bootstrap
    self._bootstrap_inner()
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/threading.py", line 973, in _bootstrap_inner
    self.run()
  File "/home/hawk/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_daemon_thread.py", line 49, in run
    self._on_run()
  File "/home/hawk/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/pydevd.py", line 261, in _on_run
    self._wait_event.wait(0.3)
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/threading.py", line 574, in wait
    signaled = self._cond.wait(timeout)
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/threading.py", line 316, in wait
    gotit = waiter.acquire(True, timeout)

~~~~~~~~~~~~~~~~~~~~~ Stack of <unknown> (140534526867008) ~~~~~~~~~~~~~~~~~~~~~
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/threading.py", line 930, in _bootstrap
    self._bootstrap_inner()
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/threading.py", line 973, in _bootstrap_inner
    self.run()
  File "/home/hawk/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_daemon_thread.py", line 49, in run
    self._on_run()
  File "/home/hawk/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/pydevd.py", line 215, in _on_run
    self._py_db_command_thread_event.wait(0.3)
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/threading.py", line 574, in wait
    signaled = self._cond.wait(timeout)
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/threading.py", line 316, in wait
    gotit = waiter.acquire(True, timeout)

~~~~~~~~~~~~~~~~~~~~~ Stack of <unknown> (140534536046144) ~~~~~~~~~~~~~~~~~~~~~
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/threading.py", line 930, in _bootstrap
    self._bootstrap_inner()
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/threading.py", line 973, in _bootstrap_inner
    self.run()
  File "/home/hawk/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_daemon_thread.py", line 49, in run
    self._on_run()
  File "/home/hawk/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_comm.py", line 222, in _on_run
    line = self._read_line()
  File "/home/hawk/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_comm.py", line 204, in _read_line
    r = self.sock.recv(1024)

~~~~~~~~~~~~~~~~~~~~~ Stack of <unknown> (140534544438848) ~~~~~~~~~~~~~~~~~~~~~
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/threading.py", line 930, in _bootstrap
    self._bootstrap_inner()
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/threading.py", line 973, in _bootstrap_inner
    self.run()
  File "/home/hawk/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_daemon_thread.py", line 49, in run
    self._on_run()
  File "/home/hawk/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_comm.py", line 368, in _on_run
    cmd = self._cmd_queue.get(True, 0.1)
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/queue.py", line 180, in get
    self.not_empty.wait(remaining)
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/threading.py", line 316, in wait
    gotit = waiter.acquire(True, timeout)
<class 'Failed'> raised from within the callback set in sys.settrace.
Debugging will be disabled for this thread (<_MainThread(MainThread, started 140534571606976)>).
Traceback (most recent call last):
  File "/home/hawk/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_frame.py", line 988, in trace_dispatch
    self.do_wait_suspend(thread, frame, event, arg)
  File "/home/hawk/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_frame.py", line 165, in do_wait_suspend
    self._args[0].do_wait_suspend(*args, **kwargs)
  File "/home/hawk/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/pydevd.py", line 2070, in do_wait_suspend
    keep_suspended = self._do_wait_suspend(thread, frame, event, arg, suspend_type, from_this_thread, frames_tracker)
  File "/home/hawk/.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/pydevd.py", line 2106, in _do_wait_suspend
    time.sleep(0.01)
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/site-packages/pytest_timeout.py", line 200, in handler
    timeout_sigalrm(item, params.timeout)
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/site-packages/pytest_timeout.py", line 375, in timeout_sigalrm
    pytest.fail("Timeout >%ss" % timeout)
  File "/home/hawk/projects/cdd_peptide_reg/conenv/lib/python3.9/site-packages/_pytest/outcomes.py", line 196, in fail
    raise Failed(msg=reason, pytrace=pytrace)
Failed: Timeout >60.0s
Fpytest session has finished, exit status:  ExitCode.TESTS_FAILED in discovery?  False

=================================== FAILURES ===================================
__________________ test_set_breakpoint_and_watch_test_timeout __________________

    def test_set_breakpoint_and_watch_test_timeout():
        """dummy test"""
>       print("This test does nothing.")
tests/operations/test_sequence_to_helm.py:530:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
tests/operations/test_sequence_to_helm.py:530: in test_set_breakpoint_and_watch_test_timeout
    print("This test does nothing.")
../../.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_frame.py:988: in trace_dispatch
    self.do_wait_suspend(thread, frame, event, arg)
../../.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_frame.py:165: in do_wait_suspend
    self._args[0].do_wait_suspend(*args, **kwargs)
../../.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/pydevd.py:2070: in do_wait_suspend
    keep_suspended = self._do_wait_suspend(thread, frame, event, arg, suspend_type, from_this_thread, frames_tracker)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

self = <pydevd.PyDB object at 0x7fd0bf9ba2e0>
thread = <_MainThread(MainThread, started 140534571606976)>
frame = <frame at 0x7fd0a1d97040, file '/home/hawk/projects/cdd_peptide_reg/tests/operations/test_sequence_to_helm.py', line 530, code test_set_breakpoint_and_watch_test_timeout>
event = 'line', arg = None, suspend_type = 'trace', from_this_thread = []
frames_tracker = <_pydevd_bundle.pydevd_suspended_frames._FramesTracker object at 0x7fd0a1d94be0>
    def _do_wait_suspend(self, thread, frame, event, arg, suspend_type, from_this_thread, frames_tracker):
        info = thread.additional_info
        info.step_in_initial_location = None
        keep_suspended = False

        with self._main_lock:  # Use lock to check if suspended state changed
            activate_gui = info.pydev_state == STATE_SUSPEND and not self.pydb_disposed
        in_main_thread = is_current_thread_main_thread()
        if activate_gui and in_main_thread:
            # before every stop check if matplotlib modules were imported inside script code
            # or some GUI event loop needs to be activated
            self._activate_gui_if_needed()

        while True:
            with self._main_lock:  # Use lock to check if suspended state changed
                if info.pydev_state != STATE_SUSPEND or (self.pydb_disposed and not self.terminate_requested):
                    # Note: we can't exit here if terminate was requested while a breakpoint was hit.
                    break
            if in_main_thread and self.gui_in_use:
                # call input hooks if only GUI is in use
                self._call_input_hook()

            self.process_internal_commands()
>           time.sleep(0.01)
E           Failed: Timeout >60.0s

../../.vscode-server/extensions/ms-python.python-2023.14.0/pythonFiles/lib/python/debugpy/_vendored/pydevd/pydevd.py:2106: Failed
=========================== short test summary info ============================
FAILED tests/operations/test_sequence_to_helm.py::test_set_breakpoint_and_watch_test_timeout
========================= 1 failed in 61.58s (0:01:01) =========================

User Settings

languageServer: "Pylance"

linting
• pylintArgs: "<placeholder>"

testing
• pytestEnabled: true

terminal
• activateEnvironment: false

Extension version: 2023.14.0
VS Code version: Code 1.81.0 (6445d93c81ebe42c4cbd7a60712e0b17d9463e97, 2023-08-02T12:37:13.485Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Remote OS version: Linux x64 5.4.72-microsoft-standard-WSL2

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8365U CPU @ 1.60GHz (8 x 1896)

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

Load (avg)
undefined

Memory (System)
15.81GB (2.46GB free)

Process Argv
--file-uri=vscode-remote://wsl+Ubuntu/home/hawk/projects/cdd_peptide_reg/registration.code-workspace --remote=wsl+Ubuntu --crash-reporter-id ea39c7bc-9acf-4ab0-a8de-b9cec0c6fcb0

Screen Reader
no

VM
0%

Item
Value

Remote
WSL: Ubuntu

OS
Linux x64 5.4.72-microsoft-standard-WSL2

CPUs
Intel(R) Core(TM) i5-8365U CPU @ 1.60GHz (4 x 1896)

Memory (System)
3.84GB (2.96GB free)

VM
0%

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
py29gd2263:30792226
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vscccc:30803845
3biah626:30602489
f6dab269:30613381
vscrp:30673768
showlangstatbar:30737416
vsctsb:30748421
a2ce3375:30757347
pythonfmttext:30731395
pythoncmvfstrcf:30756944
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
gsofa:30804715
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
e537b577:30795824
dsvsc013:30795093
dsvsc014:30804076

Here is my launch.json:
{
    // Use IntelliSense to learn about possible attributes.
    // Hover to view descriptions of existing attributes.
    // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
    "version": "0.2.0",
    "configurations": [
        {
            "name": "Python: FastAPI",
            "type": "python",
            "preLaunchTask": "create_db",
            "request": "launch",
            "module": "uvicorn",
            "justMyCode": false,
            "args": [
                "xxxxx_fastapi_app_xxxxx",
                "--reload"
            ],
            "jinja": true
        },
        {
            "name": "Python: Current File",
            "type": "python",
            "request": "launch",
            "program": "${file}",
            "console": "integratedTerminal",
            "justMyCode": false,
        },
        {
            "type": "pwa-node",
            "request": "launch",
            "name": "Temp JS Debugger",
            "skipFiles": [
                "<node_internals>/**"
            ],
            "program": "/xxx/path/to/file/xxxx/TempDebugger.js",
            "__workspaceFolder": "/home/path/to/folder/xxxx"
        },
    ]
}


text:
vscode_pytest not being invoked

Type: Bug
In my laptop, this is the command that runs when I click on the 'run tests' button in the UI. This is bad because I can't see the progress the full execution, seeing which tests pass. Instead, I have to wait until all of them have run
Running tests (pytest): /Users/xoel/CODE/theirstack/FindMeGigs/test/input/marketing/test_technologies.py
Running test with arguments: --rootdir /Users/xoel/CODE/theirstack/FindMeGigs --override-ini junit_family=xunit1 --junit-xml=/var/folders/9b/2b5zsyfj0632xhdhq9pnvdcc0000gn/T/tmp-26638HX64cb2yDPhC.xml -c pytest.ini ./test/input/marketing/test_technologies.py
Current working directory: /Users/xoel/CODE/theirstack/FindMeGigs
Workspace directory: /Users/xoel/CODE/theirstack/FindMeGigs
Run completed, parsing output

But in my cofounder's laptop, when doing the same, what's being called is different. This is the full command
Received JSON data in run script
Running pytest with args: ['-p', 'vscode_pytest', '-c', 'pytest.ini', '--rootdir=/Users/cp/Documents/workspace/FindMeGigs', '/Users/cp/Documents/workspace/FindMeGigs/test/input/marketing/test_technologies.py::test_technology_slugs', '/Users/cp/Documents/workspace/FindMeGigs/test/input/marketing/test_technologies.py::test_technology_category_slugs', '/Users/cp/Documents/workspace/FindMeGigs/test/input/marketing/test_technologies.py::test_get_company_count_per_country', '/Users/cp/Documents/workspace/FindMeGigs/test/input/marketing/test_technologies.py::test_get_company_count_per_country_france', '/Users/cp/Documents/workspace/FindMeGigs/test/input/marketing/test_technologies.py::test_categories_list', '/Users/cp/Documents/workspace/FindMeGigs/test/input/marketing/test_technologies.py::test_companies_by_technology']
============================= test session starts ==============================
platform darwin -- Python 3.11.5, pytest-8.3.2, pluggy-1.5.0
rootdir: /Users/cp/Documents/workspace/FindMeGigs
configfile: pytest.ini
plugins: asyncio-0.23.8, cov-5.0.0, env-1.1.3, anyio-4.4.0, profiling-1.7.0, split-0.9.0, xdist-3.6.1
asyncio: mode=Mode.AUTO
collected 6 items

test/input/marketing/test_technologies.py ......                         [100%]

=============================== warnings summary ===============================
.e/lib/python3.11/site-packages/passlib/utils/__init__.py:854
  /Users/cp/Documents/workspace/FindMeGigs/.e/lib/python3.11/site-packages/passlib/utils/__init__.py:854: DeprecationWarning: 'crypt' is deprecated and slated for removal in Python 3.13
    from crypt import crypt as _crypt

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
========================= 6 passed, 1 warning in 1.06s =========================
Finished running tests!

And this is what he sees on his screen

I see this happened to other users, example here
How can I get VSCode to invoke pytest the way it's done on my mate's laptop? It's much more convenient to see tests passing as they do instead of having to wait until all of them have run. Seems like vscode_pytets is not being run on my laptop while it's beeing run on his.
I've tried several versions of vscode_python and that didn't work either. Also trying on VSCode and Cursor and getting the same results on both. Also, both of us are on the last version of the vscode-python extension (2024.12.3)
This is our settings.py file:
{
    "python.testing.unittestEnabled": false,
    "python.testing.pytestEnabled": true,
    "python.analysis.typeCheckingMode": "basic",
    "python.testing.pytestArgs": [
        "-c",
        "pytest.ini"
    ],
    "[python]": {
        "editor.defaultFormatter": "charliermarsh.ruff"
    },
    "python.defaultInterpreterPath": "${workspaceFolder}/.e/bin/python",
    "ruff.interpreter": [
        "${workspaceFolder}/.e/bin/python"
    ],
    "editor.codeActionsOnSave": {
        "source.organizeImports": "explicit",
        "source.removeUnusedImports": "explicit",
        "source.fixAll": "always"
    },
    "editor.formatOnSave": true,
    "files.autoSaveDelay": 0,
    "python.terminal.activateEnvInCurrentTerminal": true,
}

And this is the list of the extensions I have installed:
adamvoss.vscode-languagetool@3.8.0
anysphere.pyright@1.1.327
charliermarsh.ruff@2024.50.0
donjayamanne.python-environment-manager@1.2.4
donjayamanne.python-extension-pack@1.7.0
eamodio.gitlens@15.5.1
github.copilot@1.235.0
github.copilot-chat@0.17.1
github.vscode-github-actions@0.27.0
hyzeta.vscode-theme-github-light@7.14.2
integromat.apps-sdk@2.0.0
janisdd.vscode-edit-csv@0.10.0
magicstack.magicpython@1.1.0
matangover.mypy@0.4.0
mechatroner.rainbow-csv@3.12.0
meezilla.json@0.1.2
mikestead.dotenv@1.0.1
ms-python.debugpy@2024.6.0
ms-python.isort@2023.10.1
ms-python.python@2024.12.3
ms-python.vscode-pylance@2024.8.1
ms-toolsai.datawrangler@1.10.0
ms-toolsai.jupyter@2024.6.0
ms-toolsai.jupyter-keymap@1.1.2
ms-toolsai.jupyter-renderers@1.0.19
ms-toolsai.vscode-jupyter-cell-tags@0.1.9
ms-toolsai.vscode-jupyter-slideshow@0.1.6
ms-vscode.js-debug-nightly@2024.10.417
sissel.shopify-liquid@4.0.1
sonarsource.sonarlint-vscode@4.11.0
supermaven.supermaven@1.1.12
telesoho.vscode-markdown-paste-image@1.1.2
tinybirdco.vscode-tinybird-support@1.0.3
vincaslt.highlight-matching-tag@0.11.0
visualstudioexptteam.intellicode-api-usage-examples@0.2.8
visualstudioexptteam.vscodeintellicode@1.3.1
wholroyd.jinja@0.0.8
wyattferguson.jinja2-snippet-kit@2.0.0
yzhang.markdown-all-in-one@3.6.2
zainchen.json@2.0.2

Extension version: 2024.16.0
VS Code version: Code 1.94.0 (d78a74bcdfad14d5d3b1b782f87255d802b57511, 2024-10-02T13:08:12.626Z)
OS version: Darwin arm64 23.6.0
Modes:

System Info

Item
Value

CPUs
Apple M1 (8 x 2400)

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: enabledwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
17, 16, 16

Memory (System)
16.00GB (0.02GB free)

Process Argv
--crash-reporter-id c05df5ab-3ca1-48a8-b61f-0924978c0ce4

Screen Reader
no

VM
0%

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
f3je6385:31013174
a69g1124:31058053
dvdeprecation:31068756
dwnewjupytercf:31046870
impr_priority:31102340
nativerepl2:31139839
refactort:31108082
pythonrstrctxt:31112756
flighttreat:31134774
wkspc-onlycs-t:31132770
wkspc-ranged-t:31151552
cf971741:31144450
autoexpandse:31146404
iacca1:31150322
5fd0e150:31146321

Hi! From your logs it looks like you aren't on the testing rewrite which is required. Could you update to our rewrite and try again? You can do so adding this setting to your users settings.json "python.experiments.optInto": ["pythonTestAdapter"]. Then you can confirm its enabled by finding Experiment 'pythonTestAdapter' is active in your python logs. If you are unable to see the log for the experiment change your log level to trace and it should show up.
To set to trace use theDeveloper: set log level command in the command palette. Thanks

authors: eleanorjboyd xoelop


text:
Automatically associate .flake8 files as an ini file

Currently I have to add this to my project so that .flake8 is considered an INI-file.
  "files.associations": {
    ".flake8": "ini"
  },

It would be cool if VS Code could add this into the extension instead so that one does not have to configure it.

Should be simple as per https://github.com/microsoft/vscode-eslint/commit/4d8d1469c2d668b9c897c4a262b0717421c1d1f5

@DonJayamanne I can fix this if you want me to, but the label "needs decision" makes me wonder if you want it fixed?

We're waiting to decide (team decision) whether we need such an enhancement.
If we get the green light I'll let you know here so you can create a PR.
My vite is to go with this change and add support for other similar files.

We change the label to "needs PR", so if anyone wants to submit a PR for this we'll be happy to review it :)

@luabud @karthiknadig You can maybe close this now, I fixed it and it has been merged :)
See https://github.com/microsoft/vscode-python/pull/7739

@thernstig thanks for reminding us to close this, and again, thanks for the PR! 😊

authors: DonJayamanne luabud thernstig


text:
Please add syntax parsing for the internal terminal display, which can be customized by users

Like sublime terminal display. reference console.sublime-syntax:
%YAML 1.2
name: console
hidden: true
scope: source.build_output
contexts:
main:
# for gnu gcc.
- match: '^(..[^:\n]*):([0-9]+):?([0-9]+)?:? '
scope: entity.name.filename
- match: '\b(warning|error): '
scope: message.error
# for ti gcc.
- match: '^\"(.*?)\", line ([0-9]*):'
  scope: entity.name.filename
- match: '(.*)\.out'
  scope: entity.name.filename
- match: '(.*)\.lib'
  scope: entity.name.filename
- match: '\b(warning|error) #[0-9]+(-D){0,1}:'
  scope: message.error
- match: '\bfailed'
  scope: message.error

- match: '\b[eE]rror[ !]'
  scope: message.error

- match: '^\[.+\]$'
  scope: comment

The process running within the terminal is in control of colors.

authors: Anders-Zhang-Github Tyriar

repo: microsoft/vscode