text:
Follow-up on the changes to the SK framework and ensure the sample remains functional.

Motivation and Context

Why is this change required?
Follow-up on the changes to the SK framework(version 0.2.3 to 0.2.4) and ensure the sample remains functional.
What problem does it solve?
Follow-up on the changes from semantic-kernel version 0.2.3 to 0.2.4:
a. The path of OpenAITextCompletion has been changed.
b. kernel.config.add_text_service has been replaced with kernel.config.add_text_backend.

Description

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
[x] I didn't break anyone :smile:

@microsoft-github-policy-service agree
At 2023-04-26 17:16:35, "microsoft-github-policy-service[bot]" @.***> wrote:
@chuanzhubin please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:
(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement
Contribution License Agreement
This Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
and conveys certain license rights to Microsoft Corporation and its affiliates (“Microsoft”) for Your
contributions to Microsoft open source projects. This Agreement is effective as of the latest signature
date below.
Definitions.
“Code” means the computer software code, whether in human-readable or machine-executable form,
that is delivered by You to Microsoft under this Agreement.
“Project” means any of the projects owned or managed by Microsoft and offered under a license
approved by the Open Source Initiative (www.opensource.org).
“Submit” is the act of uploading, submitting, transmitting, or distributing code or other content to any
Project, including but not limited to communication on electronic mailing lists, source code control
systems, and issue tracking systems that are managed by, or on behalf of, the Project for the purpose of
discussing and improving that Project, but excluding communication that is conspicuously marked or
otherwise designated in writing by You as “Not a Submission.”
“Submission” means the Code and any other copyrightable material Submitted by You, including any
associated comments and documentation.
Your Submission. You must agree to the terms of this Agreement before making a Submission to any
Project. This Agreement covers any and all Submissions that You, now or in the future (except as
described in Section 4 below), Submit to any Project.
Originality of Work. You represent that each of Your Submissions is entirely Your original work.
Should You wish to Submit materials that are not Your original work, You may Submit them separately
to the Project if You (a) retain all copyright and license information that was in the materials as You
received them, (b) in the description accompanying Your Submission, include the phrase “Submission
containing materials of a third party:” followed by the names of the third party and any licenses or other
restrictions of which You are aware, and (c) follow any other instructions in the Project’s written
guidelines concerning Submissions.
Your Employer. References to “employer” in this Agreement include Your employer or anyone else
for whom You are acting in making Your Submission, e.g. as a contractor, vendor, or agent. If Your
Submission is made in the course of Your work for an employer or Your employer has intellectual
property rights in Your Submission by contract or applicable law, You must secure permission from Your
employer to make the Submission before signing this Agreement. In that case, the term “You” in this
Agreement will refer to You and the employer collectively. If You change employers in the future and
desire to Submit additional Submissions for the new employer, then You agree to sign a new Agreement
and secure permission from the new employer before Submitting those Submissions.
Licenses.
Copyright License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license in the
Submission to reproduce, prepare derivative works of, publicly display, publicly perform, and distribute
the Submission and such derivative works, and to sublicense any or all of the foregoing rights to third
parties.
Patent License. You grant Microsoft, and those who receive the Submission directly or
indirectly from Microsoft, a perpetual, worldwide, non-exclusive, royalty-free, irrevocable license under
Your patent claims that are necessarily infringed by the Submission or the combination of the
Submission with the Project to which it was Submitted to make, have made, use, offer to sell, sell and
import or otherwise dispose of the Submission alone or with the Project.
Other Rights Reserved. Each party reserves all rights not expressly granted in this Agreement.
No additional licenses or rights whatsoever (including, without limitation, any implied licenses) are
granted by implication, exhaustion, estoppel or otherwise.
Representations and Warranties. You represent that You are legally entitled to grant the above
licenses. You represent that each of Your Submissions is entirely Your original work (except as You may
have disclosed under Section 3). You represent that You have secured permission from Your employer to
make the Submission in cases where Your Submission is made in the course of Your work for Your
employer or Your employer has intellectual property rights in Your Submission by contract or applicable
law. If You are signing this Agreement on behalf of Your employer, You represent and warrant that You
have the necessary authority to bind the listed employer to the obligations contained in this Agreement.
You are not expected to provide support for Your Submission, unless You choose to do so. UNLESS
REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING, AND EXCEPT FOR THE WARRANTIES
EXPRESSLY STATED IN SECTIONS 3, 4, AND 6, THE SUBMISSION PROVIDED UNDER THIS AGREEMENT IS
PROVIDED WITHOUT WARRANTY OF ANY KIND, INCLUDING, BUT NOT LIMITED TO, ANY WARRANTY OF
NONINFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.
Notice to Microsoft. You agree to notify Microsoft in writing of any facts or circumstances of which
You later become aware that would make Your representations in this Agreement inaccurate in any
respect.
Information about Submissions. You agree that contributions to Projects and information about
contributions may be maintained indefinitely and disclosed publicly, including Your name and other
information that You submit with Your Submission.
Governing Law/Jurisdiction. This Agreement is governed by the laws of the State of Washington, and
the parties consent to exclusive jurisdiction and venue in the federal courts sitting in King County,
Washington, unless no federal subject matter jurisdiction exists, in which case the parties consent to
exclusive jurisdiction and venue in the Superior Court of King County, Washington. The parties waive all
defenses of lack of personal jurisdiction and forum non-conveniens.
Entire Agreement/Assignment. This Agreement is the entire agreement between the parties, and
supersedes any and all prior agreements, understandings or communications, written or oral, between
the parties relating to the subject matter hereof. This Agreement may be assigned by Microsoft.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Thanks for this! We're close to release a new pip package that should reflect the updated documentation. Rather than make multiple README changes, I think it's better for the SK team to publish and then as part of that PR update all the docs all at once.
@dluc thoughts?

It's great to see your response.
I have made some modifications to the test programs under Python to adapt to the changes in version 0.2.4. This should be relatively complete, and if needed, it can be merged in.

It's already nighttime in Shanghai. Goodnight, and I wish you all a good morning.

thanks @chuanzhubin -- sorry about the disruption, we're releasing a new version and updating the docs today, pretty soon everything will be aligned and work as usual

authors: alexchaomander chuanzhubin dluc


text:
Unable to assign ClusterConfiguration using ConfigurationUpgradeDescription method

I am trying to update cluster configuration settings using UpgradeConfigurationAsync (System.Fabric.Description.ConfigurationUpgradeDescription description); but ConfigurationUpgradeDescription is not accepting configuration settings

Please let us know if this is not resolved.

source: gharchive/issue

authors: AbhishekAdusumilli craftyhouse

repo: microsoft/service-fabric

license: MIT

license_type: permissive

license_source: github-api


text:
Updated Service Fabric 9.0 Release Schedule (Tentative)

Updated Service Fabric 9.0 Release Schedule (Tentative)

@sukanyamsft @peterpogorski any chance it is April 20th, 2022? Would be nice if you can confirm some dates

source: gharchive/pull-request

authors: IvanAlekseev sukanyamsft


text:
Small typo in BDC workshop

Found a small typo in the BDC workshop on this page
https://github.com/microsoft/sqlworkshops/blob/master/sqlserver2019bigdataclusters/SQL2019BDC/01 - The Big Data Landscape.md
Activity: Review HDFS Tutorial
There are two primary storage concepts you will work with in SQL Server Big Data Clusters: the HDFS layer, and SQL Server. Fro HDFS, it's important to know the basics of how it works.

Fixed. Thanks for the catch!

authors: BuckWoody rgward

repo: microsoft/sqlworkshops


text:
Update adr.sql

There is no h in Witten :-)

Thanks for the catch! Since this site is more of a book rather than code, we make corrections using "Issues" as described in the main README.md page. This allows the author to maintain the concept and topic flow in each module. We've converted this PR to an Issue for you and the author will review after this training cycle.

authors: AaronBertrand BuckWoody


text:
Crash on RDP connection

Windows Terminal version (or Windows build number)
1.8.1521.0
Other Software
Microsoft Windows [Version 10.0.19042.1055]
Steps to reproduce
Start Terminal (either from local session or RDP)
Connect a new RDP session
Observe Terminal (and any child processes) is no longer running.
Expected Behavior
Terminal continues running across RDP connects/disconnects.
Actual Behavior
I see the following crash logs in Event Viewer:
Faulting application name: WindowsTerminal.exe, version: 1.8.2106.1001, time stamp: 0x60b64ad3
Faulting module name: Microsoft.UI.Xaml.dll, version: 2.5.2012.2003, time stamp: 0x5fc87886
Exception code: 0xc0000005
Fault offset: 0x00000000000df4af
Faulting process id: 0x502c
Faulting application start time: 0x01d75fde99430238
Faulting application path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe\Microsoft.UI.Xaml.dll
Report Id: 6cd58efd-60b4-47ca-a0fd-f325706fc589
Faulting package full name: Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Fault bucket 2238112546877327133, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.WindowsTerminal_1.8.1521.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.8.2106.1001
P4: 60b64ad3
P5: Microsoft.UI.Xaml.dll
P6: 2.5.2012.2003
P7: 5fc87886
P8: c0000005
P9: 00000000000df4af
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER904C.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9157.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9167.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9175.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER9195.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Window_ea24f84bb2ad8ddcd6855a771669148aa5dbf98_60528276_beebf310-482c-4636-b3a3-9d972986f8ca

Analysis symbol:
Rechecking for solution: 0
Report Id: 6cd58efd-60b4-47ca-a0fd-f325706fc589
Report Status: 268435456
Hashed bucket: d56910dc0d52099aaf0f5f80dbf7c71d
Cab Guid: 0

Okay this might be insane, but could you repro this with the Feedback Hub? That'll get us a stack trace we can use to actually identify the root cause here.
/feedback

I don't have WER uploads enabled on that machine.
I tried to build a debug build of Terminal and reproduce, but now the issue doesn't even happen on the build from the Store, either 🤔
Oh well, can probably close this until it happens again.

My crash stack is the same as https://github.com/microsoft/terminal/issues/10520

Going to reopen as it still occurs (now on Version: 1.9.1942.0), and is very frustrating :/

Hitting this as well. Can we use this issue to track pulling in the latest Microsoft.UI.Xaml.dll which should include https://github.com/microsoft/microsoft-ui-xaml/pull/5201 and allegedly fix this?

Since this is fixed in https://github.com/microsoft/microsoft-ui-xaml/pull/5201, which is in MUX 2.6.1, then I think we can just use the existing issue we have for "update to 2.6". Thanks all (sorry this dropped out of the triage queue)
/dup #10508

authors: Dan-Albrecht shuffle2 zadjii-msft

repo: microsoft/terminal


text:
AreSame/AreNotSame should use generic instead of object

By using generics, we are sure we can only compare two instances of the same type (including inheritance) while today it's possible to write Assert.AreSame(0, "foo"); which would obviously return false.

Marked as breaking change as it's a binary breaking change but we don't expect any issue after rebuild.

Fixed by #1430

repo: microsoft/testfx


text:
tfx extension create causes "error: Error: EISDIR: illegal operation on a directory, read".

I am creating an extension for our company containing multiple build/release tasks. They have some shared code which I wanted to make available to my co-workers as an NPM package as well as use in my own tasks.
I therefor created a folder next to my task folders containing the shared code and configured it as a stand alone NPM package. I then linked it to my tasks by using the "npm link" statement. This creates a symbolic link (as I understand) in the node_modules folder to the actual package location on my hard drive.
When running the 'tfx extension create' or 'tfx extension publish' commands the error from the issue title appears. In my understanding this is caused by the symbolic link which tfx can't traverse when building the package.
As a work-around I decided to not use a linked npm package but just reference the files directly and include them all in the extension. However, since the common code is outside the root of each of the tasks, the tasks fail when run after publish.
I feel the first issue should be addressed, but I understand that this might not happen overnight. So any help with a fix for my workaround (or any guidance of reusing code between multiple different tasks) you folks could point me to would be much appreciated
Kind regards,
Jeroen Vos

We're hitting this bug/limitation with the Azure ML AzDO task as well and have to do the workaround mentioned.

This also helps (making hard copies of all links inside node_modules):
rsync --archive --verbose --copy-links ./node_modules/ ./node_modules_cp/ && rm -r ./node_modules/ && mv ./node_modules_cp/ ./node_modules/

Same issue here, very annoying

authors: Vossekop dtzar marcopelegrini tiulpin

repo: microsoft/tfs-cli


text:
User-friendly way to initialize the submodule

Original line from the documentation:
git clone --recurse-submodules https://github.com/microsoft/triton-shared.git triton_shared

uses https to clone triton_shared, while "git@" is used explicitly by the submodule configuration which makes it fail if "git@" is not configured properly, for example, no key added.
Removing the protocol and changing the url to relative resolves this issue.
Thank you!

Thanks for taking the time to find issues in the documentation. Would changing the url to use https instead work? I'd prefer that approach over the relative url, mostly because it is not immediately clear how this works without having read the git submodule man page:
<repository> is the URL of the new submodule's origin repository.
This may be either an absolute URL, or (if it begins with ./ or ../), the location relative to the superproject's origin repository.

Also this doesn't work if the project's origin is different from github (say we host the repository on another provider).

Thanks for taking the time to find issues in the documentation. Would changing the url to use https instead work? I'd prefer that approach over the relative url, mostly because it is not immediately clear how this works without having read the git submodule man page:
<repository> is the URL of the new submodule's origin repository.
This may be either an absolute URL, or (if it begins with ./ or ../), the location relative to the superproject's origin repository.

Also this doesn't work if the project's origin is different from github (say we host the repository on another provider).

yes, if we change to "https" that should work better and will be more consistent with current documentation.
I think relative references are very common, here is the quote from git documentation:
"Since the URL in the .gitmodules file is what other people will first try to clone/fetch from, make sure to use a URL that they can access if possible. For example, .... When applicable, a relative URL can be helpful."
https://git-scm.com/book/en/v2/Git-Tools-Submodules

Anyway, I am ok with changing it to "https".
Thank you!

I think let's use the absolute https url since there might be cases where the users have their own internal mirror of triton-shared that isn't hosted on github. The absolute url will still work without requiring the triton repo to also be mirrored.

updated, please take a look, thank you!

repo: microsoft/triton-shared


text:
Update emitter to set extensions at the root of the document

Clear and concise description of the problem
This feature request proposes adding extensions defined on a Namespace at the root of an OpenApi document.
Typespec sample:
@service({
  title: "Suno"
})
@route("/createSong")
namespace Suno {
  @get op createSong(
    /** The requested song description, eg. `a country song about Thanksgiving` */
    @query topic: string,
    /** The requested song genre, eg. `Jazz` */
    @query genre?: string
    ): string;
}

@@runtime(Suno, {type: "oAuthPluginVault", "reference_id": "0123456-abcdef"}

Result:
openapi: 3.0.0
info:
 title: Suno
  description: Create any song you want based on a description
  version: 1.0.0
x-ai-runtimes:
 auth:
   type: oAuthPluginVault
   reference_id: 0123456-abcdef
paths:
 get:
      operationId: createSong
      description: Create a song given the user preferences
      parameters:
        - name: topic
          in: query
          required: true
          description: The requested song description, eg. `a country song about Thanksgiving`
          schema:
            type: string
        - name: genre
          in: query
          required: false
          description: The requested song genre, eg. `Jazz`
          schema:
            type: string
      responses:
        '200':
          description: The request has succeeded.
          content:
            application/json:
              schema:
                type: string

Checklist

[X] Follow our Code of Conduct
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

est: 3

repo: microsoft/typespec


text:
Update assignment of Json ReadOnlyMemory Property

Fixes: https://github.com/microsoft/typespec/issues/4778

API change check
API changes are not detected in this pull request.

authors: azure-sdk nisha-bhatia


text:
Linear probing or KNN evaluation of BEiT

Hello,
Thanks for the great work!
When I read the paper I found the results are fine-tuned end-to-end, and I am curious how BEiT performs on KNN evaluation or linear probing, like done with other pretraining methods such as contrastive learning.
I am recently playing with the BEiT models (both BEiT-base-16patch and BEiT-large-16patch) provided here and build knn and linear classification scripts following the experiment settings in the paper. I got the following results, which I think are a little bit weird:
For linear probing:
BEiT-large-16patch-224       18.28% (50 epochs, with mean pooling) | 18.19% (50 epochs, wo mean pooling)
BEiT-base-16patch-224       20.84% (50 epochs, with mean pooling) | 2.0% (100 epochs, wo mean pooling)
For KNN evaluation:
BEiT-large-16patch-224      top1/top5: 6.826, 13.744 (with mean pooling) | top1/top5: 2.804, 6.658 (wo mean pooling)
BEiT-base-16patch-224      top1/top5: 4.492,  9.88 (with mean pooling) | top1/top5: 2.236,  5.632 (wo mean pooling)
I guess there might be something wrong. Could you please help check if there are some issues, and if possible could you please provide some results or scripts for KNN and linear probing evaluation? Thanks!

@JegZheng Regarding to your original post where linear probing accuracy is low(see below), did you get significantly higher numbers than below? If so, can you share what fixes you do? I am using my own dataset to do pretrain + linear-probing. The linear accuracy is under my expectation.
"For linear probing:
BEiT-large-16patch-224 18.28% (50 epochs, with mean pooling) | 18.19% (50 epochs, wo mean pooling)
BEiT-base-16patch-224 20.84% (50 epochs, with mean pooling) | 2.0% (100 epochs, wo mean pooling)
"

@JegZheng Regarding to your original post where linear probing accuracy is low(see below), did you get significantly higher numbers than below? If so, can you share what fixes you do? I am using my own dataset to do pretrain + linear-probing. The linear accuracy is under my expectation.
"For linear probing: BEiT-large-16patch-224 18.28% (50 epochs, with mean pooling) | 18.19% (50 epochs, wo mean pooling) BEiT-base-16patch-224 20.84% (50 epochs, with mean pooling) | 2.0% (100 epochs, wo mean pooling) "

@LiweiPeng  Sorry I did not fix that issue. The linear probing setting could vary when using different pertaining methods and different data. Maybe we can ask the authors to see if they have any suggestions.

@JegZheng Thanks for the quick response. Based on the above paper results, it seems low linear probing results are expected.
One technique the paper used to improve linear probing is to select the best layer(e.g. BEiT-base 9th layer in hte paper). How much difference could it be between the best layer and last layer?

@LiweiPeng , @JegZheng We upload our linear probe code, you can have a try by this link
This code will train a linear classifier for each transformer layer in one forward pass, which can save many computing resources.

@addf400 Thanks for the quick response. This is very helpful.

@addf400  Awesome!

@addf400  Thanks!

Hey!
Seems like the linear probing problem was solved, but has anyone been able to solve k-NN classification problem?
I'm also getting super low numbers, similar to @JegZheng.
Can you maybe help here as well @addf400? Would be super appreciated!
Thanks in advance :)

authors: JegZheng LiweiPeng addf400 donglixp leonsick

repo: microsoft/unilm


text:
[nethost] update to 2020-10-19

Library name: nethost
New version number: 2020-10-19
Nethost should be updated to the version provided with .Net 5.

It would probably be better at this point to upgrade to the latest point release 5.0.7 which is revision 556582d964cc21b82a88d7154e915076f6f9008e on Jun 8th 2021

repo: microsoft/vcpkg


text:
OPTIONS in vcpkg_configure_cmake can not override variables in CMakeLists.txt

The line OPTIONS -DCMAKE_CXX_STANDARD=${CXX_STANDARD} take effect only if 0005-remove-CMAKE_CXX_STANDARD.patch (i.e. remove set(CMAKE_CXX_STANDARD 14) in the original CMakeLists.txt) is applied.
Why can't it override the variables defined in CMakeLists.txt?
ports/poppler/portfile.cmake
vcpkg_from_github(
    OUT_SOURCE_PATH SOURCE_PATH
    REPO freedesktop/poppler
    REF poppler-20.12.1
    SHA512 f692682689c0b0fcc3953a1cc157b6e1d2ce3ccab185189d6dc0807f1dd3ea2d1a9773d0b805079a30b3c8a3b0cf3ee83239ed48d7b08dc7762eba29c2033674
    HEAD_REF master
    PATCHES
        0001-remove-tests.patch
        0002-remove-utils.patch
        0003-remove-glib-and-GObject-introspection.patch
        0004-remove-Qt5-and-Qt6-support.patch
        0005-remove-CMAKE_CXX_STANDARD.patch
)

if("cpp17" IN_LIST FEATURES)
    set(CXX_STANDARD 17)
else()
    set(CXX_STANDARD 14)
endif()

message(${CXX_STANDARD})

vcpkg_configure_cmake(
    SOURCE_PATH ${SOURCE_PATH}
    PREFER_NINJA # Disable this option if project cannot be built with Ninja
    OPTIONS -DCMAKE_CXX_STANDARD=${CXX_STANDARD}
    #OPTIONS -DCMAKE_CXX_STANDARD=${CXX_STANDARD}
    # OPTIONS -DUSE_THIS_IN_ALL_BUILDS=1 -DUSE_THIS_TOO=2
    # OPTIONS_RELEASE -DOPTIMIZE=1
    # OPTIONS_DEBUG -DDEBUGGABLE=1
)

vcpkg_install_cmake()

file(REMOVE_RECURSE "${CURRENT_PACKAGES_DIR}/debug/include")

file(INSTALL ${SOURCE_PATH}/COPYING DESTINATION ${CURRENT_PACKAGES_DIR}/share/${PORT} RENAME copyright)

BTW, for the sample code at https://github.com/microsoft/vcpkg/blob/master/docs/maintainers/vcpkg_check_features.md
# ports/mimalloc/portfile.cmake
vcpkg_check_features(OUT_FEATURE_OPTIONS FEATURE_OPTIONS
  # Keyword FEATURES is optional if INVERTED_FEATURES are not used
    asm       MI_SEE_ASM
    override  MI_OVERRIDE
    secure    MI_SECURE
)

vcpkg_configure_cmake(
  SOURCE_PATH ${SOURCE_PATH}
  PREFER_NINJA
  OPTIONS
    # Expands to "-DMI_SEE_ASM=ON; -DMI_OVERRIDE=OFF; -DMI_SECURE=ON"
    ${FEATURE_OPTIONS}
)

It seems that OPTIONS can override the variables defined in CMakeLists.txt

Hi @playgithub
The OPTIONS parameter in vcpkg_configure_cmake can override options but not variables. If a variable it's not set, it is possible to set it with OPTIONS; but if the CMakeLists.txt declares the variable, it won't be overridden.

Options are declared using option(<option_name> "description" <value>)
Variables are declared using set(<variable_name> <value>)

You can read more here: https://cmake.org/cmake/help/latest/command/option.html
In the case of CXX_STANDARD, I think the best thing to do would be to create a patch that removes the hard-coded set(CXX_STANDARD 14) and instead let users control the standard using a toolchain file or a custom triplet.

let users control the standard using a toolchain file or a custom triplet

Use a triplet to control C++ standard is nice, has it been implemented?

authors: playgithub vicroms


text:
[New Port Request]  licensecc

Library name : licensecc
Library description : Copy protection, licensing library and license generator for Windows and Linux.
Source repository URL:
https://github.com/open-license-manager/licensecc
https://github.com/open-license-manager/lcc-license-generator
http://open-license-manager.github.io/licensecc/index.html

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now, consider making a pull request instead.

authors: IshaanKarnik PhoebeHui


text:
[boost-serialization] setting vcpkg to use dynamic libraries causes compiler error in DLL project

Package: boost:x86-windows-static -> 1.81.0
Describe the bug
when creating a windows DLL project, linking boost as a dynamic library is not possible and gives the following compiler errors.
however, linking as a static library builds fine.
Environment

OS: x64 Windows 10 VS 2019 16.11.23
Compiler: Microsoft (R) C/C++ Optimizing Compiler Version 19.29.30147 for x86
vcpkg-tool version:2022-12-14-7ae0d8527fb488fde10a89c2813802dc9b03b6f9

To Reproduce
Steps to reproduce the behavior:

./vcpkg install boost-serialization
create a DLL project in VS
use any boost serialization functions and include the corresponding header files
build the project with vcpkg configuration "use static library" set to "no" which is the default
observe compiler error

Expected behavior
should build fine and link boost as dynamic library
Failure logs
Severity    Code    Description Project File    Line    Suppression State
Error   C2491   'boost::archive::detail::archive_serializer_map<Archive>::insert': definition of dllimport function not allowed C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\archive_serializer_map.ipp    41
Error   C2491   'boost::archive::detail::archive_serializer_map<Archive>::erase': definition of dllimport function not allowed  C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\archive_serializer_map.ipp    49
Error   C2491   'boost::archive::basic_binary_iprimitive<Archive,Elem,Tr>::basic_binary_iprimitive': definition of dllimport function not allowed   C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\basic_binary_iprimitive.ipp   146
Error   C2491   'boost::archive::basic_binary_iprimitive<Archive,Elem,Tr>::~basic_binary_iprimitive': definition of dllimport function not allowed  C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\basic_binary_iprimitive.ipp   170
Error   C2491   'boost::archive::detail::archive_serializer_map<Archive>::insert': definition of dllimport function not allowed C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\archive_serializer_map.ipp    41
Error   C2491   'boost::archive::detail::archive_serializer_map<Archive>::erase': definition of dllimport function not allowed  C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\archive_serializer_map.ipp    49
...[redacted]

Please private your DLL project, thanks.
Please make sure your boost-serialization is installed under the dynamic triplet. I noticed that your boost is installed in x86-windows-static.
Package: boost:x86-windows-static -> 1.81.0

@Adela0814
Thanks for the response.
that was my bad. it also happens when using dynamic triplet.
Build started...
1>------ Build started: Project: xxx_DLL, Configuration: Debug Win32 ------
1>portable_binary_iarchive.cpp
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\archive_serializer_map.ipp(41,34): error C2491: 'boost::archive::detail::archive_serializer_map<Archive>::insert': definition of dllimport function not allowed
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\archive_serializer_map.ipp(49,34): error C2491: 'boost::archive::detail::archive_serializer_map<Archive>::erase': definition of dllimport function not allowed
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\archive_serializer_map.ipp(65,34): error C2491: 'boost::archive::detail::archive_serializer_map<Archive>::find': definition of dllimport function not allowed
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\basic_binary_iprimitive.ipp(36,45): error C2491: 'boost::archive::basic_binary_iprimitive<Archive,Elem,Tr>::init': definition of dllimport function not allowed
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\basic_binary_iprimitive.ipp(91,45): error C2491: 'boost::archive::basic_binary_iprimitive<Archive,Elem,Tr>::load': definition of dllimport function not allowed
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\basic_binary_iprimitive.ipp(103,45): error C2491: 'boost::archive::basic_binary_iprimitive<Archive,Elem,Tr>::load': definition of dllimport function not allowed
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\basic_binary_iprimitive.ipp(119,45): error C2491: 'boost::archive::basic_binary_iprimitive<Archive,Elem,Tr>::load': definition of dllimport function not allowed
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\basic_binary_iprimitive.ipp(130,45): error C2491: 'boost::archive::basic_binary_iprimitive<Archive,Elem,Tr>::load': definition of dllimport function not allowed
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\basic_binary_iprimitive.ipp(146,45): error C2491: 'boost::archive::basic_binary_iprimitive<Archive,Elem,Tr>::basic_binary_iprimitive': definition of dllimport function not allowed
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\basic_binary_iprimitive.ipp(170,46): error C2491: 'boost::archive::basic_binary_iprimitive<Archive,Elem,Tr>::~basic_binary_iprimitive': definition of dllimport function not allowed
1>portable_binary_oarchive.cpp
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\archive_serializer_map.ipp(41,34): error C2491: 'boost::archive::detail::archive_serializer_map<Archive>::insert': definition of dllimport function not allowed
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\archive_serializer_map.ipp(49,34): error C2491: 'boost::archive::detail::archive_serializer_map<Archive>::erase': definition of dllimport function not allowed
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\archive_serializer_map.ipp(65,34): error C2491: 'boost::archive::detail::archive_serializer_map<Archive>::find': definition of dllimport function not allowed
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\basic_binary_oprimitive.ipp(41,45): error C2491: 'boost::archive::basic_binary_oprimitive<Archive,Elem,Tr>::init': definition of dllimport function not allowed
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\basic_binary_oprimitive.ipp(57,45): error C2491: 'boost::archive::basic_binary_oprimitive<Archive,Elem,Tr>::save': definition of dllimport function not allowed
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\basic_binary_oprimitive.ipp(66,45): error C2491: 'boost::archive::basic_binary_oprimitive<Archive,Elem,Tr>::save': definition of dllimport function not allowed
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\basic_binary_oprimitive.ipp(77,45): error C2491: 'boost::archive::basic_binary_oprimitive<Archive,Elem,Tr>::save': definition of dllimport function not allowed
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\basic_binary_oprimitive.ipp(88,45): error C2491: 'boost::archive::basic_binary_oprimitive<Archive,Elem,Tr>::save': definition of dllimport function not allowed
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\basic_binary_oprimitive.ipp(99,45): error C2491: 'boost::archive::basic_binary_oprimitive<Archive,Elem,Tr>::basic_binary_oprimitive': definition of dllimport function not allowed
1>C:\dev\vcpkg\installed\x86-windows\include\boost\archive\impl\basic_binary_oprimitive.ipp(123,46): error C2491: 'boost::archive::basic_binary_oprimitive<Archive,Elem,Tr>::~basic_binary_oprimitive': definition of dllimport function not allowed
1>Generating Code...
1>Done building project "xxx.vcxproj" -- FAILED.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

I found the problem myself
this is an issue with the portable_binary_iarchive and portable_binary_oarchive which is not included in the standard boost but is an addon to the project.


text:
Error: Building package vtk:x64-windows failed with: BUILD_FAILED

Describe the bug
Instaling the package vtk:x64-windows causes a cmake error
Environment

OS: Windows 10
Package: vtk:x64-windows
Vcpkg version: 2019.09.12-nohash

To Reproduce
Steps to reproduce the behavior:
.\vcpkg install pcl[openni2,qt,pcap]:x64-windows --featurepackages
Expected behavior
I get the following error:
Error: Building package vtk:x64-windows failed with: BUILD_FAILED
Failure logs
config-x64-windows-out.log
Additional context
Other posts of similar issue solve it by using an earlier version of cmake such as 3.14.6 or earlier, or the packages default 3.14.0. I attempted a range of cmake versions, none of which were able to change the error. Even deleting my cmake folder and having vcpkg install the default version 3.14.0 did not fix the problem.
-- Configuring x64-windows
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
    Command failed: ninja -v
    Working Directory: D:/DEV/vcpkg/buildtrees/vtk/x64-windows-rel/vcpkg-parallel-configure
    Error code: 1
    See logs for more information:
      D:\DEV\vcpkg\buildtrees\vtk\config-x64-windows-out.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_cmake.cmake:293 (vcpkg_execute_required_process)
  ports/vtk/portfile.cmake:91 (vcpkg_configure_cmake)
  scripts/ports.cmake:94 (include)

Error: Building package vtk:x64-windows failed with: BUILD_FAILED

Hi @jonohribar
I have the same problem in #9322 - make sure you compiled Proj4 and vtk/pcl with the same version of Visual studio.
Then it worked for me.

Solved issue by installing component "Windows 10 SDK (10.0.18362.0)" through Visual Studio Installer

"Windows 10 SDK (10.0.18362.0)" requires visual studio 2019, other versions may not be recognized； oh， fuck MicroSoft...

authors: SLAMFuture jonohribar larshg


text:
[date] Update to 3.0.0

Update to version 3.0.0 to fix issue #9082.

Hi @acgetchell, could you test this PR?
Thanks.

Question:
after updating to 3.0  date offers to use date::tz in cmake as link_library, but that doesn't work. You need to use date::date-tz.
Is that another cmake bug (aliases broken) or is there another way continuing to use date::tz in a cosuming cmake project ?
Thx,

@yamcenutzer I think that because the official changed the target name, we should use the new name.

yes, ok,
I was just curious about thuis ALIAS feature of cmake. seems kinda useless to me now

When I try to use this, with the suggested date::date-tz I get:
CMake Error at /Users/adam/vcpkg/scripts/buildsystems/vcpkg.cmake:333 (_add_executable):
  Target "initialize" links to target "Threads::Threads" but the target was
  not found.  Perhaps a find_package() call is missing for an IMPORTED
  target, or an ALIAS target is missing?
Call Stack (most recent call first):
  CMakeLists.txt:80 (add_executable)

This goes away if I remove date::date-tz

authors: JackBoosY acgetchell yamcenutzer


text:
[vcpkg_fixup_pkgconfig] skip checks on paths with spaces

skip checks on paths with spaces
introduce VCPKG_SKIP_PKGCONFIG_CHECK to skip the pkg-config if set to true|on
some additional string replacements which might make spaces in paths work if a native pkg-config is used.

closes  #12689

pbc issue would be fixed via https://github.com/microsoft/vcpkg/pull/12732

@JackBoosY: I don't believe the case insensitive part since the output everything is clearly uppercase:
CreateProcessW("E:\vcpkg_cache\downloads\tools\cmake-3.17.2-windows\cmake-3.17.2-win32-x86\bin\cmake.exe" -DCURRENT_PORT_DIR=E:/VCPKG/test/vcpkg/scripts/detect_compiler -DCURRENT_BUILDTREES_DIR=E:/VCPKG/test/vcpkg/buildtrees/detect_compiler -DCURRENT_PACKAGES_DIR=E:/VCPKG/test/vcpkg/packages/detect_compiler_x64-windows-static -DCMD=BUILD -DTARGET_TRIPLET=x64-windows-static "-DTARGET_TRIPLET_FILE=E:\VCPKG\test\vcpkg\triplets\x64-windows-static.cmake" -DVCPKG_PLATFORM_TOOLSET=v142 -DDOWNLOADS=E:/vcpkg_cache/downloads -DVCPKG_CONCURRENCY=9 "-DGIT=C:/Program Files/Git/cmd/git.exe" -DVCPKG_ROOT_DIR=E:/VCPKG/test/vcpkg -DPACKAGES_DIR=E:/VCPKG/test/vcpkg/packages -DBUILDTREES_DIR=E:/VCPKG/test/vcpkg/buildtrees -D_VCPKG_INSTALLED_DIR=E:/VCPKG/test/vcpkg/installed -DDOWNLOADS=E:/vcpkg_cache/downloads -DVCPKG_MANIFEST_INSTALL=OFF -P "E:\VCPKG\test\vcpkg\scripts\ports.cmake")```

The same is true for a WSL build.

So there is a trick to make spaces work which is basically to transform -L${libdir} etc into -L"${libdir}" and probably do the same for -I<somevar> (although that does not affect the script). The only problem I have is that the regex replace (line 147-153) removing the -L flags does not work any longer although if I print the string they should be equal. So CMake seems to hide some invisible characters which I couldn't figure out yet to correct the REGEX

@Neumann-A It is always difficult to use cmake to deal with delimiters and quotes.

authors: JackBoosY Neumann-A PhoebeHui


text:
[scripts audit] vcpkg_copy_pdbs

See scripts-audit, issue #16188

/azp run

Hey @PhoebeHui, do you know what's going on with itpp:*-uwp? did that just break or something?

@strega-nil. I will take a look the failures.

@strega-nil, I could repro this issue locally, it can't find the fft package, FFT_INCLUDES was set to NOTFOUND, so it configured fail when use the FFT_INCLUDES, I have submmited PR#16385 to fix it.

Closing in favor of a single PR that contains all of these PRs. (to avoid destroying the CI system)

authors: PhoebeHui strega-nil


text:
[oatpp-openssl] new port

This is a new port for the oatpp suite of ports. Oat++ added an openssl module and this port provides access to that module.
This port can be helpful for those that wanted to use the openssl port and the oatpp-libressl port at the same time which is difficult because of conflicts between the openssl and libressl ports (oatpp-libressl, not surprisingly, depends on libressl). With this, oatpp-openssl is a drop-in replacement for oatpp-libressl without the conflicts.

Which triplets are supported/not supported? Have you updated the CI baseline?
all (I believe, linux and windows tested, including x64-windows-static-md)

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

LGTM, thanks for the PR and sorry for the long merge delay!


text:
[rsm-mmio] Add new port

Describe the pull request

What does your PR fix?
Adds a new port mmio

Which triplets are supported/not supported? Have you updated the CI baseline?
Only supports Linux/Windows + static linkage

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

@Ryan-rsm-McKenzie, thanks for your PR!
Could you change the 'tab' to 'space' in portfile.cmake?

authors: PhoebeHui Ryan-rsm-McKenzie


text:
[cpuinfo] fix arm64-osx build

Closes #28271

Thank you!

authors: JavierMatosD autoantwort


text:
[cdt] fix boost build

Otherwise cdt[core,boost] fails with
CMake Error at CMakeLists.txt:133 (target_link_libraries):
  INTERFACE library can only be used with the INTERFACE keyword of
  target_link_libraries

Thanks for the fix!

authors: BillyONeal autoantwort


text:
[curl] update to 8.2.0

Fixes #32640
Update port curl to the latest version 8.2.0.

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[ ] 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.

Feature brotli,c-ares,http2,idn,idn2,mbedtls,non-http,schannel,sspi,tool,websockets,winidn,winldap,winssl,wolfssl tested successfully in the following triplet:

x86-windows
x64-windows
x64-windows-static

Thanks for the update!


text:
[canvas-ity] New port

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

Close #33617

No feature needs to test.
Usage tested pass on x64-windows.

@BillyONeal Hi there, I've update this pr.

I noticed that the upstream is adding the license to the source code, so let's wait for the PR https://github.com/a-e-k/canvas_ity/pull/3 to merge.

I noticed that the upstream is adding the license to the source code

@Adela0814
This PR is about a year ago. It doesn't look like upstream is interested in merging it.

@BillyONeal Please review this PR again. It seems that the upstream has not been active for nearly a year.

@vicroms @dg0yt
I decide to close this PR. The upstream never accept PR and fix issue and has not been active for a year.
Perhaps not add this port to vcpkg is right choice.

I'm still here; I've just been busy with life and a bit of crunch mode at work.
I've now added a standalone LICENSE.txt to the repo.

I've now added a standalone LICENSE.txt to the repo.

@a-e-k
Thanks! I've reopen this PR.
@BillyONeal @vicroms @Adela0814
Please review this pr again.

Thanks for the new port!

authors: Adela0814 BillyONeal a-e-k xiaozhuai


text:
[fftwpp] Update to latest commit

Fixed a tab/space mix as well

Hi @Outurnate, can you please correct the Version field in the CONTROL file?

Pushed new commit with updated version string

authors: LilyWangL Outurnate


text:
The setting "FUNCTIONS_WORKER_RUNTIME" is "dotnet-isolated" after creating a C# project with .NET 6.0 LTS runtime

OS: Win10/M1
Build Version: 20230808.1
.NET Version: 7.0.306 & 6.0.412
Repro Steps:

Create a C# project with .NET 6.0 LTS runtime.
Check the local.setting.json file.

Expect:
The setting "FUNCTIONS_WORKER_RUNTIME" is "dotnet".

Actual:
The setting "FUNCTIONS_WORKER_RUNTIME" is "dotnet-isolated".

Could you verify this again please? I tried to reproduce it, but the FUNCTIONS_WORKER_RUNTIME setting is dotnet for my project.

@nturinski Verified this issue on the latest main branch build 20230816.1, I can not reproduce it for now.

Thanks for verifying. I'll close this for now then.

authors: nturinski v-xinda

repo: microsoft/vscode-azurefunctions


text:
Check for no remote branches

Fixes https://github.com/microsoft/vscode-azurestaticwebapps/issues/117
While ideally, we could just create a remote branch for the user, it's a complicated UI experience due to the fact that we can't guarantee that the repo they selected is what they currently have in the local workspace.  GitHub doesn't have an API call to create a new branch (as far as I know) so an error message seems better than nothing.
If anyone knows how to make it more of an error message or change the color of the message/icon, let me know.  I looked through the VS Code API and didn't see anything about it.
Before:

After:

I guess instead of a pick item, I could change the placeHolder though I don't know how immediately obvious that would be.

repo: microsoft/vscode-azurestaticwebapps


text:
Revise effectiveKitEnvironment to fixes #2354 and #2364

Signed-off-by: Yonggang Luo luoyonggang@gmail.com

@bobbrow Can you help me, why the CI are failed?

I'm not sure, but it's not your fault.  Other PR's all seem to be hitting this suddenly.

authors: bobbrow lygstate

repo: microsoft/vscode-cmake-tools


text:
4d1d9dd2-1e83-4578-8ea6-a15a0d2d975f

Type: Bug
Sorry, your request failed. Please report the following request id 4d1d9dd2-1e83-4578-8ea6-a15a0d2d975f and try again
Extension version: 0.21.2
VS Code version: Code 1.94.2 (384ff7382de624fb94dbaf6da11977bba1ecd427, 2024-10-09T16:08:44.566Z)
OS version: Darwin x64 24.0.0
Modes: Unsupported

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 x 2300)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
3, 3, 3

Memory (System)
16.00GB (0.63GB free)

Process Argv
--crash-reporter-id 9d57366f-7fd0-4025-84ec-b511ecabec2c

Screen Reader
yes

VM
0%

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
vscaac:30438847
c4g48928:30535728
azure-dev_surveyonecf:30548226
vscrpc:30673769
a9j8j154:30646983
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
9c06g630:31013171
a69g1124:31058053
dvdeprecation:31068756
dwnewjupyter:31046869
2f103344:31071589
impr_priority:31102340
nativerepl1:31139838
refactort:31108082
pythonrstrctxt:31112756
wkspc-onlycs-t:31132770
wkspc-ranged-t:31151552
cf971741:31144450
defaultse:31146405
iacca2:31156134
notype1cf:31157160
5fd0e150:31155592
iconenabled:31158251

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

repo: microsoft/vscode-copilot-release


text:
Code was given in the chat instead of being applied on my file

Type: Bug

Send a request with a file attached in the Edit with Copilot window
Watch the LLM randomly refuse to edit the given code directly within the IDE, and instead give the code in the text response

Extension version: 0.24.2024122001
VS Code version: Code - Insiders 1.97.0-insider (89f808979a5151bd91324e65d4f7ab1b62896983, 2024-12-20T05:04:19.167Z)
OS version: Windows_NT x64 10.0.26100
Modes:

System Info

Item
Value

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

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
15.68GB (4.12GB free)

Process Argv
--crash-reporter-id 82f8c7ba-53c1-4cf7-9188-1ddfa0bd94e5

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
vsaa593:30376534
py29gd2263:31024238
c4g48928:30535728
a9j8j154:30646983
962ge761:30841072
pythonnoceb:30776497
dsvsc014:30777825
dsvsc015:30821418
pythonmypyd1:30859725
h48ei257:31000450
pythontbext0:30879054
cppperfnew:30980852
pythonait:30973460
dvdeprecation:31040973
dwnewjupyter:31046869
newcmakeconfigv2:31071590
nativerepl1:31134653
pythonrstrctxt:31093868
nativeloc1:31118317
cf971741:31144450
e80f6927:31120813
iacca1:31150324
notype1:31143044
dwcopilot:31158714
h409b430:31177054
cf1a2727:31183122
c3hdf307:31184662
6074i472:31201624

/gifPlease

authors: MAXOUXAX joyceerhl


text:
add insertion support for monikers (MVP)

Add a "Moniker" option to the Docs Markdown menu.
Add sub-options

"range equals"
"range greater than or equal"
"range less than or equal"

Add behavior as follows if cursor is in the YAML metadata block:

"range equals" inserts monikerRange metadata with value "= " and the cursor after the equals sign.
"range greater than or equal" inserts monikerRange metadata with value ">= " and the cursor after the equals sign.
"range less than or equal"  inserts monikerRange metadata with value "<= " and the cursor after the equals sign.

If cursor is in the Markdown body of the file, add a moniker block as follows with the specified operator (the example uses equals) and the cursor after the operator:
:::moniker range="=":::
:::moniker-end:::

A post MVP enhancement would be to pull available values via API from the Docs moniker service.

work being done on PR #513

repo: microsoft/vscode-docs-authoring


text:
multiple windows everytime i click the icon of vscode, like the unsaved or closed files kept appearing

Environment (please complete the following information):

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

Describe the bug:

Repro steps:

Expected behavior:

Additional context:

This feedback should be shared on the VSCode github repo instead of on this devtools extension repo: https://github.com/microsoft/vscode
Thanks for your understanding.

authors: captainbrosset mniez

repo: microsoft/vscode-edge-devtools


text:
unable to go live my code

Environment (please complete the following information):

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

Describe the bug:

Repro steps:

Expected behavior:

Additional context:

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


text:
won't let me close instance. just stays there until I restart my pc

Environment

OS: Windows 11
Extension version 2.1.6

Describe the bug:
when I go into the sidebar in vs code, click on the edge icon, and try to close out an instance. it won't let me.
Repro steps:

open the sidebar
click the edge icon
open an instance of edge
in the sidebar click the X icon on an item in the instance list.

if this is just me, sorry
Expected behavior:
I expected it to simply close. but it didn't
Additional context:

Hi I have seen this happening from time to time, it is usually associated with another tab or window keeping the process open. If this is the case please:

Close all Edge instances
Open Windows Task Manager and validate that there are no Edge instances running.
Once you validated this, click on refresh on the Edge Devtools for VsCode extension and they should dissapear.

Thank you for reporting this issue and feel free to reopen if this does not work.


text:
Imports are incorrectly sorted and/or formatted.isort(E)

Error

If I add a space the issue is fixed, who decided import statements needs to separate?

This is the isort tool which handles import sorting. The default is to separate python standard libraries and any user libraries. This extension does not make that decision, this extension shows what is reported by isort in the UI.
Repo for the tool itself: https://github.com/PyCQA/isort
Settings you can use for the tool: https://pycqa.github.io/isort/docs/configuration/options.html
The setting you are looking for is "Lines Between Sections"

Thanks! I've disabled the extension altogether as I mainly use python for quick prototyping, therefore I don't have a need for isort. I can see where this would be useful when there's tens if not hundreds of import statements.
It shouldn't be On by default though, having to learn how to config yet another extension is just cumbersome, could I suggest putting these config options inside of Settings (not the json, but the Settings UI with checkboxes)

@Phatlynx The check setting is off by default:

It is in the UI:

Make sure that you have the latest version of the extension. As for the specific settings for isort the tool those are configured using whatever mechanism the tool supports.

authors: Phatlynx karthiknadig

repo: microsoft/vscode-isort