New package: Ahead v0.1.0

Registering package: Ahead
Repository: https://github.com/Techtonique/Ahead.jl
Created by: @thierrymoudiki
Version: v0.1.0
Commit: 204df83475f0ecfb601100e42d013273c621d7d8
Git reference: HEAD
Description: Univariate and multivariate time series with uncertainty quantification

Aheadsimilar to Fread? :open_mouth:

@JuliaRegistrator Aheadsimilar to Fread? :open_mouth:

Your new package pull request does not meet the guidelines for auto-merging. Please make sure that you have read the General registry README and the AutoMerge guidelines. The following guidelines were not met:

Package name similar to 1 existing package.

Similar to Fread. Damerau-Levenshtein distance 2 is at or below cutoff of 2.

Note that the guidelines are only required for the pull request to be merged automatically. However, it is strongly recommended to follow them, since otherwise the pull request needs to be manually reviewed and merged by a human.
After you have fixed the AutoMerge issues, simple retrigger Registrator, which will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless of course the AutoMerge issue is that you skipped a version number, in which case you should change the version number).
If you do not want to fix the AutoMerge issues, please post a comment explaining why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the Julia Slack to ask for help. Include a link to this pull request.
Since you are registering a new package, please make sure that you have also read the package naming guidelines: https://julialang.github.io/Pkg.jl/dev/creating-packages/#Package-naming-guidelines-1
If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment. You can edit blocking comments, adding [noblock] to them in order to unblock auto-merging.

Yes, it is - the difference is only 2 charatcters, which is the cutoff.
Name similarity isn't an issue though, this is just an automated check to prevent typosquatting. More broadly though did you really intent to register this package with the General registry? It has no documentation so isn't really useful for anyone at this point. I see that this is a wrapper package around an R package that you maintain, maybe have a look at other R wrapper packages like https://github.com/jmboehm/Alpaca.jl to get an idea of how people usually do this in Julia.

Technically, yes. Semantically...
The 'General registry'. Warm welcome. Not sure. The -- existing -- documentation was aimed to be gathered in the same place . On PyPI I don't document.

Yes, it is - the difference is only 2 charatcters, which is the cutoff.
Name similarity isn't an issue though, this is just an automated check to prevent typosquatting. More broadly though did you really intent to register this package with the General registry? It has no documentation so isn't really useful for anyone at this point. I see that this is a wrapper package around an R package that you maintain, maybe have a look at other R wrapper packages like https://github.com/jmboehm/Alpaca.jl to get an idea of how people usually do this in Julia.

As I said, this is an automated check to prevent typosquatting, so all it is designed to do is detect technical naming conflicts. As I also said, it shouldn't be an issue in this case - it simply prevents automerging, but as the name is actually not very similar and you have a good reason to stick with this particular name given it wraps an existing package, it won't prevent a manual merge.
How you document the functionality of your package is of course up to you, but you probably should at least allow Julia users to somehow find that documentation, e.g. by stating in the Readme and docstrings to your package where actual documentation (which shows how to use the Julia wrapper) can be found. I see you have a Python wrapper as well which has a good Readme that shows a Python user how to use the package from Python, so that's probably what's needed for the Julia version as well.

I can update the README, and provide a link to the documentation (which mirrors the R version).

As I said, this is an automated check to prevent typosquatting, so all it is designed to do is detect technical naming conflicts. As I also said, it shouldn't be an issue in this case - it simply prevents automerging, but as the name is actually not very similar and you have a good reason to stick with this particular name given it wraps an existing package, it won't prevent a manual merge.
How you document the functionality of your package is of course up to you, but you probably should at least allow Julia users to somehow find that documentation, e.g. by stating in the Readme and docstrings to your package where actual documentation (which shows how to use the Julia wrapper) can be found. I see you have a Python wrapper as well which has a good Readme that shows a Python user how to use the package from Python, so that's probably what's needed for the Julia version as well.

@nilshg @JuliaRegistrator @JuliaHubRegistrator  Hi, any update on this? Also (this might not be the best place for it), any tips of any existing CI templates for  testing on more platforms? Having various errors depending on the platform.

Readme looks fine, but this can't be automerged due to the name similarity. It needs a manual merge, easiest is probably to ping the #pkg-registration channel on the Julia lang slack

What if I don't use slack (which is the case) ? :)

Slack isn't required, maintainers also check on PRs without them being bumped on Slack. In this case however I have put a message in the Slack channel to hopefully speed things up.

I appreciate it. Cheers

The package can't be loaded:
ERROR: LoadError: REvalError: Error in library(ahead, lib.loc = ".") :
  there is no package called 'ahead'

Please read https://github.com/JuliaRegistries/General/blob/8edde9cccb3bc49ced997525a7b607ef61aac5f7/README.md#my-package-fails-to-load-because-it-needs-proprietary-softwareadditional-setup-to-work-what-can-i-do, but the best solution would really be to make this actually work.

@giordano this is a workaround for cases when the package can't be installed by a 'non-staff' member. GitHub Actions tests won't pass without it. Or maybe you'd suggest something else?

Slack isn't required, maintainers also check on PRs without them being bumped on Slack.

Do they really? Not my experience ;-) But you might be able to get a non-maintainer post on your behalf on Slack. As @nilshg did, in this case.

Or maybe you'd suggest something else?

Yes, reading https://github.com/JuliaRegistries/General/blob/8edde9cccb3bc49ced997525a7b607ef61aac5f7/README.md#my-package-fails-to-load-because-it-needs-proprietary-softwareadditional-setup-to-work-what-can-i-do.  Or making loading the R package work.

Or maybe you'd suggest something else?

Yes, reading https://github.com/JuliaRegistries/General/blob/8edde9cccb3bc49ced997525a7b607ef61aac5f7/README.md#my-package-fails-to-load-because-it-needs-proprietary-softwareadditional-setup-to-work-what-can-i-do. Or making loading the R package work.

All I see below is green checks.

“2 failing and 9 successful checks”
???

All I see below is green checks.

I don't

Also, quoting from https://github.com/JuliaRegistries/General/pull/98771#issuecomment-1888911404

I was not able to load the package (i.e. import Ahead failed). See the CI logs for details.

“2 failing and 9 successful checks”
???

@goerz failing to merge, that means. All the others tests do pass on Ubuntu. Read carefully.

All I see below is green checks.

I don't
Also, quoting from #98771 (comment)

I was not able to load the package (i.e. import Ahead failed). See the CI logs for details.

@giordano indeed, on some platforms it fails randomly. But not on your official template. Quoting 'can't be automerged due to the name similarity'.

Read carefully

Good luck with your registration. I’m out.

Read carefully

Good luck with your registration. I’m out.

@goerz Ha ha. Honesty is disturbing right? :smiley_cat: Bye

This is what I see:

The log is also the AutoMerge CI job (see here), which tries to ultimately install the package too. Note that the original message by the bot also reported that it can't load the package:

I was not able to load the package (i.e. import Ahead failed). See the CI logs for details.

Honesty is disturbing right? 😺 Bye

@thierrymoudiki This isn't working very well, please refrain from further comments like that.

indeed, on some platforms it fails randomly.

It's not random, the R package isn't installed.  I'm not going to repeat it a fourth time as I'm not interested in wasting more time in this discussion, please read https://github.com/JuliaRegistries/General/blob/8edde9cccb3bc49ced997525a7b607ef61aac5f7/README.md#my-package-fails-to-load-because-it-needs-proprietary-softwareadditional-setup-to-work-what-can-i-do.

Honesty is disturbing right? 😺 Bye

@thierrymoudiki This isn't working very well, please refrain from further comments like that.

indeed, on some platforms it fails randomly.

It's not random, the R package isn't installed. I'm not going to repeat it a fourth time as I'm not interested in wasting more time in this discussion, please read https://github.com/JuliaRegistries/General/blob/8edde9cccb3bc49ced997525a7b607ef61aac5f7/README.md#my-package-fails-to-load-because-it-needs-proprietary-softwareadditional-setup-to-work-what-can-i-do.

@giordano More factual details here ;) : https://github.com/Techtonique/Ahead.jl/actions/runs/7710059555

Not sure why this thread has disintegrated to this extent, but just to clarify:

failing to merge AUTOMATICALLY, that means. All the others tests do pass on Ubuntu. Read carefully.

"All the other tests" are just the CI of the General registry (which this is a PR to), not the CI of your package. In short, all they tell us is that the General registry is not broken if Ahead is added to it.
The one check that is failing is automerge which as you rightly point out is checking whether the package can automatically be merged or needs human intervention. Here as discussed earlier the check failed due to name similarity, which is not an issue for this package so that it could be merged manually.
However if you look into the failed action as @Seelengrab shows above what you'll see is that the check failed because the package can't be loaded, i.e. it is not currently working. This is also confirmed by your own CI, which is the relevant one here:

This doesn't look like random failures, but rather consistent failures to do with an apparent issue with how the package is built. This should be fixed before a merge to General - all that the automerge action is doing here is checking that a package registered in General can actually be sucessfully installed, which is imho a low bar.

More facts on the facts, just in case. Windows, macOS, Ubuntu, Julia 1.6 and 1.10:
https://github.com/Techtonique/Ahead.jl/actions/runs/7711922129/job/21018276042
The most accurate answer for all of us wasn’t ‘it doesn’t work on my machine’
or ‘you can’t read’ , but rather ‘it doesn’t work on Windows right now’. Or maybe... testing more OSes in the official CI template.

Looks like you've sorted the installation issues - if you trigger the registration bot again (without changing version number or anything else) the PR should update and the automerge check should be re-run.

In this case, they might actually be better off updating the version and submitting a new registration. Even if the automerge issue is solved, there are a lot of blocking comments on this one. Mosè isn't going to be back to unblock his, and I'm not sure another maintainer is going to merge this manually (future tip: don't be rude to registry maintainers when you need their help).
I can override the name similarity check on a new submission.


Enhancement to generate mapping that creates new or updates existing

I think it'd be useful to allow an additional parameter that is the same as the destination type which could be used to update an existing object if it exists. So, given a signature like this:
public MyEntity Map(MyModel model, MyEntity entity)
{
}

It could generate code like this:
public MyEntity Map(MyModel model, MyEntity entity)
{
    entity = entity ?? new MyEntity();
    entity.Prop1 = model.Prop1;
    entity.Prop2 = model.Prop2;
    return entity;
}

It should work the same if using an optional parameter:
public MyEntity Map(MyModel model, MyEntity entity = null)
What do you think?

Hi @aeslinger0
Sorry for the delay, I focused on another issue reported by you #44 and totally forgot about this one.
I would like to get back to this subject if it is still a matter.
Could you provide a sample situation when this type of proposed mapping would be useful?

I think I want to take back this request. I was thinking it would be handy for the mapping function to instantiate a new object if an existing object doesn't exist. Like when you have a "Save" method that would upsert an entity. I now think it's actually better to create the new instance outside of the mapping function versus what I wrote above since you could accidentally create a new instance when you meant to update an existing instance if the existing instance could not be found (which should return an error instead).  I see you already have a method for updating an existing object, so I don't think anything else needs to be done. So, nevermind :)


Pull Request API

Adds the ability to submit pull requests. See documentation.
Currently only allows to create and show pull requests. Functionality to accept/reject and provide feedback will be included in a future pull request.

Pull Request Test Coverage Report for Build 203

106 of 106 (100.0%)  changed or added relevant lines in 9 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.5%) to 91.637%

Totals

Change from base Build 195:
0.5%

Covered Lines:
1567

Relevant Lines:
1710

💛  - Coveralls


[2.0.3] Available from PIP for Ubuntu 18.04 + Python 3.6

From https://github.com/tabatkins/railroad-diagrams/commit/7fc0602821214267eaa8c6c3b0826589a7ccc950 the minimal Python requirement >= 3.7, but https://pypi.org/project/railroad-diagrams/2.0.3/ is still availble from PIP for Ubuntu 18.04 + Python 3.6:
root@748b3d29b97a:~# lsb_release -a
LSB Version:    core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.6 LTS
Release:    18.04
Codename:   bionic

root@748b3d29b97a:~# python3 --version
Python 3.6.9

root@748b3d29b97a:~# pip list --outdated | grep railroad-diagrams
railroad-diagrams 1.1.1   2.0.3  wheel

By adding python_requires=">= 3.7" to setup.py we could prevent this behavior precisely.
Signed-off-by: Wong Hoi Sing Edison<EMAIL_ADDRESS>

Please also yank 2.0.0, 2.0.1, 2.0.2 and 2.0.3 from https://pypi.org/project/railroad-diagrams/, if possible ;-)

For now I give a quick dirty workaround with https://github.com/alvistack/tabatkins-railroad-diagrams/commit/b3ded9548fa84b685f2957809708ea11ac37b798#diff-60f61ab7a8d1910d86d9fda2261620314edcae5894d5aaa236b821c7256badd7, also manually disable https://build.opensuse.org/repositories/home:alvistack/tabatkins-railroad-diagrams-2.0.3 OBS build for any Python < 3.7 OS.

Right, I always forget you've got to update multiple things to let the nice computer know what versions you support. Sigh.
Okay, 2.0.4 released with a python_requires, and yanked the other 2.0.* versions.

@tabatkins seems the changes didn't go to our GIT commit yet? But just changed locally and pushed to Pypi directly?

Sigh, yeah, pushed to GH now. ^_^

@tabatkins yes get the commit from GH now ;-)
BTW, wish you a kindly consideration for #91, which could also simplify our life as downstream deb/rpm packager, and so we could also providing you feedback ASAP if case happened as this PR ;-)


Fix transformc with derivs when using OCIO

I have no idea how this ever worked. In fact, it must never have, because
our checked-in reference output was wrong. But it kept matching the same
wrong until it didn't, and became a different kind of wrong on at least
one machine.
When doing transformc, where the space names necessitated using OCIO for
the transformation math, and only for the derivative case (the non-deriv
was fine all along), we were simply passing the wrong stride parameters
to the colorproc->apply() call.
Also, I noticed that we were trying to save a per-context "last
transformation" to avoid the lookup when doing repeats of needing the
same colorproc (basically, a 1-item LRU cached lookup of the
colorproc). But we never saved the space name, so the cache was not
operating.

LGTM


build(go): use go1.20

What this PR does
Use go 1.20.

Current dependencies on/for this PR:

main

PR #389

PR #387   👈

This comment was auto-generated by Graphite.

Codecov Report

:exclamation: No coverage uploaded for pull request base (deprecated_global_rand_seed@49b94d8). Click here to learn what that means.
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@                      Coverage Diff                       @@
##             deprecated_global_rand_seed     #387   +/-   ##
==============================================================
  Coverage                               ?   63.37%
==============================================================
  Files                                  ?      131
  Lines                                  ?    17609
  Branches                               ?        0
==============================================================
  Hits                                   ?    11160
  Misses                                 ?     5901
  Partials                               ?      548

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

@ijsong queued this pull request to merge with Graphite.

@ijsong merged this pull request with Graphite.


Upgrade to new protobuf version for better parsing performance

/kind feature
Describe the solution you'd like
Upgrade the version of protobuf to gain significantly better parsing performance than previous releases, especially for large payloads.
Anything else you would like to add:
There is a breaking change from version 3.19, see : https://protobuf.dev/news/2022-05-06/
Which means that version has to be requred bigger 4.21.0 and new proto files needs to be regnerated with a newer protoc version.
Potential problems
paddlepaddle still depends on the old prtobuf version
Links
https://github.com/kserve/kserve/pull/3220

@lre 's open PR: https://github.com/kserve/kserve/pull/3220


Add the ability to run tests from the source code files

First off, this is an excellent extension. I love how easy it is to run individual tests via cmd + shift + P.
There is a feature in the Golang extension which I feel would be great to incorporate into this extension to make running tests even easier. Specifically, there is a code lens that enables you to run tests right from the source code files as show in the image below:

I'm not positive, but it seems that the code at https://github.com/Microsoft/vscode-go/blob/master/src/goRunTestCodelens.ts is where the magic happens in the Golang extension. Anyways, I thought it would be worth posting here for feedback as to whether this would be useful, and if so, possible to implement in this extension.

Thanks, yes that should be possible to add.
Would need some restrictions to which files and functions they would appear on though:

A file must end in *Test.php
Function must start with test* or have @test in the docblock docs

Then we could add these (code lenses?) to test the whole class or single tests.
I'd also add a flag: disableCodeLense: default false.

Added this feature now ages later and released a new version 4.8.0


Vagrant staging

This pull request:

Refactors variables to use a nested hierarchy
Adds a staging Vagrantfile and a deploy for it
Produces stable staging and QA deploys
(Note: when running staging playbook add -e ref=develop, because staging Winthrop is currently aimed at deploying current code base)

Finally got a chance to take this for a spin.
Documentation seems to be pretty thorough and clear so far.  Was able to provision a vagrant machine and get started. I had to change permissions on vagrant/id_rsa before ansible would run (permissions were too open).  Is there anyway that can be done automatically?
Tried running the winthrop staging deploy without any options - failed do to a python dependency that isn't available anymore (outdated python3 branch of piffle that no longer exists). I see your note now that you don't expect this to work anyway, but wanted to comment that the error message is pretty hard to read. Can we output the actual error message with line breaks rendered? (This is not urgent, obviously, but it would be nice to have.)
I tried again with -e ref=develop and this time I got an error on running compress.
errored running the manage.py compress step - I think it's saying that node-sass is not installed? Again, error messages are difficult to read.  Happy to troubleshoot this myself, but not sure where to start.
Minor quibble on the naming: winthrop_stag is a little weird/distracting since stag is actually a word. I would recommend shorting to a non word (stg? not great either) or just using the full word (it's not that much longer).
I was looking at three variant playbooks for winthrop and wondering if we can put playbooks in sub .directories so they'll be more organized?  (It seems like it will quickly get unwieldy as we add other projects). Or maybe production could stay top-level but staging and qa could be in a winthrop folder?
I found this github issues discussing playbooks in subdirectories: https://github.com/ansible/ansible/issues/12862
It looks like adding roles_path = roles to ansible.cfg gets a good portion of the way there, but there are other relative paths (like template dir) that would need an ansible home directory. Not sure what other implications it would have.

@rlskoeser I'll double-check the winthrop staging. It's been running cleanly for me, but it may be the case that I missed something. The key I thought I had added some help for but again, working in a different branch so may have done something with it. It's a pain because git stores files with 644 and 755 as its only two defaults and we need 600 even though it's a key we know to be completely insecure.
The naming of winthrop_stag I'll drop to winthrop_stg or similar. The actual issue is that I'm technically creating an inline group and so it overlaps with the real winthrop_staging. If I just make staging localhost, ansible gets confused and proceeds to try to use the actual host not the Vagrant instance.
Re: subdirectories for playbooks, I like the idea but think given the discussion on the linked issue that we should leave them top dir. Its clearly an idea that Ansible needs to account for (and linking our issue to theirs is a good start to adding to people asking for it), and it would make a huge amount of sense... but for now, I'm inclined to think that forcing Ansible into a configuration it isn't quite intended for would be a bad idea.

@rlskoeser I still can't reproduce the staging error so that may be something to look at in person. The only thing I can think of is that something didn't provision correctly on the VM (vagrant destroy && vagrant up would do a full purge).
I believe I've moved things so that the insecure deploy key will get its permissions set rightly before ever being invoked.


Add Webhooks module

Adds a Webhooks module with a single function for constructing / validating a web hook event, see: https://workos.com/docs/webhooks/securing-your-webhook-endpoint/validating-events-are-from-workos.  Implementation / tests are roughly based off the node implementation.
Not sure if you're currently looking for contributions or not, if not, no worries, feel free to ignore / reject this PR, I needed to validate incoming webhooks so figured I might as well add to the SDK.  Thanks for the work on the elixir SDK, has been a great time saver and is working awesome so far!

Turns out this is still a WIP, signature is being miscalculated.


[3.x] Backport KinematicBody move_and_slide and move_and_collide fixes

Backport #49901 and #50063 to 3.x.
These two PRs together make both move_and_collide and move_and_slide more reliable and after running a lot of tests (see original PRs for details) I'm confident they won't cause major regressions.
Co-authored by @fabriceci
Supersedes #49902

@akien-mga Thanks, it's rebased.

Thanks!

Would it be possible to consider this for an update to move_and_slide? https://github.com/godotengine/godot-proposals/issues/2751

Hi. I have a little platformer game. the player moves with move_and_slide_with_snap. it works fine with godot 3.3.3 and 3.3.2, but got problems with 3.4 b4. The problem is when the player is over a platform that moves from side to side, the platform moves, but the player do not. The platform is made with a tileset. The static body is made with the tileset to and moved with an animation player. Thanks

@crapaam Hi! Please open an issue with a test project so someone can investigate the regression.


How can I tell vscode always to use the workspace typescript version ?

On the right bottom, we can select typescript version, default is the current vscode build-in typescript version. As a developer, I thinks it's better to use the different typescript version for different workspaces (especially the typescript version in their package.json). How can I tell vscode always to use the workspace typescript version ?
Actually, I was experience an issue with the version not being specified in workspace version. So I think use the workspace version is always good ? I don't know.

See #135713 and the typescript.enablePromptUseWorkspaceTsdk setting


[VS Code] SecKeychainAddGenericPassword() failed: The user name or passphrase you entered is not correct.

Error:
SecKeychainAddGenericPassword() failed: The user name or passphrase you entered is not correct.
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
0.2.405

protocolVersion
2.1

applicationName
VSCode

applicationVersion
1.22.2

platformName
MacOS

platformVersion
17.5.0

@justdomepaul Thanks for raising the issue.  We cover this in our troubleshooting https://docs.microsoft.com/en-us/visualstudio/liveshare/troubleshooting#sign-in
To quote it:
This is almost always due to a common problem with macOS where password changes are not reflected in the login keychain. Try going into "Keychain Access", locking the login keychain and then unlocking it again. This may be enough to resolve the problem, but if you are unable to unlock it with your current password, try your previous one. If that works, change the login keychain password to your current password. See here for details.
Let us know if this resolves your issue.

I can verify that locking + unlocking worked on macOS.

@SamVerschueren Great! We're looking at improving the error message here so it is less confusing for people in the future.  Thanks for reporting it!


[Authoring] findDOMNodeOwner function cannot find Action on the CardElement itself

Target Application
Web browser
Application Operating System
Windows
Schema Version
1.5
Problem Description
When calling card.findDOMNodeOwner with a HTML element representing an Action directly on the card (not ActionSet), it return CardElement. However, when calling with an Action inside ActionSet, it return the Action object.
In the code snippet below, we have 2 buttons:

An Action inside an ActionSet on the body of the card, it say "Aloha!"
An Action attached below the card, it say "Hello, World!"

When calling findDOMNodeOwner, the result is respectively:

The Action object, this is correct
The CardElement object (i.e. the root card), this is incorrect

Also, note this issue also applies to Action inside the Action.ShowUrl, where the findDOMNodeOwner is also AdaptiveCard, not the actual Action.
Expected Outcome
I believe the 2nd result should be the Action object from the CardElement, i.e. same as card.getActionAt(0).
Actual Outcome
The root CardElement.
Card JSON
{
    "type": "AdaptiveCard",
    "body": [
        {
            "type": "ActionSet",
            "actions": [
                {
                    "type": "Action.OpenUrl",
                    "title": "Aloha!",
                    "url": "https://bing.com/"
                }
            ]
        }
    ],
    "actions": [
        {
            "type": "Action.OpenUrl",
            "title": "Hello, World!",
            "url": "https://bing.com/"
        }
    ],
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "version": "1.5"
}

Repro Steps
const card = new AdaptiveCard();

card.parse({
  type: 'AdaptiveCard',
  body: [
    {
      type: 'ActionSet',
      actions: [
        {
          type: 'Action.OpenUrl',
          title: 'Aloha!',
          url: 'https://bing.com/'
        }
      ]
    }
  ],
  actions: [
    {
      type: 'Action.OpenUrl',
      title: 'Hello, World!',
      url: 'https://bing.com/'
    }
  ],
  $schema: 'http://adaptivecards.io/schemas/adaptive-card.json',
  version: '1.5'
});

const [firstButton, secondButton] = card.render().querySelectorAll('.ac-pushButton');

expect(firstButton.innerText).toBe('Aloha!');
expect(secondButton.innerText).toBe('Hello, World!');

const firstCardObject = card.findDOMNodeOwner(firstButton);
const secondCardObject = card.findDOMNodeOwner(secondButton);

expect(firstCardObject.toJSON()).toHaveProperty('type', 'Action.OpenUrl');
expect(secondCardObject.toJSON()).toHaveProperty('type', 'Action.OpenUrl'); // This line failed, the "type" expected to be "Action.OpenUrl", however, actual is "AdaptiveCard".

thanks @compulim for submitting the issue :)
we'll have a look soon :)


Search on gender using lowercase is not working. (Search on tokens should not be case sensitive https://www.hl7.org/fhir/search.html#token)

http://<IP_ADDRESS>/careconnect/STU3/Patient?gender=male
Expected 51 patients.
Received 200-OK no patients.
Are codes case insensitive?

duplicate of #1

https://github.com/nhsconnect/careconnect-reference-implementation/issues/1

https://github.com/nhsconnect/careconnect-reference-implementation/issues/12

Duplicate of issue 3 https://github.com/nhsconnect/careconnect-reference-implementation/issues/3


selinux::users && selinux::logins

Would you like to implement selinux::users ( semanage user ) and selinux::login ( semanage login )?

I'm probably not going to work on these, but if anyone wants to, any of the other providers should be a good starting point.

I will probably do this to praticing writing ruby types. :) but only after we released 1.0.0 and 2.0.0.

I've done this in my ::selinux wrapper so I can share my code if you want.

@kreon Send a PR and let's take a look. :)

I would if the code was placed in the module.
But it's inside our production wrapper for our defined selinux policy settings.
All that I can is to cut some code and show you as attachment.

Hey folks, I stumbled across this issue while trying to find a module that will allow me to manage the SElinux context of the users to comply with the DISA STIG for RHEL 7.  Adding this functionality to the module would be extremely beneficial to customers in the US Federal space that have to comply with NIST SP 800.
For reference, here is the STIG item in question:

Red Hat Enterprise Linux 7 Security Technical Implementation Guide :: Version 2, Release: 3
Benchmark Date: 26 Apr 2019
Vul ID: V-71971 |   | Rule ID: SV-86595r2_rule |   | STIG ID: RHEL-07-020020 |
Severity: CAT II |   | Classification: Unclass
Group Title: SRG-OS-000324-GPOS-00125
Rule Title: The Red Hat Enterprise Linux operating system must prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
Discussion: Preventing non-privileged users from executing privileged functions mitigates the risk that unauthorized individuals or processes may gain unnecessary access to information or privileges.
Privileged functions include, for example, establishing accounts, performing system integrity checks, or administering cryptographic key management activities.  Circumventing intrusion detection and prevention mechanisms or malicious code protection mechanisms are examples of privileged functions that require protection from non-privileged users.
Check Text: If an HBSS or HIPS is active on the system, this is Not Applicable.
Verify the operating system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
Get a list of authorized users (other than System Administrator and guest accounts) for the system.
Check the list against the system by using the following command:
# semanage login -l | more
Login Name SELinux User MLS/MCS Range Service
__default__ user_u s0-s0:c0.c1023 *
root unconfined_u s0-s0:c0.c1023 *
system_u system_u s0-s0:c0.c1023 *
joe staff_u s0-s0:c0.c1023 *

All administrators must be mapped to the "sysadm_u" or "staff_u" users role.
All authorized non-administrative users must be mapped to the "user_u" role.
If they are not mapped in this way, this is a finding.
Fix Text: Configure the operating system to prevent non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
Use the following command to map a new user to the "sysdam_u" role:
# semanage login -a -s sysadm_u <username>
Use the following command to map an existing user to the "sysdam_u" role:
# semanage login -m -s sysadm_u <username>
Use the following command to map a new user to the "staff_u" role:
#semanage login -a -s staff_u <username>
Use the following command to map an existing user to the "staff_u" role:
# semanage login -m -s staff_u <username>
Use the following command to map a new user to the "user_u" role:
# semanage login -a -s user_u <username>
Use the following command to map an existing user to the "user_u" role:
# semanage login -m -s user_u <username>
References
CCI: CCI-002165: The information system enforces organization-defined discretionary access control policies over defined subjects and objects.
NIST SP 800-53 Revision 4 :: AC-3 (4)
CCI-002235: The information system prevents non-privileged users from executing privileged functions to include disabling, circumventing, or altering implemented security safeguards/countermeasures.
NIST SP 800-53 Revision 4 :: AC-6 (10)

AFAIK currently nobody is working on this, but PRs are very welcome.

I already developed these features but my code is for old module versions.

16 мая 2019 г., в 17:45, Ewoud Kohl van Wijngaarden<EMAIL_ADDRESS>написал(а):
AFAIK currently nobody is working on this, but PRs are very welcome.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Write post on productradar.ru

https://productradar.ru

NOTE: This repository is no longer supported or updated by @gomzyakov . If you wish to continue to develop this code yourself, we recommend you fork it.


Updated index.md from a stub.

Added a cautionary note about the somewhat regular issue with Glitch where the FCC boilerplate app does not import. This is a common complaint on the forum from people who have no idea that the issue stems from Glitch.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

Closed and Reopened this PR to attempt to resolve a specific Travis build failure.

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 🎉


Another case of the virtual bottom being miscalculated

Windows Terminal version
Commit ec726e7ba70b760f98eb1e1ea1d71124536783c0
Windows build number
10.0.19041.1415
Other Software
vttest
Steps to reproduce

Open a bash shell in conhost.
Immediately run vttest.
Select test 4 (Test of double-sized characters).
Press enter twice until it gets to the 132-column test.

Expected Behavior
It should display a 132-column version of the test output with examples of double width and double height content.
Actual Behavior
The page appears mostly blank, but if you scroll back in the buffer, you can see the test content has rendered on the page above (partially overwriting the previous test). This doesn't seem to happen (at least not consistently) if you've already scrolled down in the buffer when you start the test.
I believe this is another victim of PR #12972. And it looks like the source of the problem is again in the ResizeWithReflow code, which picks a position for the virtual bottom that isn't far enough down. I think this is because the majority of the page is blank at the time of the resize.

I should add that I have an idea for fixing this: Essentially what we'd need to do is save the distance between the cursor row and the virtual bottom prior to resizing, and then add that distance to the new cursor row after resizing, and that should give us a good estimate of where the new virtual bottom ought to be. We'd still probably also need to take into account the other boundaries that we're currently checking, like the last non-space row, and the viewport height.
If that works, I'll try and put together a PR with the fix on Thursday.

(FWIW: I don't necessarily think you do, but if you do feel bad about introducing more virtual bottom bugs . . . just think about all the ones we already had that you helped to enumerate and fix(!). In true Windows Console fashion, and in the fashion of every other project everywhere, you can't make an omelet without breaking a few ~lions~ eggs.)


Kubernetes config doesn't work anymore on azure

Hello,
Redis container seem to fail to load on kubernetes config on azure website.
Docker error
2019-04-12 12:11:48.466 ERROR - Container create failed for ******__a4f9_redis_0 with System.AggregateException, One or more errors occurred.
InnerException: Docker.DotNet.DockerApiException, Docker API responded with status code=BadRequest, response={"message":"conflicting options: dns and the network mode"}
Can you confirm ?
Thanks

Same issue here with all yamls I tried, including official samples.

@yiliaomsft For awareness.

Followed-up internally.
#please-close

@msangapu-msft have you found a fix for this yet? I am getting the same issue with multi-container kubernetes yamls of my own.

Hi team, we've removed Kubernetes configuration support based on customer feedback. For Kubernetes customers, we recommend Azure Kubernetes Service (AKS).
Hope that helps!

@msangapu-msft thanks for your response.
What customer feedback did you base your decision on to keep the Kubernetes tab in the app service container configuration section - thus forcing me to waste my time attempting to get a feature to work that has been discontinued?

Further, why do you keep outdated and confusing promotional material online promoting a feature that doesn't exist anymore?
https://azure.microsoft.com/de-de/updates/app-service-multi-container-and-linux-support-for-ase-preview/

@waltherg Sorry for the trouble. Yes, this was announced "in preview" last year. Since then, due to the low adoption rate, engineering decided to stop supporting it. We recommend using AKS on Azure. "In preview" features are known to change and this was one of those cases. Hope that helps.
This is a Github sample repo and not the appropriate place to voice your concerns. If you have additional feedback, please voice it here: https://feedback.azure.com/ so it's viewed by the appropriate people.


Node types keep getting lost

After a while using VSCode, hovering over Node symbols like require will yield any, where they used to show NodeRequire instead. Likewise all intellisense for Node will be lost.
I can fix this by removing the ~/.cache/typescript dir and allowing it to be regenerated, but it keeps happening. Looks like a VSCode bug since the contents of the typescript folder look good.

After removing ~/.cache/typescript:

$ ls -a ~/.cache/typescript
./  ../  2.6/

$ ls -a ~/.cache/typescript/2.6/
./  ../  node_modules/  package.json  package-lock.json

$ cat ~/.cache/typescript/2.6/package.json
{
  "dependencies": {
    "types-registry": "^0.1.315"
  },
  "devDependencies": {
    "@types/axios-mock-adapter": "^1.9.0",
    "@types/chai": "^4.0.10",
    "@types/chai-as-promised": "^7.1.0",
    "@types/circular-json": "^0.4.0",
    "@types/mocha": "^2.2.44",
    "@types/nock": "^9.1.0",
    "@types/node": "^8.5.1",
    "@types/node-fetch": "^1.6.7",
    "@types/proxyquire": "^1.3.28",
    "@types/request": "^2.0.9",
    "@types/sinon": "^4.1.2"
  }
}

$ ls -a ~/.cache/typescript/2.6/node_modules/
 ./   ../   axios/   debug/   follow-redirects/   is-buffer/   ms/  '@types'/   types-registry/

$ ls -a ~/.cache/typescript/2.6/node_modules/@types/
./  ../  axios-mock-adapter/  chai/  chai-as-promised/  circular-json/  form-data/  mocha/  nock/  node/  node-fetch/  proxyquire/  request/  sinon/

This issue was moved to Microsoft/TypeScript#20836


The usage of extract_phrase.py

Sorry to bother, I'am stuck in using extract_phrase.py to extract the constraints.
How can I using this scripts to extract the constrains from my own dataset, it seems like there always has some files lack. What other files should I need to provide except the source and target bpe text according to the arguments in extract_phrase.py.
It has stumped me for a long time, very appreciate if you can give me some detail of how to use it.

You can refer to the example here.

Thanks a lot. I've read over the run_test.sh and try to run it. But it seems like I am missing vocab.$tgt. How can I get the raw_reference with the vocab? Do I need to manually generate it or generate it by some scripts.

@BeatsLeo I am also facing same issue, were you able to solve it yet?

Thanks a lot. I've read over the run_test.sh and try to run it. But it seems like I am missing vocab.$tgt. How can I get the raw_reference with the vocab? Do I need to manually generate it or generate it by some scripts.

you can use the fastbpe getvocab command in the fastBPE repo.


Error to print trial balance business central version 21.0.46256.46853 report 6

Hello,
when I try to print a trial balance, with balance at date <>0 as filter, the error appear:
The supplied column ID '34' cannot be found in the query
Thanks,

Duplicate of https://github.com/microsoft/AL/issues/7224 but I don't think it's on-topic at either location. As a runtime/platform/application issue, it should be reported to MS via Support/Partner, not on GitHub.

Please report bugs via Support/Partner, GitHub is for extensibility issues only. This particular issue is already reported, and fix is in progress.


Skipped catkin tests

Currently, the catkin installed job successfully runs however it skips all of its tests.
Agenda:

Check if other examples' tests are skipped
Investigate whether the job(s) always had skipped tests or if the DEE refactoring caused the tests to be skipped

PR 328 first brought this issue up.

ament_cmake_installed runs a test executable (does not mention specific tests when run)
catkin_installed does not run tests

The rest of the examples explicitly mention tests in the build and test stage.

One easy way to cross-check would be to introduce a failure or bug into one of the test cases, and confirm CI shows red.

I created a branch with the most recent commit from main being "Add some missing semicolons PR 294" that was commited Jun 25. For context, I made my first commit to this repo Aug 21st.
The catkin installed job had the same warning as what was introduced in PR 328. As such, the catkin tests that require gtest were already skipped when the refactoring started taking place.
Here is the warning below:
CMake Warning at /usr/share/catkin/cmake/test/gtest.cmake:159 (message):
  skipping gtest 'drake_catkin_installed_test' in project
  'drake_catkin_installed' because gtest was not found
Call Stack (most recent call first):
  /usr/share/catkin/cmake/test/gtest.cmake:89 (_catkin_add_executable_with_google_test)
  /usr/share/catkin/cmake/test/gtest.cmake:37 (_catkin_add_google_test)
  drake_catkin_installed/CMakeLists.txt:[54](https://github.com/RobotLocomotion/drake-external-examples/actions/runs/11486269912/job/31968186715?pr=330#step:5:55) (catkin_add_gtest)

Let's do the following instead -- open two new issues that are more crisp, and then close this issue as a duplicate of those two.
The two new issues should be titled:

[drake_ament_cmake_installed] Failing tests do not show up in CI
[drake_catkin_installed] Failing tests do not show up in CI

Each ticket should provide a recipe and/or evidence that a broken test still has GHA output showing up as a green bubble, whereas we want the red x in the PR status.  Essentially, make them a good bug report that other people can work on.
Then, I will assign two issues to the ROS people who help curate this repository, and ask them to fix it (not Kitware).

@jwnimmer-tri Okay, will do

Closing this issue as it is now a duplicate of two newly created issues.

Closing this issue as it is now a duplicate of two newly created issues


[MSYS-934]Fix for pfx_password

Signed-off-by: dheerajd-msys<EMAIL_ADDRESS>Description
This change will fix the error ArgumentError: invalid byte sequence in UTF-8
Issues Resolved
Fixes https://github.com/chef-cookbooks/windows/issues/582
Check List

[ ] All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable
[ ] All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD

LGTM. @btm and @tas50 could you please review this ?


Redux state change in drawerchild

Version
Tell us which versions you are using:

react-native-router-flux v4.0.0-beta.14 (v3 is not supported)
react-native v0.46.4
Redux v3.7.2
React-Redux v5.0.5

Expected behaviour
When state changes, the child that is dispatching the actions, should rerender with the new redux state.
Actual behaviour
When state changes, the top child will be rendered and apears on the screen.
Steps to reproduce

Make a drawer with child scenes.
Dispatch redux-action on non-top child.

Please check pure react-navigation first. RNRF just creates react-navigation structures and pass state to it.

I have the same problem and as far as I know (because I checked) there is noting stated in the RNRF documentation.

Stated what? About react navigation usage? Please fork & modify Example or create own project so I could reproduce issue. I can't work with code snippets or English wordings to reproduce issues.

Stated as in: 'They are saying nothing about it'

I don't understand. RNRF is wrapper around react-navigation, so first I need to determine where the error is.

And I need reproducible iOS project. Example of 'good' issue that I solved:
https://github.com/aksonov/react-native-router-flux/issues/2115

I'm working on it

It's an issue in react-navigation I tested it

Have you created issue there? I guess you could use Actions.refresh to refresh screen if necessary. Closing this ticket for now


Implement script to populate DB

Read information from https://github.com/Politica-Para-Todos/pARties and insert it into rails DB. It should be possible to run multiple times.

Finish https://github.com/Politica-Para-Todos/pARties. It is responsible to read information from spreadsheet and markdown and expose it as an API. That API is later consumed by a script to populate our DB


Extension issue

Issue Type: Bug
Extension Name: azurite
Extension Version: 3.9.0
OS Version: Windows_NT x64 10.0.18363
VSCode version: 1.50.1

:warning: We have written the needed data into your clipboard. Please paste! :warning:
{
	"messages": [],
	"activationTimes": {
		"codeLoadingTime": 6469,
		"activateCallTime": 1,
		"activateResolvedTime": 4,
		"activationReason": {
			"startup": true,
			"extensionId": {
				"value": "Azurite.azurite",
				"_lower": "azurite.azurite"
			},
			"activationEvent": "*"
		}
	},
	"runtimeErrors": []
}

@ziizaisoar
Thanks for reporting the issue!
Would you please clarify what's the issue do you concern most? Do you mean Azurite starting loading time in VSC extension is too long?
If so, we will evaluate it, and consider to optimize it in the future.

Hi,
I just inputted Show Running Extensions in command palette and it showed  Azurite Activation taking much longer time than other extensions, so I had it disabled.
Regards
Ji Fang
From: Wei Wei<EMAIL_ADDRESS>Sent: Monday, October 26, 2020 2:13 PM
To: Azure/Azurite<EMAIL_ADDRESS>Cc: Fang Ji<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: [Ext] Re: [Azure/Azurite] Extension issue (#601)
@ziizaisoarhttps://urldefense.com/v3/__https:/github.com/ziizaisoar__;!!Kjv0uj3L4nM6H-I!yQ7JKFxcy1W6f24ZtYm7Aa_6K_Kg8kpH82eiB2M8eEpQL5r1LCvfO8e7x7c$
Thanks for reporting the issue!
Would you please clarify what's the issue do you concern most? Do you mean Azurite starting loading time in VSC extension is too long?
If so, we will evaluate it, and consider to optimize it in the future.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/Azure/Azurite/issues/601*issuecomment-716328283__;Iw!!Kjv0uj3L4nM6H-I!yQ7JKFxcy1W6f24ZtYm7Aa_6K_Kg8kpH82eiB2M8eEpQL5r1LCvf45cf4vo$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AQFLSQ5MPEKD6KWUE76A6LLSMUHP5ANCNFSM4S5CGZ4A__;!!Kjv0uj3L4nM6H-I!yQ7JKFxcy1W6f24ZtYm7Aa_6K_Kg8kpH82eiB2M8eEpQL5r1LCvfNJ_1MNU$.
Schlumberger-Private


Ignore empty codegen modules in outputs

References:
Original report: https://github.com/tokio-rs/prost/issues/228
My report: https://github.com/tokio-rs/prost/issues/724
Partial fix in: https://github.com/tokio-rs/prost/pull/605
Issue with fix: https://github.com/hyperium/tonic/issues/964
Reverted in: https://github.com/tokio-rs/prost/pull/639
After digging in, the issue with the first fix is that while it prevented the file from being generated, it did not prevent the file from being referenced in the "include" file because both locations iterate the module hash. My proposed solution is to instead avoid adding the empty module to the list at all. Then the file does not get output and the include file does not have an entry that would otherwise be referencing an empty file.
Also did a small refactor pass on the surrounding loop to destructure the tuple instead of using tuple.0 syntax wherever it is used.
Tested by reproducing the original issue using tonic-build with the original behavior working then reintroduced the bug, then fixed it with my changes. Manually verified output files and included them in a new rust project to make sure they worked and verified that the extra file is not present in file system or the include file. Also ran cargo test on prost

@trevoranderson thank you for doing this! Would it be possible to add a test of the original behavior that was fixed with this so we can make sure we don't regress in the future?

Made an attempt at that too. I used an proto adapted from the hyperium issue report which reproduces the issue without my fix and works with the fix applied.


Dictionary Renderer Sample

@tyle8552  Can you give this a look over?
Issue: https://devtopia.esri.com/runtime/java-se-sdk/issues/556
Sample I went off:  https://github.com/Esri/arcgis-runtime-samples-qt/tree/master/ArcGISRuntimeSDKQt_CppSamples/DisplayInformation/GraphicsOverlayDictionaryRenderer

I need to do something about this name. There is going to be a dictionary renderer for graphics overlay and feature layer. So I could name it dictionary-renderer-graphicsoverlay.
Other option continuing from my  refeactoring the samples speech. There is already a feature layer category so we can put a dictionary renderer there and if we had a graphics overlay category we could put the other one there.

@john0005 I would follow the pattern set by the Qt team. Looks like they've put it in DisplayInformation.

@john0005 I added a dependency which helps simplify xml parsing. Even if it's not a standard, I think anything that simplifies a part of the sample which is not directly related to our product can be used.
I also simplified some other code. We should try to have less void methods. For example, you would assume createGraphic would create and return a graphic. We shouldn't have to look in that method to see if gets added to the graphics overlay. Making these methods functional allows us to take advantage of streams and pipeline feature/graphic processing.

Only things left is to figure out why mapView.setViewpointGeometryAsync(graphicsOverlay.getExtent() is not working. We should also find out if labels & graphics can be size-reduced when zoomed out.

For zooming out I just made it so that when you zoom out passed a certain level the graphics disappear.
For extent I found out that you have to wait till the graphics are done drawing to the view.
mapView.addLayerViewStateChangedListener(layer -> {
      if(layer.getLayerViewStatus().iterator().next() == LayerViewStatus.ACTIVE){
        mapView.setViewpointGeometryAsync(graphicsOverlay.getExtent());
      }
    });


Implement hook feature

Jenkins depends on: https://github.com/RackHD/on-tasks/pull/383

Hook features need database model and method to post data to user
provided url
Thus hook model is created as well as hook publish method
However hook publish method leverage http tool, http tool is moved from
on-task repo to lib/common

@yyscamper @brianparry @sunnyqianzhang @anhou @iceiilin
As there are too much changes on WIP code, I created a new PR. Here is the old PR and I am going to close it: https://github.com/RackHD/on-core/pull/238

BUILD on-core #1012 : FAILURE

** BUILD build-config-setup  #785: SUCCESS

** BUILD unit-tests  #10957: SUCCESS

** BUILD on-taskgraph #1912: FAILURE

** BUILD build-config-setup  #786: SUCCESS
** BUILD unit-tests  #10958: FAILURE

BUILD on-core #1013 : FAILURE

** BUILD build-config-setup  #792: SUCCESS

** BUILD unit-tests  #10962: SUCCESS

** BUILD on-taskgraph #1914: FAILURE

** BUILD build-config-setup  #793: SUCCESS
** BUILD unit-tests  #10963: FAILURE

BUILD on-core #1014 : UNSTABLE

** BUILD build-config-setup  #820: SUCCESS

** BUILD unit-tests  #10981: UNSTABLE

** BUILD SmokeTest-FIT  #116: SUCCESS

** BUILD CIT  #473: SUCCESS
** BUILD FIT  #359: SUCCESS

** BUILD on-taskgraph #1921: SUCCESS

** BUILD build-config-setup  #821: SUCCESS
** BUILD unit-tests  #10982: SUCCESS

** BUILD on-http #3085: SUCCESS

** BUILD build-config-setup  #822: SUCCESS
** BUILD unit-tests  #10983: SUCCESS

** BUILD on-dhcp-proxy #1081: SUCCESS

** BUILD build-config-setup  #823: SUCCESS
** BUILD unit-tests  #10984: SUCCESS

** BUILD on-tasks #1876: SUCCESS

** BUILD build-config-setup  #824: SUCCESS
** BUILD unit-tests  #10985: SUCCESS

** BUILD on-tftp #870: SUCCESS

** BUILD build-config-setup  #36: SUCCESS
** BUILD unit-tests  #10986: SUCCESS

** BUILD on-syslog #791: SUCCESS

** BUILD build-config-setup  #825: SUCCESS
** BUILD unit-tests  #10987: SUCCESS

BUILD unit-tests  #10981  Error Logs  ▼Test Name: Lookup Service Node ID Cache should resolve pending cache checks once a value is assigned
Error Details: expected false to be truthy
Stack Trace: AssertionError: expected false to be truthy

test this please

:+1:

Please rebase your PR branch to latest master , otherwise, on-tasks unit-test will fail. (task-schema)

BUILD on-multi #68 : FAILURE

** BUILD build-config-setup  #1474: SUCCESS
** BUILD on-core  #1071: FAILURE

** BUILD build-config-setup  #1475: SUCCESS

** BUILD unit-tests  #11528: FAILURE

** BUILD on-taskgraph #2044: SUCCESS

** BUILD build-config-setup  #1476: SUCCESS
** BUILD unit-tests  #11529: SUCCESS

** BUILD on-http #3222: UNSTABLE

** BUILD build-config-setup  #1477: SUCCESS
** BUILD unit-tests  #11530: UNSTABLE

** BUILD on-dhcp-proxy #1125: SUCCESS

** BUILD build-config-setup  #1478: SUCCESS
** BUILD unit-tests  #11531: SUCCESS

** BUILD on-tasks #1970: UNSTABLE

** BUILD build-config-setup  #1479: SUCCESS
** BUILD unit-tests  #11532: UNSTABLE

** BUILD on-tftp #934: SUCCESS

** BUILD build-config-setup  #1480: SUCCESS
** BUILD unit-tests  #11533: SUCCESS

** BUILD on-syslog #835: SUCCESS

** BUILD build-config-setup  #1481: SUCCESS
** BUILD unit-tests  #11534: SUCCESS

BUILD unit-tests  #11530  Error Logs  ▼Test Name: Http.Api.Profiles SB 2.0 GET /profiles should send down redirect.ipxe if a node is new
Error Details: expected 200 "OK", got 500 "Internal Server Error" Response body: { message: 'waterline.hooks.find(...).map is not a function',   status: '500',   UUID: '210c4e1e-ab8d-46f2-a0b9-38f08f6569d5' } Error: expected 200 "OK", got 500 "Internal Server Error"     at Test._assertStatus (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:232:12)     at Test._assertFunction (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:247:11)     at Test.assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:148:18)     at assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:127:12)     at /home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:124:5     at Test.Request.callback (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:703:3)     at IncomingMessage.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)     at emitNone (events.js:72:20)     at IncomingMessage.emit (events.js:166:7)     at endReadableNT (_stream_readable.js:923:12)     at nextTickCallbackWith2Args (node.js:458:9)     at process._tickDomainCallback (node.js:413:17)
Stack Trace: Error: expected 200 "OK", got 500 "Internal Server Error"
    at Test._assertStatus (node_modules/supertest/lib/test.js:232:12)
    at Test._assertFunction (node_modules/supertest/lib/test.js:247:11)
    at Test.assert (node_modules/supertest/lib/test.js:148:18)
    at assert (node_modules/supertest/lib/test.js:127:12)
    at node_modules/supertest/lib/test.js:124:5
    at Test.Request.callback (node_modules/supertest/node_modules/superagent/lib/node/index.js:703:3)
    at IncomingMessage.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)
    at endReadableNT (_stream_readable.js:923:12)
Test Name: Http.Api.Profiles 2.0 GET /profiles/switch/:vendor should throw a 400 on a request from an unknown switch vendor
Error Details: expected body '{"message":"waterline.hooks.find(...).map is not a function","status":"400","UUID":"fe43811a-48e8-49be-b596-c3d55c1122a9"}' to match /Unknown.*vendor/ Response body: { message: 'waterline.hooks.find(...).map is not a function',   status: '400',   UUID: 'fe43811a-48e8-49be-b596-c3d55c1122a9' } Error: expected body '{"message":"waterline.hooks.find(...).map is not a function","status":"400","UUID":"fe43811a-48e8-49be-b596-c3d55c1122a9"}' to match /Unknown.*vendor/     at error (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:265:13)     at Test._assertBody (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:188:18)     at Test._assertFunction (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:247:11)     at Test.assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:148:18)     at assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:127:12)     at /home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:124:5     at Test.Request.callback (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:703:3)     at IncomingMessage.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)     at emitNone (events.js:72:20)     at IncomingMessage.emit (events.js:166:7)     at endReadableNT (_stream_readable.js:923:12)     at nextTickCallbackWith2Args (node.js:458:9)     at process._tickDomainCallback (node.js:413:17)
Stack Trace: Error: expected body '{"message":"waterline.hooks.find(...).map is not a function","status":"400","UUID":"fe43811a-48e8-49be-b596-c3d55c1122a9"}' to match /Unknown.*vendor/
at error (node_modules/supertest/lib/test.js:265:13)
at Test._assertBody (node_modules/supertest/lib/test.js:188:18)
at Test._assertFunction (node_modules/supertest/lib/test.js:247:11)
at Test.assert (node_modules/supertest/lib/test.js:148:18)
at assert (node_modules/supertest/lib/test.js:127:12)
at node_modules/supertest/lib/test.js:124:5
at Test.Request.callback (node_modules/supertest/node_modules/superagent/lib/node/index.js:703:3)
at IncomingMessage.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)
at endReadableNT (_stream_readable.js:923:12)
Test Name: Http.Api.Profiles GET /profiles should send down redirect.ipxe if a node is new
Error Details: expected 200 "OK", got 500 "Internal Server Error" Response body: { name: 'TypeError',   message: 'waterline.hooks.find(...).map is not a function',   stack: 'TypeError: waterline.hooks.find(...).map is not a function\n    at Hook.publish (/home/jenkins/workspace/on-http/build/node_modules/on-core/lib/common/hook.js:33:10)\n    at EventsProtocol.publishExternalEvent (/home/jenkins/workspace/on-http/build/node_modules/on-core/lib/protocol/events.js:311:18)\n    at EventsProtocol.publishNodeEvent (/home/jenkins/workspace/on-http/build/node_modules/on-core/lib/protocol/events.js:368:21)\n    at /home/jenkins/workspace/on-http/build/lib/services/profiles-api-service.js:9:9230\n    at Object.tapHandler (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/finally.js:64:23)\n    at bound (domain.js:287:14)\n    at Object.runBound (domain.js:300:12)\n    at Object.tryCatcher (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)\n    at Promise._settlePromiseFromHandler (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/promise.js:510:31)\n    at Promise._settlePromiseAt (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/promise.js:584:18)\n    at Async._drainQueue (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/async.js:128:12)\n    at Async._drainQueues (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)\n    at Immediate.Async.drainQueues [as _onImmediate] (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)\n    at processImmediate [as _immediateCallback] (timers.js:396:17)',   context: {} } Error: expected 200 "OK", got 500 "Internal Server Error"     at Test._assertStatus (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:232:12)     at Test._assertFunction (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:247:11)     at Test.assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:148:18)     at assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:127:12)     at /home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:124:5     at Test.Request.callback (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:703:3)     at IncomingMessage.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)     at emitNone (events.js:72:20)     at IncomingMessage.emit (events.js:166:7)     at endReadableNT (_stream_readable.js:923:12)     at nextTickCallbackWith2Args (node.js:458:9)     at process._tickDomainCallback (node.js:413:17)
Stack Trace: Error: expected 200 "OK", got 500 "Internal Server Error"
at Test._assertStatus (node_modules/supertest/lib/test.js:232:12)
at Test._assertFunction (node_modules/supertest/lib/test.js:247:11)
at Test.assert (node_modules/supertest/lib/test.js:148:18)
at assert (node_modules/supertest/lib/test.js:127:12)
at node_modules/supertest/lib/test.js:124:5
at Test.Request.callback (node_modules/supertest/node_modules/superagent/lib/node/index.js:703:3)
at IncomingMessage.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)
at endReadableNT (_stream_readable.js:923:12)
Test Name: Http.Api.Profiles GET /profiles/switch/:vendor should throw a 400 on a request from an unknown switch vendor
Error Details: expected 400 "Bad Request", got 500 "Internal Server Error" Response body: { name: 'TypeError',   message: 'waterline.hooks.find(...).map is not a function',   stack: 'TypeError: waterline.hooks.find(...).map is not a function\n    at Hook.publish (/home/jenkins/workspace/on-http/build/node_modules/on-core/lib/common/hook.js:33:10)\n    at EventsProtocol.publishExternalEvent (/home/jenkins/workspace/on-http/build/node_modules/on-core/lib/protocol/events.js:311:18)\n    at EventsProtocol.publishNodeEvent (/home/jenkins/workspace/on-http/build/node_modules/on-core/lib/protocol/events.js:368:21)\n    at /home/jenkins/workspace/on-http/build/lib/services/profiles-api-service.js:9:9230\n    at Object.tapHandler (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/finally.js:64:23)\n    at bound (domain.js:287:14)\n    at Object.runBound (domain.js:300:12)\n    at Object.tryCatcher (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)\n    at Promise._settlePromiseFromHandler (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/promise.js:510:31)\n    at Promise._settlePromiseAt (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/promise.js:584:18)\n    at Async._drainQueue (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/async.js:128:12)\n    at Async._drainQueues (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)\n    at Immediate.Async.drainQueues [as _onImmediate] (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)\n    at processImmediate [as _immediateCallback] (timers.js:396:17)',   context: {} } Error: expected 400 "Bad Request", got 500 "Internal Server Error"     at Test._assertStatus (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:232:12)     at Test._assertFunction (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:247:11)     at Test.assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:148:18)     at assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:127:12)     at /home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:124:5     at Test.Request.callback (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:703:3)     at IncomingMessage.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)     at emitNone (events.js:72:20)     at IncomingMessage.emit (events.js:166:7)     at endReadableNT (_stream_readable.js:923:12)     at nextTickCallbackWith2Args (node.js:458:9)     at process._tickDomainCallback (node.js:413:17)
Stack Trace: Error: expected 400 "Bad Request", got 500 "Internal Server Error"
at Test._assertStatus (node_modules/supertest/lib/test.js:232:12)
at Test._assertFunction (node_modules/supertest/lib/test.js:247:11)
at Test.assert (node_modules/supertest/lib/test.js:148:18)
at assert (node_modules/supertest/lib/test.js:127:12)
at node_modules/supertest/lib/test.js:124:5
at Test.Request.callback (node_modules/supertest/node_modules/superagent/lib/node/index.js:703:3)
at IncomingMessage.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)
at endReadableNT (_stream_readable.js:923:12)

BUILD unit-tests  #11532  Error Logs  ▼Test Name: UcsTool "before all" hook
Error Details: Cannot find module '/home/jenkins/workspace/on-tasks/build/lib/utils/job-utils/http-tool.js'
Stack Trace: Error: Cannot find module '/home/jenkins/workspace/on-tasks/build/lib/utils/job-utils/http-tool.js'
    at require (internal/module.js:12:17)
    at Object.global.helper.require (node_modules/on-core/spec/helper.js:84:16)
    at Context.<anonymous> (spec/lib/utils/job-utils/ucs-tool-spec.js:18:20)
Test Name: Ucs Discovery Job "before all" hook
Error Details: Cannot find module '/home/jenkins/workspace/on-tasks/build/lib/utils/job-utils/http-tool.js'
Stack Trace: Error: Cannot find module '/home/jenkins/workspace/on-tasks/build/lib/utils/job-utils/http-tool.js'
at require (internal/module.js:12:17)
at Object.global.helper.require (node_modules/on-core/spec/helper.js:84:16)
at Context.<anonymous> (spec/lib/jobs/ucs-discovery-spec.js:47:20)

test this please

BUILD on-multi #69 : FAILURE

** BUILD build-config-setup  #1485: SUCCESS
** BUILD on-core  #1072: UNSTABLE

** BUILD build-config-setup  #1486: SUCCESS

** BUILD unit-tests  #11538: SUCCESS

** BUILD on-taskgraph #2046: SUCCESS

** BUILD build-config-setup  #1487: SUCCESS
** BUILD unit-tests  #11539: SUCCESS

** BUILD on-http #3224: UNSTABLE

** BUILD build-config-setup  #1488: SUCCESS
** BUILD unit-tests  #11540: UNSTABLE

** BUILD on-dhcp-proxy #1126: SUCCESS

** BUILD build-config-setup  #1489: SUCCESS
** BUILD unit-tests  #11541: SUCCESS

** BUILD on-tasks #1972: UNSTABLE

** BUILD build-config-setup  #1490: SUCCESS
** BUILD unit-tests  #11542: UNSTABLE

** BUILD on-tftp #935: SUCCESS

** BUILD build-config-setup  #1491: SUCCESS
** BUILD unit-tests  #11543: SUCCESS

** BUILD on-syslog #836: SUCCESS

** BUILD build-config-setup  #1492: SUCCESS
** BUILD unit-tests  #11544: SUCCESS

BUILD unit-tests  #11540  Error Logs  ▼Test Name: Http.Api.Profiles SB 2.0 GET /profiles should send down redirect.ipxe if a node is new
Error Details: expected 200 "OK", got 500 "Internal Server Error" Response body: { message: 'waterline.hooks.find(...).map is not a function',   status: '500',   UUID: '87e5bf0a-ff70-4706-b1bd-e8bba9f8e329' } Error: expected 200 "OK", got 500 "Internal Server Error"     at Test._assertStatus (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:232:12)     at Test._assertFunction (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:247:11)     at Test.assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:148:18)     at assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:127:12)     at /home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:124:5     at Test.Request.callback (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:703:3)     at IncomingMessage.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)     at emitNone (events.js:72:20)     at IncomingMessage.emit (events.js:166:7)     at endReadableNT (_stream_readable.js:923:12)     at nextTickCallbackWith2Args (node.js:458:9)     at process._tickDomainCallback (node.js:413:17)
Stack Trace: Error: expected 200 "OK", got 500 "Internal Server Error"
    at Test._assertStatus (node_modules/supertest/lib/test.js:232:12)
    at Test._assertFunction (node_modules/supertest/lib/test.js:247:11)
    at Test.assert (node_modules/supertest/lib/test.js:148:18)
    at assert (node_modules/supertest/lib/test.js:127:12)
    at node_modules/supertest/lib/test.js:124:5
    at Test.Request.callback (node_modules/supertest/node_modules/superagent/lib/node/index.js:703:3)
    at IncomingMessage.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)
    at endReadableNT (_stream_readable.js:923:12)
Test Name: Http.Api.Profiles 2.0 GET /profiles/switch/:vendor should throw a 400 on a request from an unknown switch vendor
Error Details: expected body '{"message":"waterline.hooks.find(...).map is not a function","status":"400","UUID":"b347ae3a-1570-4cfb-8f4a-9bb4565b4add"}' to match /Unknown.*vendor/ Response body: { message: 'waterline.hooks.find(...).map is not a function',   status: '400',   UUID: 'b347ae3a-1570-4cfb-8f4a-9bb4565b4add' } Error: expected body '{"message":"waterline.hooks.find(...).map is not a function","status":"400","UUID":"b347ae3a-1570-4cfb-8f4a-9bb4565b4add"}' to match /Unknown.*vendor/     at error (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:265:13)     at Test._assertBody (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:188:18)     at Test._assertFunction (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:247:11)     at Test.assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:148:18)     at assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:127:12)     at /home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:124:5     at Test.Request.callback (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:703:3)     at IncomingMessage.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)     at emitNone (events.js:72:20)     at IncomingMessage.emit (events.js:166:7)     at endReadableNT (_stream_readable.js:923:12)     at nextTickCallbackWith2Args (node.js:458:9)     at process._tickDomainCallback (node.js:413:17)
Stack Trace: Error: expected body '{"message":"waterline.hooks.find(...).map is not a function","status":"400","UUID":"b347ae3a-1570-4cfb-8f4a-9bb4565b4add"}' to match /Unknown.*vendor/
at error (node_modules/supertest/lib/test.js:265:13)
at Test._assertBody (node_modules/supertest/lib/test.js:188:18)
at Test._assertFunction (node_modules/supertest/lib/test.js:247:11)
at Test.assert (node_modules/supertest/lib/test.js:148:18)
at assert (node_modules/supertest/lib/test.js:127:12)
at node_modules/supertest/lib/test.js:124:5
at Test.Request.callback (node_modules/supertest/node_modules/superagent/lib/node/index.js:703:3)
at IncomingMessage.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)
at endReadableNT (_stream_readable.js:923:12)
Test Name: Http.Api.Profiles GET /profiles should send down redirect.ipxe if a node is new
Error Details: expected 200 "OK", got 500 "Internal Server Error" Response body: { name: 'TypeError',   message: 'waterline.hooks.find(...).map is not a function',   stack: 'TypeError: waterline.hooks.find(...).map is not a function\n    at Hook.publish (/home/jenkins/workspace/on-http/build/node_modules/on-core/lib/common/hook.js:33:10)\n    at EventsProtocol.publishExternalEvent (/home/jenkins/workspace/on-http/build/node_modules/on-core/lib/protocol/events.js:311:18)\n    at EventsProtocol.publishNodeEvent (/home/jenkins/workspace/on-http/build/node_modules/on-core/lib/protocol/events.js:368:21)\n    at /home/jenkins/workspace/on-http/build/lib/services/profiles-api-service.js:9:9230\n    at Object.tapHandler (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/finally.js:64:23)\n    at bound (domain.js:287:14)\n    at Object.runBound (domain.js:300:12)\n    at Object.tryCatcher (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)\n    at Promise._settlePromiseFromHandler (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/promise.js:510:31)\n    at Promise._settlePromiseAt (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/promise.js:584:18)\n    at Async._drainQueue (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/async.js:128:12)\n    at Async._drainQueues (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)\n    at Immediate.Async.drainQueues [as _onImmediate] (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)\n    at processImmediate [as _immediateCallback] (timers.js:396:17)',   context: {} } Error: expected 200 "OK", got 500 "Internal Server Error"     at Test._assertStatus (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:232:12)     at Test._assertFunction (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:247:11)     at Test.assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:148:18)     at assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:127:12)     at /home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:124:5     at Test.Request.callback (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:703:3)     at IncomingMessage.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)     at emitNone (events.js:72:20)     at IncomingMessage.emit (events.js:166:7)     at endReadableNT (_stream_readable.js:923:12)     at nextTickCallbackWith2Args (node.js:458:9)     at process._tickDomainCallback (node.js:413:17)
Stack Trace: Error: expected 200 "OK", got 500 "Internal Server Error"
at Test._assertStatus (node_modules/supertest/lib/test.js:232:12)
at Test._assertFunction (node_modules/supertest/lib/test.js:247:11)
at Test.assert (node_modules/supertest/lib/test.js:148:18)
at assert (node_modules/supertest/lib/test.js:127:12)
at node_modules/supertest/lib/test.js:124:5
at Test.Request.callback (node_modules/supertest/node_modules/superagent/lib/node/index.js:703:3)
at IncomingMessage.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)
at endReadableNT (_stream_readable.js:923:12)
Test Name: Http.Api.Profiles GET /profiles/switch/:vendor should throw a 400 on a request from an unknown switch vendor
Error Details: expected 400 "Bad Request", got 500 "Internal Server Error" Response body: { name: 'TypeError',   message: 'waterline.hooks.find(...).map is not a function',   stack: 'TypeError: waterline.hooks.find(...).map is not a function\n    at Hook.publish (/home/jenkins/workspace/on-http/build/node_modules/on-core/lib/common/hook.js:33:10)\n    at EventsProtocol.publishExternalEvent (/home/jenkins/workspace/on-http/build/node_modules/on-core/lib/protocol/events.js:311:18)\n    at EventsProtocol.publishNodeEvent (/home/jenkins/workspace/on-http/build/node_modules/on-core/lib/protocol/events.js:368:21)\n    at /home/jenkins/workspace/on-http/build/lib/services/profiles-api-service.js:9:9230\n    at Object.tapHandler (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/finally.js:64:23)\n    at bound (domain.js:287:14)\n    at Object.runBound (domain.js:300:12)\n    at Object.tryCatcher (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/util.js:26:23)\n    at Promise._settlePromiseFromHandler (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/promise.js:510:31)\n    at Promise._settlePromiseAt (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/promise.js:584:18)\n    at Async._drainQueue (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/async.js:128:12)\n    at Async._drainQueues (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/async.js:133:10)\n    at Immediate.Async.drainQueues [as _onImmediate] (/home/jenkins/workspace/on-http/build/node_modules/on-core/node_modules/bluebird/js/main/async.js:15:14)\n    at processImmediate [as _immediateCallback] (timers.js:396:17)',   context: {} } Error: expected 400 "Bad Request", got 500 "Internal Server Error"     at Test._assertStatus (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:232:12)     at Test._assertFunction (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:247:11)     at Test.assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:148:18)     at assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:127:12)     at /home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:124:5     at Test.Request.callback (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:703:3)     at IncomingMessage.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)     at emitNone (events.js:72:20)     at IncomingMessage.emit (events.js:166:7)     at endReadableNT (_stream_readable.js:923:12)     at nextTickCallbackWith2Args (node.js:458:9)     at process._tickDomainCallback (node.js:413:17)
Stack Trace: Error: expected 400 "Bad Request", got 500 "Internal Server Error"
at Test._assertStatus (node_modules/supertest/lib/test.js:232:12)
at Test._assertFunction (node_modules/supertest/lib/test.js:247:11)
at Test.assert (node_modules/supertest/lib/test.js:148:18)
at assert (node_modules/supertest/lib/test.js:127:12)
at node_modules/supertest/lib/test.js:124:5
at Test.Request.callback (node_modules/supertest/node_modules/superagent/lib/node/index.js:703:3)
at IncomingMessage.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)
at endReadableNT (_stream_readable.js:923:12)

BUILD unit-tests  #11542  Error Logs  ▼Test Name: UcsTool "before all" hook
Error Details: Cannot find module '/home/jenkins/workspace/on-tasks/build/lib/utils/job-utils/http-tool.js'
Stack Trace: Error: Cannot find module '/home/jenkins/workspace/on-tasks/build/lib/utils/job-utils/http-tool.js'
    at require (internal/module.js:12:17)
    at Object.global.helper.require (node_modules/on-core/spec/helper.js:84:16)
    at Context.<anonymous> (spec/lib/utils/job-utils/ucs-tool-spec.js:18:20)
Test Name: Ucs Discovery Job "before all" hook
Error Details: Cannot find module '/home/jenkins/workspace/on-tasks/build/lib/utils/job-utils/http-tool.js'
Stack Trace: Error: Cannot find module '/home/jenkins/workspace/on-tasks/build/lib/utils/job-utils/http-tool.js'
at require (internal/module.js:12:17)
at Object.global.helper.require (node_modules/on-core/spec/helper.js:84:16)
at Context.<anonymous> (spec/lib/jobs/ucs-discovery-spec.js:47:20)

BUILD on-multi #70 : FAILURE

** BUILD build-config-setup  #1493: SUCCESS
** BUILD on-core  #1073: UNSTABLE

** BUILD build-config-setup  #1494: SUCCESS

** BUILD unit-tests  #11545: SUCCESS

** BUILD on-taskgraph #2047: SUCCESS

** BUILD build-config-setup  #1495: SUCCESS
** BUILD unit-tests  #11546: SUCCESS

** BUILD on-http #3225: SUCCESS

** BUILD build-config-setup  #1496: SUCCESS
** BUILD unit-tests  #11547: SUCCESS

** BUILD on-dhcp-proxy #1127: SUCCESS

** BUILD build-config-setup  #1497: SUCCESS
** BUILD unit-tests  #11548: SUCCESS

** BUILD on-tasks #1973: UNSTABLE

** BUILD build-config-setup  #1498: SUCCESS
** BUILD unit-tests  #11549: UNSTABLE

** BUILD on-tftp #936: SUCCESS

** BUILD build-config-setup  #1499: SUCCESS
** BUILD unit-tests  #11550: SUCCESS

** BUILD on-syslog #837: SUCCESS

** BUILD build-config-setup  #1500: SUCCESS
** BUILD unit-tests  #11551: SUCCESS

BUILD unit-tests  #11549  Error Logs  ▼Test Name: UcsTool "before all" hook
Error Details: Cannot find module '/home/jenkins/workspace/on-tasks/build/lib/utils/job-utils/http-tool.js'
Stack Trace: Error: Cannot find module '/home/jenkins/workspace/on-tasks/build/lib/utils/job-utils/http-tool.js'
    at require (internal/module.js:12:17)
    at Object.global.helper.require (node_modules/on-core/spec/helper.js:84:16)
    at Context.<anonymous> (spec/lib/utils/job-utils/ucs-tool-spec.js:18:20)
Test Name: Ucs Discovery Job "before all" hook
Error Details: Cannot find module '/home/jenkins/workspace/on-tasks/build/lib/utils/job-utils/http-tool.js'
Stack Trace: Error: Cannot find module '/home/jenkins/workspace/on-tasks/build/lib/utils/job-utils/http-tool.js'
at require (internal/module.js:12:17)
at Object.global.helper.require (node_modules/on-core/spec/helper.js:84:16)
at Context.<anonymous> (spec/lib/jobs/ucs-discovery-spec.js:47:20)

test this please

BUILD on-multi #71 : FAILURE

** BUILD build-config-setup  #1501: SUCCESS
** BUILD on-core  #1074: UNSTABLE

** BUILD build-config-setup  #1502: SUCCESS

** BUILD unit-tests  #11552: SUCCESS

** BUILD on-taskgraph #2048: SUCCESS

** BUILD build-config-setup  #1503: SUCCESS
** BUILD unit-tests  #11553: SUCCESS

** BUILD on-http #3226: SUCCESS

** BUILD build-config-setup  #1504: SUCCESS
** BUILD unit-tests  #11554: SUCCESS

** BUILD on-dhcp-proxy #1128: SUCCESS

** BUILD build-config-setup  #1505: SUCCESS
** BUILD unit-tests  #11555: SUCCESS

** BUILD on-tasks #1974: UNSTABLE

** BUILD build-config-setup  #1506: SUCCESS
** BUILD unit-tests  #11556: UNSTABLE

** BUILD on-tftp #937: SUCCESS

** BUILD build-config-setup  #1507: SUCCESS
** BUILD unit-tests  #11557: SUCCESS

** BUILD on-syslog #838: SUCCESS

** BUILD build-config-setup  #1508: SUCCESS
** BUILD unit-tests  #11558: SUCCESS

BUILD unit-tests  #11556  Error Logs  ▼Test Name: UcsTool "before all" hook
Error Details: Cannot find module '/home/jenkins/workspace/on-tasks/build/lib/utils/job-utils/http-tool.js'
Stack Trace: Error: Cannot find module '/home/jenkins/workspace/on-tasks/build/lib/utils/job-utils/http-tool.js'
    at require (internal/module.js:12:17)
    at Object.global.helper.require (node_modules/on-core/spec/helper.js:84:16)
    at Context.<anonymous> (spec/lib/utils/job-utils/ucs-tool-spec.js:18:20)
Test Name: Ucs Discovery Job "before all" hook
Error Details: Cannot find module '/home/jenkins/workspace/on-tasks/build/lib/utils/job-utils/http-tool.js'
Stack Trace: Error: Cannot find module '/home/jenkins/workspace/on-tasks/build/lib/utils/job-utils/http-tool.js'
at require (internal/module.js:12:17)
at Object.global.helper.require (node_modules/on-core/spec/helper.js:84:16)
at Context.<anonymous> (spec/lib/jobs/ucs-discovery-spec.js:47:20)


Kernel local use-case fails due to 'network is unreachable'

Forwarder vpp deployment
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: forwarder-vpp
  labels:
    app: forwarder-vpp
spec:
  selector:
    matchLabels:
      app: forwarder-vpp
  template:
    metadata:
      labels:
        app: forwarder-vpp
    spec:
      containers:
        - image: networkservicemesh/cmd-vpp-forwarder:latest
          imagePullPolicy: IfNotPresent
          name: forwarder-vpp
          securityContext:
            privileged: true
          env:
            - name: SPIFFE_ENDPOINT_SOCKET
              value: unix:///run/spire/sockets/agent.sock
            - name: NSM_TUNNEL_IP
              valueFrom:
                fieldRef:
                  fieldPath: status.podIP
            - name: NSM_CONNECT_TO
              value: unix:///var/lib/networkservicemesh/nsm.io.sock
            - name: NSM_NAME
              valueFrom:
                fieldRef:
                  fieldPath: metadata.name
          volumeMounts:
            - name: spire-agent-socket
              mountPath: /run/spire/sockets
              readOnly: true
            - name: nsm-socket
              mountPath: /var/lib/networkservicemesh
      volumes:
        - name: spire-agent-socket
          hostPath:
            path: /run/spire/sockets
            type: Directory
        - name: nsm-socket
          hostPath:
            path: /var/lib/networkservicemesh
            type: DirectoryOrCreate

Steps to reproduce:

Use deployment that described above

Follow these steps: https://github.com/networkservicemesh/deployments-k8s/tree/main/examples/LocalConnection

Logs
logs.txt

@edwarnicke Currently looking into this issue. Do you have any idea about this?

@edwarnicke Currently looking into this issue. Do you have any idea about this?

Do you see the expected routes in the NSC Pod?

Do you see the expected routes in the NSC Pod?

I'm getting an ImagePullBackOff trying to get networkservicemesh/cmd-vpp-forwarder:latest
Events:
  Type     Reason     Age                From                         Message
  ----     ------     ----               ----                         -------
  Normal   Scheduled  77s                default-scheduler            Successfully assigned nsm-system/forwarder-vpp-289rj to kind-control-plane
  Normal   Pulling    39s (x3 over 77s)  kubelet, kind-control-plane  Pulling image "networkservicemesh/cmd-vpp-forwarder:latest"
  Warning  Failed     38s (x3 over 76s)  kubelet, kind-control-plane  Failed to pull image "networkservicemesh/cmd-vpp-forwarder:latest": rpc error: code = Unknown desc = failed to resolve image "docker.io/networkservicemesh/cmd-vpp-forwarder:latest": no available registry endpoint: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
  Warning  Failed     38s (x3 over 76s)  kubelet, kind-control-plane  Error: ErrImagePull
  Normal   BackOff    12s (x4 over 75s)  kubelet, kind-control-plane  Back-off pulling image "networkservicemesh/cmd-vpp-forwarder:latest"
  Warning  Failed     12s (x4 over 75s)  kubelet, kind-control-plane  Error: ImagePullBackOff

I'm getting an ImagePullBackOff trying to get networkservicemesh/cmd-vpp-forwarder:latest
Events:
  Type     Reason     Age                From                         Message
  ----     ------     ----               ----                         -------
  Normal   Scheduled  77s                default-scheduler            Successfully assigned nsm-system/forwarder-vpp-289rj to kind-control-plane
  Normal   Pulling    39s (x3 over 77s)  kubelet, kind-control-plane  Pulling image "networkservicemesh/cmd-vpp-forwarder:latest"
  Warning  Failed     38s (x3 over 76s)  kubelet, kind-control-plane  Failed to pull image "networkservicemesh/cmd-vpp-forwarder:latest": rpc error: code = Unknown desc = failed to resolve image "docker.io/networkservicemesh/cmd-vpp-forwarder:latest": no available registry endpoint: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed
  Warning  Failed     38s (x3 over 76s)  kubelet, kind-control-plane  Error: ErrImagePull
  Normal   BackOff    12s (x4 over 75s)  kubelet, kind-control-plane  Back-off pulling image "networkservicemesh/cmd-vpp-forwarder:latest"
  Warning  Failed     12s (x4 over 75s)  kubelet, kind-control-plane  Error: ImagePullBackOff

Do you see the expected routes in the NSC Pod?

I also thought about this, currently looking into https://github.com/networkservicemesh/cmd-nse-icmp-responder, looks like routes are missed there.

I'm getting an ImagePullBackOff trying to get networkservicemesh/cmd-vpp-forwarder:latest

I built it manually with the changes from https://github.com/networkservicemesh/cmd-forwarder-vpp/pull/33

Do you see the expected routes in the NSC Pod?

I also thought about this, currently looking into https://github.com/networkservicemesh/cmd-nse-icmp-responder, looks like routes are missed there.

I'm getting an ImagePullBackOff trying to get networkservicemesh/cmd-vpp-forwarder:latest

I built it manually with the changes from https://github.com/networkservicemesh/cmd-forwarder-vpp/pull/33

I think this has been resolved by https://github.com/networkservicemesh/cmd-forwarder-vpp/pull/31 carrying the fix https://github.com/networkservicemesh/sdk-vpp/pull/62

I think this has been resolved by https://github.com/networkservicemesh/cmd-forwarder-vpp/pull/31 carrying the fix https://github.com/networkservicemesh/sdk-vpp/pull/62

Fixed by #31
@edwarnicke Thanks!

Fixed by #31
@edwarnicke Thanks!


MANCHESTER CLASS_NW5 - ANVAR AZIZI - Full-Stack-Project-Assessment

Hello there @rebwar1,
Thankyou for your submission - at the moment, you've got 1085 files changed in this diff. Please could you remove your node_modules from this PR so we can review your work.


Adds score attacks.

The attack needs known keyword-trapdoor pairs.
The implementation uses known_query_size of the observed queries.
Therefore, the recovery rate will include the known keyword-trapdoor pairs.

The results of the original paper: "A Highly Accurate Query-Recovery Attack against Searchable Encryption using Non-Indexed Documents" by Damie et al. (2021) can be reproduced with this implementation of the refined score attack.
Implemented without clustering.


docs(workshop): add re-establish command

Fixes #
Description
Adding a re-establish command for getting the env vars back for MSI, and cluster creation
How was this change tested?
Testing in cloud shell
*
Does this change impact docs?

[x] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[ ] No

Release Note

NONE

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.005%) to 94.234%

Totals

Change from base Build<PHONE_NUMBER>4:
0.005%

Covered Lines:
37149

Relevant Lines:
39422

💛  - Coveralls


Context data not inherited by resource

Per the docs here: https://docs.datadoghq.com/real_user_monitoring/browser/monitoring_resource_performance/

RUM Resources inherit from all the context related to the active RUM View at the time of collection.

However maybe that's only applicable on web because we've found that our resource events inherit the View ID and name, but not custom context we added to the view and we aren't able to filter by custom view context data.
Is this a known limitation with the react-native-sdk specifically (on 1.0.0-rc5) or perhaps it's supported in a newer version? Tried upgrading but blocked by another issue: https://github.com/DataDog/dd-sdk-reactnative/issues/512
Thanks for your time!

Hi @danReynolds, thanks for reaching out!
So far we cannot reproduce the issue on the latest version. Could you specify which part of the context data you're missing specifically to help us troubleshoot?
Thanks a lot!

Thanks for the quick reply @louiszawadzki ! I'm passing extra context to the view like this:
DdRum.startView(
     'view_id',
     'view_name',
    { customField },
    Date.now()
);

but then when I look at the resource reports for this view, they don't have the customField context value on them. This is on 1.0.0-rc5 so maybe it works on latest, need to get through https://github.com/DataDog/dd-sdk-reactnative/issues/512 to try that

Hi @danReynolds, thanks a lot for clarifying!
Indeed, passing some context to a RUM View when creating it will not forward this context to children event like RUM Resources. It will only be attached to the RUM View.
If you want to have data attached to all your RUM events, use DdSdkReactNative.setAttributes.
The documentation you referred to is the documentation for our Browser SDK, which does not have a way to specify attributes for a RUM View, only global attributes (similarly to DdSdkReactNative.setAttributes), which I understand can be confusing.
If you want to find a way to filter your RUM Resources depending on the views, I encourage you to reach out to our support team which will be able to assist you on how to use the Datadog platform for your specific need.
I'll close this issue and let the other one opened until we solve it. Feel free to reopen it if I missed something :)


Use with font-face Compass mixin and it's *.eot?iefix

In a Rails 3.1 project am trying to use a Compass font-face mixin, which contains the inclusion of
*.eot?iefix
When I try to run assets:precompile the task fails saying something like: webfont.eot?iefix isn't precompiled, which probably means that Sprockets and Compass do not integrate correctly at this point of weird naming like ?iefix
Is it possible to fix this somehow?
Thanks a lot in advance!

Sorry, I don't know.
I think the maintainer of sass might have a better idea.

Ok, I've got, thanks!


implicit await in yield and return

Looking at the specification for arguments of yield and return implementation needs to add another await.
Regenerator does this, babel doesn't do this and returns promise if it is indeed promise passed to yield/return, but it doesn't sound right according to the spec.
What are the reasons behind this in the spec? It looks like an obstacle for me. What if I want to return a set of Promises to run it after in, say, Promise.all?
Also may be confusing, as everywhere the async position in expressions marked explicitly and only in these two places it is implicit.

This has been discussed in the past and was changed to be equivalent to yield await due to complex cases.
If you're asking how with yield acting as yield await can you run things concurrently? Well it's basically the same way as before:
// This presumes you want the downloads to be yield-ed in the same
// order as `urls`, the unordered one is similar but
// races the `active` array instead of waiting for the first
async function* concurrentDownload(urls, maxConcurrency=10) {
    const active = []
    for (const url of urls) {
        // Add download to list of concurrently active
        active.push(downloadOne(url))
        // But if we've hit max concurrency we'll wait for the first
        // one to complete before we continue
        if (active.length === maxConcurrency) {
            yield active.shift()
        }
    }
    // Yield the ones left in the queue
    for (const download of active) {
        yield download
    }
}