Add default shortNames to certificates CRD

Defaults to [cert, certs] and is configurable with certificateCRDShortNames parameter.
What this PR does / why we need it:
Simplifies manual certificate management with kubectl.
Fixes #311

Special notes for your reviewer:
Instead of a boolean switch do/dont include the shortNames, the value defines the aliases. This may be handy if anybody prefers [crt, crts] instead.
I'm not too keen on the certificateCRDShortNames variable name. It might be better to use Resource instead of CRD to be consistent with the createCustomResource var.
Other CRDs are probably ok without an alias, but other people workflows may differ. Should these also be configurable? In that case, the variables could be shortNames: {certificates: [], …}.
Release note:

Add Certificate CRD shortnames `cert` and `certs`. This is configurable in the Helm Chart with `certificateResourceShortNames`.

/ok-to-test

@Mikulas instead of manually editing the deployment files in docs/deploy, you should run ./hack/update-deploy-gen.sh in order to regenerate them 😄

@munnerz oh thanks 😅 makes sense

The tests pass, but please see the notes https://github.com/jetstack/cert-manager/pull/312#user-content-review-notes.
/assign @munnerz

Sorry for the delay - I like your suggestion: certificateResourceShortNames :smile:

Thanks!
/approve
/lgtm

If you could update the release note and remove WIP from the title, this should then be automatically merged :smile:

/retest

/retest

@munnerz Thanks :) Will the Submit Queue automatically squash into a single commit? I've kept it separated as fixups for review.

Nope it won't - feel free to squash now and I'll re-lgtm
On Wed, 21 Feb 2018 at 19:49, Mikuláš Dítě<EMAIL_ADDRESS>wrote:

@munnerz https://github.com/munnerz Thanks :) Will the Submit Queue
automatically squash into a single commit? I've kept it separated as fixups
for review.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jetstack/cert-manager/pull/312#issuecomment-367448718,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMbP9uqydDeEfO6ie7m7p1f1C64eACHks5tXHNDgaJpZM4SCTUh
.

/lgtm

/retest
On Wed, 21 Feb 2018 at 20:35, jetstack-bot<EMAIL_ADDRESS>wrote:

@Mikulas https://github.com/mikulas: The following test failed, say
/retest to rerun them all:
Test name Commit Details Rerun command
cert-manager-e2e-v1-8 d884404
https://github.com/jetstack/cert-manager/commit/d8844041594eb3370cee40d41ffc2131cfcceb93
link
https://jetstack-build-infra.appspot.com/build/jetstack-logs/pr-logs/pull/jetstack_cert-manager/312/cert-manager-e2e-v1-8/166/ /test
e2e v1.8
Full PR test history
https://jetstack-build-infra.appspot.com/pr/jetstack_cert-manager/312. Your
PR dashboard https://jetstack-build-infra.appspot.com/pr/Mikulas.
Please help us cut down on flakes by linking to
https://github.com/kubernetes/community/blob/master/contributors/devel/flaky-tests.md#filing-issues-for-flaky-tests
an open issue
https://github.com/jetstack/cert-manager/issues?q=is:issue+is:open when
you hit one in your PR.
Instructions for interacting with me using PR comments are available here
https://git.k8s.io/community/contributors/devel/pull-requests.md. If
you have questions or suggestions related to my behavior, please file an
issue against the kubernetes/test-infra
https://github.com/kubernetes/test-infra/issues/new?title=Prow issue:
repository. I understand the commands that are listed here
https://go.k8s.io/bot-commands.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jetstack/cert-manager/pull/312#issuecomment-367463164,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMbPxI4ZrkkMHouhU6yuMapRYejB_jxks5tXH4cgaJpZM4SCTUh
.

Awesome, thank you :)


Docker Host performance issues after starting to use PowerShell7?

I'm not sure that this is related to BcContainerHelper, but I put it out here if someone else experience similar issues and we can figure out the cause together.
Describe the issue
Lately we've started to experience performance issues with our pipeline build server.
Pipelines are getting slower and slower, to the point that my colleagues start complaining and we restart the server. After restart, the server is fast as ever, but then after a few days to a week it starts to get slow again.
It got even worse the last week, which make me think that this is related to the BC24 containers, since they are running much more frequently after the wave.
We started to see this behavior a couple of months ago, and I believe that it started after began to run pipelines on BC24.
In conjunction with that, we also installed .NET 8 and started to use PowerShell 7 in the pipelines. So, they might also be part of the cause.
Symptoms
The symptoms we see is that all PowerShell tasks in the pipelines "idles" some time before generating the PowerShell script.
In below example there is almost 4 minutes from that the task started until the script is started. After restart there is no delay there, and after a week there could be up to 10 minutes delay. And when having 20 different PowerShell tasks in the pipeline, this adds up to a lot of waiting...
2024-04-10T11:44:36.9557848Z ##[section]Starting: Create Build Container
2024-04-10T11:44:37.1721251Z ==============================================================================
2024-04-10T11:44:37.1721401Z Task         : PowerShell
2024-04-10T11:44:37.1721469Z Description  : Run a PowerShell script on Linux, macOS, or Windows
2024-04-10T11:44:37.1721588Z Version      : 2.237.5
2024-04-10T11:44:37.1721654Z Author       : Microsoft Corporation
2024-04-10T11:44:37.1721733Z Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell
2024-04-10T11:44:37.1721862Z ==============================================================================
2024-04-10T11:48:12.3345494Z Generating script.
2024-04-10T11:48:12.3680887Z ========================== Starting Command Output ===========================
2024-04-10T11:48:12.3930122Z ##[command]"C:\Program Files\PowerShell\7\pwsh.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'C:\Agent_AS015_03\_work\_temp\278905e0-b287-45ae-aba4-2ab7780ddf78.ps1'"
2024-04-10T11:48:13.1932853Z BcContainerHelper version 6.0.11

When this happened today, I noticed that the WmiPrvSE.exe process was heavy on the CPU, and like 50+ WMIC.exe processes running (started by the Build Agent). Don't know if it is related to the behavior we've seen lately, but might be relevant.

I see that BcContainerHelper uses Get-CIMInstance to get free physical memory, could that cause the WMIC processes above?
Additional context

Server is running on Windows Server 2022
12 DevOps agents are running on the server
When all agents are running, it usually uses under 50% of CPU and RAM.

Anyone else experience similar performance degradation lately?
Any suggestions on how to troubleshoot?

Are containers running Process or HyperV isolation?
Are  you running all BC related cmdlets inside containers or on the agent?
Maybe related: https://www.yammer.com/dynamicsnavdev/threads/2746068688338944

I don't think Get-CIMInstance causes these.

I use Get-CIMInstance to get a CIM instance and extract values from that (OS Version number, memory and more)

Are containers running Process or HyperV isolation?

Using process isolation

Are you running all BC related cmdlets inside containers or on the agent?

After the issues with the PS5 to PS7 bridge (https://www.yammer.com/dynamicsnavdev/threads/2687029664907264), I refactored our pipelines to not load the BC cmdlets on the host anymore.
So, all BC related cmdlets should be run inside the containers (via BcContainerHelper)

Maybe related: https://www.yammer.com/dynamicsnavdev/threads/2746068688338944

Not sure about this, when our pipelines start to slowdown (or starts to idle in all PowerShell tasks), there are still 50+ GB RAM free on the host.

I don't think Get-CIMInstance causes these.  I use Get-CIMInstance to get a CIM instance and extract values from that (OS Version number, memory and more)

Yes, tried that on my local computer as well and did not see any WMIC processes being left running.
But wanted to add the information anyway, if it might be related in some strange way....

In order to isolate processes 100%, could you try hyperv?
Using process isolation, you will still see processes from the container on the host list of processes.

Good thinking, I'll try that!
I think most pipeline containers runs with 8GB RAM, so it should hopefully work. Let's see 😃

Update: Installed Hyper-V and changed all pipelines to use that instead of process isolation last night. Performance in containers are pretty much the same as before.
One change of behavior that I see: WMIC processes are still created and are running 50+ i parallell. But now they are all terminated now and then...
When all those are running, I see a CPU spike in WmiPrvSE.exe, but that might be caused by the fact that WMIC is querying for available memory in a lot of processes at the same time...
I'm starting to believe that all this is related to the PowerShell v2 task, combined with pwsh: true that we started with when switching to PowerShell7. I also think that we updated our Azure Pipeline Agents at the same time. That version (v3.236.1) is still the latest version.
So right now we just need to wait and see if our old behavior with the host getting slow after a few days still exist.
If all fine in a week or two, we're just happy.
If not, we will start to test other versions of  the Azure Pipeline Agents to see if behavior changes.
I'll close this issue for now, will get back here if things starts to point against BCCH 😉

FYI
I found out what is causing the WMIC processes: https://github.com/microsoft/azure-pipelines-agent/blob/b34a9c376bf689d70092981eaa40d3e19327b11a/src/Agent.Worker/ResourceMetricsManager.cs#L255
I'll try to ask in that repo why it is starting that many processes, if it's a bug or by design.

Thanks for the info:-)


Can work on lenovo ideapad 5 15IIL05 ?

just askin if it can work on this model.
Specs:
Processor
1x 10th Generation Intel® Core™ i5-1035G1 Processor(Core i5-1035G1)
Memory
1x 8GB DDR4 3200
Operating System
Windows 10 Home 64(HB:Hebrew,EN:English)
Hard Drive
1x 256GB PCIe NVMe
1x 1TB HDD 5400rpm
Wireless Network
1x Intel® Wi-Fi 6 AX201 2x2 AX; Bluetooth® 5.0 or above
Ports
1x HDMI 1.4b; SD Card reader; DC-in Jack (Round); Combo of 3.5mm Stereo Headphone Output; 1 Type C (USB 3.2 Gen 2 + DP 1.2 + PD 3.0); 2 USB 3.1 (Gen1)
Camera
1x 720P HD with Array Microphone & Privacy Shutter
Graphics
1x NVIDIA GeForce MX330 2GB
Monitor
15.6 FHD
Included Warranty
1CourierCarryin

just askin if it can work on this model.

Yes, just give me 1-2 weeks so i'll end classes, and after that I hope to update this

HDMI work?

just askin if it can work on this model.

Yes you should be able now with 0.7.8 on Big Sur for now


startafter and continuationtoken are mutually exclusive

Signed-off-by: Albin Antony<EMAIL_ADDRESS>

@zhangsw @cbodley @alimaredia Please review

I think Startafter and ContinuationToken can be specified at same time. If ContinuationToken is provided, Startafter has no effects. I think we need to assure the returned Startafter and ContinuationToken are the same as we specify in the request.

I think Startafter and ContinuationToken can be specified at same time. If ContinuationToken is provided, Startafter has no effects. I think we need to assure the returned Startafter and ContinuationToken are the same as we specify in the request.

Agree


Parameter types of input params.yaml not preserved when using "Modify & Queue"

I am using PyTorch Lightning, whose trainer has a limit_num_batches argument. Based on the type of the argument, this parameter is either interpreted as absolute number of batches or a ratio of batches from the dataset. For example, 1.0 means 100% of the dataset, i.e., all batches, whereas 1 (literal int) means one single batch.
In my param.yaml file, I have a limit_num_batches entry which I load with dacite and type annotation Union[int, float]. The default value in the configuration file is limit_num_batches: 1.0.
Using the DVC VS Code extension to modify other parameters, it also passes this unchanged parameter on the command line, however, using -S limit_num_batches=1. This changes the type from floating point to integral!

To work around this, I could rewrite my code to:

Always expect limit_num_batches to be an int and using value -1 to indicate 100% (i.e., no longer be able to specify a ratio other than 0% (limit_num_batches: 0) and 100% (limit_num_batches: -1).
Change type of limit_num_batches to Union[int, str] and use limit_num_batches: X%, e.g., limit_num_batches: 20% to specify a ratio instead of values in [0, 1].
Given that 0 means both 0% and 0 num batches, and values in open interval (0, 1) must be serialized as string on the command-line with decimal point, it seems I would only need to introduce -1 as meaning 100% instead of 1.0.

Looks like this is the reason https://stackoverflow.com/questions/53005702/parse-float-with-decimals-to-json-in-javascript-also-for-1-as-1-00 ... Similar to the #2733 . Python + JS + JSON create a complete mess in handling basic things properly. We'll need to figure out something better.
Also, technically we can't probably even blame JS in this case? 1.0 is the same as 1. I would say that Lighting takes quite a strange way to determine things in this case also.

Unfortunately, I can't see how it can be solved at the moment :(. It looks like in JS (the lang extension is written in, since VS Code is also written in JS) it would be quite hard to preserve .0, JS has a single numeric type - number and rounds .0.

Yes, thanks for looking into it. Thought I'll leave it open if it's possible to preserve the decimal formatting of the input params.yaml file. The workarounds for dealing with how Lightning handles this described above work out fine actually. If chosen the third option, to simply use -1 as parameter value if I want to say limit_num_batches=1.0 and otherwise there is no ambiguity because limit_num_batches=0 and limit_num_batches>1 are clear, and 0 < limit_num_batches < 1 will always be formatted as 0.xxx. I think we can close the issue?

Thanks for the issue @aschuh-hf. As @shcheklein stated we won't be able to solve this due to some limitations of the language we are working with. Will close this now.
Please come back to us with any further feedback/issues that you have 🙏🏻.


Need to add channel permission type

Currently permission option and @slash.permission accept only User or Role type permissions, but channel-lock commands are also common even if you technically can call it in any channel.

Unfortunately, the permission option is just an abstraction of the discord permission system for interactions. The only options in it are user or role
https://discord.com/developers/docs/interactions/slash-commands#application-command-permissions-object-application-command-permission-type


Impossible to orbit the scene when drei's Html element is in the scene

given:
import { Html, KeyboardControls } from '@react-three/drei';
//...
      <Canvas shadows>

Let's Go!

<Physics timeStep="vary">
          <Suspense fallback={null}>
            <KeyboardControls map={keyboardMap}>
              <Ecctrl debug>
                <CharacterModel />
              </Ecctrl>
            </KeyboardControls>
            <Room04/>
          </Suspense>
        </Physics>
</Canvas>

you can not look around in the scene with mouse or pointer. How can we fix this? Any ideas?

Only the current domElement can interact with camera control. I think adding Html might create another dom element. 🤔
Alternatively, you could use pointerlock like in the example app.

When occlude is set to true, control is restored, but it brings another issue: the Html flickers, and its occlusion relationship is incorrect.

@chillbert In version 1.0.88, you can set camListenerTarget = "document". That should solve the problem.

@ErdongChen-Andrew thanks for the answer, setting camListenerTarget = "document"  worked for me I was using the html element to embed a youtube video and seems to work seamlessly


Enable subgraph layout

I would like to suggest spread to enable subgraph layout mentioned here by replacing nodes and edges definition with
  const nodes = options.eles.nodes();
  const edges = options.eles.edges();

thank you.

That sounds like a good idea.  If you’d like to propose a change like that, you’re welcome to create a pull request.

On May 27, 2020, at 4:16 PM, Michael Cheng<EMAIL_ADDRESS>wrote:
I would like to suggest spread to enable subgraph layout mentioned here https://js.cytoscape.org/#layouts by replacing nodes and edges definition https://github.com/cytoscape/cytoscape.js-spread/blob/master/src/layout.js#L41 with
const nodes = options.eles.nodes();
const edges = options.eles.edges();
thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/cytoscape/cytoscape.js-spread/issues/7, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHRO4677MW5YCA2T46FCX3RTVYIBANCNFSM4NMO55TA.


Add example CRDT types

This change explores how CRDT types fit into DOT.  It seems like the server/client networking and streams support can be neatly reused with CRDT types (at-least operation-based ones)..

Codecov Report

Merging #310 into master will decrease coverage by 0.31%.
The diff coverage is 94.54%.

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


[touch] Cell doubleclick does not work on iphone/ipad

On IPhone/IPad a doubleclick zooms in and does invoke the doubleclick callback.

By default mobile Safari does not support the javascript doubleclick event. It's interpreted by Safari as a "zoom".
var agent = navigator.userAgent.toLowerCase();
if(agent.indexOf('iphone') >= 0 || agent.indexOf('ipad') >= 0){
       // implement double-tap
} else{
       // implement double click
}

And you can also add viewport meta tag in your html file inside the head tag. It will prevent user to zoom in or out the page

the meta tag does not work. and i want a cell doubleclick, so i think it needs to be implemented in aggrid?

thanks, i've added this to my list for next time i do a pass on touch devices. i see what you mean, you can't enter edit mode.

tracked by AG-146
https://www.ag-grid.com/ag-grid-pipeline/

Don't suppose there's an estimated release date for this feature?

This issue doesn't appear in the pipeline anymore. Has it been dropped?

Released in v15.0

Double tap doesn't work on iPhone in version 19. Why is this closed as resolved?

Row double tap doesn't work on iPod in Safari, Please reopen this issue.

Row double tap was not working, so I switched to cell double tap. It had all of the event information I needed, but it would be great to fix the row double tap as well.


Docs erroneously say that odict.add() only has two mandatory parameters

Quoting from the Extension API docs (emphasis mine):

The add() method accepts three arguments:

key: A string. The key is used for later reference to the item.
value: The object instance stored in this item.
location: Optional. The items location in relation to other items.

But the source code for the method shows that all three arguments are required:
def add(self, key, value, location):
    """ Insert by key location. """

Either the "Optional" should be removed from the docs, or the parameter should be made optional.
I’d mildly prefer the latter, as I have some cases where the location really doesn’t matter, but it’s not a strong preference.

Not sure why the docs say "optional". It never has been and doesn't make sense to be. I'll update the docs. Thanks for the report.

Thanks! Can you publish the doc update? http://pythonhosted.org/Markdown/extensions/api.html#extendmarkdown still says "Optional."

The docs are updated on each release.

Hmm, looks like we didn't update the docs when we released 2.6.9. Opps.

Docs don't auto-deploy on release?  I figured they did, but I never really checked.

No, I never got that automated. The releases are so few and far between and it was never a problem to run make docs and then use the "edit" page on PyPI to upload the zip file. That is, until now. See #601 for the current state and my proposal to address it.

Have you settled on a theme? If you have (and when I have some time), I can probably set it up.

That is of course if you are ready to jump to Mkdocs.

The switch to MkDocs exists in the md3 branch at 6f87b32. That commit should "cherry-pick" and merge relatively easily. And I just finished and released the MkDocs-Nature theme to use with it (the md3 branch is currently using readthedocs). Whoever gets to it first...


Sub-commands for jsx

We can combine all related commands for jsx into sub-commands, maybe exposing internal tools too.
So instead of doing
jsx container-install
jsx container-kosmos
..etc
We can simply do
jsx container install
jsx openpublish generate

wont do not important now


NIFI-3669 Add SSL Support to CaptureChangeMySQL

Description of PR
NIFI-3669 Add SSL support to Binary Log Client in CaptureChangeMySQL processor.  Introduces new SSL Mode property defaulted to DISABLED with allowed values provided from the binary log client library.  Also introduces optional SSL Context Service property with custom validation to ensure that SSL Context Service is configured when SSL Mode is set to something other than DISABLED.  Includes unit tests to verify the presence of an SSLSocketFactory on the mocked binary log client and the creation of an SSLSocket with appropriate exception handling.
PR #3456 includes the same conceptual functionality, but it contains unnecessary work to initialize a new SSLContext, does not include any new unit tests, and contains merge conflicts.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[X] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[X] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[X] Has your PR been rebased against the latest commit within the target branch (typically main)?

[X] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[X] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[X] Have you written or updated unit tests to verify your changes?
[X] Have you verified that the full build is successful on JDK 8?
[X] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[X] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

The most recent CI build failed for Ubuntu JDK 11 EN and Windows JDK 1.8 due to an HTTP 503 when attempting to retrieve a dependency.  Other builds completed without errors.

Merged to main, thanks @exceptionfactory !


upgrade to MinVer 1.0.0 RC1

What issue does this PR address?
If even you don't end up using https://github.com/adamralph/minver/issues/212, it would be great to have at least one project outside those managed by me on the RC before I release MinVer 1.1.0 RTM.
Does this PR introduce a breaking change?
No.
Please check if the PR fulfills these requirements

[x] The commit follows our guidelines
[x] ~Unit Tests for the changes have been added (for bug fixes / features)~

Other information:
MinVer 1.1.0 also gets rid of these warnings (https://github.com/adamralph/minver/issues/209):

warning NU5105: The package version '2.4.1-alpha.0.18' uses SemVer 2.0.0 or components of SemVer 1.0.0 that are not supported on legacy clients. Change the package version to a SemVer 1.0.0 string. If the version contains a release label it must start with a letter. This message can be ignored if the package is not intended for older clients.

will give it a try...

Just did a build. Seems everything behaves as expected.

🎉 thanks


Bootstrap fails: Exception: NoMethodError: undefined method `empty?' for nil:NilClass

Description
I tried to bootstrap a node from Mac and getting this error.
With Chef Workstation on CentOS 7 it worked fine.
Chef Version
chef --version
Chef Workstation: 0.4.1
chef-run: 0.3.0
chef-client: 15.0.300
delivery-cli: 0.0.52 (9d07501a3b347cc687c902319d23dc32dd5fa621)
berks: 7.0.8
test-kitchen: 2.2.5
inspec: 4.3.2
Platform Version

Chef Server: CentOS 7
Node: CentOS 7
Workstation Mac OS 10.14.5
Replication Case

Install Chef Workstation on Mac OS and bootstrap a node.
Client Output

➜  .chef git:(master) ✗ knife bootstrap node.network.local --sudo --policy-group acceptance --policy-name base -N node-3 -VV
/opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:31: warning: already initialized constant Chef::Knife::Bootstrap::SUPPORTED_CONNECTION_PROTOCOLS
/opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:31: warning: previous definition of SUPPORTED_CONNECTION_PROTOCOLS was here
/opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:32: warning: already initialized constant Chef::Knife::Bootstrap::WINRM_AUTH_PROTOCOL_LIST
/opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:32: warning: previous definition of WINRM_AUTH_PROTOCOL_LIST was here
/opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:350: warning: already initialized constant Chef::Knife::Bootstrap::DEPRECATED_FLAGS
/opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:350: warning: previous definition of DEPRECATED_FLAGS was here
INFO: Using configuration from /Users/pRncs/git/lcr-policyfiles-managenodes/.chef/knife.rb
DEBUG: Checking if we need to accept Chef license to bootstrap node
DEBUG: Reading products and relationships...
DEBUG: Successfully read products and relationships
DEBUG: License acceptance required for chef version: 15
DEBUG: Searching for the following licenses: ["infra-client", "inspec"]
DEBUG: Found license chef_infra_client at /Users/pRncs/.chef/accepted_licenses/chef_infra_client
DEBUG: Found license inspec at /Users/pRncs/.chef/accepted_licenses/inspec
DEBUG: Missing licenses remaining: []
DEBUG: All licenses present
Node node-3 exists, overwrite it? (Y/N) Y
Client node-3 exists, overwrite it? (Y/N) Y
Creating new client for node-3
Creating new node for node-3
Connecting to node.network.local
DEBUG: [SSH] Using Agent keys as no password or key file have been specified
WARN: [SSH] PTY requested: stderr will be merged into stdout
DEBUG: [SSH] root@node.network.local<{:user_known_hosts_file=>"/dev/null", :port=>22, :compression=>false, :compression_level=>0, :keepalive=>true, :keepalive_interval=>60, :timeout=>60, :auth_methods=>["none", "publickey"], :keys_only=>nil, :keys=>[], :password=>"<hidden>", :forward_agent=>nil, :non_interactive=>true, :verify_host_key=>:always}> (cmd.exe /c ver)
DEBUG: [SSH] opening connection to root@node.network.local<{:user_known_hosts_file=>"/dev/null", :port=>22, :compression=>false, :compression_level=>0, :keepalive=>true, :keepalive_interval=>60, :timeout=>60, :auth_methods=>["none", "publickey"], :keys_only=>nil, :keys=>[], :password=>"<hidden>", :forward_agent=>nil, :non_interactive=>true, :verify_host_key=>:always}>
The authenticity of host 'node.network.local (<IP ADRESS>)' can't be established.
fingerprint is SHA256:<THE FINGERPRINT>

Are you sure you want to continue connecting
? (Y/N) Y
DEBUG: [SSH] Using Agent keys as no password or key file have been specified
WARN: [SSH] PTY requested: stderr will be merged into stdout
DEBUG: [SSH] root@node.network.local<{:user_known_hosts_file=>"/dev/null", :port=>22, :compression=>false, :compression_level=>0, :keepalive=>true, :keepalive_interval=>60, :timeout=>60, :auth_methods=>["none", "publickey"], :keys_only=>nil, :keys=>[], :password=>"<hidden>", :forward_agent=>nil, :non_interactive=>true, :verify_host_key=>:accept_new}> (cmd.exe /c ver)
DEBUG: [SSH] opening connection to root@node.network.local<{:user_known_hosts_file=>"/dev/null", :port=>22, :compression=>false, :compression_level=>0, :keepalive=>true, :keepalive_interval=>60, :timeout=>60, :auth_methods=>["none", "publickey"], :keys_only=>nil, :keys=>[], :password=>"<hidden>", :forward_agent=>nil, :non_interactive=>true, :verify_host_key=>:accept_new}>
DEBUG: [SSH] root@node.network.local<{:user_known_hosts_file=>"/dev/null", :port=>22, :compression=>false, :compression_level=>0, :keepalive=>true, :keepalive_interval=>60, :timeout=>60, :auth_methods=>["none", "publickey"], :keys_only=>nil, :keys=>[], :password=>"<hidden>", :forward_agent=>nil, :non_interactive=>true, :verify_host_key=>:accept_new}> (uname -s)
DEBUG: [SSH] root@node.network.local<{:user_known_hosts_file=>"/dev/null", :port=>22, :compression=>false, :compression_level=>0, :keepalive=>true, :keepalive_interval=>60, :timeout=>60, :auth_methods=>["none", "publickey"], :keys_only=>nil, :keys=>[], :password=>"<hidden>", :forward_agent=>nil, :non_interactive=>true, :verify_host_key=>:accept_new}> (uname -m)
DEBUG: [SSH] root@node.network.local<{:user_known_hosts_file=>"/dev/null", :port=>22, :compression=>false, :compression_level=>0, :keepalive=>true, :keepalive_interval=>60, :timeout=>60, :auth_methods=>["none", "publickey"], :keys_only=>nil, :keys=>[], :password=>"<hidden>", :forward_agent=>nil, :non_interactive=>true, :verify_host_key=>:accept_new}> (test -f /etc/debian_version && cat /etc/debian_version)
DEBUG: [SSH] root@node.network.local<{:user_known_hosts_file=>"/dev/null", :port=>22, :compression=>false, :compression_level=>0, :keepalive=>true, :keepalive_interval=>60, :timeout=>60, :auth_methods=>["none", "publickey"], :keys_only=>nil, :keys=>[], :password=>"<hidden>", :forward_agent=>nil, :non_interactive=>true, :verify_host_key=>:accept_new}> (test -f /etc/os-release && cat /etc/os-release)
Traceback (most recent call last):
	48: from /opt/chef-workstation/bin/knife:317:in `<main>'
	47: from /opt/chef-workstation/bin/knife:317:in `load'
	46: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/bin/knife:24:in `<top (required)>'
	45: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/application/knife.rb:162:in `run'
	44: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife.rb:221:in `run'
	43: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife.rb:473:in `run_with_pretty_exceptions'
	42: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/local_mode.rb:41:in `with_server_connectivity'
	41: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife.rb:474:in `block in run_with_pretty_exceptions'
	40: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:547:in `run'
	39: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:597:in `connect!'
	38: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:650:in `do_connect'
	37: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap/train_connector.rb:69:in `connect!'
	36: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap/train_connector.rb:56:in `connection'
	35: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh.rb:82:in `connection'
	34: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh.rb:238:in `create_new_connection'
	33: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh.rb:238:in `new'
	32: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh_connection.rb:53:in `initialize'
	31: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/extras/command_wrapper.rb:165:in `load'
	30: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/plugins/base_connection.rb:110:in `platform'
	29: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect.rb:9:in `scan'
	28: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:27:in `scan'
	27: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:27:in `each'
	26: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:33:in `block in scan'
	25: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `scan_children'
	24: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `each'
	23: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:46:in `block in scan_children'
	22: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:46:in `instance_eval'
	21: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/specifications/os.rb:29:in `block in load'
	20: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/helpers/os_windows.rb:7:in `detect_windows'
	19: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/plugins/base_connection.rb:122:in `run_command'
	18: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh_connection.rb:216:in `run_command_via_connection'
	17: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh_connection.rb:247:in `session'
	16: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh_connection.rb:178:in `establish_connection'
	15: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh.rb:246:in `start'
	14: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh.rb:246:in `new'
	13: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/session.rb:90:in `initialize'
	12: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/session.rb:223:in `wait'
	11: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/session.rb:223:in `loop'
	10: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/session.rb:225:in `block in wait'
	 9: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/session.rb:190:in `poll_message'
	 8: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/session.rb:190:in `loop'
	 7: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/session.rb:210:in `block in poll_message'
	 6: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/algorithms.rb:167:in `accept_kexinit'
	 5: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/algorithms.rb:228:in `proceed!'
	 4: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/algorithms.rb:406:in `exchange_keys'
	 3: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/kex/diffie_hellman_group1_sha1.rb:72:in `exchange_keys'
	 2: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/kex/diffie_hellman_group1_sha1.rb:188:in `verify_server_key'
	 1: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/verifiers/always.rb:21:in `verify'
/opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/verifiers/always.rb:50:in `process_cache_miss': fingerprint SHA256:<THE FINGERPRINT> is unknown for "node.network.local,<IP ADRESS>" (Net::SSH::HostKeyUnknown)
	31: from /opt/chef-workstation/bin/knife:317:in `<main>'
	30: from /opt/chef-workstation/bin/knife:317:in `load'
	29: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/bin/knife:24:in `<top (required)>'
	28: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/application/knife.rb:162:in `run'
	27: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife.rb:221:in `run'
	26: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife.rb:473:in `run_with_pretty_exceptions'
	25: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/local_mode.rb:41:in `with_server_connectivity'
	24: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife.rb:474:in `block in run_with_pretty_exceptions'
	23: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:547:in `run'
	22: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:597:in `connect!'
	21: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:650:in `do_connect'
	20: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap/train_connector.rb:69:in `connect!'
	19: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap/train_connector.rb:56:in `connection'
	18: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh.rb:82:in `connection'
	17: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh.rb:238:in `create_new_connection'
	16: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh.rb:238:in `new'
	15: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh_connection.rb:53:in `initialize'
	14: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/extras/command_wrapper.rb:165:in `load'
	13: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/plugins/base_connection.rb:110:in `platform'
	12: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect.rb:9:in `scan'
	11: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:27:in `scan'
	10: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:27:in `each'
	 9: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:33:in `block in scan'
	 8: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `scan_children'
	 7: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `each'
	 6: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:46:in `block in scan_children'
	 5: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:46:in `instance_eval'
	 4: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/specifications/os.rb:29:in `block in load'
	 3: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/helpers/os_windows.rb:7:in `detect_windows'
	 2: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/plugins/base_connection.rb:122:in `run_command'
	 1: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh_connection.rb:212:in `run_command_via_connection'
/opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh_connection.rb:224:in `rescue in run_command_via_connection': SSH command failed (fingerprint SHA256:<THE FINGERPRINT> is unknown for "node.network.local,<IP ADRESS>") (Train::Transports::SSHFailed)
	41: from /opt/chef-workstation/bin/knife:317:in `<main>'
	40: from /opt/chef-workstation/bin/knife:317:in `load'
	39: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/bin/knife:24:in `<top (required)>'
	38: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/application/knife.rb:162:in `run'
	37: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife.rb:221:in `run'
	36: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife.rb:473:in `run_with_pretty_exceptions'
	35: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/local_mode.rb:41:in `with_server_connectivity'
	34: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife.rb:474:in `block in run_with_pretty_exceptions'
	33: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:547:in `run'
	32: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:594:in `connect!'
	31: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:618:in `rescue in connect!'
	30: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:650:in `do_connect'
	29: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap/train_connector.rb:69:in `connect!'
	28: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap/train_connector.rb:56:in `connection'
	27: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh.rb:82:in `connection'
	26: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh.rb:238:in `create_new_connection'
	25: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh.rb:238:in `new'
	24: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh_connection.rb:53:in `initialize'
	23: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/extras/command_wrapper.rb:165:in `load'
	22: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/plugins/base_connection.rb:110:in `platform'
	21: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect.rb:9:in `scan'
	20: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:27:in `scan'
	19: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:27:in `each'
	18: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:33:in `block in scan'
	17: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `scan_children'
	16: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `each'
	15: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:51:in `block in scan_children'
	14: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:60:in `scan_family_children'
	13: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `scan_children'
	12: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `each'
	11: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:51:in `block in scan_children'
	10: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:60:in `scan_family_children'
	 9: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `scan_children'
	 8: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `each'
	 7: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:46:in `block in scan_children'
	 6: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:46:in `instance_eval'
	 5: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/specifications/os.rb:103:in `block in load'
	 4: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/helpers/os_linux.rb:26:in `linux_os_release'
	 3: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/helpers/os_linux.rb:38:in `parse_os_release_info'
	 2: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/helpers/os_linux.rb:38:in `each_with_object'
	 1: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/helpers/os_linux.rb:38:in `each'
/opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/helpers/os_linux.rb:43:in `block in parse_os_release_info': undefined method `empty?' for nil:NilClass (NoMethodError)

I reinstalled my Mac which solved the Problem.

got the same, same setup except High Sierra
$ knife bootstrap -N client_512_1 <IP_ADDRESS> --ssh-user root -P1
WARNING: You provided --ssh-user. This flag is deprecated. Please use '--connection-user USERNAME' instead.
Node client_512_1 exists, overwrite it? (Y/N) Y
Client client_512_1 exists, overwrite it? (Y/N) Y
Creating new client for client_512_1
Creating new node for client_512_1
Connecting to <IP_ADDRESS>
WARN: [SSH] PTY requested: stderr will be merged into stdout
The authenticity of host '<IP_ADDRESS> ()' can't be established.
fingerprint is SHA256:iY2MfKHAVkGK4NN0tW9B84uPLipg+PQ1YOPpd5hPBfY.

Are you sure you want to continue connecting
? (Y/N) Y
WARN: [SSH] PTY requested: stderr will be merged into stdout
ERROR: knife encountered an unexpected error
This may be a bug in the 'bootstrap' knife command or plugin
Please collect the output of this command with the `-VVV` option before filing a bug report.
Exception: NoMethodError: undefined method `empty?' for nil:NilClass
$ knife bootstrap -N client_512_1 <IP_ADDRESS> --ssh-user root -P1 -VV
INFO: Using configuration from /Users/integer/.chef/knife.rb
DEBUG: Checking if we need to accept Chef license to bootstrap node
DEBUG: Reading products and relationships...
DEBUG: Successfully read products and relationships
DEBUG: License acceptance required for chef version: 15
DEBUG: Searching for the following licenses: ["infra-client", "inspec"]
DEBUG: Found license chef_infra_client at /Users/integer/.chef/accepted_licenses/chef_infra_client
DEBUG: Found license inspec at /Users/integer/.chef/accepted_licenses/inspec
DEBUG: Missing licenses remaining: []
DEBUG: All licenses present
WARNING: You provided --ssh-user. This flag is deprecated. Please use '--connection-user USERNAME' instead.
Node client_512_1 exists, overwrite it? (Y/N) Y
Client client_512_1 exists, overwrite it? (Y/N) Y
Creating new client for client_512_1
Creating new node for client_512_1
Connecting to <IP_ADDRESS>
WARN: [SSH] PTY requested: stderr will be merged into stdout
DEBUG: [SSH] root@<IP_ADDRESS><{:user_known_hosts_file=>"/dev/null", :port=>22, :compression=>false, :compression_level=>0, :keepalive=>true, :keepalive_interval=>60, :timeout=>60, :auth_methods=>["none", "password", "keyboard-interactive"], :keys_only=>nil, :keys=>[], :password=>"<hidden>", :forward_agent=>nil, :non_interactive=>true, :verify_host_key=>:always}> (cmd.exe /c ver)
DEBUG: [SSH] opening connection to root@<IP_ADDRESS><{:user_known_hosts_file=>"/dev/null", :port=>22, :compression=>false, :compression_level=>0, :keepalive=>true, :keepalive_interval=>60, :timeout=>60, :auth_methods=>["none", "password", "keyboard-interactive"], :keys_only=>nil, :keys=>[], :password=>"<hidden>", :forward_agent=>nil, :non_interactive=>true, :verify_host_key=>:always}>
The authenticity of host '<IP_ADDRESS> ()' can't be established.
fingerprint is SHA256:iY2MfKHAVkGK4NN0tW9B84uPLipg+PQ1YOPpd5hPBfY.

Are you sure you want to continue connecting
? (Y/N) Y
WARN: [SSH] PTY requested: stderr will be merged into stdout
DEBUG: [SSH] root@<IP_ADDRESS><{:user_known_hosts_file=>"/dev/null", :port=>22, :compression=>false, :compression_level=>0, :keepalive=>true, :keepalive_interval=>60, :timeout=>60, :auth_methods=>["none", "password", "keyboard-interactive"], :keys_only=>nil, :keys=>[], :password=>"<hidden>", :forward_agent=>nil, :non_interactive=>true, :verify_host_key=>:accept_new}> (cmd.exe /c ver)
DEBUG: [SSH] opening connection to root@<IP_ADDRESS><{:user_known_hosts_file=>"/dev/null", :port=>22, :compression=>false, :compression_level=>0, :keepalive=>true, :keepalive_interval=>60, :timeout=>60, :auth_methods=>["none", "password", "keyboard-interactive"], :keys_only=>nil, :keys=>[], :password=>"<hidden>", :forward_agent=>nil, :non_interactive=>true, :verify_host_key=>:accept_new}>
DEBUG: [SSH] root@<IP_ADDRESS><{:user_known_hosts_file=>"/dev/null", :port=>22, :compression=>false, :compression_level=>0, :keepalive=>true, :keepalive_interval=>60, :timeout=>60, :auth_methods=>["none", "password", "keyboard-interactive"], :keys_only=>nil, :keys=>[], :password=>"<hidden>", :forward_agent=>nil, :non_interactive=>true, :verify_host_key=>:accept_new}> (uname -s)
DEBUG: [SSH] root@<IP_ADDRESS><{:user_known_hosts_file=>"/dev/null", :port=>22, :compression=>false, :compression_level=>0, :keepalive=>true, :keepalive_interval=>60, :timeout=>60, :auth_methods=>["none", "password", "keyboard-interactive"], :keys_only=>nil, :keys=>[], :password=>"<hidden>", :forward_agent=>nil, :non_interactive=>true, :verify_host_key=>:accept_new}> (uname -m)
DEBUG: [SSH] root@<IP_ADDRESS><{:user_known_hosts_file=>"/dev/null", :port=>22, :compression=>false, :compression_level=>0, :keepalive=>true, :keepalive_interval=>60, :timeout=>60, :auth_methods=>["none", "password", "keyboard-interactive"], :keys_only=>nil, :keys=>[], :password=>"<hidden>", :forward_agent=>nil, :non_interactive=>true, :verify_host_key=>:accept_new}> (test -f /etc/debian_version && cat /etc/debian_version)
DEBUG: [SSH] root@<IP_ADDRESS><{:user_known_hosts_file=>"/dev/null", :port=>22, :compression=>false, :compression_level=>0, :keepalive=>true, :keepalive_interval=>60, :timeout=>60, :auth_methods=>["none", "password", "keyboard-interactive"], :keys_only=>nil, :keys=>[], :password=>"<hidden>", :forward_agent=>nil, :non_interactive=>true, :verify_host_key=>:accept_new}> (test -f /etc/os-release && cat /etc/os-release)
Traceback (most recent call last):
	48: from /usr/local/bin/knife:317:in `<main>'
	47: from /usr/local/bin/knife:317:in `load'
	46: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/bin/knife:24:in `<top (required)>'
	45: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/application/knife.rb:162:in `run'
	44: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife.rb:221:in `run'
	43: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife.rb:473:in `run_with_pretty_exceptions'
	42: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/local_mode.rb:41:in `with_server_connectivity'
	41: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife.rb:474:in `block in run_with_pretty_exceptions'
	40: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:547:in `run'
	39: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:597:in `connect!'
	38: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:650:in `do_connect'
	37: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap/train_connector.rb:69:in `connect!'
	36: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap/train_connector.rb:56:in `connection'
	35: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh.rb:82:in `connection'
	34: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh.rb:238:in `create_new_connection'
	33: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh.rb:238:in `new'
	32: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh_connection.rb:53:in `initialize'
	31: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/extras/command_wrapper.rb:165:in `load'
	30: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/plugins/base_connection.rb:110:in `platform'
	29: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect.rb:9:in `scan'
	28: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:27:in `scan'
	27: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:27:in `each'
	26: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:33:in `block in scan'
	25: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `scan_children'
	24: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `each'
	23: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:46:in `block in scan_children'
	22: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:46:in `instance_eval'
	21: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/specifications/os.rb:29:in `block in load'
	20: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/helpers/os_windows.rb:7:in `detect_windows'
	19: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/plugins/base_connection.rb:122:in `run_command'
	18: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh_connection.rb:216:in `run_command_via_connection'
	17: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh_connection.rb:247:in `session'
	16: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh_connection.rb:178:in `establish_connection'
	15: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh.rb:246:in `start'
	14: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh.rb:246:in `new'
	13: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/session.rb:90:in `initialize'
	12: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/session.rb:223:in `wait'
	11: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/session.rb:223:in `loop'
	10: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/session.rb:225:in `block in wait'
	 9: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/session.rb:190:in `poll_message'
	 8: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/session.rb:190:in `loop'
	 7: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/session.rb:210:in `block in poll_message'
	 6: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/algorithms.rb:167:in `accept_kexinit'
	 5: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/algorithms.rb:228:in `proceed!'
	 4: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/algorithms.rb:406:in `exchange_keys'
	 3: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/kex/diffie_hellman_group1_sha1.rb:72:in `exchange_keys'
	 2: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/transport/kex/diffie_hellman_group1_sha1.rb:188:in `verify_server_key'
	 1: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/verifiers/always.rb:21:in `verify'
/opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/net-ssh-5.2.0/lib/net/ssh/verifiers/always.rb:50:in `process_cache_miss': fingerprint SHA256:iY2MfKHAVkGK4NN0tW9B84uPLipg+PQ1YOPpd5hPBfY is unknown for "<IP_ADDRESS>" (Net::SSH::HostKeyUnknown)
	31: from /usr/local/bin/knife:317:in `<main>'
	30: from /usr/local/bin/knife:317:in `load'
	29: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/bin/knife:24:in `<top (required)>'
	28: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/application/knife.rb:162:in `run'
	27: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife.rb:221:in `run'
	26: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife.rb:473:in `run_with_pretty_exceptions'
	25: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/local_mode.rb:41:in `with_server_connectivity'
	24: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife.rb:474:in `block in run_with_pretty_exceptions'
	23: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:547:in `run'
	22: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:597:in `connect!'
	21: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:650:in `do_connect'
	20: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap/train_connector.rb:69:in `connect!'
	19: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap/train_connector.rb:56:in `connection'
	18: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh.rb:82:in `connection'
	17: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh.rb:238:in `create_new_connection'
	16: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh.rb:238:in `new'
	15: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh_connection.rb:53:in `initialize'
	14: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/extras/command_wrapper.rb:165:in `load'
	13: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/plugins/base_connection.rb:110:in `platform'
	12: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect.rb:9:in `scan'
	11: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:27:in `scan'
	10: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:27:in `each'
	 9: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:33:in `block in scan'
	 8: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `scan_children'
	 7: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `each'
	 6: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:46:in `block in scan_children'
	 5: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:46:in `instance_eval'
	 4: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/specifications/os.rb:29:in `block in load'
	 3: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/helpers/os_windows.rb:7:in `detect_windows'
	 2: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/plugins/base_connection.rb:122:in `run_command'
	 1: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh_connection.rb:212:in `run_command_via_connection'
/opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh_connection.rb:224:in `rescue in run_command_via_connection': SSH command failed (fingerprint SHA256:iY2MfKHAVkGK4NN0tW9B84uPLipg+PQ1YOPpd5hPBfY is unknown for "<IP_ADDRESS>") (Train::Transports::SSHFailed)
	41: from /usr/local/bin/knife:317:in `<main>'
	40: from /usr/local/bin/knife:317:in `load'
	39: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/bin/knife:24:in `<top (required)>'
	38: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/application/knife.rb:162:in `run'
	37: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife.rb:221:in `run'
	36: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife.rb:473:in `run_with_pretty_exceptions'
	35: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/local_mode.rb:41:in `with_server_connectivity'
	34: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife.rb:474:in `block in run_with_pretty_exceptions'
	33: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:547:in `run'
	32: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:594:in `connect!'
	31: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:618:in `rescue in connect!'
	30: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap.rb:650:in `do_connect'
	29: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap/train_connector.rb:69:in `connect!'
	28: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/chef-15.0.300/lib/chef/knife/bootstrap/train_connector.rb:56:in `connection'
	27: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh.rb:82:in `connection'
	26: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh.rb:238:in `create_new_connection'
	25: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh.rb:238:in `new'
	24: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/transports/ssh_connection.rb:53:in `initialize'
	23: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/extras/command_wrapper.rb:165:in `load'
	22: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/plugins/base_connection.rb:110:in `platform'
	21: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect.rb:9:in `scan'
	20: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:27:in `scan'
	19: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:27:in `each'
	18: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:33:in `block in scan'
	17: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `scan_children'
	16: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `each'
	15: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:51:in `block in scan_children'
	14: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:60:in `scan_family_children'
	13: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `scan_children'
	12: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `each'
	11: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:51:in `block in scan_children'
	10: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:60:in `scan_family_children'
	 9: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `scan_children'
	 8: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:45:in `each'
	 7: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:46:in `block in scan_children'
	 6: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/scanner.rb:46:in `instance_eval'
	 5: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/specifications/os.rb:103:in `block in load'
	 4: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/helpers/os_linux.rb:26:in `linux_os_release'
	 3: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/helpers/os_linux.rb:38:in `parse_os_release_info'
	 2: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/helpers/os_linux.rb:38:in `each_with_object'
	 1: from /opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/helpers/os_linux.rb:38:in `each'
/opt/chef-workstation/embedded/lib/ruby/gems/2.6.0/gems/train-core-2.1.7/lib/train/platforms/detect/helpers/os_linux.rb:43:in `block in parse_os_release_info': undefined method `empty?' for nil:NilClass (NoMethodError)


AvalancheForecastZoneMap: update watch/bulletin behavior

The warnings endpoint can return three different types of products (warnings, watches and special bulletins). We only want the map to flash when there's an active warning.
A small fix to add 1 day to the warning fetch hook for the time machine, since the NAC API assumes a date and appends a time to it.

Fixes https://github.com/NWACus/avy/issues/696


SNAP-2661 : Provide Snappy UI User a control over Auto Update

What changes were proposed in this pull request?
Requirement:

Provide Snappy UI user a control using which he/she can start/stop the auto update of dashboard statistics.

Changes:

Adding JavaScript and CSS code changes for Auto Update On/OFF Switch on UI.

How was this patch tested?

NA

Please review http://spark.apache.org/contributing.html before opening a pull request.

As discussed in huddle (16 Nov 2018), merging the PR.


(Suggestion)  Ability to export as a .obj or other 3d program compatible file??

Would like to state that this mod is an absolute BANGER!
My request is that if I could see support for exporting a model as a .obj or .fbx file to use in Blender, C4D, Maya, etc.
Wanted to do a funny and put some of the playermodels I made into Risk of Rain 2 lmao.
Keep up the AMAZING work!!!

Duplicate of #198


add bbs westerburg

Hey there,
this is a pull request for the BBS Westerburg, the student's mail format is:  @bbs-ww.de
Website: https://bbs-westerburg.de/
If you look at the website (therefore use the item "Service" and click "Schulsozialarbeit")
you will see the domain<EMAIL_ADDRESS>

@kxmpetentes lib/domains/de/bbs-westerburg: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@kxmpetentes lib/domains/de/bbs-westerburg: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@kxmpetentes lib/domains/de/bbs-westerburg: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@kxmpetentes lib/domains/de/bbs-westerburg: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.


Invalid query when using codes generated from an union

Consider the following schema:
schema {
    query: Query
}

type Query {
    search(text: String!): SearchResultPage
}

type Human {
    id: ID!
    name: String!
    totalCredits: Int
}
type Droid {
    id: ID!
    name: String!
    primaryFunction: String
}

union SearchResult = Human | Droid

type SearchResultPage {
    items: [SearchResult]
}

When the codes are generated, the following client projection classes and types are created:
Clients:

SearchGraphQLQuery
SearchItemsDroidProjection
SearchItemsHumanProjection
SearchItemsProjection
SearchProjectionRoot

Types:

Droid
Human
SearchResultPage
SearchResult (interface)

When using the following GraphQLQueryRequest and serializing it using version 4.6
var request = new GraphQLQueryRequest(
                SearchGraphQLQuery.newRequest().text("R2D2").build(),
                new SearchProjectionRoot().items()
                        .onDroid()
                        .primaryFunction())
                .serialize();

query {search(text: "R2D2"){ items   { ... on SearchItemsDroid { __typename primaryFunction } } } }
It create a query with SearchItemsDroid that resulted in a UnknownType when executed within a DgsQueryExecutor:
com.netflix.graphql.dgs.exceptions.QueryException: Validation error of type UnknownType: Unknown type SearchItemsDroid @ 'search/items'
On version 4.2.0, it creates the following query instead:
query {search(text: "R2D2"){ items   { ... on Droid { __typename primaryFunction} } } }
I believe the issue to be in the GraphQLQueryRequest.kt (version 4.6.0) file:
if (projection is BaseSubProjectionNode<*, *>) {
        builder.append(projectionSerializer.serialize(projection.root() as BaseProjectionNode))
    } else if (projection != null) {
        builder.append(projectionSerializer.serialize(projection))
}

In version 4.2.0, the same file shows:
if (projection is BaseSubProjectionNode<*, *>) {
        builder.append(projection.root().toString())
} else if (projection != null) {
        builder.append(projection.toString())
}

The issue is related to the maven plugin (v1.10) using an older version of the dgs-codegen library (v 4.4.1).


Fix island label placements.

Don't allow polygons with label_placement:yes set in output, as Tangram will label these. Instead, generate the label points using the post-processor and delete the original geometry.
For future work: We should probably only be labelling the largest island in a multipolygon with the island label, or at least suppressing the nearby ones until later zooms.
Also: should we have a filter in the output which disallows setting label_placement:yes directly from the YAML? Given that the YAML-generated functions can be applied to points, lines and polygons?
Connects to #399. Requires mapzen/TileStache#153.
@rmarianski could you review, please?

:+1:


Cmake: Find libubox/list.h

Add a CMake FIND_PATH and INCLUDE_DIRECTORIES searching for
libubox/list.h. Some external toolchains which do not include
standard locations would fail to find the header otherwise.
Signed-off-by: Florian Fainelli<EMAIL_ADDRESS>

Thanks.


Limited Documentation Available for Storing Custom Environment Variables

[Enter feedback here]
I'm working with a customer who has a use case for storing global variables at the environment level to be used by multiple developers across multiple use cases.  It was extremely difficult to find this in the documentation.  I was able to scrape it together by scouring the syntax documentation.
env = Environment(name="Sample-Environment")
env.environment_variables.update({'testvar' : 'testval'})
env.register(workspace=ws)
The following page would be a good place to showcase this functionality.
https://docs.microsoft.com/en-us/azure/machine-learning/how-to-use-environments

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

ID: a10c58c2-1767-778c-5591-8b6eb1e50969
Version Independent ID: ecc11aa4-56c9-d8b0-69c0-d9978de4adc5
Content: Create reusable ML environments - Azure Machine Learning
Content Source: articles/machine-learning/how-to-use-environments.md
Service: machine-learning
Sub-service: core
GitHub Login: @rastala
Microsoft Alias: roastala

@BreakingBI Thank you for bringing this to our attention. I will have the content team evaluate this enhancement and make updates as appropriate.

#assign:@peterclu

I've added this as a doc backlog item to track. We'll continue to prioritize this with other items. Thanks so much for the feedback! #please-close


update torch and cuda

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@ShivanshuPurohit sign the CLA


Perfdash - Extracting config paths to flags

Adding support for multi flags
Extracting hardcoded config paths to deployment params.

ref #546

/assign @mborsz

/test pull-perf-tests-clusterloader2-kubemark

/lgtm


"Costinești", "Schitu" are listed in the drop-down menu

Description:
When user writes "Costinești", "Schitu" the location appears in the drop-down menu next to the comune and the county witch is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Costinești"

Expected results
The location appears in the drop-down menu as "Sat Costinești, CONSTANȚA, (Costinești)"

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Schitu"

Expected results
The location appears in the drop-down menu as "Sat Schitu, CONSTANȚA, (Costinești)"


BUG: When in iPad landscape mode, the confirm item page has a white background at the bottom and right side, the hand svg covers the buttons and prevents clickability.

BUG: When in iPad landscape mode, the confirm item page has a white background at the bottom and right side, the hand svg covers the buttons and prevents clickability.
DESCRIPTION
Steps to reproduce:

Start the app and turn to landscape mode
Navigate to confirm item page
Scroll down and to the right

Expected behaviour:

The background should remain blue
The hand svg should be above the buttons

Observed behaviour:

A white background appears at the bottom and right of the page
The hand svg covers the buttons and prevents them from functioning

The image on the confirmation page is split into it's individual images allowing the two images to separate. This is particularly evident in non-portrait screens, which includes landscape mode.
iPad Air landscape mode:

Smaller screen:

Extreme example:

Same issue found under #272


Reserved Words as Method Argument Names Cause Problems In Generated Code?

So I'm trying to use Refit against an API that has geo-coordinates in it. Unfortunately the API authors decided to shorten the argument names, so they are "lat" and "long" (ugh). "long" is of course a reserved word. It turns out you can declare a parameter with the name "long" by prefixing it with @ i.e
Task DoSomething(long lat, long @long)
{
}
However the stub generated by Refit doesn't include the @ on the parameter name in the generated code in the stub file, so it fails to compile.
Is there anyway to tell refit that's a reserved word and it should use the @? I was kind of hoping the @ itself would be enough. I guess I can probably work around this with the AliasAs attribute, but it would nice if it 'just worked'.

Fix on its way :arrow_up: :smile:

Wow, that is impressive! The cynic in me was expecting a, "so don't do that then. Closed as won't fix" response. Thanks! :smile: :+1: :cool:

It's not merged yet and won't be on NuGet for a little while, so in the meantime you'll have to alias or "don't do that" :wink:


uninitialized constant Jekyll::Cache

jekyll 3.9.0 | Error:  uninitialized constant Jekyll::Cache

{% assign meta = "https://wikipedia.org" | metadata %}
{{ meta }}

I received this error after following your install instructions and using your provided example and also included the "open-uri" and "nokogiri" gems. What I tried so far:
bundle install, bundle update, gem cleanup
Any ideas on what could be the issue?

Hi @hanniabu Could you please share your Gemfile, _config.yml, and the file where you have this:
{% assign meta = "https://wikipedia.org" | metadata %}
{{ meta }}

If those files are correct then my guess is there is something conflicting with the plugin and Jekyll version 3.9.0. I will try to reproduce the error once you share your setup. Thanks for reporting!

"jekyll" 3.9.3
"ruby" 3.2.1
"bundle" 2.4.6
I got this error too.
/home/ubuntu/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/jekyll-url-metadata-1.0.3/lib/jekyll-url-metadata/main.rb:17:in `cache': uninitialized constant Jekyll::Cache (NameError)

      @@cache ||= Jekyll::Cache.new("Jekyll::URLMetadata")
                        ^^^^^^^
        from /home/ubuntu/.rbenv/versions/3.2.1/lib/ruby/gems/3.2.0/gems/jekyll-url-metadata-1.0.3/lib/jekyll-url-metadata/main.rb:24:in `metadata'

wow solved!
But github pages doesn't support jekyll 4  above versions. sad for that :(
Thank you for instantly responding my comment. Have a good day!

@10cheon00 GitHub Pages doesn't support custom plugins for any version of jekyll. Only specific whitelisted plugins are available. If you want to use this plugin you need to either build site locally and host the _site folder. Or use a GitHub Action: Example.
@hanniabu For now the solution is to upgrade to Jekyll >=4.0.0. I will try to add logic for older jekyll versions in the meantime.

Yes.  Thank you for providing more information.