text:
Error in post-job step of CacheV2 task when caching yarn packages

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: CacheV2 (https://github.com/microsoft/azure-pipelines-tasks/tree/master/Tasks/CacheV2)
Environment

Server - Azure Pipelines

Account name: markethype
Team project name: MarketHype
Build ID: 1563
URL: https://dev.azure.com/markethype/MarketHype/_build/results?buildId=1563

Agent - Hosted:

Agent Queue name: Azure Pipelines (https://dev.azure.com/markethype/MarketHype/_settings/agentqueues?queueId=17&view=jobs)

Issue Description
Using the CacheV2 task to cache Yarn packages, we're getting an error in the post-job step of the cache task.
The task is defined exactly as in the docs.
variables:
  YARN_CACHE_FOLDER: $(Pipeline.Workspace)/.yarn

steps:
- task: Cache@2
  inputs:
    key: 'yarn | "$(Agent.OS)" | yarn.lock'
    restoreKeys: |
       yarn | "$(Agent.OS)"
    path: $(YARN_CACHE_FOLDER)
  displayName: Cache Yarn packages

We're using the vs2017-win2016 image.
Error logs
Starting: Cache Yarn packages
==============================================================================
Task         : Cache
Description  : Cache files between runs
Version      : 2.0.0
Author       : Microsoft Corporation
Help         : https://aka.ms/pipeline-caching-docs
==============================================================================
Resolving key:
 - yarn                         [string]
 - "Windows_NT"                 [string]
 - common/config/rush/yarn.lock [file] --> 0551FA989D7CDCB2101F1397E8E7C5468396D4C72935548B6A74BEB126F0296F
Resolved to: yarn|"Windows_NT"|57F7K6kT3NtH/ZuSuWsxueTn4wCxuYls973WEnqCJgE=
Information, ApplicationInsightsTelemetrySender will correlate events with X-TFS-Session 06101a50-81b0-41b6-ab13-b130ee5c98ae
Information, Getting a pipeline cache artifact with one of the following fingerprints:
Information, Fingerprint: `yarn|"Windows_NT"|57F7K6kT3NtH/ZuSuWsxueTn4wCxuYls973WEnqCJgE=`
Information, There is a cache miss.
tar: D\:\\a\\1\\.yarn: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
Information, ApplicationInsightsTelemetrySender correlated 1 events with X-TFS-Session 06101a50-81b0-41b6-ab13-b130ee5c98ae
##[error]Process returned non-zero exit code: 2
Finishing: Cache Yarn packages

Same issue here, but this time with npm
Starting: Cache npm
Task         : Cache
Description  : Cache files between runs
Version      : 2.0.1
Author       : Microsoft Corporation
Help         : https://aka.ms/pipeline-caching-docs
Resolving key:

npm                                   [string]
"Windows_NT"                          [string]
./product/package.json [file] --> 66FF0092057590D58252E7A1365E9520D41F83083CE0C8C1DA0E038DC4C2D9D1
Resolved to: npm|"Windows_NT"|2DZ3WcfStD108j8qipq/0v97TF5eyy6fpvtPYfpDrZM=
Information, ApplicationInsightsTelemetrySender will correlate events with X-TFS-Session xxxxxxxxxx-1282-485c-a6f4-b92a59ed4955
Information, Getting a pipeline cache artifact with one of the following fingerprints:
Information, Fingerprint: npm|"Windows_NT"|2DZ3WcfStD108j8qipq/0v97TF5eyy6fpvtPYfpDrZM=
Information, There is a cache miss.
tar: Cannot change to directory E:\Agents\3\283\s\node_modules: No such file or directory
tar: Error is not recoverable: exiting now
Information, ApplicationInsightsTelemetrySender correlated 1 events with X-TFS-Session XXXXXXXX282-485c-a6f4-b92a59ed4955
##[error]Process returned non-zero exit code: 2
Finishing: Cache npm

Same issue here with yarn:
tar: /blah/blahgent/_work/1/s//node_modules, !/node_modules/**/node_modules: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
Information, ApplicationInsightsTelemetrySender correlated 1 events with X-TFS-Session 18de2057-e96c-4ff9-9091-595b9595f5cf
##[error]Process returned non-zero exit code: 2
Finishing: Cache
Any clue how to solve?

Came in here to +1 to this, below is my config:
variables:
  - name: yarnCacheFolder
    value: $(Pipeline.Workspace)/.yarn

  - task: Cache@2
    displayName: Cache Yarn Packages
    inputs:
      key: yarn | $(Agent.OS) | yarn.lock
      restoreKeys: |
        yarn | $(Agent.OS)
        yarn
      path: $(yarnCacheFolder)

Post-job: Cache Yarn Packages will throw an error
/home/vsts/work/1/.yarn: Cannot open: No such file or directory

For me it works, but I have set the directory directly because I found no suitable pipeline variable:
      - task: Cache@2
        inputs:
          key: 'yarn | "$(Agent.OS)" | Frontend/.../yarn.lock'
          restoreKeys: yarn | "$(Agent.OS)"
          path: /home/vsts/.cache/yarn
        displayName: Cache Yarn packages

I'm using a hosted agent (ubuntu-18.04); maybe this works for you as well.
One can print the relevant directory for yarn with yarn cache dir

@jfheins thanks for the hint.
I was able to fix this (cloud-hosting) using:
pool:
  vmImage: 'ubuntu-latest'
variables:
 - name: YARN_CONFIG_CACHE
    value: /home/vsts/.cache/yarn/v6
...
- task: Cache@2
  displayName: Cache node modules
  inputs:
    key: 'yarn | "$(Agent.OS)" | yarn.lock'
    restoreKeys: |
      yarn | "$(Agent.OS)"
    path: $(YARN_CONFIG_CACHE)

Bumping because this is still happening and I don't think it should be closed

I was running into this exact issue and fixed it by adding YARN_CACHE_FOLDER to the pipeline variables.
I had the Cache task as part of a task group and in the pipeline that uses the task group, there is a required field that asks for the value of YARN_CACHE_FOLDER which is used as 'path' for the Cache task. Filled in the field with $(Pipeline.Workspace)/.yarn but the post-job kept failing with same error as above.
Once I also defined YARN_CACHE_FOLDER=$(Pipeline.Workspace)/.yarn in the pipeline variables, the post-job stopped failing.

Bump - this actually just started happening on a build that hasn't changed since December.

Same here for Maven:

variables:
  IS_MASTER_OR_DEVELOP: $[in(variables['Build.SourceBranch'], 'refs/heads/master', 'refs/heads/develop')]
  MAVEN_CACHE_FOLDER: $(Pipeline.Workspace)/.m2/repository
  MAVEN_OPTS: '-Dmaven.repo.local=$(MAVEN_CACHE_FOLDER)'

  - task: Cache@2
    displayName: "Cache Maven local repo"
    inputs:
      key: 'maven | "$(Agent.OS)" | **/pom.xml'
      restoreKeys: |
        maven | "$(Agent.OS)"
        maven
      path: $(MAVEN_CACHE_FOLDER)

  - task: Maven@3
    displayName: "Publish artifacts"
    condition: eq(variables.IS_MASTER_OR_DEVELOP, true)
    inputs:
      mavenPomFile: './pom.xml'
      mavenOptions: '-Xmx3072m $(MAVEN_OPTS)'
      mavenAuthenticateFeed: true
      goals: 'deploy'

Same as @loxy

@pradpant No, didn't found a solution

bump!

This was working in a single stage pipeline, once I added another stage that causes this to get called twice, I now get the error with the cache post-job
Local agent running Win10 pro
Starting: Cache Yarn packages
==============================================================================
Task         : Cache
Description  : Cache files between runs
Version      : 2.0.1
Author       : Microsoft Corporation
Help         : https://aka.ms/pipeline-caching-docs
==============================================================================
Resolving key:
 - yarn                          [string]
 - "Windows_NT"                  [string]
 - src/MyProject.Web.Host/yarn.lock [file] --> A51A47DAA3D812F7DBE1028017AC2CA60169EA036A0C8BDD2DE0B6DADB8B21FE
Resolved to: yarn|"Windows_NT"|+Z30KjYR/75Haaf6MF5eU1mX/TrlZ7I5cG6FuT0QJfE=
ApplicationInsightsTelemetrySender will correlate events with X-TFS-Session 7d701a80-cde5-40c0-abed-7f66814cc117
Getting a pipeline cache artifact with one of the following fingerprints:
Fingerprint: `yarn|"Windows_NT"|+Z30KjYR/75Haaf6MF5eU1mX/TrlZ7I5cG6FuT0QJfE=`
There is a cache miss.
tar: could not chdir to 'C:\agent\_work\5\.yarn'

ApplicationInsightsTelemetrySender correlated 1 events with X-TFS-Session 7d701a80-cde5-40c0-abed-7f66814cc117
##[error]Process returned non-zero exit code: 1
Finishing: Cache Yarn packages

Same here. Seems the cache plugin is broken. Found another solution here: https://xebia.com/blog/caching-your-node-modules-in-azure-devops/

/remove-stale

I think caching will only work on a self hosted agent?

I think caching will only work on a self hosted agent?

No, this task is especially made for the Azure hosted agents. In a self hosted scenario, most of the caching works without this task. (For example: yarn has a machine wide global cache that persists in a self hosted agent)
The tricky thing is to get the cache directory right.
For example, an Azure agent mighthave the yarn cache in "/home/vsts/.cache/yarn" while a self hosted might need "/home/AzDevOps/.cache/yarn"
I'd recommend to include a step that logs out the cache directories for easier troubleshooting:
      - script: |
          node -v
          npm -v
          yarn -v
          yarn cache dir
          npm config get cache
        displayName: "Log versions & paths"

Solution
So, the issue seems to be that $(Pipeline.Workspace) does not return the home directory and hence the step can't find the build folders that are typically in the home dir. Take the output from the command @jfheins posted and add that to the variable directly.
# example for .npm

# replace this
variables:
  CACHE_FOLDER: $(Pipeline.Workspace)/.npm

# with this
variables:
  CACHE_FOLDER: /home/vsts/.npm

Result
Here's the result of the successful run after making the change

I have the same error, but with pnpm. This is the yaml from the docs:
variables:
  pnpm_config_cache: $(Pipeline.Workspace)/.pnpm-store

steps:
  - task: Cache@2
    inputs:
      key: 'pnpm | "$(Agent.OS)" | pnpm-lock.yaml'
      path: $(pnpm_config_cache)
    displayName: Cache pnpm

  - script: |
      corepack enable
      corepack prepare pnpm@latest-8 --activate
      pnpm config set store-dir $(pnpm_config_cache)
    displayName: "Setup pnpm"

  - script: |
      pnpm install
      pnpm run build
    displayName: "pnpm install and build"

@vixero-dev Can you share your the log from the task failure?
A lot of these issues look like folks either aren't:

Setting the correct variable (as defined by the package manager) at the pipeline-level to configure where the package manager should cache things
Actually invoking the package manager (the cache task does not do this)

@johnterickson you are correct. The variable wasn't being set.
After changing this part:
  - script: |
      corepack enable
      corepack prepare pnpm@latest-8 --activate
      pnpm config set store-dir $(pnpm_config_cache)
    displayName: "Setup pnpm"

to this:
  - script: |
      corepack enable
      corepack prepare pnpm@latest-8 --activate
    displayName: "setup pnpm"

  - script: pnpm config set store-dir $(pnpm_config_cache)
    displayName: "setup pnpm config"

I stopped experiencing this issue.

I had some similar issues that ended up being due to agents getting different versions of yarn.
I added
- bash: |
        corepack enable
        echo "Requesting Yarn version $(YARN_VERSION)"
        yarn set version $(YARN_VERSION)
        echo "Running Yarn $(yarn --version)"

along with configuring the YARN_VERSION variable to 3.6.4 in my case. I found out some agents would give me 1.22 sometimes in some build steps and 3.6 in others.  This helped me diagnose this.

Also experience this issue when following Microsoft's  documentation. It is an issue with the paths. This blog posts is a great dive into how to fix this and the Cache task.

Try adding an s between $(Pipeline.Workspace) and .yarn, so variable goes from:
YARN_CACHE_FOLDER: $(Pipeline.Workspace)/.yarn

To:
YARN_CACHE_FOLDER: $(Pipeline.Workspace)/s/.yarn

This is because when using checkout: self, it checks out the repository to $(Pipeline.Workspace)/s, as is explained here. Unless your using magic, your .yarn folder should be inside the repository.

@nickshanks347 's comment is really helpful. In deed, the same also happening to other tool such as pip

I tried
variables:
 NPM_CACHE_FOLDER: $(Pipeline.Workspace)/s/.npm
# ...
steps:
 - task: Cache@2
    displayName: Cache NPM packages
    inputs:
      key: '"npm" | "$(Agent.OS)" | package-lock.json'
      restoreKeys: |
        "npm" | "$(Agent.OS)"
        "npm"
      path: $(NPM_CACHE_FOLDER)
      cacheHitVar: NPM_CACHE_RESTORED

But I get
Post-job: Cache NPM packages

[View raw log](https://dev.azure.com/landshypotek/980d789b-7245-4c89-a4a0-320898842fa4/_apis/build/builds/9637/logs/19)
Starting: Cache NPM packages
==============================================================================
Task         : Cache
Description  : Cache files between runs
Version      : 2.198.0
Author       : Microsoft Corporation
Help         : https://aka.ms/pipeline-caching-docs
==============================================================================
Resolving key:
 - "npm"             [string]
 - "Linux"           [string]
 - package-lock.json [file] --> 0C9C69F14CFB03BABFC87109EECCB2B787FBAD0ECFC7E1F9F823A953E0A5303E
Resolved to: "npm"|"Linux"|NyzAW704Sn4J2Y1PCdbgFC5xaendrqBTYW+d+xSeAhY=
Using default max parallelism.
Using default max parallelism.
Max dedup parallelism: 192
DomainId: 0
ApplicationInsightsTelemetrySender will correlate events with X-TFS-Session ab82fec9-6c06-4dc7-9d91-1f0827ba36b5
Hashtype: Dedup64K
Getting a pipeline cache artifact with one of the following fingerprints:
Fingerprint: `"npm"|"Linux"|NyzAW704Sn4J2Y1PCdbgFC5xaendrqBTYW+d+xSeAhY=`
There is a cache miss.
tar: /home/vsts/work/1/s/.npm: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
ApplicationInsightsTelemetrySender correlated 1 events with X-TFS-Session ab82fec9-6c06-4dc7-9d91-1f0827ba36b5
##[error]Process returned non-zero exit code: 2
Finishing: Cache NPM packages

I would expect the post-job to create the folder if it doesn't exist.

I would expect the post-job to create the folder if it doesn't exist.

The output is telling you that the directory with the stuff you want to cache does not exist. (i.e. there is nothing to cache)
Have you tried to run npm --global cache verify in the pipeline to have npm output the cache directory?

Hi,
We're having the same issue, but with NuGet packages.
2024-10-07T12:06:28.2977763Z ##[section]Starting: NuGet Cache
2024-10-07T12:06:28.2990900Z ==============================================================================
2024-10-07T12:06:28.2991333Z Task         : Cache
2024-10-07T12:06:28.2991508Z Description  : Cache files between runs
2024-10-07T12:06:28.2991716Z Version      : 2.198.0
2024-10-07T12:06:28.2991911Z Author       : Microsoft Corporation
2024-10-07T12:06:28.2992096Z Help         : https://aka.ms/pipeline-caching-docs
2024-10-07T12:06:28.2992514Z ==============================================================================
2024-10-07T12:06:28.7416432Z Resolving key:
2024-10-07T12:06:28.7601309Z  - nuget                                       [string]
2024-10-07T12:06:28.7646429Z  - "Windows_NT"                                [string]
2024-10-07T12:06:29.3223086Z  - **/packages.lock.json,!**/bin/**,!**/obj/** [file pattern; matches: 1]
2024-10-07T12:06:29.3250490Z    - s\Exposed-API-v2\packages.lock.json --> EA02F2C348E6430278923F99E7BD2C6199A615EA44D8C5C04AA1ADAB8EDE1223
2024-10-07T12:06:29.3275286Z Resolved to: nuget|"Windows_NT"|14ENw8o70BCYT0eXNadg8S+3a/Qg6UX21F0XdjBe9oI=
2024-10-07T12:06:29.3902883Z Using default max parallelism.
2024-10-07T12:06:30.9012730Z tar: could not chdir to 'D:\a\1\.nuget\packages'
2024-10-07T12:06:30.9014291Z
2024-10-07T12:06:30.9015271Z Using default max parallelism.
2024-10-07T12:06:30.9016140Z Max dedup parallelism: 192
2024-10-07T12:06:30.9016911Z DomainId: 0
2024-10-07T12:06:30.9018238Z ApplicationInsightsTelemetrySender will correlate events with X-TFS-Session d190de86-e08b-403a-a797-9e5695b45cf8
2024-10-07T12:06:30.9019259Z Hashtype: Dedup64K
2024-10-07T12:06:30.9020154Z Getting a pipeline cache artifact with one of the following fingerprints:
2024-10-07T12:06:30.9021249Z Fingerprint: `nuget|"Windows_NT"|14ENw8o70BCYT0eXNadg8S+3a/Qg6UX21F0XdjBe9oI=`
2024-10-07T12:06:30.9022151Z There is a cache miss.
2024-10-07T12:06:30.9454673Z ApplicationInsightsTelemetrySender correlated 1 events with X-TFS-Session d190de86-e08b-403a-a797-9e5695b45cf8
2024-10-07T12:06:30.9509135Z ##[error]Process returned non-zero exit code: 1
2024-10-07T12:06:30.9523659Z ##[section]Finishing: NuGet Cache

Can we have an update on this ?
By the way, I agree with @Evanion when he say:

I would expect the post-job to create the folder if it doesn't exist.

With nuget, the process to get it working is the same:

Identify the relevant directory (for nuget: run dotnet nuget locals all --list within the pipeline)
Use a relevant directory in the cache task

Optional: Check what pipeline variables exist and maybe you can replace part of the absolute path with a variable

authors: AlexisJacob1 Bengkel DxTa Evanion adriansergheev bradringel c-eliasson daerogami dombarnes esoxjem jfheins jmaragon johnterickson jotatoledo kevinpiske lesterchan loxy nadworny nickshanks347 rfink sheldonlynn stevewarsa vixero-dev yooakim

repo: microsoft/azure-pipelines-tasks


text:
Use .NET Core does not set dotnet version to lower (2.2.xxx) after task was updated to Version : 2.169.1

Type: Bug
Task Name:
Use .NET Core
https://github.com/microsoft/azure-pipelines-tasks/blob/master/Tasks/UseDotNetV2
Environment

Server - Azure Pipelines
Azure DevOps : skype

Issue Description
After the Use .NET Core task was updated to Version : 2.169.1 one of our user builds started to fail.
After some debugging we found that even if we use the "Use .NET Core" task and it says in logs.
Found version 2.2.402 in channel 2.2 for user specified version spec: 2.2.402
Version: 2.2.402 was found in cache.
Creating global tool path and pre-pending to PATH.
If we run a .Net Core version next it falls back to latest version found on the Agent.
##[debug]C:\windows\system32\cmd.exe /c "dotnet --version"
dotnet --version
3.1.300

@andrelvahter By default, UseDotNetV2 task installs dotnet tool to $(Agent.ToolsDirectory)/dotnet
So you could reference it by $(Agent.ToolsDirectory)/dotnet --version
Another alternative is to use DotNetCoreCLI@2, this will by default select the dotnet version installed by UseDotnet task
Do let us know if this solves your issue

@issacnitin
Seems the dotnet.exe on the root level of
$(Agent.ToolsDirectory)/dotnet
is not updated

The SDK itself is copied.

So your solution sadly does not work :(
With Prev. version of the task it probably changed the PATH variable, so you did not need to use the full path but just call dotnet.exe. A lot of engineers would need to alter they definition to use the full path ?
From the Task itself I would anticipate that the root dotnet.exe would be updated.
Agent log:

Found version 2.2.402 in channel 2.2 for user specified version spec: 2.2.402
##[debug]Processed: ##vso[telemetry.publish area=TaskDeploymentMethod;feature=UseDotNetV2]{"userVersion":"2.2.402", "resolvedVersion":"2.2.402"}
##[debug]isExplicit: 2.2.402
##[debug]explicit? true
Version: 2.2.402 was found in cache.
##[debug]Agent.Version=2.168.2
##[debug]Processed: ##vso[task.prependpath]D:\a\_work\_tool\dotnet
##[debug]set DOTNET_ROOT=D:\a\_work\_tool\dotnet
##[debug]Processed: ##vso[task.setvariable variable=DOTNET_ROOT;issecret=false;]D:\a\_work\_tool\dotnet
##[debug]set DOTNET_MULTILEVEL_LOOKUP=0
##[debug]Processed: ##vso[task.setvariable variable=DOTNET_MULTILEVEL_LOOKUP;issecret=false;]0
Creating global tool path and pre-pending to PATH.
##[debug]testing directory 'C:\Users\builder\.dotnet\tools'
##[debug]Agent.Version=2.168.2
##[debug]Processed: ##vso[task.prependpath]C:\Users\builder\.dotnet\tools
##[debug]Agent.ProxyUrl=undefined
##[debug]task result: Succeeded
##[debug]Processed: ##vso[task.complete result=Succeeded;]

@andrelvahter That's surprising, I just tried installing version 2.2.402 and in another bash task, executed $(Agent.ToolsDirectory)/dotnet/dotnet.exe --version and got the version as 2.2.402 as well. The "File Version" might be in out of sync with the actual .NET version.
We cannot install tools globally, as agents will have access to only specific folders that are scoped down from the machine in which the agent is running. So the globally installed .NET versions are part of the agent image itself. You can find details about agent images here: https://github.com/actions/virtual-environments
As a workaround, for now, I still believe you can use $(Agent.ToolsDirectory)/dotnet/dotnet.exe. Do let us know if this works out

@issacnitin
Think it worked because you did not have a newer version already cached.
You can take a look at this pipeline .
https://skype.visualstudio.com/SBS/_build/results?buildId=31055087&view=logs&j=fd490c07-0b22-5182-fac9-6d67fe1e939b&t=00933dce-c782-5c03-4a85-76379ccfa50a

@andrelvahter AFAIK dotnet --version will print the version of dotnet.exe cli. It does not mean that 2.2.402 SDK is not installed. You can run dotnet --info to list all installed SDK versions.
dotnet.exe is just a cli and it invokes appropriate version of SDK based on the global.json found in the project. Since you are specifically trying to use 2.2.402, I assume that you have specified this version in global.json in your project. If so, then during dotnet execution, this version only will be picked.
Also, AFAIK you do not need to specify full path $(Agent.ToolsDirectory)/dotnet/dotnet.exe, as the task adds this to PATH.

@andrelvahter You're right, the cached dotnet CLI is not being overridden when installing a new version using UseDotNetV2. Thanks for reporting the issue!
As a workaround, you can change $(Agent.ToolsDirectory)/dotnet to say $(Agent.ToolsDirectory)/dotnet/2.2.402. Another workaround is, as @bishal-pdMSFT mentioned, use a global.json with the version specified. As 2.2.402 is installed by default in the latest windows images, you can avoid the UseDotNetV2 task if you're running on a hosted agent.
@bishal-pdMSFT You're right that we're adding it to the path, but now the path has multiple values for dotnet CLI. In the case of Unix based OS, the first executable found is picked, in Windows, I believe it is the same, but not sure. But yes, if we're pre-pending to the path, trying to execute using dotnet.exe is worth the effort.

Cool,
Ty for looking into it @issacnitin and @bishal-pdMSFT and for the hints and workarounds.
Now that we know the state we can take actions.
All the best,
Andrel

Awesome! I'm closing the issue for now, please feel free to re-open in case of any queries or concerns regarding this. Thanks @andrelvahter

@issacnitin Is this going to be fixed?  the cached dotnet CLI is not being overridden when installing a new version using UseDotNetV2. Thanks for reporting the issue!

The behaviour is by task design. Using global.json in an environment with multiple versions of .NET SDK is standard practice, @bishal-pdMSFT can take a call if we should change this behaviour

@rebecca-makar Could you help us with the incentive to have this behaviour changed ?

the cached dotnet CLI is not being overridden when installing a new version using UseDotNetV2

This is not an issue. A cached version of dotnet.exe does not mean that it will use cached version of SDK.
CLI != SDK
CLI will invoke correct version of SDK if it is specified in global.json.

ok, thank you!

source: gharchive/issue

authors: andrelvahter bishal-pdMSFT issacnitin rebecca-makar

license: MIT

license_type: permissive

license_source: github-api


text:
Notebooks: Highlight and Insert Code keyboard shortcut error in Markdown mode

Version: 1.34.0-rc1 (user setup)
Commit: 651f6fdcfc28e07f2ff25b76900fc5b52559a8b8
Date: 2021-12-09T02:01:49.852Z
VS Code: 1.58.0
Electron: 12.0.9
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Windows_NT x64 10.0.22000
Steps:

Create new notebook and add text cell
Type some text in cell
Try to highlight text using keyboard shortcut Ctrl + Shift + h
Try to insert code using keyboard shortcut Ctrl + Shift + k

Expected:
Text is highlighted
Code block is inserted
Actual:

NOT a regression but this is pretty bad functionality wise and is a simple fix so feel we should take this for ask mode.

repo: microsoft/azuredatastudio


text:
Fix web smoke tests

This PR fixes #

by default the driver tries to click the middle of the button, however that is a notification for the tests (privacy notification) so this just moves where it is trying to clikc to avoid the notification.

Coverage decreased (-0.002%) to 37.883% when pulling 271e9364b1cafc7ee78341929483537d8ad3d217 on test/fixweb into 3432743f63e8f7fb8a8f18124d7118cb78a54a95 on main.

source: gharchive/pull-request

authors: anthonydresser coveralls


text:
Allow override for Microsoft.Bot.Builder.AI.QnA.Dialogs.QnAMakerDialog

Class I'm referring to:
https://github.com/microsoft/botbuilder-dotnet/blob/main/libraries/Microsoft.Bot.Builder.AI.QnA/Dialogs/QnAMakerDialog.cs
Is your feature request related to a problem? Please describe.
The QnAMaker Dialog is a great boilerplate template to get up and running with the QnA service and Bot Service, but it is frustrating that I cannot modify the response back to the user. Particularly the method DisplayQnAResultAsync. With this change, I could return adaptive cards back to the user instead of plain text.
Describe the solution you'd like
change:
private async Task<DialogTurnResult> DisplayQnAResultAsync(WaterfallStepContext stepContext, CancellationToken cancellationToken)
to:
protected async virtual Task<DialogTurnResult> DisplayQnAResultAsync(WaterfallStepContext stepContext, CancellationToken cancellationToken)
Describe alternatives you've considered
Re-implement the class from the source code. It is pretty counter-productive to have to copy 600+ lines of code to just modify a response

@pchoudhari can you comment?

Thanks for the suggestion, we will triage this. Assigning to @vipeketi and @DishaAgarwal

@sahithikkss, could you address the PR comment so it could be merged?  Thanks! https://github.com/microsoft/botbuilder-dotnet/pull/4574

authors: nick-romano-kci pchoudhari tsuwandy vishwacsena

repo: microsoft/botbuilder-dotnet


text:
${} instead of @{} as bounding syntax.

Fixes #
Description

Specific Changes

Testing

Pull Request Test Coverage Report for Build 106367

7 of 7 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 84.255%

Totals

Change from base Build 106328:
0.0%

Covered Lines:
8733

Relevant Lines:
10025

💛  - Coveralls

authors: Danieladu coveralls

repo: microsoft/botbuilder-js


text:
fix: [#4490] Usage of a vulnerable package - Upgrade recognizers-text-number

Fixes #4490
Description
This PR upgrades the recognizers-text-number package to the latest version 1.3.1 containing the fix for the lodash.trimend security issue CVE-2020-28500.
It only upgrades this package leaving the rest of the recognizers-text packages in version 1.1.4 to avoid introducing breaking changes.
Specific Changes

Upgraded recognizers-text-number in botbuilder-dialogs-adaptive and botbuilder-dialogs.
Added @microsoft/recognizers-text-number ~1.3.1 in the root's  package.json resolutions section to force the latest version when the package is a nested dependency.
Updated unit tests to work with the new entities that are now recognized.
Updated yarn.lock file.

Testing
These images show the unit tests passing after the upgrade.

Pull Request Test Coverage Report for Build 5904039003

0 of 0   changed or added relevant lines in 0 files are covered.
82 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-0.4%) to 84.49%

Files with Coverage Reduction
New Missed Lines
%

libraries/botbuilder-lg/src/templateExtensions.ts
1
84.48%

libraries/botframework-streaming/src/utilities/createNodeServer.ts
1
78.57%

libraries/botframework-streaming/src/namedPipe/namedPipeServer.ts
12
50.68%

libraries/botframework-streaming/src/namedPipe/namedPipeClient.ts
17
34.09%

libraries/botframework-streaming/src/namedPipe/namedPipeTransport.ts
51
3.92%

Totals

Change from base Build 5903299207:
-0.4%

Covered Lines:
20052

Relevant Lines:
22485

💛  - Coveralls

authors: ceciliaavila coveralls


text:
Publishing child apps from other authoring resources than dispatch app shows error

Tool
Name: Dispatch
Version: 1.6.8
OS: Win 10 build 18363.720
Describe the bug and reproduction steps
I have 2 LUIS child apps in different authoring resources. I want to create a dispatch app in authoring resource 1 (AR1), using an app from AR1 and using another app from AR2.
The script runs through and I can use the dispatch app afterwars. However I get the following error in the logs and am unsure whether it's any problem that the child apps are not republished (why are they published at all, I wonder?).
[...]
Publishing app1 model...
Publishing app2 model...
Failed adding subscription key/publishing app2 - {
  "error": {
    "code": "Unauthorized",
    "message": "The user is not the owner or a co-owner of this application."
  }
}
Training test-dispatch model...
Publishing test-dispatch model...
[...]

I guess it's internally using the key of AR1 instead of AR2 for this request?
To Reproduce
Steps to reproduce the behavior:
Create a LUIS dispatch application using
dispatch init -n "test-dispatch" --luisAuthoringKey "key1" --luisAuthoringRegion "westeurope"
dispatch add -t luis -i "id1" -k "key1" --intentName "app1"
dispatch add -t luis -i "id2" -k "key2" --intentName "app2"
dispatch create

Expected behavior
No errors should be shown in the output.
[bug]

@sibbl, are AR1/AR2 owned by the same user?  How about subscription key?  Trying to get a repro...

@tsuwandy yes, both ARs were created by me. What could be specific is that the apps were all in AR2 beforehand. App1 created by me, app2 imported by a colleague. I then moved app1 into AR1 and created the dispatch app there.

And Dispatch is created using AR1 (which also has prediction resource)?

@tsuwandy yes, indeed. Dispatch and app1 are in AR2, app1 was kept in AR1.

@sibbl I got a repro. Still investigating, will update this thread as soon I figure out how to fix.

@sibbl , will have to consult with LUIS team what to do in this case.
Is there specific reason they have to be in different apps?

@tsuwandy you mean in different authoring resources? The background is mostly organizational so that we have a better separation of concern.
We have reusable Luis apps (AR2) and project specific Luis apps (AR1). Both kind of apps are combined into dispatch applications which we use for MS bot framework based chatbots for example.

@sibbl, we just published an update to dispatch (version 1.6.9).    Ignore the child publishing error as long as the whole dispatch app is created, trained and published.    We still have to support both apps not yet migrated to Azure and also those already on Azure LUIS resource.   Let me know if you are seeing issues using the newly created Dispatch app.  Please reactivate this issue if you are not able to use the Dispatch app.   Thanks!
P.S. I tried querying the newly created dispatch and i was able to get the child result in the connectedServiceResult, see below.
{
"query": "turn off light",
"topScoringIntent": {
"intent": "l_HomeAutomation",
"score": 1.0
},
"intents": [
{
"intent": "l_HomeAutomation",
"score": 1.0
},
{
"intent": "None",
"score": 6.6E-09
},
{
"intent": "l_Weather",
"score": 1.48148147E-10
}
],
"entities": [
{
"entity": "turn",
"type": "Device_PatternAny",
"startIndex": 0,
"endIndex": 3,
"role": ""
}
],
"connectedServiceResult": {
"query": "turn off light",
"topScoringIntent": {
"intent": "ControlDevice",
"score": 1.0
},
"intents": [
{
"intent": "ControlDevice",
"score": 1.0
},
{
"intent": "None",
"score": 3.9E-09
}
],
"entities": [
{
"entity": "light",
"type": "Device",
"startIndex": 9,
"endIndex": 13,
"score": 0.9847512
},
{
"entity": "turn off",
"type": "Operation",
"startIndex": 0,
"endIndex": 7,
"resolution": {
"values": [
"off"
]
}
},
{
"entity": "off",
"type": "Operation",
"startIndex": 5,
"endIndex": 7,
"resolution": {
"values": [
"off"
]
}
},
{
"entity": "turn",
"type": "Device_PatternAny",
"startIndex": 0,
"endIndex": 3,
"role": ""
}
]
}
}

Let me know if you are seeing issues using the newly created Dispatch app.

The error above is still happening with 1.6.9

Please reactivate this issue if you are not able to use the Dispatch app.

Tricky question as I can obviously use the Dispatch app.
So as far as I understand this issue should be closed, although it's not fixed (even though it's just a UI thing) but I can safely ignore the error for now and should not report any issue again? Well, okay then. 🤷♂

@sibbl , the child publishing error could be safely ignored as long as the dispatch app is created, trained and published.  Make sure you could use it at run time and that you could get back the child result as well.  create command failed for me before v 1.6.9.
The tool still needs to support LUIS apps that have not yet been converted to use Azure LUIS resource, unfortunately there is no way for the tool to know whether LUIS app is using Azure resource or the old authoring model.
Let me know if you are not able to use the Dispatch app at run time.

authors: sibbl tsuwandy

repo: microsoft/botbuilder-tools


text:
Programmer Calculator - Please add a feature to convert 8 bit words to their respective ASCII characters

Problem Statement

I am currently debugging UART communication with an oscilloscope and as of now I have to read the binary bits, convert to hex with the calculator, then look in a table for ASCII characters.
Evidence or User Insights

As of now the calculator only deals with raw numbers and data formulations. Adding this feature would connect the calculator more to the real world applications. I am an Electrical Engineer.
Proposal

This makes the calculator more functional and reduces the need for a table of ascii characters.
Goals

It would be nice if there was a keyboard that included the entire table, and you could type in ascii and see the binary, hex, etc.
Non-Goals

Performing math with ascii characters would be nice, but not necessary.
Low-Fidelity Concept

Have a condensed ascii character keyboard that contains only letters and numbers, with an option to expand it to the full table. If this is too much room, then simply have an option to type the character or pull one from an expandable list that is in a separate window. It wouldn't make sense to include by default the ascii character option in along with binary, decimal, hex, and octal, because ascii characters are not a number base. Perhaps add a checkbox to enable or disable this format (show or not show it along with all the other number types)
Requested Assignment

I'm just suggesting this idea.  I don't want to implement it.

I had intended to create a similar issue, but saw that this one already existed. Being able to convert from/to ASCII would have helped a lot in some development situations.
ASCII is sufficient for most cases and is enough in a first version, but there are also many other character tables. It should be possible to be able to choose the character table. Also able to choose different versions of Unicode.
In a further development, it would have been smooth if you could provide a longer text or hex string to convert.

repo: microsoft/calculator


text:
Allow deletion of typed-in operators

Problem Statement
In the current version of Calculator, if you typed in an operator, you cannot delete it. This will cause significant inconvenience, especially when dealing with rather complicated expressions, since you may have to discard the done part of the expression due to the wrong operator and type everything again from the beginning.
Adding the requested feature will greatly improve convenience.
Evidence or User Insights
Many scientific calculators, such as the Casio fx-991ES PLUS, support such feature; also, you can easily find online calculators doing so.
Proposal
If there is an operator at the end of an expression (like what is shown in the picture below,)

the user should be able to delete it by backspace on their real keyboard or by the deletion button on the calculator GUI.
Goals
(the same to what mentioned in 'proposal'.)
Low-Fidelity Concept
I think a GIF or a video will explain this perfectly. However, I don't get one.
Requested Assignment
I'm just suggesting this idea. I don't want to implement it.
(Actually I really want to implement it, but I am completely not able to)

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

This is similar enough to #163 that we would like to treat it as a duplicate. Let's continue the conversation there on how best to allow editing/deletion of typed-in operators.

authors: MicrosoftIssueBot Northurland grochocki


text:
Add recipe for bash script code reviews

This pull request adds a section about bash script code reviews to the engineering playbook. The section is based on findings from a customer project and answers questions such as:

What style guide should bash scripts follow?
Which automated code quality tools should bash scripts use?
How can bash scripts with complicated dependencies be made more robust?

@SaraSp @cloudbeatsch flagging for review, thanks!

authors: c-w fnocera


text:
[A] Added NIST Privacy Framework Mappings

Added NIST Privacy Framework to ISO Mappings

Dear Shiva,
Thank you so much for the mapping submission. The data curators and I are reviewing your mapping and will get back to you in case of any question.
All best,
Alex Li

Dear Shiva,
Thank you for your patience. The data curators reviewed your proposal and agreed with almost all of your contributions. There are two amendments that we would like to make, however.
First, we propose to map CT.DM-P5 to 7.4.5, 7.4.6, 7.4.8, 8.4.1, and 8.4.2. In other words, we propose to add 7.4.6, 8.4.1 and 8.4.2.
Second, we propose to map PR.DS-P5 to 6.2, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 6.10, 6.11, 6.12, and 6.15. All of your proposed item are inclusive of the above. But we think it makes sense to add most of clause 6 because NIST's understanding of data leak is rather comprehensive.
If you can agree to these adjustments, we can incorporate them into the project shortly. Please let us know what you think. We can also meet over a call if you see fit.
All best,
Alex

Hi Alex,
I reviewed the sections mentioned by you, and agree with the comments. You can make the changes and merge the request.
I would be glad to get in touch with the team.
As my next steps I was thinking of adding country specific GDPR implementations like UK Data Protection Act and France CNIL to start with into the project, but am slightly not sure how we want to structure them, like should we include them in the GDPR section or have one separate section for each county. We can co-ordinate this over mail/github issue or have a call based on your availability, else you can always discuss it in the next monthly meeting I would review them when its available in the repository.
And thanks to the team for reviewing the commit.
--
Best regards
Shiva Saxena

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: shivasaxena sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Hi Shiva,
Before I merge your pull request, I want to confirm why you have two separate pull requests. The pull request we are on "Added NIST Privacy Framework Mappings #9" already seems to contain the node dependency update we need. I'm not sure what the other pull request does.
As to EU member states and UK variations on GDPR, I think it is better to structure them separately. This will allow us to compare the difference between member states. Work wise, it is not too difficult since you can duplicate the GDPR mapping content and edit the delta.
Since you have no dispute over the suggested changes, I think we can continue to correspond over GitHub to spare one of us working at late hours to chat given the time zone difference between India and Seattle.
All best,
Alex

Hi Alex,
The idea was to have one commit per change, so I committed one for node and one for the data mapping update. Then I merged the node updates to my master and so the node updates are showing updates here too.
You can merge this change and close the other marked as already merged.
Moving forward I'll keep my master branch separate and have one branch per commit.
--
Best regards
Shiva Saxena

authors: alliMSFT msftclas shivasaxena

license: mit

license_source: bigquery


text:
added Number.toFixed function

I added an empty toFixed function in packages/core/src/number.ts and test case in devs/run-tests/02numbers.ts. when I run the test case withyarn build and yarn test, the console will return an exception
WASM> Exception: TypeError
WASM>  message: setting field 'toFixed' of a builtin frozen object
WASM>  at prototype [as F1_pc16] (node_modules/@devicescript/core/src/number.ts:1:1)
WASM>  at main [as F0_pc3] (devs/run-tests/02numbers.ts:1:1)
I think some settings occured this error?

@microsoft-github-policy-service agree

Try this:
diff --git a/runtime/devicescript/objects.c b/runtime/devicescript/objects.c
index b75762b7..1e80756c 100644
--- a/runtime/devicescript/objects.c
+++ b/runtime/devicescript/objects.c
@@ -261,8 +261,9 @@ static const uint8_t builtin_proto_idx[] = {
     [DEVS_BUILTIN_OBJECT_BUFFER] = 10,
     [DEVS_BUILTIN_OBJECT_GPIO_PROTOTYPE] = 11,
     [DEVS_BUILTIN_OBJECT_GPIO] = 12,
+    [DEVS_BUILTIN_OBJECT_NUMBER_PROTOTYPE] = 13,
 };
-#define MAX_PROTO 12
+#define MAX_PROTO 13

 devs_maplike_t *devs_get_builtin_object(devs_ctx_t *ctx, unsigned idx) {
     if (idx < sizeof(builtin_proto_idx)) {

It didn't work?

It didn't work?

No, it didn't.

repo: microsoft/devicescript


text:
ERROR: Could not allocate a buffer for target

When specifying a block size of 256 and up I receive this error.
I verified it happens on Windows Server 2016 and 2019
I am using the latest version of diskspd.
diskspd.exe -c1024M -w0 -t8 -d60 -o128 -r -b512K -C1 -Z1G -W1 -L -h "B:\temp\Diskspd\diskspdtest.dat"
ERROR: Could not allocate a buffer for target 'B:\temp\Diskspd\diskspdtest.dat'. Error code: 0x8
There has been an error during threads execution
Error generating I/O requests

An error code of 0x8 maps to there not enough memory resources available to process the command. I would suggest removing the -Z option if it's not needed or reduce it to something significantly smaller.
Please see issue #126 for further information on using the -Z option.

Thanks for your quick reply
Omitting the -Z parameter now allows using a block size of 512 (-b512K) but fails on 1024.
Is there any other advice?

Sorry, I missed the error you posted above. The -Z option isn't needed in your case as the workload is set to 100 percent reads. The problem you're facing is that we create both read and write buffers for each of the targets based on the block size and the request count even if the percentage of reads or writes is zero.
The call to VirtualAlloc is failing as your system has insufficient resources to fulfill the request. You either need to reduce the block size or the number of outstanding I/O requests used with the -o option.
You should also check that the architecture of the executable matches your platform. The 64-bit version is contained within the amd64 directory and should be used on Windows Server.

I was about to say the same. Also let me repeat back what your command line is now.
diskspd.exe -c1024M -w0 -t8 -d60 -o128 -r -b512K -C1 -W1 -L -h "B:\temp\Diskspd\diskspdtest.dat"
This specifies 8 threads issuing a target of 128 1 MiB IOs each. That’s a queue depth of 1024 IOs and 1 GiB of total queued IO operations. As DanP says DISKSPD is over-allocating for these IOs (2GiB: something that could be addressed), and if your system is 32bit this is likely exactly what the issue is. However, it is unlikely your storage requires anywhere near this amount to saturate and achieve maximum bandwidth, certainly with large IOs.
Try -t8 -o4, and then add to the queue depth in small increments. I believe you’ll see maximums before -o16. Then look at the latencies and explore how queue depth affects them, and consider thinning out the number of threads and queue depth to arrive at a total queue depth which is “just about right” for reaching maximum with moderate latency.
This is a pattern of analysis that’s common, and why the buffer allocation behavior is rarely a limit (even on 32bit systems).
From: Daniel Pearsonmailto:notifications@github.com
Sent: Thursday, April 2, 2020 09:57
To: microsoft/diskspdmailto:diskspd@noreply.github.com
Cc: Subscribedmailto:subscribed@noreply.github.com
Subject: Re: [microsoft/diskspd] ERROR: Could not allocate a buffer for target (#135)
Sorry, I missed the error you posted above. The -Z option isn't needed in your case as the workload is set to 100 percent reads. The problem you're facing is that we create both read and write buffers for each of the targets based on the block size and the request count even if the percentage of reads or writes is zero.
The call to VirtualAlloc is failing as your system has insufficient resources to fulfill the request. You either need to reduce the block size or the number of outstanding I/O requests used with the -o option.
You should also check that the architecture of the executable matches your platform. The 64-bit version is contained within the amd64 directory and should be used on Windows Server.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/diskspd/issues/135#issuecomment-607967868, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACCWSKJZIUOFTHW2LB3FZS3RKS7YNANCNFSM4L2KWY6Q.

Thanks you both! for the detailed information.
I used now the 64bit (amd64) version and was able to go up to a block size of 8192 with no failure. So yes using the 32 bit version is surly limited and that's understood.
Is there a any reference you can pointy me to to learn more on stress tests?

That's great news. If you haven't taken a look already, the wiki is a great place to start.

Excellent, i have gone over the wiki which was very usefull.

authors: DanPear dl2n yanivetrogi

repo: microsoft/diskspd


text:
Adds caching for CosmosDbSearchParameterStatusDataStore

Description
Checks the last updated date before fetching all SearchParameterStatuses.
This brings the RU usage from ~60 to ~2.8
Related issues
Addresses [issue #].
Testing
Describe how this change was tested.
FHIR Team Checklist

[ ] Update the title of the PR to be succinct and less than 50 characters
[ ] Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
[ ] Tag the PR with the type of update: Bug, Dependencies, Enhancement, or New-Feature
[ ] Tag the PR with Azure API for FHIR if this will release to the managed service
Review squash-merge requirements

Semver Change (docs)
Patch|Skip|Feature|Breaking (reason)

I think the idea of querying only when the datetime indicates that we need to is a very good idea.  I wonder if we should put this logic in the SearchParameterStatusManager as it is already tracking a timestamp for the last time the searchparameter status was checked.  In the data layer perhaps we add a simple method to get the latest timestamp, and the status manager then compares that against the last time?  This way that same simple method can be implemented for both SQL and Cosmos and the status manager will contain the logic.

authors: brendankowitz feordin

repo: microsoft/fhir-server


text:
[FluentSlider] [FluentNumberField] Fix #2948

Pull Request
📖 Description
Fixes issues reported in #2948. Two issue reported both related to changing the value of the control programatically.
🎫 Issues
The underlying issue is that the web components being wrapped were designed to have there states only changed interactively.  bind-value does not behave as expected. Inward binding works only on for initialization. Outward binding works as expected.
This gives the appearance of a sync issue.
👩💻 Reviewer Notes
FluentSlider - #2665 did not fully fix #2609. The original fix was to prevent the flickering when the slider was moved rapidly originally reported. I was not able to reproduce this problem with the current implementation of FluentDataGrid. I did end up adding debouncing with the DebounceAction.  I believe I did this correctly.
FluentNumberField - The fix was to ensure the underlying web component reflected the correct value. I could not find a way of distinguishing if the value was changed by manipulating the control or if it was changed programatically. I opted to use some javascript to force the value in the web component. I also added a DisposeAsync. It was missing.
I've also included an issue-tester page as part of this draft
📑 Test Plan
✅ Checklist
General

[ ] I have added tests for my changes.
[X] I have tested my changes.
[ ] I have updated the project documentation to reflect my changes.
[X] I have read the CONTRIBUTING documentation and followed the standards for this project.

Component-specific

[ ] I have added a new component
[ ] I have added Unit Tests for my new component
[ ] I have modified an existing component
[ ] I have validated the Unit Tests for an existing component

@vnbaaij
I've fixed the unit test by easing the BUnit JSInterop mode. I'm not sure if that breaks any testing conventions.
Should this be split into two PRs? One for FluentSlider and one for FluentNumberField.

Found another issue with my fix for FluentNumberField 😞

repo: microsoft/fluentui-blazor


text:
Bump JDK from 11 to 17

It would be nice to be able to take advantage of some of the language features that have been added since JDK 11.

The sort of PR where builds must fail :-)

The sort of PR where builds must fail :-)

Heh. Works on my machine.
Meant to be the sort of PR that engenders discussion.

Does it mean we can refactor some code, especially replacing the old switch case with an enhanced switch case?

@dsgrieve I'm talking about this: https://docs.oracle.com/en/java/javase/11/docs/specs/jar/jar.html#multi-release-jar-files
It allows us to only revert to an older version on specific .java files, not an entire project.

I'm really on the fence on this one. I'm personally working in JDK 16 and will likely move to 17 very shortly. So, part of me is saying, let us run the tests in JDK 17 and if it's all green, let's do it. Then, I'm also thinking about some of the developers I know who expressed interest that are stuck using their corporate supplied laptops that have just been allowed to move up to JDK 11... so, working in JDK 17... where does it leave them. Then the other part of my brain says, do we even have any of these developers in our audience. The answer to that question... I don't know and if they are not here now, would moving to JDK 17 cause them to be excluded in the future... I simply don't know. We need a @brunoborges surgery :-)

I'm really on the fence on this one. I'm personally working in JDK 16 and will likely move to 17 very shortly. So, part of me is saying, let us run the tests in JDK 17 and if it's all green, let's do it. Then, I'm also thinking about some of the developers I know who expressed interest that are stuck using their corporate supplied laptops that have just been allowed to move up to JDK 11... so, working in JDK 17... where does it leave them. Then the other part of my brain says, do we even have any of these developers in our audience. The answer to that question... I don't know and if they are not here now, would moving to JDK 17 cause them to be excluded in the future... I simply don't know. We need a @brunoborges surgery :-)

This point is very valid, we may well have corporate folks (or others) who can't develop on 17.  Let's keep this open and see what folks say.  @brunoborges Twitter poll?
As a side note - this is what a mailing list would be useful for? I'm not sure how we can broadcast this sort of thing.

Moving forward with this could potentially create two code streams where any fix in one would have to be applied to the other.

authors: brunoborges dsgrieve karianna kirk-microsoft rokon12

repo: microsoft/gctoolkit


text:
DocAssistant Enterprise - enhanced by AI, is poised to transform the way organizations handle document management. With features such as tiered access, top-notch security, smooth data access, and easy-to-use interfaces, it's geared to boost both productivity and efficiency.

Project name
DocAssistant Enterprise
Description
DocAssistant Enterprise
Revolutionizing Document Access Systems

The Url for Web App: https://hack-togather-wa.azurewebsites.net/
As we navigate the digital world, AI tools have become crucial in aiding productivity and efficiency. DocAssistant Enterprise is a system that has evolved from the foundation of DocAssistant to not only work with individual documents but handle a multitude of them across any organization.
DocAssistant Enterprise is designed to revolutionize your document management systems. It allows a seamless transition between various access levels within a company, making data retrieval a hassle-free experience for all users. Whether you're a business analyst needing developer-level data or a CEO requiring an overview of all documents, our system has got you covered.
This advanced system ensures high-level security by granting access to specific data to authorized personnel only. It proficiently manages denied document requests, maintaining stringent security measures while offering a user-friendly document management interface.
The system offers an intuitive and dynamic interface that can be customized to your preference. It facilitates the creation of new user accounts, management of document permissions, and batch uploading of documents.
The AI in DocAssistant Enterprise is powered by Azure Search Indexing and Open AI's ada model. It intelligently divides documents into manageable parts, collecting key details and feeding them into the Azure Search Index. Through smart prompt integration and orchestration of GPT chat models, our system serves as a co-pilot to aid employees in interacting with company data.
With DocAssistant Enterprise, online safety is a top priority. It allows you to focus on your offline security while it takes care of your online document management.
This project was made possible thanks to the combined efforts of our developers, business analysts, and testers, who worked tirelessly to deliver a product that truly revolutionizes document management. Thanks to Microsoft cognitive services Azure Open AI service, Azure Form Recognizer, and Azure Bot, we have been able to create a product that stands above the rest.
Future Development Features of DocAssistant Enterprise
As DocAssistant Enterprise continues to evolve and adapt to the ever-changing demands of the digital landscape, we are excited to announce a few features that we plan to develop in the future to enhance user experience and functionality:

SharePoint Documentation Interaction: We aim to integrate a feature that will allow users to engage in chats about different sections of SharePoint Documentation. This will enable users to have interactive discussions, share insights, and clarify doubts about SharePoint Documentation, fostering a collaborative environment.

Confluence Support: Acknowledging the widespread use of Confluence in managing project documentation, we plan to extend our support to this platform. This feature will allow users to integrate their Confluence documentation with DocAssistant Enterprise, enhancing accessibility and efficiency.

Azure DevOps Ticket Interaction: We plan to implement a feature that allows users to chat about tickets in Azure DevOps. This will facilitate real-time discussions about ongoing tasks, issues, or bugs, leading to quicker resolution and streamlined workflow.

GitHub Markdown Files Support: Recognizing the widespread use of GitHub for project development and management, we plan to extend our support to GitHub Markdown files. Users will be able to integrate their GitHub repositories with DocAssistant Enterprise, facilitating seamless interaction with project documentation stored as Markdown files.

Support for Various Document Formats: To make DocAssistant Enterprise a truly versatile tool, we plan to expand our support to various document formats without any limitations. This means users will be able to upload, access, and interact with documents regardless of their format, further simplifying document management and ensuring a more inclusive user experience.

These planned features aim to make DocAssistant Enterprise an even more comprehensive tool for document access, catering to a wider array of user needs and preferences. We look forward to rolling out these updates in the future!
Project Team:
Yurii Moroziuk – Project Lead /.Net Developer / DevOps
E-mail: Yurii.Moroziuk@hotmail.com
Credly: https://www.credly.com/users/yurii-moroziuk/badges
GitHub: https://github.com/YuriyMorozyuk95
Khrystyna Halytska - .Net Developer
E-mail: christinaozarko@gmail.com
Credly: https://www.credly.com/users/khrystyna-ozarko
GitHub: https://github.com/KhrystynaOX
Oleksandr Bendziak - Business Analysis, AI Prompt Engineer, Quality Assurance
E-mail: oleksandr.bendziak@gmail.com
Credly: https://www.credly.com/users/oleksandr-bendziak
GitHub: https://github.com/OlksBndz
Project Repository URL
https://github.com/YuriyMorozyuk95/DocAssistant.Ent
Project video
https://youtu.be/4GhzXbXEhRc
Team members
YuriyMorozyuk95, KhrystynaOX, OlksBndz

moved to https://github.com/microsoft/hack-together-dotnet/issues/90

repo: microsoft/hack-together-dotnet


text:
[MS-900] 챌린지 완료 인증

깃헙 ID: https://github.com/junsoo0

Microsoft Learn 프로필 링크: https://learn.microsoft.com/ko-kr/users/junsoo/

클라우드 스킬 챌린지 토픽/코드: Microsoft 365 기초 (MS-900)

/ok

repo: microsoft/hackers-ground


text:
Documentation: Missing Center of Excellence Starter-kit option

Documentation Issue
The Admin Environment and Settings section mentions "Bootstrap the Admin Environments with Center of Excellence Starter-kit" option. However, this option is missing in the deployment UI.
Had a look into the PR history and can see this option has been removed in https://github.com/microsoft/industry/pull/309 - foundations/powerPlatform/referenceImplementation/ppNorthStar-arm.json line 530.
Could you please advise if this has been done intentionally?
Can we expect this feature implemented in the script anytime soon?
Code of Conduct

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

Hi @mehowq - and thanks for reaching out, and I sincerely apologise for the delayed response. We were planning to include it initially, but due to some constraints with the API surface to put it together end-2-end, we removed the option for now.

authors: krnese mehowq

repo: microsoft/industry


text:
Stop working when typing

Describe the bug
Typing something, then cannot type anymore.
To Reproduce
Steps to reproduce the behavior:

type gcc lab2/5.2.c -
cannot type anymore

Expected behavior
Typing something, then cannot type anymore.
Environment

OS: Windows 22621.2506
Output of inshellisense --version: 0.0.1-rc.4
Nodejs Version: v20.9.0

Thanks for reporting this! I'm able to replicate this and will work on a fix

repo: microsoft/inshellisense


text:
Implement gpu pipeline and refactor training pipeline and configs

Renamed lightgbm_distributed into lightgbm_training so that all training options are available in one pipeline.
Created multiple docker containers for each lightgbm version (cpu/gpu/custom) and put them in a folder in lightgbm_python.
Implemented docker environment override from AzureML component sdk to switch docker environment at runtime
Added device_type as a parameter in lightgbm_python script
Implemented params in lightgbm_training conf file to change compute target, device type, override docker, etc.

Current cuda builds are failing, will fix that in another PR #70

repo: microsoft/lightgbm-benchmark


text:
Question: How can I edit the built-in control's theme

when developing UWP or WPF I can right-click on the control in the XAML designer and select "Edit theme", but WinUI 3 Preview 3 is apparently doesn't has a XAML designer yet, so what should I do when I want to change some details or layout of the built-in control(It could be any of them, not specifically someone)

@MikeHillberg I don't think we currently support the VisualStudio "Edit theme" button in winui 3 right now correct?
@dylech30th many of the Winui3 control templates are going to be the same or similar to the Winui 2 ones which are open source and can be found in this repo. Some of the controls are not included in this repo and then I would recommend using the Edit theme button in a regular UWP app to get the template.  Other than that I don't think there is a way to get the template.

For built-in UWP controls, you can find the template themes at C:\Program Files (x86)\Windows Kits\10\DesignTime\CommonConfiguration\Neutral\UAP\10.0.18362.0\Generic .

For built-in UWP controls, you can find the template themes at C:\Program Files (x86)\Windows Kits\10\DesignTime\CommonConfiguration\Neutral\UAP\10.0.18362.0\Generic .

Are these for the WinUI controls, or the Inbox Xaml controls?

The inbox xaml controls.

authors: StephenLPeters dylech30th huoyaoyuan mdtauk

repo: microsoft/microsoft-ui-xaml


text:
MatrixTransform always crashes

Describe the bug
media:RadialGradientBrush.Transform is broken.
Please use any matrix.
xmlns:media="using:Microsoft.UI.Xaml.Media"
I have a brush
<media:RadialGradientBrush
x:Key="YesKey1"
Center="432, -325"
RadiusX="47"
RadiusY="47">

media:RadialGradientBrush.Transform

</media:RadialGradientBrush.Transform>
</media:RadialGradientBrush>
If I remove Transform my application works fine.
Microsoft Visual Studio Professional 2019
Version 16.9.5
VisualStudio.16.Release/16.9.5+31229.75
Microsoft .NET Framework
Version 4.8.04084
Installed Version: Professional
Visual C++ 2019   00435-20310-66783-AA325
Microsoft Visual C++ 2019
.NET Core Debugging with WSL 2   1.0
.NET Core Debugging with WSL 2
ADL Tools Service Provider   1.0
This package contains services used by Data Lake tools
ASA Service Provider   1.0
ASP.NET and Web Tools 2019   16.9.693.2781
ASP.NET and Web Tools 2019
ASP.NET Core Razor Language Services   16.1.0.2112521+5741df381174d72f08e3632bb99f52e8635b6a1a
Provides languages services for ASP.NET Core Razor.
ASP.NET Web Frameworks and Tools 2019   16.9.693.2781
For additional information, visit https://www.asp.net/
Azure App Service Tools v3.0.0   16.9.693.2781
Azure App Service Tools v3.0.0
Azure Data Lake Node   1.0
This package contains the Data Lake integration nodes for Server Explorer.
Azure Data Lake Tools for Visual Studio   2.6.3000.0
Microsoft Azure Data Lake Tools for Visual Studio
Azure Functions and Web Jobs Tools   16.9.693.2781
Azure Functions and Web Jobs Tools
Azure Stream Analytics Tools for Visual Studio   2.6.3000.0
Microsoft Azure Stream Analytics Tools for Visual Studio
C# Tools   3.9.0-6.21160.10+59eedc33d35754759994155ea2f4e1012a9951e3
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Common Azure Tools   1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
Cookiecutter   16.9.21111.1
Provides tools for finding, instantiating and customizing templates in cookiecutter format.
Extensibility Message Bus   1.2.6 (master@34d6af2)
Provides common messaging-based MEF services for loosely coupled Visual Studio extension components communication and integration.
Fabric.DiagnosticEvents   1.0
Fabric Diagnostic Events
IntelliCode Extension   1.0
IntelliCode Visual Studio Extension Detailed Info
JetBrains ReSharper 2020.3.4   Build 203.0.20210316.132251
JetBrains ReSharper package for Microsoft Visual Studio. For more information about ReSharper, visit http://www.jetbrains.com/resharper. Copyright © 2021 JetBrains, Inc.
Microsoft Azure HDInsight Azure Node   2.6.3000.0
HDInsight Node under Azure Node
Microsoft Azure Hive Query Language Service   2.6.3000.0
Language service for Hive query
Microsoft Azure Service Fabric Tools for Visual Studio   16.0
Microsoft Azure Service Fabric Tools for Visual Studio
Microsoft Azure Stream Analytics Language Service   2.6.3000.0
Language service for Azure Stream Analytics
Microsoft Azure Stream Analytics Node   1.0
Azure Stream Analytics Node under Azure Node
Microsoft Azure Tools   2.9
Microsoft Azure Tools for Microsoft Visual Studio 2019 - v2.9.40423.1
Microsoft Continuous Delivery Tools for Visual Studio   0.4
Simplifying the configuration of Azure DevOps pipelines from within the Visual Studio IDE.
Microsoft JVM Debugger   1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines
Microsoft Library Manager   2.1.113+g422d40002e.RR
Install client-side libraries easily to any web project
Microsoft MI-Based Debugger   1.0
Provides support for connecting Visual Studio to MI compatible debuggers
Microsoft Visual C++ Wizards   1.0
Microsoft Visual C++ Wizards
Microsoft Visual Studio Tools for Containers   1.1
Develop, run, validate your ASP.NET Core applications in the target environment. F5 your application directly into a container with debugging, or CTRL + F5 to edit & refresh your app without having to rebuild the container.
Microsoft Visual Studio VC Package   1.0
Microsoft Visual Studio VC Package
Mono Debugging for Visual Studio   16.9.7 (df23ba6)
Support for debugging Mono processes with Visual Studio.
Node.js Tools   1.5.21130.2 Commit Hash:dacc0e71a5e060cdcab466a301cacea359c1b6da
Adds support for developing and debugging Node.js apps in Visual Studio
NuGet Package Manager   5.9.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/
NVIDIA CUDA 11.2 Wizards   11.2
Wizards to create new NVIDIA CUDA projects and source files.
Office Developer Tools for Visual Studio   16.0.30502.00
Microsoft Office Developer Tools for Visual Studio
ProjectServicesPackage Extension   1.0
ProjectServicesPackage Visual Studio Extension Detailed Info
Python   16.9.21111.1
Provides IntelliSense, projects, templates, debugging, interactive windows, and other support for Python developers.
Python - Conda support   16.9.21111.1
Conda support for Python projects.
Python - Django support   16.9.21111.1
Provides templates and integration for the Django web framework.
Python - Profiling support   16.9.21111.1
Profiling support for Python projects.
Rapid XAML Analysis   0.12.2
Tools to accelerate XAML app development by providing analysis and code fixes.
Rapid XAML Editor Extras   0.12.2
Tools to accelerate XAML app development by providing additional features to the Visual Studio editor.
Rapid XAML Generation   0.12.2
Tools to accelerate XAML app development by generating XAML.
Rapid XAML Roslyn Analyzers   0.12.2
Roslyn analyzers to help with XAML development.
Rapid XAML Templates   0.12.2
Project and item templates to help with XAML development.
Rapid XAML Toolkit   0.12.2
Tools to accelerate XAML app development.
This extension holds references and functionality used by the other Rapid XAML extensions.
SQL Server Data Tools   16.0.62103.10080
Microsoft SQL Server Data Tools
StylerPackage Extension   1.0
StylerPackage Visual Stuido Extension Detailed Info
Test Adapter for Boost.Test   1.0
Enables Visual Studio's testing tools with unit tests written for Boost.Test.  The use terms and Third Party Notices are available in the extension installation directory.
Test Adapter for Google Test   1.0
Enables Visual Studio's testing tools with unit tests written for Google Test.  The use terms and Third Party Notices are available in the extension installation directory.
ToolWindowHostedEditor   1.0
Hosting json editor into a tool window
TypeScript Tools   16.0.30201.2001
TypeScript Tools for Microsoft Visual Studio
UnoPlatformPackage Extension   1.0
UnoPlatformPackage Visual Studio Extension Detailed Info
Visual Basic Tools   3.9.0-6.21160.10+59eedc33d35754759994155ea2f4e1012a9951e3
Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Visual C++ for Cross Platform Mobile Development (Android)   16.0.31025.194
Visual C++ for Cross Platform Mobile Development (Android)
Visual F# Tools   16.9.0-beta.21102.9+7ce7132f1459095e635194d09d6f73265352029a
Microsoft Visual F# Tools
Visual Studio Code Debug Adapter Host Package   1.0
Interop layer for hosting Visual Studio Code debug adapters in Visual Studio
Visual Studio Container Tools Extensions   1.0
View, manage, and diagnose containers within Visual Studio.
Visual Studio Tools for CMake   1.0
Visual Studio Tools for CMake
Visual Studio Tools for Containers   1.0
Visual Studio Tools for Containers
Visual Studio Tools for Kubernetes   1.0
Visual Studio Tools for Kubernetes
Visual Studio Tools for Unity   4.9.1.0
Visual Studio Tools for Unity
VisualStudio.DeviceLog   1.0
Information about my package
VisualStudio.Foo   1.0
Information about my package
VisualStudio.Mac   1.0
Mac Extension for Visual Studio
VisualSVN   7.3.3
Integration with Subversion version control. For more information about VisualSVN, see the VisualSVN website at https://www.visualsvn.com
Copyright © 2021 VisualSVN Software Ltd. All rights reserved.
Windows Template Studio   4.1.21179.1
Windows Template Studio quickly builds a UWP app, using a wizard-based UI to turn your needs into a foundation of Windows 10 patterns and best practices.
WinUI Essentials   1.2
The easiest way to set up Visual Studio for the ultimate WinUI development experience.
Workflow Manager Tools 1.0   1.0
This package contains the necessary Visual Studio integration components for Workflow Manager.
Xamarin   16.9.000.292 (d16-9@26a958f)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin Designer   16.9.0.318 (remotes/origin/7b35adcdd1b204bbdcb279e0f029d151a20a4bf3@7b35adcdd)
Visual Studio extension to enable Xamarin Designer tools in Visual Studio.
Xamarin Templates   16.9.72 (426ebf6)
Templates for building iOS, Android, and Windows apps with Xamarin and Xamarin.Forms.
Xamarin.Android SDK   11.2.2.1 (d16-9/877f572)
Xamarin.Android Reference Assemblies and MSBuild support.
Mono: 5e9cb6d
Java.Interop: xamarin/java.interop/d16-9@54f8c24
ProGuard: Guardsquare/proguard/v7.0.1@912d149
SQLite: xamarin/sqlite/3.34.1@daff8f4
Xamarin.Android Tools: xamarin/xamarin-android-tools/d16-9@d210f11
Xamarin.iOS and Xamarin.Mac SDK   14.16.0.5 (ab40b131d)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.

@AghaKhan what is the crash? do you have a call stack or a dump you can share?

Thanks for prompt reply.
I am going to send a link where we are only looking why MatrixTransfom (Only in XAML) crashes. I think it works fine in code behind, because I never had this problem. You are only going to look 3 or 4 line of code.
Kindly download the code BugInXaml
look Styles.xaml fine. Please uncomment from 11 to 13 and run the application and you will get a crash.  You will get the crash in App.g.i.cs and look the message in (sender,e) Exception = {"The text associated with this error code could not be found.\r\n\r\nFailed to assign to property 'Windows.UI.Xaml.Media.Brush.Transform'. [Line: 12 Position: 30]"}
I hope it will help to fix the problem.

@geGao18 any idea why this transform would cause that crash?
        <media:RadialGradientBrush.Transform>
            <MatrixTransform Matrix="1,0,0,0,1,0" />
        </media:RadialGradientBrush.Transform>

It's not invertible - it scales the X axis by 1 and the Y axis by 0. That's probably why it's giving an error.
What's the scenario here? That transform will squish the gradient to nothing. If you wanted an identity transform, it'll be "1, 0, 0, 1, 0, 0".

Oh No. I tried many vector, and it always fails. Please try any vector. It always fails. Thanks for reply Agha

authors: AghaKhan StephenLPeters gegao18


text:
2.8.0-prerelease.220118001 WebView2.dll Microsoft Store certification failures

Describe the bug
See https://github.com/MicrosoftEdge/WebView2Feedback/issues/1868
I've been struggling with apps that fail certification ("Attention needed") because of WebView2.
Submitting it a few more times will eventually get it to pass. How or why I don't know.
Error Found: The supported APIs test detected the following errors:
API _CxxThrowException in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API __C_specific_handler in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API __std_exception_copy in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API __std_exception_destroy in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API __std_terminate in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API __std_type_info_destroy_list in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API _purecall in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API memcpy in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API memmove in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API memset in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API wcsrchr in vcruntime140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API ?_Xlength_error@std@@YAXPEBD@Z in msvcp140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API ?_Xout_of_range@std@@YAXPEBD@Z in msvcp140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API ?__ExceptionPtrAssign@@YAXPEAXPEBX@Z in msvcp140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API ?__ExceptionPtrCopy@@YAXPEAXPEBX@Z in msvcp140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API ?__ExceptionPtrCopyException@@YAXPEAXPEBX1@Z in msvcp140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API ?__ExceptionPtrCreate@@YAXPEAX@Z in msvcp140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API ?__ExceptionPtrCurrentException@@YAXPEAX@Z in msvcp140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API ?__ExceptionPtrDestroy@@YAXPEAX@Z in msvcp140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API ?__ExceptionPtrRethrow@@YAXPEBX@Z in msvcp140.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.
API __CxxFrameHandler4 in vcruntime140_1.dll is not supported for this application type. Microsoft.Web.WebView2.Core.dll calls this API.

Steps to reproduce the bug
Use 2.8.0-prerelease.220118001 in app
Submit app to Store
Expected behavior
App should pass without problem because of 2.8.0-prerelease.220118001
Screenshots
No response
NuGet package version
No response
Windows app type

[X] UWP
[ ] Win32

Device form factor
Desktop
Windows version
Windows 11 (21H2): Build 22000
Additional context
Version 2.8.0-prerelease.220118001 is not available in the drop-down on this form.

@krschau any ideas on what could be going on here?

Same issue, even if I set the minimum SDK of the application to 22000, the store still cannot be verified, I have failed several times in this step

@Richasy I reinstellend Nugget Packs (clear Cache) and reinstalled SDK after that it worked for me, i have no idea why that worked.

Can we please get this fixed? I can't keep hitting "Submit to the Microsoft Store" hoping it will work eventually.

Hitting the same problem. I need to use the preview version because it contains a recently implemented fix for a extremely annoying issue.
Any updates on this?

Same issue.

This is the same issue @myokeeh mentioned in the original post, so keep an eye on https://github.com/MicrosoftEdge/WebView2Feedback/issues/1868 as well as this issue.
The Store team is looking into this. They've made one WACK improvement that I suspect will help, but we're continuing to investigate.

We have gotten word from the store team that the WACK tools have been updated so that should solve the API check issues during store ingestion.  Of course if anyone does see any problems please let us know.

@DavidShoe @krschau this is happening again.

authors: DavidShoe Richasy krschau lars-rogalski myokeeh ojhad onein528 tipa


text:
MenuFlyout does not update correctly on theme change

Describe the bug
Changing the system theme from Light to Dark or from Dark to Light will not update the Theme of a MenuFlyout on runtime like the rest of the controls.
This happens also in WinUI 3 Gallery app, but randomly, as I can't reproduce it everytime. On my app, on the otherhand, I can reproduce it everytime.
The only way it will display the correct theme is to reopen the app.
It might also be related to #3373 which was for WinUI 2.
Steps to reproduce the bug

Create a blank WASDK app, packaged.
Add a MenuFlyout on the MainWindow.

<StackPanel Orientation="Horizontal" HorizontalAlignment="Center" VerticalAlignment="Center">
    <AppBarButton Icon="Sort" IsCompact="True">
        <AppBarButton.Flyout>
            <MenuFlyout>
                <MenuFlyoutItem Text="By rating" Tag="rating"/>
                <MenuFlyoutItem Text="By match" Tag="match"/>
                <MenuFlyoutItem Text="By distance" Tag="distance"/>
            </MenuFlyout>
        </AppBarButton.Flyout>
    </AppBarButton>
</StackPanel>

Open the MenuFlyout.
Step 3 is important, because if you don't open it first, and you change the theme, then open, the correct theme will be applied.

Change the system theme from the Settings App > Personalization > Colors : Chose Color Mode - Light or Dark

Open the MenuFlyout.

Observe the strange color state of the Flyout, it's not Light or Dark theme, more of a broken dimmed or washed out state.

Expected behavior
The Flyout should display the correct theme based on what theme was selected by the OS at runtime, without the need to reopen the app or to not open the MenuFlyout first.
Screenshots

Light Theme normal state

Light Theme switched state

Dark Theme normal state

Dark Theme switched state
NuGet package version
WinUI 3 - Windows App SDK 1.2.2: 1.2.221209.1
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response

We were able to repro this simple case, looks like a theming issue on the background, thanks for filing.

@gabbybilka I'm also hitting this with a Flyout with custom content. It seems that if the flyout isn't shown prior to the theme change it works correctly, but after, the style seems to be cached. Is there a workaround until this is fixed to notify the flyout to recreate the content or update its style references?

This also affects content dialogs.

A fix for this was checked in for WinAppSDK 1.6, and was included in 1.6-experimental1.

authors: ThreeSevenths bogdan-patraucean codendone gabbybilka mikernet


text:
Bug:Build failure due to namespace changes in XamlTypeInfo after C++/WinRT update

Describe the bug
In cppwinrt version 2.0.240111.5
I'm experiencing a build failure when referencing a WinUI 3 runtime component (root namespace: Control1) in a WinUI 3 project (root namespace: App1). The namespaces registered in App1's XamlTypeInfo are different before and after updating C++/WinRT.
Before the update, the entry in XamlTypeInfo looks like this:
L"Control1.UserControl1", L"",
&ActivateType<::winrt::Control1::UserControl1>, nullptr, nullptr, nullptr,
121, // Microsoft.UI.Xaml.Controls.UserControl
85, 0, -1, TypeKind::Metadata,
TypeInfo_Flags_None,
-1,

After the update, it changes to:
L"Control1.UserControl1", L"",
&ActivateLocalType<::winrt::Control1::implementation::UserControl1>, nullptr, nullptr, nullptr,
121, // Microsoft.UI.Xaml.Controls.UserControl
85, 0, -1, TypeKind::Custom,
TypeInfo_Flags_IsLocalType | TypeInfo_Flags_None,
-1,

Steps to reproduce the bug
I'm experiencing a build failure when referencing a WinUI 3 runtime component (root namespace: Control1) in a WinUI 3 project (root namespace: App1).
Expected behavior
No response
Screenshots
No response
NuGet package version
None
Windows version
No response
Additional context
No response

Was it just C++/WinRT that changed?
I ask this because C++/WinRT isn't responsible for the generation of any of the files involved in XamlTypeInfo. The way the build process works is:

Midl compiles the .idl files into the individual .winmd files. You can find these in $(IntDir)\Unmerged.

Mdmerge merges these individual .winmd files into the application combined .winmd file. So it reads the files from $(IntDir)\Unmerged and writes to $(IntDir)\Merged$(RootNamespace).winmd.

It copies this merged .winmd file to $(OutDir).

Cppwinrt runs for the first time. This run generates the basic platform headers. These are stored in $(ProjectDir)\Generated Files.

Cppwinrt runs for the second time. This run generates additional platform headers, this would include SDK references. These are stored in the same place.

Cppwinrt runs for the third time. This run reads the application .winmd files and produces the component headers and implementation source. These are stored in the same place. This means that C++/WinRT is responsible for reading the .winmd file and generating .h files under $(ProjectDir)\Generated Files.

The first Xaml Compiler pass runs. This reads the various .winmd files and produces some header and source files.

The second Xaml Compiler pass runs. This reads the various .winmd files and the state from the first pass and produces the remaining source files, this is when XamlTypeInfo.cpp should be generated.

So I could understand an update to the Windows App SDK package causing this, since that is what contains the Xaml Compiler. But an update to C++/WinRT shouldn't cause this.

Possibly related: https://github.com/microsoft/cppwinrt/issues/1397

@takatsuka2022 Can you share a repro project?

We have created a test pro. We have also confirmed that the solution builds successfully and is executable by reverting the CppWinRT version back to 2.0.230706.1.
ControlLib 2.zip

@takatsuka2022 thank you for the repro.  A fix has been made to CppWinRT: https://github.com/microsoft/cppwinrt/pull/1404

Fix has been published: https://www.nuget.org/packages/Microsoft.Windows.CppWinRT/2.0.240405.15


text:
Update HNav based on API Review

Fixes #2195
Description
After going through an API review for the new Hierarchical NavigationView, there were two recommendations:

Rename NavigationViewCollapsedEventArgs and NavigationViewExpandingEventArgs to NavigationViewItemCollapsedEventArgs and NavigationViewItemExpandingEventArgs

Add an ExpandingItem and CollapsedItem property to the args

How Has This Been Tested?
Updated test to verify new changes

/azp run

@ojhad looks like there were some test failures in the test pass:

InteractionTests.NavigationViewTests.VerifyExpandCollpaseFunctionality
InteractionTests.NavigationViewTests.SelectingNonTopLevelItemInOverflow

/azp run

/azp run

authors: kmahone ojhad


text:
MuseCoco Live Demo

Hi,
Are you planning to create a live demo/Hugging Face Space demo of MuseCoco?
Thanks!

I'd love to check it myself also!

authors: demoskalifi fakerybakery

repo: microsoft/muzic


text:
Issue creating new container, Access denied to a layer???

PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Describe the issue
Unable to create a new container, always get the error below.  I suspect it is a Docker problem and not a BCContainerHelper issue but don't know where to get help with Docker issues.

Docker : Error response from daemon: container 86afd4f8812b3a61c950b51f6941b51ab10e73111b325c8f5a95c1e32dd6cf52: driver "windowsfilter" failed to remove root filesystem: failed to
detach VHD: The device is not ready.: rename D:\dockerdata\windowsfilter\86afd4f8812b3a61c950b51f6941b51ab10e73111b325c8f5a95c1e32dd6cf52
D:\dockerdata\windowsfilter\86afd4f8812b3a61c950b51f6941b51ab10e73111b325c8f5a95c1e32dd6cf52-removing: Access is denied.
At C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\2.0.16\HelperFunctions.ps1:120 char:17
Docker rm $out -f
~~~~~~~~~~~~~~~~~
CategoryInfo          : NotSpecified: (Error response ...cess is denied.:String) [], RemoteException
FullyQualifiedErrorId : NativeCommandError

Scripts used to create container and cause the issue
$containerName = 'rms-bc14'
$password = 'P@ssw0rd'
$securePassword = ConvertTo-SecureString -String $password -AsPlainText -Force
$credential = New-Object pscredential 'admin', $securePassword
$auth = 'UserPassword'
$artifactUrl = Get-BcArtifactUrl -type 'OnPrem' -version '14.8.38658.0' -country 'gb' -select 'Closest'
$licenseFile = 'd:\license\bc14license.flf'
New-BcContainer `
    -accept_eula `
    -containerName $containerName `
    -credential $credential `
    -auth $auth `
    -artifactUrl $artifactUrl `
    -includeTestToolkit `
    -licenseFile $licenseFile `
    -dns '192.168.0.1' `
    -usessl -installCertificateOnHost `
    -isolation 'hyperv' `
    -includeCSIDE `
    -updateHosts

Full output of scripts
BcContainerHelper is version 2.0.16
BcContainerHelper is running as administrator
Host is Microsoft Windows 10 Pro - 21H1
Docker Client Version is 20.10.8
Docker Server Version is 20.10.8
Removing container rms-bc14
Removing rms-bc14 from container hosts file
Removing rms-bc14-* from container hosts file
Removing d:\bccontainerhelper\Extensions\rms-bc14
Fetching all docker images
Fetching all docker volumes
INFO: Windows 10 21H1 images are not yet available, using 2004 as these are found to work better than 20H2 on 21H1
Using image mcr.microsoft.com/businesscentral:10.0.19041.1288
Creating Container rms-bc14
Style: onprem
Multitenant: No
Version: 14.8.38658.0
Platform: 14.0.38650.0
Generic Tag: 1.0.1.8
Container OS Version: 10.0.19041.1288 (2004)
Host OS Version: 10.0.19043.1288 (21H1)
Using hyperv isolation
Using locale en-GB
Disabling the standard eventlog dump to container log every 2 seconds (use -dumpEventLog to enable)
Using license file d:\license\bc14license.flf
Files in d:\bccontainerhelper\Extensions\rms-bc14\my:
- AdditionalOutput.ps1
- AdditionalSetup.ps1
- license.flf
- MainLoop.ps1
- SetupVariables.ps1
- updatehosts.ps1
Creating container rms-bc14 from image mcr.microsoft.com/businesscentral:10.0.19041.1288
86afd4f8812b3a61c950b51f6941b51ab10e73111b325c8f5a95c1e32dd6cf52
Docker : Error response from daemon: container 86afd4f8812b3a61c950b51f6941b51ab10e73111b325c8f5a95c1e32dd6cf52: driver "windowsfilter" failed to remove root filesystem: failed to
detach VHD: The device is not ready.: rename D:\dockerdata\windowsfilter\86afd4f8812b3a61c950b51f6941b51ab10e73111b325c8f5a95c1e32dd6cf52
D:\dockerdata\windowsfilter\86afd4f8812b3a61c950b51f6941b51ab10e73111b325c8f5a95c1e32dd6cf52-removing: Access is denied.
At C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\2.0.16\HelperFunctions.ps1:120 char:17
                 Docker rm $out -f
                 ~~~~~~~~~~~~~~~~~
     CategoryInfo          : NotSpecified: (Error response ...cess is denied.:String) [], RemoteException
     FullyQualifiedErrorId : NativeCommandError

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context

does it happen all the time? Yes
did it use to work? Yesterday I created a container without an issue.

Well, there’s probably the quite simple answer: Now you are using Isolation hyperv and earlier you where using isolation process (your log says you do so).

I will write a blog post telling everybody that Windows Server 2019, Windows Server 2022 or Windows 11 are recommended platforms.

authors: GreatScott000 NAVspecialist freddydk

repo: microsoft/navcontainerhelper


text:
Error with Compile-ObjectsInNavContainer command

Hi,
It's my first time that I'm working with NavContainerHelper, I'm trying to compile modified objects by executing the command : "Compile-ObjectsInNavContainer -containername navserver -SynchronizeSchemaChanges Yes" where navserver is my server name but I'm getting the error :
Compiling objects with compiled=0
Generating symbols for objects compiled
!
at Compile-NAVApplicationObject, C:\Program Files (x86)\Microsoft Dynamics NAV\140\RoleTailored Client\Microsoft.Dynamics.Nav.Ide.psm1: line 610
at , : line 30
!
At C:\Program Files\WindowsPowerShell\Modules\navcontainerhelper\0.6.1.5\ContainerHandling\Invoke-ScriptInNavContainer.ps1:30 char:13

        Invoke-Command -Session $session -ScriptBlock $scriptbloc ...

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

CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Compile-NAVApplicationObject
PSComputerName        : c56f86632ba94bba3fc81f41f5cb11e573b0d22d4b1ab8977e66dcf8e44b3df0

when Im restarting the navcontainer I get the warning : You are running a container which is 274 days old. it could be the origin of the problem ?

If you only get a warning - that's fine - you must have started the container using accept_outdated.
I am afraid you are hit by https://freddysblog.com/2020/02/14/hyperv-isolation-to-the-rescue/ - I saw another issue around writeerror, which was caused by this. You could uninstall the february security update and retry.

it works after uninstalling the february security, Thanks Freddydk.

authors: Oufaraj freddydk


text:
Web Client is not working BC14

The web client is not working and it is empty when it starts container.  Other container web clients are working fine but not sure what is causing for this  below is the log
Starting Local SQL Server
Starting Internet Information Server
Starting Service Tier
Container IP Address: 172.30.161.204
Container Hostname  : HOSK
Container Dns Name  : HOSK
Web Client          :
Dev. Server         : http://HOSK
Dev. ServerInstance : NAV
Setting HOSK to 172.30.161.204 in host hosts file
Files:
http://HOSK:8080/al-3.0.154634.vsix
Initialization took 17 seconds
Ready for connections!
Initializing...
Setting host.docker.internal to  in container hosts file (copy from host hosts file)
Setting gateway.docker.internal to  in container hosts file (copy from host hosts file)
Setting host.docker.internal to 10.0.0.7 in container hosts file (copy from host hosts file)
Setting gateway.docker.internal to 10.0.0.7 in container hosts file (copy from host hosts file)
Setting kubernetes.docker.internal to 127.0.0.1 in container hosts file (copy from host hosts file)
Setting host.containerhelper.internal to 172.30.160.1 in container hosts file
Restarting Container
PublicDnsName unchanged
Hostname is HOSK
PublicDnsName is HOSK
Using NavUserPassword Authentication
Container IP Address: 172.30.167.210
Setting HOSK to 172.30.167.210 in host hosts file
Container IP Address: 172.30.168.88
Setting HOSK to 172.30.168.88 in host hosts file
Initialization took 21 seconds
Setting host.containerhelper.internal to 172.31.224.1 in container hosts file
Container IP Address: 172.31.229.155
Setting HOSK to 172.31.229.155 in host hosts file
Initialization took 27 seconds

What script leads to this output?

New-BCContainer     -accept_eula
-containerName $containerName     -imageName mcr.microsoft.com/businesscentral/onprem:14.4.35602.0-na-ltsc2019
-licenseFile 'C:\Users\skulla\OneDrive - ArcherPoint, Inc\Documents\Licenses\APDEV-BC.flf'     -memoryLimit 8G
-Verbose     -shortcuts Desktop
-updateHosts     -includeCside
-enableSymbolLoading     -includeAL
-auth navuserpassword `
-accept_outdated
First time it works but after a day or two the web client stopped working, one time in the log i got the message like you don't have permission denied to the path Microsoft.AI.Agent.ntercept.dll at New-NAVWebSite but that even disappeared after couple of restarts and is blank

Some important information there in the second reply, but I would also need the full output.
I cannot see what isolation mode you are running, what windows version the host is etc. etc.
and please mark script and output with "insert code" in the toolbar - then it is formatted better.
Also, does this happen all the time - or did this happen maybe due to a windows update?
Typically if I get all these info in the first iteration, I can answer questions in a few minutes and it saves me and you precious time.

Closing this bug. Please reopen with sufficient information for us to be able to see what is going on, else troubleshooting will be guesswork.

authors: freddydk skkulla


text:
compatibility with pwsh

Using an empty string as parameter not works in pwsh.
This code fails in PS7.x
$a = ""
docker ps $a

This code works in PS5.x and PS7.x
$a = $null
docker ps $a

Thanks

authors: freddydk lukas-pfeifhofer


text:
ChildProcessError: “powershell.exe”is not recognized as an internal or external command, operable program or batch file.

Describe the issue:
I started NNI yesterday by following the  tutorial,but I had a problem when I was running the MNIST example——the experiment has been successfully launched, there was an error in the "Status" property of the experimental interface. The detailed content of Error is Command failed: powershell.exe New-Item -Path "XXX" -ItemType "directory" -Force 'powershell.exe' is not recognized as an internal or external command,operable program or batch file. powershell.exe' New-Item -Path "XXX" -ItemType "directory" -Force (exited with error code 1). I tried to solve the problem but not succeeded.
Environment:

NNI version:2.5
Training service (local|remote|pai|aml|etc):local
Client OS:Windows 10
Server OS (for remote mode only):None
Python version:3.8.5
PyTorch/TensorFlow version: torch 1.1.0/ tf 2.7.0
Is conda/virtualenv/venv used?:maybe no,but I had conda
Is running in Docker?:no

Experimental Interface

dispatcher

nnictl_stderr

nnimanager

nnictl_stdout
blank

Hello @DoveEchoing , maybe this can help you.
https://stackoverflow.com/questions/29778121/powershell-is-not-recognized-as-an-internal-or-external-command-operable-progr

Hello @DoveEchoing , maybe this can help you.
https://stackoverflow.com/questions/29778121/powershell-is-not-recognized-as-an-internal-or-external-command-operable-progr

Thank you, I will read it carefully.

Hello @DoveEchoing , maybe this can help you.
https://stackoverflow.com/questions/29778121/powershell-is-not-recognized-as-an-internal-or-external-command-operable-progr

I fixed this problem by adding powershell path to environment variable, but I had another problem——all trials had failed.

Hello @DoveEchoing , maybe this can help you.
https://stackoverflow.com/questions/29778121/powershell-is-not-recognized-as-an-internal-or-external-command-operable-progr

I fixed this problem by adding powershell path to environment variable, but I had another problem——all trials had failed.

I will try to solve it.

I meet this problem when use nni in vscode, and adding path donot work .I solve it by starting nni in powershell directly.

authors: DoveEchoing J-shang feiguofeiguo

repo: microsoft/nni