text:
All options have been expanded in call sites?

Hi there, just a quick question for you, I just updated the PlaywrightSharp nuget package to latest version and read the September report in which I saw there were breaking changes to the way we initialize the browser.
In the text after, it is said the the rest of the code should not have to be updated to work with the newer package, but in my case it breaks in multiple places... I would like to know if it's normal or if I did something wrong here...
For example, I was usually calling page.GoToAsync in the following way:
await page.GoToAsync(url, new GoToOptions
{
    WaitUntil = new WaitUntilNavigation[] { WaitUntilNavigation.Load }
});

but that doesn't seem to work anymore, it seems like the GoToOptions have been expanded so that we need to put them directly at call site like so:
await page.GoToAsync(url, LifecycleEvent.Load);

In this specific case, the call site is clearer and more concise which is really nice, but in other cases(for example when calling GetPdfAsync, the call has to explicitely specify each option while before I could simply pass the options object.
In my use case, I usually passed the PdfOptions around in my own api and only passed this object to the final function performing the actual conversion, which made it cleaner compared to now where I need to pass each option individually to each call. For now I copied the previous PdfOptions in my local code and I expand it to the final call but I was wondering if I did something wrong or not due to the note on the blog post saying that no other code would need to be updated....
Thanks in advance!

Hi @lvmajor. I will ship v1.4.1 very soon. In that version, we are dropping almost every option class. We are almost leaving LaunchOption, LaunchPersistentOptions, and BrowserContextOptions, which could be stored in config files by the user.

What is the motivation behind dropping all options classes? Couldn't there be overloads to let users call the functions with both the options class and the expanded/local params options?

First, thank you for being an early user @lvmajor.
As you may know, being in the v0 stage gives us the liberty to shape the API before reaching v1. Sorry to break your code 🤓
This is a product decision coming from the Playwright team. The idea is having the same philosophy across bindings.
We don't see the use of getting these options in the long term (except for the launch options for settings). As you saw, it looks prettier.
On the other hand, we have extensions methods in C#. That gives the user the extensibility to create an extension method with an option class if they want to.
That being said, if you have a use case scenario where you say that an option class would be helpful, please don't hesitate to share it.

Do you think we can close this @Ivmajor?

Sure sorry I should have done it yesterday

authors: kblok lvmajor

repo: microsoft/playwright-sharp


text:
[BUG]: Theming component issue

Describe the bug
Hi, we've imported the latest version of Theming component and tried to use the CoE Theme Editor. We can't use the app to change the colours for a test theme. The buttons to change the colours don't appear. I've tried both the Edge Chromium and Chrome browser and the issue happens for both.
Component (please tell us which flow or app you are experiencing issues with):

Solution - Theming
Version - 1.0.0.9
App - CoE Theme Editor

To Reproduce
Steps to reproduce the behavior:

Launch the CoE Editor app
Click on the button to change colour, nothing happens.

Expected behavior
I would expect the buttons to be available to change colours.
Screenshots

Have you followed the pre-requisites here https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup-theming#prerequisites and can you try opening the app in Edit mode and check if it shows up then?
Thank you
Manuela

Hi Manuela,
Thanks for steer. We did enable the pre-req feature but this was only done after the solution was imported. We’ve re-imported the solution and the colour selection boxes now appear.
However, when I attempt to change the Primary1Colour value from white to green, the app suddenly appears to restart. When I go back into the app and edit my theme, the Primary1Colour value remains as white.
If I attempt to change the colour again, the app appears to save the change but gets stuck at this screen. See the screenshot below for what I see:
@.***D73A8C.95C46EB0]
Could this be a potential bug with the app?
Regards,
@.D73A8C.95C46EB0]
[M&G Plc Logo]
@.D73A8C.95C46EB0]
Melvin Uy
Collaboration Technical Specialist
Workspace Collaboration O365
@. @.>
t. 02039770030 (Internal: 60030)
10 Fenchurch Avenue
London EC3M 5AG
@.***D73A8C.95C46EB0]
@.***D73A8C.95C46EB0]
@.***D73A8C.95C46EB0]
@.***D73A8C.95C46EB0]
From: Manuela Pichler @.>
Sent: 22 April 2021 18:49
To: microsoft/powerapps-tools @.>
Cc: Uy, Melvin @.>; Author @.>
Subject: Re: [microsoft/powerapps-tools] [BUG]: Theming component issue (#955)
Have you followed the pre-requisites here https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup-theming#prerequisites and can you try opening the app in Edit mode and check if it shows up then?
Thank you
Manuela
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/powerapps-tools/issues/955#issuecomment-825059342, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AO4ITOQWP4RJPUE2L7HRHP3TKBORZANCNFSM43MY6FRQ.
This email is confidential and should not be used by anyone who is not the original intended recipient. PGDS cannot accept liability for statements made which are clearly the sender's own and not made on behalf of the company. In addition no statement should be construed as giving investment advice within or outside the United Kingdom.
PGDS (UK ONE) LIMITED, 10 Fenchurch Avenue, London EC3M 5AG. Incorporated and registered in England and Wales. Registered Office as above. Registered number 1967719.
"PGDS" is the trading name of certain subsidiaries of M&G; plc (registered in England, number 11444019), whose registered office is at 10 Fenchurch Avenue, London EC3M 5AG, some of whose subsidiaries are authorised and regulated, as applicable, by the Prudential Regulation Authority and the Financial Conduct Authority. PGDS (UK One) Limited is part of the same corporate group as the Prudential Assurance Company. The Prudential Assurance Company is a direct/indirect subsidiary of M&G; plc, a company incorporated in the United Kingdom. The Prudential Assurance Company is not affiliated in any manner with Prudential Financial, Inc, a company whose principal place of business is in the United States of America or Prudential plc, an international group incorporated in the United Kingdom.
An e-mail reply to this address may be subject to interception or monitoring for operational reasons or for lawful business practices.

We have some outstanding issues with the Theming editor, see #467 and #421 but the app should work when in Edit mode. The issues appear to be only with Play mode.

Thanks for the steer, I’ve managed to get the app working in edit mode as advised.
Please go ahead and archive the ticket for this issue.
Regards,
@.D73A93.3724C880]
[M&G Plc Logo]
@.D73A93.3724C880]
Melvin Uy
Collaboration Technical Specialist
Workspace Collaboration O365
@. @.>
t. 02039770030 (Internal: 60030)
10 Fenchurch Avenue
London EC3M 5AG
@.***D73A93.3724C880]
@.***D73A93.3724C880]
@.***D73A93.3724C880]
@.***D73A93.3724C880]
From: Manuela Pichler @.>
Sent: 26 April 2021 11:13
To: microsoft/powerapps-tools @.>
Cc: Uy, Melvin @.>; Author @.>
Subject: Re: [microsoft/powerapps-tools] [BUG]: Theming component issue (#955)
We have some outstanding issues with the Theming editor, see #467https://github.com/microsoft/powerapps-tools/issues/467 and #421https://github.com/microsoft/powerapps-tools/issues/421 but the app should work when in Edit mode. The issues appear to be only with Play mode.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/powerapps-tools/issues/955#issuecomment-826706765, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AO4ITOVBNWEENH6S3F7DG33TKU4C7ANCNFSM43MY6FRQ.
This email is confidential and should not be used by anyone who is not the original intended recipient. PGDS cannot accept liability for statements made which are clearly the sender's own and not made on behalf of the company. In addition no statement should be construed as giving investment advice within or outside the United Kingdom.
PGDS (UK ONE) LIMITED, 10 Fenchurch Avenue, London EC3M 5AG. Incorporated and registered in England and Wales. Registered Office as above. Registered number 1967719.
"PGDS" is the trading name of certain subsidiaries of M&G; plc (registered in England, number 11444019), whose registered office is at 10 Fenchurch Avenue, London EC3M 5AG, some of whose subsidiaries are authorised and regulated, as applicable, by the Prudential Regulation Authority and the Financial Conduct Authority. PGDS (UK One) Limited is part of the same corporate group as the Prudential Assurance Company. The Prudential Assurance Company is a direct/indirect subsidiary of M&G; plc, a company incorporated in the United Kingdom. The Prudential Assurance Company is not affiliated in any manner with Prudential Financial, Inc, a company whose principal place of business is in the United States of America or Prudential plc, an international group incorporated in the United Kingdom.
An e-mail reply to this address may be subject to interception or monitoring for operational reasons or for lawful business practices.

Closing as duplicate of other Theming editor issues.

source: gharchive/issue

authors: manuelap-msft melmgcoe

repo: microsoft/powerapps-tools

license: MIT

license_type: permissive

license_source: github-api


text:
[Creator Starter Kit] BUG: Left navigation panel is blank in the Creator Kit Reference App

Describe the bug
Not able to see left navigation panel content in the Creator Kit Reference App
To Reproduce
Steps to reproduce the behavior:

Go to the Solution - Creator Kit, or Go to the Apps list
Click on 'Play' on the app - Creator Kit Reference App
See below when the app is played, left navigation is blank

@swatibece can you please confirm if you have enabled the Power Apps code components for canvas apps in the environment settings? Link to docs: https://docs.microsoft.com/en-us/power-apps/developer/component-framework/component-framework-for-canvas-apps#enable-the-power-apps-component-framework-feature

Yes, I had PCF enabled, but I have now again deleted the solution, imported again and it looks fine, except for some of the controls like....dialog box or panel control under "Surfaces" . The complete screen is not visible and need to do Zoom to 80 to 70 %. Also, tried changing screen resolution. Not sure if it is the issue only with system though.

authors: denisem-msft swatibece

repo: microsoft/powercat-creator-kit


text:
Support for PowerApps GCC

Do these Actions support PowerApps in GCC? Are there any known limitations? Thanks!

assuming the GH workflow runner has both access to the AAD/CDS endpoints in GCC and can pull GH actions from public GH, yes: should work. If you see issues, we'd like to know

I just tested the sample export and branch yaml file against a GCC test environment and it works successfully.
https://github.com/microsoft/powerplatform-actions-lab/blob/main/sample-workflows/export-and-branch-solution.yml

authors: SteveWinward anweiss davidjenni

repo: microsoft/powerplatform-actions


text:
spawn Unknown error when running synced offline power platform actions in UsGovDoD cloud

I am getting an error when running synced offline power platform actions on GitHub Enterprise server in US Gov DoD cloud.
I originally tested the power platform actions in an IL4-GCCH environment and was successful. After testing in IL4 I wanted to test in IL5-DoD tenant.
*IL5 tenant uses GitHub Enterprise server and requires manually syncing actions.
Steps

Manually Synced the power-platform-actions using action-sync tool to enterprise server.
Followed basic tutorial  for automating solution deployment

I have double checked the yaml file syntax and service principal settings / secret. When executing from IL5 I did have to update the cloud to UsGovDod. Looking to determine if this is an issue on my side our the code behind when communicating with DoD cloud.
Error

Debug

Workflow
name: export-and-branch-solution
# Export solution from DEV environment
#  unpack it and prepare, commit and push a git branch with the changes

on:
  workflow_dispatch:
    inputs:
      # Change this value
      solution_name:
        description: 'name of the solution to worked on from Power Platform'
        required: true
        default: ALMDemoSolution
       #Do Not change these values
      solution_exported_folder:
        description: 'folder name for staging the exported solution *do not change*'
        required: true
        default: out/exported/
      solution_folder:
        description: 'staging the unpacked solution folder before check-in *do not change*'
        required: true
        default: out/solutions/
      solution_target_folder:
       description: 'folder name to be created and checked in *do not change*'
       required: true
       default: solutions/
env:
#edit your values here
  ENVIRONMENT_URL: '<URL>'
  CLIENT_ID: '<Client Id>'
  TENANT_ID: '<Tenant Id>'
permissions:
  contents: write
jobs:
  export-from-dev:
    runs-on: [<Runner Tag>]
    env:
      RUNNER_DEBUG: 1

    steps:
    - uses: actions/checkout@v2
      with:
        lfs: true

    - name: who-am-i action
      uses: <synced repo>/powerplatform-actions/who-am-i@v0
      with:
        environment-url: ${{env.ENVIRONMENT_URL}}
        app-id: ${{env.CLIENT_ID}}
        client-secret: ${{ secrets.PowerPlatformSPN }}
        tenant-id: ${{env.TENANT_ID}}
        cloud: UsGovDod

    - name: export-solution action
      uses: <synced repo>/powerplatform-actions/export-solution@v0
      with:
        environment-url: ${{env.ENVIRONMENT_URL}}
        app-id: ${{env.CLIENT_ID}}
        client-secret: ${{ secrets.PowerPlatformSPN }}
        tenant-id: ${{env.TENANT_ID}}
        solution-name: ${{ github.event.inputs.solution_name }}
        solution-output-file: ${{ github.event.inputs.solution_exported_folder}}/${{ github.event.inputs.solution_name }}.zip
        cloud: UsGovDod

    - name: unpack-solution action
      uses: <synced repo>/powerplatform-actions/unpack-solution@v0
      with:
        solution-file: ${{ github.event.inputs.solution_exported_folder}}/${{ github.event.inputs.solution_name }}.zip
        solution-folder: ${{ github.event.inputs.solution_folder}}/${{ github.event.inputs.solution_name }}
        solution-type: 'Unmanaged'
        overwrite-files: true

    - name: branch-solution, prepare it for a PullRequest
      uses: <synced repo>/powerplatform-actions/branch-solution@v0
      with:
        solution-folder: ${{ github.event.inputs.solution_folder}}/${{ github.event.inputs.solution_name }}
        solution-target-folder: ${{ github.event.inputs.solution_target_folder}}/${{ github.event.inputs.solution_name }}
        repo-token: ${{ secrets.GITHUB_TOKEN }}
        allow-empty-commit: true```

Running with latest, it advises PAC needs to be installed on runner. Thinking this might be the issue... ?

We documented changes for v1 actions: https://learn.microsoft.com/en-us/power-platform/alm/devops-github-available-actions#helper-tasks

Perfect! Updating the jobs to v1 and adding the install Power Platform tools task has corrected the issue. Thank you @petrochuk

authors: DevonAleshireMSFT petrochuk


text:
Sliders should be snapped to the correct end when out of bounds

Affects all sliders.

Still repros.

authors: abchatra pelikhan samelhusseini

repo: microsoft/pxt-arcade


text:
Type annotation not supported for PEP-526

Environment data

Language Server version: v2020.7.3
OS and version: Ubuntu 16.04.5 LTS
Python version (& distribution if applicable, e.g. Anaconda): Python 3.6.10

Expected behaviour
No error message. According to PEP 526 https://www.python.org/dev/peps/pep-0526/#global-and-local-variable-annotations
It should be OK to initialize a List with a type and initial value.
Actual behaviour
Error message with: Type annotation not supported for this type of expression
Logs
Type annotation not supported for this type of expression

Code Snippet / Additional information
my_varibale: List[MyClass] = []

This should work fine. Are you sure you're importing List from typing? Is it perhaps redeclared or reassigned within your source file?

Problem solved.
I used this annotation with a value in a dict, something like:
myDict[mykey]: List[myclass] = []

that is not working. thank you for you help.

Ah yes, you cannot use an annotation on an expression like myDict[mykey]. That expression already has a type that is defined by the myDict symbol.
For example, you could do the following:
myDict: Dict[str, List[MyClass]] = {}
myDict[mykey] = []

authors: WuZhuoran erictraut

repo: microsoft/pylance-release


text:
Is it possible to realize weighted machine learning on Qlib?

❓ Questions and Help
I want to give different weights to each stock based on market value, and  train the lightGBM model with the samples and their weights. But it seems troublesome for me to realize weighted machine learning under the framework of Qlib.
If I can get the weight for each stock outside Qlib, is it possible to realize weighted machine learning on Qlib?
I think I should modify codes in Qlib.contrib.model?
Thanks!

@JessieJie1998
Hi, it is possible to train model with weighted samples in Qlib.
Here is an example from my personal code base.

The weights are stored as a column in the dataset.
You can follow this example.
We may release examples with weighted samples in the future.

@you-n-g Thanks for your prompt reply

repo: microsoft/qlib


text:
Allow reflection to find type in loaded assembly

Two changes to QuantumMachineFactory here, to address issues I found while consuming this from IQ#:

Take an IWorkspace parameter instead of a Workspace parameter.
Load the type directly from the already-loaded assembly with the expected name, rather than using Type.GetType(), which seems to sometimes require an AssemblyQualifiedName including version number and public key token in order to load the type successfully. (Open to suggestions here, in case there's a simpler way of doing this, but this seems to work.)

Thanks for trying this out! Did you do anything special such that the existing Type.GetType() call was succeeding? When I tried to call the code using Type.GetType(), it couldn't find the assembly (even if it had already been loaded) unless I also included the version and the PublicKeyToken in the type string, i.e., in a format like this:
System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
I suppose we could always expose both versions of this, if we need to obtain the Type in different ways. IQ# does its own package loading and management at runtime, so I guess it's not surprising that this behaves differently.

In reply to: 414007852 [](ancestors = 414007852)

No, I don't think I needed to do anything to get Type.GetType to work. Could you post the error message you get from it?

Could it have something to do with IQ# using signed versions of the IonQ assembly? That could mean that Type.GetType would fail for the standalone executable as well if it uses a signed version. (I'm not sure if the versions we have been using for testing have been signed or not.) We could try specifying just the assembly name and public key token (but not the version), but I am not sure if the public key token stays the same or changes when the version number is changed.

Below is the error I get. I'll try just specifying the PublicKeyToken and not the version; I think that should be consistent for all signed versions, but I'd need to confirm this.
System.IO.FileNotFoundException
  HResult=0x80070002
  Message=Could not load file or assembly 'Microsoft.Quantum.Providers.IonQ, Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
  Source=<Cannot evaluate the exception source>
  StackTrace:
  System.Private.CoreLib.dll!System.RuntimeTypeHandle.GetTypeByName(string name, bool throwOnError, bool ignoreCase, System.Runtime.CompilerServices.StackCrawlMarkHandle stackMark, System.Runtime.CompilerServices.ObjectHandleOnStack assemblyLoadContext, bool loadTypeFromPartialName, System.Runtime.CompilerServices.ObjectHandleOnStack type, System.Runtime.CompilerServices.ObjectHandleOnStack keepalive) Unknown
  System.Private.CoreLib.dll!System.RuntimeTypeHandle.GetTypeByName(string name, bool throwOnError, bool ignoreCase, ref System.Threading.StackCrawlMark stackMark, System.Runtime.Loader.AssemblyLoadContext assemblyLoadContext, bool loadTypeFromPartialName) Unknown
  System.Private.CoreLib.dll!System.RuntimeType.GetType(string typeName, bool throwOnError, bool ignoreCase, ref System.Threading.StackCrawlMark stackMark) Unknown
  System.Private.CoreLib.dll!System.Type.GetType(string typeName, bool throwOnError) Unknown
  Microsoft.Azure.Quantum.Client.dll!Microsoft.Azure.Quantum.QuantumMachineFactory.CreateMachine(Microsoft.Azure.Quantum.Workspace workspace, string targetName, string storageAccountConnectionString) Unknown
  Microsoft.Quantum.IQSharp.AzureClient.dll!Microsoft.Quantum.IQSharp.AzureClient.AzureClient.SubmitJobAsync(Microsoft.Jupyter.Core.IChannel channel, Microsoft.Quantum.IQSharp.IOperationResolver operationResolver, string operationName) Line 162 C#
> Microsoft.Quantum.IQSharp.AzureClient.dll!Microsoft.Quantum.IQSharp.AzureClient.SubmitMagic.RunAsync(string input, Microsoft.Jupyter.Core.IChannel channel) Line 63 C#
  Microsoft.Quantum.IQSharp.AzureClient.dll!Microsoft.Quantum.IQSharp.AzureClient.AzureClientMagicBase.Run(string input, Microsoft.Jupyter.Core.IChannel channel) Line 35 C#

In reply to: 630504039 [](ancestors = 630504039)

source: gharchive/pull-request

authors: rmshaffer samarsha

repo: microsoft/qsharp-runtime


text:
Extend submitter factory

This change extends the submitter factory such that it can create new QIR submitters for standalone executables.

/azp run

/azp run

Closing in favor of  https://github.com/microsoft/qsharp-runtime/pull/1004.


text:
Need a way to add custom native UI components

Summary
Same way like react-native-windows / iOS / Android's documentation to support add custom native UI component.
Motivation
I'm developing a native panoramic video player for react-native, for now I have been packaged it for react native on iOS platform. And I hope use the same core player component running on macOS by using react-native framework, also other platforms(Windows and Android).
I have been checked the documentation about react-native-macos, but there is no content about native UI component development like the react-native-windows.
Hope provide a way to realize it, thanks.
Basic Example
No response
Open Questions
No response

Most of the iOS instructions apply 100% to macOS. The difference is you're using appkit instead of UIKit, but that's about it. It's the same native module code, same macros, same label of Swift support, etc.

Most of the iOS instructions apply 100% to macOS. The difference is you're using appkit instead of UIKit, but that's about it. It's the same native module code, same macros, same label of Swift support, etc.

Thank you! I'll have a try :)

Closing this as the issue is resolved!

authors: Bijiabo HeyImChris Saadnajmi

repo: microsoft/react-native-macos


text:
Sample for Multiple Windows

Summary
Filing issue to raise discussion on whether we officially want to support the multiple windows scenario for RNW. If so, let's create a sample and make sure this configuration is tested in our release validation.
Motivation

Basic Example
No response
Open Questions
No response

Has there been any progress on this?

authors: SBS-randerson chiaramooney

repo: microsoft/react-native-windows-samples


text:
Use LSTUR Model with own Data

Description
I am trying to use the LSTUR model with a dataset about purchase data, but I don't understand which format data have to pass to the model.
In the example:
 model = LSTURModel(hparams, iterator, seed=seed)
Is data stored inside the "iterator" object?

How can I transform my dataset into the correct format to use LSTUR?

good question

authors: Creat-King claraMarti

repo: microsoft/recommenders


text:
fairness-interpretability-dashboard-income-prediction.ipynb / from raiwidgets import ExplanationDashboard command --> TypeError: init() got an unexpected keyword argument 'unbound_message'

Describe the bug
When running the fairness-interpretability-dashboard-income-prediction.ipynb notebook, the command:
from raiwidgets import ExplanationDashboard
returns the following error:
TypeError: init() got an unexpected keyword argument 'unbound_message'
To Reproduce
Steps to reproduce the behavior:

Go to Azure Machine Learning Service
Click on Notebook
Upload fairness-interpretability-dashboard-income-prediction.ipynb
Run through notebook
Scroll down to command 'from raiwidgets import ExplanationDashboard'
See error

Stack trace
TypeError                                 Traceback (most recent call last)
Cell In [13], line 1
----> 1 from raiwidgets import ExplanationDashboard
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/raiwidgets/init.py:7
4 """Package for the fairness, explanation, and error analysis widgets."""
6 from .version import version
----> 7 from .error_analysis_dashboard import ErrorAnalysisDashboard
8 from .explanation_dashboard import ExplanationDashboard
9 from .fairness_dashboard import FairnessDashboard
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/raiwidgets/error_analysis_dashboard.py:6
1 # Copyright (c) Microsoft Corporation
2 # Licensed under the MIT License.
4 """Defines the ErrorAnalysis dashboard class."""
----> 6 from flask import jsonify, request
8 from .constants import ModelTask
9 from .dashboard import Dashboard
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/flask/init.py:4
1 from markupsafe import escape
2 from markupsafe import Markup
----> 4 from . import json as json
5 from .app import Flask as Flask
6 from .app import Request as Request
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/flask/json/init.py:8
4 import typing as t
6 from jinja2.utils import htmlsafe_json_dumps as _jinja_htmlsafe_dumps
----> 8 from ..globals import current_app
9 from .provider import _default
11 if t.TYPE_CHECKING:  # pragma: no cover
File /anaconda/envs/azureml_py38/lib/python3.8/site-packages/flask/globals.py:56
54 _cv_app: ContextVar["AppContext"] = ContextVar("flask.app_ctx")
55 __app_ctx_stack = _FakeStack("app", _cv_app)
---> 56 app_ctx: "AppContext" = LocalProxy(  # type: ignore[assignment]
57     _cv_app, unbound_message=_no_app_msg
58 )
59 current_app: "Flask" = LocalProxy(  # type: ignore[assignment]
60     _cv_app, "app", unbound_message=_no_app_msg
61 )
62 g: "_AppCtxGlobals" = LocalProxy(  # type: ignore[assignment]
63     _cv_app, "g", unbound_message=_no_app_msg
64 )
TypeError: init() got an unexpected keyword argument 'unbound_message'
Expected behavior
This command should execute without error.
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser:  Chrome
Python version: Python 3.8 - AzureML
raiwidgets and responsibleai package versions: 0.24.1, 0.24.1

@slsu0424 can you please try upgrading your version of flask in your environment:
pip install --upgrade flask
It looks like the error is coming from flask package.  What is your flask package version?  The latest is 2.2.3:
https://pypi.org/project/Flask/

@slsu0424 can you please try upgrading your version of flask in your environment: pip install --upgrade flask It looks like the error is coming from flask package. What is your flask package version? The latest is 2.2.3: https://pypi.org/project/Flask/

Thank you, that solved the issue for me!

authors: ExOblivione imatiach-msft slsu0424

repo: microsoft/responsible-ai-toolbox


text:
[WIP] upgrade nrwl packages to latest to fix ci-notebook UI build errors

Description
The builds are currently failing due to errors in ci-notebook UI tests pipeline:
> nx run localization:build
Error loading `tslib` helper library.
Package subpath './package.json' is not defined by "exports" in D:\a\responsible-ai-toolbox\responsible-ai-toolbox\node_modules\rollup-plugin-typescript2\node_modules\tslib\package.json

> nx run mlchartlib:build
Error loading `tslib` helper library.
Package subpath './package.json' is not defined by "exports" in D:\a\responsible-ai-toolbox\responsible-ai-toolbox\node_modules\rollup-plugin-typescript2\node_modules\tslib\package.json

This PR attempts to fix this by upgrading nrwl to latest packages.
Note: I had to also run this command after upgrading nrwl:
npm install -g nx
nx g @nrwl/workspace:fix-configuration

Checklist

[ ] I have added screenshots above for all UI changes.
[ ] I have added e2e tests for all UI changes.
[ ] Documentation was updated if it was needed.

closing as this did not fix the issue - there were other issues when I tried to upgrade


text:
No documentation on adding bash tabs

I have the Linux sybsystem installed on my Windows machine, but in the Cascadia window there's no option to create a new bash tab.
I didn't see any documentation on how to edit the configuration to enable this

I think as we stabilize the settings format, documentation on how to do this is definitely something we should add.
Even a quick docs/howto/AddACustomProfile.md file would probably be very helpful.
@bitcrazed @cinnamon-msft

This is how I enable bash in Windows Terminal:

Use the uuidgen tool in Visual Studio Command Prompt to generate a guid
Copy a profile in Windows Terminal's setting profile, replace:

guid with the one you generated
name : wsl
commandline: ubuntu.exe
icon: you can find it in C:\Program Files\WindowsApps\ where ubuntu is located

Answered; thanks @jeffery-song.

authors: DHowett-MSFT EranGon Jeffery-Song zadjii-msft

repo: microsoft/terminal


text:
Missing instructions on how to cancel a long running operation.

In cmd and other terminals I can CTRL-C to stop ng serve operation. In windows terminal I can't  do that. I'm looking through the stackoverflow, and documentation and I don't see an action that does this. Or any tips on  how to add a  custom action to do this.

{     "$schema": "https://aka.ms/terminal-profiles-schema",     "actions":      [         {             "command":              {                 "action": "copy",                 "singleLine": false             },             "keys": "ctrl+c"         },         {             "command": "find",             "keys": "ctrl+shift+f"         },         {             "command": "paste",             "keys": "ctrl+v"         },         {             "command":              {                 "action": "splitPane",                 "split": "auto",                 "splitMode": "duplicate"             },             "keys": "alt+shift+d"         }     ],     "alwaysShowTabs": false,     "copyFormatting": "none",     "copyOnSelect": false,     "defaultProfile": "{edb4a67f-c47a-5b4c-8893-7b8ab051e892}",     "disableAnimations": true,     "experimental.rendering.forceFullRepaint": true,     "initialCols": 160,     "initialRows": 67,     "largePasteWarning": false,     "launchMode": "default",     "multiLinePasteWarning": false,     "profiles":      {         "defaults": {},         "list":          [             {                 "acrylicOpacity": 0.34999999999999998,                 "colorScheme": "One Half Dark",                 "commandline": "powershell.exe",                 "cursorShape": "filledBox",                 "font":                  {                     "face": "Anonymous Pro for Powerline"                 },                 "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",                 "hidden": false,                 "name": "Windows PowerShell",                 "scrollbarState": "hidden",                 "useAcrylic": false             },             {                 "colorScheme": "Solarized Dark",                 "commandline": "cmd.exe",                 "font":                  {                     "face": "DejaVu Sans Mono for Powerline"                 },                 "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",                 "hidden": false,                 "name": "Command Prompt"             },             {                 "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",                 "hidden": false,                 "name": "Azure Cloud Shell",                 "source": "Windows.Terminal.Azure"             },             {                 "guid": "{2ece5bfe-50ed-5f3a-ab87-5cd4baafed2b}",                 "hidden": false,                 "name": "Git Bash",                 "source": "Git"             },             {                 "acrylicOpacity": 0.78000000000000003,                 "antialiasingMode": "cleartype",                 "backgroundImage": null,                 "backgroundImageOpacity": 0.17000000000000001,                 "backgroundImageStretchMode": "none",                 "colorScheme": "Dracula",                 "commandline": "C:\\Users\\daniel.mejia\\scoop\\apps\\Commandbox\\current\\box.exe",                 "cursorShape": "filledBox",                 "experimental.retroTerminalEffect": false,                 "font":                  {                     "face": "DejaVu Sans Mono for Powerline",                     "size": 10                 },                 "intenseTextStyle": "none",                 "name": "Commandbox",                 "padding": "5",                 "scrollbarState": "hidden",                 "startingDirectory": "%USERPROFILE%",                 "suppressApplicationTitle": true,                 "tabTitle": "Commandbox",                 "useAcrylic": false             },             {                 "acrylicOpacity": 0.45000000000000001,                 "backgroundImage": null,                 "backgroundImageAlignment": "top",                 "backgroundImageOpacity": 0.16,                 "backgroundImageStretchMode": "none",                 "bellStyle": "none",                 "colorScheme": "Campbell",                 "commandline": "wsl.exe ~ -d Ubuntu-20.04",                 "cursorHeight": 43,                 "cursorShape": "emptyBox",                 "experimental.retroTerminalEffect": false,                 "font":                  {                     "face": "DejaVu Sans Mono for Powerline"                 },                 "guid": "{07b52e3e-de2c-5db4-bd2d-ba144ed6c273}",                 "hidden": false,                 "name": "Ubuntu",                 "scrollbarState": "hidden",                 "source": "Windows.Terminal.Wsl",                 "startingDirectory": null,                 "useAcrylic": false             },             {                 "commandline": "wsl.exe ~ -d NixOS",                 "guid": "{c397f356-5e7b-55bc-956b-8cb4b9762c26}",                 "hidden": false,                 "name": "NixOS",                 "source": "Windows.Terminal.Wsl"             },             {                 "acrylicOpacity": 0.78000000000000003,                 "antialiasingMode": "cleartype",                 "backgroundImage": null,                 "backgroundImageOpacity": 0.17000000000000001,                 "backgroundImageStretchMode": "none",                 "colorScheme": "Dracula",                 "commandline": "C:\\Development\\Tools\\Commandbox\\box.exe",                 "cursorShape": "filledBox",                 "experimental.retroTerminalEffect": false,                 "font":                  {                     "face": "DejaVu Sans Mono for Powerline",                     "size": 10                 },                 "guid": "{a9684815-03cd-4d9c-9cad-26196592ad81}",                 "intenseTextStyle": "none",                 "name": "Rise",                 "padding": "5",                 "scrollbarState": "hidden",                 "startingDirectory": "%USERPROFILE%",                 "suppressApplicationTitle": true,                 "tabTitle": "Rise and Sync",                 "useAcrylic": true             }         ]     },     "schemes":      [         {             "background": "#0C0C0C",             "black": "#0C0C0C",             "blue": "#0037DA",             "brightBlack": "#767676",             "brightBlue": "#3B78FF",             "brightCyan": "#61D6D6",             "brightGreen": "#16C60C",             "brightPurple": "#B4009E",             "brightRed": "#E74856",             "brightWhite": "#F2F2F2",             "brightYellow": "#F9F1A5",             "cursorColor": "#FFFFFF",             "cyan": "#3A96DD",             "foreground": "#CCCCCC",             "green": "#13A10E",             "name": "Campbell",             "purple": "#881798",             "red": "#C50F1F",             "selectionBackground": "#FFFFFF",             "white": "#CCCCCC",             "yellow": "#C19C00"         },         {             "background": "#012456",             "black": "#0C0C0C",             "blue": "#0037DA",             "brightBlack": "#767676",             "brightBlue": "#3B78FF",             "brightCyan": "#61D6D6",             "brightGreen": "#16C60C",             "brightPurple": "#B4009E",             "brightRed": "#E74856",             "brightWhite": "#F2F2F2",             "brightYellow": "#F9F1A5",             "cursorColor": "#FFFFFF",             "cyan": "#3A96DD",             "foreground": "#CCCCCC",             "green": "#13A10E",             "name": "Campbell Powershell",             "purple": "#881798",             "red": "#C50F1F",             "selectionBackground": "#FFFFFF",             "white": "#CCCCCC",             "yellow": "#C19C00"         },         {             "background": "#26292E",             "black": "#070612",             "blue": "#BD93F9",             "brightBlack": "#6272A4",             "brightBlue": "#0E90B0",             "brightCyan": "#A4FFFF",             "brightGreen": "#50FA7B",             "brightPurple": "#C14BD9",             "brightRed": "#C73B86",             "brightWhite": "#FFFFFF",             "brightYellow": "#40C963",             "cursorColor": "#F8F8F2",             "cyan": "#8BE9FD",             "foreground": "#AB42BD",             "green": "#898D96",             "name": "Dracula",             "purple": "#8C8D99",             "red": "#FF5555",             "selectionBackground": "#656970",             "white": "#F8F8F2",             "yellow": "#F1FA8C"         },         {             "background": "#282C34",             "black": "#282C34",             "blue": "#61AFEF",             "brightBlack": "#5A6374",             "brightBlue": "#61AFEF",             "brightCyan": "#56B6C2",             "brightGreen": "#98C379",             "brightPurple": "#C678DD",             "brightRed": "#E06C75",             "brightWhite": "#DCDFE4",             "brightYellow": "#E5C07B",             "cursorColor": "#FFFFFF",             "cyan": "#56B6C2",             "foreground": "#DCDFE4",             "green": "#98C379",             "name": "One Half Dark",             "purple": "#C678DD",             "red": "#E06C75",             "selectionBackground": "#FFFFFF",             "white": "#DCDFE4",             "yellow": "#E5C07B"         },         {             "background": "#FAFAFA",             "black": "#383A42",             "blue": "#0184BC",             "brightBlack": "#4F525D",             "brightBlue": "#61AFEF",             "brightCyan": "#56B5C1",             "brightGreen": "#98C379",             "brightPurple": "#C577DD",             "brightRed": "#DF6C75",             "brightWhite": "#FFFFFF",             "brightYellow": "#E4C07A",             "cursorColor": "#4F525D",             "cyan": "#0997B3",             "foreground": "#383A42",             "green": "#50A14F",             "name": "One Half Light",             "purple": "#A626A4",             "red": "#E45649",             "selectionBackground": "#FFFFFF",             "white": "#FAFAFA",             "yellow": "#C18301"         },         {             "background": "#000000",             "black": "#000000",             "blue": "#268BD2",             "brightBlack": "#073642",             "brightBlue": "#839496",             "brightCyan": "#93A1A1",             "brightGreen": "#586E75",             "brightPurple": "#6C71C4",             "brightRed": "#CB4B16",             "brightWhite": "#FDF6E3",             "brightYellow": "#657B83",             "cursorColor": "#FFFFFF",             "cyan": "#2AA198",             "foreground": "#839496",             "green": "#859900",             "name": "Solarized Dark",             "purple": "#D33682",             "red": "#DC322F",             "selectionBackground": "#FFFFFF",             "white": "#EEE8D5",             "yellow": "#B58900"         },         {             "background": "#FDF6E3",             "black": "#002B36",             "blue": "#268BD2",             "brightBlack": "#073642",             "brightBlue": "#839496",             "brightCyan": "#93A1A1",             "brightGreen": "#586E75",             "brightPurple": "#6C71C4",             "brightRed": "#CB4B16",             "brightWhite": "#FDF6E3",             "brightYellow": "#657B83",             "cursorColor": "#002B36",             "cyan": "#2AA198",             "foreground": "#657B83",             "green": "#859900",             "name": "Solarized Light",             "purple": "#D33682",             "red": "#DC322F",             "selectionBackground": "#FFFFFF",             "white": "#EEE8D5",             "yellow": "#B58900"         },         {             "background": "#000000",             "black": "#000000",             "blue": "#3465A4",             "brightBlack": "#555753",             "brightBlue": "#729FCF",             "brightCyan": "#34E2E2",             "brightGreen": "#8AE234",             "brightPurple": "#AD7FA8",             "brightRed": "#EF2929",             "brightWhite": "#EEEEEC",             "brightYellow": "#FCE94F",             "cursorColor": "#FFFFFF",             "cyan": "#06989A",             "foreground": "#D3D7CF",             "green": "#4E9A06",             "name": "Tango Dark",             "purple": "#75507B",             "red": "#CC0000",             "selectionBackground": "#FFFFFF",             "white": "#D3D7CF",             "yellow": "#C4A000"         },         {             "background": "#FFFFFF",             "black": "#000000",             "blue": "#3465A4",             "brightBlack": "#555753",             "brightBlue": "#729FCF",             "brightCyan": "#34E2E2",             "brightGreen": "#8AE234",             "brightPurple": "#AD7FA8",             "brightRed": "#EF2929",             "brightWhite": "#EEEEEC",             "brightYellow": "#FCE94F",             "cursorColor": "#000000",             "cyan": "#06989A",             "foreground": "#555753",             "green": "#4E9A06",             "name": "Tango Light",             "purple": "#75507B",             "red": "#CC0000",             "selectionBackground": "#FFFFFF",             "white": "#D3D7CF",             "yellow": "#C4A000"         },         {             "background": "#000000",             "black": "#000000",             "blue": "#000080",             "brightBlack": "#808080",             "brightBlue": "#0000FF",             "brightCyan": "#00FFFF",             "brightGreen": "#00FF00",             "brightPurple": "#FF00FF",             "brightRed": "#FF0000",             "brightWhite": "#FFFFFF",             "brightYellow": "#FFFF00",             "cursorColor": "#FFFFFF",             "cyan": "#008080",             "foreground": "#C0C0C0",             "green": "#008000",             "name": "Vintage",             "purple": "#800080",             "red": "#800000",             "selectionBackground": "#FFFFFF",             "white": "#C0C0C0",             "yellow": "#808000"         }     ],     "showTabsInTitlebar": true,     "showTerminalTitleInTitlebar": false,     "startOnUserLogin": true,     "tabSwitcherMode": "disabled",     "tabWidthMode": "equal",     "theme": "light" }

@zadjii-msft  last question: When I open a WT window with cmd.exe or powershell, then run a command like ng or npx I notice the tab title changes to that command. So are commands being logged in some history table I can access?


text:
Another exception on close, maybe not a crash?

This one seems to hit 100% for me in Debug builds, currently on 1167e20 but I'd bet this is in main.
Repro:

Open a debug Terminal in vs
Persist layouts is off, not sure it matters.
close the window with the 'x'
experience crash

Likely regressed in #11440, this line: https://github.com/microsoft/terminal/pull/11440/files#diff-d9af234d6dd21db9240dc3733d69471898a79f1c4386cb3c48ac45ab7158cd07R405
AppHost::LastTabClosed RESETS the _getWindowLayoutThrottler, then calls SignalClose(). That goes up and back down to the _windowManager.WindowClosed handler set up in AppHost::_BecomeMonarch. At this point, _getWindowLayoutThrottler DOESN'T HAVE A VALUE, so
_getWindowLayoutThrottler.value()()

causes a std::bad_optional_access exception.
I don't know if this is a crash, or just a first-chance exception that VS is reporting that doesn't matter. It's definitely a bug though.

Stack
 	WindowsTerminal.exe!<lambda_d14224e5f61d340d2454360bff63413e>::operator()<winrt::Windows::Foundation::IInspectable const &,winrt::Windows::Foundation::IInspectable const &>(const winrt::Windows::Foundation::IInspectable & __formal, const winrt::Windows::Foundation::IInspectable & __formal) Line 818	C++
 	WindowsTerminal.exe!winrt::impl::delegate<winrt::Windows::Foundation::TypedEventHandler<winrt::Windows::Foundation::IInspectable,winrt::Windows::Foundation::IInspectable>,<lambda_d14224e5f61d340d2454360bff63413e>>::Invoke(void * sender, void * args) Line 895	C++
 	Microsoft.Terminal.Remoting.dll!winrt::Windows::Foundation::TypedEventHandler<winrt::Windows::Foundation::IInspectable,winrt::Windows::Foundation::IInspectable>::operator()(const winrt::Windows::Foundation::IInspectable & sender, const winrt::Windows::Foundation::IInspectable & args) Line 2525	C++
 	Microsoft.Terminal.Remoting.dll!winrt::impl::invoke<winrt::Windows::Foundation::TypedEventHandler<winrt::Windows::Foundation::IInspectable,winrt::Windows::Foundation::IInspectable>,winrt::Windows::Foundation::IInspectable,winrt::Windows::Foundation::IInspectable>(const winrt::Windows::Foundation::TypedEventHandler<winrt::Windows::Foundation::IInspectable,winrt::Windows::Foundation::IInspectable> & delegate, const winrt::Windows::Foundation::IInspectable & <args_0>, const winrt::Windows::Foundation::IInspectable & <args_1>) Line 5762	C++
 	Microsoft.Terminal.Remoting.dll!winrt::event<winrt::Windows::Foundation::TypedEventHandler<winrt::Windows::Foundation::IInspectable,winrt::Windows::Foundation::IInspectable>>::operator()<winrt::Windows::Foundation::IInspectable,winrt::Windows::Foundation::IInspectable>(const winrt::Windows::Foundation::IInspectable & <args_0>, const winrt::Windows::Foundation::IInspectable & <args_1>) Line 5897	C++
 	Microsoft.Terminal.Remoting.dll!<lambda_feabb5633168b9dfc8d0e9799de5ebe0>::operator()<winrt::Windows::Foundation::IInspectable const &,winrt::Windows::Foundation::IInspectable const &>(const winrt::Windows::Foundation::IInspectable & <args_0>, const winrt::Windows::Foundation::IInspectable & <args_1>) Line 2520	C++
 	Microsoft.Terminal.Remoting.dll!winrt::impl::delegate<winrt::Windows::Foundation::TypedEventHandler<winrt::Windows::Foundation::IInspectable,winrt::Windows::Foundation::IInspectable>,<lambda_feabb5633168b9dfc8d0e9799de5ebe0>>::Invoke(void * sender, void * args) Line 895	C++
 	Microsoft.Terminal.Remoting.dll!winrt::Windows::Foundation::TypedEventHandler<winrt::Windows::Foundation::IInspectable,winrt::Windows::Foundation::IInspectable>::operator()(const winrt::Windows::Foundation::IInspectable & sender, const winrt::Windows::Foundation::IInspectable & args) Line 2525	C++
 	Microsoft.Terminal.Remoting.dll!winrt::impl::invoke<winrt::Windows::Foundation::TypedEventHandler<winrt::Windows::Foundation::IInspectable,winrt::Windows::Foundation::IInspectable>,std::nullptr_t,std::nullptr_t>(const winrt::Windows::Foundation::TypedEventHandler<winrt::Windows::Foundation::IInspectable,winrt::Windows::Foundation::IInspectable> & delegate, void * const & <args_0>, void * const & <args_1>) Line 5762	C++
 	Microsoft.Terminal.Remoting.dll!winrt::event<winrt::Windows::Foundation::TypedEventHandler<winrt::Windows::Foundation::IInspectable,winrt::Windows::Foundation::IInspectable>>::operator()<std::nullptr_t,std::nullptr_t>(void * const & <args_0>, void * const & <args_1>) Line 5897	C++
 	Microsoft.Terminal.Remoting.dll!winrt::Microsoft::Terminal::Remoting::implementation::Monarch::SignalClose(const unsigned __int64 peasantId) Line 212	C++
 	Microsoft.Terminal.Remoting.dll!winrt::impl::produce<winrt::Microsoft::Terminal::Remoting::implementation::Monarch,winrt::Microsoft::Terminal::Remoting::IMonarch>::SignalClose(unsigned __int64 peasantId) Line 999	C++
 	Microsoft.Terminal.Remoting.dll!winrt::impl::consume_Microsoft_Terminal_Remoting_IMonarch<winrt::Microsoft::Terminal::Remoting::IMonarch>::SignalClose(unsigned __int64 peasantId) Line 117	C++
 	Microsoft.Terminal.Remoting.dll!winrt::Microsoft::Terminal::Remoting::implementation::WindowManager::SignalClose() Line 74	C++
 	Microsoft.Terminal.Remoting.dll!winrt::impl::produce<winrt::Microsoft::Terminal::Remoting::implementation::WindowManager,winrt::Microsoft::Terminal::Remoting::IWindowManager>::SignalClose() Line 1710	C++
 	WindowsTerminal.exe!winrt::impl::consume_Microsoft_Terminal_Remoting_IWindowManager<winrt::Microsoft::Terminal::Remoting::IWindowManager>::SignalClose() Line 655	C++
>	WindowsTerminal.exe!AppHost::LastTabClosed(const winrt::Windows::Foundation::IInspectable & __formal, const winrt::TerminalApp::LastTabClosedEventArgs & __formal) Line 412	C++
 	WindowsTerminal.exe!<lambda_3930e0e5f7a1efe801e738623725cca1>::operator()<winrt::Windows::Foundation::IInspectable const &,winrt::TerminalApp::LastTabClosedEventArgs const &>(const winrt::Windows::Foundation::IInspectable & <args_0>, const winrt::TerminalApp::LastTabClosedEventArgs & <args_1>) Line 2512	C++
 	WindowsTerminal.exe!winrt::impl::delegate<winrt::Windows::Foundation::TypedEventHandler<winrt::Windows::Foundation::IInspectable,winrt::TerminalApp::LastTabClosedEventArgs>,<lambda_3930e0e5f7a1efe801e738623725cca1>>::Invoke(void * sender, void * args) Line 895	C++
 	TerminalApp.dll!winrt::Windows::Foundation::TypedEventHandler<winrt::Windows::Foundation::IInspectable,winrt::TerminalApp::LastTabClosedEventArgs>::operator()(const winrt::Windows::Foundation::IInspectable & sender, const winrt::TerminalApp::LastTabClosedEventArgs & args) Line 2525	C++
 	TerminalApp.dll!winrt::impl::invoke<winrt::Windows::Foundation::TypedEventHandler<winrt::Windows::Foundation::IInspectable,winrt::TerminalApp::LastTabClosedEventArgs>,winrt::TerminalApp::implementation::TerminalPage,std::nullptr_t>(const winrt::Windows::Foundation::TypedEventHandler<winrt::Windows::Foundation::IInspectable,winrt::TerminalApp::LastTabClosedEventArgs> & delegate, const winrt::TerminalApp::implementation::TerminalPage & <args_0>, void * const & <args_1>) Line 5762	C++
 	TerminalApp.dll!winrt::event<winrt::Windows::Foundation::TypedEventHandler<winrt::Windows::Foundation::IInspectable,winrt::TerminalApp::LastTabClosedEventArgs>>::operator()<winrt::TerminalApp::implementation::TerminalPage,std::nullptr_t>(const winrt::TerminalApp::implementation::TerminalPage & <args_0>, void * const & <args_1>) Line 5897	C++
 	TerminalApp.dll!winrt::TerminalApp::implementation::TerminalPage::_RemoveTab(const winrt::TerminalApp::TabBase & tab) Line 528	C++
 	TerminalApp.dll!winrt::TerminalApp::implementation::TerminalPage::_HandleCloseTabRequested$_ResumeCoro$1() Line 478	C++
 	[External Code]
 	TerminalApp.dll!winrt::TerminalApp::implementation::TerminalPage::_RemoveTabs$_ResumeCoro$1() Line 814	C++
 	[External Code]
 	TerminalApp.dll!winrt::TerminalApp::implementation::TerminalPage::_RemoveAllTabs() Line 1053	C++
 	TerminalApp.dll!winrt::TerminalApp::implementation::TerminalPage::CloseWindow$_ResumeCoro$1() Line 1406	C++
 	[External Code]
 	TerminalApp.dll!winrt::TerminalApp::implementation::AppLogic::CloseWindow(winrt::Microsoft::Terminal::Settings::Model::LaunchPosition pos) Line 1178	C++
 	TerminalApp.dll!winrt::impl::produce<winrt::TerminalApp::implementation::AppLogic,winrt::TerminalApp::IAppLogic>::CloseWindow(winrt::impl::struct_Microsoft_Terminal_Settings_Model_LaunchPosition position) Line 2764	C++
 	WindowsTerminal.exe!winrt::impl::consume_TerminalApp_IAppLogic<winrt::TerminalApp::IAppLogic>::CloseWindow(const winrt::Microsoft::Terminal::Settings::Model::LaunchPosition & position) Line 245	C++
 	WindowsTerminal.exe!AppHost::Initialize::__l2::<lambda>() Line 310	C++
 	WindowsTerminal.exe!winrt::impl::variadic_delegate<void <lambda>(void),void>::invoke() Line 5316	C++
 	WindowsTerminal.exe!winrt::impl::delegate_base<void>::operator()() Line 5385	C++
 	WindowsTerminal.exe!winrt::impl::invoke<winrt::delegate<>>(const winrt::delegate<> & delegate) Line 5762	C++
 	WindowsTerminal.exe!winrt::event<winrt::delegate<>>::operator()<>() Line 5897	C++
 	WindowsTerminal.exe!IslandWindow::MessageHandler(const unsigned int message, const unsigned __int64 wparam, const __int64 lparam) Line 493	C++
 	WindowsTerminal.exe!NonClientIslandWindow::MessageHandler(const unsigned int message, const unsigned __int64 wParam, const __int64 lParam) Line 910	C++
 	WindowsTerminal.exe!BaseWindow<IslandWindow>::WndProc(HWND__ * const window, const unsigned int message, const unsigned __int64 wparam, const __int64 lparam) Line 35	C++
 	[External Code]
 	WindowsTerminal.exe!BaseWindow<IslandWindow>::MessageHandler(const unsigned int message, const unsigned __int64 wparam, const __int64 lparam) Line 97	C++
 	WindowsTerminal.exe!IslandWindow::MessageHandler(const unsigned int message, const unsigned __int64 wparam, const __int64 lparam) Line 625	C++
 	WindowsTerminal.exe!NonClientIslandWindow::MessageHandler(const unsigned int message, const unsigned __int64 wParam, const __int64 lParam) Line 910	C++
 	WindowsTerminal.exe!BaseWindow<IslandWindow>::WndProc(HWND__ * const window, const unsigned int message, const unsigned __int64 wparam, const __int64 lparam) Line 35	C++
 	[External Code]
 	WindowsTerminal.exe!wWinMain(HINSTANCE__ * __formal, HINSTANCE__ * __formal, wchar_t * __formal, int __formal) Line 198	C++
 	[External Code]

There is a CATCH_LOG() at the bottom of WindowManager::SignalClose - still tho, seems like something we could clean up.

Yup, that makes sense and is definitely something I overlooked or didn't notice because of catching the exception, and the fact that I made it so calling quit didn't call the WindowClosed handlers.
I don't really have time to work on anything here for the next couple of weeks, but it can be solved in a number of ways

just checking if the value is set before calling it
removing the WindowClosed/WindowOpened handlers like the GetWindowLayout handler is removed here: https://github.com/microsoft/terminal/blob/main/src/cascadia/WindowsTerminal/AppHost.cpp#L406
???
ripping up the whole things and starting over

Probably should also give some thought to the placement of SignalClose itself. Originally it was just called when the WindowManager ran its destructor, but of course in the linked PR I added it earlier in the closing process and so some of the assumptions have been broken.

authors: Rosefield zadjii-msft


text:
Strange hint when using Simplified Chinese (American keyboard) input method

Windows Terminal version
1.11.2921.0
Windows build number
10.0.19043.1348
Other Software
I'm using 搜狗拼音输入法 Sogou Pinyin ver 10.1.0.4428 ,

along with Simplified Chinese (American keyboard) (Added using Sogou Pinyin)

and English (American keyboard)

Steps to reproduce

When I try to input with Chinese Simplified (American keyboard), there will be a hint before actually input into the terminal, I need to  press enter twice to input into the terminal (like inputing with Sogou Pinyin Chinese mode).

While switch to other terminals like PowerShell, there will not be a hint.
Expected Behavior
When using Chinese (American keyboard), behave like PowerShell.
Actual Behavior
There is a hint.

@skyline75489 This isn't the same as #1304, is it?

@skyline75489 This isn't the same as #1304, is it?

Yes, they are saying the same thing.
Sorry for not found an existing issue.

No worries, that's a tricky one to find. I only found it because I was confident that I had seen the sogou pinyin icon somewhere else on the repo before 😅
/dup #1304

authors: DevDengChao zadjii-msft


text:
Unable to pass command line parameters after the double dash in Windows Terminal

Windows Terminal version
1.21.2911.0
Windows build number
10.0.19045.2604
Other Software
Node: v20.16.0
NPM: 10.8.1
Steps to reproduce
Here is the command I want to run on Windows Terminal:
pm2 start C:\Users\User\AppData\Roaming\npm\node_modules\http-server\bin\http-server --name http-server-app -- --port 3000

If I run it in the Windows Terminal, I will get this error:

error: unknown option `--port'.

The same error will appear in the Powershell. But it will succeed in the Command Line.
Is there a way to solve this problem?
Expected Behavior
The port number parameter can be passed to the command line successfully.
Actual Behavior
error: unknown option `--port'.

When you say “in Windows Terminal,” is there a chance you mean “in PowerShell”?
Terminal supports running different shells, like PowerShell and Command Prompt.
If you are seeing a difference in argument handling, there is a chance you are not using the shell you are expecting.

Is there a way to solve this problem?

You can run Command Prompt inside Windows Terminal. Please consult the dropdown menu for either a one-off option to run Command Prompt or a permanent option to configure your “Default Profile”.

@hh54188 try using quotes or escape the double hyphen.
Sample output:
PS C:\Users\WDAGUtilityAccount> pm2 start C:\Users\User\AppData\Roaming\npm\node_modules\http-server\bin\http-server --name http-server-app '--' --port 3000
[PM2][ERROR] Script not found: C:\Users\User\AppData\Roaming\npm\node_modules\http-server\bin\http-server
PS C:\Users\WDAGUtilityAccount> pm2 start .\AppData\Roaming\npm\node_modules\http-server\bin\http-server --name http-ser
ver-app -- --port 3000

  error: unknown option `--port'

PS C:\Users\WDAGUtilityAccount> pm2 start .\AppData\Roaming\npm\node_modules\http-server\bin\http-server --name http-server-app `-- --port 3000
[PM2] Starting C:\Users\WDAGUtilityAccount\AppData\Roaming\npm\node_modules\http-server\bin\http-server in fork_mode (1 instance)
[PM2] Done.
┌────┬────────────────────┬──────────┬──────┬───────────┬──────────┬──────────┐
│ id │ name               │ mode     │ ↺    │ status    │ cpu      │ memory   │
├────┼────────────────────┼──────────┼──────┼───────────┼──────────┼──────────┤
│ 0  │ http-server-app    │ fork     │ 0    │ online    │ 0%       │ 45.6mb   │
└────┴────────────────────┴──────────┴──────┴───────────┴──────────┴──────────┘

authors: DHowett elsaco hh54188


text:
Can't scroll or drag files over some areas with non 100% scaling

Environment
Windows build number: 10.0.18362.0
Windows Terminal version (if applicable): built from master @ f4294b1

Any other software? N/A

Steps to reproduce

Turn off the Windows setting scroll inactive window when I hover over them
Have terminal on monitor with scaling other than 100%
Have enough text to scroll
Focus terminal and scroll with mouse wheel

Expected behavior
Terminal should scroll
Actual behavior
Scrolling behavior is different depending on the mouse position. In some areas, it scrolls properly. In other regions, scrolling won't work.

If scaling is 100%, then scrolling works properly. If scroll inactive window setting is on, then scrolling works properly.
Same issue for both normal and non client window

Heres what I think is happening:
With scroll inactive window off, the wm_mousewheel messages are only be sent to current focused window (If i've read the docs correctly).
I think that the window that takes focus is not scaled properly so in some areas the mouse is 'outside' and won't receive the mouse wheel messages (maybe it needs to be focused and hovered?).
Terminal does have a couple windows (the host and the xaml island ones) but i'm not sure which one takes focus when terminal is active. I tried checking for wm_mousewheel in the window procs but I could not see the message being sent.
I have my suspicions that it's the top level window that is supposed to be receiving the messages because using Spy++, when I highlighted the top level window, its size also matched the area where scrolling works. But visually, everything seems to be scaled properly so I'm not too sure now.

@austin-lamb & @ocalvo might be interested in this

I just want to say we all really appreciate how robust this bug report is and how well you've investigated it.
Thanks!

Oh no, this is likely a platform bug. We've got a discussion with some folks on the XAML team to help investigate this, but I think this isn't going to make the 1.0 cut.
This issue is now tracking the internal bugs MSFT:25518888 and MSFT:23625486

Also adding MSFT:35026617 to the list of internal tracking issues, since 23625486 was resolved, but didn't fix this.

Alrighty so MSFT:35026617 was fixed earlier this year, but unfortunately doesn't make the cut to service back to Windows 10. Alas 🤷. Anyways, this is fixed on the latest Windows 11 builds, so I'm gonna close this out, since there's nothing else for us to do here. Thanks!

Still not working.
https://github.com/microsoft/terminal/assets/104540921/6dd0b1e4-2d9e-4c1e-83fd-6e5d91e9e604

authors: DHowett-MSFT dsafa malcolm-bell zadjii-msft


text:
Cannot run WindowsTerminal.exe as other user from the Windows Store version

Environment
Windows build number: 10.0.18362.387
Windows Terminal version (if applicable): 0.6.2951.0

Any other software?

Steps to reproduce
When I try to either engage "runas" on C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe or shift right click and "run as another user" on WindowsTerminal.exe, it gives me an error.
Can this be fixed? Or alternately, can a feature be built into Windows Terminal where you can relaunch as a different user?

Expected behavior
App launches as the user I specify

Actual behavior
The application will either a) reject my perfectly valid credentials (which work in other prompts), or b) give me an access denied error.
Runas:
Attempting to start C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe as user "domainname\otherusername" ...
RUNAS ERROR: Unable to run - C:\Program Files\WindowsApps\Microsoft.WindowsTerminal_0.6.2951.0_x64__8wekyb3d8bbwe\WindowsTerminal.exe
5: Access is denied.
"Run as other user" GUI:
"Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item."
Unsure if this same issue happens on the non-Store version.

Thanks for the report. This looks like a /dupe of #1032.

Thanks for the report. This looks like a /dupe of #1032.

I would argue this is not a dupe of #1032 as #1032 does not imply that the user account requesting the elevated window/tab is different than the admin user account. In my case, I have two accounts on my system. One account is my daily driver which is a standard user, the other is my admin account. With the current setup I am unable to elevate a tab or window in the terminal app, and need to revert to using powershell or cmd directly, which defeats the purpose of terminal.

Thanks for the report. This looks like a /dupe of #1032.

I would argue this is not a dupe of #1032 as #1032 does not imply that the user account requesting the elevated window/tab is different than the admin user account. In my case, I have two accounts on my system. One account is my daily driver which is a standard user, the other is my admin account. With the current setup I am unable to elevate a tab or window in the terminal app, and need to revert to using powershell or cmd directly, which defeats the purpose of terminal.

I use the same scenario, two accounts on the same machine, one of them admin. Elevation works as long as the same profiles have the same version of Windows Terminal.

authors: DHowett-MSFT dejandjuranovic jflattery yllekz


text:
Hush a garrulous event from TerminalControl

Fixes MSFT-36708760

@msftbot merge this in 1 minute


text:
Add generic documentation for TerminalInput::_initKeyboardMap() function of t…

…erminalInput.cpp file
Summary of the Pull Request
Add generic documentation about TerminalInput function, specially _initKeyboardMap(),
for greater code clarity
References and Relevant Issues
Detailed Description of the Pull Request / Additional comments
Validation Steps Performed
PR Checklist

[ ] Closes #xxx
[ ] Tests added/passed
[ ] Documentation updated

If checked, please file a pull request on our docs repo and link it here: #xxx

[ ] Schema updated (if necessary)

Thank you for the feedback!


text:
Info display for arity one or more is broken

Describe the bug
When using arity OneOrMore, the arity displayed when doing --info is 1..2147483647 and not 1..N or 1..*.
Steps To Reproduce
Look at --test-parameter in MSTest.
Additional context
See PR #3106

Let's use N for the display to be matching the doc https://learn.microsoft.com/dotnet/standard/commandline/syntax#argument-arity

repo: microsoft/testfx


text:
Move IsTestingPlatformApplication from .props to .targets

Leave a chance to user to override EnableMSTestRunner property before we evaluate it for the IsTestingPlatformApplication property.

This is not possible.


text:
KfRaiseIrql usersim API doesn't accurately match kernel mode

In kernel mode, this is a relatively light weight API. The usersim version is very heavy and causes tests to timeout due to cost.

Nit with title: the performance might not match, but the performance is poor partly because it tries very hard to match the observable functional behavior of kernel mode. Do you know what the bottleneck is?

Looks like SetThreadPriority and SetThreadGroupAffinity are super slow. I will try profiling to narrow down why.

Correct. The test case that breaks is running BPF programs at passive level, which requires raising and lowering IRQL on every epoch enter / exit.

For context, I added a considerable amount of overhead in PR https://github.com/microsoft/usersim/pull/53. Previously this routine was somewhat lighter weight, but also allowed a variety of observable misbehavior, including passive threads and other DPCs preempting dispatch level code on the same processor.
Perhaps we could relax some of those constraints if the tests do not depend on dispatch level code being properly serialized WRT each other and/or WRT passive threads.

authors: Alan-Jowett mtfriesen

repo: microsoft/usersim


text:
vcxproj file won't load on xbox

In #82, Nick writes regarding cxplat/src/cxplat_winkernel/cxplat_winkernel.vcxproj:

We can do this in a follow up PR, but this project file needs some work. It won't load on xbox for instance.

@nibanks can you provide more details on what the problems are?

See these compiler options and these linker options as examples of things we learned the hard way that XBOX requires, or fails to load.

authors: dthaler nibanks


text:
[hunspell] build failure within VS 2019 prompt

Host Environment

OS: Windows 10.0.18363.720
Compiler: VS 2019

To Reproduce
Steps to reproduce the behavior:
./vcpkg install hunspell --triplet x64-windows
Failure logs
Computing installation plan...
The following packages will be built and installed:
    hunspell[core]:x64-windows
Starting package 1/1: hunspell:x64-windows
Building package hunspell[core]:x64-windows...
-- Using cached C:/Users/wangqr/Files/src/vcpkg/downloads/hunspell-hunspell-v1.7.0.tar.gz
-- Extracting source C:/Users/wangqr/Files/src/vcpkg/downloads/hunspell-hunspell-v1.7.0.tar.gz
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
    Command failed: "C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/bin/cmake.exe" -E tar xjf C:/Users/wangqr/Files/src/vcpkg/downloads/hunspell-hunspell-v1.7.0.tar.gz
    Working Directory: C:/Users/wangqr/Files/src/vcpkg/buildtrees/hunspell/src/TEMP
    Error code: 1
    See logs for more information:
      C:\Users\wangqr\Files\src\vcpkg\buildtrees\hunspell\extract-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_extract_source_archive.cmake:43 (vcpkg_execute_required_process)
  scripts/cmake/vcpkg_extract_source_archive_ex.cmake:108 (vcpkg_extract_source_archive)
  scripts/cmake/vcpkg_from_github.cmake:139 (vcpkg_extract_source_archive_ex)
  ports/hunspell/portfile.cmake:3 (vcpkg_from_github)
  scripts/ports.cmake:90 (include)

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

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

C:\Users\wangqr\Files\src\vcpkg\buildtrees\hunspell\extract-err.log

CMake Error: Problem with archive_write_header(): Can't create ''
CMake Error: Current file: hunspell-1.7.0/README
CMake Error: Problem extracting tar: C:/Users/wangqr/Files/src/vcpkg/downloads/hunspell-hunspell-v1.7.0.tar.gz

Additional context
7-zip can open and extract hunspell-hunspell-v1.7.0.tar.gz without issue.

Clean everything and try again

I have fresh cloned vcpkg from a5a244f5bdc390fc1c3d42e126e0bfd80541f060 and the issue is the same.
Full stdout at https://paste.ubuntu.com/p/xHnKgYZxCX/

Did you use **VS2019 command prompt ** or just ordinary Windows Command Prompt to run vcpkg install hunspell?

I was using VS2019 command prompt (x64 native). Just tried ordinary Windows Command Prompt and it does work fine. Is this expected?

When you use VS2019 command prompt, CMake that comes with Visual Studio will be used because cmake is in %PATH%.
When ordinary Windows Command Prompt is used, CMake that downloaded by vcpkg will be used. This is always the version that works correctly.

MSVC 16.5.0 ships CMake 3.16.
vcpkg downloads CMake 3.14.
CMake 3.16 is known to breaks some packages, so in the mean time, use CMake 3.14.

When running in cmd, it actually uses the CMake that I installed. I've logged out ${CMAKE_COMMAND}, and it is C:/Program Files/CMake/bin/cmake.exe. The version of that CMake is 3.17.0.

Also problematic with cmake 3.17. Could you try to temporarily, either

move your C:/Program Files/CMake/bin/cmake.exe to somewhere else; or
modify %PATH% to remove C:\Program Files\CMake\bin``%PATH%

so that it does not find cmake in %PATH%

No, I mean it is working normally with CMake 3.17

@wangqr Dose this issue still occur when using a PowerShell window to install hunspell:x64-windows?

But your log says cmake is in program files

Output of vcpkg.exe install hunspell:x64-windows --debug: https://paste.ubuntu.com/p/FW8yzHSw5b/
If I run it from plain PowerShell, it success: https://paste.ubuntu.com/p/yYj4bvyFch/
If I start PowerShell from VS 2019 prompt, it fails: https://paste.ubuntu.com/p/jxQzM4ytNp/

But your log says cmake is in program files

The log says failed command is C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/bin/cmake.exe so I think it is the one provided by VS. And VS is installed in program files.

@wangqr What's the version of the C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/bin/cmake.exe?

C:\Program Files (x86)\Microsoft Visual Studio\2019\Community>"C:/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/IDE/CommonExtensions/Microsoft/CMake/CMake/bin/cmake.exe" --version
cmake version 3.16.19112601-MSVC_2

CMake suite maintained and supported by Kitware (kitware.com/cmake).

This is a cmake bug, and I think it has been fixed in 3.17.0, because your issue disappeared with your C:\Program Files\CMake\bin\cmake.exe (cmake version 3.17.0)

In that case, can VS upgrade the bundled CMake?

I think you could send a feedback to Visual Studio. Please refer to this: https://developercommunity.visualstudio.com/content/problem/post.html?space=8

https://developercommunity.visualstudio.com/content/problem/964144/cmake-bundled-in-vs1029-breaks-vcpkg-problem-with.html

Thank you!

authors: Cheney-W linquize wangqr

repo: microsoft/vcpkg


text:
[tensorflow:x64-windows] build failure

Host Environment

OS: Windows Version 10.0.19043.1055
Compiler: Visual Studio 2019 Community

To Reproduce
>vcpkg install tensorflow:x64-windows

Failure logs
Starting package 1/1: tensorflow:x64-windows
Building package tensorflow[core]:x64-windows...
[DEBUG] CreateProcessW("C:\vcpkg\downloads\tools\cmake-3.20.2-windows\cmake-3.20.2-windows-i386\bin\cmake.exe" -DALL_FEATURES= -DCURRENT_PORT_DIR=C:/vcpkg/ports/tensorflow -D_HOST_TRIPLET=x64-windows -DFEATURES=core -DPORT=tensorflow -DVCPKG_USE_HEAD_VERSION=0 -D_VCPKG_DOWNLOAD_TOOL=BUILT_IN -D_VCPKG_EDITABLE=0 -D_VCPKG_NO_DOWNLOADS=0 -DCMD=BUILD -DDOWNLOADS=C:/vcpkg/downloads -DTARGET_TRIPLET=x64-windows "-DTARGET_TRIPLET_FILE=C:\vcpkg\triplets\x64-windows.cmake" -DVCPKG_BASE_VERSION=2021-05-05 -DVCPKG_CONCURRENCY=13 -DVCPKG_PLATFORM_TOOLSET=v142 -DGIT=c:/code/depot_tools/git.bat -DVCPKG_ROOT_DIR=C:/vcpkg -DPACKAGES_DIR=C:/vcpkg/packages -DBUILDTREES_DIR=C:/vcpkg/buildtrees -D_VCPKG_INSTALLED_DIR=C:/vcpkg/installed -DDOWNLOADS=C:/vcpkg/downloads -DVCPKG_MANIFEST_INSTALL=OFF -P "C:\vcpkg\scripts\ports.cmake")
-- Using msys root at C:/vcpkg/downloads/tools/msys2/b3b3d399e80e310e
-- Using C:/vcpkg/downloads/tensorflow-tensorflow-v2.4.1.tar.gz
-- Extracting source C:/vcpkg/downloads/tensorflow-tensorflow-v2.4.1.tar.gz
-- Applying patch C:/vcpkg/installed/x64-windows/share/tensorflow-common/fix-build-error.patch
-- Applying patch C:/vcpkg/installed/x64-windows/share/tensorflow-common/fix-windows-build.patch
-- Using source at C:/vcpkg/buildtrees/tensorflow/src/v2.4.1-81b5bb6ede.clean
-- Configuring TensorFlow (dbg)
-- Warning: Building TensorFlow can take an hour or more.
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:146 (message):
    Command failed: C:/vcpkg/downloads/tools/msys2/b3b3d399e80e310e/usr/bin/bash.exe --noprofile --norc -c "'C:/vcpkg/downloads/tools/bazel/3.7.0-windows/bazel.exe' --output_user_root='C:/vcpkg/buildtrees/tensorflow/.bzl' build --verbose_failures --compilation_mode=dbg --features=fastbuild    --python_path='C:/vcpkg/downloads/tools/msys2/b3b3d399e80e310e/mingw64/bin/python3.exe' --define=no_tensorflow_py_deps=true ///tensorflow:tensorflow.dll ///tensorflow:install_headers"
    Working Directory: C:/vcpkg/buildtrees/tensorflow/x64-windows-dbg
    See logs for more information:
      C:\vcpkg\buildtrees\tensorflow\build-x64-windows-dbg-err.log

Call Stack (most recent call first):
  installed/x64-windows/share/tensorflow-common/tensorflow-common.cmake:230 (vcpkg_execute_build_process)
  ports/tensorflow/portfile.cmake:7 (include)
  scripts/ports.cmake:139 (include)

[DEBUG] cmd_execute_and_stream_data() returned 1 after 27515884 us
Error: Building package tensorflow:x64-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with `.\vcpkg update`, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
  Package: tensorflow:x64-windows
  Vcpkg version: 2021-05-05-9f849c4c43e50d1b16186ae76681c27b0c1be9d9

Additionally, attach any relevant sections from the log files above.
[DEBUG] C:\A\1\121\s\src\vcpkg\install.cpp(511)
[DEBUG] Exiting after 31109065 us (31108257 us)

----------------
[\vcpkg\buildtrees\tensorflow\build-x64-windows-dbg-err.log]
...
ERROR: no such package '@io_bazel_rules_go//go': error running 'git init C:/vcpkg/buildtrees/tensorflow/.bzl/yvfmeljr/external/io_bazel_rules_go' while working with @io_bazel_rules_go:
java.io.IOException: ERROR: src/main/native/windows/process.cc(202): CreateProcessW("git" init C:/vcpkg/buildtrees/tensorflow/.bzl/yvfmeljr/external/io_bazel_rules_go): The system cannot find the file specified.
 (error: 2)
...

build-x64-windows-dbg-err.log

ERROR: An error occurred during the fetch of repository 'io_bazel_rules_go':
   Traceback (most recent call last):
	File "C:/vcpkg/buildtrees/tensorflow/.bzl/yvfmeljr/external/bazel_tools/tools/build_defs/repo/git.bzl", line 181, column 30, in _git_repository_implementation
		update = _clone_or_update(ctx)
	File "C:/vcpkg/buildtrees/tensorflow/.bzl/yvfmeljr/external/bazel_tools/tools/build_defs/repo/git.bzl", line 36, column 20, in _clone_or_update
		git_ = git_repo(ctx, directory)
	File "C:/vcpkg/buildtrees/tensorflow/.bzl/yvfmeljr/external/bazel_tools/tools/build_defs/repo/git_worker.bzl", line 91, column 12, in git_repo
		_update(ctx, git_repo)
	File "C:/vcpkg/buildtrees/tensorflow/.bzl/yvfmeljr/external/bazel_tools/tools/build_defs/repo/git_worker.bzl", line 101, column 9, in _update
		init(ctx, git_repo)
	File "C:/vcpkg/buildtrees/tensorflow/.bzl/yvfmeljr/external/bazel_tools/tools/build_defs/repo/git_worker.bzl", line 118, column 15, in init
		_error(ctx.name, cl, st.stderr)
	File "C:/vcpkg/buildtrees/tensorflow/.bzl/yvfmeljr/external/bazel_tools/tools/build_defs/repo/git_worker.bzl", line 190, column 9, in _error
		fail("error running '%s' while working with @%s:\n%s" % (command_text, name, stderr))
Error in fail: error running 'git init C:/vcpkg/buildtrees/tensorflow/.bzl/yvfmeljr/external/io_bazel_rules_go' while working with @io_bazel_rules_go:
java.io.IOException: ERROR: src/main/native/windows/process.cc(202): CreateProcessW("git" init C:/vcpkg/buildtrees/tensorflow/.bzl/yvfmeljr/external/io_bazel_rules_go): The system cannot find the file specified.
 (error: 2)

Same results when cloned to D:
D:\>"C:\Program Files\Git\cmd\git.exe" clone https://github.com/microsoft/vcpkg.git
Cloning into 'vcpkg'...
...
D:\>cd vcpkg

D:\vcpkg>bootstrap-vcpkg.bat
Downloading https://github.com/microsoft/vcpkg-tool/releases/download/2021-05-05-9f849c4c43e50d1b16186ae76681c27b0c1be9d9/vcpkg.exe -> D:\vcpkg\vcpkg.exe
Done.

D:\vcpkg>vcpkg install tensorflow
...
CMake Error at scripts/cmake/vcpkg_execute_build_process.cmake:146 (message):
    Command failed: D:/vcpkg/downloads/tools/msys2/b3b3d399e80e310e/usr/bin/bash.exe --noprofile --norc -c "'D:/vcpkg/downloads/tools/bazel/3.7.0-windows/bazel.exe' --output_user_root='D:/vcpkg/buildtrees/tensorflow/.bzl' build --verbose_failures --compilation_mode=dbg --features=fastbuild    --python_path='D:/vcpkg/downloads/tools/msys2/b3b3d399e80e310e/mingw64/bin/python3.exe' --define=no_tensorflow_py_deps=true ///tensorflow:tensorflow.dll ///tensorflow:install_headers"
    Working Directory: D:/vcpkg/buildtrees/tensorflow/x64-windows-dbg
    See logs for more information:
      D:\vcpkg\buildtrees\tensorflow\build-x64-windows-dbg-err.log

Call Stack (most recent call first):
  installed/x64-windows/share/tensorflow-common/tensorflow-common.cmake:230 (vcpkg_execute_build_process)
  ports/tensorflow/portfile.cmake:7 (include)
  scripts/ports.cmake:139 (include)

build-x64-windows-dbg-err.log
Possibly of note:  Immediately after build failure, if I try to remove the buildtrees directory I get in use/permission errors:
D:\vcpkg>rd /s buildtrees
buildtrees, Are you sure (Y/N)? y
buildtrees\tensorflow\.bzl\57u5iwxm\java.log.monster.Josh.log.java.20210617-225547.3524 - The process cannot access the file because it is being used by another process.
buildtrees\tensorflow\.bzl\57u5iwxm\server\jvm.out - The process cannot access the file because it is being used by another process.
buildtrees\tensorflow\.bzl\install\3d1356cc22901f271d47ddd780d95b50\A-server.jar - The process cannot access the file because it is being used by another process.
buildtrees\tensorflow\.bzl\install\3d1356cc22901f271d47ddd780d95b50\cpu_profiler.dll - Access is denied.
buildtrees\tensorflow\.bzl\install\3d1356cc22901f271d47ddd780d95b50\embedded_tools\jdk\bin\java.dll - Access is denied.
buildtrees\tensorflow\.bzl\install\3d1356cc22901f271d47ddd780d95b50\embedded_tools\jdk\bin\java.exe - Access is denied.
buildtrees\tensorflow\.bzl\install\3d1356cc22901f271d47ddd780d95b50\embedded_tools\jdk\bin\jimage.dll - Access is denied.
buildtrees\tensorflow\.bzl\install\3d1356cc22901f271d47ddd780d95b50\embedded_tools\jdk\bin\jli.dll - Access is denied.
buildtrees\tensorflow\.bzl\install\3d1356cc22901f271d47ddd780d95b50\embedded_tools\jdk\bin\management.dll - Access is denied.
buildtrees\tensorflow\.bzl\install\3d1356cc22901f271d47ddd780d95b50\embedded_tools\jdk\bin\management_ext.dll - Access is denied.
buildtrees\tensorflow\.bzl\install\3d1356cc22901f271d47ddd780d95b50\embedded_tools\jdk\bin\msvcp140.dll - Access is denied.
buildtrees\tensorflow\.bzl\install\3d1356cc22901f271d47ddd780d95b50\embedded_tools\jdk\bin\net.dll - Access is denied.
buildtrees\tensorflow\.bzl\install\3d1356cc22901f271d47ddd780d95b50\embedded_tools\jdk\bin\nio.dll - Access is denied.
buildtrees\tensorflow\.bzl\install\3d1356cc22901f271d47ddd780d95b50\embedded_tools\jdk\bin\server\jvm.dll - Access is denied.
buildtrees\tensorflow\.bzl\install\3d1356cc22901f271d47ddd780d95b50\embedded_tools\jdk\bin\sunec.dll - Access is denied.
buildtrees\tensorflow\.bzl\install\3d1356cc22901f271d47ddd780d95b50\embedded_tools\jdk\bin\vcruntime140.dll - Access is denied.
buildtrees\tensorflow\.bzl\install\3d1356cc22901f271d47ddd780d95b50\embedded_tools\jdk\bin\verify.dll - Access is denied.
buildtrees\tensorflow\.bzl\install\3d1356cc22901f271d47ddd780d95b50\embedded_tools\jdk\bin\zip.dll - Access is denied.
buildtrees\tensorflow\.bzl\install\3d1356cc22901f271d47ddd780d95b50\embedded_tools\jdk\lib\modules - The process cannot access the file because it is being used by another process.
buildtrees\tensorflow\.bzl\install\3d1356cc22901f271d47ddd780d95b50\windows_jni.dll - Access is denied.

buildtrees\tensorflow\.bzl\57u5iwxm\server\jvm.out - The process cannot access the file because it is being used by another process.

Parallel build needs to be turned off.
cc @jgehw

Parallel build needs to be turned off.

I wouldn't say so: this error arose from parallel manual cleanup while no all build processes had been killed before.
The build error was caused by:
CreateProcessW("git" init C:/vcpkg/buildtrees/tensorflow/.bzl/yvfmeljr/external/io_bazel_rules_go): The system cannot find the file specified.
Seems that git is not in the PATH environment variable.

@traumedy Can you please remove folder C:/vcpkg/buildtrees/tensorflow and try again?

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

authors: JackBoosY jgehw traumedy


text:
Not sure if static builds are using static libs

We use a .props file in our vcpkg-enabled builds:
  <PropertyGroup>
	<WindowsTargetPlatformVersion>10.0.18362.0</WindowsTargetPlatformVersion>
	<PlatformToolset>v142</PlatformToolset>
    <VcpkgEnabled>true</VcpkgEnabled>
	<VcpkgUseStatic>true</VcpkgUseStatic>

We were building without VcpkgUseStatic but I added this and re-ran our build. I can see seemingly as many DLLs are being copied as previously in the AppLocalFromInstalled step in the msbuild logs. And I see this:

VcpkgTripletSelection:
Using triplet "x64-windows-vs2019" from "C:\vcpkg\scripts\buildsystems\msbuild......\installed\x64-windows-vs2019"

I am not sure if it should explicitly mention static building or not, I not it should append -static to the triplet name but not whether it should display this. The raw path above does not include the static suffix.
I am aware some ports only support dynamic linking but it seems like it's doing it for everything.
Is there some way to tell for certain if it is using the static version or not? Could I bodge something into one of the scripts maybe?

Afaik this only works if you not use a custom triplet name. If you use a custom triplet name you have to add -static yourself

Can anyone confirm @autoantwort is correct? I can't really see how vcpkg even knows it's a custom triplet and I figured it was a simple shortcut if(VcPckUseStatic)triplet = triplet+"-static" but it's an easy workaround. I could try building with my explicit static triplet by name tomorrow, but it takes a while to build :)

https://github.com/microsoft/vcpkg/blob/b7f99c3c4b32c0b31b73701e92bb42fbea0c83cb/scripts/buildsystems/msbuild/vcpkg.targets#L15-L16

https://github.com/microsoft/vcpkg/blob/b7f99c3c4b32c0b31b73701e92bb42fbea0c83cb/scripts/buildsystems/msbuild/vcpkg.targets#L15-L16

Oh, hang on my msbuild script is very minimal but is that saying in L16 to only use the result of L15 if the triplet is empty, e.g. default? I missed that!

is that saying in L16 to only use the result of L15 if the triplet is empty, e.g. default?

Yeah. So instead of doing <VcpkgUseStatic>true</VcpkgUseStatic> in your property sheet do <VcpkgTriplet>$(VcpkgPlatformTarget)-$(VcpkgOSTarget)-vs2019-static</VcpkgTriplet> or something like that.

Many thanks. Yeah we just need to explicitly set our triplet name.
I'll close as it seems to be pretty clear. I do wonder if this functionality is ideal (or if the documentation in VS could be improved). I quite like the idea of specifying triplet but still being able to toggle -static personally.

authors: autoantwort jdx-john


text:
cannot use qt6 qmake to build project

When I try to use qt6 qmake to build, it shows:
Could not find qmake spec 'win32-msvc'.
Then adding -spec D:\vcpkg\installed\x64-windows-static\share\Qt6\mkspecs\win32-msvc to qmake, it shows:
Project ERROR: Could not find feature thread.
For qmake -query, it puts out:
QT_SYSROOT:
QT_INSTALL_PREFIX:D:/vcpkg/installed/x64-windows-static
QT_INSTALL_ARCHDATA:D:/vcpkg/installed/x64-windows-static/share/Qt6
QT_INSTALL_DATA:D:/vcpkg/installed/x64-windows-static/share/Qt6
QT_INSTALL_DOCS:D:/vcpkg/installed/x64-windows-static/doc/Qt6
QT_INSTALL_HEADERS:D:/vcpkg/installed/x64-windows-static/include/Qt6
QT_INSTALL_LIBS:D:/vcpkg/installed/x64-windows-static/lib
QT_INSTALL_LIBEXECS:D:/vcpkg/installed/x64-windows-static/tools/Qt6/bin
QT_INSTALL_BINS:D:/vcpkg/installed/x64-windows-static/bin
QT_INSTALL_TESTS:D:/vcpkg/installed/x64-windows-static/tests
QT_INSTALL_PLUGINS:D:/vcpkg/installed/x64-windows-static/Qt6/plugins
QT_INSTALL_QML:D:/vcpkg/installed/x64-windows-static/Qt6/qml
QT_INSTALL_TRANSLATIONS:D:/vcpkg/installed/x64-windows-static/translations/Qt6
QT_INSTALL_CONFIGURATION:
QT_INSTALL_EXAMPLES:D:/vcpkg/installed/x64-windows-static/share/examples/Qt6
QT_INSTALL_DEMOS:D:/vcpkg/installed/x64-windows-static/share/examples/Qt6
QT_HOST_PREFIX:D:/vcpkg/installed/x64-windows-static
QT_HOST_DATA:D:/share/Qt6
QT_HOST_BINS:D:/vcpkg/installed/x64-windows-static/bin
QT_HOST_LIBEXECS:D:/vcpkg/installed/x64-windows-static/tools/Qt6/bin
QT_HOST_LIBS:D:/vcpkg/installed/x64-windows-static/lib
QMAKE_SPEC:win32-msvc
QMAKE_XSPEC:win32-msvc
QMAKE_VERSION:3.1
QT_VERSION:6.2.2

OS: Windows 10 19044.1387
Compiler: Visual Studio Community 2022

But for qt5, qmake works well as usual, and for cmake build project, building poppler-qt6 is fine.
So is there any bug with qt6 qmake?

cc @Neumann-A

a) which feature set of qtbase the is the featuren concurrent which enables threads
b) which host triplet? QT_HOST_DATA looks wrong. Maybe qt.conf in the folder of qmake wasn't configured correctly.
c) by default -static triplets are not the native host triplets.

a) which feature set of qtbase the is the featuren concurrent which enables threads b) which host triplet? QT_HOST_DATA looks wrong. Maybe qt.conf in the folder of qmake wasn't configured correctly. c) by default -static triplets are not the native host triplets.

a) I found QThread in 'x64-windows-static\include\Qt6\QtCore', maybe it's qt6 core function?
b) x64-windows-static? I install both x64-windows and x64-windows-static for qt6. Here's the content of x64-windows-static\tools\Qt6\bin\qt.conf:
[DevicePaths]
Prefix=./../../../
Headers=include/Qt6/
Libraries=lib
Plugins=Qt6/plugins
Qml2Imports=Qt6/qml
Documentation=doc/Qt6/
Binaries=bin
LibraryExecutables=tools/Qt6/bin
ArchData=share/Qt6
Data=share/Qt6
Translations=translations/Qt6/
Examples=share/examples/Qt6/
[Paths]
Prefix=./../../../
Headers=include/Qt6/
Libraries=lib
Plugins=Qt6/plugins
Qml2Imports=Qt6/qml
Documentation=doc/Qt6/
Binaries=bin
LibraryExecutables=tools/Qt6/bin
ArchData=share/Qt6
Data=share/Qt6
Translations=translations/Qt6/
Examples=share/examples/Qt6/
HostPrefix=./../../../
HostData=./../../..//share/Qt6
HostBinaries=bin
HostLibraries=lib
HostLibraryExecutables=tools/Qt6/bin
It does exist some different paths from qt5, there're no qt5 in my vcpkg now, and I built qt6 from fresh today.

Could you manually remove the additional / in HostData=./../../..//share/Qt6 and see if it resolves the issue. If not try to set it to HostData=share/Qt6
The reason this is an issue is probably because you didn't do vcpkg install qtbase --triplet=x64-windows-static --host-triplet=x64-windows-static As such the qt.conf in x64-windows-static is invalid since the valid one is in x64-windows

Ok, it works fine when set it to HostData=share/Qt6.
Yeah, I installed qt6 as vcpkg install qtbase:x64-windows. I didn't consider host-triplet before.

Please keep this issue open until #21944 merge.

authors: Canvis-Me JackBoosY Neumann-A