text:
Require MFA

Feature Request
Is your feature request related to a problem?
As a partner, who is required to authenticate using MFA, I am frustrated when the connector does not work as expected because the user account used to authenticate was not challenged for MFA due to way Identity Security Defaults works.
Describe the solution you would like
The connector should require MFA

This can be accomplished by adding the amr_values query string parameter with a value of mfa to the StartLogin method. When implemented the code would look like
StartLogin = (resourceUrl, state, display) =>
    let
        authorizeUrl = authorize_uri & "?" & Uri.BuildQueryString([
            client_id = client_id,
            redirect_uri = redirect_uri,
            state = state,
            scope = "offline_access https://graph.microsoft.com/.default",
            response_type = "code",
            response_mode = "query",
            login = "login",
            amr_values = "mfa"
        ])
    in
        [
            LoginUri = authorizeUrl,
            CallbackUri = redirect_uri,
            WindowHeight = 860,
            WindowWidth = 1024,
            Context = null
        ];

repo: microsoft/secmgmt-insights-connector


text:
Java: Return response from OpenAPI functions differ between Python and .NET

In .NET, responses from OpenAPI functions get wrapped in a RestApiOperationResponse object. This does not happen in Python or Java. Because of this, the behavior between the languages differs.
There should be a test to validate that the responses from OpenAPI function are identical and a proposal should be provided to align the two SDKs.

Java repo moved, will check if this is still the case.

source: gharchive/issue

repo: microsoft/semantic-kernel

license: MIT

license_type: permissive

license_source: github-api


text:
Make Semantic Kernel (mostly) NativeAOT / trimming compatible

Motivation and Context
Enable SK assemblies to be used in NativeAOT applications (mostly) safely.
Description
There are still some warnings, mostly due to dependencies that aren't trimming-safe.  This also doesn't add any CI validation, which we can follow-up on subsequently to help ensure this doesn't regress.
Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
[x] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with dotnet format
[x] All unit tests pass, and I have added new tests where possible
[ ] I didn't break anyone :smile:

cc: @eerhardt, @eiriktsarpalis

Enable SK assemblies to be used in NativeAOT applications (mostly) safely.

Were you able to remove any dependencies from JsonStringEnumConverter? If not, serialization is almost guaranteed to fail at runtime in AOT.

Were you able to remove any dependencies from JsonStringEnumConverter

It's not used by the core assemblies. It's used by some of the exterior skills. That's part of the "mostly".
What would you suggest? Implement a custom converter for each?

What would you suggest? Implement a custom converter for each?

I would suppose it depends on whether we're planning to support AOT in these additional components. We could either wait until these are properly supported in .NET 8 or write an AOT-safe enum converter. I think just copying the generic converter implementation and using that directly without factories should suffice.

@dluc / @shawncal, this is ready for review when you get a chance.  The core SK assemblies as of this PR are ready for nativeaot, as are some of the other skill libraries, but there are a few that are problematic, e.g. the GRPC skill library is using reflection emit, which is a no-no for nativeaot.  This is also only about the SK assemblies themselves; many of the other dependencies they rely on are not necessarily usable yet with nativeaot, e.g. the Azure OpenAI library.  I will separately follow-up on adding some kind of CI protection for this so that we don't regress.

As there hasn't been a ton of interest in this, we downgraded the dependency for System.Text.Json back to .NET 6 (and there were necessary bug fixes in .NET 7 to enable this), and this does add a bit of additional burden on devs working in these libraries, I'm going to close this for now.

source: gharchive/pull-request

authors: eiriktsarpalis stephentoub


text:
.Net: move maxtokens property to base config

Motivation and Context

Description

Contribution Checklist

[ ] The code builds clean without any errors or warnings
[ ] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[ ] All unit tests pass, and I have added new tests where possible
[ ] I didn't break anyone :smile:

/sk generate-pr-description


text:
fixed issue 186

#186

#314

repo: microsoft/semantic-link-labs


text:
Reading EventData properties in spring cloud stream binder

Is there any way to get properties of EventType using @StreamListener(Sink.INPUT) message handling?
I am only able to get the event type payload.
Snapshot Code for Reproduce
@Slf4j
@EnableBinding(Sink.class)
public class EventhubSink {

  @StreamListener(Sink.INPUT)
  public void handleMessage(String payload, @Header(AzureHeaders.CHECKPOINTER) Checkpointer checkpointer) {
    checkpointer.success().handle((r, ex) -> {
      if (ex == null) {
        log.info("checkpointed {}", payload);
      }
      return null;
    });
  }
}

Thanks for reporting this. Could you clarify your issue?

What do you mean exactly by EventType? Is this a custom header or property you passed in? If so, you can use @Header("eventType") EventType eventType

Oh, I am sorry, I meant com.microsoft.azure.eventhubs.EventData (EventDataImpl).
My producer creates message using EventDataImpl - add some properties to it and then sends it to EventHub.
Then I've got two implementatrions:

Spring-cloud-stream-binder where I cannot get the properties out of the received message all I can get are Headers  and  paylod as either byte[] or Object(String)
azure-spring-messaging where in listener under  @AzureMessageListener I can work with full EventData object without any problems

Currently, event hub stream binder can't directly accept EventData like below:
@StreamListener(Sink.INPUT)
  public void handleMessage(EventData eventData) {}

The design of binder is to decouple with specific message format such as EventData. If you just want to add some custom headers, you can use spring Message.

No update on this issue, close it.

repo: microsoft/spring-cloud-azure


text:
Azure Active Directory authentication login failed

Describe the bug
Login failed with Azure Active Directory authentication at Query Editor
What happened?
When I try to Sign-in at Query Editor with Azure Active Directory authentication at SQL database then the login failed with the message " Login failed for user ''. The server is not currently configured to accept this token".
The Screenshot attached:-

What did you expect to happen?
Log-in should not be failed
How would you reproduce the bug?

Go to SQL Database
Go to Query editor (preview).
Login with Azure Active Directory authentication.

Did this happen via Desktop and/or Smartphone?
Desktop
Operating System
Windows 11
What browsers are you seeing the problem on?
Chrome
Version
No response
Device
No response
What is your current role?
Student Ambassador
What technical topic is this bug related to?
Application Development, Developer Tools, Other
Relevant log output
No response

SAME!!, I am experiencing the same issue.

repo: microsoft/studentambassadors


text:
Split tab uses wrong path for new session

Windows Terminal version
1.14.2281.0
Windows build number
10.0.19044.0
Other Software
No response
Steps to reproduce
Start wt in some place.
Start new wt tab in other place. Split new tab.

Expected Behavior
Splited tab have same paths on both sides.
Actual Behavior
New session have same path as when first instance of wt started

Duplicate of #13861 because GH shows 500 on first try

repo: microsoft/terminal


text:
Resizing WT window with nvim causes flickering.

Windows Terminal version
1.19.10573.0
Windows build number
10.0.22631.0
Other Software
nvim 0.9.0
Steps to reproduce
Open nvim, then resize the window.
Expected Behavior
It should redraw the content smoothly.
Actual Behavior
Flickering.
Also tried Helix, same.

Thanks for filing! This is caused by the alt buffer whenever it resizes. This is something that will require an ecosystem change to move towards synchronized updates. We're tracking this over in #8331.
Marking as /dup of #8331

@carlos-zamora Thanks for your reply.
But I don't think it is dup. The classic CMD, Ubuntu and Linux Mint default terminal do not suffer from this.
It's more like a rendering issue. If nvim set to a colorscheme with background, it's very obvious. Not drawing in an intermediate state but just flickering, like the old GDI without double buffering on a slow computer.
Sorry to post a new comment on a closed issue.

authors: carlos-zamora flyingcat


text:
test without namespace causes null ref

The following class
using Microsoft.VisualStudio.TestTools.UnitTesting;

[TestClass]
public class UnitTest1
{
    [TestMethod]
    public void TestMethod1()
    {
    }
}

in this project
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>net48</TargetFramework>
    <IsPackable>false</IsPackable>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="16.10.0" />
    <PackageReference Include="MSTest.TestAdapter" Version="2.2.4" />
    <PackageReference Include="MSTest.TestFramework" Version="2.2.4" />
    <PackageReference Include="coverlet.collector" Version="3.0.3">
      <PrivateAssets>all</PrivateAssets>
      <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
    </PackageReference>
  </ItemGroup>

</Project>

produces
PS C:\Code\TestProject1> dotnet test
  Determining projects to restore...
  Restored C:\Code\TestProject1\TestProject1\TestProject1.csproj (in 205 ms).
  You are using a preview version of .NET. See: https://aka.ms/dotnet-core-preview
  TestProject1 -> C:\Code\TestProject1\TestProject1\bin\Debug\net48\TestProject1.dll
Test run for C:\Code\TestProject1\TestProject1\bin\Debug\net48\TestProject1.dll (.NETFramework,Version=v4.8)
Microsoft (R) Test Execution Command Line Tool Version 17.0.0-preview-20210512-01
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
[MSTest][Discovery][C:\Code\TestProject1\TestProject1\bin\Debug\net48\TestProject1.dll] MSTestAdapter failed to discover tests in class 'UnitTest1' of assembly 'C:\Code\TestProject1\TestProject1\bin\Debug\net48\TestProject1.dll' because Object reference not set to an instance of an object..
No test is available in C:\Code\TestProject1\TestProject1\bin\Debug\net48\TestProject1.dll. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.

PS C:\Code\TestProject1>

Repro

NamespacelessTest.zip

Env

Windows 10
.NET SDK (6.0.100-preview.5.21302.13)

AB#1633111

@SimonCropp thanks for your feedback.

@SimonCropp  this needs to be fixed in our FQN code. We are assuming that there is always an interface there.

Hi @SimonCropp! Sorry it took us so much time to answer and fix your issue.
I have linked a PR that adds an integration test to show issue is fixed and ensures we don't regress.
We will include this change as part of release v3 of MSTest. We cannot ship it as a 2.2.11 release as we were forced to drop support of some .NET Framework to bump the version of Test Platform we are using.

@Evangelink thanks so much. please reach out if you need someone to do some beta testing of version 3

With pleasure! I will ping you when we release the preview version. Thanks!

Hey @SimonCropp, we just released a pre-release version of MSTest v3.0.0. If you are still up to do some beta testing, we would really like to get your feedback as there are lots of cleanup/infra/bug fixes included already.

@Evangelink yep it now works with test that have no namespace.

Awesome thanks! If you are encountering any issue/regression with this pre-release, please raise an issue in the repo and we will make it high prio.

authors: Evangelink Haplois SimonCropp nohwnd

repo: microsoft/testfx


text:
[http-server-csharp] operations with normal response and error response is generated to return JsonNode

In todoApp, we have this operation:
  @get op get(@path id: TodoItem.id): TodoItem | NotFoundResponse;

but the generated operation for this is:
    public interface ITodoItemsOperations
    {
        Task<JsonNode> GetAsync(long id);
    }

which is not a really good API.
Other operations are returning the WithStandardErrors<T | NotFoundResponse> but they work fine.

This is about rendering of unions, which we are handlign with a separate issue

authors: ArcturusZhang markcowl

repo: microsoft/typespec


text:
CSharp Service Emitter

Fixes #3141

:x: There is undocummented changes. Run chronus add to add a changeset or click here.
The following packages have changes but are not documented.

:x:@typespec/service-generator-csharp

You can try these changes at https://cadlplayground.z22.web.core.windows.net/prs/2904/
Check the website changes at https://tspwebsitepr.z22.web.core.windows.net/prs/2904/

You can try these changes here

🛝 Playground
🌐 Website
📚 Next docs

Fixes #3141

Happy end of July/start of July! 🎉
Just wanted to say how I’m excited to try this out and to say thank you for all the work on TypeSpec. I continue to watch the project grow 😃

authors: azure-sdk connorjs markcowl


text:
mpfr build failure

Host Environment

OS: osx
Compiler: apple Clang 12.0

To Reproduce
Steps to reproduce the behavior:
./vcpkg install mpfr
**Failure logs**
Computing installation plan...
The following packages will be built and installed:
    mpfr[core]:x64-osx
  * mpir[core]:x64-osx
Additional packages (*) will be modified to complete this operation.
Starting package 1/2: mpir:x64-osx
Building package mpir[core]:x64-osx...
-- Downloading http://mpir.org/mpir-3.0.0.tar.bz2...
-- Extracting source /Users/amir/projects/github-code/vcpkg/downloads/mpir-3.0.0.tar.bz2
-- Using source at /Users/amir/projects/github-code/vcpkg/buildtrees/mpir/src/3.0.0-a3f571144a
-- Configuring x64-osx-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
    Command failed: /Users/amir/projects/github-code/vcpkg/buildtrees/mpir/src/3.0.0-a3f571144a/configure --prefix=/Users/amir/projects/github-code/vcpkg/packages/mpir_x64-osx/debug --disable-silent-rules --enable-gmpcompat --enable-cxx --enable-static --disable-shared --with-sysroot=/Users/amir/projects/github-code/vcpkg/installed/x64-osx/debug
    Working Directory: /Users/amir/projects/github-code/vcpkg/buildtrees/mpir/x64-osx-dbg
    Error code: 1
    See logs for more information:
      /Users/amir/projects/github-code/vcpkg/buildtrees/mpir/configure-x64-osx-dbg-out.log
      /Users/amir/projects/github-code/vcpkg/buildtrees/mpir/configure-x64-osx-dbg-err.log

Call Stack (most recent call first):
  ports/mpir/portfile.cmake:39 (vcpkg_execute_required_process)
  scripts/ports.cmake:76 (include)

Error: Building package mpir:x64-osx 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: mpir:x64-osx
  Vcpkg version: 2020.02.04-unknownhash

Additionally, attach any relevant sections from the log files above.

Additional context
Add any other context about the problem here, such as what you have already tried to resolve the issue.
It was installed successfully with "Vcpkg package management program version 2020.06.15-unknownhash" version.

My final intention is to install cgal, but looks like gmp and mpir have conflicts.

autoconf-x64-osx-err.log
autoconf-x64-osx-out.log

Yes, mpir conflicts with gmp.

@ghamarian ,Thanks for posting this issue.
This is duplicated with issue #243 .
You have to install autoconf-archive in order to fix this.

Thanks, @JonLiu1993  brew install autoconf-archive resolved the issue.

authors: JackBoosY JonLiu1993 ghamarian

repo: microsoft/vcpkg


text:
[tesseract] update to <5.0.1>

Library name: tesseract
New version number: 5.0.1
Other information that may be useful (release notes, etc...)
https://github.com/tesseract-ocr/tesseract/releases/tag/5.0.1

FYI, there is a draft PR for updating Tesseract already started, PR #23101 if you want to take a look at it.

Duplicate of #16019

authors: JonLiu1993 bakashigure wrosecrans


text:
[intel-mkl] msvc msbuild linker failure

Operating system
Windows 11
Compiler
MSVC
Steps to reproduce the behavior
Clean machine, with no intel mkl libs installed anywhere.

vcpkg install intel-mkl

build a project requiring a mkl function:

I'm using a custom static lib triplet with:
set(VCPKG_TARGET_ARCHITECTURE x64)
set(VCPKG_CRT_LINKAGE static)
set(VCPKG_LIBRARY_LINKAGE static)

Failure logs
1>Cmn64_Src_Dsp.obj : error LNK2019: unresolved external symbol DftiCreateDescriptor referenced in function "void __cdecl Dsp::Intel::FftSetupReal(struct DFTI_DESCRIPTOR * &,enum DFTI_CONFIG_VALUE,unsigned __int64)" (?FftSetupReal@Intel@Dsp@@YAXAEAPEAUDFTI_DESCRIPTOR@@W4DFTI_CONFIG_VALUE@@_K@Z)
and many more
Additional context
This occurs with the updated port file that installs intel-mkl into the vcpkg/installed folder.
Libs are install into: vcpkg/installed//lib/intel64
But linking is done with: vcpkg/installed//lib/*.lib
Copying the files from: vcpkg/installed//lib/intel64
to: vcpkg/installed//lib/
and rebuilding works correctly.

Ran into the same issue, "LNK2019: unresolved external symbol dss_create_ referenced in function...."
Manifest mode ("dependencies": ["intel-mkl"]), x64-windows-static-md, manually copying .lib files work.

authors: Henrik-Norgren reid-p


text:
Gtk-WARNING **: Could not find the icon

Gtk-WARNING **: Could not find the icon 'window-minimize-symbolic-ltr'. The 'hicolor' theme
was not found either, perhaps you need to install it.
You can get a copy from:
http://icon-theme.freedesktop.org/releases

I encountered this problem on windows 10 as well, the fix is fairly simple.
You just have to run msys2 (which is installed to vcpkg/downloads/tools/msys2 when you get gtkmm I think) and use 'pacman' to install either mingw32/mingw-w64-i686-adwaita-icon-theme or mingw64/mingw-w64-x86_64-adwaita-icon-theme.
Then after its installed you create a directory 'shared' in your build directories, and copy the icons directory from msys/mingw64/share/ to your build/share directory.
After that the app should be able to locate the icons properly.

Thanks for posting this issue. Please open a new issue if this is still a problem for you.

Just to confirm, is this a symptom of #6554?

my share/icons folder has Adwaita and hicolor icons folder.when I run gtk app, there is no warning message display , but icons doesn't showed correctly on titlebar, same as "ishaantantra" report

I encountered this problem on windows 10 as well, the fix is fairly simple.
You just have to run msys2 (which is installed to vcpkg/downloads/tools/msys2 when you get gtkmm I think) and use 'pacman' to install either mingw32/mingw-w64-i686-adwaita-icon-theme or mingw64/mingw-w64-x86_64-adwaita-icon-theme.
Then after its installed you create a directory 'shared' in your build directories, and copy the icons directory from msys/mingw64/share/ to your build/share directory.
After that the app should be able to locate the icons properly.

Are you sure msys2 is installed via gtkmm? I just tried vcpkg install gtkmm:x64-windows and the build was a success, but there is no msys2 under vcpkg/downloads/tools.

share/icons

my share/icons folder has Adwaita and hicolor icons folder.when I run gtk app, there is no warning message display , but icons doesn't showed correctly on titlebar, same as "ishaantantra" report

Where exactly is your share/icons located? The full path or relative path to vcpkg root?

I encountered this problem on windows 10 as well, the fix is fairly simple.
You just have to run msys2 (which is installed to vcpkg/downloads/tools/msys2 when you get gtkmm I think) and use 'pacman' to install either mingw32/mingw-w64-i686-adwaita-icon-theme or mingw64/mingw-w64-x86_64-adwaita-icon-theme.
Then after its installed you create a directory 'shared' in your build directories, and copy the icons directory from msys/mingw64/share/ to your build/share directory.
After that the app should be able to locate the icons properly.

Are you sure msys2 is installed via gtkmm? I just tried vcpkg install gtkmm:x64-windows and the build was a success, but there is no msys2 under vcpkg/downloads/tools.

You install mingw-w64-x86_64-adwaita-icon-theme using  pacman -S mingw-w64-x86_64-adwaita-icon-theme.
Find the share folder in msys2
<path-to-msys64>\mingw64\share e.g.- C:\msys64\mingw64\share
Here you locate icons folder and copy it to
<path-to-vcpkg>\installed\x64-windows\share e.g.- D:\vcpkg\installed\x64-windows\share
All warnings regarding could not icon are resolved from this.
Kindly note this is the procedure for 64-bit version same can be modified for 32-bit version.

@ishaantantra Thank you! Figured that out myself though. But it's a shame that icons and themes are N/A with vcpkg.

@kakyoism I completely agree with you. If Gtk needs the icons, then icons therefore are a dependency, and something vcpkg should handle automatically.

So are their any plans to include the icons? Or do we have to manually install them?

My code to show the path:
  /* icon theme "D:/vcpkg/installed/x64-windows/share/icons" */
  GtkIconTheme* icon_theme = gtk_icon_theme_get_default();
  gchar** path;
  gint n_elements;

  gtk_icon_theme_get_search_path(icon_theme,
    &path, &n_elements);

  g_print("\n\n icons theme: %s, element#: %d\n\n", *path, n_elements);

Now, run your code to find the path on the console:
 invalid for instance '000002ECD36AF8F0' of type 'preview-image'

 icons theme: C:\Users\Homan\AppData\Local\icons, element#: 12

(basic-tutorial-5.exe:32428): GLib-GObject-WARNING **: 10:10:12.532: ../gobject/gsignal.c:2529: signal 'realize' is invalid for instance '000002ECD12B9210' of type 'video/x-h265, stream-format=(string)byte-stream, alignment=(string)au, profile=(string){ main, main-10 }, width=(int)[ 64, 8192 ], height=(int)[ 64, 8192 ]'

Copy the icons from: C:\msys64\mingw64\share\icons
to YOUR path: C:\Users\ YOUR ACCOUNT \AppData\Local\icons
ICONS FIXED!

authors: filipwtf furkcom homandiy ishaantantra kakyoism ketsuban phanalax sam20908 wangli28


text:
CGAL doesn't automatically pull in mpir and mpfr

I had to manually add linker references to the vcpkg MPIRand MPFR libraries in order to successfully link a program that uses CGAL

Hi @rkcarroll,
Can you provide more information? How did you build this library? And what information did vcpkg gives to you?
Thanks.

I'd also like to know!

Honestly, it's been a few weeks since I made the original post, so I can't guarantee the accuracy of this statement, but here is what I remember:  CGAL references MPIR and MPFR; however, installing vcpkg's CGAL package does not automatically install the vcpkg MPIR's and MPFR's packages.  I don't think the Linux version of CGAL requires these packages, btw.  Anyway, manually installing the vcpkg MPIR and MPFR fixes the problem.

Ah, I've tried pre-installing mpir(which works) and mpfr (which doesn't -- see https://github.com/Microsoft/vcpkg/issues/5910).

I installed CGAL successfully with VS2017 15.9.11 and VCPKG latest source on Windows 10. Its dependencies contain MPIR and MPFR. This is my build log.

PS F:\vcpkg> .\vcpkg.exe install cgal
The following packages will be built and installed:
/ * boost-any[core]:x86-windows
/ * boost-bimap[core]:x86-windows
......
/    cgal[core]:x86-windows
/  * liblzma[core]:x86-windows
/  * mpfr[core]:x86-windows
/  * mpir[core]:x86-windows
/  * zstd[core]:x86-windows
Additional packages (*) will be modified to complete this operation.
Starting package 1/32: mpir:x86-windows
Building package mpir[core]:x86-windows...
-- Downloading https://github.com/wbhart/mpir/archive/mpir-3.0.0.tar.gz...
-- Extracting source F:/vcpkg/downloads/wbhart-mpir-mpir-3.0.0.tar.gz
-- Applying patch enable-runtimelibrary-toggle.patch
-- Using source at F:/vcpkg/buildtrees/mpir/src/mpir-3.0.0-c9f63a8302
-- Building F:/vcpkg/buildtrees/mpir/x86-windows/build.vc15/dll_mpir_gc/dll_mpir_gc.vcxproj for Release
-- Building F:/vcpkg/buildtrees/mpir/x86-windows/build.vc15/dll_mpir_gc/dll_mpir_gc.vcxproj for Debug
-- Performing post-build validation
-- Performing post-build validation done
Building package mpir[core]:x86-windows... done
Installing package mpir[core]:x86-windows...
Installing package mpir[core]:x86-windows... done
Elapsed time for package mpir:x86-windows: 1.788 min
Starting package 2/32: mpfr:x86-windows
Building package mpfr[core]:x86-windows...
-- Downloading http://www.mpfr.org/mpfr-4.0.1/mpfr-4.0.1.tar.xz...
-- Extracting source F:/vcpkg/downloads/mpfr-4.0.1.tar.xz
-- Configuring x86-windows
-- Building x86-windows-dbg
-- Building x86-windows-rel
-- Performing post-build validation
-- Performing post-build validation done
Building package mpfr[core]:x86-windows... done
Installing package mpfr[core]:x86-windows...
Installing package mpfr[core]:x86-windows... done
Elapsed time for package mpfr:x86-windows: 30.64 s
Starting package 3/32: boost-any:x86-windows
......
Building package cgal[core]:x86-windows... done
Installing package cgal[core]:x86-windows...
Installing package cgal[core]:x86-windows... done
Elapsed time for package cgal:x86-windows: 1.914 min
/
Total elapsed time: 10.14 min
/
The package cgal:x86-windows provides CMake targets:
/
find_package(CGAL CONFIG REQUIRED)
# Note: 1 target(s) were omitted.
target_link_libraries(main PRIVATE ${cgal_lib} CGAL::${cgal_lib} CGAL_Qt5_moc_and_resources CGAL::Qt5_moc_and_resources)

@Rastaban I think this issue can be closed. It is fixed.

It's not resolved on all platforms:
macOS 10.14:
┌─[adam][hapkido][±][master ✓][~/vcpkg]
└─▪ ./vcpkg install cgal
The following packages will be built and installed:
    cgal[core]:x64-osx
  * mpfr[core]:x64-osx
Additional packages (*) will be modified to complete this operation.
Starting package 1/2: mpfr:x64-osx
Building package mpfr[core]:x64-osx...
-- Using cached /Users/adam/vcpkg/downloads/mpfr-4.0.1.tar.xz
-- Configuring x64-osx-dbg
-- Configuring x64-osx-rel
-- Building x64-osx-dbg
CMake Error at scripts/cmake/vcpkg_build_cmake.cmake:202 (message):
    Command failed: /usr/local/Cellar/cmake/3.14.3/bin/cmake;--build;.;--config;Debug;--target;install;--;-v
    Working Directory: /Users/adam/vcpkg/buildtrees/mpfr/x64-osx-dbg
    See logs for more information:
      /Users/adam/vcpkg/buildtrees/mpfr/install-x64-osx-dbg-out.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_install_cmake.cmake:24 (vcpkg_build_cmake)
  ports/mpfr/portfile.cmake:18 (vcpkg_install_cmake)
  scripts/ports.cmake:71 (include)

Error: Building package mpfr:x64-osx 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: mpfr:x64-osx
  Vcpkg version: 2018.11.23-unknownhash

Additionally, attach any relevant sections from the log files above.

I'm having similar issues with Windows 10:
The following packages will be built and installed:
    mpfr[core]:x86-windows
Starting package 1/1: mpfr:x86-windows
Building package mpfr[core]:x86-windows...
Warning: The following VS instances are excluded because the English language pack is unavailable.
    C:\Program Files (x86)\Microsoft Visual Studio\2019\Community
    C:\Program Files (x86)\Microsoft Visual Studio\2017\Community
Please install the English language pack.
-- Downloading http://www.mpfr.org/mpfr-4.0.2/mpfr-4.0.2.tar.xz...
-- Downloading http://www.mpfr.org/mpfr-4.0.2/mpfr-4.0.2.tar.xz... Failed. Status: 7;"Couldn't connect to server"
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/mpfr/portfile.cmake:3 (vcpkg_download_distfile)
  scripts/ports.cmake:94 (include)

It seems like the http link should be https.

@oxydated I think you can't access the download link. Can I manually download mpfr in this link?

@oxydated I think you can't access the download link. Can I manually download mpfr in this link?

Yes, I can.

@oxydated Okay, I confirm we should use https instead of http, we will fix it later.

I have tried vcpkg install cgal on Linux, and mpir and mpfr were pulled in.

This issue should be fixed in #8659.

@oxydated Please download mpfr manually by this link and put it into VCPKG_PATH/downloads/, then rebuild mpfr.

Hi everyone, this issue should be fixed in #8659.
Please update vcpkg and rebuild cgal.
Thanks.

authors: JackBoosY acgetchell lrineau oxydated rkcarroll wangli28


text:
Could not detect a Windows SDK / TargetPlatformVersion

Win7 X64
(base) D:\vcpkg-master>bootstrap-vcpkg.bat
Could not detect a Windows SDK / TargetPlatformVersion
所在位置 D:\vcpkg-master\scripts\bootstrap.ps1:327 字符: 10
+     throw <<<<  "Could not detect a Windows SDK / TargetPlatformVersion"
    + CategoryInfo          : OperationStopped: (Could not detec...PlatformVersion:String) [], RuntimeException
    + FullyQualifiedErrorId : Could not detect a Windows SDK / TargetPlatformVersion

Hi @03128crz  thanks for posting this issue.
Could you help confirm whether you have installed Windows SDK in your visual studio?

Hi @03128crz thanks for posting this issue.
Could you help confirm whether you have installed Windows SDK in your visual studio?

Hi, How to confirm whether installed Windows SDK ? if not install and which version of SDK I need to installed

You can check this on your local and confirm whether there are Windows SDK.
C:\Program Files (x86)\Windows Kits\
If you don't install them before, you can open your Visual Studio Installer and enter Individual Components page to install. Generally, we install the latest version.

I installed the SDK but it does not seem to work

@Lekja00160612
Please help confirm if you met the same error as this issue.

**_Could not detect a Windows SDK / TargetPlatformVersion
At C:\vcpkg\scripts\bootstrap.ps1:327 char:5

throw "Could not detect a Windows SDK / TargetPlatformVersion"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : OperationStopped: (Could not detec...PlatformVersion:String) [], RuntimeException
FullyQualifiedErrorId : Could not detect a Windows SDK / TargetPlatformVersion_**

this is the error i got any idea how to fix this ??

**_Could not detect a Windows SDK / TargetPlatformVersion
At C:\vcpkg\scripts\bootstrap.ps1:327 char:5

throw "Could not detect a Windows SDK / TargetPlatformVersion"

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : OperationStopped: (Could not detec...PlatformVersion:String) [], RuntimeException
FullyQualifiedErrorId : Could not detect a Windows SDK / TargetPlatformVersion_**

this is the error i got any idea how to fix this ??

I wonder what the meaning of 'meet an error' is? It seems to be a very popular expression here.
I reckon we should either change our translator or take an English course or BOTH!
Have a look at this blog: http://english-for-chinese.blogspot.com/2008/06/and-meet-problem.html

I wonder what the meaning of 'meet an error' is? It seems to be a very popular expression here.
I reckon we should either change our translator or take an English course or BOTH!
Have a look at this blog: http://english-for-chinese.blogspot.com/2008/06/and-meet-problem.html


text:
[vcpkg manifest] look at platform directives

Fixes #12538
Thanks @ras0219-msft !

/azp run


text:
[libxlsxwriter] upgrade to 0.9.5

Upgrade to the latest version of libxlsxwriter.
Closes #12724

There is a C++ compilation issue in this release so I will close it and re-open with 0.9.6.

You can also update to 0.9.6 in this PR.


text:
[libtins] Update to version 4.3

Update libtins to version 4.3 and enables C++11 support.

LGTM, thanks for the PR!


text:
Nanodbc/fix/config cmake files path linux

Describe the pull request

What does your PR fix? Fixes #
On Linux the *cmake.config files are not found after VCPKG install (see https://github.com/nanodbc/nanodbc/issues/260).
This PR provides the right path for those files (see the path on nanodbc CMake install https://github.com/nanodbc/nanodbc/blob/master/CMakeLists.txt#L268)

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

Does your PR follow the maintainer guide?
I updated the port version to 2 instead of 1 because it seems that it was reset to 0 without changing the package version (https://github.com/microsoft/vcpkg/commit/75bd2efe0dce862dfa025209b8cecc61a00a1852#diff-a787227381783470350e4b19cf34e27eabfefd76122c6836cab686377e59e10d). The consequence is that the baseline.json already contains a port version to 1 with same package version (https://github.com/microsoft/vcpkg/blob/master/versions/n-/nanodbc.json#L11), so to avoid conflict I updated to port version 2.

Did you test the usage locally?

Yes, tested with vcpkg install and manifest files.
Also tested with "version>=" in manifest files it works with "version>=": "2.13.0#2".

It doesn't work with other versions on same vcpkg git branch (for example "version>=": "2.13.0#1" or "version>=": "2.12.4" in manifest) but it seems to be the case on the head of vcpkg master branch so maybe I misuse/misunderstood the feature or it's not finished?

Vcpkg install fails if manifest file contains a dependency version constraint different than the one used in the current vcpkg git commit (for example if I use "version>=": "2.13.0#1" or "version>=": "2.12.4" instead of "version>=": "2.13.0#2" in my local vcpkg branch) but it seems to be the case on the head of vcpkg master branch so maybe I misuse/misunderstood the feature or it's not finished?
Example output of vcpkg-manifest-install.log after install fail:
Error: no version entry for nanodbc at version 2.13.0#1
We are currently using the version in the ports tree (2.13.0#2).

Ok I actually misused it 😅, I didn't have a builtin-baseline fields in my vcpkg.json, so added it it works now.

Why still not merged ?
Waiting for next VCPKG release or some more checks ?
I noticed that it's the same for older approved pull requests but find nothing about merging in documentation.

@ras0219-msft ，Please merge this pr.

Ping @vicroms for merge this PR.


text:
[json-dto] Update to 0.2.13

json_dto library updated to the latest version.

@eao197 ,Thanks for your pr.


text:
[quazip] Update to 1.3

Describe the pull request

What does your PR fix?
Updates quazip to 1.3

Which triplets are supported/not supported? Have you updated the CI baseline?
As before, Yes

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

Thanks!

authors: chausner strega-nil-ms


text:
[libpqxx] update to 7.7.3

Fix #24311
Update [libpqxx] versionto 7.7.3
Feature test successfully in the following triplet:

x86-windows
x64-windows
x64-windows-static

Delete the wrong branch


text:
[gdk-pixbuf] Convert option to feature

Fixes #37974
png, jpeg and tiff support are optional in gdk-pixbuf, however vcpkg has them hard-wired.
Turn png, jpeg and tiff into features, and enable those 3 by default to preserve compatibility.

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

Features png,tiff,jpeg tested successfully by x64-linux triplet.

Hmm this PR regressed a lot of things due to making stuff default features which is unsupported on windows.


text:
[mbedtls] update to 2.28.8

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

All features are tested successfully in the following triplet:
x86-windows
x64-windows
x64-windows-static

@MonicaLiu0311 Thank you for the review!
can you add the review label?

@MonicaLiu0311 Thank you for the review! can you add the review label?

Wait for the x64-osx CI Pipeline to finish.


text:
Treenikauppa

Repro steps:

Action: appService.Deploy
Error type: Error
Error Message: Failed to deploy because the path is not part of an open workspace. Open in a workspace and try again.
Version: 0.16.0
OS: darwin
Product: Visual Studio Code
Product Version: 1.38.1
Language: en

Call Stack
Object.<anonymous> extension.bundle.js:157:354245
o extension.bundle.js:157:353308

@SamiSuihkonen Please open your project in VS Code before you deploy.  The "Browse" button is intended to browse to subfolders in your root directory.

authors: SamiSuihkonen nturinski

repo: microsoft/vscode-azureappservice


text:
There is no a prompt asking when opening a template file with a 2018-05-01 schema

OS: All
Build Version: 20191101.29
Regression: Not a Regression
Repro Steps:

Get a template file with below schema from https://github.com/bmoore-msft/arm-template-language-samples like "schema-expresions-everywhere.json".

"$schema": "https://schema.management.azure.com/schemas/2018-05-01/subscriptionDeploymentTemplate.json#"

Open it in VS Code.
Check whether pop up a prompt asking or not.

Expect:
Pop up a prompt asking like below.

Actual:
There is no a prompt asking.

Thanks, that's expected, because there is not a more recent subscription deployment schema.  The only two schemas that are old and have an updated version are the resource group deployment schemas:

schema.management.azure.com/schemas/2014-04-01-preview/deploymentTemplate.json and
schema.management.azure.com/schemas/2015-01-01/deploymentTemplate.json

Got it. Thanks for your share and we will update it for our test case.

authors: StephenWeatherford v-dantch

repo: microsoft/vscode-azurearmtools


text:
No intellisense if no ending "]" and closing function ")" missing

Related to #902

{
  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
  "contentVersion": "1.0.0.0",
  "parameters": {
    "vmName": {
      "type": "string",
      "metadata": {
        "description": "Name of the virtual machine"
      }
    },
    "aadClientID": {
      "type": "string",
      "metadata": {
        "description": "Client ID of AAD app which has permissions to KeyVault"
      }
    },
    "aadClientCertThumbprint": {
      "type": "string",
      "metadata": {
        "description": "Thumbprint of the certificate associated with the AAD app which has permissions to KeyVault"
      }
    },
    "keyVaultName": {
      "type": "string",
      "metadata": {
        "description": "Name of the KeyVault to place the volume encryption key"
      }
    },
    "keyVaultResourceGroup": {
      "type": "string",
      "metadata": {
        "description": "Resource group of the KeyVault"
      }
    },
    "useExistingKek": {
      "type": "string",
      "defaultValue": "nokek",
      "allowedValues": [
        "nokek",
        "kek"
      ],
      "metadata": {
        "description": "Select kek if the secret should be encrypted with a key encryption key and pass explicit keyEncryptionKeyURL. For nokek, you can keep keyEncryptionKeyURL empty."
      }
    },
    "keyEncryptionKeyURL": {
      "type": "string",
      "defaultValue": "",
      "metadata": {
        "description": "URL of the KeyEncryptionKey used to encrypt the volume encryption key"
      }
    },
    "volumeType": {
      "type": "string",
      "defaultValue": "All",
      "metadata": {
        "description": "Type of the volume OS or Data to perform encryption operation"
      }
    },
    "sequenceVersion": {
      "type": "string",
      "defaultValue": "1.0",
      "metadata": {
        "description": "Pass in an unique value like a GUID everytime the operation needs to be force run"
      }
    },
    "location": {
      "type": "string",
      "defaultValue": "[resourceGroup().location]",
      "metadata": {
        "description": "Location for all resources."
      }
    }
  },
  "variables": {
    "extensionName": "AzureDiskEncryption",
    "extensionVersion": "1.1",
    "encryptionOperation": "EnableEncryption",
    "keyEncryptionAlgorithm": "RSA-OAEP",
    "updateVmUrl": "[concat('https://raw.githubusercontent.com/Azure/azure-quickstart-templates/master/201-encrypt-running-windows-vm/updatevm-',parameters('useExistingKek'),'.json')]",
    "keyVaultURL": "[concat('https://', parameters('keyVaultName'), '.vault.azure.net/')]",
    "keyVaultResourceID": "[concat(subscription().id,'/resourceGroups/',parameters('keyVaultResourceGroup'),'/providers/Microsoft.KeyVault/vaults/', parameters('keyVaultName'))]"
  },
  "resources": [
    {
      "type": "Microsoft.Compute/virtualMachines/extensions",
      "name": "[concat(parameters('vmName'),'/', variables('extensionName'))]",
      "apiVersion": "2016-04-30-preview",
      "location": "[parameters('location')]",
      "properties": {
        "publisher": "Microsoft.Azure.Security",
        "type": "AzureDiskEncryption",
        "typeHandlerVersion": "[variables('extensionVersion')]",
        "autoUpgradeMinorVersion": true,
        "forceUpdateTag": "[parameters('sequenceVersion')]",
        "settings": {
          "AADClientID": "[parameters('aadClientID')]",
          "AADClientCertThumbprint": "[parameters('aadClientCertThumbprint')]",
          "KeyVaultURL": "[variables('keyVaultURL')]",
          "KeyEncryptionKeyURL": "[parameters('keyEncryptionKeyURL')]",
          "KeyEncryptionAlgorithm": "[variables('keyEncryptionAlgorithm')]",
          "VolumeType": "[parameters('volumeType')]",
          "EncryptionOperation": "[variables('encryptionOperation')]"
        }
      }
    },
    {
      "name": "updatevm",
      "type": "Microsoft.Resources/deployments",
      "apiVersion": "2015-01-01",
      "dependsOn": [
        "[resourceId('Microsoft.Compute/virtualMachines/extensions',  parameters('vmName'), variables('extensionName'))]"
      ],
      "properties": {
        "mode": "Incremental",
        "templateLink": {
          "uri": "[variables('updateVmUrl')]",
          "contentVersion": "1.0.0.0"
        },
        "parameters": {
          "vmName": {
            "value": "[parameters('vmName')]"
          },
          "keyVaultResourceID": {
            "value": "[variables('keyVaultResourceID')]"
          },
          "keyVaultSecretUrl": {
            "value": "[reference(resourceId('Microsoft.Compute/virtualMachines/extensions',  parameters('vmName'), variables('extensionName'))).instanceView.statuses[0].message]"
          },
          "keyEncryptionKeyURL": {
            "value": "[parameters('keyEncryptionKeyURL')]"
          }
        }
      }
    }
  ],
  "outputs": {
    "BitLockerKey": {
      "type": "string",
      "value": "[reference(resourceId('Microsoft.Compute/virtualMachines/extensions',  parameters('vmName'), variables('extensionName'))).instanceView.statuses[0].message]"
    }
  }
}

No repro.


text:
[Bug] quick fix dropdown sort order should show import as first option

with copilot extension installed, when using quick fix menu to fix a broken import, Copilot options are shown at the top and import option is last.

suggested feature is to show import option first and copilot options after that. this is specific to fixing import but likely the case for other simple fixes.

This is also affecting Roslyn.  You guys are showing over our high priority items.  Specifically, "Add import".  This is the item that has highest pri in our system, and literally has billions of usages in our telemetry tracking.  Can you prioritize the work to not show up above these lang-specific, high pri items?  Thanks!

Agree, this is annoying enough I may uninstall co-pilot.

This is very annoying unfortunately

Copilot quick fix options are super annoying. Please provide a setting to disable them or place them at the bottom

related to https://github.com/microsoft/vscode-copilot/issues/670

Was able to disable this by disabling:
Settings > Extensions > Copilot > Enable Code Actions
Alternatively, via settings.json:
{

  "github.copilot.editor.enableCodeActions": false,

}

Not sure what else it disables yet tho. Will update if I stumble upon something else 👍

Hi this setting indeed removes the copilot code actions.
We are currently discussing how best to reorder the code actions with the team.

Hi @aiday-mar can you please keep roslyn in the loop on this?  Your code actions are definitely affecting some of our core experiences.  Thanks!

Disabling the option outright is a terrible option, because at times I may want to use the Copilot options, the imports quick fix is what 99.99999999999999999% of developers want at the top. Please fix this by adding an option to order, so put Copilot stuff at the bottom of the menu where it belongs.

Hi all, this issue is fixed in latest insiders and copilot-chat. When stable comes out you should see it there.

@aiday-mar How is this fixed? I still get the Copilot stuff as the first entries in the list half a year later on stable. Is there some setting to order them to the bottom?

Hi @i-am-the-slime could you please post here a screen-recording of this behavior. Are you on the latest stable?

authors: ChewingGlass CyrusNajmabadi aiday-mar caxco93 dmitrifaleev i-am-the-slime marwie nolawnchairs ranjitparva

repo: microsoft/vscode-copilot-release


text:
extension does not work with extended config files

If I have a .eslintrc.js like this, it works for build-time linting but not the eslint VSCode plugin:
// This is a workaround for https://github.com/eslint/eslint/issues/3458
require('@rushstack/eslint-config/patch/modern-module-resolution');

module.exports = {
	extends: ['@xlib/eslint-config'],
	parserOptions: { tsconfigRootDir: __dirname },
	rules: { 'tsdoc/syntax': 'error' }
};

I tried a lot of different things, including just having the @xlib/eslint-config do nothing except a single rule, and do nothing except itself extend @rushstack/eslint-config  but nothing works.
Here is a git branch with the example code:  https://github.com/jasonswearingen/xlib-monorepo/tree/vscode-eslint-bug1
and here are repro instructions:
npm install -g pnpm
pnpm install -g @microsoft/rush
# navigate to the xlib-monorepo
cd ./repos/xlib-monorepo/
rush install
rush build  #you'll see eslint errors show up
cd ./example-apps/verify-node/
code .

running vscode, open the .eslintrc.js and example.test.ts files.   you'll see that no eslint error show up.
from the rush build step above you would see the eslint warnings, and also if you run pnpm build you'll see them.

I should add, that with some extend choices it seems to work, but when trying to create a repro step to show that I wasn't able to find an example of it sometimes working.

@jasonswearingen this is very likely caused by the same reason described here: https://github.com/microsoft/vscode-eslint/issues/1040#issuecomment-669193727
The rush tool patches the ESLint script to make ESLint work in their setup which VS Code doesn't know about. IMO they should if this patching is necessary do the same for VS Code settings.
Please ping if you think this is not a dub of #1040.

@dbaeumer it may be related, but not the same problem I think.
In my project's main branch if I use extends: ['@rushstack/eslint-config'],  your eslint plugin works.     It's only when I try to  extends: ['@xlib/eslint-config'], my own (basically empty) eslint-config that the VSCode ESLint plugin doesn't work.
I didn't mention this because in my basic repro steps because it doesn't seem to work on my windows machine  (but it does under ubuntu via WSL2)
That said, this module resolution stuff + derived configs from multiple packages that rushstack does sure seems super hacky, so I don't blame you for not wanting to look at it.  I'm just going to copy/paste the eslint configs for the near term.

i created an sample project from scratch and eslint seems to work with extends.  so probably is a rushstack problem.  I'll be doing more research on this.

@dbaeumer so I figured out the problem.   mostly "user error"
If people are having problems, I would recomend you tell them to troubleshoot by first running eslint . from the command line.
In my case, the "extends": [ "@xlib/eslint-config",], is referencing a project that doesn't have the various eslint plugins installed, so running eslint . errors with the appropriate messages.      running pnpm build or rush build doesn't fail, probably because it's using some internal version of eslint.  so it looks like (from the naive user) that everything is working properly.

@jasonswearingen happy to hear that you were able to track this down. And yes eslint --debug . helps a lot :-)

authors: dbaeumer jasonswearingen

repo: microsoft/vscode-eslint


text:
Failed to load the ESLint library (Yarn 2 + PnP)

I've been trying to troubleshoot this for a while now with no success and saw a related issue so perhaps it is a bug or something I am missing. I think this may have worked at some point but can't remember for sure.
I keep getting the following error...
[Info  - 10:06:58 PM]
Failed to load the ESLint library for the document /Users/eric/Code/project/packages/components-shared/SomeCompoment.tsx

To use ESLint please install eslint by running yarn add eslint in the workspace folder project
or globally using 'yarn global add eslint'. You need to reopen the workspace after installing eslint.

Alternatively you can disable ESLint for the workspace folder project by executing the 'Disable ESLint' command.

I already tried yarn add eslint at /Users/eric/Code/project and it is in the root package. I am using yarn workspaces in case it makes a difference. yarn global add eslint should be removed as it has been disabled on yarn 2.
Here are the settings in my .vscode/settings.json some of which got added through yarn dlx @yarnpkg/pnpify --sdk vscode.
yarn run eslint . works when run from  /packages/components-shared
{
    "eslint.nodePath": ".yarn/sdks",
    "eslint.packageManager": "yarn",
    "eslint.workingDirectories": ["./packages/components-shared"],
    "eslint.validate": [
      "javascript",
      "javascriptreact",
      "html",
      "css",
      "typescriptreact",
      "typescript"
    ]
}

@ericvera does the validation happen correctly when you use eslint in the terminal. If this is the case can you please provide me with a GitHub repository I can clone that demos what you are experiencing.

@dbaeumer the validation does happen correctly. I do not have a repo that can be shared for repro and it may be some time before I can take the time to create one.
Any chance there is a guide somewhere with troubleshooting options? Debug logs?

Which command do you use and which cwd?

Found the solution so closing.
Solution:

Command + Shift + P
Select the >ESLint: Select Node Path command
and selecting Use NODE_PATH value defined via setting .yarn/sdk

My guess is that at some point either I dismissed the prompt or selected the wrong value. Setting a new project from scratch to try to repro the issue led me to the finding.
A great time saver would be for the error message of not being able to load ESLint to detect Yarn Berry and add those steps rather than yarn global add eslint. Which no longer works.
Anyways, thanks for the quick follow-ups!

@ericvera there should have been a notification informing you about the confirmation need for nodePath. This changed lately to get it in line with VS Code's recommendation to have user approval for settings that influence code execution.

@dbaeumer there was.
Some context in case it helps:
At the time I didn't know what it was and in the middle of some work assumed it safe to dismiss. I guess by choosing the wrong option.
It took me some time to notice as TS linting was still working. After noticing I did see references to similar issues and comments you have left on those about the new dialog but didn't completely connect the two until I tried to set everything up from scratch.
Looking at the code I saw that there are custom messages for yarn/npm/pnpm so perhaps a variant for yarn+pnp (still not sure what to call it) would simplify things if the issue keeps coming back.
Thanks again for the follow-up.

I have this problem, but I don't have a command anything like:
Use NODE_PATH value defined via setting .yarn/sdk
What was that command supposed to do, and can I do it some other way? I'm using Yarn 3.* (berry) so this is probably the problem I'm having, but I yarn global add eslint as advised doesn't work, and I can't work out what it's trying to do exactly, or what failure it's getting.
Where is this "ESLint library" supposed to be, and how can I help it find it?

OK, the bit which is possibly obvious to everyone but me is...
(1) I had a .yarn/sdks directory, but it just had the scelte-language-server in it, nothing else.
(2) I read the (new since I last read it) yarn docs, which had stuff about typing: yarn dlx @yarnpkg/sdks so I did that.
(3) That, plus {"eslint.nodePath": ".yarn/sdks", "eslint.trace.server": "verbose",
"eslint.packageManager": "yarn",} in settings... seemed to fix it

authors: dbaeumer ericvera phil-w


text:
Display(Sheet)..?

Environment data

VS Code version: XXX
Jupyter Extension version (available under the Extensions sidebar): XXX
Python Extension version (available under the Extensions sidebar): XXX
OS (Windows | Mac | Linux distro) and version: XXX
Python and/or Anaconda version: XXX
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): XXX
Jupyter server running: Local | Remote | N/A

Expected behaviour
XXX
Actual behaviour
XXX
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]

XXX

Logs

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

XXX

Thanks for the bug. We need some more information to understand what your issue is.
Can you provide:

A description of the problem
A sample of code that repros the problem
The contents of your 'jupyter' output tab.

Closing as no info provided. Please reopen if you can provide the necessary information.

authors: khatriharsh rchiodo

repo: microsoft/vscode-jupyter


text:
Add content encoding to server options

For more context, see #553.
This PR adds allows clients to define contentEncoder and contentDecoder in their server options. This addition makes it easier for clients to opt-in to different content encodings, such as msgpack, without having to worry about the life cycle of the process spawned - which is necessary when passing a function.
There's a simple example usage in the integration tests, which doesn't actually do anything, but demonstrates that clients will be able to hook their own content encoders and decoders.

I will close the PR for now. Please ping if you decide to continue working on this.

authors: dbaeumer vinistock

repo: microsoft/vscode-languageserver-node

license: mit

license_source: bigquery


text:
GE Creating comment failed when comment on PR

Using the below versions and Github Enterprise the following error is encountered when posting a comment:
Creating comment failed: Error: GraphQL error: Field 'subjectType' doesn't exist on type 'PullRequestReviewThread'
Works as expected on the release version of the extension

Extension version: 0.62.0 Pre Release
VSCode Version: 1.78 Insiders
OS:Windows

Steps to Reproduce:

Open A PR
Write a comment
Attempt to Add A comment
Error Creating comment failed: Error: GraphQL error: Field 'subjectType' doesn't exist on type 'PullRequestReviewThread' occurs

Cheers
James

@jpspringall are you using GitHub Enterprise?

@jpspringall are you using GitHub Enterprise?

Hey @alexr00 Yeah it is Github Enterprise, and I'm not sure if you have access to GE, so was just flagging this before it made it into general release .
Unfortunately, I've lost my GE sandbox from the previous issue we had, but I'll try and grab the debug logs at some point, but it may take me 24/48 hours as I have a busy few days coming up
Cheers
J

Can confirm I am seeing this (or similar) problem, using GHE:
2023-05-03 13:46:06.229 [info] Review> current branch NZP-2528-deploytrack-lambda-buildchain is associated with pull request #801
2023-05-03 13:46:06.229 [info] Review> Resolving pull request
2023-05-03 13:48:11.612 [error] PullRequestModel> Failed to get pull request review comments: Error: GraphQL error: Field 'subjectType' doesn't exist on type 'PullRequestReviewThread'
2023-05-03 13:50:58.012 [error] PullRequestModel> Failed to get pull request review comments: Error: GraphQL error: Field 'subjectType' doesn't exist on type 'PullRequestReviewThread'
2023-05-03 13:50:58.012 [error] PullRequestModel> Failed to get pull request review comments: Error: GraphQL error: Field 'subjectType' doesn't exist on type 'PullRequestReviewThread'

@jpspringall thanks for the thought. I do have access to GitHub Enterprise and this should be easy to repro.

To verify:

Open a GHE repo and sign in with your GHE account.
Make a pull request.
Verify that you can leave a comment on one of the changed lines of the PR.
Reload
Verify that you can see your comment.
Verify that you can resolve and unresolve your comment.

Can confirm this works for me.
Thanks @alexr00

Thanks for verifying!

authors: alexr00 jnpwly jpspringall

repo: microsoft/vscode-pull-request-github


text:
Support kernelChange in raw sessions

Splitting kernel change out from the restart work.

Not sure how we validate these? All at once?

@rchiodo I was just about to go through the validations myself. Personally I was going to close all the "work item" bugs. I felt like those were part of doing the work and the validation for those is usage / bugbash. I really like our validation step, but I felt that it was more for bugs, not for components of feature work. I'll have the work items cleared out by this afternoon and try to validate a few things myself.

authors: IanMatthewHuff rchiodo

repo: microsoft/vscode-python


text:
Add separate python.testing.pytestArgs settings for regular, debug and discovery runs

Evolved from #21190.
Related to #693, #19809, #19985 and some others.
Some of the pytest plugins may change how it works (e.g. running in parallel via pytest-xdist) or do some actions that are required on regular test runs but are unwanted on debug or discovery runs (e.g. generating a coverage report via pytest-cov). Currently vscode provides a single setting for configuring the args, and they are used for all the kinds of runs. Sometimes such behavior is inconvenient. Separating the single setting into 3 (for regular runs, for debug runs and for discovery runs) would make configuring pytest much more flexible.
Something like
"python.testing.pytestArgs": {
    "run": [], // equal to the current "python.testing.pytestArgs": []
    "debug": [],
    "discovery": []
}

or
"python.testing.pytestRunArgs": [],
"python.testing.pytestDebugArgs": [],
"python.testing.pytestDiscoveryArgs": []

Also related to  #18778. Here is that whole comment from there:
I would like to use additional pytest options when running tests, but not when discovering tests.
Scenario

I want to generate coverage data on every test run, so I have this in my settings.json:

    "python.testing.pytestArgs": [
        "src/unittests",
        "--cov=.",
        "--cov-report=xml:coverage.xml",
        "-vvv"
    ],

But I don't want to generate coverage when debugging a test, so I disable it in my launch.json:

        {
            "name": "Debug Tests",
            "type": "python",
            "request": "test",
            "console": "integratedTerminal",
            "env": {"PYTEST_ADDOPTS": "--no-cov"},
            "justMyCode": false
        }

I also don't want coverage data when tests are discovered because discovery is way faster without these options. This seems to be impossible at the moment.

What I need
I think I need either a possibility to inject the --no-cov option somewhere around https://github.com/microsoft/vscode-python/blob/e2bf90c991075aefcc15b16642a5122ceab84152/pythonFiles/testing_tools/adapter/pytest/_discovery.py#L65 or I need a possibility to just add the coverage options for non-debug test runs only.

Thank you to everyone who upvoted this issue! Since the community showed interest in this feature request we will leave this issue open as something to consider implementing at some point in the future.
We do encourage people to continue 👍 the first/opening comment as it helps us prioritize our work based on what the community seems to want the most.

I created a proposal with a solution for this problem, would love your input on the above issue! https://github.com/microsoft/vscode-python/issues/21845

closing as the proposal will guide the solution creation to your PR

authors: brettcannon eleanorjboyd mpekurin


text:
Python "Create Environment" button is not visible on requirements.txt file

Type: Bug
VS Code Version: 1.87.0
OS Version: MacOS Sonoma 14.3.1 (23D60)
Steps to Reproduce:

Install python extension
Add the Python project as a folder in the workspace.
Verified the "Python › Create Environment: Content Button" in settings is "show"
Opened requirements.txt file present in the project

Extension version: 2024.2.1
VS Code version: Code 1.87.0 (019f4d1419fbc8219a181fab7892ebccf7ee29a2, 2024-02-27T23:42:51.279Z)
OS version: Darwin arm64 23.3.0
Modes:

System Info

Item
Value

CPUs
Apple M2 (8 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
5, 3, 3

Memory (System)
16.00GB (0.06GB free)

Process Argv
--crash-reporter-id 4817f3f8-cb2d-4ac7-8d9c-a9c3c8d0db4b

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
pydisww1:30959800
d34g3935:30971562
edj9j583:30969295
fegfb526:30973843
ccp2r6:30958158
dsvsc020:30976470

@karthiknadig any updates on this?

Sorry, I have not had a chance to investigate this yet.

@akhil31415 The button is only shown if the following conditions are met:

python.createEnvironment.contentButton is set to show (which is what you have set).
There are dependencies in requirement.txt which are not in the selected environment.

Can you check the logs  Output >Python to make sure that there are errors reported by installed check script? you can try setting python.missingPackage.severity to error and see if problems are reported when you requirements.txt.

with these settings:
    "python.createEnvironment.contentButton": "show",
    "python.missingPackage.severity": "Error"

I tried the above steps
Getting the below output with error on the terminal
2024-04-08 00:05:59.058 [info] Experiment 'pythonRecommendTensorboardExt'
is active
2024-04-08 00:05:59.058 [info] Experiment 'pythonREPLSmartSend' is active
2024-04-08 00:05:59.058 [info] Experiment 'pythonTerminalEnvVarActivation'
is active
2024-04-08 00:05:59.058 [info] Experiment 'pythonTestAdapter' is active
2024-04-08 00:05:59.058 [info] Default formatter is set to null for
workspace /Users/akhilesh/IdeaProjects/PAIG/plugin-test/test-python
2024-04-08 00:05:59.058 [info] Running installed packages checker: python
/Users/akhilesh/.vscode/extensions/ms-python.python-2024.4.0/python_files/installed_check.py
/Users/akhilesh/IdeaProjects/PAIG/plugin-test/test-python/requirements.txt
2024-04-08 00:05:59.058 [info] > python ~/.vscode/extensions/ms-
python.python-2024.4.0/python_files/installed_check.py ./requirements.txt
2024-04-08 00:05:59.058 [error] Error while getting installed packages
check result:
[Error: spawn python ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:284:19)
at onErrorNT (node:internal/child_process:477:16)
at process.processTicksAndRejections
(node:internal/process/task_queues:82:21)] {
errno: -2,
code: 'ENOENT',
syscall: 'spawn python',
path: 'python',
spawnargs: [
'/Users/akhilesh/.vscode/extensions/ms-python.python-2024.4.0/python_files/installed_check.py'
,
'/Users/akhilesh/IdeaProjects/PAIG/plugin-test/test-python/requirements.txt'
]
}
2024-04-08 00:05:59.058 [info] Test server listening.
2024-04-08 00:05:59.058 [info] Python interpreter path:
/opt/homebrew/bin/python3.12
2024-04-08 00:05:59.084 [info] > pyenv which python
2024-04-08 00:05:59.084 [info] cwd: .
2024-04-08 00:05:59.758 [info] Starting Jedi language server for
test-python.
On Tue, Apr 2, 2024 at 10:31 AM Karthik Nadig @.***>
wrote:

with these settings:
"python.createEnvironment.contentButton": "show",
"python.missingPackage.severity": "Error"

image.png (view on web)
https://github.com/microsoft/vscode-python/assets/3840081/1296f381-05c0-4bdc-9246-65d6cbf228d9
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode-python/issues/23022#issuecomment-2031086668,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADCWCBZ26N63LVSU7RM6BJ3Y3I3R5AVCNFSM6AAAAABEE2OCC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZRGA4DMNRWHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@akhil31415 This looks like python extension was not able to find the right python. Can you make sure by running Select Interpreter command that the python is selected. If there is a valid python the log usually will have an entry saying selected python with a full path to it.


text:
Test: Native python locator

Refs: #23719, #23567

[ ] macOS @eleanorjboyd
[x] linux @cwebster-99
[x] windows @luabud
[x] anyOS @brettcannon

Complexity: 1
Create Issue

Requirements

Latest Python extension pre-release
Set "python.locator": "native" in user settings. Reload.

Testing
This is an open ended testing for the python locator. Add the above setting and see if it finds various pythons on your machine, hit the refresh button (in the selection quickpick) and see how it reacts.

so exciting! this is what the native locator found:

and this is with js:

authors: karthiknadig luabud


text:
$LMOD_SETTARG_CMD VS Code error message

I have looked for an existing issue about this but don't see any. I have also tried VS Code Insiders and get the same error message.
When I run a debug in VS Code, I get the following error message prompt and the debug session fails. I can open the "launch.json" and see the debug settings.

I initially raised the issue on the main VS Code repo https://github.com/microsoft/vscode/issues/82508 but I have been redirected here as they seem to think it is caused by the Python extension.
All my debugging sessions worked last week when I tried them last, this just seems to have started not working. I appreciate that's not much to go on, but it is all I have got a the moment!
Any help/guidance appreciated as I cannot now debug any of my (Python) applications.

VSCode Version: 1.39.1
OS Version: Win 10, Version 1809
Extension version 2019.10.41019
Python version (Anaconda): 3.6.7
Type of virtual environment used (conda):

Steps to reproduce:

Press F5 or click the debug menu icon and select config to debug

Logs
Output for Python in the Output panel: nothing
Output from Console under the Developer Tools panel: [Extension Host] ApplicationInsights:Sender ["Not saving data due to max size limit being met. Directory size in bytes is: 50001353"]

Can you try older version of the VSCode? It coincided with our release. Also, can you please share your launch.json.

This is related https://github.com/microsoft/vscode/issues/82611

Closing this since it is VS Code issue.

I downgraded VS Code to 1.38.1 and that has fixed the issue

authors: PeterJPRoche karthiknadig


text:
Python debugger Attach to PID not working

Environment data

VS Code version: 1.41.1
Extension version (available under the Extensions sidebar):
Name: Python, Id: ms-python.python, Version: 2020.3.61768-dev
OS and version: Ubuntu 19.10
Python version (& distribution if applicable, e.g. Anaconda): 3.7.5

Expected behaviour
Debugger attaches to PID
Actual behaviour
"Attaching the debugger to a local process is an experimental feature. It will be available to all users soon."
I followed directions from luabud in issue #1078 here then re-started vscode.
However I'm still getting the above message decided in issue #8935 here.

@awittaker, thanks for letting us know about this.  At the moment users are selected at random for inclusion in the "experiment".  You can see what experiments you are in by looking at the top of the "Python" output panel.  Please provide the content of that panel.  Thanks!

Attaching the debugger to a local process is an experimental feature. It will be available to all users soon.
me too, and how to enable, In a hurry,:C

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.

authors: awittaker brettcannon ericsnowcurrently heartacker


text:
Add support for find in notebook editor

For #9470

Codecov Report

Merging #9471 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #9471      +/-   ##
==========================================
- Coverage   60.91%   60.89%   -0.02%
==========================================
  Files         530      530
  Lines       28650    28650
  Branches     4344     4344
==========================================
- Hits        17452    17447       -5
- Misses      10245    10248       +3
- Partials      953      955       +2

Impacted Files
Coverage Δ

...rc/client/common/application/webPanels/webPanel.ts
13.63% <ø> (ø)
:arrow_up:

src/client/common/utils/platform.ts
64.7% <0%> (-11.77%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.36% <0%> (-2.28%)
:arrow_down:

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

src/client/common/process/proc.ts
14.7% <0%> (-0.74%)
:arrow_down:

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 bbd5152...58b3a4f. Read the comment docs.

authors: DonJayamanne codecov-io


text:
The top of the screen is not displayed correctly when maximized.

Issue Type: Bug
When the window is maximized, the upper part of the screen (near the title bar) may not be displayed.
This problem occurs about once every half month.
The condition of reappearance is unknown.
Restarting the computer will fix the problem.
When the window is restored to normal size (Windows Key + Down Arrow), it will be displayed normally, but it will not be displayed again when the window is maximized.
note: Translated with www.DeepL.com/Translator (free version)

VS Code version: Code 1.47.1 (485c41f9460bdb830c4da12c102daff275415b53, 2020-07-13T22:42:53.386Z)
OS version: Windows_NT x64 10.0.18363

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8 x 3000)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: 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)
15.94GB (8.60GB free)

Process Argv
--disable-extensions

Screen Reader
no

VM
0%

Extensions disabled

Screen Shot

Is this still an issue with latest insiders https://code.visualstudio.com/insiders ?

repo: microsoft/vscode


text:
Intellisense for C++: Values for enum variables/arguments prediction

I'd like to propose improvement to how does IntelliSense operate on enums.
Currently if you have code like following and you press Ctrl+Space inside parentheses of the foo function call, IntelliSense returns huge list of unrelated items like: pre-processor derictives, integer constants, functions. See screenshot attached.
//
// Code example
//
enum SomeEnums
{
Element1,
Element2
};
int main()
{
SomeEnums  SomeEnum;
SomeEnum = /* press Ctrl+Space here */
return 0;
}
All 99% of the suggested items are not compatible with enum. They cannot be implicitly converted to enum.
The screenshots show the work of another IDE in this situation - the first to offer compatible options

/extC++


text:
typescript language feature failed 5 times

Issue Type: Bug
Starting VSCode show up the error popup. I have no idea why.
VS Code version: Code 1.47.3 (91899dcef7b8110878ea59626991a18c8a6a1b3e, 2020-07-23T15:51:39.791Z)
OS version: Linux x64 5.4.0-42-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-8100 CPU @ 3.60GHz (4 x 3600)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: disabled_softwareskia_renderer: disabled_off_okvideo_decode: unavailable_offviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
1, 1, 1

Memory (System)
15.58GB (7.23GB free)

Process Argv
--no-sandbox --unity-launch

Screen Reader
no

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
x11

Extensions (31)

Extension
Author (truncated)
Version

better-comments
aar
2.1.0

cucumberautocomplete
ale
2.15.0

vscode-color
ans
0.4.5

vscode-styled-jsx
bla
1.5.0

vscode-intelephense-client
bme
1.5.3

bracket-pair-colorizer
Coe
1.0.61

vscode-svgviewer
css
2.0.0

vscode-markdownlint
Dav
0.36.2

vscode-eslint
dba
2.1.8

githistory
don
0.6.9

gitlens
eam
10.2.2

EditorConfig
Edi
0.15.1

prettier-vscode
esb
5.1.3

vscode-firefox-debug
fir
2.9.0

terraform
has
2.1.1

graphql-for-vscode
kum
1.15.3

dotenv
mik
1.0.1

vscode-docker
ms-
1.4.1

mssql
ms-
1.9.0

vsliveshare
ms-
1.0.2478

vetur
oct
0.26.1

indent-rainbow
ode
7.4.0

material-icon-theme
PKi
4.2.0

vscode-graphql
Pri
0.2.14

gruvbox-material
sai
6.3.3

code-settings-sync
Sha
3.4.3

open-in-browser
tec
2.0.0

serverless-ide-vscode
Thr
0.5.26

twig
wha
1.0.2

better-align
wwm
1.1.6

material-theme
zhu
3.8.5

(3 theme extensions excluded)

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

The project's typescript version was 3.9.4.
By selecting the VSCode typescript version (3.9.7), the error stopped occuring.
I'm closing this issue then.
Thanks for your time.

authors: mjbvz mlaopane


text:
Why my pc end up open VScode by cmd on windows

Hi
When I try to open python file on cmd,I don't know why VScode is open as automatic,,,how can I get back normal system work?
I already trid uninstall VScode with system files and reset cmd.
now I use windows10 & VScode & anaconda(these are latest versoin)
cmd error is bellow↓↓
[main 2020-08-14T01:59:15.655Z] update#setState idle
(node:4200) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information
(node:4200) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information
(node:4200) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information
(node:4200) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information
(node:18100) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information
(node:18100) Electron: Loading non context-aware native modules in the renderer process is deprecated and will stop working at some point in the future, please see https://github.com/electron/electron/issues/18397 for more information

/needsMoreInfo

authors: Hideyukit-DD mjbvz


text:
The Source Control view displays arrow signs for repos which don't even have any changes

VSCode Version: 1.48.2
OS Version: Windows 10 Enterprise

Steps to Reproduce:

Open multiple repos in VSCode, for example I've a few dozens of repos opening in the same VSCode work space.
Observed that for those repos, in the version 1.48.2, the Source Control view now displays an arrow sign at the most left for each of them, even for those don't have any changes! For example in the below screenshot, only a few repos actually have changes, but here we cannot easily tell will two they are which is extremely inconvenient.

When opening the same work space in 1.47.3, it displays an arrow sign at the most left in each row only for repos which do have changes, but not for those which don't. This is very convenient to spot which repos have changes and which don't. It's so much better. The below screenshot shows clearly that 4 repos have changes.

Please revert this behaviour in 1.48.2 to 1.47.3, it'd be much more helpful. Thanks,
BTW, before 1.47.0, as shown below, at least the visual effect for spotting changes looks even nicer, IMHO.

This is fixed in Insiders: you can show the Source Control Repositories view and control this visibility yourself again. It will be released on the next stable.

@joaomoreno I just downloaded VSCode 1.49.0 Insiders. Only see a new setting called scm.repositories.visible added as shown below, but not to control the arrow signs. So which new setting has been added to control the arrow signs?

Oh I see what you mean. The arrows were set to always show on repositories to help with consistency in understanding which rows are repositories. UX feedback drove us there. Sorry about that.
For that amount of repositories, I suggest you simply use the Source Control Repositories view.

I actually think that the new way regarding displaying the arrows is worse in terms of UX 🙄 🤣 , comparing to the 1.47.3 way which does provide the convenience, and tidy view.


text:
Cannot run extensions tests headless

I'd like to run extension tests in a CI or a TTY.
Steps to Reproduce:

Open a TTY (on Linux, press Ctrl+Alt+F1)
git clone https://github.com/microsoft/vscode-extension-samples
cd vscode-extension-samples/helloworld-test-sample
npm install
xvfb-run -a npm test

Expected behavior
The tests succeed
Actual behavior
The tests fail
Additional information
The xvfb-run command was taken from the docs.
Install xvfb with sudo apt install xvfb on Ubuntu
Seems like extension tests cannot be run in an environment without graphic interface
Seems related to #103060 and #103113 but I don't use snap and those issues are closed
Complete trace
Found .vscode-test/vscode-1.51.1. Skipping download.
Warning: 'sandbox' is not in the list of known options, but still passed to Electron/Chromium.

[main 2020-12-04T13:01:47.387Z] update#setState idle

[main 2020-12-04T13:01:47.388Z] update#ctor - manual checks only; automatic updates are disabled by user preference

/dev/fd/3: Aucun fichier ou dossier de ce type

Server response:

/dev/fd/3: Aucun fichier ou dossier de ce type

Server response:

/dev/fd/3: Aucun fichier ou dossier de ce type

Server response:

/dev/fd/3: Aucun fichier ou dossier de ce type

Server response:

/dev/fd/3: Aucun fichier ou dossier de ce type

Server response:

[26655:1204/140147.684597:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.

/dev/fd/3: Aucun fichier ou dossier de ce type

Server response:

/dev/fd/3: Aucun fichier ou dossier de ce type

Server response:

/dev/fd/3: Aucun fichier ou dossier de ce type

Server response:

Exit code:   null
Done

Failed to run tests

Version: 1.52.0-insider
Commit: 92192baf760315ac47fb2caaf3ce6d0778962352
Date: 2020-12-03T05:44:34.000Z
Electron: 9.3.5
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Linux x64 4.15.0-123-generic

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

I think we have https://github.com/microsoft/vscode-test/blob/master/sample/azure-pipelines.yml as an example for how to configure Azure pipelines to run extension tests.

Thank you, it works
Seems like xvfb-run doesn't work in a TTY, but starting an Xvfb server does.
Some notes

It makes some extensions crash, so I launch test with extensions disabled (launchArgs: ["--disable-extensions"])
You might want to add a TTY section in this document if I'm not the only one doing this

Future developers might want to try this quickly-written script
#!/bin/bash
set -eux

# Start server
/usr/bin/Xvfb :99 -screen 0 1024x768x24 &
sleep 1

# Make sure it's running
ps aux | grep Xvfb --color=always | grep -v grep

# Run tests
DISPLAY=:99.0 node ./dist/test/runTest.js

# Kill server
killall Xvfb

authors: bpasero sguillia


text:
Join Cells with multiple selections

Now that multi-select lands in notebook core, we want to support Join Cells (merging selected cells). A few open questions for implementation:

Should we allow cells of different kinds/languages be merged?
Should cells from two distinct selections be merged into one cell or separate cells (one cell per selection)

Run action on all selected cells
The simplest solution is merging all selected cells into one. It's intuitive as all cells in the selections will be merged, which is never ambiguous.
Run action per distinct selection
Imagine we have a notebook with 5 cells
  python_1,
  python_2,
  md_1,
  python_3,
  python_4

Python cells 1, 2, 3 and 4 are selected, so we have 2 distinct selections, { start: 0, end: 2 }, { start: 3, end: 5 }. After users run Join Cells:
  'python_1
  md_1,
  'python3

Each distinct selection shrinks into a single cell.

Was searching for a way to quickly merge cells (similarly to "Shift+M" in JupyterLab) and found this open thread. Please consider my suggestions:

Should we allow cells of different kinds/languages be merged?

No. Why: the merged cells with mixed languages/Markdown won't be executable/readable
Suggestion: Simply abort the operation and prompt the user as this is more often than not an accidental selection

Should cells from two distinct selections be merged into one cell or separate cells (one cell per selection)

One cell. So with the given example the end result becomes python_1 (with content of all 4 python_x cells), md_1
Why: the users need this function to consolidate/refactor code cells. If not consolidated into one cell then it defeats the purpose. If instead the user really just wants to get python_1, md_1, python_3, then he/she can simply merge python_1 and python_2 first and then repeat for python_3 and python_4. The process is still efficient with shortcut keys (Shift+Down, Shift+M, ESC, Down, Down, Shift+Down, Shift+M)

Would really love to see this feature implemented. Currently I see that you can merge the highlighted cells with ctrl + alt + j but that feature also merges the cell "below" the selected cells. I get the need to have something that "merges cell below" but I mostly just use the feature to "merge only highlighted cells".
Any timeline on this?

@frank-yifei-wang @aymather thank you both for the suggestions. I pushed a new command Join Selected Cells which will be available in Insiders soon.

authors: aymather frank-yifei-wang rebornix


text:
Crash in V8 when using Node FFI modules

Issue Type: Bug
The crash occurs when the InterSystems Language Server extension is activated.
The extension calls out from JavaScript to an InterSystems shared library (packaged with the extension) and then uses the following Node FFI modules to turn the returned result into JavaScript objects:

ffi-napi 4.0.3
ref-array-napi 1.2.2
ref-napi 3.0.2
ref-struct-napi 1.1.1

Although we have been using older versions of these modules the crash also occurs with these latest versions of them.
This works fine with VSCode Stable (and has done for months) but crashes on Insiders.  It also works fine with stand-alone Node.
The crash actually occurs when the JavaScript code either uses toArray or attempts to access a part of the returned object using subscripting (i.e. [..]).  The last JS code executed before calling native code is in ref-napi: ref.js calls _reinterpret to "reinterpret" the buffer by - as I understand it - creating a larger buffer at the same address.
I have attached a zip of the .dmp file created by VSCode Insiders.
ER: The Language Server extension starts up and functions normally
AR: The Language Server crashes on activation and (after a retry)  disconnects from the client.
VS Code version: Code - Insiders 1.56.0-insider (13f1afffab09548c10ddb3bc5d5db52587876ad8, 2021-04-28T04:50:45.511Z)
OS version: Darwin x64 18.7.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (8 x 4200)

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)
1, 2, 2

Memory (System)
32.00GB (6.63GB free)

Process Argv
--crash-reporter-directory /Users/andyc/crash

Screen Reader
no

VM
0%

Extensions (3)

Extension
Author (truncated)
Version

servermanager
int
2.0.3

vscode-objectscript
int
1.0.10

language-server
int
1.1.4

A/B Experiments
vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
pythonvspyt602:30291494
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry914:30244316
pythonvspyt639:30291487
pythontb:30258533
vspre833:30267464
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscus158:30286553
vscgsv2ct:30286873
vscorehov:30294388
3f5j7703:30294757

a47c8fa5-5629-44e8-9b59-52c9caa07aae.dmp.zip

I'm not sure whether this is included in the .dmp file so here's the error report and stack trace:
#
# Fatal error in , line 0
# ignored
#
#
#
#FailureMessage Object: 0x7ffee10b4a50
 1: 0x111306b72 node::MultiIsolatePlatform::CancelPendingDelayedTasks(v8::Isolate*) [/Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 2: 0x11454a8b1 v8::internal::compiler::ZoneStats::GetCurrentAllocatedBytes() const [/Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 3: 0x10f64e713 v8::internal::BackingStore::Reallocate(v8::internal::Isolate*, unsigned long) [/Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 4: 0x10f495044 v8::ArrayBuffer::GetBackingStore() [/Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 5: 0x1112607a9 napi_get_typedarray_info [/Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
 6: 0x11710bffd Napi::TypedArrayOf<unsigned char>::TypedArrayOf(napi_env__*, napi_value__*) [/Users/andyc/git/language-server/server/node_modules/ref-array-napi/node_modules/ref-napi/build/Release/binding.node]
 7: 0x11710a0ae (anonymous namespace)::WrapPointer(Napi::Env, char*, unsigned long) [/Users/andyc/git/language-server/server/node_modules/ref-array-napi/node_modules/ref-napi/build/Release/binding.node]
 8: 0x11710b698 (anonymous namespace)::ReinterpretBuffer(Napi::CallbackInfo const&) [/Users/andyc/git/language-server/server/node_modules/ref-array-napi/node_modules/ref-napi/build/Release/binding.node]
 9: 0x1170c7ef3 napi_value__* Napi::details::WrapCallback<Napi::details::CallbackData<Napi::Value (*)(Napi::CallbackInfo const&), Napi::Value>::Wrapper(napi_env__*, napi_callback_info__*)::'lambda'()>(Napi::details::CallbackData<Napi::Value (*)(Napi::CallbackInfo const&), Napi::Value>::Wrapper(napi_env__*, napi_callback_info__*)::'lambda'()) [/Users/andyc/git/language-server/server/node_modules/ref-napi/build/Release/binding.node]
10: 0x1170c7ea9 Napi::details::CallbackData<Napi::Value (*)(Napi::CallbackInfo const&), Napi::Value>::Wrapper(napi_env__*, napi_callback_info__*) [/Users/andyc/git/language-server/server/node_modules/ref-napi/build/Release/binding.node]
11: 0x111262013 napi_is_detached_arraybuffer [/Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
12: 0x10f4c54a0 v8::internal::ClassScope::ResolvePrivateNamesPartially() [/Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
13: 0x10f4c50f5 v8::internal::ClassScope::ResolvePrivateNamesPartially() [/Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
14: 0x10f4c4773 v8::internal::ClassScope::ResolvePrivateNamesPartially() [/Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
15: 0x10fb1b478 v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) [/Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]
16: 0x10fab52ef v8::internal::SetupIsolateDelegate::SetupHeap(v8::internal::Heap*) [/Applications/Visual Studio Code - Insiders.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Electron Framework]

@deepak1556 is this your domain?

Original issue: https://github.com/intersystems/language-server/issues/152

Thanks - I meant to put that in but forgot.
Andy

On 28 Apr 2021, at 17:51, Brett Saviano @.***> wrote:
Original issue: intersystems/language-server#152
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thanks for the ping @gjsjohnmurray.
Insiders has updated to node v14 which disallows creating two ArrayBuffer instances pointing to the same memory https://github.com/nodejs/node/issues/32463. ref-napi seems to have addressed this in https://github.com/node-ffi-napi/ref-napi/commit/aede9057f9ff29c50d3be8fa90ddfbe28e5dc238 but there are still users reporting to hit this with 3.0.2 on node v14 https://github.com/node-ffi-napi/ref-napi/issues/47. I would suggest to create a minimal repro and report it in the module to get the issue fixed, there is not much vscode can do here.
Also, I noticed that you are using ref-struct-napi and ref-array-napi, it is recommended to use ref-struct-di and ref-array-di https://github.com/node-ffi-napi/ref-napi/commit/e36f35eaa653bb599be158a83f3ca519b46718e9

authors: deepak1556 gjsjohnmurray isc-AndrewCheshire isc-bsaviano


text:
formatOnSave not working properly

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

VS Code Version: 1.57.1
OS Version: MacOS Big Sur 11.3.1

Since I updated my VSCode this morning my VSCode is not properly formatting on save, it seems to ignore my prettierrc. Which is really annoying because I have to wait for the pipeline to break to notice that there is some linting issue. What can I do?

l have the same problem. When l just update my vscode,l can't formatOnSave , l also can't code completion when l code C++. l want to know what can l do?

Same for me, prettier stopped working in latest version. Tried to check "Default formatter" but seems to be correct.

Same for me, prettier stopped working in latest version.

Maybe this is a problem with prettier?

Double check that VS code is using the correct python interpreter.
For some reason after the latest VS code update my python interpreter was downgraded to python 2.7 which caused me numerous issues since my environment is really set up for python 3.7. Once I fixed this format on save functionality was restored (along with resolving many of my other issues).

I see 2 issues here which might be related:
settings:
"editor.formatOnSave": true,
"[typescript]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode"
  },
"html.format.wrapAttributes": "force-expand-multiline",
"html.format.wrapLineLength": 220,

As far as I understand, prettier is hence only used for ts files otherwise use the default.
Issue 1: On Save .html-files: The formatting behaves differently from before the update. Maybe due to bugfixes, i.e. formatting of tag attributes now complies to the setting: "html.format.wrapAttributes" before it didn't in my project.
Also all tags now get a new line... why? did something change in the default "html.format.extraLiners" (a setting that we dont use)?
Issue 2: On Save .ts-files I get the message "Extension 'Prettier - Code formatter' - cannot format ..." before this worked. Should not be an issue with Prettier because this worked before.

I have the same problem with Python. After updating to the latest version, auto formatting does not work anymore with the settings that worked before.
It seems to execute the formatter executable correctly, at least it works when executing it manually, but the output is not leading to any change to the source code.

Can everyone in this issue make sure that they operate inside a "trusted workspace". Iff untrusted extensions will be disabled and symptom of that will be features like "format on save" or IntelliSense not working anymore.
Read me here: https://code.visualstudio.com/docs/editor/workspace-trust or try with this setting "security.workspace.trust.enabled": false

Hi @jrieken thank you.
I tried and it was set to true initially, when setting to false VS Code prompted for a restart and it seems to work now, even if I set it to true again. Looks like the additional restart might have fixed my 'not working'-issue (Issues 2 and 3 that I mentioned above) *grrrr... I'm going to monitor this for a while.
Issue 1 formatting html still behaves differently than before.

authors: CrimpCity clieee codetent daniel-seitz jrieken xqacmer youssefazriouil


text:
Files don't show in some projects

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

VS Code Version: 1.62.2
OS Version: Ubuntu 20.04.3 LTS

Steps to Reproduce:

Open up a project.
Try to find some file either from command palete with ctrl+p or with the explorer.
Verify files are there using the system explorer/terminal/whatever other tool.

My guess is that at some point VSCode had some issues with Git versions? It's happening in all of my projects from a couple of versions back, but I thought it might be fixed already. I'm not seeing that there are more complaints about this so I wonder if this is only happening to me and if there might be some weird caching somewhere involved that won't let VSCode refresh disk contents if not already indexed?
Sorry for not being able to give more info, you guys are doing a great job!

Could you give an example of what files don't show? It's expected that git ignored and search.exclude'd/files.exclude'd files don't appear.

As you can see both the terminal and the Git extension can find the file image_path_builder.py. Of course if I do code ${file} it will open the file, but I can't open it from the explorer, command palette or include it in searches. This file is of course not excluded as it's a normal python file.

This is something that jus happens when I pull new changes and it started happening a couple of versions back

do you have files.exclude configured in either a local settings.json file or your global settings?

So sorry, I stubbornly thought that that couldn't be it and I see that it just happens that at least in this specific case that happened. I have no way to see if the other instances where it happened it fell under this coincidence, but I'm guessing that's it :facepalm:
As you guessed one of the excluded expressions was "**/storage/**/*": true,.
Very sorry for the inconvenience and keep up the great work!

No worries, I'm glad we figured it out :)

authors: JacksonKearl arudp


text:
Displaying statistics on the use of programming language features

I propose to make it possible to view a detailed summary of the used and unused features of the current programming language.

/needsMoreInfo

Hi! E.g if I did not use null propagation in current project and I do not know about it then I MUST discover it using the statistics information.

This is up to each language/extension. Please file individual features requests against them for the statistics you want to see

authors: aslot mjbvz