BuildVersion | Update your Assembly Versions w/ MSBuild | Code Editor library

stdout is usually line buffered only if connected to a terminal. Connecting it to a pipe causes full buffering.

Although some commands, including tee, are guaranteed not to buffer at all (hence the last example of tee | sed).

You can use stdbuf -oL sed 's...g' or unbuffer sed 's...g' to get line buffering. stdbuf is part of GNU coreutils so should be available on Linux, It's also available by default on FreeBSD.

This article from 2006 is old, but provides some good detail. The author is a GNU coreutils maintainer.

http://www.pixelbeat.org/programming/stdio_buffering/

https://community.synopsys.com/s/document-item?bundleId=integrations-detect&topicId=scripts%2Fscript-escaping-special-characters.html&_LANG=enus

To have literal detect.sh --detect.project.name=\"Project Test\"

You have to escape each backslash with another one in groovy string

The simple answer is that there are two inputs for each id, e.g. signInFormUsername, and by this we get multiple items matching each selector. The second element for each selector is invisible (display: none). The solution is to filter out the invisible elements:

You code is fine, I've tested it and it works. The problem is the Pipeline editor. It doesn't seem to be able to parse the Conditional so it will give you squiggly lines and an error message but you can ignore it.

One thing that worked for me was to change the USB hub I was connecting to on my MacBook M1. I had daisy chained two hubs and the device was connected to the second one.

So if your issue is with a USB hub, you can troubleshoot here as well.

This is by design, the Windows PowerShell version of ConvertFrom-Json explicitly requests the runtime doesn't immediately enumerate array output (Write-Output $array -NoEnumerate basically).

The reason is that a JSON document with a top-level single-item array like [1] would be indistinguishable from the document 1 if PowerShell's default pipeline enumeration behavior was allowed.

As you've found, you can work around this by nesting the pipeline that ends with ConvertFrom-Json, using either the grouping operator (...), or either of the subexpression operators $(...) or @(...):

I think I may have figured out the problem. It appears that this is related to the use of conditionals in the variable setup. While the variables will be set in any valid trigger configuration, it appears that the proper values are not used during validation and that may have been causing the problem. Switching my conditional variables to first set a default value and then replace the value conditionally seems to have fixed the problem.

It would be nice if Microsoft would give a more useful error message here, something to the extent of the values not being found for a given variable, but adding defaults does seem to have fixed the problem.

After investigation, the step which invokes commands npm version $(buildVersion) --no-git-tag-version was touching package-lock.json

I added additional step which resets the version after Publish to feed

CSS variables are copied as they are from where they are defined to the place where they are used. It is mostly just a dynamic copy and paste which is why stuff like that works: