Adding "proximityPlacementGroup" property in "VirtualMachineScaleSetUpdateProperties". Adding "includeColocationStatus" optional flag as part of Get ProximityPlacementGroup URL

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-python

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

@rosingla Could you fix the CI errors? If you need some help, please ping me.

@rosingla Please rebase or merge the master branch into your branch to fix BreakingChange CI.

@rosingla Could you fix the CI errors? If you need some help, please ping me.

@MyronFanQiu  - there are currently 3 CI errors:

spellcheck error for "colocation" word. Fixing it by adding it as a custom word in customwords.txt
For the other two errors, I couldn't understand if they are occurring due to changes introduced by me. Lokking further I got the following error:

Error: (node:5944) UnhandledPromiseRejectionWarning: TypeError: volume[member].bind is not a function
at patchFilesystem (/home/vsts/work/1/s/node_modules/autorest/dist/static-loader.js:277:43)
at /home/vsts/work/1/s/node_modules/autorest/dist/static-loader.js:281:18
at Object.global.staticloader.undo (/home/vsts/work/1/s/node_modules/autorest/dist/static-loader.js:163:7)
at process.exit (/home/vsts/work/1/s/node_modules/autorest/dist/static-loader.js:170:27)
at main (/home/vsts/.autorest/@microsoft.azure_autorest-core@2.0.4407/node_modules/@microsoft.azure/autorest-core/dist/app.js:517:21)
https://dev.azure.com/azure-sdk/public/_build/results?buildId=183399&view=logs&j=08b5038d-1e84-5877-88da-859df8312b69&t=c1978ecd-fc8a-5291-6d7a-7dd459d8b50f&l=66
Please let me know if I missed something or how do I fix these errors. My branch is currently upto date with master.

@rosingla Thanks. The other errors are caused by other issues and has been fixed in other PR. PR is merged.


Editable row add and edit

i'm following this guide http://jsfiddle.net/NfPcH/93/
how can i detect if add row is to save and edit is to update???
because add and edit have the same function of $scope.saveUser????

i check the id if true or false and put in the condition :)


Executing a schedule with one instruction raises an error

Information

Qiskit Terra version:
Python version:
Operating system:

What is the current behavior?
If I make a schedule with only one instruction:
sched = pulse.Acquire(20, pulse.AcquireChannel(0), pulse.MemorySlot(0))

then when I execute it, it's type is Instruction and not Schedule, so execute wrongly sends it through the transpiler, thinking it's a QuantumCircuit. Since the transpiler is expecting a circuit, we end up with an attribute error as it tries to access circuit.qubits, which isn't a Schedule property.
Steps to reproduce the problem
What is the expected behavior?
Suggested solutions
The easiest fix is to replace isinstance(experiments, Schedule) with isinstance(experiments, (Schedule, pulse.Instruction), or perhaps more correctly: isinstance(experiments, ScheduleComponent). Would have to add tests and make sure there aren't other consequences of taking an Instruction as input.

This is just an instruction though. Should we allow executing a sole instruction?

yes


follow-up to #41: invalid type: null

#41 resulted in clean checks against most of restic repositories, but I have found one that still throws an error. At 64TB this repo takes a bit longer to process
[...]
 - reading snapshots...
[00:00:00] ████████████████████████████████████████       4751/4751
 - checking trees...
[00:23:58] █████████████████████████████████░░░░░░░       3998/4751
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: invalid type: null, expected a sequence at line 1 column 13', src/blob/tree.rs:203:33

Older restic is possible. With #47 process moved past prior fault point, before succumbing to oom-reaper. Need to find out what and where might be leaking memory
 - checking trees...
[00:29:17] █████████████████████████████████████░░░       4479/4751
Killed

Older restic is possible. With #47 process moved past prior fault point

Ok, that means that #47 solves the this issues.
I opened #48 for the OOM problem.


Wiki Localization

Hey,
if its ok i would translate the entire wiki into german.

Yes of course! I could help a little bit too. My German isn't 100% but it
could always be revised :D
Now that I think about it, I could do a French translation too as I'm
fluent in French.
I guess just make mirror of the current wiki but in German, and I'll have
the landing page be multilingual. Thanks for the contribution!
On Apr 7, 2016 11:09 PM, "Philipp"<EMAIL_ADDRESS>wrote:

Hey,
if its ok i would translate the entire wiki into german.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/NodeOS/NodeOS/issues/222

While you are on it, if you both could review and update the info on the wiki it would be great :-D

Sure, yesterday i cloned the wiki to my local machine and update some stuff.
One Question: Is it possible to push the wiki to the master branch of the repo?

Is it possible to push the wiki to the master branch of the repo?

What do you mean? GitHub wikis has their own (hidden) git repo, that's the same name of the main project but ending in '.wiki'
https://help.github.com/articles/adding-and-editing-wiki-pages-locally/
Are you talking about this, or about moving the wiki to the docs folder of the project?

Basicly i mean that im rewriting the docs at the moment and when im done i want to push them to the wiki, do i need the permission for this or can anybody push to it.

I have no permission to push to the wiki :-(

Basicly i mean that im rewriting the docs at the moment and when im done
i want to push them to the wiki, do i need the permission for this or can
anybody push to it.

As far as I know, anyone can publish on the wiki.

Ok like i said i cloned the wiki to my local machine and i want to push to the wiki but i get a 403 Permission denied

Maybe you can add me as a member of nodeos

Ok like i said i cloned the wiki to my local machine and i want to push to the wiki but i get a 403 Permission denied

How did you cloned the wiki and how are you doing the push?

If I recall correctly, wiki's are just repositories so they can be cloned.
I also could alter it's content without being a member of the repo so maybe
anyone can push too.
On Apr 9, 2016 1:52 PM, "Jesús Leganés Combarro"<EMAIL_ADDRESS>wrote:

Ok like i said i cloned the wiki to my local machine and i want to push to
the wiki but i get a 403 Permission denied
How did you cloned the wiki and how are you doing the push?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/NodeOS/NodeOS/issues/222#issuecomment-207843436

I already did update most of it :)
I decided I'd be a wiki maintainer since I like to type so I've been
keeping it fairly up to date :P. I just need to write about the logon
On Apr 9, 2016 4:27 AM, "Jesús Leganés Combarro"<EMAIL_ADDRESS>wrote:

While you are on it, if you both could review and update the info on the
wiki it would be great :-D
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/NodeOS/NodeOS/issues/222#issuecomment-207767021

@piranna i cloned by the link that is displayed on the wiki page under the sidebar
and then it gives me a folder called NodeOS.wiki with a .git inside the rest is just git add, comit and push nothing more but like i said above i get a 403
@lite20 currently im updating it make it more user friendly and rearrange some Pages for more readability

currently im updating it make it more user friendly and rearrange some Pages for more readability

Yeah go for it! I don't mind.

@luii Email me the next time you're ready to push and I'll see what we can do.

@lite20 can i become a member of nodeos?

@lite20 can i become a member of nodeos?

Done.

@lite20 how can i email you, there is no email on your profile

Oh you couldn't push? Create a fork?
On Apr 9, 2016 2:00 PM, "Lite McFish"<EMAIL_ADDRESS>wrote:

If I recall correctly, wiki's are just repositories so they can be cloned.
I also could alter it's content without being a member of the repo so maybe
anyone can push too.
On Apr 9, 2016 1:52 PM, "Jesús Leganés Combarro"<EMAIL_ADDRESS>wrote:

Ok like i said i cloned the wiki to my local machine and i want to push
to the wiki but i get a 403 Permission denied
How did you cloned the wiki and how are you doing the push?
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/NodeOS/NodeOS/issues/222#issuecomment-207843436

already pushed the changes to the wiki

@lite20 https://github.com/lite20 how can i email you, there is no
email on your profile

Oh that's weird I thought I added it. If anyone ever needs to reach me, you
can use<EMAIL_ADDRESS>On Apr 10, 2016 8:45 AM, "Philipp Czarnetzki"<EMAIL_ADDRESS>wrote:

already pushed the changes to the wiki
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/NodeOS/NodeOS/issues/222#issuecomment-207995212

Ok that good, if you dont like parts of the new docs please feel free to contact me

I'll take a look at them right now. :)
On Sun, Apr 10, 2016, 1:40 PM Philipp Czarnetzki<EMAIL_ADDRESS>wrote:

Ok that good, if you dont like parts of the new docs please feel free to
contact me
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/NodeOS/NodeOS/issues/222#issuecomment-208049629

@lite20 how should i translate the file and where should i place them, in a seperate folder inside the docs folder in NodeOS?

@lite20 how should i translate the file and where should i place them, in a seperate folder inside the docs folder in NodeOS?

We have two options, have them in the wiki or move them to the docs folder in NodeOS source code. I vote for the second option and deprecate the wiki (I always forget it exists...).

I would place them in the docs, but keep the wiki and i can update it!
Any suggenstions on the folder structure for the docs?
I would use ISO 639-1 language codes for the folder names corresponding to the language they'll be translated into.
NodeOS
-> docs
---> en - English Translation
---> fr - French Translation
---> de - German Translation
---> es - Spanish Translation

I was going to propose to follow the schema used by GitBook for the multi-language books, but I think it's the same that you have proposed.

Do we have enough people who speak german and french ? I speak both... so I can help if needed ...

I can be able only english and spanish.

I translate the current Wiki to german

I can do frech ...

@piranna Should we push directly to the Repo with [ci skip] in the commit or should we create a seperate repo (like: "nodeos-de") and link it with git submodule to this repo?

I'm against to move the docs to independent repos, I think it's better to have them here with the main source code. What's that thing of [ci skip]?

Do we have enough people who speak german and french ? I speak both...

What really? I'm multilingual too! French is actually my dominant language.

@piranna we could create a mirror site like we did for the blog to hide the bloat of all the other languages being present? We could also then format it as we pleased.

@piranna if you place [ci skip] or [skip ci] inside the commit title semaphoreci will skip this commit
because its not a build process relevant commit.
@lite20 would it not be better to push it all to the docs folder and then create a list of languages inside the wiki?

@lite20 Oh wow ^^ Yeah... I'm swiss ... we've got about 4 official languges and even more that we (can) learn in school ^^
@luii I like the idea of seperated sites bette, I think it'd be much cleaner :/

@Coretool i also prefer the idea of seperated stites.
I would also create git submodules in the nodeos/docs folder

@piranna we could create a mirror site like we did for the blog to hide
the bloat of all the other languages being present? We could also then
format it as we pleased.

I think that's diferent, the blog was an independent project. What's the
standard on Node.js projects beside Readme.md?

Good trick, didn't know it :-)

@lite20 would it not be better to push it all to the docs folder and then
create a list of languages inside the wiki?

I agree on that, only that put the languages list on the repo too.

I would also create git submodules in the nodeos/docs folder

I don't like submodules too much... :-/

Check out how I handled double languages with HexCade:
https://bitbucket.org/Lite20/hexcade/wiki/Home
We could potentially do this?
On Fri, Apr 15, 2016, 2:35 AM Jesús Leganés Combarro <
<EMAIL_ADDRESS>wrote:

I would also create git submodules in the nodeos/docs folder

I don't like submodules too much... :-/
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/NodeOS/NodeOS/issues/222#issuecomment-210360327

GitBook multi-language format is very similar to the solution that you propose :-) This way we could be able later easily publish NodeOS docs too :-D

GitBook sounds good to me! Let's do it! I'll probably implement it w/ HexCade too.
By the way, since I know you're curious, HexCade is an interpreted language I started creating to better understand interpreted languages. It's key features are how it handles threads, it's true asynchronous nature, and it's object context design (in JS we have contexts; in HxC, contexts from, for example functions, are variables too and can be accessed by other parts of a program if needed)


Support --test-setup argument in Jenkins

Support querying for the source of testing setup in the Jenkins source.
This argument will only be used when a few jobs are passed, since it
requires requesting artifacts and we want to avoid overloading the
Jenkins instance.

How is it used with Jenkins?
Should this be working?
cibyl --jobs DFG-network-openstack-designate-16.2_director-rhel-virthost-3cont_2comp-ipv4-geneve --test-setup

It should if you specify the value. Currently, the --test-setup supports only filtering, calling it without any value will produce an error, but this behaviour can be easily changed. However, the job that you have used as example those not have logs, so the information is not available. One that works for me is DFG-network-openstack-designate-17.0_director-rhel-virthost-3cont_2comp-ipv4-geneve

Filtering in what way? This doesn't work for me cibyl --test-setup rpm

For any query that includes more than 12 jobs (this is an arbitrary limit that I set at some point), it will not do anything, since it will not request the logs (too many requests to the Jenkins instance). For example the query cibyl --jobs DFG-network-openstack-designate  --test-setup rpm show only one job, but changing it to cibyl --jobs DFG-network-openstack-designate  --test-setup git, shows zero.

For any query that includes more than 12 jobs (this is an arbitrary limit that I set at some point), it will not do anything, since it will not request the logs (too many requests to the Jenkins instance). For example the query cibyl --jobs DFG-network-openstack-designate --test-setup rpm show only one job, but changing it to cibyl --jobs DFG-network-openstack-designate --test-setup git, shows zero.

k I see. In that case, by default cibyl  --test-setup git would probably go to 'Elasticsearch`
In that case, the following two should cover all designate jobs (at least those with builds):
cibyl --jobs DFG-network-openstack-designate --test-setup rpm
cibyl --jobs DFG-network-openstack-designate --test-setup git
But I get as a result only one job with "rpm".  Shouldn't I see more jobs that have 'rpm' setup or 'git'?


Npm install failure when installing from node10

I am not sure of the exact issue causing this or if it was caused on my end but here is the call stack when trying to npm ci from node v10 in a docker file.
Callstack
><EMAIL_ADDRESS>install /usr/src/app/node_modules/epoll
> node-gyp rebuild

qemu: Unsupported syscall: 397
qemu: Unsupported syscall: 397
gyp: Call to 'node -e "require('nan')"' returned exit status 0 while in binding.gyp. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)
gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Linux 4.9.125-linuxkit
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/src/app/node_modules/epoll
gyp ERR! node -v v10.18.0
gyp ERR! node-gyp -v v5.0.5
gyp ERR! not ok
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!

COPY package.json package-lock.json $APP_DIR

COPY . .

RUN npm ci && npm cache clean --force

If you change the base image to 8.17.0-buster the build works.
The only package in the package.json is.
"dependencies": {
    "onoff": "^5.0.1"
}

I'm not really sure what the problem is here but two things that stick out in the output provided above are:
qemu: Unsupported syscall: 397
qemu: Unsupported syscall: 397

and:
gyp ERR! System Linux 4.9.125-linuxkit

As can be seen here, syscall 397 is statx and as can be seen in the "VERSIONS"  section of the statx man-page statx was added to Linux in kernel 4.11. On the other hand, the output provided above indicates that Linux kernel 4.9.125 is being used.
Debian 9 (Stretch) comes with a Linux kernel version between 3.16 and 4.9. Given that "System Linux 4.9.125-linuxkit" which is presumably Debian 9 is being used, I would imagine that the dockerfile should be using arm32v7/node:10.18.0-stretch rather than arm32v7/node:10.18.0-buster.
Please try with 10.18.0-stretch to see if it works.

As can be seen below, onoff installs and runs without problems on Raspbian Buster with Node.js v8, v10, v12, v13 and v14-nightly.
Node.js v8.17.0
pi@raspberrypi:~/onoff $ rm -rf *
pi@raspberrypi:~/onoff $ node -v
v8.17.0
pi@raspberrypi:~/onoff $ npm i onoff

><EMAIL_ADDRESS>install /home/pi/onoff/node_modules/epoll
> node-gyp rebuild

make: Entering directory '/home/pi/onoff/node_modules/epoll/build'
  CXX(target) Release/obj.target/epoll/src/epoll.o
  SOLINK_MODULE(target) Release/obj.target/epoll.node
  COPY Release/epoll.node
make: Leaving directory '/home/pi/onoff/node_modules/epoll/build'
npm WARN saveError ENOENT: no such file or directory, open '/home/pi/onoff/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/onoff/package.json'
npm WARN onoff No description
npm WARN onoff No repository field.
npm WARN onoff No README data
npm WARN onoff No license field.

+<EMAIL_ADDRESS>added 6 packages from 12 contributors and audited 6 packages in 10.13s
found 0 vulnerabilities

pi@raspberrypi:~/onoff $ node node_modules/onoff/examples/wait-for-interrupt.js
Please press the button on GPIO4...
Button pressed!, its value was 1
pi@raspberrypi:~/onoff $

Node.js v10.18.0
pi@raspberrypi:~/onoff $ rm -rf *
pi@raspberrypi:~/onoff $ node -v
v10.18.0
pi@raspberrypi:~/onoff $ npm i onoff

><EMAIL_ADDRESS>install /home/pi/onoff/node_modules/epoll
> node-gyp rebuild

make: Entering directory '/home/pi/onoff/node_modules/epoll/build'
  CXX(target) Release/obj.target/epoll/src/epoll.o
  SOLINK_MODULE(target) Release/obj.target/epoll.node
  COPY Release/epoll.node
make: Leaving directory '/home/pi/onoff/node_modules/epoll/build'
npm WARN saveError ENOENT: no such file or directory, open '/home/pi/onoff/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/onoff/package.json'
npm WARN onoff No description
npm WARN onoff No repository field.
npm WARN onoff No README data
npm WARN onoff No license field.

+<EMAIL_ADDRESS>added 6 packages from 12 contributors and audited 6 packages in 8.802s
found 0 vulnerabilities

pi@raspberrypi:~/onoff $ node node_modules/onoff/examples/wait-for-interrupt.js
Please press the button on GPIO4...
Button pressed!, its value was 1
pi@raspberrypi:~/onoff $

Node.js v12.14.0
pi@raspberrypi:~/onoff $ rm -rf *
pi@raspberrypi:~/onoff $ node -v
v12.14.0
pi@raspberrypi:~/onoff $ npm i onoff

><EMAIL_ADDRESS>install /home/pi/onoff/node_modules/epoll
> node-gyp rebuild

make: Entering directory '/home/pi/onoff/node_modules/epoll/build'
  CXX(target) Release/obj.target/epoll/src/epoll.o
  SOLINK_MODULE(target) Release/obj.target/epoll.node
  COPY Release/epoll.node
make: Leaving directory '/home/pi/onoff/node_modules/epoll/build'
npm WARN saveError ENOENT: no such file or directory, open '/home/pi/onoff/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/onoff/package.json'
npm WARN onoff No description
npm WARN onoff No repository field.
npm WARN onoff No README data
npm WARN onoff No license field.

+<EMAIL_ADDRESS>added 6 packages from 12 contributors and audited 6 packages in 7.168s
found 0 vulnerabilities

pi@raspberrypi:~/onoff $ node node_modules/onoff/examples/wait-for-interrupt.js
Please press the button on GPIO4...
Button pressed!, its value was 1
pi@raspberrypi:~/onoff $

Node.js v13.5.0
pi@raspberrypi:~/onoff $ rm -rf *
pi@raspberrypi:~/onoff $ node -v
v13.5.0
pi@raspberrypi:~/onoff $ npm i onoff

><EMAIL_ADDRESS>install /home/pi/onoff/node_modules/epoll
> node-gyp rebuild

make: Entering directory '/home/pi/onoff/node_modules/epoll/build'
  CXX(target) Release/obj.target/epoll/src/epoll.o
  SOLINK_MODULE(target) Release/obj.target/epoll.node
  COPY Release/epoll.node
make: Leaving directory '/home/pi/onoff/node_modules/epoll/build'
npm WARN saveError ENOENT: no such file or directory, open '/home/pi/onoff/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/onoff/package.json'
npm WARN onoff No description
npm WARN onoff No repository field.
npm WARN onoff No README data
npm WARN onoff No license field.

+<EMAIL_ADDRESS>added 6 packages from 12 contributors and audited 6 packages in 10.088s
found 0 vulnerabilities

pi@raspberrypi:~/onoff $ node node_modules/onoff/examples/wait-for-interrupt.js
Please press the button on GPIO4...
Button pressed!, its value was 1
pi@raspberrypi:~/onoff $

Node.js v14.0.0-nightly20191225398790149d
pi@raspberrypi:~/onoff $ rm -rf *
pi@raspberrypi:~/onoff $ node -v
v14.0.0-nightly20191225398790149d
pi@raspberrypi:~/onoff $ npm i onoff
npm WARN npm npm does not support Node.js v14.0.0-nightly20191225398790149d
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11, 12, 13.
npm WARN npm You can find the latest version at https://nodejs.org/

><EMAIL_ADDRESS>install /home/pi/onoff/node_modules/epoll
> node-gyp rebuild

make: Entering directory '/home/pi/onoff/node_modules/epoll/build'
  CXX(target) Release/obj.target/epoll/src/epoll.o
  SOLINK_MODULE(target) Release/obj.target/epoll.node
  COPY Release/epoll.node
make: Leaving directory '/home/pi/onoff/node_modules/epoll/build'
npm WARN saveError ENOENT: no such file or directory, open '/home/pi/onoff/package.json'
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN enoent ENOENT: no such file or directory, open '/home/pi/onoff/package.json'
npm WARN onoff No description
npm WARN onoff No repository field.
npm WARN onoff No README data
npm WARN onoff No license field.
npm WARN You are using a pre-release version of node and things may not work as expected

+<EMAIL_ADDRESS>added 6 packages from 12 contributors and audited 6 packages in 6.25s
found 0 vulnerabilities

pi@raspberrypi:~/onoff $ node node_modules/onoff/examples/wait-for-interrupt.js
Please press the button on GPIO4...
Button pressed!, its value was 1
pi@raspberrypi:~/onoff $

@kiwdahc Was it possible to make any progress here?


J2K-Codec

SteamDB app page links to a few games using this
https://steamdb.info/app/3483/
https://steamdb.info/app/32140/
https://steamdb.info/app/78000/
Brief explanation of the change
Detect j2k-codec.dll.

After running changed rules in this pull request (this bot only tests rules.ini changes):
Changed technologies: SDK.J2K
These apps now match: (40) 3470 3472 3480 3482 3483 3540 3542 3560 3562 3580 3582 3620 3622 3630 3632 3650 3652 7340 15960 15962 16020 16022 16030 16032 16060 16062 16090 16098 20700 20710 20720 20730 29120 32140 37990 78000 78002<PHONE_NUMBER>470 1937900
Please confirm that all these changed apps are correct.


lnwire: signature parsing/conversion fuzz tests

We call lnwire's signature parsing and conversion functions from many places in LND, often with untrusted inputs, and existing fuzz tests had incomplete coverage of these functions.
No crashes found after 100+ CPU-hours of fuzzing for each fuzz target.

@crypt-iq: review reminder
@ellemouton: review reminder

Rebased and added release note.

Looks like something else snuck in before and added another conflict in the release notes.

Looks like something else snuck in before and added another conflict in the release notes.

Fixed.

Again, sorry... I promise, this PR is next in the merge queue!

Rebase.  Third time's the charm.


Fix jira usage per lib docs

Fix JIRA config variables
Fix usage per new API after GDPR changes which only allows accountId instead of username fields
Fix docs for configuring JIRA plugin
Pin jira library to 2.0.0 in order to lockdown library usage per library version and allow upgrades after review of version stability

Changes look good to me. We can merge after deciding if we want to pin the jira Python client version or not.

Changes look good to me. We can merge after deciding if we want to pin the jira Python client version or not.

I don't like pinning the client either, but if atlassian decides to only update the client when the API version changes (no backward compatibility) it might make sense to pin it.

I don't like pinning the client either, but if atlassian decides to only update the client when the API version changes (no backward compatibility) it might make sense to pin it.


Added EarlyStopping strategy into callback.py for python users.

Added EarlyStopping class in callback.py for python users to use early stopping strategy.
The modifications are in both callback.py and base_module.py. This is for solving #4965 and #3737.
This new class is following the style of Keras which gives a patience for users to control the rounds they can wait before cancelling out the training.

Will open a new request with clean commits


[Android][Keyboard] Return endCoordinates for keyboardDidHide keyboard event

Summary
This pull request enhances the Keyboard API event emitter for Android upon keyboardDidHide by returning a KeyboardEvent with a meaningful endCoordinates property (instead of emitting a null as of current implementation). This change standardizes the keyboardDidHide keyboard event emission across both iOS and Android, which makes it easier for developers to use the API.
In particular, the semantics of endCoordinates emitted during the keyboardDidHide event on Android will match nicely with semantics of the same event emitted on iOS:

screenY will be height of the screen, as that the keyboard has collapsed to the bottom of the screen
screenX will be 0, as the keyboard will always be flush to the sides of the screen
height will be 0, as the keyboard has fully collapsed
width will be the width of the screen, as the keyboard will always extend to the width of the screen

Also, the flowtypes for KeyboardEvent have been further improved and are more explicit to better highlight the different object shapes (see IOSKeyboardEvent and AndroidKeyboardEvent) depending on the platform.
Changelog
[Android] [Added] - Return endCoordinates for keyboardDidHide keyboard event
Test Plan

Listen to the keyboardDidShow and keyboardDidHide keyboard events, and log out the event details via console.log
Launch the App in both Android and iOS
Enter input in a text field
Close the keyboard
Compare the keyboard event details across both platforms. Most importantly, the endCoordinates property on both event details should share the same semantic meaning.

keyboardDidHide event on iPhone 8

keyboardDidHide event on Google Nexus 5X

Closing pull request to fix type issues, will create new pull request once it's done.


Cloud run + Firebase hosting

I'm having an issue with my sitemap urls showing as my raw cloud run url https://my-app-tzrt63zhyq-ts.a.run.app/... rather that the custom url is is correctly hosted at using firebase hosting https://my-app.com/... How is it getting this url? Can we just adjust this manually? Thanks!

Hi, have you set the SERVER_NAME config variable in flask?

Yeah I've set it to https://my-app.com

Given that sitemapper uses url_for(), It might be useful to know that whenever I use url_for() in the app, I need to use url_for(auth.login) rather than url_for("/login"), otherwise I get redirected to the cloudrun url.
auth_bp = Blueprint("auth", __name__)

@auth_bp.route("/login", methods=["GET", "POST"])
def login():
    ....

Flask Sitemapper uses url_for with the endpoint name to generate the sitemaps URLs.
auth_bp = Blueprint("auth", __name__)

@sitemapper.include()
@auth_bp.route("/login", methods=["GET", "POST"])
def login():
    ....

In this example, the URL for the sitemap will be generated by:
flask.url_for("auth.login", _external=True, _scheme="https")

It seems that this approach does not work with your hosting method. This stack overflow question seems to be about the same issue and it was suggested that a workaround be used by creating a BASE_CONFIG config variable. Unfortunately, this approach will not work without changes to Flask Sitemapper's source code (although it should work elsewhere).
However, a workaround could be done by including some extra code when you call sitemapper.generate(). For example:
@app.route("/sitemap.xml")
def sitemap():
  response = sitemapper.generate()

  # modify xml
  xml = response.get_data()
  xml.replace("wrong_domain.com", "right_domain.com")

  # use modified xml
  response.set_data(xml)

  return response

Thanks! That's a pretty easy workaround and will do for my needs


[Turbo] Allowing version 8

Q
A

Bug fix?
no

New feature?
yes

Issues
None

License
MIT

Turbo 8 is now beta! This allows Turbo 8 to be installed. There are no BC breaks that would affect us that i'm aware of, which is not surprising as we do very little with Turbo other than supply it to the user.
Once we merge and release this, users installing TurboBundle will get v8 by default, even while in beta stage. From AssetMapper's perspective, that happens because https://data.jsdelivr.com/v1/packages/npm/@hotwired/turbo/resolved already selects beta. I can't find any specifier - e.g. https://data.jsdelivr.com/v1/packages/npm/@hotwired/turbo/resolved?specifier=stable that selects the latest, non-beta version.
Cheers!

We could make a first call to fetch the releases
https://data.jsdelivr.com/v1/packages/npm/@hotwired/turbo?specifier=stable

Turbo 8 is out!


Rudimentary broken pixels treatment

Fill pixel_status in SimTelEventSource
Ignore broken pixels in GlobalPeakWindowSum and NeighborPeakWindowSum extractors
Interpolate images and peak_time of broken pixels in CameraCalibrator using a simple average of their neighbors

Before:

After:

Those are normally computed after charge extraction, but before parameterization.

Those are computed from interleaved pedestals, and the information about current interleaved pedestal monitoring will be available in the current physics event exactly at this position (pedestal_failing_pixels), right?

Ignore broken pixels in GlobalPeakWindowSum and NeighborPeakWindowSum extractors

Looks like also TwoPassWindowSum as well

Those are computed from interleaved pedestals, and the information about current interleaved pedestal monitoring will be available in the current physics event exactly at this position (pedestal_failing_pixels), right?

Yes, I would imagine that was the intent there. Maybe the name is not great (it sounds more like pixels where a pedestal could not be computed, rather than where the pedestal variance is too high or too low).

Looks like also TwoPassWindowSum as well

Not exactly. The broken_pixels argument had to be added to all extractors, because they share a common API. But only the two extractors mentioned make actual use of this information.

Not exactly. The broken_pixels argument had to be added to all extractors, because they share a common API. But only the two extractors mentioned make actual use of this information.

Then shouldn't TwoPass also use it? In computing the time gradient in the first pass, broken pixels should be ignored.

Then shouldn't TwoPass also use it? In computing the time gradient in the first pass, broken pixels should be ignored.

Ignored? Or should I add the interpolation?

, especially when there are large regions of broken pixels like a full module or more where it could do more harm than good

Pixels where no valid neighbors are found are set to 0

which to my mind means that this should be a separate step in the CameraCalibrator

It is, the interpolation happens in CameraCalibrator. The extractors combining multiple pixels however need to be able to ignore broken pixels.

Perhaps BrokenPixelInpainter (since interpolation is only one way to do it). That way we can also include other types of broken pixel in the inpainting.

I started with a Component, then removed it again... The idea here was to start simple and adding another component that needs to have the API __call__(event) and does a loop over the telescope events was not something I found attractive.
It all should get better with the ArrayEventContainer -> TelescopeEventContainer -> [DL0, DL1, DL2,MON] structure, since then these components concerned with telescope calibration don't have a loop inside and can just take the single telescope event.

I think it would only be necessary to interpolate the second pass. The first pass just determines the time gradient used for charge extraction - there just skipping broken pixels should be fine.

That's actually not how it works.
The first pass is just a simple integration for each pixel with some hard coded behavior to make it work exactly like MARS. Which makes it a bit ugly. But since no global or neighbor information is used here, nothing to worry about for the broken pixels.
The second pass starts with the parametrization of the first pass result. It applies a cleaning, thus using neighbor information.
So my strategy would be to add the interpolation in the second pass before the parametrization.
Like this, if only the first pass is used, the interpolation happens in CameraCalibrator for all pixels. If both passes are used, the cleaning and parametrization actually handle the broken pixels but the broken pixels are extracted again. Then the final result is interpolated in CameraCalibrator.

An alternative for now would be to use a TelescopeComponent with API __call__(self, tel_id, image, peak_time, broken_pixels).
I can change to that.

@kosack I introduced the component (I had to also move it to ctapipe.image otherwise there would have been a circular import.
I think it also makes sense there and we have anyways this issue here: https://github.com/cta-observatory/ctapipe/issues/1037


[Bug report]: Angular with esbuild fails

Requirements before reporting

[X] No duplicated issue reported.
[X] I have checked the latest version if the bug exist there. See all available packages at npmJS.com
[X] I have followed the installation guide.

Package versions
@scania/tegel-angular: 1.7.0
Framework
Angular
Version
Angular 16+
Reproduction steps

Create or use an angular project that uses esbuild. This is default in Angular 17.
Import @scania/tegel-angular and use a tegel component.
Build the project, ng build --verbose

Then we get the following error
Could not resolve "@scania/tegel-angular"
Reproduction repo exists here: https://github.com/adarean5/tegel-angular-esbuild-issue-repro
Code example
....
Screenshots

Expected behaviour
It should be possible to use @scania/tegel-angular with esbuild.
Contact information
<EMAIL_ADDRESS>

Issue is resolved in @scania/tegel-angular-17


[Bug] TEST_P related tests are very flaky with paralle tests

Search before asking

[X] I searched in the issues and found nothing similar.

Version
master after #54
Minimal reproduce step
Run ShutdownTest in parallel
python3 ./gtest_parallel.py --dump_json_test_results=/tmp/gtest_parallel_results.json \
  --workers=4 --retry_failed=2 -d /tmp \
  ./tests/pulsar-tests --gtest_filter='*ShutdownTest*'

What did you expect to see?
All tests passed.
What did you see instead?
FAILED TESTS (8/6):
     192 ms: ./tests/pulsar-tests Pulsar/ShutdownTest.testDestructor/1 (try #1)
     190 ms: ./tests/pulsar-tests Pulsar/ShutdownTest.testDestructor/2 (try #1)
     190 ms: ./tests/pulsar-tests Pulsar/ShutdownTest.testClose/2 (try #1)
     129 ms: ./tests/pulsar-tests Pulsar/ShutdownTest.testDestructor/2 (try #2)
     128 ms: ./tests/pulsar-tests Pulsar/ShutdownTest.testClose/2 (try #2)
     134 ms: ./tests/pulsar-tests Pulsar/ShutdownTest.testDestructor/1 (try #2)
     106 ms: ./tests/pulsar-tests Pulsar/ShutdownTest.testDestructor/2 (try #3)
     117 ms: ./tests/pulsar-tests Pulsar/ShutdownTest.testClose/2 (try #3)

Anything else?
It's because gtest-parallel runs tests in different processes, not threads. So the topic name could be the same even if it has the timestamp suffix. We can see it from the logs:
2022-10-21 10:42:06.749 ERROR [140341161174784] MultiTopicsConsumerImpl:449 | Closing the consumer failed for partition - persistent://public/default/shutdown-test-0-1666320126-partition-0 with error - AlreadyClosed
2022-10-21 10:42:06.849 ERROR [140219768280832] MultiTopicsConsumerImpl:449 | Closing the consumer failed for partition - persistent://public/default/shutdown-test-0-1666320126-partition-1 with error - AlreadyClosed

Are you willing to submit a PR?

[X] I'm willing to submit a PR!

It's also the cause of #24


Fix coverage reporting

Right now pipeline which reports coverage to coverall.io is broken. Need to find a good, lightweight pipeline runner and resurrect the coverage.

Try GitHub Actions


Update CharacterUtility for 7.0

I can't see where you found that 114 number, but I do see it is higher now, so guess it's just in a function that isn't part of the vtable


fix: trying to validate non-hardhat contracts

The reported error on (#255) happens when you are on a hardhat project, but open a contract that doesn't belong to the project's dependency graph. This PR aborts the build if that's the case.
Closes #255

Codecov Report

:exclamation: No coverage uploaded for pull request base (development@daa19c2). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head 64a9920 differs from pull request most recent head 20c20a0. Consider uploading reports for the commit 20c20a0 to get more accurate results

@@              Coverage Diff               @@
##             development     #260   +/-   ##
==============================================
  Coverage               ?   70.27%
==============================================
  Files                  ?      170
  Lines                  ?     4128
  Branches               ?      725
==============================================
  Hits                   ?     2901
  Misses                 ?      991
  Partials               ?      236

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Based on discussion with @alcuadrado, we want to edit the validation within the worker to add a pre-compile task check to determine whether the current file path is in the dependency graph (that it is a hardhat project file). If it is not we return an error and display a useful error message. @armando

Based on discussion with @alcuadrado, we want to edit the validation within the worker to add a pre-compile task check to determine whether the current file path is in the dependency graph (that it is a hardhat project file). If it is not we return an error and display a useful error message. @Armando

What error message should we show and how should we display it ? (I'm thinking status bar item but want to be sure)

Based on discussion with @alcuadrado, we want to edit the validation within the worker to add a pre-compile task check to determine whether the current file path is in the dependency graph (that it is a hardhat project file). If it is not we return an error and display a useful error message. @Armando

What error message should we show and how should we display it ? (I'm thinking status bar item but want to be sure)

Status bar item for the message - like our other "problem with validation process" type errors. There is no import line to link it back to so no sense in which we can have a diagnostic.
For the message, maybe something like "Not part of Hardhat project". Do you think adding a link to the docs explaining the layout would work?

@kanej Updated PR


The upload flag of cosign initialize is not used

cosign initialize has an upload flag which is supposed to set a threshold of root key signers and has default value 3. Currently this value is not used in any way because we always take the root threshold of the local repo and use this number to update from the remote one.
I propose to change the name of the flag from upload to threshold and use it to override the root threshold when updating from the remote TUF repo. I believe this was the original intent of this flag.

After discussion with @asraa we decided to simply delete this flag (PR #1201)


Add a report showing number of issues/PRs with label

Given a standard set of labels, add a report that shows the number of issues/PRs open under each label per repo.

Got a lot of this written. Bugs to work out and a design issue in how to define the columns for generate-dashboard without having access to a context.

Added in fdcfa0d5833cee5a2a595ebe8d62f16ff62fd0d9