text:
Require "as const"?

Suggestion
I have a factory function that takes a specification in the form of an object literal and returns a class. If the description passed in is a literal and annotated with as const, then the static properties it takes from the specification retain their exact types (like strings for instance), vs. the more generic "string" type:
type Specification = { readonly type: string; };

function SourceNode<T extends Specification>(props: T) {
    return { ...props }; // simplified to show a reduction.
};

export const Statment = SourceNode({
    type: "Statement"
} as const);

// This statically knows it will never enter this if
if (Statement.type === "pizza") {
}

However, if you forget as const, all of this of course falls apart. I'd like a way to immediately surface an error if you don't pass an as const object literal:
// Would be nice if this yelled at you, or maybe could somehow infer that it's const since it's never used again?
export const Statement = SourceNode({
    type: "Statement"
});

I've tried every manner of annotation but haven't been able to accomplish this, but would love to know if there is a way to do this currently:
function SourceNode<T extends Readonly<Specification>>(props: T)  { readonly [key in keyof T]: T[key] } {
    return { ...props } as const;
};

🔍 Search Terms
as const, required, const annotation
✅ Viability Checklist
My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

A workaround from https://github.com/microsoft/TypeScript/issues/30680#issuecomment-752725353

Is the underlying use case here the same as #30680?  I would think you'd rather see SourceCode({type: "Statement"}) have "Statement" be inferred as a string literal type.  Or would you really prefer an error like:
type Specification = { readonly type: string; };

function SourceNode<T extends (string extends T["type"] ?
  { readonly type: "OH NOES YOU FORGOT as const" } : Specification)>(props: T) {
  return { ...props }; // simplified to show a reduction.
};

export const BadStatement = SourceNode({
  type: "Statement" // error, Type '"Statement"' is not assignable to type '"OH NOES YOU FORGOT as const"'.
});

export const Statement = SourceNode({
  type: "Statement" // okay
} as const);

I suppose if someone writes SourceNode(somethingCreatedEarlier) then any chance of inferring something narrower is gone, at which point you'd maybe still want an error.  If so you can probably do something like this yourself, at least as a workaround until and unless this feature is implemented:
// I don't know, something like this
type Const<T> = T extends object ? { readonly [K in keyof T]: Const<T[K]> } :
  T extends number ? number extends T ? 0 : T :
  T extends string ? string extends T ? "" : T : T;

function foo<T>(x: Const<T>) { }

const oops = [123]
foo(oops) // error, number[] not assignable to readonly 0[]

const okay = [123] as const;
foo(okay) // okay

Playground link

I'm not 100% clear on what the thing being asked for is - if you wrote
let s = "ok".
SourceNode({ type: s } as const);

then the implicit contract is violated while the syntactic one is met. Conversely you could write
const s: { type: "statement } = { type : "statement" };
SourceNode(s);

and the implicit contract is met while the syntactic one is violated.
Programming languages generally don't create constructs that forbid indirection - I don't think we'd ever add something that says that the syntactic form you pass to a function has to be a particular thing. Framework-specific linters do exist (e.g. React's hooks lint) and might be more appropriate.

Programming languages generally don't create constructs that forbid indirection

In some sense, I am kind of trying to write a syntax construct, and thus the lack of indirection would be fine, "the same way" you can't do import pathVariable, and are instead forced to use a string literal with import statements. I am attempting to make a class factory, so I wish I could just do SourceNode Statement { }...

I'm not 100% clear on what the thing being asked for is - if you wrote

The responses above have actually been super helpful and given me plenty to experiment with. To get to the heart of the matter as to why I wouldn't just use a generic for this for example, is because it seems like any information I want to access both at runtime and type-check time needs to be expressed twice. I wish I could just treat exact strings kind of like in C++ templates:
type SourceNode<Name extends exact string> = class
{
    static type: Name = Name;
    type: Name = Name;
};

However, I can't (to my knowledge) assign a value to the value of an exact string (nor can I assign types to static members of course). But if the above was possible, I could avoid having to do something like:
class Statement extends SourceNode<"Statement">
{
    static type = "Statement"; // Ugh.
    type = "Statement";
}

My workaround is to have a class factory that piggy-backs off of this sort of literal type inference to have my cake and eat it too:
interface SourceNodeSpecification
{
  type: string;
};

const SourceNode = (specification: SourceNodeSpecification) =>
  class
  {
      static type = specification.type;
      type = specification.type;
  };

That way I can now do:
const Statement = SourceNode
({
    type: "Statement";
} as const);

function doStuff(node: Statement | Declaration)
{
    if (statement.type === "Statement")
    {
       // whatever.
    }
    else
    {
         // Must be a Declaration here...
    }
}

And then have all my nodes I instantiate have the correct type without having to pass in a string anywhere else in the program.

authors: RyanCavanaugh jcalz tolmasky whzx5byb


text:
Why tsc wont check type of references project

Why tsc wont check type of references project?
I think tsc should follow references projects and perform type checking of them.

It looks like this is a question rather than a bug report. This issue tracker is for tracking bugs and active work on TypeScript itself, rather than a general forum for programmers using TypeScript to get help or ask questions.
You can ask questions on sites like Stack Overflow. We are not able to provide one-on-one support on the issue tracker. Please read the issue template carefully - it has important information on what kinds of reports can be acted on here, as well as links to useful TypeScript resources. Thanks!

source: gharchive/issue

authors: RyanCavanaugh lovetingyuan

repo: microsoft/TypeScript

license_type: permissive

license_source: github-api


text:
Control flow for constructor properties

This is an experimental PR to use control flow analysis when determining the types of properties declared by this.xxx = ... assignments in constructors in .js files.
A propery is considered a constructor declared property when all declaration sites are this.xxx assignments, when no declaration sites have JSDoc type annotations, and when at least one declaration site is in the body of a class constructor. A constructor declared property has an evolving type determined by CFA in the body of the constructor that declares it. In all other contexts, the property has a declared type that is a union of the final assigned types at each return point from the constructor.
The PR currently only uses CFA for properties declared in class constructors. It needs to also cover constructor functions, but that requires attaching a returnFlowNode to function declarations (similar to what we do for constructor declarations). We may want to consider ways to reduce the overhead of that.
The baseline changes are all because constructor declared properties are now considered to have type any when they are assignment targets in the constructor body. This an effect of how CFA auto-typing works.
Fixes #37900.

@ahejlsberg do we have a test for the declaration emit of a property like this? afaik none of the cases in tests/cases/conformance/jsdoc/declarations/jsDeclarationsClasses.ts are complex enough to trigger this.

@weswigham Best I can tell there are several classes in that test that now have property types computed by CFA with no changes in baselines. I wouldn't expect any either since declaration emit just uses getTypeOfSymbol.

@typescript-bot user test this

@sandersn I'm looking at the user test suite baseline changes, and so far things seem reasonable. The increased precision of CFA causes more errors in places as expected, for example when CFA discovers that a property is conditionally (instead of definitely) initialized in the constructor.
The chrome-devtools errors are insanely hard to verify because there's no indentation in the code, but best I can tell they're to be expected.

I ran a before/after perf comparison of 10 runs of chrome-devtools-frontend, since it's a nice big code base with lots of functions.
Here's the average of 10 runs:
Before, time: 15.94 s
After, time: 16.21 s
1.66% slower.
Before, memory: 751.06 MB
After, memory: 757.27 MB
0.82% more memory.
Not that much difference actually.
(@ahejlsberg only one file in chrome-devtools-frontend is indentation-free, and it's a checked-in dependency. I always just skip that one.)

@typescript-bot user test this

@sandersn Fixed some over eager widening in auto-typed assignments. User test baselines now look good. More errors because we figure out more types, but the errors are to be expected and some of them actually reveal questionable logic.
I tried to get some perf numbers by running tsc on chrome-devtools-frontend but there is so much variability in the numbers that I can't really see any appreciable difference.

source: gharchive/pull-request

authors: ahejlsberg sandersn weswigham


text:
Emit error when trying to iterate a value with union type with non-iterable constituent when --downlevelIterator

Fixes #39161 .
Example
code
function getArrayOrUndefined() {
  return Math.random() > 0.5 ? [] : undefined;
}

const result = [...getArrayOrUndefined()];

{
  "compilerOptions": {
    "target": "es5",
    "lib": ["es2015"],
    "strict": true,
    "downlevelIteration": true
  }
}

Current Behavior
(no compile error)
New Behavior
src/index.ts:5:20 - error TS2548: Type 'never[] | undefined' is not an array type or does not have a '[Symbol.iterator]()' method that returns an iterator.

5 const result = [...getArrayOrUndefined()];
                     ~~~~~~~~~~~~~~~~~~~~~

Found 1 error.

Details of Code Change
This PR adds a shouldIgnoreNonIterableUnionConstituent parameter to getIterationTypesOfIterable which, if false is specified, returns noIterationTypes whenever given union type includes a non-iterable constituent. Otherwise, non-iterable constituents are just ignored; for example, the yielded type of number[] | undefined is considered number.
I first considered making this the default behavior, but then one test failed (namely generatorYieldContextualType.ts). As the old behavior seemed kind of reasonable in some situations, I kept the change smaller by adding that parameter.

@jakebailey Thank you very much for noticing this PR!
However, the issue seems to have already been fixed by #40350.
#39161 and this PR can now be closed.

Wow, clearly I didn't note the date, sorry about that!
I tested this manually, and yeah, this is fixed.

authors: jakebailey uhyo


text:
Experiment: Produce wide index signatures from the spread of an index signature

Fixes #56431
Related: https://github.com/microsoft/TypeScript/issues/27273 (does not change the behavior of dropping index signatures from the left side of a spread)
This would need a lot more test coverage if it proves viable but wanted to run the top repos first.

@typescript-bot perf test this
@typescript-bot run dt
@typescript-bot user test this
@typescript-bot test top200


text:
Fixing typos and grammar in base prompts

Fixed typos and grammar in base prompts
Re-phrased specific lines for coherence

@mosheber Thanks for checking these for us. Can you create a PR to pre-release branch first?

@mosheber Thanks for checking these for us. Can you create a PR to pre-release branch first?

sure thing!

authors: mosheber vyokky

repo: microsoft/UFO

license: MIT


text:
Error Code: 0x8015DC12

I got this error when installing any app or logging in to Xbox. I don't know what to do on that webpage.

Is this the right repository to report this issue? If not, then can you tell me which is the right repository?

repo: microsoft/WSL-DistroLauncher


text:
SO_REUSEPORT not supported on this platform. Exiting..

I am receiving this error on windows, how can I solve this issue?
thanks

/dupe #1419 for lack of template

authors: elekgeek therealkenc

repo: microsoft/WSL


text:
WSL connection to GPU disrupted without throwing error? nvidia-smi doesnt respond and doesnt time out.

Version
Microsoft Windows [Version 10.0.22000.708]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
510.16
Distro Version
Ubuntu 20.04
Other Software
Visual Studio Code 1.68.1 with WSL
nvidai-smi
Repro Steps

Open Windows Terminal (Ubuntu 20.04 shell)
Open python project with Visual Studio Code (cd my/python/project; code .)
Open integrated terminal and launch jupyter notebook jupyter-notebook
Run python program with PyTorch using CUDA / gpu
eventually iterations of training stop and jupyter environment is frozen (cant interupt or shut down kernel). Additional opening a new terminal shell and typing nvidia-smi results in nothing. It doesnt time out, it doesnt throw an error, it just waits. Further, opening another notebook (same jupyter notebook server) and running commands on cpu it runs fine. There are no screen tears, or any indication that it is a GPU error as the windows GUI is fine. Further it doesnt seem to be a memory issue (64gb ram, 24gb vram)

Expected Behavior
That this doesnt occur? That the gpu still runs
Actual Behavior
See step 5 of repro steps
Diagnostic Logs
None.  dmesg | grep -i nvrm | head has nothing.

@benhillis  any idea?


text:
⚠⛓💥 Broken links - MS UI XAML repo: directory to controls is changed

Which version of the app?
WinUI 3 Gallery
Description
Looks like the repo uses a new structure: they added folder /src/ to the path:
https://github.com/microsoft/microsoft-ui-xaml/tree/winui3/release/1.6-stable/src/controls/dev/
Now, all links to "control source code" are broken.
P.S. what's the difference between the main branch?

Thanks jay-o-way for catching this!!
Some context:
The WinUI repo moved the actual controls source code to the main branch, as it should be. Before that, the code was in specific release branches. As a result, we had to link to each source code file from within the Gallery.
Now that all the stable code lives in main, we can directly link to that.

repo: microsoft/WinUI-Gallery


text:
Speech Recognition issues on Xbox

I can run the SpeechRecognitionAndSynthesis sample app with no problems on Win10 but when running on Xbox I notice two issues:

Scenarios 4, 5 and 8 produce the message "The speech recognition privacy settings have not been accepted. Open Privacy Settings to review the privacy policy and enable personalization." which takes you to the App Privacy settings but the Speech option is no longer there (I suspect it was removed at the same time as Cortana?).

The other scenarios 6-11 either fail with an unknown error or immediately go to Idle state. I suspect it it because of the permissions required for option 1.

Are you able to run this app on Xbox and is there a workaround for accepting the privacy permission such as using the online Xbox privacy settings?
Note that the Features Not Yet Supported on Xbox doc says that Windows.ApplicationModel.VoiceCommands is not supported but this sample code does not use it. It does not mention Windows.Media.SpeechRecognition.

Why you don't asking it on https://forums.xboxlive.com/ ?

@Djm00n, I posted the issue here because this Windows-universal-sample is not working on one of the UWP supported platforms.  With all respect, I doubt the folks over at https://forums.xboxlive.com/  would know how to get a UWP sample app to work.
I would like the MSFT team to tell me if they can replicate what I am seeing or maybe there is something special users have to do now to enable speech (that is not documented) on Xbox.
Thank you.

I have asked the feature team to investigate.

Do you have an update please? I have the voice recognition feature disabled in the Xbox version of the app and would like to be able to turn it on.
Thank you!

@oldnewthing were you able to speak to the feature team about this? Is there a workaround to allow users to accept the privacy settings in the app (similar to what they do for MS Graph) since Cortana has been discontinued on Xbox?
I have a new release coming out soon and would really like to enable this functionality for Xbox users. Please let me know?

@LDS2020 The ticket on the feature team is still open. I have reminded them that a customer is waiting.

Captain’s log, The year is 2023! We have yet been able to have a solid resolve for set problem listed from so long ago. It’s desolate this far out. Some of the crew still maintain hope that this is will be resolved but others have lost all hope! Are we all abandoned from this resolve? It’s hard to stay optimistic but we will stand strong in hopes. That one day, someone will come through and save us all from the isolation of a question with no answer.

repo: microsoft/Windows-universal-samples


text:
A MenuFlyout with ToggleMenuFlyoutItems and MenuFlyoutSeparator has padding for icons/glyphs

Describe the bug

A MenuFlyout with ToggleMenuflyoutItems and MenuFlyoutSeparator has padding for icons/glyphs
Steps to reproduce the bug

Steps to reproduce the behavior:

Go to MenuFlyout
Click on "Options" under "A MenuFlyout with ToggleMenuflyoutItems and MenuFlyoutSeparator has padding for icons/glyphs"

Expected behavior

Actual behavior

Screenshots

Version Info

Gallery version (found on Settings page):
1.2.8.0
Windows 10 version:

[ ] Insider Build (xxxxx)
[x] May 2019 Update (18362)
[ ] October 2018 Update (17763)
[ ] April 2018 Update (17134)
[ ] Fall Creators Update (16299)
[ ] Creators Update (15063)
[ ] Anniversary Update (14393)

Device form factor:

[x] Desktop
[ ] Mobile
[ ] Xbox
[ ] Surface Hub
[ ] IoT

Additional context

The reason for the space is that the Repeat and Shuffle options can be toggled on. It looks strange when they are both toggled off, but here's what it looks like when one of them is toggled on:

This could be made clearer if the app had one of the items checked by default. This should be a quick fix so I'll keep this issue open to track that work.

I've updated the sample to have the items checked by default, which should hopefully make the reason for the "gap" more apparent. Thank you for reporting this @Poopooracoocoo

Thanks! :D

authors: Poopooracoocoo stmoy

repo: microsoft/Xaml-Controls-Gallery


text:
AFE frequent crashes when trying to open the lambda editor

I am not sure if something has changed recently, but recently it is a lottery if my lambda editor make it through the initial load. It ends up crashing the whole excel and all open excel window close.

is it a known issue?
is there any workaround to it? I don't care making it slower or downgrading it, just want to continue doing my job.

It seems that clearing the Office cache has helped: Excel Options -> Save -> Cache Settings -> Delete cached files
No issue for now.

repo: microsoft/advanced-formula-environment


text:
ld: library not found for -lPods when running in XCode using Ionic

Description
I installed the plugins per the installation instructions, did ionic cordova prepare ios and run in XCode I get a build error - ld: library not found for -lPods

Repro Steps
Please list the steps used to reproduce your issue.

Create blank Ionic app.
Do cordova platform add ios@5.0.0
Follow steps at https://docs.microsoft.com/en-us/appcenter/sdk/getting-started/cordova

Details

Which SDK version are you using?

Followed steps at https://docs.microsoft.com/en-us/appcenter/sdk/getting-started/cordova

Which OS version did you experience the issue on?

n/a

What version of Cordova, Cordova platforms, Cocoapods, and Ruby are you using?

Cordova 8.1.2, Cocoapods 1.7.5, Ruby 2.3.7p45

Hey, @daviddickson, thanks for getting in touch!
Can you tell me, which file are you opening in XCode? It looks like you are opening xcodeproj file, is that correct?

Correct.
On Thu, Aug 8, 2019 at 11:27 AM Dmitrii Chichuk notifications@github.com
wrote:

Hey, @daviddickson https://github.com/daviddickson, thanks for getting
in touch!
Can you tell me, which file are you opening in XCode? It looks like you
are opening xcodeproj file, is that correct?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/appcenter-sdk-cordova/issues/103?email_source=notifications&email_token=AAQDIVWR4RXGI4HPONE2J73QDQ3PDA5CNFSM4IKDKDP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD337QJY#issuecomment-519567399,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAQDIVWTK6EVBESV4MR3C53QDQ3PDANCNFSM4IKDKDPQ
.

@daviddickson CocoaPods generates .xcworkspace. It should be used instead of the .xcodeproj file.

authors: Jamminroot MatkovIvan daviddickson

repo: microsoft/appcenter-sdk-cordova


text:
Azure Container App does not scale down to zero with Service Bus Queue KEDA rule

This issue is a:

[x] bug report -> please search issues before submitting
[ ] documentation issue or request
[ ] regression (a behavior that used to work and stopped in a new release)

Issue description
I have deployed an Azure Container App configured with a scaling range of 0/10, designed to be triggered by a Dapr service bus queue inbound binding component. Messages that come into the service bus queue are being picked up successfully, but when I have no messages for the cooldown period (300 seconds), the container does not scale back to 0 but remains in the running state.
Steps to reproduce

Create a container app with a Dapr service bus queue component

Set KEDA rule with the following settings:

Scale the App to 0/10

Send one message and wait

Expected behavior [What you expected to happen.]
The container should activate when there is a message in the service bus and scale down to zero when there are no messages within the Azure Service Bus queue for the cooldown period (300 seconds).
Actual behavior [What actually happened.]
The App is not scaled down to zero, it remains running.

Hi, it looks like the Service Bus connections info in Authentication has the wrong parameter name. It should be "connection". Could you help to update it and try again?
Ref: https://keda.sh/docs/2.12/scalers/azure-service-bus/#authentication-parameters

I have updated the parameter name to "connection" but still one replica remains running.

I was running into the same issue. In the scaling rule, I used a (container app) secret that was a key vault reference.
After changing it to not use a secret from key vault but just a container app secret, the scaling started working again.

Although this solves the issue, using key vault references for the scaling rules should be possible in my opinion.

Changing the key to a "Container Apps Secret" did the job. After the cooldown period (5 minutes) it scales down to zero replicas.

authors: CeyssensStef SpiritZhou tino-github

repo: microsoft/azure-container-apps


text:
Error

I am getting following error in the Release pipeline.
2020-04-10T22:35:29.8370293Z ##[section]Starting: Result : Scale test
2020-04-10T22:35:29.8378819Z ==============================================================================
2020-04-10T22:35:29.8379194Z Task         : Email Report
2020-04-10T22:35:29.8379551Z Description  : Send rich email report for test results and for tasks in this stage
2020-04-10T22:35:29.8379895Z Version      : 1.1.8
2020-04-10T22:35:29.8380171Z Author       : Microsoft Corporation
2020-04-10T22:35:29.8381713Z Help         : Sets 'EmailReportTask.EmailSent' variable to true if it sent email successfully. Learn More
2020-04-10T22:35:29.8382423Z ==============================================================================
2020-04-10T22:35:29.8478866Z ##[error]File not found: '/home/vsts/work/_tasks/EmailReport_36fd41b1-8024-4ce9-a5a0-53c3e54ed105/1.1.8/Index.js'
2020-04-10T22:35:29.8483248Z ##[section]Finishing: Result : Sparta Scale test within vnet

Have the same error. 👎

Me as well

me too
any update?

From the extension install history,
we have Email Report Extension version 1.1.7 & 1.1.9 installed, but not 1.1.8
where is the 1.1.8 come from?

same issue.

also having the same issue - is there any known solution?

Any update, I'm also getting same error or any other plugin which we can use.

+1 same issue.

this is a problem with the "i" in "index"...it has been reported several times.
cannot be bothered to wait for Microsoft to fix this one, I am using now my own extension:
https://marketplace.visualstudio.com/items?itemName=calrom-jtejero.CalromEmailReportExtension
the code is in my fork:
https://github.com/calrom-jtejero/azure-devops-engineering-extensions

CalromEmailReportExtension

Thank you for takin

this is a problem with the "i" in "index"...it has been reported several times.
cannot be bothered to wait for Microsoft to fix this one, I am using now my own extension: https://marketplace.visualstudio.com/items?itemName=calrom-jtejero.CalromEmailReportExtension
the code is in my fork: https://github.com/calrom-jtejero/azure-devops-engineering-extensions
hope this helps you all

Thank you very much for your time and work!

@calrom-jtejero

this is a problem with the "i" in "index"...it has been reported several times.
cannot be bothered to wait for Microsoft to fix this one, I am using now my own extension: https://marketplace.visualstudio.com/items?itemName=calrom-jtejero.CalromEmailReportExtension
the code is in my fork: https://github.com/calrom-jtejero/azure-devops-engineering-extensions
hope this helps you all

I am still not able to get it working. I am getting below error in the pipeline:
(node:668) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): MailError: Error: Message failed: 550 MIME message is missing 'From' header
Below is how my pipeline looks:
      - task: VSTest@2
        displayName: "Run Tests"
        env:
          BaseUrl: $(BaseUrl)
          BROWSER_TYPE: ${{ upper(parameters.webBrowser) }}
          HEADLESS_MODE: ${{ parameters.headlessMode }}
          OS1_Accountant_EMAIL: $(OS1_Accountant_EMAIL)
          OS2_Accountant_EMAIL: $(OS2_Accountant_EMAIL)
          OS1_Client_EMAIL: $(OS1_Client_EMAIL)
          OS1_Client_EMAIL2: $(OS1_Client_EMAIL2)
          OS2_Client_EMAIL: $(OS2_Client_EMAIL)
          OS2_Client_EMAIL2: $(OS2_Client_EMAIL2)
          OS1_Client_PASSWORD: $(clientospassword)
          OS2_Client_PASSWORD: $(clientospassword)
          OS1_Accountant_PASSWORD: $(accountantospassword)
          OS2_Accountant_PASSWORD: $(accountantospassword)
          TakeScreenShots: ${{ parameters.takeScreenshots }}
        inputs:
          testSelector: "testAssemblies"
          testAssemblyVer2: |
            **\OpenSpaceAutomation.dll
            !**\*TestAdapter.dll
            !**\obj\**
          searchFolder: $(Pipeline.Workspace)/Solution/
          testFiltercriteria: "TestCategory=${{ parameters.tags }}"
          runInParallel: true
          batchingBasedOnAgentsOption: "customBatchSize"
          customBatchSizeValue: "1000"
          rerunFailedTests: true
          rerunFailedThreshold: "70"
          publishLocation: "pipeline"
          publishtestResults: true

      - task: CalromEmailReport@1
        inputs:
          sendMailConditionConfig: 'Always'
          subject: '[{environmentStatus}] {passPercentage} tests passed in $(Release.EnvironmentName) stage for $(Build.BuildNumber)'
          toAddress: 'ashish.bhatt@gmail.com'
          defaultDomain: 'xyz.co.uk'
          groupTestResultsBy: 'run'
          includeCommits: true
          maxTestFailuresToShow: '15'
          includeOthersInTotal: true
          usePreviousEnvironment: true
          smtpConnectionEndpoint: 'sendgrid-smtp'

authors: Incarnation-p-lee SunnyOswal Tom4U anjuligoring ashishbhatt-afk bharatrakhi calrom-jtejero movergan sabjarka seetuaccn wang-songbo


text:
how to add sequence provisioning in the task AzureVmssDeploymentTask

Note
Issues in this repo are for tracking bugs, feature requests and questions for the tasks in this repo
For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
If you have an issue or request for the Azure Pipelines service, use developer community instead:
https://developercommunity.visualstudio.com/spaces/21/index.html )
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Feature/Bug
Enter Task Name: AzureVmssDeploymentTask
list here (V# not needed):
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
Environment

Server - Azure Pipelines

Issue Description
How do we add the extension sequence for the vm scale set?
In my scenario we have antimalware extension which supposed to run the before the custom script extension, when i trigger the deployment through the pipeline it works i add the antimalware extension and then will add the custom script extension task.
Im facing issue when i reimage the vmss from the portal, it doesnt guarantee that the custom script runs after the antimalware.
Is there any provision to send the extension sequencing through the pipeline?

Extension sequencing for VM Scale set can be achieved via multiple method. Read HERE
You can try the Template one while creating the VM scale set for the first time. This might retain the sequence even when you try to reimage.
I would also advice you to ask the Azure VM/Compute team for how sequencing can be achieved. I am thus closing this issue, as it seem to be much of a knowledge ask from Azure VM/Compute team.

authors: hiyadav vinothinidharmaraj

repo: microsoft/azure-pipelines-tasks


text:
Error: 'subscriptionId' cannot be null

Required Information
Question, Bug, or Feature?
Type: Bug?
Enter Task Name: AzureFunctionAppV1 and AzureRmWebAppDeploymentV4
Environment

Server - Azure Pipelines

If using Azure Pipelines, provide the account name, team project name, build definition name/build number: not specific to our environment....

Agent - Hosted

If using Hosted agent, provide agent queue name: Azure Pipelines

Issue Description
When using the two mentioned tasks to deploy a WebApp/FunctionApp we get the error: "'subscriptionId' cannot be null" when using a Management Group Service connection. Checking the code both tasks don't support the subscriptionId yet. Using the tasks with the normal Subscription Level Service connection works fine.
Task logs
##[error]Error: 'subscriptionId' cannot be null.
Error logs
##[error]Error: 'subscriptionId' cannot be null.

Can you explain your scenario, why do you need management group service connection for these tasks?

@Paxilein management group service connection will not work for deploying to a web app. When creating managment group service connection you do not provide a subscription id but for deploying to resources like a web app, we need to have the subscription id.

@arjgupta Yes, that's why I opened the issue... To have that feature of adding the SubscriptionId to the Task, like other tasks already have...
@AmrutaKawade Well, my scenario is that my Azure-Access-Manager does give me the Management Group Service Connection and tells me to use it wherever possible...

This issue SHOULD not be closed. Considering that more tasks receive this capability (of using a Management Group scoped service connection) by using the subscription Id parameter (e.g. the AzureCLI@2 etc., the AzureResourceManagerTemplateDeployment@3 task etc.), not having the ability of passing in a subscriptionId parameter makes this task less flexible and incompatible with the rest of the pipeline using Management Group scoped service conenctions.

No Clue why this issue is closed. What is the constraint to not be able to use the AzureKeyVault task with a Management Group scoped service connection?

This issue SHOULD not be closed. Considering that more tasks receive this capability (of using a Management Group scoped service connection) by using the subscription Id parameter (e.g. the AzureCLI@2 etc., the AzureResourceManagerTemplateDeployment@3 task etc.), not having the ability of passing in a subscriptionId parameter makes this task less flexible and incompatible with the rest of the pipeline using Management Group scoped service conenctions.

running into the same error here, need to deploy function app through management group level service connection.
disappointing to see this issue is closed without resolution :(

thanks for opening-up again @v-saikumart.
working around this issue now by using a command line deploy, but specifically deploying the app settings is a PITA.
would love to use AzureFunctionAppV1 / *vNext to do the trick with management group level service connections,
like we used to do with subscription level service connections.

Seeing the same error when using an AzureKeyVault@2 task with a management group scoped service connection. Would be great if we could get the ability to specify a subscription ID as a parameter for tasks.

The ability to use a service connection with a Management Group scope for tasks like AzureAppServiceManage would be reallyt good for flexibility and efficiency in managing deployments across different environments and subscriptions. The suggestion to enable the passing of a subscription ID parameter to these tasks, to make them compatible with Management Group scoped service connections, is a valid and necessary enhancement.

At the very least, some sane error message with a link to some explanation should be provided. It's how useless and misleading the current message is

authors: AmrutaKawade CARLOSMECK Paxilein arjgupta iamalexmang jboeshart kekovski msterin pmooij


text:
npm exited with non-zero code: 4294963238

Note
Issues in this repo are for tracking bugs, feature requests and questions for the tasks in this repo
npm exited with non-zero code: 4294963238
Error: npm exited with non-zero code: 4294963238
at ChildProcess.completionListener (C:\Users\Admin\AppData\Roaming\npm\node_modules\expo-cli\node_modules@expo\spawn-async\src\spawnAsync.ts:65:13)
at Object.onceWrapper (events.js:422:26)
at ChildProcess.emit (events.js:315:20)
at ChildProcess.cp.emit (C:\Users\Admin\AppData\Roaming\npm\node_modules\expo-cli\node_modules\cross-spawn\lib\enoent.js:34:29)
at maybeClose (internal/child_process.js:1048:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
...
at Object.spawnAsync [as default] (C:\Users\Admin\AppData\Roaming\npm\node_modules\expo-cli\node_modules@expo\spawn-async\src\spawnAsync.ts:26:19)
at NpmPackageManager._runAsync (C:\Users\Admin\AppData\Roaming\npm\node_modules\expo-cli\node_modules@expo\package-manager\src\NodePackageManagers.ts:157:31)
at NpmPackageManager.addAsync (C:\Users\Admin\AppData\Roaming\npm\node_modules\expo-cli\node_modules@expo\package-manager\src\NodePackageManagers.ts:100:18)
at installAsync (C:\Users\Admin\AppData\Roaming\npm\node_modules\expo-cli\src\commands\install.ts:129:3)
at Command. (C:\Users\Admin\AppData\Roamin
For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
If you have an issue or request for the Azure Pipelines service, use developer community instead:
https://developercommunity.visualstudio.com/spaces/21/index.html )
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: here
Enter Task Name: here
list here (V# not needed):
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
Environment

Server - Azure Pipelines or TFS on-premises?

If using TFS on-premises, provide the version:

If using Azure Pipelines, provide the account name, team project name, build definition name/build number:

Agent - Hosted or Private:

If using Hosted agent, provide agent queue name:

If using private agent, provide the OS of the machine running the agent and the agent version:

Issue Description
[Include task name(s), screenshots and any other relevant details]
Task logs
[Enable debug logging and please provide the zip file containing all the logs for a speedy resolution]
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
[Insert error from the logs here for a quick overview]

please provide more details on scenario for better understanding the issue

please provide more details on scenario for better understanding the issue


text:
[BUG]: NodeTool@0 Version 18.x results in a 404

Task name
NodeTool
Task version
0
Environment type (Please select at least one enviroment where you face this issue)

[X] Self-Hosted
[ ] Microsoft Hosted
[ ] VMSS Pool
[ ] Container

Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Windows Server 2019 1809
Task log
2023-03-16T10:33:21.5870388Z ##[debug]Evaluating condition for step: 'Install Node.js'
2023-03-16T10:33:21.5872870Z ##[debug]Evaluating: SucceededNode()
2023-03-16T10:33:21.5873449Z ##[debug]Evaluating SucceededNode:
2023-03-16T10:33:21.5874689Z ##[debug]=> True
2023-03-16T10:33:21.5875321Z ##[debug]Result: True
2023-03-16T10:33:21.5875880Z ##[section]Starting: Install Node.js
2023-03-16T10:33:21.5989656Z ==============================================================================
2023-03-16T10:33:21.5990050Z Task         : Node.js tool installer
2023-03-16T10:33:21.5990274Z Description  : Finds or downloads and caches the specified version spec of Node.js and adds it to the PATH
2023-03-16T10:33:21.5990605Z Version      : 0.213.0
2023-03-16T10:33:21.5990824Z Author       : Microsoft Corporation
2023-03-16T10:33:21.5991049Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/tool/node-js
2023-03-16T10:33:21.5991337Z ==============================================================================
2023-03-16T10:33:21.6706380Z ##[debug]Using node path: D:\DevOps\agent3\externals\node16\bin\node.exe
2023-03-16T10:33:21.7894947Z ##[debug]agent.TempDirectory=D:\DevOps\agent3\_work\_temp
2023-03-16T10:33:21.7909919Z ##[debug]loading inputs and endpoints
2023-03-16T10:33:21.7914903Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_SYSTEMVSSCONNECTION_ACCESSTOKEN
2023-03-16T10:33:21.7927399Z ##[debug]loading ENDPOINT_AUTH_SCHEME_SYSTEMVSSCONNECTION
2023-03-16T10:33:21.7929736Z ##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION
2023-03-16T10:33:21.7931855Z ##[debug]loading INPUT_CHECKLATEST
2023-03-16T10:33:21.7933808Z ##[debug]loading INPUT_FORCE32BIT
2023-03-16T10:33:21.7935879Z ##[debug]loading INPUT_VERSIONSOURCE
2023-03-16T10:33:21.7938748Z ##[debug]loading INPUT_VERSIONSPEC
2023-03-16T10:33:21.7942082Z ##[debug]loading SECRET_SYSTEM_ACCESSTOKEN
2023-03-16T10:33:21.7947742Z ##[debug]loaded 8
2023-03-16T10:33:21.7952685Z ##[debug]Agent.ProxyUrl=undefined
2023-03-16T10:33:21.7953660Z ##[debug]Agent.CAInfo=undefined
2023-03-16T10:33:21.7954538Z ##[debug]Agent.ClientCert=undefined
2023-03-16T10:33:21.7955444Z ##[debug]Agent.SkipCertValidation=undefined
2023-03-16T10:33:21.8323004Z ##[debug]Agent.ProxyUrl=undefined
2023-03-16T10:33:21.8323844Z ##[debug]Agent.CAInfo=undefined
2023-03-16T10:33:21.8324537Z ##[debug]Agent.ClientCert=undefined
2023-03-16T10:33:21.8325425Z ##[debug]check path : D:\DevOps\agent3\_work\_tasks\NodeTool_31c75bbb-bcdf-4706-8d7c-4da6a1959bc2\0.213.0\node_modules\azure-pipelines-tool-lib\lib.json
2023-03-16T10:33:21.8329386Z ##[debug]adding resource file: D:\DevOps\agent3\_work\_tasks\NodeTool_31c75bbb-bcdf-4706-8d7c-4da6a1959bc2\0.213.0\node_modules\azure-pipelines-tool-lib\lib.json
2023-03-16T10:33:21.8331508Z ##[debug]system.culture=en-US
2023-03-16T10:33:21.8456449Z ##[debug]force32bit=false
2023-03-16T10:33:21.8459496Z ##[debug]check path : D:\DevOps\agent3\_work\_tasks\NodeTool_31c75bbb-bcdf-4706-8d7c-4da6a1959bc2\0.213.0\task.json
2023-03-16T10:33:21.8461074Z ##[debug]adding resource file: D:\DevOps\agent3\_work\_tasks\NodeTool_31c75bbb-bcdf-4706-8d7c-4da6a1959bc2\0.213.0\task.json
2023-03-16T10:33:21.8462548Z ##[debug]system.culture=en-US
2023-03-16T10:33:21.8470853Z ##[debug]versionSource=spec
2023-03-16T10:33:21.8472691Z ##[debug]versionSpec=18.x
2023-03-16T10:33:21.8473407Z ##[debug]versionFilePath=undefined
2023-03-16T10:33:21.8474746Z ##[debug]checkLatest=false
2023-03-16T10:33:21.8477966Z ##[debug]isExplicit: null
2023-03-16T10:33:21.8479321Z ##[debug]explicit? false
2023-03-16T10:33:21.8481157Z ##[debug]isExplicit: null
2023-03-16T10:33:21.8481875Z ##[debug]explicit? false
2023-03-16T10:33:21.8482569Z ##[debug]Agent.Version=2.217.2
2023-03-16T10:33:21.8483308Z ##[debug]Agent.ToolsDirectory=D:\DevOps\agent3\_work\_tool
2023-03-16T10:33:21.8489933Z ##[debug]evaluating 0 versions
2023-03-16T10:33:21.8490668Z ##[debug]match not found
2023-03-16T10:33:21.8491325Z ##[debug]isExplicit: null
2023-03-16T10:33:21.8491971Z ##[debug]explicit? false
2023-03-16T10:33:21.9339088Z ##[debug]cleaning: v19.8.1
2023-03-16T10:33:21.9340604Z ##[debug]cleaning: v19.8.0
2023-03-16T10:33:21.9341474Z ##[debug]cleaning: v19.7.0
2023-03-16T10:33:21.9342323Z ##[debug]cleaning: v19.6.1
2023-03-16T10:33:21.9343133Z ##[debug]cleaning: v19.6.0
2023-03-16T10:33:21.9343940Z ##[debug]cleaning: v19.5.0
2023-03-16T10:33:21.9344742Z ##[debug]cleaning: v19.4.0
2023-03-16T10:33:21.9345544Z ##[debug]cleaning: v19.3.0
2023-03-16T10:33:21.9346352Z ##[debug]cleaning: v19.2.0
2023-03-16T10:33:21.9347155Z ##[debug]cleaning: v19.1.0
2023-03-16T10:33:21.9347957Z ##[debug]cleaning: v19.0.1
2023-03-16T10:33:21.9348867Z ##[debug]cleaning: v19.0.0
2023-03-16T10:33:21.9350169Z ##[debug]cleaning: v18.15.0
2023-03-16T10:33:21.9352306Z ##[debug]cleaning: v18.14.2
2023-03-16T10:33:21.9353015Z ##[debug]cleaning: v18.14.1
2023-03-16T10:33:21.9353682Z ##[debug]cleaning: v18.14.0
2023-03-16T10:33:21.9354339Z ##[debug]cleaning: v18.13.0
2023-03-16T10:33:21.9355088Z ##[debug]cleaning: v18.12.1
2023-03-16T10:33:21.9356179Z ##[debug]cleaning: v18.12.0
2023-03-16T10:33:21.9357112Z ##[debug]cleaning: v18.11.0
2023-03-16T10:33:21.9357964Z ##[debug]cleaning: v18.10.0
2023-03-16T10:33:21.9359199Z ##[debug]cleaning: v18.9.1
2023-03-16T10:33:21.9360039Z ##[debug]cleaning: v18.9.0
2023-03-16T10:33:21.9360928Z ##[debug]cleaning: v18.8.0
2023-03-16T10:33:21.9361597Z ##[debug]cleaning: v18.7.0
2023-03-16T10:33:21.9362249Z ##[debug]cleaning: v18.6.0
2023-03-16T10:33:21.9362905Z ##[debug]cleaning: v18.5.0
2023-03-16T10:33:21.9363562Z ##[debug]cleaning: v18.4.0
2023-03-16T10:33:21.9364281Z ##[debug]cleaning: v18.3.0
2023-03-16T10:33:21.9364944Z ##[debug]cleaning: v18.2.0
2023-03-16T10:33:21.9365581Z ##[debug]cleaning: v18.1.0
2023-03-16T10:33:21.9366552Z ##[debug]cleaning: v18.0.0
2023-03-16T10:33:21.9367389Z ##[debug]cleaning: v17.9.1
2023-03-16T10:33:21.9368042Z ##[debug]cleaning: v17.9.0
2023-03-16T10:33:21.9368688Z ##[debug]cleaning: v17.8.0
2023-03-16T10:33:21.9369340Z ##[debug]cleaning: v17.7.2
2023-03-16T10:33:21.9370126Z ##[debug]cleaning: v17.7.1
2023-03-16T10:33:21.9370796Z ##[debug]cleaning: v17.7.0
2023-03-16T10:33:21.9371440Z ##[debug]cleaning: v17.6.0
2023-03-16T10:33:21.9372090Z ##[debug]cleaning: v17.5.0
2023-03-16T10:33:21.9372740Z ##[debug]cleaning: v17.4.0
2023-03-16T10:33:21.9373388Z ##[debug]cleaning: v17.3.1
2023-03-16T10:33:21.9374047Z ##[debug]cleaning: v17.3.0
2023-03-16T10:33:21.9374772Z ##[debug]cleaning: v17.2.0
2023-03-16T10:33:21.9375427Z ##[debug]cleaning: v17.1.0
2023-03-16T10:33:21.9376129Z ##[debug]cleaning: v17.0.1
2023-03-16T10:33:21.9376900Z ##[debug]cleaning: v17.0.0
2023-03-16T10:33:21.9377560Z ##[debug]cleaning: v16.19.1
2023-03-16T10:33:21.9378212Z ##[debug]cleaning: v16.19.0
2023-03-16T10:33:21.9378876Z ##[debug]cleaning: v16.18.1
2023-03-16T10:33:21.9379522Z ##[debug]cleaning: v16.18.0
2023-03-16T10:33:21.9380246Z ##[debug]cleaning: v16.17.1
2023-03-16T10:33:21.9380901Z ##[debug]cleaning: v16.17.0
2023-03-16T10:33:21.9381552Z ##[debug]cleaning: v16.16.0
2023-03-16T10:33:21.9382222Z ##[debug]cleaning: v16.15.1
2023-03-16T10:33:21.9382872Z ##[debug]cleaning: v16.15.0
2023-03-16T10:33:21.9383525Z ##[debug]cleaning: v16.14.2
2023-03-16T10:33:21.9384366Z ##[debug]cleaning: v16.14.1
2023-03-16T10:33:21.9385020Z ##[debug]cleaning: v16.14.0
2023-03-16T10:33:21.9385670Z ##[debug]cleaning: v16.13.2
2023-03-16T10:33:21.9386384Z ##[debug]cleaning: v16.13.1
2023-03-16T10:33:21.9387211Z ##[debug]cleaning: v16.13.0
2023-03-16T10:33:21.9387885Z ##[debug]cleaning: v16.12.0
2023-03-16T10:33:21.9388561Z ##[debug]cleaning: v16.11.1
2023-03-16T10:33:21.9389215Z ##[debug]cleaning: v16.11.0
2023-03-16T10:33:21.9390141Z ##[debug]cleaning: v16.10.0
2023-03-16T10:33:21.9390799Z ##[debug]cleaning: v16.9.1
2023-03-16T10:33:21.9391430Z ##[debug]cleaning: v16.9.0
2023-03-16T10:33:21.9392153Z ##[debug]cleaning: v16.8.0
2023-03-16T10:33:21.9392799Z ##[debug]cleaning: v16.7.0
2023-03-16T10:33:21.9393443Z ##[debug]cleaning: v16.6.2
2023-03-16T10:33:21.9394086Z ##[debug]cleaning: v16.6.1
2023-03-16T10:33:21.9396049Z ##[debug]cleaning: v16.6.0
2023-03-16T10:33:21.9397056Z ##[debug]cleaning: v16.5.0
2023-03-16T10:33:21.9397961Z ##[debug]cleaning: v16.4.2
2023-03-16T10:33:21.9398871Z ##[debug]cleaning: v16.4.1
2023-03-16T10:33:21.9399769Z ##[debug]cleaning: v16.4.0
2023-03-16T10:33:21.9400652Z ##[debug]cleaning: v16.3.0
2023-03-16T10:33:21.9401532Z ##[debug]cleaning: v16.2.0
2023-03-16T10:33:21.9402489Z ##[debug]cleaning: v16.1.0
2023-03-16T10:33:21.9403455Z ##[debug]cleaning: v16.0.0
2023-03-16T10:33:21.9404473Z ##[debug]cleaning: v15.14.0
2023-03-16T10:33:21.9405535Z ##[debug]cleaning: v15.13.0
2023-03-16T10:33:21.9406505Z ##[debug]cleaning: v15.12.0
2023-03-16T10:33:21.9407539Z ##[debug]cleaning: v15.11.0
2023-03-16T10:33:21.9408549Z ##[debug]cleaning: v15.10.0
2023-03-16T10:33:21.9409607Z ##[debug]cleaning: v15.9.0
2023-03-16T10:33:21.9410690Z ##[debug]cleaning: v15.8.0
2023-03-16T10:33:21.9411915Z ##[debug]cleaning: v15.7.0
2023-03-16T10:33:21.9413044Z ##[debug]cleaning: v15.6.0
2023-03-16T10:33:21.9414213Z ##[debug]cleaning: v15.5.1
2023-03-16T10:33:21.9415314Z ##[debug]cleaning: v15.5.0
2023-03-16T10:33:21.9416616Z ##[debug]cleaning: v15.4.0
2023-03-16T10:33:21.9417741Z ##[debug]cleaning: v15.3.0
2023-03-16T10:33:21.9418853Z ##[debug]cleaning: v15.2.1
2023-03-16T10:33:21.9419954Z ##[debug]cleaning: v15.2.0
2023-03-16T10:33:21.9421186Z ##[debug]cleaning: v15.1.0
2023-03-16T10:33:21.9423030Z ##[debug]cleaning: v15.0.1
2023-03-16T10:33:21.9425169Z ##[debug]cleaning: v15.0.0
2023-03-16T10:33:21.9426354Z ##[debug]cleaning: v14.21.3
2023-03-16T10:33:21.9427492Z ##[debug]cleaning: v14.21.2
2023-03-16T10:33:21.9428579Z ##[debug]cleaning: v14.21.1
2023-03-16T10:33:21.9430036Z ##[debug]cleaning: v14.21.0
2023-03-16T10:33:21.9431125Z ##[debug]cleaning: v14.20.1
2023-03-16T10:33:21.9432609Z ##[debug]cleaning: v14.20.0
2023-03-16T10:33:21.9433756Z ##[debug]cleaning: v14.19.3
2023-03-16T10:33:21.9434889Z ##[debug]cleaning: v14.19.2
2023-03-16T10:33:21.9436003Z ##[debug]cleaning: v14.19.1
2023-03-16T10:33:21.9436729Z ##[debug]cleaning: v14.19.0
2023-03-16T10:33:21.9437392Z ##[debug]cleaning: v14.18.3
2023-03-16T10:33:21.9438065Z ##[debug]cleaning: v14.18.2
2023-03-16T10:33:21.9438793Z ##[debug]cleaning: v14.18.1
2023-03-16T10:33:21.9439448Z ##[debug]cleaning: v14.18.0
2023-03-16T10:33:21.9440110Z ##[debug]cleaning: v14.17.6
2023-03-16T10:33:21.9440825Z ##[debug]cleaning: v14.17.5
2023-03-16T10:33:21.9441485Z ##[debug]cleaning: v14.17.4
2023-03-16T10:33:21.9442143Z ##[debug]cleaning: v14.17.3
2023-03-16T10:33:21.9442890Z ##[debug]cleaning: v14.17.2
2023-03-16T10:33:21.9443555Z ##[debug]cleaning: v14.17.1
2023-03-16T10:33:21.9444211Z ##[debug]cleaning: v14.17.0
2023-03-16T10:33:21.9444868Z ##[debug]cleaning: v14.16.1
2023-03-16T10:33:21.9445511Z ##[debug]cleaning: v14.16.0
2023-03-16T10:33:21.9446169Z ##[debug]cleaning: v14.15.5
2023-03-16T10:33:21.9446831Z ##[debug]cleaning: v14.15.4
2023-03-16T10:33:21.9447483Z ##[debug]cleaning: v14.15.3
2023-03-16T10:33:21.9448157Z ##[debug]cleaning: v14.15.2
2023-03-16T10:33:21.9448815Z ##[debug]cleaning: v14.15.1
2023-03-16T10:33:21.9449471Z ##[debug]cleaning: v14.15.0
2023-03-16T10:33:21.9450135Z ##[debug]cleaning: v14.14.0
2023-03-16T10:33:21.9450793Z ##[debug]cleaning: v14.13.1
2023-03-16T10:33:21.9451447Z ##[debug]cleaning: v14.13.0
2023-03-16T10:33:21.9452092Z ##[debug]cleaning: v14.12.0
2023-03-16T10:33:21.9452817Z ##[debug]cleaning: v14.11.0
2023-03-16T10:33:21.9453534Z ##[debug]cleaning: v14.10.1
2023-03-16T10:33:21.9454193Z ##[debug]cleaning: v14.10.0
2023-03-16T10:33:21.9454849Z ##[debug]cleaning: v14.9.0
2023-03-16T10:33:21.9455496Z ##[debug]cleaning: v14.8.0
2023-03-16T10:33:21.9456146Z ##[debug]cleaning: v14.7.0
2023-03-16T10:33:21.9456842Z ##[debug]cleaning: v14.6.0
2023-03-16T10:33:21.9457488Z ##[debug]cleaning: v14.5.0
2023-03-16T10:33:21.9458126Z ##[debug]cleaning: v14.4.0
2023-03-16T10:33:21.9458775Z ##[debug]cleaning: v14.3.0
2023-03-16T10:33:21.9459425Z ##[debug]cleaning: v14.2.0
2023-03-16T10:33:21.9460226Z ##[debug]cleaning: v14.1.0
2023-03-16T10:33:21.9460880Z ##[debug]cleaning: v14.0.0
2023-03-16T10:33:21.9461531Z ##[debug]cleaning: v13.14.0
2023-03-16T10:33:21.9462192Z ##[debug]cleaning: v13.13.0
2023-03-16T10:33:21.9462848Z ##[debug]cleaning: v13.12.0
2023-03-16T10:33:21.9463507Z ##[debug]cleaning: v13.11.0
2023-03-16T10:33:21.9464150Z ##[debug]cleaning: v13.10.1
2023-03-16T10:33:21.9464807Z ##[debug]cleaning: v13.10.0
2023-03-16T10:33:21.9465467Z ##[debug]cleaning: v13.9.0
2023-03-16T10:33:21.9466119Z ##[debug]cleaning: v13.8.0
2023-03-16T10:33:21.9466773Z ##[debug]cleaning: v13.7.0
2023-03-16T10:33:21.9521336Z ##[debug]cleaning: v13.6.0
2023-03-16T10:33:21.9522201Z ##[debug]cleaning: v13.5.0
2023-03-16T10:33:21.9522866Z ##[debug]cleaning: v13.4.0
2023-03-16T10:33:21.9523524Z ##[debug]cleaning: v13.3.0
2023-03-16T10:33:21.9524166Z ##[debug]cleaning: v13.2.0
2023-03-16T10:33:21.9528830Z ##[debug]cleaning: v13.1.0
2023-03-16T10:33:21.9529554Z ##[debug]cleaning: v13.0.1
2023-03-16T10:33:21.9530233Z ##[debug]cleaning: v13.0.0
2023-03-16T10:33:21.9530896Z ##[debug]cleaning: v12.22.12
2023-03-16T10:33:21.9531565Z ##[debug]cleaning: v12.22.11
2023-03-16T10:33:21.9532368Z ##[debug]cleaning: v12.22.10
2023-03-16T10:33:21.9533039Z ##[debug]cleaning: v12.22.9
2023-03-16T10:33:21.9533698Z ##[debug]cleaning: v12.22.8
2023-03-16T10:33:21.9534345Z ##[debug]cleaning: v12.22.7
2023-03-16T10:33:21.9535004Z ##[debug]cleaning: v12.22.6
2023-03-16T10:33:21.9576579Z ##[debug]cleaning: v12.22.5
2023-03-16T10:33:21.9577366Z ##[debug]cleaning: v12.22.4
2023-03-16T10:33:21.9578031Z ##[debug]cleaning: v12.22.3
2023-03-16T10:33:21.9578687Z ##[debug]cleaning: v12.22.2
2023-03-16T10:33:21.9579616Z ##[debug]cleaning: v12.22.1
2023-03-16T10:33:21.9580517Z ##[debug]cleaning: v12.22.0
2023-03-16T10:33:21.9581177Z ##[debug]cleaning: v12.21.0
2023-03-16T10:33:21.9581814Z ##[debug]cleaning: v12.20.2
2023-03-16T10:33:21.9582556Z ##[debug]cleaning: v12.20.1
2023-03-16T10:33:21.9583235Z ##[debug]cleaning: v12.20.0
2023-03-16T10:33:21.9583891Z ##[debug]cleaning: v12.19.1
2023-03-16T10:33:21.9584540Z ##[debug]cleaning: v12.19.0
2023-03-16T10:33:21.9585203Z ##[debug]cleaning: v12.18.4
2023-03-16T10:33:21.9585860Z ##[debug]cleaning: v12.18.3
2023-03-16T10:33:21.9586505Z ##[debug]cleaning: v12.18.2
2023-03-16T10:33:21.9587161Z ##[debug]cleaning: v12.18.1
2023-03-16T10:33:21.9587796Z ##[debug]cleaning: v12.18.0
2023-03-16T10:33:21.9588446Z ##[debug]cleaning: v12.17.0
2023-03-16T10:33:21.9589098Z ##[debug]cleaning: v12.16.3
2023-03-16T10:33:21.9589966Z ##[debug]cleaning: v12.16.2
2023-03-16T10:33:21.9597126Z ##[debug]cleaning: v12.16.1
2023-03-16T10:33:21.9597979Z ##[debug]cleaning: v12.16.0
2023-03-16T10:33:21.9598654Z ##[debug]cleaning: v12.15.0
2023-03-16T10:33:21.9599314Z ##[debug]cleaning: v12.14.1
2023-03-16T10:33:21.9600048Z ##[debug]cleaning: v12.14.0
2023-03-16T10:33:21.9600713Z ##[debug]cleaning: v12.13.1
2023-03-16T10:33:21.9601370Z ##[debug]cleaning: v12.13.0
2023-03-16T10:33:21.9602051Z ##[debug]cleaning: v12.12.0
2023-03-16T10:33:21.9602715Z ##[debug]cleaning: v12.11.1
2023-03-16T10:33:21.9603430Z ##[debug]cleaning: v12.11.0
2023-03-16T10:33:21.9604111Z ##[debug]cleaning: v12.10.0
2023-03-16T10:33:21.9604823Z ##[debug]cleaning: v12.9.1
2023-03-16T10:33:21.9605479Z ##[debug]cleaning: v12.9.0
2023-03-16T10:33:21.9606129Z ##[debug]cleaning: v12.8.1
2023-03-16T10:33:21.9606772Z ##[debug]cleaning: v12.8.0
2023-03-16T10:33:21.9607420Z ##[debug]cleaning: v12.7.0
2023-03-16T10:33:21.9608166Z ##[debug]cleaning: v12.6.0
2023-03-16T10:33:21.9608819Z ##[debug]cleaning: v12.5.0
2023-03-16T10:33:21.9609529Z ##[debug]cleaning: v12.4.0
2023-03-16T10:33:21.9610189Z ##[debug]cleaning: v12.3.1
2023-03-16T10:33:21.9610838Z ##[debug]cleaning: v12.3.0
2023-03-16T10:33:21.9611486Z ##[debug]cleaning: v12.2.0
2023-03-16T10:33:21.9612132Z ##[debug]cleaning: v12.1.0
2023-03-16T10:33:21.9612766Z ##[debug]cleaning: v12.0.0
2023-03-16T10:33:21.9613415Z ##[debug]cleaning: v11.15.0
2023-03-16T10:33:21.9614251Z ##[debug]cleaning: v11.14.0
2023-03-16T10:33:21.9614905Z ##[debug]cleaning: v11.13.0
2023-03-16T10:33:21.9615557Z ##[debug]cleaning: v11.12.0
2023-03-16T10:33:21.9616217Z ##[debug]cleaning: v11.11.0
2023-03-16T10:33:21.9616865Z ##[debug]cleaning: v11.10.1
2023-03-16T10:33:21.9617561Z ##[debug]cleaning: v11.10.0
2023-03-16T10:33:21.9618205Z ##[debug]cleaning: v11.9.0
2023-03-16T10:33:21.9618910Z ##[debug]cleaning: v11.8.0
2023-03-16T10:33:21.9619555Z ##[debug]cleaning: v11.7.0
2023-03-16T10:33:21.9620196Z ##[debug]cleaning: v11.6.0
2023-03-16T10:33:21.9620833Z ##[debug]cleaning: v11.5.0
2023-03-16T10:33:21.9621478Z ##[debug]cleaning: v11.4.0
2023-03-16T10:33:21.9622126Z ##[debug]cleaning: v11.3.0
2023-03-16T10:33:21.9622792Z ##[debug]cleaning: v11.2.0
2023-03-16T10:33:21.9623446Z ##[debug]cleaning: v11.1.0
2023-03-16T10:33:21.9624091Z ##[debug]cleaning: v11.0.0
2023-03-16T10:33:21.9624744Z ##[debug]cleaning: v10.24.1
2023-03-16T10:33:21.9625388Z ##[debug]cleaning: v10.24.0
2023-03-16T10:33:21.9626051Z ##[debug]cleaning: v10.23.3
2023-03-16T10:33:21.9626705Z ##[debug]cleaning: v10.23.2
2023-03-16T10:33:21.9627352Z ##[debug]cleaning: v10.23.1
2023-03-16T10:33:21.9628105Z ##[debug]cleaning: v10.23.0
2023-03-16T10:33:21.9628758Z ##[debug]cleaning: v10.22.1
2023-03-16T10:33:21.9629760Z ##[debug]cleaning: v10.22.0
2023-03-16T10:33:21.9630487Z ##[debug]cleaning: v10.21.0
2023-03-16T10:33:21.9631150Z ##[debug]cleaning: v10.20.1
2023-03-16T10:33:21.9631790Z ##[debug]cleaning: v10.20.0
2023-03-16T10:33:21.9632448Z ##[debug]cleaning: v10.19.0
2023-03-16T10:33:21.9633097Z ##[debug]cleaning: v10.18.1
2023-03-16T10:33:21.9633747Z ##[debug]cleaning: v10.18.0
2023-03-16T10:33:21.9634398Z ##[debug]cleaning: v10.17.0
2023-03-16T10:33:21.9635048Z ##[debug]cleaning: v10.16.3
2023-03-16T10:33:21.9635695Z ##[debug]cleaning: v10.16.2
2023-03-16T10:33:21.9636342Z ##[debug]cleaning: v10.16.1
2023-03-16T10:33:21.9636992Z ##[debug]cleaning: v10.16.0
2023-03-16T10:33:21.9637644Z ##[debug]cleaning: v10.15.3
2023-03-16T10:33:21.9638297Z ##[debug]cleaning: v10.15.2
2023-03-16T10:33:21.9638950Z ##[debug]cleaning: v10.15.1
2023-03-16T10:33:21.9639682Z ##[debug]cleaning: v10.15.0
2023-03-16T10:33:21.9640340Z ##[debug]cleaning: v10.14.2
2023-03-16T10:33:21.9640990Z ##[debug]cleaning: v10.14.1
2023-03-16T10:33:21.9641638Z ##[debug]cleaning: v10.14.0
2023-03-16T10:33:21.9642290Z ##[debug]cleaning: v10.13.0
2023-03-16T10:33:21.9642943Z ##[debug]cleaning: v10.12.0
2023-03-16T10:33:21.9643579Z ##[debug]cleaning: v10.11.0
2023-03-16T10:33:21.9644230Z ##[debug]cleaning: v10.10.0
2023-03-16T10:33:21.9644874Z ##[debug]cleaning: v10.9.0
2023-03-16T10:33:21.9645521Z ##[debug]cleaning: v10.8.0
2023-03-16T10:33:21.9646168Z ##[debug]cleaning: v10.7.0
2023-03-16T10:33:21.9646883Z ##[debug]cleaning: v10.6.0
2023-03-16T10:33:21.9647533Z ##[debug]cleaning: v10.5.0
2023-03-16T10:33:21.9648180Z ##[debug]cleaning: v10.4.1
2023-03-16T10:33:21.9648827Z ##[debug]cleaning: v10.4.0
2023-03-16T10:33:21.9649470Z ##[debug]cleaning: v10.3.0
2023-03-16T10:33:21.9650116Z ##[debug]cleaning: v10.2.1
2023-03-16T10:33:21.9650759Z ##[debug]cleaning: v10.2.0
2023-03-16T10:33:21.9651412Z ##[debug]cleaning: v10.1.0
2023-03-16T10:33:21.9652053Z ##[debug]cleaning: v10.0.0
2023-03-16T10:33:21.9652697Z ##[debug]cleaning: v9.11.2
2023-03-16T10:33:21.9653347Z ##[debug]cleaning: v9.11.1
2023-03-16T10:33:21.9653994Z ##[debug]cleaning: v9.11.0
2023-03-16T10:33:21.9654636Z ##[debug]cleaning: v9.10.1
2023-03-16T10:33:21.9655266Z ##[debug]cleaning: v9.10.0
2023-03-16T10:33:21.9655907Z ##[debug]cleaning: v9.9.0
2023-03-16T10:33:21.9656552Z ##[debug]cleaning: v9.8.0
2023-03-16T10:33:21.9657195Z ##[debug]cleaning: v9.7.1
2023-03-16T10:33:21.9657906Z ##[debug]cleaning: v9.7.0
2023-03-16T10:33:21.9658603Z ##[debug]cleaning: v9.6.1
2023-03-16T10:33:21.9659252Z ##[debug]cleaning: v9.6.0
2023-03-16T10:33:21.9659944Z ##[debug]cleaning: v9.5.0
2023-03-16T10:33:21.9660589Z ##[debug]cleaning: v9.4.0
2023-03-16T10:33:21.9661985Z ##[debug]cleaning: v9.3.0
2023-03-16T10:33:21.9662641Z ##[debug]cleaning: v9.2.1
2023-03-16T10:33:21.9663286Z ##[debug]cleaning: v9.2.0
2023-03-16T10:33:21.9663944Z ##[debug]cleaning: v9.1.0
2023-03-16T10:33:21.9664594Z ##[debug]cleaning: v9.0.0
2023-03-16T10:33:21.9665241Z ##[debug]cleaning: v8.17.0
2023-03-16T10:33:21.9665890Z ##[debug]cleaning: v8.16.2
2023-03-16T10:33:21.9667046Z ##[debug]cleaning: v8.16.1
2023-03-16T10:33:21.9667705Z ##[debug]cleaning: v8.16.0
2023-03-16T10:33:21.9668358Z ##[debug]cleaning: v8.15.1
2023-03-16T10:33:21.9669004Z ##[debug]cleaning: v8.15.0
2023-03-16T10:33:21.9669823Z ##[debug]cleaning: v8.14.1
2023-03-16T10:33:21.9670476Z ##[debug]cleaning: v8.14.0
2023-03-16T10:33:21.9671123Z ##[debug]cleaning: v8.13.0
2023-03-16T10:33:21.9671766Z ##[debug]cleaning: v8.12.0
2023-03-16T10:33:21.9672410Z ##[debug]cleaning: v8.11.4
2023-03-16T10:33:21.9673055Z ##[debug]cleaning: v8.11.3
2023-03-16T10:33:21.9673688Z ##[debug]cleaning: v8.11.2
2023-03-16T10:33:21.9674350Z ##[debug]cleaning: v8.11.1
2023-03-16T10:33:21.9674996Z ##[debug]cleaning: v8.11.0
2023-03-16T10:33:21.9675642Z ##[debug]cleaning: v8.10.0
2023-03-16T10:33:21.9676393Z ##[debug]cleaning: v8.9.4
2023-03-16T10:33:21.9677038Z ##[debug]cleaning: v8.9.3
2023-03-16T10:33:21.9677682Z ##[debug]cleaning: v8.9.2
2023-03-16T10:33:21.9678392Z ##[debug]cleaning: v8.9.1
2023-03-16T10:33:21.9679043Z ##[debug]cleaning: v8.9.0
2023-03-16T10:33:21.9679673Z ##[debug]cleaning: v8.8.1
2023-03-16T10:33:21.9680373Z ##[debug]cleaning: v8.8.0
2023-03-16T10:33:21.9681014Z ##[debug]cleaning: v8.7.0
2023-03-16T10:33:21.9681651Z ##[debug]cleaning: v8.6.0
2023-03-16T10:33:21.9682291Z ##[debug]cleaning: v8.5.0
2023-03-16T10:33:21.9682934Z ##[debug]cleaning: v8.4.0
2023-03-16T10:33:21.9683575Z ##[debug]cleaning: v8.3.0
2023-03-16T10:33:21.9684214Z ##[debug]cleaning: v8.2.1
2023-03-16T10:33:21.9684943Z ##[debug]cleaning: v8.2.0
2023-03-16T10:33:21.9685586Z ##[debug]cleaning: v8.1.4
2023-03-16T10:33:21.9686492Z ##[debug]cleaning: v8.1.3
2023-03-16T10:33:21.9687163Z ##[debug]cleaning: v8.1.2
2023-03-16T10:33:21.9687807Z ##[debug]cleaning: v8.1.1
2023-03-16T10:33:21.9688462Z ##[debug]cleaning: v8.1.0
2023-03-16T10:33:21.9689102Z ##[debug]cleaning: v8.0.0
2023-03-16T10:33:21.9689744Z ##[debug]cleaning: v7.10.1
2023-03-16T10:33:21.9690385Z ##[debug]cleaning: v7.10.0
2023-03-16T10:33:21.9691024Z ##[debug]cleaning: v7.9.0
2023-03-16T10:33:21.9691653Z ##[debug]cleaning: v7.8.0
2023-03-16T10:33:21.9692293Z ##[debug]cleaning: v7.7.4
2023-03-16T10:33:21.9692932Z ##[debug]cleaning: v7.7.3
2023-03-16T10:33:21.9693569Z ##[debug]cleaning: v7.7.2
2023-03-16T10:33:21.9694211Z ##[debug]cleaning: v7.7.1
2023-03-16T10:33:21.9694852Z ##[debug]cleaning: v7.7.0
2023-03-16T10:33:21.9695487Z ##[debug]cleaning: v7.6.0
2023-03-16T10:33:21.9696129Z ##[debug]cleaning: v7.5.0
2023-03-16T10:33:21.9696769Z ##[debug]cleaning: v7.4.0
2023-03-16T10:33:21.9697399Z ##[debug]cleaning: v7.3.0
2023-03-16T10:33:21.9698037Z ##[debug]cleaning: v7.2.1
2023-03-16T10:33:21.9698689Z ##[debug]cleaning: v7.2.0
2023-03-16T10:33:21.9699330Z ##[debug]cleaning: v7.1.0
2023-03-16T10:33:21.9699970Z ##[debug]cleaning: v7.0.0
2023-03-16T10:33:21.9700623Z ##[debug]cleaning: v6.17.1
2023-03-16T10:33:21.9701266Z ##[debug]cleaning: v6.17.0
2023-03-16T10:33:21.9701909Z ##[debug]cleaning: v6.16.0
2023-03-16T10:33:21.9702551Z ##[debug]cleaning: v6.15.1
2023-03-16T10:33:21.9703185Z ##[debug]cleaning: v6.15.0
2023-03-16T10:33:21.9703835Z ##[debug]cleaning: v6.14.4
2023-03-16T10:33:21.9704476Z ##[debug]cleaning: v6.14.3
2023-03-16T10:33:21.9705119Z ##[debug]cleaning: v6.14.2
2023-03-16T10:33:21.9705764Z ##[debug]cleaning: v6.14.1
2023-03-16T10:33:21.9706432Z ##[debug]cleaning: v6.14.0
2023-03-16T10:33:21.9707402Z ##[debug]cleaning: v6.13.1
2023-03-16T10:33:21.9708359Z ##[debug]cleaning: v6.13.0
2023-03-16T10:33:21.9709212Z ##[debug]cleaning: v6.12.3
2023-03-16T10:33:21.9710655Z ##[debug]cleaning: v6.12.2
2023-03-16T10:33:21.9711513Z ##[debug]cleaning: v6.12.1
2023-03-16T10:33:21.9712623Z ##[debug]cleaning: v6.12.0
2023-03-16T10:33:21.9713299Z ##[debug]cleaning: v6.11.5
2023-03-16T10:33:21.9713968Z ##[debug]cleaning: v6.11.4
2023-03-16T10:33:21.9714609Z ##[debug]cleaning: v6.11.3
2023-03-16T10:33:21.9715254Z ##[debug]cleaning: v6.11.2
2023-03-16T10:33:21.9715895Z ##[debug]cleaning: v6.11.1
2023-03-16T10:33:21.9716532Z ##[debug]cleaning: v6.11.0
2023-03-16T10:33:21.9717171Z ##[debug]cleaning: v6.10.3
2023-03-16T10:33:21.9717811Z ##[debug]cleaning: v6.10.2
2023-03-16T10:33:21.9718453Z ##[debug]cleaning: v6.10.1
2023-03-16T10:33:21.9719091Z ##[debug]cleaning: v6.10.0
2023-03-16T10:33:21.9719725Z ##[debug]cleaning: v6.9.5
2023-03-16T10:33:21.9720350Z ##[debug]cleaning: v6.9.4
2023-03-16T10:33:21.9720988Z ##[debug]cleaning: v6.9.3
2023-03-16T10:33:21.9721627Z ##[debug]cleaning: v6.9.2
2023-03-16T10:33:21.9722268Z ##[debug]cleaning: v6.9.1
2023-03-16T10:33:21.9722985Z ##[debug]cleaning: v6.9.0
2023-03-16T10:33:21.9723627Z ##[debug]cleaning: v6.8.1
2023-03-16T10:33:21.9724272Z ##[debug]cleaning: v6.8.0
2023-03-16T10:33:21.9724957Z ##[debug]cleaning: v6.7.0
2023-03-16T10:33:21.9725598Z ##[debug]cleaning: v6.6.0
2023-03-16T10:33:21.9726319Z ##[debug]cleaning: v6.5.0
2023-03-16T10:33:21.9726967Z ##[debug]cleaning: v6.4.0
2023-03-16T10:33:21.9727607Z ##[debug]cleaning: v6.3.1
2023-03-16T10:33:21.9728247Z ##[debug]cleaning: v6.3.0
2023-03-16T10:33:21.9728883Z ##[debug]cleaning: v6.2.2
2023-03-16T10:33:21.9729585Z ##[debug]cleaning: v6.2.1
2023-03-16T10:33:21.9730226Z ##[debug]cleaning: v6.2.0
2023-03-16T10:33:21.9730866Z ##[debug]cleaning: v6.1.0
2023-03-16T10:33:21.9731507Z ##[debug]cleaning: v6.0.0
2023-03-16T10:33:21.9732138Z ##[debug]cleaning: v5.12.0
2023-03-16T10:33:21.9732781Z ##[debug]cleaning: v5.11.1
2023-03-16T10:33:21.9733430Z ##[debug]cleaning: v5.11.0
2023-03-16T10:33:21.9734079Z ##[debug]cleaning: v5.10.1
2023-03-16T10:33:21.9734782Z ##[debug]cleaning: v5.10.0
2023-03-16T10:33:21.9735475Z ##[debug]cleaning: v5.9.1
2023-03-16T10:33:21.9736205Z ##[debug]cleaning: v5.9.0
2023-03-16T10:33:21.9737054Z ##[debug]cleaning: v5.8.0
2023-03-16T10:33:21.9738207Z ##[debug]cleaning: v5.7.1
2023-03-16T10:33:21.9756487Z ##[debug]cleaning: v5.7.0
2023-03-16T10:33:21.9757630Z ##[debug]cleaning: v5.6.0
2023-03-16T10:33:21.9758286Z ##[debug]cleaning: v5.5.0
2023-03-16T10:33:21.9759189Z ##[debug]cleaning: v5.4.1
2023-03-16T10:33:21.9759848Z ##[debug]cleaning: v5.4.0
2023-03-16T10:33:21.9760484Z ##[debug]cleaning: v5.3.0
2023-03-16T10:33:21.9761123Z ##[debug]cleaning: v5.2.0
2023-03-16T10:33:21.9761760Z ##[debug]cleaning: v5.1.1
2023-03-16T10:33:21.9762401Z ##[debug]cleaning: v5.1.0
2023-03-16T10:33:21.9763034Z ##[debug]cleaning: v5.0.0
2023-03-16T10:33:21.9763676Z ##[debug]cleaning: v4.9.1
2023-03-16T10:33:21.9764315Z ##[debug]cleaning: v4.9.0
2023-03-16T10:33:21.9764956Z ##[debug]cleaning: v4.8.7
2023-03-16T10:33:21.9765601Z ##[debug]cleaning: v4.8.6
2023-03-16T10:33:21.9766240Z ##[debug]cleaning: v4.8.5
2023-03-16T10:33:21.9766944Z ##[debug]cleaning: v4.8.4
2023-03-16T10:33:21.9767581Z ##[debug]cleaning: v4.8.3
2023-03-16T10:33:21.9768216Z ##[debug]cleaning: v4.8.2
2023-03-16T10:33:21.9768861Z ##[debug]cleaning: v4.8.1
2023-03-16T10:33:21.9769500Z ##[debug]cleaning: v4.8.0
2023-03-16T10:33:21.9770137Z ##[debug]cleaning: v4.7.3
2023-03-16T10:33:21.9770769Z ##[debug]cleaning: v4.7.2
2023-03-16T10:33:21.9771406Z ##[debug]cleaning: v4.7.1
2023-03-16T10:33:21.9772044Z ##[debug]cleaning: v4.7.0
2023-03-16T10:33:21.9772678Z ##[debug]cleaning: v4.6.2
2023-03-16T10:33:21.9773314Z ##[debug]cleaning: v4.6.1
2023-03-16T10:33:21.9773942Z ##[debug]cleaning: v4.6.0
2023-03-16T10:33:21.9774583Z ##[debug]cleaning: v4.5.0
2023-03-16T10:33:21.9775617Z ##[debug]cleaning: v4.4.7
2023-03-16T10:33:21.9776289Z ##[debug]cleaning: v4.4.6
2023-03-16T10:33:21.9777000Z ##[debug]cleaning: v4.4.5
2023-03-16T10:33:21.9777648Z ##[debug]cleaning: v4.4.4
2023-03-16T10:33:21.9778293Z ##[debug]cleaning: v4.4.3
2023-03-16T10:33:21.9778935Z ##[debug]cleaning: v4.4.2
2023-03-16T10:33:21.9780268Z ##[debug]cleaning: v4.4.1
2023-03-16T10:33:21.9780911Z ##[debug]cleaning: v4.4.0
2023-03-16T10:33:21.9781558Z ##[debug]cleaning: v4.3.2
2023-03-16T10:33:21.9782215Z ##[debug]cleaning: v4.3.1
2023-03-16T10:33:21.9782854Z ##[debug]cleaning: v4.3.0
2023-03-16T10:33:21.9783495Z ##[debug]cleaning: v4.2.6
2023-03-16T10:33:21.9784141Z ##[debug]cleaning: v4.2.5
2023-03-16T10:33:21.9784782Z ##[debug]cleaning: v4.2.4
2023-03-16T10:33:21.9785423Z ##[debug]cleaning: v4.2.3
2023-03-16T10:33:21.9786064Z ##[debug]cleaning: v4.2.2
2023-03-16T10:33:21.9786701Z ##[debug]cleaning: v4.2.1
2023-03-16T10:33:21.9787341Z ##[debug]cleaning: v4.2.0
2023-03-16T10:33:21.9787978Z ##[debug]cleaning: v4.1.2
2023-03-16T10:33:21.9788620Z ##[debug]cleaning: v4.1.1
2023-03-16T10:33:21.9789264Z ##[debug]cleaning: v4.1.0
2023-03-16T10:33:21.9790159Z ##[debug]cleaning: v4.0.0
2023-03-16T10:33:21.9790812Z ##[debug]cleaning: v0.12.18
2023-03-16T10:33:21.9791460Z ##[debug]cleaning: v0.12.17
2023-03-16T10:33:21.9792120Z ##[debug]cleaning: v0.12.16
2023-03-16T10:33:21.9792759Z ##[debug]cleaning: v0.12.15
2023-03-16T10:33:21.9793409Z ##[debug]cleaning: v0.12.14
2023-03-16T10:33:21.9794555Z ##[debug]cleaning: v0.12.13
2023-03-16T10:33:21.9795223Z ##[debug]cleaning: v0.12.12
2023-03-16T10:33:21.9795876Z ##[debug]cleaning: v0.12.11
2023-03-16T10:33:21.9796529Z ##[debug]cleaning: v0.12.10
2023-03-16T10:33:21.9797181Z ##[debug]cleaning: v0.12.9
2023-03-16T10:33:21.9797828Z ##[debug]cleaning: v0.12.8
2023-03-16T10:33:21.9798511Z ##[debug]cleaning: v0.12.7
2023-03-16T10:33:21.9799150Z ##[debug]cleaning: v0.12.6
2023-03-16T10:33:21.9799795Z ##[debug]cleaning: v0.12.5
2023-03-16T10:33:21.9800441Z ##[debug]cleaning: v0.12.4
2023-03-16T10:33:21.9801088Z ##[debug]cleaning: v0.12.3
2023-03-16T10:33:21.9801734Z ##[debug]cleaning: v0.12.2
2023-03-16T10:33:21.9802374Z ##[debug]cleaning: v0.12.1
2023-03-16T10:33:21.9803017Z ##[debug]cleaning: v0.12.0
2023-03-16T10:33:21.9803730Z ##[debug]cleaning: v0.11.16
2023-03-16T10:33:21.9804392Z ##[debug]cleaning: v0.11.15
2023-03-16T10:33:21.9805034Z ##[debug]cleaning: v0.11.14
2023-03-16T10:33:21.9805685Z ##[debug]cleaning: v0.11.13
2023-03-16T10:33:21.9806344Z ##[debug]cleaning: v0.11.12
2023-03-16T10:33:21.9806993Z ##[debug]cleaning: v0.11.11
2023-03-16T10:33:21.9807637Z ##[debug]cleaning: v0.11.10
2023-03-16T10:33:21.9808281Z ##[debug]cleaning: v0.11.9
2023-03-16T10:33:21.9808918Z ##[debug]cleaning: v0.11.8
2023-03-16T10:33:21.9809555Z ##[debug]cleaning: v0.11.7
2023-03-16T10:33:21.9810258Z ##[debug]cleaning: v0.11.5
2023-03-16T10:33:21.9810913Z ##[debug]cleaning: v0.11.3
2023-03-16T10:33:21.9811552Z ##[debug]cleaning: v0.11.2
2023-03-16T10:33:21.9812198Z ##[debug]cleaning: v0.11.1
2023-03-16T10:33:21.9812840Z ##[debug]cleaning: v0.11.0
2023-03-16T10:33:21.9813493Z ##[debug]cleaning: v0.10.48
2023-03-16T10:33:21.9814183Z ##[debug]cleaning: v0.10.47
2023-03-16T10:33:21.9814831Z ##[debug]cleaning: v0.10.46
2023-03-16T10:33:21.9815477Z ##[debug]cleaning: v0.10.45
2023-03-16T10:33:21.9816135Z ##[debug]cleaning: v0.10.44
2023-03-16T10:33:21.9816786Z ##[debug]cleaning: v0.10.43
2023-03-16T10:33:21.9817431Z ##[debug]cleaning: v0.10.42
2023-03-16T10:33:21.9818077Z ##[debug]cleaning: v0.10.41
2023-03-16T10:33:21.9818730Z ##[debug]cleaning: v0.10.40
2023-03-16T10:33:21.9819378Z ##[debug]cleaning: v0.10.39
2023-03-16T10:33:21.9820024Z ##[debug]cleaning: v0.10.38
2023-03-16T10:33:21.9820668Z ##[debug]cleaning: v0.10.37
2023-03-16T10:33:21.9821316Z ##[debug]cleaning: v0.10.36
2023-03-16T10:33:21.9821956Z ##[debug]cleaning: v0.10.35
2023-03-16T10:33:21.9822600Z ##[debug]cleaning: v0.10.34
2023-03-16T10:33:21.9823236Z ##[debug]cleaning: v0.10.33
2023-03-16T10:33:21.9823883Z ##[debug]cleaning: v0.10.32
2023-03-16T10:33:21.9824535Z ##[debug]cleaning: v0.10.31
2023-03-16T10:33:21.9825184Z ##[debug]cleaning: v0.10.30
2023-03-16T10:33:21.9825832Z ##[debug]cleaning: v0.10.29
2023-03-16T10:33:21.9826473Z ##[debug]cleaning: v0.10.28
2023-03-16T10:33:21.9827610Z ##[debug]cleaning: v0.10.27
2023-03-16T10:33:21.9828267Z ##[debug]cleaning: v0.10.26
2023-03-16T10:33:21.9828919Z ##[debug]cleaning: v0.10.25
2023-03-16T10:33:21.9829794Z ##[debug]cleaning: v0.10.24
2023-03-16T10:33:21.9831457Z ##[debug]cleaning: v0.10.23
2023-03-16T10:33:21.9832523Z ##[debug]cleaning: v0.10.22
2023-03-16T10:33:21.9833200Z ##[debug]cleaning: v0.10.21
2023-03-16T10:33:21.9833861Z ##[debug]cleaning: v0.10.20
2023-03-16T10:33:21.9834514Z ##[debug]cleaning: v0.10.19
2023-03-16T10:33:21.9835164Z ##[debug]cleaning: v0.10.18
2023-03-16T10:33:21.9835872Z ##[debug]cleaning: v0.10.17
2023-03-16T10:33:21.9836527Z ##[debug]cleaning: v0.10.16
2023-03-16T10:33:21.9837165Z ##[debug]cleaning: v0.10.15
2023-03-16T10:33:21.9837810Z ##[debug]cleaning: v0.10.14
2023-03-16T10:33:21.9838453Z ##[debug]cleaning: v0.10.13
2023-03-16T10:33:21.9839095Z ##[debug]cleaning: v0.10.12
2023-03-16T10:33:21.9839741Z ##[debug]cleaning: v0.10.11
2023-03-16T10:33:21.9840383Z ##[debug]cleaning: v0.10.10
2023-03-16T10:33:21.9841128Z ##[debug]cleaning: v0.10.9
2023-03-16T10:33:21.9841772Z ##[debug]cleaning: v0.10.8
2023-03-16T10:33:21.9842408Z ##[debug]cleaning: v0.10.7
2023-03-16T10:33:21.9843296Z ##[debug]cleaning: v0.10.6
2023-03-16T10:33:21.9843947Z ##[debug]cleaning: v0.10.5
2023-03-16T10:33:21.9844589Z ##[debug]cleaning: v0.10.4
2023-03-16T10:33:21.9845229Z ##[debug]cleaning: v0.10.3
2023-03-16T10:33:21.9845870Z ##[debug]cleaning: v0.10.2
2023-03-16T10:33:21.9846509Z ##[debug]cleaning: v0.10.1
2023-03-16T10:33:21.9847150Z ##[debug]cleaning: v0.10.0
2023-03-16T10:33:21.9847790Z ##[debug]cleaning: v0.9.12
2023-03-16T10:33:21.9848482Z ##[debug]cleaning: v0.9.11
2023-03-16T10:33:21.9849127Z ##[debug]cleaning: v0.9.10
2023-03-16T10:33:21.9849771Z ##[debug]cleaning: v0.9.9
2023-03-16T10:33:21.9850414Z ##[debug]cleaning: v0.9.8
2023-03-16T10:33:21.9851051Z ##[debug]cleaning: v0.9.7
2023-03-16T10:33:21.9851690Z ##[debug]cleaning: v0.9.6
2023-03-16T10:33:21.9852324Z ##[debug]cleaning: v0.9.5
2023-03-16T10:33:21.9852993Z ##[debug]cleaning: v0.9.4
2023-03-16T10:33:21.9853637Z ##[debug]cleaning: v0.9.3
2023-03-16T10:33:21.9854274Z ##[debug]cleaning: v0.9.2
2023-03-16T10:33:21.9854912Z ##[debug]cleaning: v0.9.1
2023-03-16T10:33:21.9855549Z ##[debug]cleaning: v0.9.0
2023-03-16T10:33:21.9856250Z ##[debug]cleaning: v0.8.28
2023-03-16T10:33:21.9856898Z ##[debug]cleaning: v0.8.26
2023-03-16T10:33:21.9857543Z ##[debug]cleaning: v0.8.25
2023-03-16T10:33:21.9858185Z ##[debug]cleaning: v0.8.24
2023-03-16T10:33:21.9858828Z ##[debug]cleaning: v0.8.23
2023-03-16T10:33:21.9859468Z ##[debug]cleaning: v0.8.22
2023-03-16T10:33:21.9860108Z ##[debug]cleaning: v0.8.21
2023-03-16T10:33:21.9860735Z ##[debug]cleaning: v0.8.20
2023-03-16T10:33:21.9861376Z ##[debug]cleaning: v0.8.19
2023-03-16T10:33:21.9862017Z ##[debug]cleaning: v0.8.18
2023-03-16T10:33:21.9862654Z ##[debug]cleaning: v0.8.17
2023-03-16T10:33:21.9863421Z ##[debug]cleaning: v0.8.16
2023-03-16T10:33:21.9864393Z ##[debug]cleaning: v0.8.15
2023-03-16T10:33:21.9865312Z ##[debug]cleaning: v0.8.14
2023-03-16T10:33:21.9866157Z ##[debug]cleaning: v0.8.13
2023-03-16T10:33:21.9866947Z ##[debug]cleaning: v0.8.12
2023-03-16T10:33:21.9867612Z ##[debug]cleaning: v0.8.11
2023-03-16T10:33:21.9868258Z ##[debug]cleaning: v0.8.10
2023-03-16T10:33:21.9868903Z ##[debug]cleaning: v0.8.9
2023-03-16T10:33:21.9869899Z ##[debug]cleaning: v0.8.8
2023-03-16T10:33:21.9870548Z ##[debug]cleaning: v0.8.7
2023-03-16T10:33:21.9871184Z ##[debug]cleaning: v0.8.6
2023-03-16T10:33:21.9871820Z ##[debug]cleaning: v0.8.5
2023-03-16T10:33:21.9872533Z ##[debug]cleaning: v0.8.4
2023-03-16T10:33:21.9873181Z ##[debug]cleaning: v0.8.3
2023-03-16T10:33:21.9873810Z ##[debug]cleaning: v0.8.2
2023-03-16T10:33:21.9874449Z ##[debug]cleaning: v0.8.1
2023-03-16T10:33:21.9875146Z ##[debug]cleaning: v0.8.0
2023-03-16T10:33:21.9875792Z ##[debug]cleaning: v0.7.12
2023-03-16T10:33:21.9876436Z ##[debug]cleaning: v0.7.11
2023-03-16T10:33:21.9877073Z ##[debug]cleaning: v0.7.10
2023-03-16T10:33:21.9877865Z ##[debug]cleaning: v0.7.9
2023-03-16T10:33:21.9878569Z ##[debug]cleaning: v0.7.8
2023-03-16T10:33:21.9879213Z ##[debug]cleaning: v0.7.7
2023-03-16T10:33:21.9879854Z ##[debug]cleaning: v0.7.6
2023-03-16T10:33:21.9880554Z ##[debug]cleaning: v0.7.5
2023-03-16T10:33:21.9881204Z ##[debug]cleaning: v0.7.4
2023-03-16T10:33:21.9881851Z ##[debug]cleaning: v0.6.21
2023-03-16T10:33:21.9882494Z ##[debug]cleaning: v0.6.20
2023-03-16T10:33:21.9883132Z ##[debug]cleaning: v0.6.19
2023-03-16T10:33:21.9883773Z ##[debug]cleaning: v0.6.18
2023-03-16T10:33:21.9884485Z ##[debug]cleaning: v0.6.17
2023-03-16T10:33:21.9885134Z ##[debug]cleaning: v0.6.16
2023-03-16T10:33:21.9885771Z ##[debug]cleaning: v0.6.15
2023-03-16T10:33:21.9886411Z ##[debug]cleaning: v0.6.14
2023-03-16T10:33:21.9887052Z ##[debug]cleaning: v0.6.13
2023-03-16T10:33:21.9887708Z ##[debug]evaluating 589 versions
2023-03-16T10:33:21.9888365Z ##[debug]matched: 18.15.0
2023-03-16T10:33:21.9889012Z ##[debug]isExplicit: 18.15.0
2023-03-16T10:33:21.9889667Z ##[debug]explicit? true
2023-03-16T10:33:21.9890312Z ##[debug]Agent.Version=2.217.2
2023-03-16T10:33:21.9891019Z ##[debug]Agent.ToolsDirectory=D:\DevOps\agent3\_work\_tool
2023-03-16T10:33:21.9891881Z ##[debug]checking cache: D:\DevOps\agent3\_work\_tool\node\18.15.0\x64
2023-03-16T10:33:21.9892697Z ##[debug]not found
2023-03-16T10:33:21.9893328Z ##[debug]cleaning: v18.15.0
2023-03-16T10:33:21.9893942Z ##[debug]
2023-03-16T10:33:21.9894637Z ##[debug]Agent.Version=2.217.2
2023-03-16T10:33:21.9895351Z ##[debug]Agent.TempDirectory=D:\DevOps\agent3\_work\_temp
2023-03-16T10:33:21.9896103Z ##[debug]testing directory 'D:\DevOps\agent3\_work\_temp'
2023-03-16T10:33:21.9896765Z Downloading: https://nodejs.org/dist/v18.15.0/node-v18.15.0-win-x64.7z
2023-03-16T10:33:21.9897524Z ##[debug]destination D:\DevOps\agent3\_work\_temp\388592de-dfd7-479a-8571-78f354aba6ef
2023-03-16T10:33:21.9898272Z ##[debug]downloading
2023-03-16T10:33:21.9899274Z ##[debug]Failed to download "388592de-dfd7-479a-8571-78f354aba6ef" from "https://nodejs.org/dist/v18.15.0/node-v18.15.0-win-x64.7z". Code(404) Message(Not Found)
2023-03-16T10:33:21.9900216Z ##[debug]agent.tempDirectory=D:\DevOps\agent3\_work\_temp
2023-03-16T10:33:21.9901005Z ##[debug]testing directory 'D:\DevOps\agent3\_work\_temp\temp_1497714889'
2023-03-16T10:33:21.9901781Z ##[debug]testing directory 'D:\DevOps\agent3\_work\_temp'
2023-03-16T10:33:21.9902533Z ##[debug]mkdir 'D:\DevOps\agent3\_work\_temp\temp_1497714889'
2023-03-16T10:33:21.9903301Z ##[debug]D:\DevOps\agent3\_work\_temp\temp_1497714889\node.exe
2023-03-16T10:33:21.9904090Z ##[debug]testing directory 'D:\DevOps\agent3\_work\_temp\temp_1497714889'
2023-03-16T10:33:21.9904659Z Downloading: https://nodejs.org/dist/v18.15.0/win-x64/node.exe
2023-03-16T10:33:21.9905379Z ##[debug]destination D:\DevOps\agent3\_work\_temp\temp_1497714889\node.exe
2023-03-16T10:33:21.9906086Z ##[debug]downloading
2023-03-16T10:33:22.0017941Z ##[debug]Failed to download "D:\DevOps\agent3\_work\_temp\temp_1497714889\node.exe" from "https://nodejs.org/dist/v18.15.0/win-x64/node.exe". Code(404) Message(Not Found)
2023-03-16T10:33:22.0019295Z ##[debug]D:\DevOps\agent3\_work\_temp\temp_1497714889\node.exe
2023-03-16T10:33:22.0020121Z ##[debug]testing directory 'D:\DevOps\agent3\_work\_temp\temp_1497714889'
2023-03-16T10:33:22.0020702Z Downloading: https://nodejs.org/dist/v18.15.0/node.exe
2023-03-16T10:33:22.0021418Z ##[debug]destination D:\DevOps\agent3\_work\_temp\temp_1497714889\node.exe
2023-03-16T10:33:22.0022138Z ##[debug]downloading
2023-03-16T10:33:22.0220155Z ##[debug]Failed to download "D:\DevOps\agent3\_work\_temp\temp_1497714889\node.exe" from "https://nodejs.org/dist/v18.15.0/node.exe". Code(404) Message(Not Found)
2023-03-16T10:33:22.0222303Z ##[debug]task result: Failed
2023-03-16T10:33:22.0256427Z ##[error]Unexpected HTTP response: 404
2023-03-16T10:33:22.0267266Z ##[debug]Processed: ##vso[task.issue type=error;]Unexpected HTTP response: 404
2023-03-16T10:33:22.0274471Z ##[debug]Processed: ##vso[task.complete result=Failed;]Unexpected HTTP response: 404
2023-03-16T10:33:22.0343703Z ##[section]Finishing: Install Node.js

Relevant log output
2023-03-16T10:33:21.9898272Z ##[debug]downloading
2023-03-16T10:33:21.9899274Z ##[debug]Failed to download "388592de-dfd7-479a-8571-78f354aba6ef" from "https://nodejs.org/dist/v18.15.0/node-v18.15.0-win-x64.7z". Code(404) Message(Not Found)
2023-03-16T10:33:21.9900216Z ##[debug]agent.tempDirectory=D:\DevOps\agent3\_work\_temp
2023-03-16T10:33:21.9901005Z ##[debug]testing directory 'D:\DevOps\agent3\_work\_temp\temp_1497714889'
2023-03-16T10:33:21.9901781Z ##[debug]testing directory 'D:\DevOps\agent3\_work\_temp'
2023-03-16T10:33:21.9902533Z ##[debug]mkdir 'D:\DevOps\agent3\_work\_temp\temp_1497714889'
2023-03-16T10:33:21.9903301Z ##[debug]D:\DevOps\agent3\_work\_temp\temp_1497714889\node.exe
2023-03-16T10:33:21.9904090Z ##[debug]testing directory 'D:\DevOps\agent3\_work\_temp\temp_1497714889'
2023-03-16T10:33:21.9904659Z Downloading: https://nodejs.org/dist/v18.15.0/win-x64/node.exe
2023-03-16T10:33:21.9905379Z ##[debug]destination D:\DevOps\agent3\_work\_temp\temp_1497714889\node.exe
2023-03-16T10:33:21.9906086Z ##[debug]downloading
2023-03-16T10:33:22.0017941Z ##[debug]Failed to download "D:\DevOps\agent3\_work\_temp\temp_1497714889\node.exe" from "https://nodejs.org/dist/v18.15.0/win-x64/node.exe". Code(404) Message(Not Found)
2023-03-16T10:33:22.0019295Z ##[debug]D:\DevOps\agent3\_work\_temp\temp_1497714889\node.exe
2023-03-16T10:33:22.0020121Z ##[debug]testing directory 'D:\DevOps\agent3\_work\_temp\temp_1497714889'
2023-03-16T10:33:22.0020702Z Downloading: https://nodejs.org/dist/v18.15.0/node.exe
2023-03-16T10:33:22.0021418Z ##[debug]destination D:\DevOps\agent3\_work\_temp\temp_1497714889\node.exe
2023-03-16T10:33:22.0022138Z ##[debug]downloading
2023-03-16T10:33:22.0220155Z ##[debug]Failed to download "D:\DevOps\agent3\_work\_temp\temp_1497714889\node.exe" from "https://nodejs.org/dist/v18.15.0/node.exe". Code(404) Message(Not Found)
2023-03-16T10:33:22.0222303Z ##[debug]task result: Failed
2023-03-16T10:33:22.0256427Z ##[error]Unexpected HTTP response: 404
2023-03-16T10:33:22.0267266Z ##[debug]Processed: ##vso[task.issue type=error;]Unexpected HTTP response: 404
2023-03-16T10:33:22.0274471Z ##[debug]Processed: ##vso[task.complete result=Failed;]Unexpected HTTP response: 404
2023-03-16T10:33:22.0343703Z ##[section]Finishing: Install Node.js

Aditional info
It looks like the pipeline cannot find `node v18.x`. Perhaps this is also more related to Node Then the pipeline

Same is the case with v16.x
It fails while downloading "node.exe" (https://nodejs.org/dist/v16.19.0/node.exe).
If you observe the directory (https://nodejs.org/dist/v16.19.0) - node.exe is not in there.

This is causing build failures. Hope it is fixed soon!

Let me add- We're using Azure DevOps Services and the Azure managed agents. I can confirm we're also also seeing a similar issue with NodeTool as of this morning:

These appear to be pulling a newer version of the NodeTool task relative to the reports above (0.218.0), and it's generating a slightly different error message. High-level, this looks related, though.

We're seeing the same.

We are experiencing the same issue with version 16.14.2.
Download is failing at dist/v16.14.2/node.exe


text:
"npm Authenticate (for task runners)" should use environment variables to improve security

Environment

Server - Azure Pipelines
Agent - Hosted or Private: either

Issue Description
The "npm Authenticate (for task runners)" task allows a shell command such as npm publish to obtain its NPM registry credentials from a VSTS "service connection".  This is more secure/maintainable than storing an authentication token in an environment variable.
However, the design of "npm Authenticate (for task runners)" task seems to work like this:

Inject the credentials into an .npmrc file on disk (whose path is specified as part of the build step)
Allow the rest of the build steps to execute
In a special post-build step:  Revert the changes from step 1, restoring the .npmrc file to its original state

There are a couple problems with this design:

If the post-build step never executes (e.g. because the machine crashed), the credentials will be saved on disk forever.  This seems like a security concern, given that the NPM publishing token is a very powerful and sensitive credential.
The NPM tool only searches for .npmrc in a few places.  In a monorepo with hundreds of projects, we need the file to be in a central location that will be found by many different npm publish invocations.  We can put the file in the user home directory, but that will affect other jobs running on the same VM.  That's a security concern also.

Proposed improvement
I'd like to propose a different design:  The "npm Authenticate (for task runners)" task should store its authentication token in an environment variable.  The task would be configured to invoke a shell command similar to the "Command Line" task.  The environment variable would only be visible to this process; it would not be accessible from any other build steps.
This could be implemented as an optional mode for the existing task, or maybe it could be a new task type.
What do you think?  Does this sound like a useful improvement?  Or is there some way to solve the above security problems using the existing design?
@nickpape-msft @iclanton

@pgonzal unfortunately you've hit on a fundamental challege with build. When someone has access to your build environment, lots of nefarious things can happen. We mitigate this when you're working within the same organization by using a token scoped to the execution of the build, but that obviously doesn't help when you're publishing to e.g. npmjs.
The npm Authenticate task is actually designed to leave the token available for you to use for the scope of the build. This allows you to call npm in whatever way you wish (through gulp, grunt, ps, bash, etc.) and have npm self-discover the token it needs to perform your desired action.
The npm task works closer to the way you describe. It still creates a temporary file but it cleans it up at the end of that task, rather than the end of the build. If we made the changes you proposed, it would be to this task. I don't think the environment variable support was there the last time we updated the task - good to know they're improving security here.
Adding @bryanmacfarlane, who's thought a lot about token security in build - he may have additional thoughts.

Or, thinking more, we might also switch the npm Authenticate task to use the environment variable (as that's just generally better than having a token on disk). But, we'd probably make the environment variable available for the scope of the build, or have that configurable, to enable the scripting scenarios I described.

@alexmullans  FWIW when I first tried "npm Authenticate (for task runners)", I was dismayed to find that our npmjs.com authentication token was accidentally pushed to our public GitHub repo.  (!) This happened because the target .npmrc file was under our repo folder, and one of the build steps ran a version-bumping operation that made changes to package.json and then did something akin to git add  && git commit && git push.  That script did not anticipate other processes writing files into the Git working folder, so the .npmrc change inadvertently got included.  Coming from that experience, I feel like environment variables are inherently MUCH safer than writing tokens into a file on disk.

I don't think the environment variable support was there the last time we updated the task - good to know they're improving security here.

In our case, we don't run npm publish directly.  Instead we use rush publish which figures out which package(s) have changes to be published, and automates running npm publish (or actually pnpm publish, or yarn publish in some cases) for each individual project.  Rush supports a command line sort of like this:
rush publish --npm-auth-token $(YOUR_TOKEN_HERE) ...

So the environment variable is useful even if you aren't using the NPM package manager.

But, we'd probably make the environment variable available for the scope of the build, or have that configurable, to enable the scripting scenarios I described.

I suppose you have a fair point:  If any of the build steps executes malicious code, then theoretically all subsequent build steps could have the binary that they invoked replaced by a malicious binary that captures the environment variable.  However I think it's still less secure:  For example, a non-malicious person might do something like dump all the environment variables to the console for diagnostic purposes.  If the authentication token is available to ALL steps, then this person would inadvertently dump the token into the log files.  (Even if VSTS detected this and masked the password, it could still happen via a build artifact.)
Given the high risk of a public npmjs.com authentication token, I would encourage the VSTS design to be as conservative as possible, versus by default sharing the environment as widely as possible.  Security is arguably more important than convenience for this case.

@alexmullans - we'll discuss and loop back.

I've tracked this work internally as part of a set of updates we'd like to make to the npm task. In general, @pgonzal, I think you're right that we need to move to using an environment variable.

Awesome, thanks Alex!

@pgonzal we're tracking design work for this here, fyi. https://github.com/Microsoft/azure-pipelines-yaml/pull/40#pullrequestreview-170819959

This has been fixed and released as part of this design: https://github.com/Microsoft/azure-pipelines-yaml/blob/master/design/artifacts-in-pipelines.md#authentication-1.
The new NpmAuthenticate task uses environment variables to authenticate feeds. You can read more about this task here: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/package/npm-authenticate?view=azure-devops

Is there a way to use version 1 of this task in non-yaml pipelines? We're stuck on the classic pipelines as our repo is still hosted in Subversion.

Looks like this never made it out of the design stage?
I bake git describe information into my application and was curious why git describe was always returning a dirty flag for the repository in a a node script but not an earlier PowerShell script when built in Pipelines and it turned out to be these tasks modifying the .npmrc file in the repository. It does seem like it would be preferable if it not modify the .npmrc file in place, but I understand in reading this discussion better why it does.

authors: LodewijkSioen WorldMaker aasim alexmullans bryanmacfarlane octogonz pgonzal


text:
not able to add azure account

Duplicate of #10734

authors: aaomidi alanrenmsft

repo: microsoft/azuredatastudio


text:
Databases should be listed alphabetically in Publish Database Project UI

Note: this seems to be happening only sporadically.  Low pri

seems to be fixed now.

authors: Benjin udeeshagautam


text:
not able to do keyboard navigation within ADS because of the callout dialog

once we have the callout dialog opened once, the keyboard navigation within ADS is broken, unless the notebook is closed.

also, keyboard navigation is not possible within this dialog

@halerankin please take a look. We need to fix this for March. Please let me know if you have any concerns.

authors: alanrenmsft chlafreniere


text:
Query Plan tab is shown for incorrect query

Azure Data Studio Version: master

Steps to Reproduce:

Run a query using the Explain button
Open a new query window and type some SQL
Run the new query with the Run button

Expected: No query plan for new query
Actual: The old query plan from the first query is shown in the new query

@anthonydresser I think this starting happening around the time Messages was moved into its own tab.  Let me know if you don't have time to investigate and we can load balance.  Thanks!


text:
BDC with AD mode wizard  hasn't implemented the newly introduced  activeDirectory Node under security config.

ADS hasn’t implemented AD the new security config node activeDirectory,
Control.json generated by AD and see activeDirectory  node is empty and the variables were added under security node directly similar to CU1
"security": {
    "activeDirectory": {
        "ouDistinguishedName": "",
        "dnsIpAddresses": [],
        "domainControllerFullyQualifiedDns": [],
        "domainDnsName": "",
        "clusterAdmins": [],
        "clusterUsers": []
    },
    "ouDistinguishedName": "OU=bdc, DC=contoso, DC=com",
    "dnsIpAddresses": [
        "192.168.1.200"
    ],
    "domainControllerFullyQualifiedDns": [
        "DC1.CONTOSO.COM"
    ],
    "domainDnsName": "contoso.com",
    "realm": "CONTOSO.COM",
    "clusterAdmins": [
        "bdcadmins"
    ],
    "clusterUsers": [
        "bdcusers"
    ]
}

This deployment is failing with this error
Creating SQL Server 2019 Big Data Cluster: mssql-cluster using configuration ads-bdc-custom-profile
If you don't see output produced by azdata, you can run the following command in a terminal window to check the deployment status:
C:\Users<user>\AppData\Local\Programs\Python\Python37\kubectl.exe get pods -n mssql-cluster
Executing: azdata bdc create -c ads-bdc-custom-profile
The privacy statement can be viewed at:
https://go.microsoft.com/fwlink/?LinkId=853010
The license terms for SQL Server Big Data Cluster can be viewed at:
Enterprise: https://go.microsoft.com/fwlink/?linkid=2104292
Standard: https://go.microsoft.com/fwlink/?linkid=2104294
Developer: https://go.microsoft.com/fwlink/?linkid=2104079
Cluster deployment documentation can be viewed at:
https://aka.ms/bdc-deploy
ERROR: Failed to set security configuration. Please check the deployment documentation https://aka.ms/bdc-deploy . Security configuration parameter 'clusterAdmins' must contain a single domain group. Values specified:
An exception has occurred, use %tb to see the full traceback.
SystemExit: Command execution failed with exit code: 1.
azdata bdc create -c ads-bdc-custom-profile
c:\users<user>\azuredatastudio-python\0.0.1\lib\site-packages\IPython\core\interactiveshell.py:3334: UserWarning: To exit: use 'exit', 'quit', or Ctrl-D.
warn("To exit: use 'exit', 'quit', or Ctrl-D.", stacklevel=1)
ADS version
Version: 1.16.0-insider (user setup)
Commit: 506c6a5e5f8423d3249670f55b1466b1980a5f03
Date: 2020-02-17T05:43:18.399Z
VS Code: 1.42.0
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363

@rl-msft Thanks for reporting the issue, I have fixed it and please try the latest insider build.

authors: alanrenmsft rl-msft


text:
add right padding to notebook toolbar action item (#13640)

add right padding to action item

remove extra line and add space

This PR fixes #13607

Pull Request Test Coverage Report for Build 399038968

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 41.157%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/jupyter/serverInstance.ts
4
73.81%

Totals

Change from base Build 397431474:
-0.01%

Covered Lines:
21844

Relevant Lines:
48622

💛  - Coveralls

authors: barbaravaldez coveralls


text:
Make publish to docker settings properties required

It's annoying having to deal with checking these properties everywhere and it doesn't seem to make sense to have them optional - we should always have these properties both exist when we finish gathering the publish options.

Pull Request Test Coverage Report for Build 2592763229

0 of 19 (0.0%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.006%) to 42.17%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/sql-database-projects/src/dialogs/deployDatabaseQuickpick.ts
0
3
0.0%

extensions/sql-database-projects/src/controllers/projectController.ts
0
16
0.0%

Files with Coverage Reduction
New Missed Lines
%

extensions/sql-database-projects/src/dialogs/deployDatabaseQuickpick.ts
1
4.4%

Totals

Change from base Build 2591849983:
0.006%

Covered Lines:
28200

Relevant Lines:
62427

💛  - Coveralls

authors: Charles-Gagnon coveralls


text:
Update changelog for 1.41.2

Document hotfixed issues from https://github.com/microsoft/azuredatastudio/milestone/97 into the changelog.

Pull Request Test Coverage Report for Build 4136960492

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 41.937%

Totals

Change from base Build 4136827664:
0.0%

Covered Lines:
28651

Relevant Lines:
63452

💛  - Coveralls

authors: coveralls kburtram


text:
[New Migration Experience] bug fixes

Few bugs found during the test-

Next button was reenabled on successful assessment (A bug that next button not working on successful assessment).
Some Text fixes for importa performance data

Pull Request Test Coverage Report for Build 6729610562

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.006%) to 41.57%

Files with Coverage Reduction
New Missed Lines
%

extensions/sql-database-projects/src/common/httpClient.ts
1
66.18%

extensions/sql-database-projects/src/dialogs/publishDatabaseDialog.ts
2
52.03%

Totals

Change from base Build 6728611477:
-0.006%

Covered Lines:
30785

Relevant Lines:
69356

💛  - Coveralls

authors: coveralls krritik


text:
Add Obsolete attribute to CosmosDbStorage

Fixes: https://github.com/microsoft/botframework-sdk/issues/5634
Deprecate CosmosDbStorage and CosmosDbStorageOptions with recommendation to use CosmosDbPartitionedStorage, and fix compiler warnings in CosmosDbStorageTests

Pull Request Test Coverage Report for Build 106337

0 of 0   changed or added relevant lines in 0 files are covered.
958 unchanged lines in 117 files lost coverage.
Overall coverage decreased (-1.6%) to 77.821%

Files with Coverage Reduction
New Missed Lines
%

/libraries/Adapters/Microsoft.Bot.Builder.Adapters.Facebook/FacebookAdapterOptions.cs
1
92.31%

/libraries/AdaptiveExpressions/ExpressionProperties/ArrayExpression.cs
1
54.55%

/libraries/integration/Microsoft.Bot.Builder.Integration.ApplicationInsights.Core/ApplicationBuilderExtensions.cs
1
125.0%

/libraries/Microsoft.Bot.Builder.AI.LUIS/LuisApplication.cs
1
97.37%

/libraries/Microsoft.Bot.Builder.AI.LUIS/V3/LuisApplication.cs
1
97.37%

/libraries/Microsoft.Bot.Builder.AI.LUIS/V3/LuisUtil.cs
1
95.24%

/libraries/Microsoft.Bot.Builder/BotStateSet.cs
1
85.71%

/libraries/Microsoft.Bot.Builder.Dialogs/Debugging/DebugSupport.cs
1
77.78%

/libraries/Microsoft.Bot.Builder.Dialogs/Debugging/SourceRange.cs
1
45.45%

/libraries/Microsoft.Bot.Builder.Dialogs.Declarative/DeclarativeType.cs
1
72.73%

Totals

Change from base Build 106151:
-1.6%

Covered Lines:
21003

Relevant Lines:
26989

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.ApplicationInsights.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Integration.AspNet.Core.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Testing.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.6.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Streaming.dll compared against version 4.6.3

authors: EricDahlvang coveralls fuselabs

repo: microsoft/botbuilder-dotnet