Not finding linux pact mock service on centos 7

I was previously using nodejs 4.3.2 on a centos 7 linux box running jenkins.
Since I've updated to nodejs 8.3.0, I can't seem to be able to require @pact-foundation/pact-node.
I get the following error:
Warning: Cannot find module '@pact-foundation/pact-mock-service-linux-x64' Use --force to continue.

I tried with @pact-foundation/pact-node version v4.8.1 and v4.12.0 (latest).
I first noticed the problem with karma-pact, but the problem happens in another repo where I don't use karma-pact.

Update, not related to nodejs v8.3.0 (unless it doesn't happen all the time).
I'm now able to load pact-node when I revert it to v4.8.1, so maybe just a problem with this v4.12.0.
Hope that helps.

Sorry another update, really hard to track what's going on.
I had the error once with nodejs v8.3.0 and and pact-node v4.8.1, so it is related to the latest nodejs version as I've never had it before, just not happening all the time.
The failure happens in a grunt task that looks like in case it is relevant:
grunt.registerTask('pact-service', 'Start pact mock service', function () {
        var done = this.async();
        var path = require('path');
        var pactWrapper = require('@pact-foundation/pact-node');

As you may have guessed, we use optional dependencies to pull down dynamically (install time) the correct OS-specific package, in this case linux 64 bit. It's common to see that warning, but of course if it doesn't install one of the packages things won't work!
Are you able to please enable detailed logging for the npm install step (forgotten how off the top of my head) and share a gist of the output? That might help us track it down.
FWIW we currently test Pact Nnode with whatever TravisCI provides, currently v8.2.1.

OS: Linux Centos 7
Nodejs: v8.3.0
NPM: 5.3.0
Pact-node: 4.8.1
You can find 2 log files in this gist, a npm install verbose and the jenkins job where the following error appears:
Error: Cannot find module '@pact-foundation/pact-mock-service-linux-x64'

https://gist.github.com/soundstep/e8c1b72707fa18a041e591b7ed7b543b
Hope that helps!

This is probably because if the way pact node tries to discover the os
specific version. I should have time to fix this tomorrow and try out node
8.
On Mon., 14 Aug. 2017, 11:03 pm Romuald Quantin<EMAIL_ADDRESS>wrote:

OS: Linux Centos 7
Nodejs: v8.3.0
NPM: 5.3.0
Pact-node: 4.8.1
You can find 2 log files in this gist, a npm install verbose and the
jenkins job where the following error appears:
Error: Cannot find module '@pact-foundation/pact-mock-service-linux-x64'
https://gist.github.com/soundstep/e8c1b72707fa18a041e591b7ed7b543b
Hope that helps!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pact-foundation/pact-node/issues/42#issuecomment-322184180,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjA5HbvxKpnrY0UoxDPkUf0l-BbICTiks5sYEWogaJpZM4O2Les
.

Hi @mboudreau
Funny thing is that sometimes it is working, it is 50/50 I would say in our pipeline. There must be some timings involved? Did you see anything wrong in these logs?
Let me know if you guys can reproduce.

I'll look into it and report back.  There shouldn't be any "timing"
involved with the dependency, but there is a timeout in case the executable
doesn't spin up.  It would be helpful if you are to produce a dockerfile
that means me reproduce the issue.  Thanks.
On Tue, Aug 15, 2017 at 5:17 PM Romuald Quantin<EMAIL_ADDRESS>wrote:

Hi @mboudreau https://github.com/mboudreau
Funny thing is that sometimes it is working, it is 50/50 I would say in
our pipeline. There must be some timings involved? Did you see anything
wrong in these logs?
Let me know if you guys can reproduce.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pact-foundation/pact-node/issues/42#issuecomment-322394664,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjA5BZnQbQBMK4PQRCnQog3xHn4snIWks5sYUYVgaJpZM4O2Les
.

I'll make to make some time to try to reproduce the problem with a simple example. Meanwhile if you find the problem, let me know ;)

Another update, I reproduced the problem on this Centos 7 instance fairly easily with these files:
https://gist.github.com/soundstep/8989b6c1c431458c8e4da3a9d0bfe8ba
I tried to dockerize it, but I can't reproduce the problem at all.
Seems to be related to speed, timing, execute timing, race condition or something similar?
The linux instance is a 4 CPU core (Intel(R) Xeon(R) CPU E5-2680 v2 @ 2.80GHz), with 8BG of RAM, so pretty beefy.
I'm going to have a go on other Centos 7 instances, and in vagrant on my local machine.
Can you give some details on how you do the os detection? Maybe a small script that I can try out?
CentOS Linux release 7.3.1611 (Core)
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

CentOS Linux release 7.3.1611 (Core)
CentOS Linux release 7.3.1611 (Core)

Here is the error it generates BTW:
    throw err;
    ^

Error: Cannot find module '@pact-foundation/pact-mock-service-linux-x64'
    at Function.Module._resolveFilename (module.js:489:15)
    at Function.Module._load (module.js:439:25)
    at Module.require (module.js:517:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/home/romuquan/test-centos-pact/node_modules/@pact-foundation/pact-mock-service/index.js:7:18)
    at Module._compile (module.js:573:30)
    at Object.Module._extensions..js (module.js:584:10)
    at Module.load (module.js:507:32)
    at tryModuleLoad (module.js:470:12)
    at Function.Module._load (module.js:462:3)```

Thanks @soundstep - I wish all bug reports came with as much info! This should enable us to get to the bottom of it.

@soundstep you are an absolute champ! Looking at the problem now.

@soundstep I'm 90% sure this has nothing to do with node, but instead npm. As part of the install step, it tries to install an OS specific binary of the pact mock service.  By default, it tries to download all of them, but npm will ignore all of them except for one because of the package restrictions (must be on "linux" and have architecture "x64").  I'm guessing that something might have changed in npm that makes it think that centos is not linux or that the architecture is wrong.  I'm digging in further by using a centos image on my virtualbox since it seems to work in docker (weird!) and can't reproduce.

@soundstep erm, I can't seem to be able to reproduce your issue using the centos7 image in Virtualbox.  Every time I run node, it seems to find the pact-mock-service correctly.  However, I did notice that in your gist, you seem to be ignoring the npm install step (as per what is in your output), which is quite important or else it won't get the OS specific binaries needed.

Npm install is not there? I did test manually though. I will re-check today
and keep you posted.
Your guess sounds right about npm, did you notice anything special in the
verbose log in the first gist?
On 16 Aug 2017 04:09, "Michel Boudreau"<EMAIL_ADDRESS>wrote:

@soundstep https://github.com/soundstep erm, I can't seem to be able to
reproduce your issue using the centos7 image in Virtualbox. Every time I
run node, it seems to find the pact-mock-service correctly. However, I did
notice that in your gist, you seem to be ignoring the npm install step
(as per what is in your output), which is quite important or else it won't
get the OS specific binaries needed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pact-foundation/pact-node/issues/42#issuecomment-322654620,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIIrRfFNqv9_vZ-kZnWkGnUYHRCsd2aks5sYl14gaJpZM4O2Les
.

From your gist:
[vagrant@ie11win7 app]$ node -v
v8.3.0
[vagrant@ie11win7 app]$ node index.js
module.js:491
    throw err;
    ^

Error: Cannot find module '@pact-foundation/pact-mock-service-linux-x64'
    at Function.Module._resolveFilename (module.js:489:15)
    at Function.Module._load (module.js:439:25)
    at Module.require (module.js:517:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/app/node_modules/@pact-foundation/pact-mock-service/index.js:7:18)
    at Module._compile (module.js:573:30)
    at Object.Module._extensions..js (module.js:584:10)
    at Module.load (module.js:507:32)
    at tryModuleLoad (module.js:470:12)
    at Function.Module._load (module.js:462:3)

Which seems to be missing npm install step in there. Either way, I can't seem to be able to reproduce it with centos7 using your exact steps.  I didn't end up using vagrant however since it shouldn't matter just to run a few steps.

I was not able to reproduce in docker either, that's why I tried vagrant.
Docker is not fully emulating an os, as the kernel is shared with your
local computer. Our DevOps never use docker to debug os related problem for
that very reason.
I will test again once I get to the office and keep you posted.
On 16 Aug 2017 07:47, "Michel Boudreau"<EMAIL_ADDRESS>wrote:

From your gist:
[vagrant@ie11win7 app]$ node -v
v8.3.0
[vagrant@ie11win7 app]$ node index.js
module.js:491
throw err;
^
Error: Cannot find module '@pact-foundation/pact-mock-service-linux-x64'
at Function.Module._resolveFilename (module.js:489:15)
at Function.Module._load (module.js:439:25)
at Module.require (module.js:517:17)
at require (internal/module.js:11:18)
at Object. (/app/node_modules/@pact-foundation/pact-mock-service/index.js:7:18)
at Module._compile (module.js:573:30)
at Object.Module._extensions..js (module.js:584:10)
at Module.load (module.js:507:32)
at tryModuleLoad (module.js:470:12)
at Function.Module._load (module.js:462:3)
Which seems to be missing npm install step in there. Either way, I can't
seem to be able to reproduce it with centos7 using your exact steps. I
didn't end up using vagrant however since it shouldn't matter just to run a
few steps.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pact-foundation/pact-node/issues/42#issuecomment-322681693,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIIrYVAbml8tk1HNm9KpQQA6FDgi04Sks5sYpCDgaJpZM4O2Les
.

Yep, hence why I installed centos on a VM and tried it there, but still wasn't able to reproduce it.

You're right, I cannot reproduce it this morning, I must have done some wrong.
I'm re-testing on the original box and I see logs like this:
[romuquan@jenkins test-centos-pact]$ npm install

><EMAIL_ADDRESS>install /home/romuquan/test-centos-pact/node_modules/dtrace-provider
> node scripts/install.js

><EMAIL_ADDRESS>postinstall /home/romuquan/test-centos-pact/node_modules/@pact-foundation/pact-mock-service
> node ./src/check-dependencies.js

[2017-08-16T08:08:32.065Z] ERROR<EMAIL_ADDRESS>on 10ft-infradev-aeuw1-jenkins-0cb3d3354739239a8: pact-node: Cannot resolve OS specific pact module. Download/install must of failed, please try again.
npm WARN<EMAIL_ADDRESS>No repository field.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: `node ./src/check-dependencies.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!  There is likely additional logging output above.
4670 verbose exit [ 1, true ]

Yeah, that happens when none of the optional dependencies has been
installed.  We have a postinstall script to make sure that the optional
dependency has been downloaded.  Could you run npm install -ddd to see
all logs of what's going on behind the scenes?
On Wed, Aug 16, 2017 at 6:24 PM Romuald Quantin<EMAIL_ADDRESS>wrote:

You're right, I cannot reproduce it this morning, I must have done some
wrong.
I'm re-testing on the original box and I see logs like this:
[romuquan@jenkins test-centos-pact]$ npm install

<EMAIL_ADDRESS>install /home/romuquan/test-centos-pact/node_modules/dtrace-provider
node scripts/install.js

<EMAIL_ADDRESS>postinstall /home/romuquan/test-centos-pact/node_modules/@pact-foundation/pact-mock-service
node ./src/check-dependencies.js

[2017-08-16T08:08:32.065Z] ERROR<EMAIL_ADDRESS>on 10ft-infradev-aeuw1-jenkins-0cb3d3354739239a8: pact-node: Cannot resolve OS specific pact module. Download/install must of failed, please try again.
npm WARN<EMAIL_ADDRESS>No repository field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: node ./src/check-dependencies.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!  There is likely additional logging output above.
4670 verbose exit [ 1, true ]
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pact-foundation/pact-node/issues/42#issuecomment-322701388,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjA5C6ZELoF66aeOmZ--HSHfzx7VWFCks5sYqdWgaJpZM4O2Les
.

The problem is, it is not all time, so it is kind of hard to reproduce.
I was always wondering why it says<EMAIL_ADDRESS>on 10ft-infradev-aeuw1-jenkins-0cb3d3354739239a8: Platform specific dependency '@pact-foundation/pact-mock-service-darwin' installed successful on a linux system.
Silly question but... could this be related to network problem somehow?
When I see:
[2017-08-16T08:08:32.065Z] ERROR<EMAIL_ADDRESS>on 10ft-infradev-aeuw1-jenkins-0cb3d3354739239a8: pact-node: Cannot resolve OS specific pact module. Download/install must of failed, please try again.

Could it be a download that fails for some reason?
Still investigating but right now it is working, I'll try a bit later, I know the problem is still there.

yeah, I did see that today as well.  I'm not too sure what's going on
because when I actually look at the folders, there's nothing there for
'darwin' only 'linux-x64', however, this chat has sparked an idea in my
head that I'll have to check out tomorrow morning.
On Wed, Aug 16, 2017 at 7:16 PM Romuald Quantin<EMAIL_ADDRESS>wrote:

The problem is, it is not all time, so it is kind of hard to reproduce.
I was always wondering why it says<EMAIL_ADDRESS>on
10ft-infradev-aeuw1-jenkins-0cb3d3354739239a8: Platform specific dependency
'@pact-foundation/pact-mock-service-darwin' installed successful on a
linux system.
Silly question but... could this be related to network problem somehow?
When I see:
[2017-08-16T08:08:32.065Z] ERROR<EMAIL_ADDRESS>on 10ft-infradev-aeuw1-jenkins-0cb3d3354739239a8: pact-node: Cannot resolve OS specific pact module. Download/install must of failed, please try again.
Could it be a download that fails for some reason?
Still investigating but right now it is working, I'll try a bit later, I
know the problem is still there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pact-foundation/pact-node/issues/42#issuecomment-322713576,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjA5KTl8d82DeiCmM2IxhPQNaYJDMuJks5sYrNsgaJpZM4O2Les
.

I suppose it could be @soundstep . I've just spun up a clean centos ec2 64 bit instance with your steps:
curl --silent --location https://rpm.nodesource.com/setup_8.x | sudo bash -
sudo yum -y install nodejs
npm install pact
<EMAIL_ADDRESS>
Worked a charm.
I'm wondering if as you say, it could be network related or something else.  It might be worth attempting an install of a different version of pact-node to  work around any potential caching, or even running outside of your work network just to rule it out.
FWIW I recently had issues behind a corporate proxy and had to make a few adjustments to a dockerfile to make it work:
npm config set maxsockets 5
npm config set registry http://registry.npmjs.org/
npm config set strict-ssl false

There's a post somewhere that mentions npm seems to be a load testing tool for routers...

Right interesting @mefellows !
I'm trying to gather a bit more logs.
Do you guys mind check that one: https://gist.github.com/soundstep/68e47a96f784abb08104aacba4d32089
It looks like it has installed the pact=mock-service for darwin, while this is happening on the Centos 7 machine.
Am I reading the logs wrong?

@soundstep no, you're definitely on the right track, those logs are saying that it is downloading the darwin version, which is weird.  I'll investigate further, but I'm not sure why you're seeing it consistently while I can run pact without a hitch on the latest centos7.

Actually, it is not consistently, it is like 50/50. Sometimes it works, sometimes it doesn't.
I think I've noticed that starting from a clean workspace (no node_modules folder), it will always fail. Then re-running a job on the same workspace (with a previous node_modules), it sometimes work.

Note that we are also using a private npm registry on artifactory, I hope it has nothing to do with that and some sort of caching. Actually, I can use the normal npm registry on this project, I will disable it just to make sure!

@soundstep hm, artifactory caching might be the cause.  Kinda hard to reproduce on my end ;)

@mboudreau nevermind, it is not used on this project. I'll double check the npmrc file is correct, just to make sure.

I think I finally understood what's happening: the package-lock.json file!
We are developing on MacOS computer, and sadly, pushing the package-lock.json file to our repo.
This makes NPM install the darwin version of the pact-mock-service on the linux machine, as it has been stored in the lock file.
Here is what show in the package-lock:
"dependencies": {
    "@pact-foundation/pact-mock-service": {
      "version": "0.10.2",
      "resolved"<EMAIL_ADDRESS>      "integrity": "sha1-LukJYpZNyk86HEgw4Fd7/GGtgKk=",
      "requires": {
        "@pact-foundation/pact-mock-service-darwin": "0.10.2",
        "bunyan": "1.8.12",
        "bunyan-prettystream": "0.1.3"
      }
    },
    "@pact-foundation/pact-mock-service-darwin": {
      "version": "0.10.2",
      "resolved"<EMAIL_ADDRESS>      "integrity": "sha1-Wphp1pr8Z8hbkDOEmGmRJBuHXok=",
      "optional": true
    },

So there is no bug in pact-node, which is great news but I think it is a little weakness with the optionalDependencies field.
We are used to push Gemfile.lock file to our repo because it is a good thing, so we thought it would be the same thing for node. I think I will now add the package-lock.json file in our .gitignore.
I will link this issue to npm just so they think about this issue.
Bottom line, thank you guys for the help, you were so responsive, you're awesome ;)

@soundstep No way! Of course I forgot about that since it's a new thing for npm 5. I definitely recommend you add the package.lock file to your .gitignore and delete it from the repo as not only is this going to cause issues with your build server, but any person trying to develop on your project that's not on a mac.
Thanks for bearing with us and giving us an abundant amount of info to help us debug. Don't hesitate to bring up more bugs if you're always going to be this thorough ;)

Great spot!!
Hmm this is another pain point. It's good practice to check in the
package-lock.json so recommending against this approach is not something
I'm a fan of. IMO we should consider removing the optional dependencies.
I'd rather see us pull down the correct binaries to install during the post
install phase instead.
We could then also get rid of the other packages (mock service and
verifier) , something that's a frustrating aspect of our release process.
We then just have two components - pact-node (engineer wrapper) and pact
(the dsl).
Thoughts?
On Aug 17, 2017 9:26 PM, "Michel Boudreau"<EMAIL_ADDRESS>wrote:

@soundstep https://github.com/soundstep No way! Of course I forgot
about that since it's a new thing for npm 5. I definitely recommend you add
the package.lock file to your .gitignore and delete it from the repo as not
only is this going to cause issues with your build server, but any person
trying to develop on your project that's not on a mac.
Thanks for bearing with us and giving us an abundant amount of info to
help us debug. Don't hesitate to bring up more bugs if you're always going
to be this thorough ;)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pact-foundation/pact-node/issues/42#issuecomment-323043367,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADSjJVKyzhrEFVAoFtKepIHjRZTBHFkks5sZCNigaJpZM4O2Les
.

The only other possibility is to load all OS specific dependencies, which
is then required based on the runtime, but this makes the install process
heavy since we're now installing all binaries.  Postinstall process won't
work since it isn't triggered on npm update, which can cause some
versioning issues.
On Thu, Aug 17, 2017 at 9:38 PM Matt Fellows<EMAIL_ADDRESS>wrote:

Great spot!!
Hmm this is another pain point. It's good practice to check in the
package-lock.json so recommending against this approach is not something
I'm a fan of. IMO we should consider removing the optional dependencies.
I'd rather see us pull down the correct binaries to install during the post
install phase instead.
We could then also get rid of the other packages (mock service and
verifier) , something that's a frustrating aspect of our release process.
We then just have two components - pact-node (engineer wrapper) and pact
(the dsl).
Thoughts?
On Aug 17, 2017 9:26 PM, "Michel Boudreau"<EMAIL_ADDRESS>wrote:

@soundstep https://github.com/soundstep No way! Of course I forgot
about that since it's a new thing for npm 5. I definitely recommend you
add
the package.lock file to your .gitignore and delete it from the repo as
not
only is this going to cause issues with your build server, but any person
trying to develop on your project that's not on a mac.
Thanks for bearing with us and giving us an abundant amount of info to
help us debug. Don't hesitate to bring up more bugs if you're always
going
to be this thorough ;)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<
https://github.com/pact-foundation/pact-node/issues/42#issuecomment-323043367
,
or mute the thread
<
https://github.com/notifications/unsubscribe-auth/AADSjJVKyzhrEFVAoFtKepIHjRZTBHFkks5sZCNigaJpZM4O2Les
.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pact-foundation/pact-node/issues/42#issuecomment-323045887,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjA5L_BTT36kTkKxn8780NNTynlZn-iks5sZCYYgaJpZM4O2Les
.

What I would recommend is that you install/download/build the os specific stuff during an npm rebuild, which happen during an npm install (npm build).
https://docs.npmjs.com/cli/rebuild
That's what lib-sass is doing for example. if you switch machine or node version, they log a message like "Please execute npm rebuild lib-sass".
Another example, it is considered a good practice when building nodejs micro-services using RPM, to have the node_modules folder included in the RPM (as it should be self-contained). So people usually trigger a npm rebuild when they update their services on linux, as the RPM might be built on another type of machine. Like this guy there: https://github.com/bbc/speculate#install-your-dependencies-first
Point is, if you execute npm rebuild, it should re-download or re-build anything that is os-specific.
I think it makes sense.

Good points, I'll have to look into that.
On Thu, Aug 17, 2017 at 10:04 PM Romuald Quantin<EMAIL_ADDRESS>wrote:

What I would recommend is that you install/download/build the os specific
stuff during an npm rebuild, which happen during an npm install (npm
build).
https://docs.npmjs.com/cli/rebuild
That's what lib-sass is doing for example. if you switch machine or node
version, they log a message like "Please execute npm rebuild lib-sass".
Another example, it is considered a good practice when building nodejs
micro-services using RPM, to have the node_modules folder included in the
RPM (as it should be self-contained). So people usually trigger a npm
rebuild when they update their services on linux, as the RPM might be
built on another type of machine. Like this guy there:
https://github.com/bbc/speculate#install-your-dependencies-first
Point is, if you execute npm rebuild, it should re-download or re-build
anything that is os-specific.
I think it makes sense.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pact-foundation/pact-node/issues/42#issuecomment-323052092,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjA5KOxPxoZUTWx9VWe1qcnKzQd6c6mks5sZCwugaJpZM4O2Les
.

We heavily use pact in production, so I'll definitely be there if we find issues ;)
We fixed a few in the ruby pact-mock-service, we also made https://github.com/ITV/scala-pact

@soundstep I was on a mobile before, but I was essentially trying to say the same thing. We don't actually go through the same compile as saas does however (which does a native compile with node-gyp), but it is analogous.
I think it's acceptable to force an npm reinstall for this if an update is required. If angular cli can get away with it -

rm -rf node_modules dist
rm -r -fo node_modules,dist in Windows PowerShell
npm install --save-dev @angular/cli@latest
npm install

then surely we can too!

Also, we love the work you guys (including Dave) have done at ITV!

@mefellows I don't think having to re-do an npm install is the solution, that's why I specifically gave you the other example with the node micro-service bundle in an RPM. They are supposed to be ready-to-use and self-contained.
You would never do an npm install in a production environment, that's not how softwares should be deployed, especially not relying on network or npm registry. Ideally, it should rely on nothing so that your deployment is the safest possible.
What I mean is, you should be able to deploy a node app without accessing to the network. The only thing you need to do is a npm rebuild to satisfy os-dependencies, things that can't be done outside of the actual environment.
You could argue that pact-node is a build tool and wouldn't be used that way, that's fine. But I would still do it the right way, who knows how pact-node should be used and you should actually not ncare about that.
What would be the problem in getting the right pact-mock-service in a preinstall script for example?
If you run a npm rebuild, the preinstall script and others will be re-executed.
"scripts": {
    "preinstall": "get my correct pact-mock-service dependency"

Hope that helps!

Agree with all of those points. Provided the install hooks fire as it says
on the label this should be easy, there should be no problem..
We just need to try it out and test it is all I'm saying.
On Aug 18, 2017 7:20 PM, "Romuald Quantin"<EMAIL_ADDRESS>wrote:
@mefellows https://github.com/mefellows I don't think having to re-do an npm
install is the solution, that's why I specifically gave you the other
example with the node micro-service bundle in an RPM. They are supposed to
be ready-to-use and self-contained.
You would never do an npm install in a production environment, that's not
how softwares should be deployed, especially not relying on network or npm
registry. Ideally, it should rely on nothing so that your deployment is the
safest possible.
What I mean is, you should be able to deploy a node app without accessing
to the network. The only thing you need to do is a npm rebuild to satisfy
os-dependencies, things that can't be done outside of the actual
environment.
You could argue that pact-node is a build tool and wouldn't be used that
way, that's fine. But I would still do it the right way, who knows how
pact-node should be used and you should actually not ncare about that.
What would be the problem in getting the right pact-mock-service in a
preinstall script for example?
If you run a npm rebuild, the preinstall script and others will be
re-executed.
"scripts": {
"preinstall": "get my correct pact-mock-service dependency"
Hope that helps!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pact-foundation/pact-node/issues/42#issuecomment-323304271,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADSjOMhMS2zMfVK47pK8NlSeVNfH37Yks5sZVdVgaJpZM4O2Les
.

@mefellows Yep, just checked it, the preinstall script is executed on npm rebuild, thus npm intall.
You should all fine with that!
Cheers.

Great! One thing to note is that we will require network access in this
phase to pull down the OS specific bundle.
But whichever way you look at it, it's better than the current situation.
On Aug 18, 2017 7:46 PM, "Romuald Quantin"<EMAIL_ADDRESS>wrote:
@mefellows https://github.com/mefellows Yep, just checked it, the
preinstall script is executed on npm rebuild, thus npm intall.
You should all fine with that!
Cheers.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pact-foundation/pact-node/issues/42#issuecomment-323310338,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADSjD4A-YtVvPJHMhIL4udh_W3CzkaRks5sZV2FgaJpZM4O2Les
.

Yeah good point. Can't really help with that I guess.
And I guess the pact-mock-service are big enough so that you can't include them all?

Exactly. Longer term we will probably be able to compile in this step
though.
On Aug 18, 2017 8:13 PM, "Romuald Quantin"<EMAIL_ADDRESS>wrote:
Yeah good point. Can't really help with that I guess.
And I guess the pact-mock-service are big enough so that you can't include
them all?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pact-foundation/pact-node/issues/42#issuecomment-323316137,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADSjJcMteWlhKxsp-7Gv8vn0xXc2021ks5sZWPQgaJpZM4O2Les
.

finally got one of my projects that uses pact-node upgraded to node 8 and ran into this problem. i do not agree with the recommendation to ignore the lockfile since the whole point of the lockfile is to keep package versions consistent across machines.
i tried to run the npm rebuild on travis, but (i assume) since i was still versioning the lockfile, i got
pact-node: Cannot resolve OS specific pact module. Download/install must of failed, please try again.

i was able to get the travis build to work by running npm install @pact-foundation/pact-mock-service-linux-x64 as a before_script step on travis. this works for my team since we are all developing on osx, but i'm not sure how to solve this with the current approach for teams that have developers across OSs.
it looks like npm 5 doesnt support this type of approach very well yet, but it looks like you've got things set up correctly for when it does, at least from what i understand. might be worth keeping track of issues like:

https://github.com/npm/npm/issues/17519

Thanks @travi, there's a bit of work for us to get to our optimal solution, and your workaround seems appropriate for now. I'm watching both of those issues to see if our recommendation changes, but in any case I feel the optional dependencies approach needs to be revised.

I'm also hitting this problem with a dockerised build. I'll try @travi's workaround.

Thanks Tim - we're working on it, we promise!

FYI see https://github.com/pact-foundation/pact-js/issues/91 (on our project board for a proposal with options related to this issue and beyond. Thoughts welcome!

@mefellows @travi @soundstep
After some though, the rebuild option simply will not work for our purpose as we need npm's internals to install our binary and packages properly using npm link and should be resolvable using require.resolve.  If we are to use npm rebuild, many of these things won't happen.  Package structures can get screwy between npm versions, hence the need for require.resolve.  I had tried the rebuild option (originally just a postinstall with npm install in it) when I originally made this package, but problems arose with the new flat structure of npm and that it might revert back to a hierarchical one depending on context.  The other issue is that it would actually download and install the package every time npm install was ran, meaning it's not a normal one-off situation.
Using optionalDependencies was the best solution from a developer experience standpoint, and now npm seems to have made our lives difficult again with changing how it works under the covers with package-lock.json file not support a core feature of npm.
As far as I'm concerned, this is not a pact-node issue, but an npm issue: https://github.com/npm/npm/issues/18135
Only way to properly fix this would be to include all binaries of all OS in a single package, then have a simple script that checks the user's OS and use the correct binary when pact-node is used.  Can't say I like the idea of having pact-node be ~28mb for each download, but if we have no choice...

@mboudreau i agree 100%. i think you had the dependencies configured correctly from the start here, but are facing what i consider a clear npm bug. i'm really surprised that npm/npm#18135 doesnt seem to have much priority behind it yet.

@travi yeah, sadly.  I might have to use my recommendation at the end up loading all binaries and doing runtime check as to while one to grab :/
@mefellows Thoughts on this?

@travi @soundstep @mefellows Good news everyone.
Pact standalone now packages all binaries in a single dependency that's not OS specific anymore.  This shitty issue with npm optional dependencies and package-lock.json should now be fixed for pact-node in version 5.1.2.  Please try it out and report back to see if it works for your situation.
Very sorry about this whole ordeal.  Cheers.

Thanks so much @mboudreau for all your work on a bunch of stuff this past few days - I encourage anyone to look at the commit history to see this dedication.

I'm going to close this ticket as I haven't heard back from anyone, but this should be fixed by now.  If someone doesn't agree, I'll reopen.

@mefellows is publishing a new version of pact-js that uses this version - I'll test it for our case and confirm that our workaround isn't necessary any more.

FYI pact 4.0.x was released today, please let us know how you go!

Sorry @mboudreau and @mefellows, I was silent because I didn't have a chance to test!
But thanks everyone for the hard work!

No worries @soundstep, whenever you get the chance mate.

I ran into this same issue - using 4.12.
I upgraded to 5.2.0 and the issue was resolved.
Thankyou

Which reminds me - we tested this, and it works perfectly. Thanks, sorry for forgetting to update!

@soundstep Just as a closing comment, we've now merged the pact-standalone with in pact-node, starting at version 6.12.0.  Only the OS specific version is downloaded on postinstall and not all binaries as to remove the need for a weighty package that has all operating systems.
Give it a whirl :D


Emit client side metrics for per activity timeouts(schedule->start->close) and decision timeouts

Easier to diagnose if the activity/decision workers are falling behind.

One idea would be to emit latency metric of schedule to start time for each task .

Done with https://github.com/uber/cadence/commit/de42b327767d5a037d22a3cd10d019b484519069
https://github.com/uber/cadence/commit/95c7ec969b12578a7a19a62f305efebb23945965


fix(communication): use new redirect policy from core

All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Please consider rebasing on main. There are a lot of unrelated changes in this set.

Fixed. @jsquire


Include example HTTP request payload and response for each API endpoint in the API documentation

There are some curl examples at https://api.stackstorm.com/
But we should update API docs code generation code to include example request payload and example response for each API endpoint.
API docs without examples are nice, but not all that useful. With examples in place it's much faster and easier to get started (it's the same with regular code docs - just API reference documentation is not that useful, you need actual code samples, etc.).
To make the whole thing maintainable, actual payload examples should be tested. This means we need to write sample payload fixture files which we then use in st2api tests. Those example files are then also used inside the API docs.
Here is an example of docs I worked on in the past which includes examples which are tested (we used the same example payloads in our test suite) - https://developer.rackspace.com/docs/rackspace-monitoring/v1/api-reference/entities-operations/#create-an-entity.
This means no manual one off examples or similar. Examples which are not automatically tested are worse then no examples (they create maintenance burden and it's easy for them to get out of date and become wrong).
In addition to the sample request payload and response, we should also include example cURL line which uses data from the sample request fixture.
Once we also have Python client code automatically generated from the specs we should also include st2client examples (probably not worth spending the effort now in writing the code which would generate examples for the current st2client code).
Related repos:

https://github.com/StackStorm/st2apidocs
https://github.com/StackStorm/st2apidocgen

So yeah, just to point out. Examples are easy to add on API docs side. The main problem is to gather them inside openapi.yaml, which as Kami points out, should be done somewhat automatically. I personally have no idea how are we going to do that.

example like https://docs.camunda.org/manual/7.5/reference/rest/case-execution/variables/get-single-variable/


Consider aarch64 build

Hello, thank you for providing this as the flatpak build is quite heavy, currently for a lot of us Asahi Linux users we only have Brave and Chromium as options. Would you perhaps consider providing an aarch64 build?

Hi, you're welcome. As for aarch64 build, then it is now available for Fedora 39 and 40. Please confirm that it works. I cannot do it myself.

It works wonderfully thank you so much!
-------- Original Message --------
On 3/24/24 00:42, wojnilowicz  wrote:

Hi, you're welcome. As for the aarch64 build, then it is now available for Fedora 39 and 40. Please confirm that it works. I cannot do it myself.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

I'm happy to hear that 🙂 Thanks for the publicity you made on reddit. My name is a bit misspelled there though 🙄


[WIP] DON'T MERGE - Adds gems for google map integration:

Getting error message ActionController::RoutingError (No route matches [GET] /assets/bootstrap.min.css.map) when rendering home page. We think that it's maybe to do with the order of scripts in the application layout... any ideas?

Got a visible map.  Looks good.


Look at constraining Controller ClusterRole

The /config/200-clusterrole.yaml really lets the controller have RBAC super-powers that in many cases it simply does not need (or at least strongly suspect this:)). We should look to constrain the privileges as much as we can.

Was this ever looked at? We're considering Tekton for CI/CD but with the permissions granted to the controller in the deployment YAML, we'd need to dedicate a k8s cluster just for Tekton, since it gets really wide access.

We've looked into scoping down what Tekton has permissions for at the cluster-scope (see history), but I don't think anybody's looked into constraining what namespaces it has access to. For that you'd need to tell Tekton which namespace(s) you expect to be able to run workloads in, which necessarily can't be configured ahead of time by Tekton. What namespaces should Tekton be configured to run workloads in by default?
You could definitely manually replace the default ClusterRole with namespaced Roles for each namespace you expect to run in, but that does get tedious. Maybe this is something the Operator could be responsible for? If you tell the Controller what namespaces the controller should run workloads in it could grant it access to only those namespaces. But in order to do that, the Operator would need pretty expansive superpowers, so it might just be moving the problem around. 🤔
Either way, let's reopen to continue this discussion.


Color header in chrome (android)

This is not difficult in a "normal website" what about shaarli?
http://stackoverflow.com/a/26960753

All in all, Shaarli is a website as well so no it won't be difficult :)
Thanks for the idea, I'll do it soon!

Done. https://github.com/kalvn/Shaarli-Material/commit/cc568a710bbfd6b976b96eabde30775f9bfeaad9
If you use the color customization of Shaarli Material, it should use it. Otherwise, it'll use the default blue.

:+1: great


Fixes bug #143 incorrect error message

Resolves #143
Fixes bug incorrect error message when user list card expenditures with empty card transaction list.

Codecov Report

Merging #147 into master will increase coverage by 0.12%.
The diff coverage is 84.61%.

@@             Coverage Diff             @@
##             master    #147      +/-   ##
===========================================
+ Coverage     22.67%   22.8%   +0.12%
  Complexity      395     395
===========================================
  Files           120     120
  Lines          4071    4083      +12
  Branches        552     552
===========================================
+ Hits            923     931       +8
- Misses         3085    3089       +4
  Partials         63      63

Impacted Files
Coverage Δ
Complexity Δ

...va/owlmoney/model/transaction/TransactionList.java
81.56% <ø> (ø)
80 <0> (ø)
:arrow_down:

src/main/java/owlmoney/model/card/Card.java
86.51% <84.61%> (-3.1%)
26 <8> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9401fd0...e1942c1. Read the comment docs.


Question: Why is WinUI 3's scroll experience is far from WinUI 2

Open both WinUI 3 Control Gallery and WinUI 2 Control Gallery's Settings page, it seems that the WinUI3 version only got 30fps while the WinUI 2 version has an excellent scroll experience with an adaptive framerate that correlated to the screen's refresh rate, this also happens in my own app built with WinUI 3. If you are using an high-refresh-rate screen, the difference would be even more obvious

same issues here

Dupe #2513

Thank you for the reply, I've just confirmed that the scroll experience in Windows App SDK 1.0 is good if you are using the mouse wheel, it seems that the framerate is still 30fps when you are dragging the slider of the scroll bar instead of using the mouse wheel, and that is not gonna happen in WinUI 2

You can find the videos here and the difference is so obvious
ListView Scrolling in UWP(WinUI 2.6): Video link
in contrast to
ListView Scrolling in WinUI 3 Desktop(Windows App SDK 1.0.0 Experimental): Video link

https://github.com/microsoft/microsoft-ui-xaml/issues/4690

I'm aware of that, thanks for the reply

@Austin-Lamb @bartekk8 and @RBrid FYI

I'm just curious if this is still an issue. I'm testing the latest WinUI 3 and 2 Gallery and they seem very similar to me. But perhaps I'm wrong. @dylech30th, @sylveon any updated feedback?

I just tried both side by side and while it doesn't appear that the WinUI 3 gallery is capped to 60fps anymore, the WinUI 2 gallery still feels smoother to scroll through.

I can confirm that scrolling in the "All Controls" section of the winui gallery is extremly sluggish compared to the winui 2 version.


Muilti-dapr in one k8s cluster;

Note: If you have a general support question and are looking for a quicker response, please checkout our discord channel for answers from the community:
https://aka.ms/dapr-discord
In what area(s)?

/area runtime

/area operator

/area placement

/area docs

/area test-and-release

Ask your question here
I'm trying to  use dapr as our micrservices's foundamatial framework,  but I'm confused by the guildline of how to deploy dapr in k8s, we have three enviroment (DEV/PPE/PROD)in out release pipeline in one K8s cluster, I think I need to deploy three dapr in each namespace, we well test our services in DEV namespace and next step test in PPE namespace finally publish to PROD namespace.But when I try to deploy dapr with helm in second namespace I got an error: "Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists"; It seems that dapr is prefer to be installed once in one k8s cluster, that makes me confused. Is there some document or  guildlines that could help me to deply multi dapr in one k8s cluster? thanks !

@xckai
Dapr is currently a cluster-wide installation. So you are correct, it can only be installed once per cluster.
There is an emerging way to tackle this, with the use of vcluster - there is a very recent video of Yaron demonstrating vcluster so you can have multiple virtual k8s clusters in a single physical cluster. You can then deploy dapr into each virtual cluster.
As an aside, It's worth pointing out that placing Dev and Prod environments into the same physical k8s cluster is not recommended.


filebot: use FHS env

Description of changes
filebot --mode interactive executes /bin/stty, which is not present on
NixOS. Fix this by running filebot in a FHS environment with coreutils.
Closes #188828.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 189546 run on x86_64-linux 1

1 package built:

filebot

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/595

filebot --mode interactive executes /bin/stty, which is not present on
NixOS. Fix this by running filebot in a FHS environment with coreutils.

Could we patch that or does that break the binary?

I haven't looked at this in detail, but I think filebot is using Lanterna. Lanterna used to hardcode the path of /bin/stty, but this was fixed at some point: https://github.com/mabe02/lanterna/commit/217bcd24566c51f444d73fcb0e7396db29206e7a
I'm not sure if patching the jar is feasible, but maybe we can update the dependency? I don't have much experience with this.

I haven't had any luck with it yet, but with the jar cli it's possible to extract & update jars:
https://docs.oracle.com/javase/tutorial/deployment/jar/unpack.html
https://docs.oracle.com/javase/tutorial/deployment/jar/update.html
This is what I tried:
  patchPhase = ''
    runHook prePatch
    mkdir -p tmp
    ${openjdk17}/bin/jar xvf jar/lanterna.jar com/googlecode/lanterna/terminal/ansi/UnixLikeTTYTerminal.class
    sed -i "s|/bin/stty|${coreutils}/bin/stty|g" com/googlecode/lanterna/terminal/ansi/UnixLikeTTYTerminal.class
    ${openjdk17}/bin/jar uvf jar/lanterna.jar com/googlecode/lanterna/terminal/ansi/UnixLikeTTYTerminal.class
    rm -f com/googlecode/lanterna/terminal/ansi/UnixLikeTTYTerminal.class
    runHook postPatch
  '';

And it currently fails with the following error on the jar uvf command:
java.lang.IllegalArgumentException: malformed input off : 1, length : 1
        at java.base/java.lang.String.throwMalformed(String.java:1240)
        at java.base/java.lang.String.decodeUTF8_UTF16(String.java:1191)
        at java.base/java.lang.String.newStringUTF8NoRepl(String.java:728)
        at java.base/java.lang.System$2.newStringUTF8NoRepl(System.java:2398)
        at java.base/java.util.zip.ZipCoder$UTF8ZipCoder.toString(ZipCoder.java:199)
        at java.base/java.util.zip.ZipCoder.toStringUTF8(ZipCoder.java:90)
        at java.base/java.util.zip.ZipInputStream.readLOC(ZipInputStream.java:301)
        at java.base/java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:124)
        at jdk.jartool/sun.tools.jar.Main.update(Main.java:934)
        at jdk.jartool/sun.tools.jar.Main.run(Main.java:347)
        at jdk.jartool/sun.tools.jar.Main.main(Main.java:1683)
Caused by: java.nio.charset.MalformedInputException: Input length = 1
        ... 11 more

This is indeed possible to fix by upgrading lanterna.jar to the latest version and specifying the com.googlecode.lanterna.terminal.UnixTerminal.sttyCommand system property as explained in https://github.com/NixOS/nixpkgs/pull/189546#issuecomment-1236183109. Here's the overlay that works for me:
(self: super: {
  filebot = super.filebot.overrideAttrs (old: {
    postPatch =
      let
        lanterna_3_1_1 = builtins.fetchurl {
          url = "https://search.maven.org/remotecontent?filepath=com/googlecode/lanterna/lanterna/3.1.1/lanterna-3.1.1.jar";
          sha256 = "sha256-7zxCeXYW5v9ritnvkwRpPKdgSptCmkT3HJOaNgQHUmQ=";
        };
      in ''
        cp ${lanterna_3_1_1} jar/lanterna.jar
      '';

    installPhase = old.installPhase + ''
      substituteInPlace $out/opt/.filebot.sh-wrapped \
        --replace '-jar "$FILEBOT_HOME/jar/filebot.jar"' '-Dcom.googlecode.lanterna.terminal.UnixTerminal.sttyCommand=${pkgs.coreutils}/bin/stty -jar "$FILEBOT_HOME/jar/filebot.jar"'
    '';
  });
})


wsk package list showing package versions as separate items

Environment details:
IBM Bluemix - US South.
Steps to reproduce the issue:
$ wsk property get
whisk auth		xxx:yyy
whisk API host		openwhisk.ng.bluemix.net
whisk API version	v1
whisk namespace		_
whisk CLI version	2016-12-13T10:40:19+00:00
whisk API build		2017-01-30T14:37:50Z
whisk API build number	whisk-build-3033
$ wsk package list
packages
<EMAIL_ADDRESS>                                   private
<EMAIL_ADDRESS>                                   private

Looking at the HTTP traffic, the kafka package has two versions due to being updated.
Provide the expected results and outputs:
$ wsk package list
packages
<EMAIL_ADDRESS>                                   private

Single package identifer should be listed despite number of versions.

What's the problem? A typo when you created package?

Your awesome and I just need 👓 It took me a while to see it


Make getDimensionFromEmptyDims allocate less memory

mwp@Matthews-MacBook-Pro-3 ~/.go/src/github.com/signalfx/metricproxy (enhance)*$ benchcmp /tmp/old.txt /tmp/new.txt
benchmark                                    old ns/op     new ns/op     delta
BenchmarkGetDimensionFromNameEmptyDims-8     1826          1540          -15.66%
BenchmarkGetDimensionFromName-8              3679          3476          -5.52%
benchmark                                    old allocs     new allocs     delta
BenchmarkGetDimensionFromNameEmptyDims-8     4              2              -50.00%
BenchmarkGetDimensionFromName-8              9              8              -11.11%

benchmark                                    old bytes     new bytes     delta
BenchmarkGetDimensionFromNameEmptyDims-8     159           63            -60.38%
BenchmarkGetDimensionFromName-8              575           527           -8.35%

This is used for every plugin_instance, type_instance or host dimension passed in from collectd

Coverage remained the same at 100.0% when pulling efcc90d6c6c72899cff0da0d1c5eb69b4c9097e1 on enhance into 5fa39d00a262256a3bd08c814e08dc3570325831 on master.

Coverage remained the same at 100.0% when pulling c9eded9bc9f1d2be16069f02f55b071b8df18be5 on enhance into 5fa39d00a262256a3bd08c814e08dc3570325831 on master.

Coverage remained the same at 100.0% when pulling 5f827b2e8a1d131eb045da9f693f8111000ffea4 on enhance into 5fa39d00a262256a3bd08c814e08dc3570325831 on master.


Update README.md

Minor correction in cluster status command
changed from docker exec vernemq1 vmq-admin cluster status -> docker exec vernemq1 vmq-admin cluster show

Thanks for the correction!


Send SIGUSR2 signal on restart like nodemon?

Would it be possible to add a some signal, e.g. SIGUSR2 before a restart to allow a micro server to perform some cleanup? nodemon does this: https://github.com/remy/nodemon/#controlling-shutdown-of-your-script
My use-case is a setInterval() that I want to call clearInterval() on each time micro-dev restarts the server. Right now I end up with one interval long running for every single start/restart of the server.

That sounds sweet!

The thing is that we're not killing the process, but rather removing some cached files from memory and then loading the server again (which is much faster). In turn, the user wouldn't be able to handle the restart by himself. Or maybe we should send a function to call after cleanup along with the event?

Simple way to do that:
https://github.com/Kikobeats/svr/blob/61c44191297f7e738bfa03876b4be5ba91e70b0e/bin/watch/index.js#L40

I have a similar use-case where I have a readstream open and when micro-dev reloads, another stream starts and the existing one doesn't get killed. I think that's what happens, anyways; The code runs number-of-restarts times.
I guess you'd need to have dev env only related code in your service then to handle cleaning up stuff like this, which I'm not sure you'd want.
A thing that might be nice is a "cold reloading" switch, but just using nodemon with micro-dev -c achieves the same thing.
Very contrived example:
process.stdin.pipe(process.stdout)

module.exports = (req, res) => {
  res.end('OK!')
}

(type something into the same terminal micro-dev is running in and press enter. resave. repeat)

Added in https://github.com/zeit/micro-dev/pull/48


Keylogger

Script Title - As the name suggests, it should able to record keys (Can be sone by pynput)
what will change - Adding script
Instructions

Create a new folder for your script and file/folder name should be appropriate.
Create a README.md in your folder for program Instructions
add requirements.txt if needed

Please add/delete options that are not relevant.

[x] Adding New Code

Programming Language

[x] Python

Happy Coding,

Can I take this issue?

sure, go-ahead

Okay! Thank you @pawangeek

Hello, @pawangeek!
Could you please tell me how to pass the codespell test and flake8linter test? I'm a newbie here.

Hi @pawangeek !
I installed code spell checker extension on my vscode and it is showing warning because of the module pynput.
Any solution on how to remove the warning and get all the checks passed?

@pawangeek Please check PR #184 .


release <IP_ADDRESS> is crashing if error in bind or connect

What steps will reproduce the problem?
1. Enter a non existing ip in Bind or Connect
2. A memory access violation occurs in CEPoll::update_events()
3. Application crashes

What version of the product are you using? On what operating system?
UDTProtocol ver <IP_ADDRESS>

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 13 Sep 2013 at 7:38

Unable to replicate the issue.


Problem installing quickumls on Windows

In attempting to install quickumls on Windows10 and Python 3.8.5 in an Anaconda environment, I get the following log:

(base) PS C:\Users\Ron> pip install quickumls
Collecting quickumls
Downloading quickumls-1.4.0.post1.tar.gz (22 kB)
Requirement already satisfied: leveldb>=0.193 in c:\users\ron\anaconda3\lib\site-packages (from quickumls) (0.201)
Requirement already satisfied: numpy>=1.8.2 in c:\users\ron\anaconda3\lib\site-packages (from quickumls) (1.19.2)
Requirement already satisfied: spacy>=1.6.0 in c:\users\ron\anaconda3\lib\site-packages (from quickumls) (2.3.2)
Requirement already satisfied: unidecode>=0.4.19 in c:\users\ron\anaconda3\lib\site-packages (from quickumls) (1.2.0)
Requirement already satisfied: nltk>=3.3 in c:\users\ron\anaconda3\lib\site-packages (from quickumls) (3.5)
Collecting quickumls_simstring>=1.1.5r1
Downloading quickumls_simstring-1.1.5r1.tar.gz (68 kB)
|████████████████████████████████| 68 kB 1.2 MB/s
ERROR: Command errored out with exit status 1:
command: 'C:\Users\Ron\anaconda3\python.exe' -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\Ron\AppData\Local\Temp\pip-install-kzzwupen\quickumls-simstring\setup.py'"'"'; file='"'"'C:\Users\Ron\AppData\Local\Temp\pip-install-kzzwupen\quickumls-simstring\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' egg_info --egg-base 'C:\Users\Ron\AppData\Local\Temp\pip-pip-egg-info-ia24qkh_'
cwd: C:\Users\Ron\AppData\Local\Temp\pip-install-kzzwupen\quickumls-simstring
Complete output (7 lines):
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\Ron\AppData\Local\Temp\pip-install-kzzwupen\quickumls-simstring\setup.py", line 93, in
readme = reader.read()
File "C:\Users\Ron\anaconda3\lib\encodings\cp1252.py", line 23, in decode
return codecs.charmap_decode(input,self.errors,decoding_table)[0]
UnicodeDecodeError: 'charmap' codec can't decode byte 0x9d in position 471: character maps to
----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

I'm glad that our other documentation helped out.  If you have other issues, let me know since I've spent a lot of hours making sure that QuickUMLS can build in various environments.  Windows takes by far the most effort and care.


[now dev] Add support for .env file to define Now secrets

If a now.json files relies on secret env vars, then they must be defined in the user's local .env file otherwise now dev exits with an error.

Codecov Report

Merging #2048 into canary will decrease coverage by 0.15%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           canary   #2048      +/-   ##
=========================================
- Coverage    4.67%   4.51%   -0.16%
=========================================
  Files         243     243
  Lines        8501    8524      +23
  Branches      865     865
=========================================
- Hits          397     385      -12
- Misses       8088    8123      +35
  Partials       16      16

Impacted Files
Coverage Δ

src/commands/dev/lib/dev-builder.ts
0% <ø> (ø)
:arrow_up:

src/util/errors-ts.ts
0% <ø> (ø)
:arrow_up:

src/commands/dev/lib/dev-server.ts
0% <0%> (ø)
:arrow_up:

src/util/get-project-name.js
90.9% <0%> (-9.1%)
:arrow_down:

src/util/get-files.js
91.53% <0%> (-8.47%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7a9d5e6...43fccc3. Read the comment docs.

Awesome @TooTallNate 🎉

Haven't try it but LGTM ✅

@TooTalNate is this mentioned anywhere in the docs


CEZ distribuce integration

Zkontrolujte existující problémy

[X] Completed

Verze
0.5.0
Napište svůj dotaz nebo s čím potřebujete pomoci
Hello, I have just started with Home Assistant and one of my first projects from HACS is CEZ distribuce integration.
I have downloaded the files into custom_ components:

And added the binary_sensor into configuration.yaml:

What are next steps in order to see the application in a dashboard?
Thank you very much indeed.
Best regards
Pavel

Hi, it's simple. Restart HA. Look into Devices & services => Entities and search stred_a1b5dp6 or cezdistribuce. When you see a binary sensor you can use it in automation and other stuff.
Another approach is to use Developer tools => states and write stred_ into Entity filter.

Thanks a lot


Software requirements

I am trying to install Appliance 9.54 with Win Server 2016 but failed due to now its only support win server 2019.
However, the doc still indicate the Win Server 2016 still supported

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 7f1a6a67-a0d7-9dc8-54ae-395072d8a383
Version Independent ID: 5460d9fe-ddcb-d80b-56fd-a7a0cb72dbdb
Content: Deploy Azure Site Recovery replication appliance - Modernized - Azure Site Recovery
Content Source: articles/site-recovery/deploy-vmware-azure-replication-appliance-modernized.md
Service: site-recovery
GitHub Login: @ankitaduttaMSFT
Microsoft Alias: ankitadutta

@Shiylue
Thanks for your feedback! We will investigate and update as appropriate.

Post 9.54, only WS2019 will be supported as the appliance. Updating the documentation now and will remove WS2016 as supported.

#please-close


fix(ui): Web recaptcha hover removed after use.

Fixes #4377
After showing a recaptcha in web for SMS login, the recaptcha icon
overlay persists on the app until it is reloaded, often blocking an
app's buttons and other interactive widgets. This adds removal of the
web UI element in the clear method, and ensures that clear is called on
any RecaptchaVerifier() objects created by flutterfire.
Description
Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[X] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[X] All existing and new tests are passing.
[X] I updated/added relevant documentation (doc comments with ///).
[X] The analyzer (melos run analyze) does not report any problems on my PR.
[X] I read and followed the Flutter Style Guide.
[X] I signed the CLA.
[X] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[X] No, this is not a breaking change.

Thanks for the reviews! Are there any other steps needed to merge this?

It's good 😁 Thanks for your help


Pilot page still shows old GitHub handle information

https://pilot.traefik.io/plugins/276812076107694611/deny-ip-plugin

hi @ChunkleChip, I've tagged folks who might know how to deal with this issue better than I could these days. Thank you for your report. I'm closing this because I am unable to take any action on it.
cc @santoDE


Use ..json instead of a singular locale file

There's too much of a disconnect between a single centralized translation file and the JSON document it translates.
It would be better to fetch base on language preference:

team.en.json for English (default)
team.fr.json for French

and keep both files in the same directory.

see pull request #14
& staged here

team.fr.json to match team.json


suppress creation of textual.log

Hello,
Really cool app.
Is it possible to suppress the creation of textual.log when running tiptop?

thank you,
Andres

Fixed in 0.1.5. Thanks for the report!

thanks!.. upgraded to 0.1.5


window.URL no emit file

Clear and concise description of the problem
const metaUrl = new window.URL('./nested/asset.png', import.meta.url) can't emit asset
Suggested solution
const metaUrl = window.URL('./nested/asset.png', import.meta.url)
Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

I'm not sure if we need this. Wouldn't it work for client-side only? I think recommending an isomorphic new URL syntax is the way to go.

in the ssr, it may be throw error. but in the client-side it no support the syntax. I am interested in how to recommend isomorphic grammars at compile time.😀

Hmm yeah you're right, new URL only works for the client side (as mentioned in the docs in doesn't work in SSR), but I think it would work in web workers too, and they don't have access to window. The isomorphic syntax is actually the current feature we have, by using new URL directly. I'm not sure what's the usecase for new window.URL but I think it's best to keep it simple as new URL first.

thanks, should use the isomorphic syntax to support new URL, this is better way.

Should we close this issue?


org.bouncycastle.asn1.ASN1Private class existed in 1.69 no longer exists

Hi Bouncy Castle team,
I recently found the class org.bouncycastle.asn1.ASN1Private previous existed in 1.69 no longer exists in latest code base.
There is still a doc for this class in 1.69 version here
The project I am working on is depending on this ASN1Private class. Can anyone help explain why this class is removed and if there is any solution for replacement? Thank you!

All types of tagged object (CONTEXT, APPLICATON, PRIVATE) are now handled by ASN1TaggedObject and its subclasses (or ASN1TaggedObjectParser when parsing).
Instead of creating a DERPrivate, create a DERTaggedObject (or BER, DL) using a constructor that accepts a tagClass, and pass BERTags.PRIVATE as the tag class.
When parsing, an ASN1TaggedObject subclass will be returned for the PRIVATE-tagged encoding. Check its tag class and tag number to make sure it matches what you are expecting e.g. using ASN1TaggedObject.hasTag, before accessing the base object. There are also a whole range of utility methods in ASN1Util to simplify checking/extracting tagged values.
DERPrivateTest also survives and was converted from using ASN1Private to using ASN1TaggedObject, so may be helpful.


[Question] How do you remove aria-hidden=true on navigation?

Hi James,
I'm changing an existing site over to v4 from v3 and noticed that I needed to tweak some css (adding display:block to #navigation) to show my dropdown nav on wider displays. I'm using a dropdown to toggle the nav on mobile.
When I was having a look in Developer Tools to suss this out I noticed that the navigation is set to aria-hidden=true on wider displays as I'm forcing it to be expanded. The role changes as expected on mobile.
Is there something I'm missing to have this change? Don't suppose it's a big issue, but wanted to ask as it looks like responsive sets  display: none !important; on items with [aria-hidden="true"] and I notice that on the docs site you have the main nav set as aria-hidden=false on wider displays as you'd expect.
Are there any drawbacks to leaving it as  [aria-hidden="false"] and forcing it's appearance with display: block!important;?
Cheers,
Iain

Hi Ian,

Are there any drawbacks to leaving it as [aria-hidden="false"] and forcing it's appearance with display: block!important;?

I take it you mean [aria-hidden="true"]? If so then yes. From an accessibility point of view you don't want the two to be mixed up as you prevent screen readers from reading the content. You'll notice also that the tabindex attribute changes also which will affect keyboard accessibility.
I use a little snippet of JavaScript code in the documentation to ensure that those attributes are changed.
https://github.com/ResponsiveBP/Responsive/blob/gh-pages/assets/js/docs.js#L6
I use this css to then tweak the navigation styles in a media query. Really I should probably use the attribute selector though.
https://github.com/ResponsiveBP/Responsive/blob/gh-pages/assets/css/docs.css#L82
Hope that helps.
James

Hi James,
Yes I did mean [aria-hidden="true"], sorry about that!
Do you mind if I use the JS snippet myself?
As for the CSS I was previously using…
#navigation.collapse {
height: auto;
overflow: visible;
}
…but noticed that wasn't working on the new version, so was trying to suss out why I needed to use display: block as well this time around.
If I can use the JS above that shouldn't be needed as the role will change, but I will look to used the attribute selector.
Cheers,
Iain

Yeah fire away chum, use anything you like :smile:

Awesome, thanks again for your help!


Showcase norch-functionality with test-data

[x] Displaying categories for search results
[ ] Displaying buckets for search results
[ ] Displaying images (data not searchable, but displayable)
[x] Filter on categories
[ ] Filter on buckets
[ ] Autosuggest (matcher)
[ ] Hit highlighting

Which categories and buckets to show can be configured in the data model.

For images to work like this, the search-index-indexer needs a bug-fix.

Bug is fixed


(SP: 1) Update get cooperations endpoint response

[ ] the response should contain cooperation sections property
[ ] update swagger endpoint docs

This task is not relevant anymore


support text/plain

It would be nice to support text/plain as well as application/json. Some people prefer plain text when they want to send an encoded text (e.g. client credentials in JWT) to the HTTP server.

Hi @z8674558 I have merged this PR and #225. These features will be released into v4.2.3
Thanks for your contribution. :)


CVE Scanning for node not possible

Hi,
OCP Version - Central: 4.9.33
OCP Version - Secured Cluster: 4.10.20, 4.9.33, 4.8.19
Stackrox Version: 3.71.0
we are deploying Stackrox on OCP4. The Vulnerability Management Details page for a node of a secured cluster does not show any CVE Data, instead I can only see a message
CVE DATA MAY BE INACCURATE
Node unsupported.
Scanning this node is not supported at this time. Please see the release notes for more information.

Question 1: where can I find the release notes?
Question 2: is there a roadmap for new features? E.g. I saw #2588 for example and am wondering when to expect this in a versioned release
Question 3: how can I enable scans for CoreOS nodes?

@jvdm could you please chime in here?

@balpert89 CoreOS node scanning is currently disabled because some of the CVE sources we use for node scanning are not OS-specific. Instead, we use NVD, despite the fact that Red Hat OVALs offer more accurate information. To avoid confusion, it was disabled.
The release notes refer to RHACS release notes for 3.71. In Stackrox, they are somewhat tracked in the Changelog for 3.70. Sorry for the confusion. Stackrox is currently highly tied with RHACS, so some of the information can only be seen downstream.
The notes say:

Vulnerability scanning and reporting for Red Hat Enterprise Linux CoreOS (RHCOS) nodes has been disabled until scanning improvements are made for improved accuracy and to support full host-level scanning beyond just Kubernetes components. Currently, RHCOS uses National Vulnerability Database (NVD) vulnerability data for reporting vulnerabilities for Kubernetes components from RHCOS. In the enhanced version, vulnerability reporting will be based on Red Hat published security data. (ROX-10662)

So this brings me to your second question.

Question 2: is there a roadmap for new features?

The roadmap to release RHCOS node scans using Red Hat's security data and also listing RHCOS packages is 3.73, currently scheduled for 5 December 2022.

Question 3: how can I enable scans for CoreOS nodes?

Unfortunately, it's not possible to enable it without modifying the code. Putting it behind a toggle could be an option, but I am not sure it worth the effort since 3.71 is our next release.
Hope your questions were answered. Feel free to re-open with you want to follow up.
Otherwise, see you on 3.71!


How to get tags as a string ?

I see that you have removed input text field
https://select2.org/upgrading/migrating-from-35#no-more-hidden-input-tags
But I need the data for my system in single one line of string separated by comma.
like it is here: https://selectize.github.io/selectize.js/
<input type="hidden" name="tags" value="drama, action, crime" />

Is it possible somehow to have a hidden field and update it for e.g. on select2 onChange ? or there is possible to set some options for this ?

okey, seems this is works for me
    $('.js-tags').select2({tags: true, multiple: true, tokenSeparators: [',', ' ']});

    $('.js-tags').on('change', function (e) {
        $('.js-tags').each(function() {
            var name = $(this).attr('data-name');
            $('input[name='+name+']').val($(this).val().toString());
        });
    });

...

    {{ tr(title) }}
    <select class="{{ class }} js-tags" data-name="{{ name }}" multiple="multiple">
        {% for key, value in current_value %}
            <option value="{{ value }}" selected="selected">{{ value }}</option>
        {% endfor %}
    </select>
    <input type="hidden" name="{{ name }}" value="{{ current_value|join(',') }}">
    {% if help %}
        {{ help }}
    {% endif %}

Looks like you found the solution that lines up with what we would have recommended.

This appears to be more of a usage question than a bug report or common feature request.  As we continue to keep the Select2 issue tracker geared towards these two areas, bug reports and common feature requests, we are redirecting usage questions to other communities such as the mailing list, IRC, or Stack Overflow.


Specify a custom config config.yaml path

It would be great if we could specify a specific configuration path to use.
Possible way:

env var like TERMINUS_CONFIG_FILE
option like terminus --config-file

At the same time, if we could also specify another PATH for %APPDATA%\terminus.
On linux I can cheat with specify HOME=fakehome terminus but on Windows I can't :(


Externalize BOM ingestion pipeline

At the moment, processing of uploaded BOMs is happening entirely in-memory.
BomUploadProcessingTasks are enqueued to the internal task queue (see https://github.com/DependencyTrack/hyades/blob/main/WTF.md#why), and processed by the EventService thread pool.
The current design has some downsides:

When the API server crashes or is stopped, queued tasks are lost. Users have to re-upload their BOM again after the API server was restarted, which may or may not be practical, depending on the users' workflows.
Processing can not be shared among multiple instances of the API server.
We do not store the original BOM, because it is not practical to store many large documents in a RDBMS.
If BOMs are re-uploaded for the same project in close succession, we'll run into race conditions, as BOM ingestion is not executed in a single, large DB transaction.

The proposed enhancement involves storage of uploaded BOMs in a Koala-compatible system (e.g. the CycloneDX BOM Repository Server), and publishing "BOM uploaded" events to Kafka. Consumers (API server or specialized workers) consume from the Kafka topic, and perform the actual ingestion into the database.

Processing could then happen in a distributed fashion, by one or more API server instances (or even specialized workers).
Uploaded BOMs would not be lost in case an API server instance is stopped or crashes.
Original BOMs would be retained, and could be referenced by the DT UI.

See https://github.com/DependencyTrack/dependency-track/issues/877

Kafka's consumer model would ensure that BOM uploads for the same project are processed serially.
Would allow for policies on original BOMs.

See https://github.com/DependencyTrack/dependency-track/issues/773

If Koala was able to accept SPDX, but return CycloneDX, we could implement official support for SPDX ingestion.

See https://github.com/DependencyTrack/dependency-track/issues/1746

Aids in achieving #375.

sequenceDiagram
    Client->>+API Server: Upload BOM
    API Server->>Koala: Upload BOM
    Koala->>Koala: Validate BOM
    Koala->>API Server: Location of BOM in Koala (URL)
    API Server->>API Server: Generate and persist correlation ID
identifying the upload
    API Server->>Kafka: Publish event to "BOM uploaded" topic
    Note over API Server, Kafka: Key=Project UUID
Value=Koala URL
Header=Correlation ID
    API Server->>Client: Report correlation ID
    loop continuously
        API Server->>Kafka: Consume from "BOM uploaded" topic
        loop for each event
            API Server->>Koala: Fetch BOM
            API Server->>API Server: Process BOM
            alt processing failed
                API Server->>API Server: Update status of upload in DB to "failed"
                API Server->>Kafka: Publish event to "BOM Processing failed" topic
            else processing succeeded
                API Server->>API Server: Update status of upload in DB to "successful"
                API Server->>Kafka: Publish event to "BOM Processed" topic
                API Server->>API Server: Trigger vuln analysis etc.
            end
        end
    end

Warning
Because BOM processing can take up to multiple minutes for huge BOMs, it is not viable to perform processing in Kafka Streams, where short processing times are mandatory (see #529). We either need to offload processing to a separate thread pool, or write some custom logic around the low-level Kafka consumer.

We need to look into proper AuthN / AuthZ for the Koala service. The BOM repo server does not have those built-in.
Focusing on the client-side a little more, existing workflows should still continue to work:
sequenceDiagram
    Client->>+API Server: Upload BOM
    API Server->>Client: Report correlation ID
    loop continuously
        Client->>API Server: Is BOM still being processed?
(Using correlation ID)
        alt processing ongoing
            API Server->>Client: "true"
        else processing completed
            API Server->>Client: "false"
            Client->>Client: Stop polling
        end
    end
    Client->>API Server: Fetch findings
    Client->>API Server: Fetch policy violations

Decoupled the centralized tracking of processing status(es) into #664. Deprioritizing this issue.

Project Koala / Transparency Exchange API will not arrive anytime soon, so we need to evaluate alternatives.
I don't think we should introduce a generic blob storage for this yet. Instead, we might want to consider storing uploaded BOMs in a new table, as BYTEA column.
BOMs can be arbitrarily large. While Postgres compresses large values, we still need to send all that data over the wire twice (once for storage, once for retrieval). The default compression is also not particularly good.
We already bring in zstd-jni via kafka-clients. I did some testing and it is possible to compress a ~22MB JSON BOM to ~1MB with reasonable resource consumption using zstd. I would thus propose that we perform compression/decompression in the application.


How to add coupon/voucher?

I want to add some coupon/voucher for my campain but didn't find anywhere to config
Can I workaround by add a new product but it's kinda manual cause I have many plans

By coupon/voucher I assume you mean discount codes?

@duylddev Discounts & coupon codes is a high priority. We're expecting to launch support for it in December at the latest


[Carla 0.9.5] Visualize two lidars' data at the same time in rviz

Hello Carla team,
As the manual_control.py is always activating just one camera and deactivating other sensors, is there a way that spawn multiple lidar sensor and activate them at the same time? Furthermore, visualize the data in rviz.
Thanks in advance.

Update.
I am currently able to spawn multiple lidar in manual_control.py and get lidar data from two lidar sensor through ros_bridge. But it seems the data from two lidar are sending to the same topic which leads to some conflict in rviz visualization.
One of the lidar's transformation is not correct and the points is flashing in rviz.
May I know if it is possible to set a different topic for different sensor instance? or is there any other way that work this problem out


[DS-2397] Sort out Unit vs. Integration tests, and run them separately

https://jira.duraspace.org/browse/DS-2397
This is just a start, but it provides the infrastructure for integration tests in dspace-api and moves two tests so that they are run in the IT phase rather than the UT phase.  Other projects should be able to reuse the changes here.

I like what has been done so far, and Travis CI seems to approve of the changes. +1 to merge as-is, DS-2397 didn't ask for more tests, just to clarify them. You've done that with this change.

+1 Looks good to me. I'll note there's one Integration Test that hasn't been moved over to using failsafe:
https://github.com/DSpace/DSpace/blob/master/dspace-api/src/test/java/org/dspace/content/packager/DSpaceAIPIntegrationTest.java
However, that could likely be moved separately as needed.


Information Update for "Integrating Graphs with Large Language Models: Methods and Prospects"

Hi Peter,
Thank you very much for including our work in your repo!
Could you please help us update the information of the paper "Integrating Graphs with Large Language Models: Methods and Prospects"? The paper is now accepted by IEEE Intelligent Systems and will be published soon.
Warmest Regards,
Yizhen Zheng

Hi Yizhen,
Thanks for bringing up the paper. I'm happy to add it to the repo.
Best,
Bowen


Mismatching Calculations

I have been using the Imperas RISV Tests included with riscvOVPsim for compliance testing and having some queries on the F ISA extension tests.
OVPSim : https://github.com/riscv-ovpsim/imperas-riscv-tests
F ISA test download page: https://www.ovpworld.org/library/wikka.php?wakka=riscvOVPsimPlus
These tests from Imperas are the updated RISCV Compliance tests and the fpnew is have some mismatches on the FDIV, FMUL and FSQRT tests.
Here are the mismatching calculations:
FPNEW_MISMATCH_COMPLIANCE_V2.xlsx
I have only seen F ISA extension tests pass with the models (e.g. C/BFM), so this suggests there is a mismatch between the RTL and models.
Can you comment on my findings?

Hello @M31581,
Thanks for reporting. There are some rounding problems with the divider/square root units when used in combination with RNE policy. Indeed, there is a plan to update the entire divsqrt unit.
Have you also found mismatches with fmul operations? I don't find them in the .xlsl file.
Best regards,
Matteo

Hi @mp-17
Thanks for confirming, good to here there is a plan to update the entire divsqrt unit.
Yes I have found mismatches in the fmul operations, the "I-FDIV-S-DYN-RDN-01 and I-FDIV-S-RDN-01" table is actually a typo it is the "I-FMUL-S-DYN-RDN-01 and I-FMUL-S-RDN-01".
I have just updated the table with correct info.
Regards,
Tommy


fix: fixed Overlay button in footer

fix #1654
Description
Corrected overlaping of footer icons
What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[x] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents
Fixes #1654

Mobile & Desktop Screenshots/Recordings

Before

After

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

This Looks good... Thanks @himanshumalviya15 for this quick fix


feat: [#8787] Update ARM templates and test

Description
This PR updates the ARM templates to use AzureBot instead of Bot Channel Registration to create resources. The changes include:

ResourceGroupId variable added in template-with-new-rg template.
WebAppService resource updated in template-with-new-rg template.
BotService resource updated in template-wit-new-rg and funcion-template-with-preexisting-rg templates.

Task Item
Fixes # 8787
#minor
Screenshots
NodeJS EmptyBot working as expected using the template-with-new-rg template.

C# CoreBot working as expected using the template-with-new-rg template.

Function EmptyBot working as expected using the template-with-preexisting-rg template.

Please review the PR's description to match the sections with the PRs on this repo. What does All resources are updated in template-with-new-rg template. mean? Were they really all updated? The diff is not helping either, it shows all the file as changed.

Done. Thanks.


Access Wallace lab data store

check that Edward has granted you permission to access the lab datastore (where sequencing data is held)

I have given permission, but I don't know if @JingQiChong has succeeded in accessing yet.

I managed to access the lab datastore. Turned out I have been using the wrong command line because I did not know there is a slight difference in how to access datastore in Bifx server.


records: add file preview

Closes #235
Screenshots:
zip

image

pdf

not previewable content

Will work when invenio-previewer is released. Merging...


[DO NOT MERGE] Suggested hover style for action link

What?
Draft PR - conversation starter:
There was a request from Design to update a missing hover state on the action link on corona virus landing page.
Ticket: https://trello.com/c/mBN0xr04
Why?
Updating the corona virus landing page action link with a unique hover style in complete isolation is not ideal.
Users will have have a mix of hover styles even within the same page. For example, this also impacts Bread Crumbs which is also on this page.
This prompted a wider discussion, white text (while on a coloured background) + hover styles do not exists within the Component Guide and there is already an issue  raised about ensuring consistent hover styles across gov.uk
As a result Design actioned a wider exploration piece to discover a colour that met AA standards and was a perceivable change within multiple contexts. The result was the solution #DDDCDB
Draft PR to prompt Frontend discussion for new hex (or possible variation of existing hex) to be absorbed into govuk-frontend or the Design System
Visual Changes

Anything Else?
There's a couple possible implementation approaches

Close ticket, mark do not fix (issue has already been raised)
Update landing page insolation
Update action link in isolation
Update within all publishing_components add a new colour var to gov-frontend
Add to Design System $govuk-link-hover-white-text-colour: #DDDCDB

PR raised


Redshift external table definitions

Where to put Redshift external table definitions?
Feature description
Context from Slack: https://getdbt.slack.com/archives/C2JRRQDTL/p1533315273000059?thread_ts=1533246671.000100&cid=C2JRRQDTL
We use Redshift Spectrum external tables to read data from S3. The table definition needs a place to live, and would ideally be updated ahead of every dbt run. However, to execute CREATE EXTERNAL TABLE the user needs to either be a superuser or the owner of the schema the table is being created in. It would be great to be able to have a place to put a hook that runs with different credentials than the rest of the dbt run.
Alternatively, this could be solved with a dbt command that would execute a particular SQL file with a given dbt target, which would let us script this like:
dbt exec --target=spectrum-owner redshift-spectrum-setup.sql
dbt run

Who will this benefit?
Helpful for all kinds of initialization that needs to be run to prepare for a dbt run with different credentials.

Thanks for the writeup @martinmelin!
Is there any penalty for having many external tables that all point to the same data in S3? I think the dbt way of doing this is for each dbt user to have their own external schema, containing their own external tables. That way, devs can make changes in their own (external) schemas without affecting the work of other devs, or the production dbt user.
In order for dbt to properly support Spectrum, I think we'll need:

the ability to create external schemas
the ability to create external tables

I'm unsure of how to best implement external schemas, but I think there are definitely a couple of options. One might be to just create these schemas in the on-run-start hooks for the project. Another implementation might look more like configuration (in dbt_project.yml?)
For external tables, I think we pretty easily account for those with a materialization. This should be pretty straightforward based on the documentation here.
I'm not super interested in maintaining all of the external table options in dbt, eg:
partitioned by (saledate date)
row format delimited
fields terminated by '|'
stored as textfile
location 's3://awssampledbuswest2/tickit/spectrum/sales_partition/'
table properties ('numRows'='170000');

I think a good approach might be to just make a raw materialization which accepts create table SQL like this:
create external table spectrum.sales_part(
salesid integer,
listid integer,
sellerid integer,
buyerid integer,
eventid integer,
dateid smallint,
qtysold smallint,
pricepaid decimal(8,2),
commission decimal(8,2),
saletime timestamp)
partitioned by (saledate date)
row format delimited
fields terminated by '|'
stored as textfile
location 's3://awssampledbuswest2/tickit/spectrum/sales_partition/'
table properties ('numRows'='170000');

Last we'd have to think through partitioning.... The more of this issue, the more involved I realize this feature is! So, lots to discuss here. Keen to hear your thoughts!

@martinmelin I'm going to close this issue, as I think external tables should (probably) be created manually (there should only be one in your Redshift!). That said, I think it's a great idea to version the DDL along with your dbt models!
This might be a good way to accomplish something similar in the future: https://github.com/fishtown-analytics/dbt/issues/582


Add BowerCDN install helper

Hello,
I think it would be helpful for users to know they can use BowerCDN to install this module.
Let me know what you think.
Thanks

Thanks but there's a lot of different ways people might want to serve or load their scripts and I don't want to start recommending one over the other for this project specifically.


Reimpl MagickWand::set_image_pixels

Signed-off-by: Jiahao XU<EMAIL_ADDRESS>

Feel free to merge.

Feel free to merge.

Hmmm, I don't have the permission to merge though.

Feel free to merge.

Hmmm, I don't have the permission to merge though.

Permission added.

@jmjoy Thanks!


Add unit tests for organization discovery

Issue https://github.com/wso2/product-is/issues/19496

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/8537927722

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/8537927722
Status: success


Add flag to opt-in to multitenancy (fixes #56)

Flag name is --multi-repo. Feel free to suggest another name. Single root route defined for now.
cc: @liamawhite

Thanks for merge.

Also is it worth having a separate package for the multi-tenancy code? As long as you have a standard interface it will keep it more modular and more readable

Yes, last commit prepares for that. Opened #63 to continue discussion.


Create utility that asserts that IRModules aren't modified in-place

Background: In TVM, the IRModule data structure is intended to be immutable. This is a property which unfortunately can't be enforced by a C++ language construct such as const because it is perceived to be too big of a hammer for that problem (I think one of the core challenges is that due to pointers, it's too difficult to propagate const through generic data structures such as Map). Instead, we have to enforce this through convention of not implementing functions on IR data structures which may mutate them.
We are pretty good about this but unfortunately definitely not perfect. We could use a backstop here to provide us a guarantee, in test, that a pass doesn't mutate an IRModule but instead creates a copy wherever state is changed. This task captures writing that test utility.

@gigiblender may take a look at this

#11498


Checkbox "check all" in header does not appear

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here

Current behavior
I copied code from demo:
https://github.com/swimlane/ngx-datatable/blob/master/demo/selection/selection-chkbox.ts#L15
In my template i have checkbox for each row, but in header, the checkbox for "check all or uncheck all" doesn't appear.
Expected behavior
When i use
<ngx-datatable-column
[width]="30"
[headerCheckboxable]="true"
[checkboxable]="true">
Checkbox for check all should appear in header.

Table version: 4.2.0

Angular version: 2.4.1

Browser: Chrome

Language: Typescript

and how to align text for entire column?
i see the cssClasses have been removed from column.directive ??
https://github.com/swimlane/ngx-datatable/pull/416/commits/117370b9adcee11cd891038294713f43f31bb3c1
so how to use them?

update: header checkbox appeared in version 5.0.0
But it doesn't check all checkboxes, just do nothing. In demo page :
http://swimlane.github.io/ngx-datatable/#     <-
Checkbox aslo doesn't work.

I can confirm this. The checkbox is there and does not check all of the checkboxed rows. It will however clear any selected rows.

It's strange behavior when you click the checkbox to select all rows and they are not checked. To check all the boxes you can use the method below.
onSelect({ selected }) {
  this.selected = selected;
}

I have the same problem."CkeckBox all" doesn't  appear. My version is 7.1.1

What I mentioned in my previous comment does not work. I've created a workaround by using a templates with my own checkboxes. The problem is that the checkboxes in the body and header are not properly communicating with each other, which leads to this kind of strange behaviour.

@Gamemaniak please show your code

closing due to inactivity

Add <[selectionType]="'checkbox'"> property to
Ex :<ngx-datatable class="material" [rows]="rowset"
[columnMode]="'force'"
[headerHeight]="50"
[footerHeight]="50"
[rowHeight]="'auto'"
[limit]="10"
[selectionType]="'checkbox'"
(activate)="onActivate($event)"
(select)='onSelect($event)' >

is there any update on this issue ? checkbox on the header still doesnt appear.
Im using version 14.0.0