text:
[ICU] build failure

Operating system
Windows
Compiler
MSVC
Steps to reproduce the behavior
vcpkg install icu

Failure logs
C:\vcpkg>vcpkg install icu
warning: The vcpkg C:\vcpkg\vcpkg.exe is using detected vcpkg root C:\vcpkg and ignoring mismatched VCPKG_ROOT environment value C:\software\tools\vcpkg. To suppress this message, unset the environment variable or use the --vcpkg-root command line switch.
warning: In the September 2023 release, the default triplet for vcpkg libraries changed from x86-windows to the detected host triplet (x64-windows). For the old behavior, add --triplet x86-windows . To suppress this message, add --triplet x64-windows .
Computing installation plan...
The following packages will be built and installed:
icu[core,tools]:x64-windows -> 73.1
Detecting compiler hash for triplet x64-windows...
Restored 0 package(s) from C:\Users\heimann\AppData\Local\vcpkg\archives in 287 us. Use --debug to see more details.
Installing 1/1 icu:x64-windows...
Building icu[core,tools]:x64-windows...
-- Using cached icu4c-73_1-src.tgz.
-- Cleaning sources at C:/vcpkg/buildtrees/icu/src/c-73_1-src-3575e21c7c.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source C:/vcpkg/downloads/icu4c-73_1-src.tgz
-- Applying patch disable-escapestr-tool.patch
-- Applying patch remove-MD-from-configure.patch
-- Applying patch fix_parallel_build_on_windows.patch
-- Applying patch fix-extra.patch
-- Applying patch mingw-dll-install.patch
-- Applying patch disable-static-prefix.patch
-- Applying patch fix-win-build.patch
-- Using source at C:/vcpkg/buildtrees/icu/src/c-73_1-src-3575e21c7c.clean
-- Found external ninja('1.10.2').
-- Getting CMake variables for x64-windows
-- Using cached msys2-autoconf-wrapper-20221207-1-any.pkg.tar.zst.
-- Using cached msys2-automake-wrapper-20221207-1-any.pkg.tar.zst.
-- Using cached msys2-binutils-2.40-1-x86_64.pkg.tar.zst.
-- Using cached msys2-libtool-2.4.7-3-x86_64.pkg.tar.zst.
-- Using cached msys2-make-4.4.1-1-x86_64.pkg.tar.zst.
-- Using cached msys2-pkgconf-1.9.4-1-x86_64.pkg.tar.zst.
-- Using cached msys2-which-2.21-4-x86_64.pkg.tar.zst.
-- Using cached msys2-autoconf-archive-2022.09.03-1-any.pkg.tar.zst.
-- Using cached msys2-bash-5.2.015-1-x86_64.pkg.tar.zst.
-- Using cached msys2-coreutils-8.32-5-x86_64.pkg.tar.zst.
-- Using cached msys2-file-5.44-5-x86_64.pkg.tar.zst.
-- Using cached msys2-gawk-5.2.1-2-x86_64.pkg.tar.zst.
-- Using cached msys2-grep-1~3.0-6-x86_64.pkg.tar.zst.
-- Using cached msys2-gzip-1.12-2-x86_64.pkg.tar.zst.
-- Using cached msys2-diffutils-3.9-1-x86_64.pkg.tar.zst.
-- Using cached msys2-sed-4.9-1-x86_64.pkg.tar.zst.
-- Using cached msys2-msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst.
-- Using cached msys2-autoconf2.71-2.71-1-any.pkg.tar.zst.
-- Using cached msys2-automake1.16-1.16.5-1-any.pkg.tar.zst.
-- Using cached msys2-libiconv-1.17-1-x86_64.pkg.tar.zst.
-- Using cached msys2-libintl-0.21-2-x86_64.pkg.tar.zst.
-- Using cached msys2-zlib-1.2.13-1-x86_64.pkg.tar.zst.
-- Using cached msys2-tar-1.34-3-x86_64.pkg.tar.zst.
-- Using cached msys2-findutils-4.9.0-3-x86_64.pkg.tar.zst.
-- Using cached msys2-gmp-6.2.1-2-x86_64.pkg.tar.zst.
-- Using cached msys2-gcc-libs-11.3.0-3-x86_64.pkg.tar.zst.
-- Using cached msys2-libbz2-1.0.8-4-x86_64.pkg.tar.zst.
-- Using cached msys2-liblzma-5.4.1-1-x86_64.pkg.tar.zst.
-- Using cached msys2-libzstd-1.5.4-1-x86_64.pkg.tar.zst.
-- Using cached msys2-libreadline-8.2.001-3-x86_64.pkg.tar.zst.
-- Using cached msys2-mpfr-4.2.0-2-x86_64.pkg.tar.zst.
-- Using cached msys2-libpcre-8.45-3-x86_64.pkg.tar.zst.
-- Using cached msys2-m4-1.4.19-2-x86_64.pkg.tar.zst.
-- Using cached msys2-perl-5.36.0-1-x86_64.pkg.tar.zst.
-- Using cached msys2-ncurses-6.4-1-x86_64.pkg.tar.zst.
-- Using cached msys2-libcrypt-2.1-4-x86_64.pkg.tar.zst.
-- Using msys root at C:/vcpkg/downloads/tools/msys2/87962f0d86055c95
CMake Warning at scripts/cmake/vcpkg_configure_make.cmake:269 (message):
Unable to find system dir in the PATH variable! Appending required msys
paths!
Call Stack (most recent call first):
ports/icu/portfile.cmake:54 (vcpkg_configure_make)
scripts/ports.cmake:168 (include)
-- Generating configure for x64-windows
-- Finished generating configure for x64-windows
-- Using cached mingw-w64-i686-pkgconf-1~1.8.0-2-any.pkg.tar.zst.
-- Using cached msys2-msys2-runtime-3.4.6-1-x86_64.pkg.tar.zst.
-- Using msys root at C:/vcpkg/downloads/tools/msys2/6f3fa1a12ef85a6f
-- Configuring x64-windows-dbg
-- Configuring x64-windows-rel
-- Building x64-windows-dbg
-- Installing x64-windows-dbg
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:134 (message):
Command failed: C:/vcpkg/downloads/tools/msys2/87962f0d86055c95/usr/bin/make.exe -j 17 --trace -f Makefile install DESTDIR=/C/vcpkg/packages/icu_x64-windows
Working Directory: C:/vcpkg/buildtrees/icu/x64-windows-dbg/
See logs for more information:
C:\vcpkg\buildtrees\icu\install-x64-windows-dbg-out.log
C:\vcpkg\buildtrees\icu\install-x64-windows-dbg-err.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_build_make.cmake:168 (vcpkg_execute_build_process)
scripts/cmake/vcpkg_install_make.cmake:2 (vcpkg_build_make)
ports/icu/portfile.cmake:144 (vcpkg_install_make)
scripts/ports.cmake:168 (include)
error: building icu:x64-windows failed with: BUILD_FAILED
Elapsed time to handle icu:x64-windows: 6.5 min
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+icu
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?title=[icu]+Build+error&body=Copy+issue+body+from+C%3A%2Fvcpkg%2Finstalled%2Fvcpkg%2Fissue_body.md
Additional context
This error has already been fixed in the https://github.com/microsoft/vcpkg/issues/32711

This error has already been fixed in the https://github.com/microsoft/vcpkg/issues/32711

Does PR https://github.com/microsoft/vcpkg/pull/32750 resolve your issue?

This error has already been fixed in the https://github.com/microsoft/vcpkg/issues/32711

Does PR #32750 resolve your issue?

I'm seeing this as well in 2023.08.09 which should have that PR unfortunately.

The last test of the installation of the ICU package this week led to the error again. I can't build my project because of this.

I have a tentative fix in my pull request. Hopefully it also works for you.

I tested that on myself. It works. Thanks on flmmkch

source: gharchive/issue

authors: LilyWangLL flmmkch gennadij trileyinvicro

repo: microsoft/vcpkg

license: MIT

license_type: permissive

license_source: github-api


text:
[libressl] No .cmake files inside the share directory after vcpkg install

Describe the bug
find_package(LibreSSL) fails because the port has no .cmake file inside its share deployment folder.
Environment

OS: Windows
Compiler: MSVC 19.37.32825.0

To Reproduce
I'm using vcpkg in manifest mode.
Create a vcpkg.json with this content:
{
  "$schema": "https://raw.githubusercontent.com/microsoft/vcpkg-tool/main/docs/vcpkg.schema.json",
  "dependencies": [
    "libressl"
  ]
}

Create a CMakeLists.txt with this content:
project(MyProj CXX)

find_package(LibreSSL REQUIRED)

After generating the CMake cache, the output is:
1> CMake generation started for default configuration: 'x64-Debug'.
1> Found and using vcpkg toolchain file (C:/Dev/vcpkg/scripts/buildsystems/vcpkg.cmake).
1> Command line: "C:\Windows\system32\cmd.exe" /c "%SYSTEMROOT%\System32\chcp.com 65001 >NUL && "C:\PROGRAM FILES\MICROSOFT VISUAL STUDIO\2022\PROFESSIONAL\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\CMake\bin\cmake.exe"  -G "Ninja"  -DCMAKE_BUILD_TYPE:STRING="Debug" -DCMAKE_INSTALL_PREFIX:PATH="D:\Dev\libresslcmaketest\out\install\x64-Debug" -DCMAKE_C_COMPILER:FILEPATH="C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe" -DCMAKE_CXX_COMPILER:FILEPATH="C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe"   -DCMAKE_MAKE_PROGRAM="C:\PROGRAM FILES\MICROSOFT VISUAL STUDIO\2022\PROFESSIONAL\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\Ninja\ninja.exe" -DCMAKE_TOOLCHAIN_FILE="C:/Dev/vcpkg/scripts/buildsystems/vcpkg.cmake" "D:\Dev\libresslcmaketest" 2>&1"
1> Working directory: D:\Dev\libresslcmaketest\out\build\x64-Debug
1> [CMake] CMake Warning (dev) at CMakeLists.txt:1 (project):
1> [CMake]   cmake_minimum_required() should be called prior to this top-level project()
1> [CMake]   call.  Please see the cmake-commands(7) manual for usage documentation of
1> [CMake]   both commands.
1> [CMake] This warning is for project developers.  Use -Wno-dev to suppress it.
1> [CMake]
1> [CMake] -- Running vcpkg install
1> [CMake] Detecting compiler hash for triplet x64-windows...
1> [CMake] All requested packages are currently installed.
1> [CMake] Total install time: 300 ns
1> [CMake] -- Running vcpkg install - done
1> [CMake] CMake Error at C:/Dev/vcpkg/scripts/buildsystems/vcpkg.cmake:859 (_find_package):
1> [CMake]   By not providing "FindLibreSSL.cmake" in CMAKE_MODULE_PATH this project has
1> [CMake]   asked CMake to find a package configuration file provided by "LibreSSL",
1> [CMake]   but CMake did not find one.
1> [CMake]
1> [CMake]   Could not find a package configuration file provided by "LibreSSL" with any
1> [CMake]   of the following names:
1> [CMake]
1> [CMake]     LibreSSLConfig.cmake
1> [CMake]     libressl-config.cmake
1> [CMake]
1> [CMake]   Add the installation prefix of "LibreSSL" to CMAKE_PREFIX_PATH or set
1> [CMake]   "LibreSSL_DIR" to a directory containing one of the above files.  If
1> [CMake]   "LibreSSL" provides a separate development package or SDK, be sure it has
1> [CMake]   been installed.
1> [CMake] Call Stack (most recent call first):
1> [CMake]   CMakeLists.txt:3 (find_package)
1> [CMake] CMake Warning (dev) in D:\Dev\libresslcmaketest\CMakeLists.txt:
1> [CMake]   No cmake_minimum_required command is present.  A line of code such as
1> [CMake]
1> [CMake]     cmake_minimum_required(VERSION 3.26)
1> [CMake]
1> [CMake]   should be added at the top of the file.  The version specified may be lower
1> [CMake]   if you wish to support older CMake versions for this project.  For more
1> [CMake]   information run "cmake --help-policy CMP0000".
1> [CMake] This warning is for project developers.  Use -Wno-dev to suppress it.
1> [CMake]
1> [CMake] -- Configuring incomplete, errors occurred!
1> 'C:\Windows\system32\cmd.exe' '/c "%SYSTEMROOT%\System32\chcp.com 65001 >NUL && "C:\PROGRAM FILES\MICROSOFT VISUAL STUDIO\2022\PROFESSIONAL\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\CMake\bin\cmake.exe"  -G "Ninja"  -DCMAKE_BUILD_TYPE:STRING="Debug" -DCMAKE_INSTALL_PREFIX:PATH="D:\Dev\libresslcmaketest\out\install\x64-Debug" -DCMAKE_C_COMPILER:FILEPATH="C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe" -DCMAKE_CXX_COMPILER:FILEPATH="C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe"   -DCMAKE_MAKE_PROGRAM="C:\PROGRAM FILES\MICROSOFT VISUAL STUDIO\2022\PROFESSIONAL\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\Ninja\ninja.exe" -DCMAKE_TOOLCHAIN_FILE="C:/Dev/vcpkg/scripts/buildsystems/vcpkg.cmake" "D:\Dev\libresslcmaketest" 2>&1"' execution failed with error: ''C:\Windows\system32\cmd.exe' '/c "%SYSTEMROOT%\System32\chcp.com 65001 >NUL && "C:\PROGRAM FILES\MICROSOFT VISUAL STUDIO\2022\PROFESSIONAL\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\CMake\bin\cmake.exe"  -G "Ninja"  -DCMAKE_BUILD_TYPE:STRING="Debug" -DCMAKE_INSTALL_PREFIX:PATH="D:\Dev\libresslcmaketest\out\install\x64-Debug" -DCMAKE_C_COMPILER:FILEPATH="C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe" -DCMAKE_CXX_COMPILER:FILEPATH="C:/Program Files/Microsoft Visual Studio/2022/Professional/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe"   -DCMAKE_MAKE_PROGRAM="C:\PROGRAM FILES\MICROSOFT VISUAL STUDIO\2022\PROFESSIONAL\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\CMAKE\Ninja\ninja.exe" -DCMAKE_TOOLCHAIN_FILE="C:/Dev/vcpkg/scripts/buildsystems/vcpkg.cmake" "D:\Dev\libresslcmaketest" 2>&1"' returned with exit code: 1'.

Moreover, if you check the share folder inside the libressl port, you'll see that there is no LibreSSLConfig.cmake file inside it. Actually, there is no .cmake file at all.

I'll try to add usage.


text:
[vulkan-validationlayers] ErrorOutOfHostMemory when run

Description
When running a vulkan project that loads validation layers, I am unable to successfully create an instance due to an ErrorOutOfHostMemory exception
Environment

OS: Windows (MinGW)
IDE: CLion
Compiler: g++ 14.2 / clang++ 19.1.3 (Tried both)

To Reproduce
Steps to reproduce the behavior:

./vcpkg install vulkan-validationlayers
Set VK_ADD_LAYER_PATH=@layer_path@
Run program with vulkan validation layers
See error vk::createInstance: ErrorOutOfHostMemory

Expected behavior
The program successfully loads the validation layers
Additional context
Using system installed Vulkan SDK the error is not present on the same build (running the exe directly without setting VK_ADD_LAYER_PATH)

Set VK_ADD_LAYER_PATH=@layer_path@

What did you actually do in this step?

Set VK_ADD_LAYER_PATH=@layer_path@

What did you actually do in this step?

I set as VK_ADD_LAYER_PATH=vcpkg_installed\x64-mingw-dynamic\bin
I have also set it to the absolute path with the same result

@InfiniteLoopGameDev Could you please try x64-windows?

I am able to confirm that it is specifically vulkan-validationlayers; by replacing the DLL in vcpkg_installed\x64-mingw-dynamic\bin by the one that is provided by the vulkan SDK without actually installing the DLL.
I have also tried using the debug version by setting it to VK_ADD_LAYER_PATH=vcpkg_installed\x64-mingw-dynamic\debug\bin. That gave me the following output:
mimalloc-redirect: error: unable to find target module.
mimalloc-redirect: warning: standard malloc is _not_ redirected! -- using regular malloc/free. (v1.1c)
mimalloc: assertion failed: at "C:/Users/<username>/.vcpkg-clion/vcpkg/buildtrees/mimalloc/src/v2.1.7-7cda0129ba.clean/src/options.c":264, mi_add_stderr_output
  assertion: "mi_out_default == NULL"

I'm having the same issue when i use mingw

I'm having the same issue when i use mingw

@smile-zyk Have you tried with Visual Studio / x64-windows? If, so does it give you the same issue?

After much trouble of trying to get WSL2 to work. I have successfully compiled and ran my code with WSL2. So the problem seems to come from Windows

I also tried x64-windows-static which also worked (the test on WSL was x64-linux-dynamic) but x64-mingw-static. I now don't know what is happening. It might be that vulkan-validationlayers might not be able to find its dependencies at runtime on Windows host

but x64-mingw-static. I now don't know what is happening.

Maybe https://github.com/microsoft/mimalloc/issues/542? There is  "redirect: unable to find module".

BTW does x64-mingw-dynamic work?

BTW does x64-mingw-dynamic work?

Sadly, No


text:
[easyhook] support static build

Library name: easyhook
Library description:
Source repository URL: https://github.com/EasyHook/EasyHook
Project homepage (if different from the source repository):
Please Add static easyhook library

@JackBoosY thanks

please support static build of easyhook @JackBoosY

Blocked by #260 #138.

Besides static build, it's also desirable to have a dynamic version of EasyHook that is available when using static triplets.
Injected DLLs often needs to be self-contained (it should not reference any 3rd party DLLs) because the dependencies of injected DLL is usually not inside the target process's DLL search path. Linking to (the dynamic version of) EasyHook will be fine, because EasyHook will load itself into the target process beforehand.
This means we need to build our library with the static triplet, but currently EasyHook cannot be installed using static triplet..

Close this PR until upstream fixes this.

authors: JackBoosY lanyizi mmhatami


text:
[suitesparse[metis]] build failure

Host Environment

OS: Windows
Compiler: revision

To Reproduce
Steps to reproduce the behavior:
./vcpkg install suitesparse[metis] --recurse
Failure logs
The following packages will be built and installed:
  * metis[core]:x64-windows
    suitesparse[core,metis]:x64-windows
Additional packages (*) will be modified to complete this operation.
Starting package 1/2: metis:x64-windows
Building package metis[core]:x64-windows...
-- Note: metis only supports static library linkage. Building static library.
-- Downloading http://glaros.dtc.umn.edu/gkhome/fetch/sw/metis/metis-5.1.0.tar.gz...
-- Downloading http://glaros.dtc.umn.edu/gkhome/fetch/sw/metis/metis-5.1.0.tar.gz... Failed. Status: 6;"Couldn't resolve host name"
CMake Error at scripts/cmake/vcpkg_download_distfile.cmake:175 (message):

      Failed to download file.
      If you use a proxy, please set the HTTPS_PROXY and HTTP_PROXY environment
      variables to "https://user:password@your-proxy-ip-address:port/".
      Otherwise, please submit an issue at https://github.com/Microsoft/vcpkg/issues

Call Stack (most recent call first):
  ports/metis/portfile.cmake:8 (vcpkg_download_distfile)
  scripts/ports.cmake:94 (include)

Error: Building package metis:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: metis:x64-windows
  Vcpkg version: 2019.09.12-nohash

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

related to: https://github.com/microsoft/vcpkg/issues/8336

@xarthurx Normally this error means either they are behind a proxy or the download site vcpkg is trying to download the file from is unavailable...
I just tried to contact the download site "http://glaros.dtc.umn.edu/gkhome/fetch/sw/metis/metis-5.1.0.tar.gz" to see if it would download the file to my pc but I get an error:
This site can't be reached
glaros.dtc.umn.edu's server IP address could not be found.
ERR_NAME_NOT_RESOLVED
So the site may indeed be down or has been taken offline.

Seems it's site has problem. Please download this package and put it into VCPKG_PATH/downloads then rebuild suitesparse.
metis-5.1.0.tar.gz
Thanks.

@xarthurx Does this  issue solved?

@JackBoosY Yes. I'll close it now. Thanks for the help.

I think we can still fix this issue long term though. (I just had this failure again since this site seems to be down again.)
METIS is now distributed via github:
https://github.com/KarypisLab/METIS
However, the previously included GKLib library is not a sub module, so that would also need to be added:
https://github.com/KarypisLab/GKlib
Some changes have been made so the patches we currently have will not apply anymore. I will try and get a PR together, but wanted to make sure this was in a comment somewhere.

authors: JackBoosY SallySoul timautry xarthurx


text:
[fmt] build failure while cygwin is installed and having a PATH variable to it

Host Environment

OS: Win 10
Compiler: Vcpkg version: 2019.09.12-nohash

To Reproduce
Steps to reproduce the behavior:
.\vcpkg.exe install fmt
Failure logs
PS C:\dev\tools\vcpkg> .\vcpkg.exe install fmt
The following packages will be built and installed:
fmt[core]:x86-windows
Starting package 1/1: fmt:x86-windows
Building package fmt[core]:x86-windows...
-- Downloading https://github.com/fmtlib/fmt/archive/6.0.0.tar.gz...
CMake Error at C:/dev/tools/vcpkg/scripts/cmake/vcpkg_download_distfile.cmake:185 (file):
file RENAME failed to rename
/cygdrive/c/dev/tools/vcpkg/C:/dev/tools/vcpkg/downloads/temp/fmtlib-fmt-6.0.0.tar.gz

to
/cygdrive/c/dev/tools/vcpkg/C:/dev/tools/vcpkg/downloads/fmtlib-fmt-6.0.0.tar.gz

because: No such file or directory
Call Stack (most recent call first):
C:/dev/tools/vcpkg/scripts/cmake/vcpkg_from_github.cmake:132 (vcpkg_download_distfile)
C:/dev/tools/vcpkg/ports/fmt/portfile.cmake:2 (vcpkg_from_github)
C:/dev/tools/vcpkg/scripts/ports.cmake:94 (include)
Error: Building package fmt:x86-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: fmt:x86-windows
Vcpkg version: 2019.09.12-nohash
Additionally, attach any relevant sections from the log files above.
PS C:\dev\tools\vcpkg> .\vcpkg update
Using local portfile versions. To update the local portfiles, use git pull.
No packages need updating.
Additional context
PS was run as admin, 98GBs free on C:, I'll stand by for any requests for info.

x86-windows.vcpkg_abi_info.txt was created in a "C:\dev\tools\vcpkg\buildtrees\fmt" directory
Content of the file:
CONTROL 9cebf357c183e641caa402126ebc6d6688d1a771 portfile.cmake b2434022329236462cc9304b9e3c3a19ef69faa8 cmake 3.14.5 powershell ab1effc926b000a6adc12198a1886514ec203621a53b0cd7ec1cd9a8225dccda7e857feaabcfba4004bea73129b986abaad777c4573f44e0af70411226ce08b0 vcpkg_fixup_cmake_targets 0ddb96472da00d45d10e0b0bf037bfb744164d0a triplet e8dc96fd479b53bb0e6748625827c8268017e35a features core

Looks like the cygdrive created a wierd directory for C:
`PS C:\dev\tools\vcpkg> ls
Directory: C:\dev\tools\vcpkg

Mode                LastWriteTime         Length Name

d-----       11/27/2019   3:01 AM                .github
d-----       11/27/2019   3:06 AM                buildtrees
d-----       11/27/2019   3:06 AM                C
d-----       11/27/2019   3:01 AM                docs
d-----       11/27/2019   3:06 AM                downloads
d-----       11/27/2019   3:06 AM                installed
d-----       11/27/2019   3:06 AM                packages
d-----       11/27/2019   3:01 AM                ports
d-----       11/27/2019   3:03 AM                scripts
d-----       11/27/2019   3:03 AM                toolsrc
d-----       11/27/2019   3:01 AM                triplets
-a----       11/27/2019   3:01 AM              8 .gitattributes
-a----       11/27/2019   3:01 AM           5625 .gitignore
-a----       11/27/2019   3:01 AM              0 .vcpkg-root
-a----       11/27/2019   3:01 AM            100 bootstrap-vcpkg.bat
-a----       11/27/2019   3:01 AM            109 bootstrap-vcpkg.sh
-a----       11/27/2019   3:01 AM         368962 CHANGELOG.md
-a----       11/27/2019   3:01 AM           2432 CONTRIBUTING.md
-a----       11/27/2019   3:01 AM           1096 LICENSE.txt
-a----       11/27/2019   3:01 AM           2334 NOTICE.txt
-a----       11/27/2019   3:01 AM           4345 README.md
-a----       11/27/2019   3:01 AM           3282 README_zh_CN.md
-a----       11/27/2019   3:03 AM        1014272 vcpkg.exe`

The same thing just occurred for me while installing SDL2

OK, I already have an install of cygwin on my computer. I renamed the "c:\cygwin64" directory (which "C:\cygwin64\bin"i s in my PATH env) to "c:\cygwin64BAK" and all the packages install.
I don't know if it's because of cygwin being there, git, or the CMake in that install conflicting, but it looks like it has something to do with that. Should be enough for you guys to reproduce the issue.

Duplicated to #3205, #5856.

I don't know if you'd like me to edit the title of this issue, there is no problem installing fmt. My problem appears to be installing any package via vcpkg while cygwin is installed and having a PATH variable to it.

Also, I am not behind a proxy... Just FYI for setting up an environment to replicate.

Hi, @toboRlivE
You Can use Visual Studio 2019, not cygwin, link https://visualstudio.microsoft.com/zh-hans/vs/?rr=http%3A%2F%2Fwww.baidu.com%2Flink%3Furl%3DSVTex4JDby4HUtB3gxXDHqArrMBZVveLt-rW0hhxWp2B6Yr7zThG_Oyd8vLX72rg%26wd%3D%26eqid%3De1838db7000095d9000000065de47f03  Community 2019 is free.
Professionnal 2019 and Enterprise 2019 need to pay.

Thanks, I am using VS2019 already. I just have an install of cygwin on my computer previously, and when I installed and started using vcpkg, I came across that issue. I read through a few of the issues that seem to have the same symptoms, so I added as much detail as I could so you could replicate the problem.

I don't think this is a port bug, I'm pretty sure it has to do with vcpkg internals conflicting with cygwin being in my PATH env. Just wanted to leave a reminder that if I mangle the path to my cygwin install, or remove the PATH variable, vcpkg installs packages with no problem. I don't know how to change the tag on this issue.

Would you like me to change the Label or Title of the issue?

@toboRlivE, thanks for reporting this issue and providing us details about this issue!  We will try to repro it.

Confirmed, this issue caused by using cmake under cygwin.
Repro steps:

git clone https://github.com/microsoft/vcpkg
./bootstrap-vcpkg.bat
Installed cygwin(select cmake)
Add C:\cygwin64\bin to PATH
./vcpkg install fmt

VCPKG try to find cmake that installed by system first, if it doesn't exist, it will download a new one. If it exist, then it will use that one. Using cmake under cygwin looks has some issues here.

This issue current disappears in the latest vcpkg(2021-08-03-1a6d67b8150e94b7f473c6ab1c0cfd), it's due to the camke version used in vcpkg(3.20.2) is large than the version of cygwin(3.20.0), If set the cmake version used by vcpkg to 3.20.0, this issue will appear again.

Oh, I should record this issue number, given the many duplicate issues.
The cygwin cmake needs to be recognized. IIRC one indicator is the list of generators. @Cheney-W can you share the output of cmake -G for cygwin's cmake?

C:\cygwin64\bin>cmake.exe -G
CMake Error: No generator specified for -G
Generators
* Unix Makefiles               = Generates standard UNIX makefiles.
  Ninja                        = Generates build.ninja files.
  Ninja Multi-Config           = Generates build-<Config>.ninja files.
  CodeBlocks - Ninja           = Generates CodeBlocks project files.
  CodeBlocks - Unix Makefiles  = Generates CodeBlocks project files.
  CodeLite - Ninja             = Generates CodeLite project files.
  CodeLite - Unix Makefiles    = Generates CodeLite project files.
  Eclipse CDT4 - Ninja         = Generates Eclipse CDT 4.0 project files.
  Eclipse CDT4 - Unix Makefiles= Generates Eclipse CDT 4.0 project files.
  Kate - Ninja                 = Generates Kate project files.
  Kate - Unix Makefiles        = Generates Kate project files.
  Sublime Text 2 - Ninja       = Generates Sublime Text 2 project files.
  Sublime Text 2 - Unix Makefiles
                               = Generates Sublime Text 2 project files.

Thanks! This confirms that there are no Windows generators (not even MinGW). IIRC this identical with the cmake in the msys subsystem of MSYS2. I will verify this later, on a Windows machine.

The latest vcpkg currently uses CMake 3.30.1.
PS E:\vcpkg> ./vcpkg version
vcpkg package management program version 2024-11-12-eb492805e92a2c14a230f5c3deb3e89f6771c321

See LICENSE.txt for license information.

The latest cygwin version is 3.5.4, which includes three optional CMake versions: 3.28.3, 3.25.3, 3.23.2.

Whenever I intentionally make the CMake version in vcpkg the same as in cygwin, I get an error. Currently I have tried CMake 3.28.3 and CMake 3.25.3, both give the following error:
PS E:\vcpkg> ./vcpkg install fmt
Computing installation plan...
The following packages will be built and installed:
    fmt:x64-windows@11.0.2#1
Detecting compiler hash for triplet x64-windows...
error: while detecting compiler information:
The log file content at "E:\vcpkg\buildtrees\detect_compiler\stdout-x64-windows.log" is:
CMake Error at E:/vcpkg/scripts/ports.cmake:143 (message):
  Cannot find port:

    Directory does not exist: E;/vcpkg/scripts/detect_compiler

error: vcpkg was unable to detect the active compiler's information. See above for the CMake failure output.

If the CMake versions are inconsistent, the installation is successful.

The Cygwin environment, as the derived MSYS2 environment, is a POSIX-like runtime, not a Windows-like runtime. That's why Cygwin CMake uses POSIX path separator (/), POSIX path list separators (:), and POSIX paths (/C/Windows). This is incompatible by purpose. It is meant for buildings programs which are completely unaware of Windows.
IIRC these versions of CMake also come without Visual Studio generators, so they are easy to detect with cmake -G. This was elaborated in a previous issue.
This is a frequent issue. The vcpkg team should really improve the diagnostics for this case. All information is readily available.

authors: AlvinZhangH Cheney-W MonicaLiu0311 PhoebeHui dg0yt toboRlivE


text:
[libssh] disable gssapi

What does your PR fix?
The .pc file of libssh does not add the appropriate linking flags for gssapi when it is found as a system library on linux or osx. This patch disables the feature so libssh can still be linked against on those platforms. Potential fix for Fixes #18166.

Which triplets are supported/not supported? Have you updated the CI baseline?
No changes.

Does your PR follow the maintainer guide?
Yes, to the best of my knowledge.

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?
Yes.

Thanks for your fixing @mcmtroffaes.

Thanks @mcmtroffaes !

source: gharchive/pull-request

authors: NancyLi1013 mcmtroffaes strega-nil-ms


text:
[Guilite] Add new port

Describe the pull request
The smallest header-only GUI library (4 KLOC) for all platforms.
https://github.com/idea4good/GuiLite

What does your PR fix?

New port

Which triplets are supported/not supported? Have you updated the CI baseline?

All

Does your PR follow the maintainer guide?

Yes

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?

Yes
If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

Thanks for the new port!

authors: BillyONeal SamuelMarks


text:
[rtaudio] update to 6.0.1

Fixes https://github.com/microsoft/vcpkg/issues/35504
Features passed with following triplets:
x86-windows
x64-windows
x64-windows-static

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

/azp run

Thanks for the update!

authors: BillyONeal Cheney-W


text:
[rocksdb] update to 9.6.1

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

Thanks for the update!


text:
QoL: Buildtype variables for looping over buildtypes

While working on the qt scripts I often defined those variables below to avoid unnecessary code duplication to loop over the different buildtypes
TODO:

[ ] Rename VCPKG_BUILD_TRIPLET_* to something different ?
[ ] Remove VCPKG_BUILDTREE_TRIPLET_DIR_ ?

Thanks for the PR!
This in principle seems like it could be a useful abstraction, but I'd like to see it demonstrated in multiple contexts before merging.
Specifically, if it turns out to only be useful in Qt5, then it should be private to Qt5. However, if it can be used to make code significantly cleaner and clearer in more contexts, I'd like to see this PR introduce at least two of those refactorings.

TODO (only 2 of N):

[ ] Refactor vcpkg_build_cmake
[ ] Refactor vcpkg_build_msbuild
[ ] Refactor vcpkg_build_qmake
[ ] Refactor vcpkg_configure_cmake
[ ] Refactor vcpkg_configure_meson
[ ] Refactor vcpkg_configure_qmake
[ ] Refactor vcpkg_fixup_cmake_targets
[ ] Refactor vcpkg_install_meson (a bit short for a refactor, but consistency is important)
[ ] Refactor vcpkg_install_msbuild
[ ] Refactor an unknown number of ports which might benift from the PR (purely optional; but at least qt if the update to 5.12.4 PR is merged.)

Please resolve these conflicts.
Thanks.

Pinging @Neumann-A  for response. Is work still being done for this PR?

@JackBoosY: You put the PR back into Draft?!?! I consider it finished for the time unless there is something which needs to ne fixed which I don't know of or you want some changes to it. Maybe run a full rebuild of everything to check if everything is working as intended.

@Neumann-A Sorry, my fault.

/azp run

Could you select some ports to test these functions?

hmm most regressions are failed due to download failures. The rest seems to be port build issues and not related to these changes.

Test result:

sdl2:x64-uwp: failed on master branch.

Waiting for other pipeline results...

Hmm from the whole list only two ports seem to be relevant which are:
seal:x64-linux : needs further investigate
libfabric:x64-windows-static : needs further investigate

I was able to build both successfully using this branch.

@Neumann-A Yep, I also can't repro that in my machine.

OMG...more and more different regressions...

[ ] osg:x64-linux
[ ] signalrclient:x64-linux
[ ] opencc:x64-linux
[ ] seal:x64-linux
[ ] xmsh:x64-osx
[ ] rply:x64-osx
[ ] seal:x64-osx
[ ] signalrclient:x64-osx
[ ] gmp:x64-osx
[ ] rply:x64-uwp
[ ] solid3:x64-uwp
[ ] protobuf:x64-uwp
[ ] signalrclient:x64-windows
[ ] seal:x64-windows
[ ] libaiff:x64-windows
[ ] monkeys-audio:x64-windows
[ ] rply:x64-windows
[ ] pdal:x64-windows
[ ] gmp:x64-windows
[ ] dmlc:x64-windows
[ ] icu:x64-windows
[ ] signalrclient:x64-windows-static
[ ] seal:x64-windows-static
[ ] dcmtk:x64-windows-static
[ ] icu:x64-windows-static
[ ] rply:x64-windows-static
[ ] pdal:x64-windows-static
[ ] gmp:x64-windows-static
[ ] zxing-cpp:x64-windows-static
[ ] libfabric:x64-windows-static
[ ] signalrclient:x86-windows
[ ] seal:x86-windows
[ ] monkeys-audio:x86-windows
[ ] gsoap:x86-windows
[ ] rply:x86-windows
[ ] pdal:x86-windows
[ ] gmp:x86-windows
[ ] icu:x86-windows

/azp run

This PR always seems to be the first one that triggers msys losing it ¯\_(ツ)_/¯

/azp run

Either the msys servers relied upon by some ports are broken causing CI failure, or something in this change causes CI to hang consistently.

This change depends on msys being fixed as in https://github.com/microsoft/vcpkg/pull/11443 or https://github.com/microsoft/vcpkg/pull/11471

@JackBoosY: None of those regressions look like they are caused by this PR. I assume some hidden unresolved dependencies in the ports which generate the errors in a full rebuild. (also see #11502 for comparison)
pdal: -> find_package issue. PostgreSQL::PostgreSQL in wrapper used without check if it actually exists.

@Neumann-A That's correct, I only want to know which port failed on the baseline.

@JackBoosY: Ah okay was just wondering due to the requires:author-response tag

/azp run

@Neumann-A pipelines are fixed, could you resolve the file conflict?
Thanks.

@JackBoosY: done

Can you merge the latest changes into this branch?

/azp run

/azp run

@Neumann-A, ocilib:x86-windows and ocilib:x64-windows failed with debug mode, I noticed it only build release mode before, the solution doesn't configure debug mode, could you help have a look?
   "D:\buildtrees\ocilib\x86-windows-dbg\v4.6.4-271d6c24cf\proj\dll\ocilib_dll_vs2019.sln" (Rebuild target) (1) ->
   (ValidateSolutionConfiguration target) ->
     D:\buildtrees\ocilib\x86-windows-dbg\v4.6.4-271d6c24cf\proj\dll\ocilib_dll_vs2019.sln.metaproj : error MSB4126: The specified solution configuration "Debug|x86" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration. [D:\buildtrees\ocilib\x86-windows-dbg\v4.6.4-271d6c24cf\proj\dll\ocilib_dll_vs2019.sln]

monkeys-audio regression will be fixed in another PR.

Closing this PR since it seems that no progress is being made. Please reopen if work is still being done.

authors: BillyONeal JackBoosY Neumann-A PhoebeHui ras0219-msft


text:
[Survey] User feedback

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

7 Have issue with docker image
good I like it for being user friendly but can be more intuitive
more clear visual understanding with interactive learning pattern for the new user, problem solving help when issues arise

What issues are you having when using Azure Stream Analytics extension?

repo: microsoft/vscode-asa


text:
Azure Remote Debugging is currently only supported for Node.js apps on Linux.

Action: appService.StartRemoteDebug
Error type: Error
Error Message: Azure Remote Debugging is currently only supported for Node.js apps on Linux.
Version: 0.16.2
OS: win32
OS Release: 10.0.17763
Product: Visual Studio Code
Product Version: 1.40.2
Language: en

@ereeneid Thanks for reporting.  If you're trying to remote debug, it's currently only supported on Node.js.  What are you trying to remote debug?

authors: ereeneid nturinski

repo: microsoft/vscode-azureappservice


text:
test

Does this occur consistently?
Repro steps:

Action: appService.Deploy
Error type: Error
Error Message: "resourceGroupName" should satisfy the constraint - "Pattern": /^[-w._()]+[^.]$/
Version: 0.19.0
OS: win32
OS Release: 10.0.19041
Product: Visual Studio Code
Product Version: 1.49.1
Language: en

Call Stack
WebApps._getConfiguration extension.bundle.js:225:1884985
extension.bundle.js:225:3167679extension.bundle.js:225:3167679
WebApps.getConfiguration extension.bundle.js:225:3167657
SiteClient.<anonymous> extension.bundle.js:164:145908
extension.bundle.js:164:142930extension.bundle.js:164:142930
i extension.bundle.js:164:142616
SiteClient.getSiteConfig extension.bundle.js:164:145730
extension.bundle.js:1:552564extension.bundle.js:1:552564
fulfilled extension.bundle.js:1:551148
processTicksAndRejections task_queues.js:94:5

What did you use as your app name?

authors: nturinski snsclanceo


text:
Region issues

Does this occur consistently?
Repro steps:

Action: azureFunctions.createFunctionApp
Error type: Unauthorized
Error Message: The scale operation is not allowed for this subscription in this region. Try selecting different region or scale option.
Version: 0.24.1
OS: linux
OS Release: 5.4.0-47-generic
Product: Visual Studio Code
Product Version: 1.48.2
Language: en

Call Stack
new RestError extension.bundle.js:48:94460
extension.bundle.js:48:1291123
processTicksAndRejections task_queues.js:85:5

Please try creating your function app in a different region.  If this still doesn't work, please provide detailed repro steps.

authors: chimerashashi nturinski

repo: microsoft/vscode-azurefunctions


text:
Debugging Azure Function with vscode

I've been struggling to debug an HttpTrigger type azure function with vscode.
My assumption is that the issue might be related to the config files within .vscode/ or at worst, my own environment.
As of now, when I try to debug a recently created function (func init) I get the following error from vscode:
> Executing task: dotnet clean /property:GenerateFullPaths=true /consoleloggerparameters:NoSummary <

execvp(3) failed.: Permission denied

The terminal process "dotnet 'clean', '/property:GenerateFullPaths=true', '/consoleloggerparameters:NoSummary'" failed to launch (exit code: 1)

Inside .vscode/ there 4 files:

    ├── extensions.json
    ├── launch.json
    ├── settings.json
    └── tasks.json

and inside task.json there are a few dotnet related commands that are causing the error above.
Despite these files being automatically generated by core tools (func) I removed the dotnet lines from task.json and hit Debug.
After a few seconds I get:
Failed to detect running Functions host within "60" seconds. You may want to adjust the "azureFunctions.pickProcessTimeout" setting.

Is there any command to automatically generate the debug configuration? e.g. ".NET generate assets for build and debug"
Have you faced anything similar to it?

My env settings:
OS: Ubuntu 20.04.4 LTS
Code:1.64.2 x64
Azure Functions Extension: v1.6.0
Core Tools Version: 3.0.3904

RaphaelSilv  Thanks for reporting!  It looks like the dotnet clean command isn't able to run in its current directory due to user permissions.
The tasks.json is necessary to debug because we are looking for that task to attach to the process, so deleting it will cause some issues.

Replace the type from process to shell inside tasks.json solved it.
FWIW:

omnisharp-vscode #4556

Thanks for bringing this issue to our attention.  Seems like this might be an upstream issue that we can't do anything about.  Changing it to shell seems like it has some negative performance impacts, but it's worth to use this workaround until it can get resolved.

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 RaphaelSilv nturinski


text:
[Suggestion] It would be better to change the "Downloaded to 'Users/...'. Succeeded" to the "Download to 'Users/...'. Succeeded" in the Azure: Activity Log window

OS: Win10
Build Version: 20230104.1
Regression: Not a regression
Repro Steps:

Expand a storage account -> Expand a blob container-> Right click a file/folder -> Click "Download...".
Check the log message in the Azure: Activity Log window.

Actual:
Show the "Downloaded to 'Users/...'. Succeeded" in the Azure: Activity Log window.

Suggestion;
It would be better to change the "Downloaded to 'Users/...'. Succeeded" to the "Download to 'Users/...'. Succeeded" in the Azure: Activity Log window.
More Info:
This issue doesn't reproduce after uploading a file/folder.

We should remove the 'ed' from 'downloaded' and also remove the extra period as well.

repo: microsoft/vscode-azurestorage


text:
message(DEBUG "...") doesn't display in VSCode output?

Brief Issue Summary
While working on my projects I added some message(DEBUG "...") statements.  I also set "cmake.loggingLevel": "debug".
Expected:
What I expected to see was the message statements from DEBUG and above.
Apparent Behavior:
What I do see is that there is some extra info the the VSCode Output [driver] messages etc. But none of the message(DEBUG "...") statements.
If I use message(STATUS "...") then I do see the messages.
Have I misinterpreted the cmake.loggingLevel settings? Is that not controlling the log level of CMake when it runs?
CMake Tools Log
[driver] Start configure
[driver] Runnnig pre-configure checks and steps
[driver] Run _refreshExpansions
[cms-driver] Run doRefreshExpansions
[driver] Run _refreshExpansions cb
[cmake] Configuring done
[cmake] CMake Deprecation Warning:
[cmake]   The 'cmake-server(7)' is deprecated.  Please port clients to use the
[cmake]   'cmake-file-api(7)' instead.
[cmake]
[cmake]
[cmake] Generating done
[cache] Reading CMake cache file c:/Users/Thomas/SourceTree/traceup/cext/build/Release/CMakeCache.txt
[cache] Parsing CMake cache string
[extension] [1947] cmake.configure finished (returned 0)
[kit] OK running C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\VC\Auxiliary\Build\vcvarsall.bat amd64, env vars: undefined

Platform and Versions

Operating System: Windows 10
CMake Version: 3.15.4
VSCode Version: 1.40.0
CMake Tools Extension Version: 1.2.1
Compiler/Toolchain: Visual C++ 2019

Sorry, I meant to respond to this earlier, but lost track of it.  YOu shouldn't need to set cmake.loggingLevel to Debug to make this work because it is controlled by a different mechanism.
This works for me in 3.14, but it didn't work for me in 3.15.  It could be a CMake bug, but I haven't had the time to try a lot of different configurations.
CMakeLists.txt
project(foo)
add_executable(foo src/1.cpp)
message(DEBUG "debug message")

Output
[cmake] DEBUGdebug message
[cmake] Configuring done
[cmake] Generating done

Gotcha. I recently upgraded to CMake 3.15 because of some good new features/improvement in that version.
So is the message type being mapped to VSCode's Output types?

but it didn't work for me in 3.15. It could be a CMake bug, but I haven't had the time to try a lot of different configurations.
I didn't even try this with cmake directly from the terminal. After I set up CMake Tools I've exclusively done everything from VSCode. (Great extension btw!)

Add to CMakeLists.txt:
# Use cmake --log-level=debug to get debug output.
set( CMAKE_MESSAGE_LOG_LEVEL "STATUS" )

The latter is the default, which you can change on the command line.

Can I also use cmake.configureArgs for this?

I've tried with
  "cmake.configureArgs": [
    "--log-level=DEBUG"
  ],

And that didn't seem to yield any message(DEBUG ...) messages.
  "cmake.buildArgs": [
     "--log-level=DEBUG"
  ],

This will lead to an error [build] ninja: fatal: -l parameter not numeric: did you mean -l 0.0?
Is there any way to control the warning level for CMake via CMakeTools that doesn't require editing CMakeList.txt files?

Ah! After updating to CMake 3.16 the above worked as expected. Must be 3.15 being bugged.

Why are you CC-ing me?
On Mon, 23 Mar 2020 09:47:13 -0700
Thomas Thomassen notifications@github.com wrote:

I've tried with
  "cmake.configureArgs": [
    "--log-level=DEBUG"
  ],

And that didn't seem to yield any message(DEBUG ...) messages.
  "cmake.buildArgs": [
     "--log-level=DEBUG"
  ],

This will lead to an error [build] ninja: fatal: -l parameter not numeric: did you mean -l 0.0?
Is there any way to control the warning level for CMake via
CMakeTools that doesn't require editing CMakeList.txt files?

--
Carlo Wood carlo@alinoe.com

I wasn't, I'm replying to the issue via GitHub. Must be the notification system from GitHub.

That's great!  I'll close the issue.

authors: CarloWood bobbrow thomthom

repo: microsoft/vscode-cmake-tools


text:
Owner

Copilot Chat Extension Version:
VS Code Version:
OS Version:
Logs:

Steps to Reproduce:

Please elaborate

authors: SWCurragh TylerLeonhardt

repo: microsoft/vscode-copilot-release


text:
Deployment issue on VSCode  cosmosDB

Repro steps:

Action: cosmosDB.createAccount
Error type: ServiceUnavailable
Error Message: Long running operation failed with error: "Sorry, we are currently experiencing high demand in this region, and cannot fulfill your request at this time. We work continuously to bring more and more capacity online, and encourage you to try again shortly. Please do not hesitate to contact us via Azure support at any time or for any reason using this link http://aka.ms/azuresupport.
ActivityId: 38e053a4-0790-4844-b951-565cf5f5aaf8, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0, Microsoft.Azure.Documents.Common/2.11.0,...
Version: 0.12.2
OS: win32
Product: Visual Studio Code
Product Version: 1.45.1
Language: en

Unfortunately our extension in VS Code can't do anything if there's no availability in Azure. This could be related to high demand during the build conference, but I'm purely speculating. I recommend trying a different region, trying again later, or contact Azure support as linked in the error message above.

authors: EricJizbaMSFT MANakib

repo: microsoft/vscode-cosmosdb


text:
Add devcontainer definition for k3d kubernetes cluster (minikube alternative)

Description
Add a new devcontainer definition for k3d kubernetes cluster.
With this, user will be able to create a new devcontainer which will enable the creation of a local kubernetes cluster (automated or manual).
This PR is based off of kubernetes-helm-minikube dev container.
PR Checklist

[X] I have updated the documentation accordingly.

[X] Added README.md describing the container
[X] Added sample nginx deployment document in README.md

[X] I have added/updated tests to cover my changes.

[X] Changed test.sh under test-project directory

[X] All new and existing tests passed.
[X] My code follows the code style of this project.
[X] I have checked to ensure there aren't other open Pull Requests for the same update/change.
[ ] Lint checker not integrated but fixed most Markdown lint errors (followed existing container document format)

Does this introduce a breaking change?

[ ] Yes
[X] No

Testing

[X] Manually created Codespaces from .devcontainer

[X] Provisioned a k3d cluster from terminal
[X] Automatically provisioned k3d cluster in postStartCommand

[X] Manually created local devcontainer

[X] Provisioned a k3d cluster from terminal afterwards
[X] Automatically provisioned k3d cluster in postStartCommand

[X] Manually applied pods/deployments to verify k3d cluster

References

Reference: https://github.com/microsoft/vscode-dev-containers/issues/1455

@iamnicoj @sivamu @juzuluag

@bamurtaugh can you please clarify what this means in practice? As an end user I see a PR that's open and ready to merge. Are user-contributed devcontainer features frozen from being accepted into main? What should end users of these features do in the meantime? I would appreciate a functional alternative in the interim.

Thanks again for opening this PR!
As a heads up, our team has been actively focused on an updated plan for community contributions and this repo moving forward, which we've now outlined in this issue: https://github.com/microsoft/vscode-dev-containers/issues/1589. This includes moving to a couple new repos for images (https://github.com/devcontainers/images) and Features (https://github.com/devcontainers/features).
We anticipate to have a similar repo and distribution process for templates/definitions. We'll keep everyone updated (likely via another issue in this repo or comment on https://github.com/microsoft/vscode-dev-containers/issues/1589) when our new templates repo is available and the process is defined.
Please let me know if you have any questions, thank you!

authors: bamurtaugh kforeverisback worldofgeese

repo: microsoft/vscode-dev-containers


text:
Broken test 'Import pandas and goto it:'

https://github.com/microsoft/vscode-jupyter/actions/runs/3086711973/jobs/4991343761
      Error: Waiting for editor to switch
      + expected - actual

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

@IanMatthewHuff looks like this test is consistently failing, will be disabling this test.

No longer an issue.

repo: microsoft/vscode-jupyter


text:
Why do we use msrCrypto?

It was added here: https://github.com/microsoft/vscode-jupyter/pull/11263
The library is huge at 343KB, src/notebooks is 490KB for comparison. It also says:

It is recommended that this library be used as a polyfill for the native Web Crypto API supported in modern browsers. It is strongly advised that you used the native browser crypto whenever available. It will be more thoroughly tested, more secure, and have significantly better performance.
...
var crypto =  window.crypto /*native*/ || window.msCrypto /*IE11 native*/ || window.msrCrypto; /*polyfill*/

This advice isn't followed, we actually recommend the opposite here? (note that msrCrypto is used regardless of which call from crypto is used.
https://github.com/microsoft/vscode-jupyter/blob/2482391980596b07d958e5fe15b3b2afd684eaab/src/platform/common/crypto.ts#L10-L18
If we must use it, could we switch to fetching it via a CDN only when a polyfill is needed?

Some more information in PRs or a link to issues would have been useful here, the PR doesn't address why this was introduced


text:
"Greyed out text" in the input box

Testing microsoft/vscode#122243
The text in the input box for the PR title looks like it's greyed out. This mislead me for example to assume that the pre-filled in title is a placeholder and not an actual string.

Interestingly, these inputs are already using var(--vscode-input-foreground) as the color which matches other inputs in VS Code. The vscode-dropdown-foreground color which the selects are using appears to be a bit different and higher contrast. @misolori do you think we should align these colors?

I think this just varies by theme, for example the GH Light theme shows both text as the same colors, though it looks like the placeholder text is not using any color token?

Updated the placeholder text color to use the vscode theme token for it

authors: RMacfarlane kieferrm misolori

repo: microsoft/vscode-pull-request-github


text:
Switching to a diff of a file with comments always open comments pane.

Extension version: 0.40.0
VSCode Version: 1.66.1 (8dfae7a5cd50421d10cd99cb873990460525a898)
OS: Darwin arm64 20.6.0

Steps to Reproduce:

Navigate to PR w/ file-comments.
Open one such file. 'Comments' tab opens up in the bottom pane.
Close 'Comments' pane and navigate to different tab.
Go back to file-with-comments. 'Comments' tab opens up again.

It'd be nice if the Comments pane wouldn't pop up everytime I go back to the diff view or at least have an option to disable that behaviour.

You can disable this with the setting comments.openView. With VS Code 1.67 this has already been changed to be less aggressive and only open on the first file with comments.


text:
Add status checks to the pull request description

It would great to expose PR status checks in the description. For example in Github we see

+1 for this one

+1 - Definitely a make or break for this extension

+1 one of the key values of making a pr on GitHub's ui

+1 yass

With the change for https://github.com/microsoft/vscode-pull-request-github/issues/1105 now merged, all status checks should show up on the description page. This isn't released yet but will be available in the nightly version of the extension tomorrow.

authors: RMacfarlane Skowt cat-turner glemaitre hemlok patocallaghan


text:
Highlighting for Python Code

Issue Type: Bug
Theme highlighting not working when using Python extension.
Python extension some times crashes and return original theme highlighting.
Extension version: 2020.4.74986
VS Code version: Code 1.44.2 (ff915844119ce9485abfe8aa9076ec76b5300ddd, 2020-04-16T16:36:23.138Z)
OS version: Windows_NT x64 10.0.18362

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 1992)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: enabledrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.85GB (13.98GB free)

Process Argv

Screen Reader
no

VM
0%

Are you using the Python Language server, i.e check the value of python.jediEnabled in settings

As you can see I have disabled Jedi. This is in my user settings, not sure if a I understand the difference between user and workspace, in case this is can produce a issue as well.
My vscode use to crash very often, that is almost unusable, and according to other github issues this was supposed to be resolved.
Any help will be deeply appreciated.

authors: Rcubes karrtikr

repo: microsoft/vscode-python


text:
command 'python.analysis.restartLanguageServer' already exists

We need to move this command to a global location rather than inside individual language server proxy. Potentially this should be in activation service for the language server since that currently handles starting a new server.

Duplicate of #13441


text:
Jedi 2and3 builtin error

Hi,
Everytime I launch a file in VScode, 2 Syntaxes errors are reported from the pythonFiles\lib\jedilsp\jedi\third_party\typeshed\stdlib\2and3 builtins.pyi file :
SyntaxError: non-default argument follows default argument jedi [1307, 12]
(and same for line 1319)
Lines 1306 and 1307 are:
@overload
def max(__iterable: Iterable[_T], *, key: Callable[[_T], Any] = ..., default: _VT) -> Union[_T, _VT]: ...
Lines 1318 and 1319 are:
@overload
def min(__iterable: Iterable[_T], *, key: Callable[[_T], Any] = ..., default: _VT) -> Union[_T, _VT]: ...
I have never modified this file since I am a beginner and I don't know what am I supposed to do about it.
Since these errors appeared my debugger works poorly and report non-existent errors on my files.

Thank you for your help!

This should be filed on jedi, https://github.com/davidhalter/jedi
/cc @davidhalter

@amina197 your version of Python is too old for keyword-only arguments which is what that file is using. You can either upgrade your version of Python or turn off Jedi and use either Pylance or no IntelliSense.

If it is a parso bug then it will be fixed in the next release of the extension for Jedi LSP and wasn't an issue in "old" Jedi as that's pinned for Python 2.7 support.

authors: amina197 brettcannon karthiknadig


text:
vscode-insider with Extension activation failed

Environment data

VS Code version: 1.55.0-insider
Extension version (available under the Extensions sidebar): 2021.3.680753044
OS and version: windows 10 Enterprise 20H2 19042.867
Python version (& distribution if applicable, e.g. Anaconda): 3.9.2

[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]
Expected behaviour
my extension can not work normally for a long time.
Actual behaviour
Opening a python file prints Extension activation failed, run the 'Developer: Toggle Developer Tools' command for more information.
toggle developer tools, and can see errors:
Conflict in settings file vscode-userdata:/c%3A/Users/yke/AppData/Roaming/Code%20-%20Insiders/User: Ignoring python.insidersChannel as python is "set PYTHONIOENCODING=utf8 && python -u"
  | (anonymous) | @ | workbench.desktop.main.js:633
-- | -- | -- | --
  | u | @ | workbench.desktop.main.js:633
  | f | @ | workbench.desktop.main.js:633
  | doParseRaw | @ | workbench.desktop.main.js:633
  | parseRaw | @ | workbench.desktop.main.js:633
  | parseContent | @ | workbench.desktop.main.js:633
  | loadConfiguration | @ | workbench.desktop.main.js:1265
  | async function (async) |   |
  | loadConfiguration | @ | workbench.desktop.main.js:1265
  | reload | @ | workbench.desktop.main.js:1265
  | reloadLocalUserConfiguration | @ | workbench.desktop.main.js:2060
  | (anonymous) | @ | workbench.desktop.main.js:2060
  | requestIdleCallback (async) |   |
  | e.runWhenIdle | @ | workbench.desktop.main.js:68
  | (anonymous) | @ | workbench.desktop.main.js:2060
  | Promise.then (async) |   |
  | updateWorkspaceAndInitializeConfiguration | @ | workbench.desktop.main.js:2060
  | initialize | @ | workbench.desktop.main.js:2060
  | async function (async) |   |
  | initialize | @ | workbench.desktop.main.js:2060
  | createWorkspaceService | @ | workbench.desktop.main.js:2789
  | initServices | @ | workbench.desktop.main.js:2789
  | open | @ | workbench.desktop.main.js:2789
  | f | @ | workbench.desktop.main.js:2798
  | m.load.removeDeveloperKeybindingsAfterLoad | @ | workbench.js:32
  | (anonymous) | @ | bootstrap-window.js:167
  | async function (async) |   |
  | (anonymous) | @ | bootstrap-window.js:162
  | r._invokeFactory | @ | loader.js:1133
  | r.complete | @ | loader.js:1143
  | r._onModuleComplete | @ | loader.js:1769
  | r._onModuleComplete | @ | loader.js:1781
  | r._resolve | @ | loader.js:1729
  | r.defineModule | @ | loader.js:1372
  | p | @ | loader.js:1819
  | _ | @ | loader.js:860
  | (anonymous) | @ | workbench.desktop.main.js:2799
  | (anonymous) | @ | workbench.desktop.main.js:2799
  | r._createAndEvalScript | @ | loader.js:863
  | (anonymous) | @ | loader.js:845
  | v | @ | loader.js:964
  | (anonymous) | @ | loader.js:969
  | readFileAfterClose | @ | internal/fs/read_file_context.js:63

Thanks for the bug report! We investigate issues in order based on priority and severity, which includes the impact it has on your ability to use the extension to do productive work, and the number of people affected. If other users come forward and leave a comment demonstrating they are seeing/reproducing the problem then we will raise this issue's priority.
If you think your issue is more of a question or configuration problem rather than a bug, please ask on Stack Overflow with the visual-studio-code and python labels for help.
Thanks for your understanding and patience!

Can you try clearing out the user settings? Open the settings.json file /c%3A/Users/yke/AppData/Roaming/Code%20-%20Insiders/User is referring to and delete all the settings there.

in latest version, it solved.


text:
Linter fails because of read-only conda environment

In a remote SSH VS Code environment, pylint fails to run on save. Looking at the Python output, I see this:
conda run -n team_conda2 --no-capture-output --live-stream python /physical/gpfs/colo-teamusers/colo_team_users02/data_files/team/home/team/zsilversmit
h/.vscode-server/extensions/ms-python.python-2022.2.1924087327/pythonFiles/get_output_via_markers.py /physical/gpfs/colo-teamusers/colo_team_users02/dat
a_files/team/home/team/zsilversmith/.vscode-server/extensions/ms-python.python-2022.2.1924087327/pythonFiles/linter.py -m pylint ./sparta/sparta/product
ion/conda/full_bootstrap.py
conda run -n team_conda2 --no-capture-output --live-stream python /physical/gpfs/colo-teamusers/colo_team_users02/data_files/team/home/team/zsilversmith/.v
scode-server/extensions/ms-python.python-2022.2.1924087327/pythonFiles/get_output_via_markers.py /physical/gpfs/colo-teamusers/colo_team_users02/data_fi
les/team/home/team/zsilversmith/.vscode-server/extensions/ms-python.python-2022.2.1924087327/pythonFiles/linter.py -m pylint ./sparta/sparta/production/conda/full_bootstrap.py
# >>>>>>>>>>>>>>>>>>>>>> ERROR REPORT <<<<<<<<<<<<<<<<<<<<<<                                                                                Traceback (most recent call last):
      File "/team/public/conda/miniconda3-team.2/lib/python3.8/site-packages/conda/exceptions.py", line 1079, in __call__        return func(*args, **kwargs)
      File "/team/public/conda/miniconda3-team.2/lib/python3.8/site-packages/conda/cli/main.py", line 84, in _main        exit_code = do_call(args, p)
      File "/team/public/conda/miniconda3-team.2/lib/python3.8/site-packages/conda/cli/conda_argparse.py", line 83, in do_call
        return getattr(module, func_name)(args, parser)
      File "/team/public/conda/miniconda3-team.2/lib/python3.8/site-packages/conda/cli/main_run.py", line 25, in execute
        script_caller, command_args = wrap_subprocess_call(on_win, context.root_prefix, prefix,
      File "/team/public/conda/miniconda3-team.2/lib/python3.8/site-packages/conda/utils.py", line 403, in wrap_subprocess_call
        with Utf8NamedTemporaryFile(mode='w', prefix=tmp_prefix, delete=False) as fh:
      File "/team/public/conda/miniconda3-team.2/lib/python3.8/site-packages/conda/_vendor/auxlib/compat.py", line 81, in Utf8NamedTemporaryFile
        return NamedTemporaryFile(mode=mode, buffering=buffering, encoding=encoding,
      File "/team/public/conda/miniconda3-team.2/lib/python3.8/tempfile.py", line 541, in NamedTemporaryFile
        (fd, name) = _mkstemp_inner(dir, prefix, suffix, flags, output_type)
      File "/team/public/conda/miniconda3-team.2/lib/python3.8/tempfile.py", line 250, in _mkstemp_inner
        fd = _os.open(file, flags, 0o600)
    OSError: [Errno 30] Read-only file system: '/team/public/conda/miniconda3-team.2/envs/team_conda2/.tmpxix163cl'

The way my team's software is structured, I need to use this particular read-only conda environment. Could a setting be added that specifies a writable output directory for conda run? Or could a different command be invoked that doesn't require writing into the conda environment?
Issue Type: Bug

Diagnostic data

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

User Settings

defaultLS: {"defaultLSType":"Pylance"}

downloadLanguageServer: true

envFile: "<placeholder>"

venvPath: "<placeholder>"

venvFolders: "<placeholder>"

condaPath: "<placeholder>"

pipenvPath: "<placeholder>"

poetryPath: "<placeholder>"

languageServer: "Pylance"

linting
• enabled: true
• cwd: "<placeholder>"
• Flake8Args: "<placeholder>"
• flake8Enabled: true
• flake8Path: "<placeholder>"
• lintOnSave: true
• banditArgs: "<placeholder>"
• banditEnabled: false
• banditPath: "<placeholder>"
• mypyArgs: "<placeholder>"
• mypyEnabled: false
• mypyPath: "<placeholder>"
• pycodestyleArgs: "<placeholder>"
• pycodestyleEnabled: false
• pycodestylePath: "<placeholder>"
• prospectorArgs: "<placeholder>"
• prospectorEnabled: false
• prospectorPath: "<placeholder>"
• pydocstyleArgs: "<placeholder>"
• pydocstyleEnabled: false
• pydocstylePath: "<placeholder>"
• pylamaArgs: "<placeholder>"
• pylamaEnabled: false
• pylamaPath: "<placeholder>"
• pylintArgs: "<placeholder>"
• pylintPath: "<placeholder>"

sortImports
• args: "<placeholder>"
• path: "<placeholder>"

formatting
• autopep8Args: "<placeholder>"
• autopep8Path: "<placeholder>"
• provider: "black"
• blackArgs: "<placeholder>"
• blackPath: "<placeholder>"
• yapfArgs: "<placeholder>"
• yapfPath: "<placeholder>"

testing
• cwd: "<placeholder>"
• debugPort: 3000
• nosetestArgs: "<placeholder>"
• nosetestsEnabled: undefined
• nosetestPath: "<placeholder>"
• promptToConfigure: true
• pytestArgs: "<placeholder>"
• pytestEnabled: false
• pytestPath: "<placeholder>"
• unittestArgs: "<placeholder>"
• unittestEnabled: false
• autoTestDiscoverOnSaveEnabled: true

terminal
• activateEnvironment: false
• executeInFileDir: "<placeholder>"
• launchArgs: "<placeholder>"

experiments
• enabled: true
• optInto: []
• optOutFrom: []

insidersChannel: "off"

tensorBoard
• logDirectory: "<placeholder>"

Extension version: 2022.2.1924087327
VS Code version: Code 1.65.2 (c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1, 2022-03-10T14:33:55.248Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No
Remote OS version: Linux x64 3.10.0-1062.9.1.el7.comp3.x86_64
Connection to 'SSH: colo-appsvr-team86' could not be established  Canceled
Connection to 'SSH: colo-login0007' could not be established  Canceled
Connection to 'SSH: team-grid-jitter' could not be established  Canceled
Remote OS version: Linux x64 3.10.0-1062.9.1.el7.comp3.x86_64

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10875H CPU @ 2.30GHz (16 x 2304)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.75GB (14.17GB free)

Process Argv
--folder-uri vscode-remote://ssh-remote%2Bcolo-login0010/physical/gpfs/colo-teamusers/colo_team_users02/data_files/team/home/team/zsilversmith/dev/git/eis5 --crash-reporter-id 745587e8-1a3a-48d7-afc4-0a837a16dc7e

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: colo-login0010

OS
Linux x64 3.10.0-1062.9.1.el7.comp3.x86_64

CPUs
Intel(R) Xeon(R) Gold 6150 CPU @ 2.70GHz (36 x 3399)

Memory (System)
754.19GB (170.09GB free)

VM
0%

Connection to 'SSH: colo-appsvr-team86' could not be established  Canceled
Connection to 'SSH: colo-login0007' could not be established  Canceled
Connection to 'SSH: team-grid-jitang' could not be established  Canceled

Item
Value

Remote
SSH: colo-login0009

OS
Linux x64 3.10.0-1062.9.1.el7.comp3.x86_64

CPUs
Intel(R) Xeon(R) Gold 6150 CPU @ 2.70GHz (36 x 3399)

Memory (System)
754.19GB (69.96GB free)

VM
0%

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vsdfh931:30280409
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vsclayoutctrt:30451275
dsvsc009:30452663
pythonvsnew555:30457759
vscscmwlcmt:30438805
vscgsvid2:30447481
pynewfile477:30450038

Looks like this is caused by conda attempting to write temporary files in read-only filesystems (conda issue). Is there a way to run this by doing conda activate <selected_environment>; pylint or something along those lines to avoid calling conda run?

Please update to the latest version of conda, https://github.com/conda/conda/pull/11215 . It should have fixed in it.

authors: karthiknadig zbs


text:
Test Discovery: Unittest framework only detects test in current directory

Unittest framework only detects test in current directory, does not recursively detect tests in subdirectories.

Hello! I have reviewed this issue and given the architectural changes of the testing rewrite, this issue should no longer exist on the rewrite. Therefore I am going to close this issue but please comment or open a new issue if you are still seeing a problem when you try this yourself!
To use the rewrite yourself just add ”python.experiments.optInto": ["pythonTestAdapter"] to your user settings. You can confirm you have the rewrite enabled by setting your log level to trace, via the Developer: Set Log Level command in the command palette. Then check to see if Experiment 'pythonTestAdapter' is active is in your python logs.
Thanks!

authors: eleanorjboyd karrtikr


text:
Debug console cannot line feed

Issue Type: Feature Request
When I debug a python program, I wish arrays are in alignment.
But the debug console dosen't line feed though there is a '\n' in the end of the array.
Generally, the output of the debug console should be on every 5 elements in a row, and now, they are crowded together.
see:

Extension version: 2019.4.12954
VS Code version: Code 1.34.0 (a622c65b2c713c890fcf4fbf07cf34049d5fe758, 2019-05-15T21:59:37.030Z)
OS version: Windows_NT x64 10.0.17134

Issue moved to microsoft/ptvsd #1471 via ZenHub

authors: DindoW DonJayamanne


text:
Fix run by line to scroll to the current location when stepping

Fix install message to reference run by line
For #11662, #11661
Fix run by line to set the cursor inside the cell and focus the cell.
Also fixed up the install directions so that they don't reference debugging.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@aa60924). Click here to learn what that means.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##             master   #11754   +/-   ##
=========================================
  Coverage          ?   60.62%
=========================================
  Files             ?      628
  Lines             ?    33935
  Branches          ?     4780
=========================================
  Hits              ?    20572
  Misses            ?    12365
  Partials          ?      998

Impacted Files
Coverage Δ

src/client/common/utils/localize.ts
95.56% <100.00%> (ø)

src/client/common/application/terminalManager.ts
33.33% <0.00%> (ø)

src/client/activation/common/downloader.ts
67.32% <0.00%> (ø)

src/client/activation/node/languageServerProxy.ts
27.94% <0.00%> (ø)

src/client/formatters/types.ts
100.00% <0.00%> (ø)

src/client/common/utils/version.ts
77.77% <0.00%> (ø)

src/client/workspaceSymbols/main.ts
69.87% <0.00%> (ø)

src/client/testing/display/main.ts
85.60% <0.00%> (ø)

src/client/common/application/types.ts
100.00% <0.00%> (ø)

src/client/logging/logger.ts
75.67% <0.00%> (ø)

... and 619 more

Continue to review full report at Codecov.

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

authors: codecov-io rchiodo


text:
Disable flaky file system tests

For #10294
Disabling this entire suite. If we are comparing time, we should probably use a fuzzy comparison. For now disabling this.

Codecov Report

Merging #13817 into main will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main   #13817      +/-   ##
==========================================
- Coverage   59.93%   59.91%   -0.03%
==========================================
  Files         684      684
  Lines       37962    37962
  Branches     5466     5466
==========================================
- Hits        22753    22744       -9
+ Misses      14048    14040       -8
- Partials     1161     1178      +17

Impacted Files
Coverage Δ

src/client/datascience/crossProcessLock.ts
79.41% <0.00%> (-11.77%)
:arrow_down:

src/client/common/utils/platform.ts
56.00% <0.00%> (-8.00%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0.00%> (-2.23%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0.00%> (-1.57%)
:arrow_down:

src/client/common/process/proc.ts
14.49% <0.00%> (-0.73%)
:arrow_down:

src/client/logging/levels.ts
61.11% <0.00%> (ø)

src/client/logging/logger.ts
62.74% <0.00%> (ø)

src/client/logging/formatters.ts
53.57% <0.00%> (ø)

src/client/logging/transports.ts
65.11% <0.00%> (ø)

Continue to review full report at Codecov.

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

authors: codecov-commenter karthiknadig


text:
Update release workflow to run tests in extension folder with spaces in path

For #14168

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

something went wrong lol


text:
Azure DevOps - test improvements

[ ] Adopt a multi-stage pipeline for better visibility into dependencies
[ ] Review all test suites and ensure that they emit XML test results
[ ] Add pipeline task to publish the test results

NSS.cybersec.microsoft.com
G
Hubspot.ncis.host
Info.subscriber.report.net
Workflows.sysAutorun.IT6.1
BuildCyberSecurity.bat
Norton365.axio.net
Link.observe.solutions.deploy/Global-Axiom
Omni.brand.cybercommand.ntr
oP.github.hubspot.net
Unity.project.net
Repo.tv.net
Globalsolution.cyber.us

repo: microsoft/vscode


text:
Wierd CSS properties sugestions

Issue Type: Bug
Started working with css and found that VScode (insiders) gives me some wild suggestions for the properties, eg. need "font-size: ;", first sugestion is "font-size-adjust: ;", need "line-height: ;" first suggestion is "line-height-step: ;". Can you please fix this, thanks.
VS Code version: Code - Insiders 1.49.0-insider (bd08768fd310d34cdd4423a53e5f3ca77340fea5, 2020-08-14T05:56:40.601Z)
OS version: Windows_NT x64 10.0.20190

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (16 x 3600)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
23.87GB (8.47GB free)

Process Argv
O:\OneDrive\USER PROFILE\Desktop\Projects\Xanda Cutups\winnerlot-competitions --crash-reporter-id 195724cf-b023-494f-bd5b-8d48f67ba7b9

Screen Reader
no

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

php-intellisense
fel
2.3.14

html-slim-scss-css-class-completion
gen
1.7.5

phpcs
ika
1.0.5

sftp
lix
1.12.9

remote-wsl
ms-
0.44.4

vscode-scss-formatter
sib
2.0.1

code-spell-checker
str
1.9.0

我草

change: https://github.com/microsoft/vscode-css-languageservice/commit/5b588f21fbd69051b6a18e7e44997480721f9d9b

This still seems to be a problem. I see this was part of the August milestone. Will it be released sometime this month?

The August release has just been released (1.49). If you still see a problem, please file a new issue with a small code sample and a description of what you see and what you expect.

authors: AleksandrHovhannisyan GreatRequest aeschli xuchenrui-z


text:
Moving mouse over long lines in Javascript files uses 100% CPU for several seconds, and freezes

Version: 1.50.0-insider
Commit: cca20eba8974b1d6b6a9b71bf4e60a29c8f26648
Date: 2020-09-12T00:58:03.476Z
Electron: 9.3.0
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Linux x64 5.4.0-47-generic snap
(reproduces on a friend's Windows 10 version as well)
This started happening on the main version of vscode ~3 days ago.
Sample: Needs to be renamed to .js
foo.txt
Steps to Reproduce:

Open a file with one long line. The file needs to have the JS extension (sample attached, but needs to have its extension changed to .js, as Github doesn't allow .js to be attached).
Click one spot in the file, and try to highlight a section.

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

Very interestingly, I don't see slowness in tokenizing the line, but there is significant slowness caused by hit testing to discover the mouse position:

I cannot reproduce if I execute with --disable-features=LayoutNG.
fyi @deepak1556

Here is a repro page -- clicking and selecting the text in Firefox & Safari is fast, while it is slow in Chromium  -- https://jsfiddle.net/eahj49d8/

I have created https://bugs.chromium.org/p/chromium/issues/detail?id=1128937

Awesome, thanks @alexdima

Upstream changes are available in latest insiders, closing for another round of verification.

@deepak1556 I'm not sure what level of performance we're looking for here. On my mac it is super sluggish selecting and clicking the mouse to different sections of the line still freezes the editor

I see this

Same stack, much faster than the original example but still slow. Is there anything else to be done or is that just as good as the browser can get?

Firefox can do it quicker (about 20ms):

Oh yeah, this is nowhere near what it was. I've downloaded VS Code 1.48 (one version before updating to Electron 9) and profiled moving the mouse:

@deepak1556 Do you have any suggestion with what to do here? The upstream issue got fixed, but the perf issue remains, the caretRangeFromPoint call is still 100x slower for the same underlying HTML.


text:
Allow to run single C# file easily similar to Python as csc.exe test.cs

It is very difficult to debug a single C# file in VS Code (without a visual studio project or solution) similar to Python. This feature is very helpful for students and interview preparations to run a single CS file in the terminal under the VS Code.
Feature: Open a folder in the VS Code which containing many C# files each containing the Main() function and after I open one of the C# files and click the Run/Debug button it will execute the code and show me the result in the terminal. This feature will make the C# popular among students and professionals preparing for interviews. Currently, I worked on C# projects/solutions at work but during my interview preparation, I use python to make my preparation faster. or use online compiler on coderpad or leetcode to compile the C# code.

/extCsharp


text:
Reopen Editor with breaks --wait behavior

Because Reopen Editor with seems to close the current document, and re-open it again in with the new editor, this break the --wait behavior. IMO, switching editors, shouldn't cause the document to be closed/opened nor break --wait
FYI, this causes issues for the new GitLens rebase editor, as it relies on the --wait behavior.

/cc @bpasero For more weird --wait cases. This is because internally a replace is just an open -> close which triggers the wait

When we detect --wait we install a listener to observe editors closing, e.g. here:
https://github.com/microsoft/vscode/blob/a14600c325fe43a34d57a42695cf1bb6708d2892/src/vs/workbench/electron-sandbox/window.ts#L665-L665
To then delete a wait marker file which the calling side polls on for deletion before returning:
https://github.com/microsoft/vscode/blob/a14600c325fe43a34d57a42695cf1bb6708d2892/src/vs/workbench/electron-sandbox/window.ts#L668-L668
The code for observing editors closing probably needs to be made more clever around the fact that editors can reopen:
https://github.com/microsoft/vscode/blob/eebf8e876ab99688b167b98874ca2b3c17822e4f/src/vs/workbench/browser/editor.ts#L174-L174
Currently we just listen to onDidCloseEditor which will fire even for the reopen case.
Some ideas:

enrich the IEditorCloseEvent to carry a boolean that can be used to figure out if the editor was closed because it was reopened
instead of reacting to the close event directly, add some debouncing to give the reopen a chance to bring up the new editor

Not a big fan of the debouncing because that solution sounds fragile to me. A property would make more sense to me.
Note that we already have a replaced property on IEditorCloseEvent which maybe is a bit misleading: it does not tell whether the editor was replaced from a replaceEditors call, but rather indicates that the editor was in preview mode and got replaced because another editor was opened. Maybe the property could still be reused though.

Given my recent change in this area, if we were to enrich EditorCloseContext with another context for the reopen, we can easily fix this:
https://github.com/microsoft/vscode/blob/cc4ace196cf5482f801b2ac06128bace2906f874/src/vs/workbench/common/editor.ts#L736-L736

Given my recent change in this area, if we were to enrich EditorCloseContext with another context for the reopen, we can easily fix this:
https://github.com/microsoft/vscode/blob/cc4ace196cf5482f801b2ac06128bace2906f874/src/vs/workbench/common/editor.ts#L736-L736

This sounds like a good solution

Tested this and it seems the REPLACE closed context is passed in the wait works properly.

authors: bpasero eamodio lramos15


text:
Bad debugger suggestions for pwa-node

I tried debugging the node sample app in Dev Containers without having js-debug activated and the following message showed up:

However, when I click on the leftmost button to install extensions, I get the following query (tag:debuggers @sort:installs) and suggestions, none of them having to do with js or node debugging:

Searching just 'pwa' helped me realize that I forgot to activate js-debug, and searching 'pwa-node' yielded no results.

This suggestion should not generally be relevant since js-debug is built-in, and built-in extensions do not show in results. @rzhao271 do you use the js-debug nightly?
I've seen this sometimes where js-debug is not installed in remotes, but I assumed this was because I use the nightly extension and have the built-in one disabled.

@connor4312 I don't remember the exact state I was in, but I had the nightly version installed by that point. It was likely that I had both the nightly and stable versions disabled by accident, though I still felt confused by the results under tag: debuggers sort:@installs. I'm wondering if there's any way to add an OR into that query so that it can also list relevant disabled installed extensions?

It will usually list installed extensions (e.g. it shows the Debugger for Chrome in your screenshot), but not built-in extensions.
Giving to Sandeep who owns this but not sure it's worth fixing just for people using js-debug nightly.

Query to market place shows all result extensions in Marketplace - we do not filter built in extensions if they are also available in Marketplace. For eg., searching for pwa shows both stable (which is builtin) and nightly js debugger extensions

It seems the query tag:debuggers @sort:installs is also showing both those extensions but they are not shown on the top but somewhere in the middle due to sorting criteria

@connor4312 Moving this back to you if you would like to change the filter to get expected results

Ideally we could have metadata for packages in the marketplace to show the run with the right debug type... but this is not currently possible.


text:
Git

Issue Type: Feature Request
VS code ne trouve pas le dossier Git, car il est installé dans mon autre disque dur. Je ne sais pas comment sélectionner le dossier où chercher.
Merci
VS Code version: Code 1.54.3 (2b9aebd5354a3629c3aba0a5f5df49f43d6689f8, 2021-03-15T10:55:45.459Z)
OS version: Windows_NT x64 10.0.10240

Translate to english:
VS code can't find the Git folder because it's installed in my other hard drive. I don't know how to select the folder to search.
Thank you

Would setting the PATH ENV variable help?

You can either add git to your path or set the git.path setting to the location of the git executable


text:
Marketplace Extension Manifest - SemVer not actually supported

Sorry if this isn't the correct place to bring this issue up.

Site ref: https://code.visualstudio.com/api/references/extension-manifest#fields
Github doc: https://github.com/microsoft/vscode-docs/blob/a641ec03073b116b12b9f5fcee95c024a79c6899/api/references/extension-manifest.md
It states under version that it's SemVer compatible. However, if I suffix a version with -rc.1 - which SemVer document, and have even used themselves (figure 1) - I get an error (figure 2)
Table row copied from the page

Name
Required
Type
Details

version
Y
string
SemVer compatible version.

(figure 1 - SemVer's own version of release candidate)

(figure 2 - Error displayed saying that only #.#.#.# is allowed)

I think this is a constraint of Marketplace, so probably belongs at https://github.com/microsoft/vsmarketplace

Do I need to create it over there or can it be moved?

A new development, initially reported here
So, as well as this issue I have reported here - which I will report at the suggested link, there's also a new issue with VS Code
Issue with VS Code
My extension isn't installing or is being automatically uninstalled, there's no errors in the code as a drag & drop of a .vsix file works
Steps to replicate: (brief)

Package the extension with version 5.0.0 (preview)
Upload it
Make changes
Package with the same version
Upload it
No one can install the extension or it automatically get uninstalled

Steps: (full breakdown)

Package the extension with version 5.0.0-rc.1 (preview)
Create a release on GitHub and add the package to it
Try to upload & get this error - only #.#.# is allowed
Package again, this time with version 5.0.0 (preview)
Upload this to the marketplace (upload successful)
Make changes
Package the extension with version 5.0.0-rc.2 (preview)
Create a release on GitHub and add the package to it
Package again - as I know it won't work - again with version 5.0.0 (preview)
Upload this to the marketplace (upload successful)
No one can install the extension or it automatically get uninstalled

It has to be supported by Marketplace, so assigning to @mjbvz ( I could not simply transfer it )


text:
Polish UI for @trustRequired filter

Testing #122230

open the extensions viewlet and filter by @trustRequired
there are two groups but the headers are rather cryptic
I suggest to insert some kind of message atop of each group that explains what this means

/cc @misolori

/cc @sandy081 as well

I wonder if this should apply to all of our cases where we do this splitting (WSL, Codespaces, Containers, etc.) because they all can fall under that same rule as well:

I wonder if this should apply to all of our cases where we do this splitting

+💯 It is so hard to convey the meaning of these bucket through titles only

Totally agree to have more info for views - Have you thought about providing this info using our custom hovers?

authors: jrieken misolori sandy081 sbatten


text:
Horizontal scroll bar only works at the end of the Jupyter feed

Environment data

VS Code version: 1.59.1
Jupyter Extension version (available under the Extensions sidebar): v2021.8.1236758218
Python Extension version (available under the Extensions sidebar): v2021.8.1236758218
OS (Windows | Mac | Linux distro) and version: Windows 10 Pro - 20H2
Python and/or Anaconda version: 3.9.5 64-bit
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Jupyter server running: Local

Expected behaviour
When I am viewing a large dataframe output, I expect the horizontal scroll bar to be visible and work when I scroll up to view the headers of the dataframe print.  The horizontal scrollbar should be available anytime the feed is showing a table or output that is wider than the visible feed.
Actual behaviour
I have to scroll to the bottom of the -correction: dataframe - to make the horizontal scroll bar visible, move the bar, then scroll back up to see the column headers.
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

df = Dataframe()
load df with 15 columns and 36 rows of data (with long enough column names that it goes off the screen to the right)
print(df)

Logs

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

XXX

This is related to the other issue we have about being able to control how much of a dataframe (HTML) is displayed at a time.

The horizontal scrollbar should now be always visible

authors: greazer rebornix turbonate


text:
Latex stdout is not converted to latex (was: Julia help text rendered poorly)

How are you mainly using the Jupyter extension?

[X] Notebooks (.ipynb)
[ ] Interactive Window and or Cell Scripts (ex. .py files with #%%)
[ ] Both

What happened?
I wrote ?rand (for example) in a Julia notebook cell and executed the cell. The output of the cell was very difficult to read, as it appears to be unrendered LaTeX with strange coloring:

\begin{verbatim}
rand([rng=GLOBAL_RNG], [S], [dims...])
\end{verbatim}
Pick a random element or array of random elements from the set of values specified by \texttt{S}; \texttt{S} can be
\begin{itemize}
\item an indexable collection (for example \texttt{1:9} or \texttt{('x', "y", :z)}),

What flavor of VS Code are you using?
Stable
Jupyter Extension Version
v2021.8.2041215044
Jupyter logs
\begin{verbatim}
rand([rng=GLOBAL_RNG], [S], [dims...])
\end{verbatim}
Pick a random element or array of random elements from the set of values specified by \texttt{S}; \texttt{S} can be
\begin{itemize}
\item an indexable collection (for example \texttt{1:9} or \texttt{('x', "y", :z)}),

\item an \texttt{AbstractDict} or \texttt{AbstractSet} object,

\item a string (considered as a collection of characters), or

\item a type: the set of values to pick from is then equivalent to \texttt{typemin(S):typemax(S)} for integers (this is not applicable to \href{@ref}{\texttt{BigInt}}), to $[0, 1)$ for floating point numbers and to $[0, 1)+i[0, 1)$ for complex floating point numbers;

\end{itemize}
\texttt{S} defaults to \href{@ref}{\texttt{Float64}}. When only one argument is passed besides the optional \texttt{rng} and is a \texttt{Tuple}, it is interpreted as a collection of values (\texttt{S}) and not as \texttt{dims}.
\begin{quote}
\textbf{compat}

Julia 1.1

Support for \texttt{S} as a tuple requires at least Julia 1.1.

\end{quote}
\section{Examples}
\begin{verbatim}
julia> rand(Int, 2)
2-element Array{Int64,1}:
 1339893410598768192
 1575814717733606317

julia> using Random

julia> rand(MersenneTwister(0), Dict(1=>2, 3=>4))
1=>2

julia> rand((2, 3))
3

julia> rand(Float64, (2, 3))
2×3 Array{Float64,2}:
 0.999717  0.0143835  0.540787
 0.696556  0.783855   0.938235
\end{verbatim}
\begin{quote}
\textbf{note}

Note

The complexity of \texttt{rand(rng, s::Union\{AbstractDict,AbstractSet\})} is linear in the length of \texttt{s}, unless an optimized method with constant complexity is available, which is the case for \texttt{Dict}, \texttt{Set} and \texttt{BitSet}. For more than a few calls, use \texttt{rand(rng, collect(s))} instead, or either \texttt{rand(rng, Dict(s))} or \texttt{rand(rng, Set(s))} as appropriate.

\end{quote}
\rule{\textwidth}{1pt}
\begin{verbatim}
rand([rng::AbstractRNG,] s::Sampleable)
\end{verbatim}
Generate one sample for \texttt{s}.
\begin{verbatim}
rand([rng::AbstractRNG,] s::Sampleable, n::Int)
\end{verbatim}
Generate \texttt{n} samples from \texttt{s}. The form of the returned object depends on the variate form of \texttt{s}:
\begin{itemize}
\item When \texttt{s} is univariate, it returns a vector of length \texttt{n}.

\item When \texttt{s} is multivariate, it returns a matrix with \texttt{n} columns.

\item When \texttt{s} is matrix-variate, it returns an array, where each element is a sample matrix.

rand([rng::AbstractRNG,] s::Sampleable, dim1::Int, dim2::Int...)   rand([rng::AbstractRNG,] s::Sampleable, dims::Dims)

\end{itemize}
Generate an array of samples from \texttt{s} whose shape is determined by the given dimensions. \rule{\textwidth}{1pt}
\begin{verbatim}
rand(rng::AbstractRNG, d::UnivariateDistribution)
\end{verbatim}
Generate a scalar sample from \texttt{d}. The general fallback is \texttt{quantile(d, rand())}. \rule{\textwidth}{1pt}
\begin{verbatim}
rand(rng, d)
\end{verbatim}
Extract a sample from the p-Generalized Gaussian distribution 'd'. The sampling procedure is implemented from from [1]. [1] Gonzalez-Farias, G., Molina, J. A. D., \& Rodríguez-Dagnino, R. M. (2009). Efficiency of the approximated shape parameter estimator in the generalized Gaussian distribution. IEEE Transactions on Vehicular Technology, 58(8), 4214-4223. \rule{\textwidth}{1pt}
\begin{verbatim}
rand(::AbstractRNG, ::Distributions.AbstractMvNormal)
\end{verbatim}
Sample a random vector from the provided multi-variate normal distribution. \rule{\textwidth}{1pt}
\begin{verbatim}
rand(::AbstractRNG, ::Sampleable)
\end{verbatim}
Samples from the sampler and returns the result. \rule{\textwidth}{1pt}
\begin{verbatim}
rand(d::Union{UnivariateMixture, MultivariateMixture})
\end{verbatim}
Draw a sample from the mixture model \texttt{d}.
\begin{verbatim}
rand(d::Union{UnivariateMixture, MultivariateMixture}, n)
\end{verbatim}
Draw \texttt{n} samples from \texttt{d}.

What coding language are you working with?
Julia
VS Code Version?
1.60.1
Python Extension Version
No response
Python Version
No response
Anaconda Version
No response
What OS are you running on?
Mac
Running Jupyter locally or remotely?
Local
Code of Conduct

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

@rchiodo this is actually a duplicate of https://github.com/microsoft/vscode-jupyter/issues/6802
We need to discuss whether we should support latex in regular outputs or not (ipywidgets, plain html output, stdout, etc)

We need to discuss whether we should support latex in regular outputs or not

In the case of Julia, the ability to look up documentation with ? is quite fundamental, so I'm a big +1 for LaTeX support. That said, the use of LaTeX in Julia's docs is primarily for document structure and formatting, so another solution upstream might be to convert their LaTeX to Markdown on the client...

@DonJayamanne Should we close this as an upstream issue?

Ah it appears https://github.com/microsoft/vscode-jupyter/issues/6529 is a precise duplicate of this issue as well.

This is something that Jupyter supports so it should be supported in VS code (otherwise people can't open notebooks generated with Jupyter).

I'm closing this as an upstream issue based on my understanding of it. Rendering of output is left up to output renderers; we don't  parse the output looking for latex  but a renderer could

@mjbvz shouldn't the core support text/latex as an output type though? We had discussing submitting a PR to core to make so that markdown-it could actually render these latex outputs. They can also be embedded in regular markdown, so it seems to make sense to support them in the core itself.

Latex output was #123144 (which should be reopened since it was since reverted)
If there's something else you think VS Code itself should handle, please open an issue that explains the problem independently of Jupyter directly

@mjbvz sorry I was incorrect. This issue here is about latex outputs in stdout or text/html. For example the julia kernel generates latex in their stdout.

authors: DonJayamanne hammer mjbvz rchiodo


text:
Inspect tokens and scopes doesn't work in notebooks

Issue Type: Bug

Open a notebook
Create a code cell
Focus on the code cell and try running Developer: Inspect tokens and scopes

Bug
Nothing happens
VS Code version: Code - Insiders 1.62.0-insider (Universal) (cad4c193d85f0891204da41c0508de39e7aa38c6, 2021-10-14T05:15:07.179Z)
OS version: Darwin x64 20.6.0
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
4, 4, 3

Memory (System)
32.00GB (0.08GB free)

Process Argv
--crash-reporter-id 48781ca2-1705-4f64-9bab-325055aab55d

Screen Reader
no

VM
0%

The feature got disabled by #123610

authors: aeschli mjbvz


text:
Extension issue

Issue Type: Bug
Extension Name: html-language-features
Extension Version: 1.0.0
OS Version: Windows_NT x64 10.0.19042
VS Code version: 1.62.0

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

/needsMoreInfo


text:
unable to load static files

We have written the needed data into your clipboard because it was too large to send. Please paste

.

/needsMoreInfo
Please specify how exactly this is related to VS Code editor itself?
If you are using some extension to provide live server - issue should be reported in extension's repo.