Adding API Definition retrieval service implementation

Purpose
Fix for: https://github.com/wso2/apk/issues/439

Codecov Report
Base: 11.68% // Head: 11.69% // Increases project coverage by +0.01% :tada:

Coverage data is based on head (e494f1d) compared to base (5064d7b).
Patch coverage: 16.66% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #449      +/-   ##
==========================================
+ Coverage   11.68%   11.69%   +0.01%
==========================================
  Files          72       72
  Lines        5350     5378      +28
  Branches     2994     3013      +19
==========================================
+ Hits          625      629       +4
- Misses       4725     4749      +24

Impacted Files
Coverage Δ

...rtal/devportal-domain-service/ballerina/apiDAO.bal
0.00% <0.00%> (ø)

...domain-service/ballerina/devportal-api_service.bal
9.77% <11.11%> (+0.07%)
:arrow_up:

...tal/devportal-domain-service/ballerina/apiImpl.bal
92.30% <100.00%> (+2.30%)
:arrow_up:

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 at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


MenuItem is rendered as active link with React 15.3.1

Could be this React version not supported yet? I have created a simple page with the following App code
import React, { Component } from 'react'
import { Button, Menu } from 'stardust'

export default class TryStardust extends Component {
  render() {
    return (

        <Menu>
          <Menu.Item>ABC</Menu.Item>
        </Menu>
        <Button>Hello</Button>

    )
  }
}

Add the generated code is

      ABC

  <button type="button" class="ui button">Hello</button>

We support React 15.x.  The doc site is also a React app using 15.x.
However, the Menu is a legacy component undergoing a complete overhaul, see #382.  Unfortunately, the old (currently published) behavior automatically made the first item active if no other item was active.  Thankfully, there is no such non-sense in the revamped Menu component.


[Chromebook] MSLError: This title is not available to watch instantly

Bug report
Your Environment

Netflix add-on version: 1.18.2+matrix.1
Operating system version/name: Chrome OS 96.0.4664.111 (Build officiel) (32 bits)
Device model:  Acer Chromebook R 13 CB5-312T-K62F

Used Operating system:

[x] Android (Android app support but the operating system is "Chrome OS")
[ ] iOS
[ ] Linux
[ ] OSX
[ ] Raspberry-Pi
[ ] Windows

Describe the bug

Hello,
When I try to play a video, I have the "MSLError: This title is not available to watch instantly"
Please try another title.
To try to solve this problem you can force "Widevine L3" from the add-on Expert settings.
I tried to apply the L3 ESN but the issue is the same.
The ESN isn't the same than the one in my Netflix Android app so i tried to enter it manually in the add-on ESN setting but it said "ESN cannot be used" or something like this. But maybe I made an error : it's a very long code and the copy paste doesn't work.
Thanks :)
Expected behavior

The video should be played :) .
Actual behavior

I have an MSLError.
Steps to reproduce the behavior

Open the add-on
Browse Netflix
Launch a video

Debug log

The debug log can be found here:

https://paste.kodi.tv/denuyenate.kodi
[### Additional context or screenshots (if appropriate)
Other information

Actually I have two issues with the Netflix add-on I just installed on my Chromebook, this is the second:
https://github.com/CastagnaIT/plugin.video.netflix/issues/1285

Confirmting "MSLError: This title is not available to watch instantly" persists after latest Netflix Addon update.

Same here, Kodi 19 (LibreElec). Tried to follow instructions to force L3 in ENV/Widevine settings, but that's not even selectable/changeble (is set to "Disabled").

Same here, Kodi 19 on RPi4. And I confirm the lack of option to force L3 in the plugin.

I ran into the same issue with CoreELEC 19.3. A clean install of CoreELEC and Netflix Addon fixed the issue.

i suspect that the esn generation could be wrong for the chromebook, i need more info:

on expert setting open "Widevine/esn settings", then "save system info" and attach here the file
install the official nfx app take a screenshot of the esn from the app settings (censure only few last chars)

Hi @CastagnaIT :),
Sorry for my late reply.
This is the SystemInfo file:
NFSystemInfo.txt
And this is the screenshot:

Thanks

Same issue here on Windows 10

Plugin worked until 25th Jan 2022, tried to use it tonight 28th and no joy kept getting the same MSLError , but no indication of how to fix it. Only extra info is from CCurlFile::FillBuffer - Failed HTTP returned error 500.
Kodi v 18.9 running on PC on Linux Mint 20.3 64bit version, Intel Core 2 Quad cpu 2.4GHz
Plugin video netflix v1.12.8
Rgrds Peter

@nonobio sorry for the big delay, but this is not the only project i follow
you are the first user to notify me of chromebook use, i am not sure that this fix test will works:

uninstall the addon and also remove settings when prompt
install this test plugin.video.netflix_1.18.3+matrix.1_20220128_t1.zip
try play

let me know what happens, and if fails provide also a new NFsysteminfo file

to all other users this issue is a special case for Chromebook device, other cases will not be taken into account

Plugin worked until 25th Jan 2022, tried to use it tonight 28th and no joy kept getting the same MSLError , but no indication of how to fix it. Only extra info is from CCurlFile::FillBuffer - Failed HTTP returned error 500. Kodi v 18.9 running on PC on Linux Mint 20.3 64bit version, Intel Core 2 Quad cpu 2.4GHz Plugin video netflix v1.12.8
Rgrds Peter

Same here, but with an Odroid C2 (arm) running the netflix plugin 1.12.8
Tried with different versions of widevine that were backed up, tried logging out & in, nothing works :(

Hi @CastagnaIT ,
Don't worry about the delay, it isn't urgent and I understand you don't have only my problem to solve ;) . By the way, thanks again for this add-on.
I did what you said but the issue is the same.
This is the new NFsysteminfo file :
20220201_NFSystemInfo.txt
Thanks :)

Got same MSLError error since today's morning on two devices (Android Projector and raspberrpi 4 - Raspbian GNU/Linux 10 (buster)).

Got it too at about the same time, I'm running LibreElec with Kodi 18.9 on a raspberry pi 4

Also have this error as of today, on several different devices running Libreelec and Coreelec , both Kodi 18.9

@b4zyl, @Tudwall , @lymon66  - Try with this solution. It worked for me OdroidN2/CoreElec

I can confirm that this error started today on Raspbian buster, Kodi 18.7 on a raspberry pi 4

please stop spam this thread for kodi 18

I'm not sure it is a chromebook issue, I ahve the same issue o rpi4, LE 9.2.8, netflix v1.12.8

So do I, see above.

The same is happening with my installation: LE 9.2.8 w Netflix plugin v1.12.8 (the latest in Leia repository). Attached is the debug log.
Why Netflix is doing it to its service....???
kodi20220202.log

@nonobio please try install from scratch (same steps above)
plugin.video.netflix_1.18.4+matrix.1_20220213_t2.zip
If it still does not work, unfortunately i have no other solutions,
out of curiosity the "Playback specification" on ntfx android app say HD or SD?

Hi @CastagnaIT ,
I just tried the 1.18.4 : I have this error : "MSLError: Request failed validation during key exchange."
"Playback specification" say "SD".
Thanks for your help.


Prepare dev releases.

A set of dev-releases so that some folks can test the new AMD loader.
(Note this is a merge into the amd-build branch).

I think dev releases should:

be labeled, not numbered
not be checked into master

And maybe they don't need to go through code review?

I'd like to do nightly automated releases, but we don't have time for that right now I don't think.
What about recommending users build from master?


missing redirects

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65fc48921fd3fe2b355bab65--harness-developer.netlify.app


With admin permissions I get /usr/local/bin/gauge: cannot execute binary file

Steps to replicate

On Mac, with admin permissions install the released version of Gauge using the pkg.
Run install.sh and I get ./install.sh: line 39: /usr/local/bin/gauge: cannot execute binary file
the Details

inblr-<username>:install <username>$ unzip /Users/<username>/Downloads/gauge-0.8.2.nightly-2017-03-21-linux.x86_64\ \(1\).zip
Archive:  /Users/<username>/Downloads/gauge-0.8.2.nightly-2017-03-21-linux.x86_64 (1).zip
   creating: bin/
  inflating: bin/gauge
  inflating: bin/gauge_screenshot
   creating: config/
  inflating: config/gauge.properties
  inflating: config/notice.md
   creating: config/skel/
   creating: config/skel/env/
  inflating: config/skel/env/default.properties
  inflating: config/skel/example.spec
  inflating: install.sh
inblr-<username>:install <username>$ ./install.sh
Installing gauge at /usr/local/bin
Enter custom install location :-

You do not have write permissions for /usr/local
Running script as sudo
Password:
Installed gauge binaries at /usr/local
Creating /Users/<username>/.gauge/config ...
Adding gauge to system path...
Adding GAUGE_ROOT to environment...
Gauge core successfully installed.

Enter comma(',') separated list of plugins which you would like to install :-

Installing plugin html-report ...
./install.sh: line 39: /usr/local/bin/gauge: cannot execute binary file

@sguptatw Is this still an issue?


Change apt-get's & use nala along with apt

Merge with #442 #443
Type of Change

[x] New feature
[x] Refactoring

Description
#422 does this slightly correct; I have added the missing ones that weren't included in his PR
ONLY after I made my 3 PRs did he decide to implement MY fixes.. before: https://github.com/ChrisTitusTech/linutil/commit/61cddeb2566f0c874c15428986381832203f3591 after: https://github.com/ChrisTitusTech/linutil/commit/100fc58daa91b127187497f0061922786747db0d
My commits are VERIFIED, meaning everything that I do contains MY work. Take a look at these 2 commits and decide for your self. The first commit contained INCOMPLETE functionality and only after making my 3 PRs that fixed those issues did he decide to grab the changes in my commits and then implement them in his
Checklist

[x] My code adheres to the coding and style guidelines of the project.
[x] I have performed a self-review of my own code.
[x] My changes generate no errors/warnings/merge conflicts.

@ChrisTitusTech

[!CAUTION]
This PR is not tested.
This implementation is wrong and will not use nala.
Changing apt-get with apt is not recommended when running scripts

Changing apt-get with apt is not recommended when running scripts

This PR is tested. Using apt instead of apt-get is better as it's newer and more developed: apt-get is old and will deprecate eventually, Nala will work; as this is already implemented some-what in the existing scripts.

Your criticism is not appreciated when you copied my whole implementation into YOUR PR, and DID not give credit.. Unlike you I REWROTE everything. Here are the commits on your PR if needed: before: https://github.com/ChrisTitusTech/linutil/commit/61cddeb2566f0c874c15428986381832203f3591 after: https://github.com/ChrisTitusTech/linutil/commit/100fc58daa91b127187497f0061922786747db0d

Here is Adam's input on these PRs

@jeevithakannan2

This PR is not tested.

You have no way of knowing this.

This implementation is wrong and will not use nala.

?? https://github.com/ChrisTitusTech/linutil/pull/422#issuecomment-2355774644

Changing apt-get with apt is not recommended when running scripts

I already proved you wrong in https://github.com/ChrisTitusTech/linutil/pull/422#issuecomment-2355774644.

I think #440 #442 #443 approach this better. #422 is clearly copying the changes from them into his own implementation.

For scripting apt-get will be used.


image pull secrets

Hello,
if I open a MR with image pull secrets to this helm chart, would you be willing to merge it?
thanks

sure, go for it


⚠ Jenkins Plugins Artifactory has degraded performance

In 19dd1a1, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1283 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 7277cc4 after 1 hour, 40 minutes.


Unstable tie breaking for cursor based pagination

Describe the bug
I have an issue with paging not working correctly. I have a datamodel like
type User {
    id: ID! @unique
    numFollowers: Int! @default(value: "0")
}

To Reproduce
Steps to reproduce the behavior:

Go to prisma playground
Run a query like

query users {
  users(
  orderBy: numFollowers_DESC,
  after: null,
  first: 3) {
    id
    numFollowers
  }
}

Take id of the last item and run the same query again, passing inside the after.
Notice that the returned list is empty.
Expected behavior
Consecutive pages of users are paged correctly.
Screenshots
This is from a project that has at least 50 users:
Page 0:

Page 1:

Versions (please complete the following information):

OS: OS X High Sierra
prisma CLI: prisma/1.17.1 (darwin-x64) node-v10.11.0
Prisma Server: 1.17.1

Does your project contain users with numFollowers of negative value?
How many users does your project contain with numFollowers of 0?

My current example project contains 53 users. Two of them have a numFollowers of 1 and everyone else has a numFollowers of 0

I just tested with generating 50 users where their numFollowers was not 0 and paging worked.

So it seems to be broken only when the number is 0?

My hunch is that tiebreakers are not applied correctly. Please add the test data where you can reproduce the error in form of prisma export 🙂.

@marktani please find it here. It's test data from my local server version. The user model is a bit more complicated (has more stuff) but it otherwise reproduces the problem
export-2018-10-05T15:04:38.741Z.zip

I can reproduce this error on 1.19-beta as described here: https://github.com/marktani/r-3258
However, I am not sure if it is really a bug, as I'm not sure if the Relay pagination spec requires pagination to be "stable" for ties.

No

We'll release a fix today for this. Sorry that it took so long and thanks for the detailed reproduction!


When the video ends nothing shows up

When the video ends nothing shows me that the video has ended and sometimes i find myself waiting, until i realise that the video has already ended and i exit or re-watch .
What am asking is a re-watch button or something that shows me that the video has ended ! thnx <3

When the video ends nothing shows me that the video has ended and sometimes i find myself waiting, until i realise that the video has already ended and i exit or re-watch . What am asking is a re-watch button or something that shows me that the video has ended ! thnx <3

I think I will disagree on this it just same thing other video player to like vlc and it's not bad . a button like re watch it just feels like watching video online like in YouTube

Hi,
sorry for the late response but i just got used to it and I think it just fine as it is thank you for your comment <3


Upload files other than images (pdf, doc and so on)

Is there a way out of the box to upload a whitelisted series of file types within the Link uploader inside Django-CKEditor?
I read the code and it seems to be allowing only images.
Thanks

I ended up doing something like this https://gist.github.com/rhymes/32526b198fbcbfb40c68
It's definitely a hack.

There is one pull request waiting. A decision must be made how to handle this. Does django-ckeditor should stick to ckeditor or should it provide wider functionality set.

#153

Other files can be uploaded now, so closing this.


Vulnerability roundup 107: envoy-1.17.3: 3 advisories [8.6]

search, files

[ ] CVE-2021-39162 CVSSv3=8.6 (nixos-unstable)
[ ] CVE-2021-39206 CVSSv3=8.6 (nixos-unstable)
[ ] CVE-2021-39204 CVSSv3=7.5 (nixos-unstable)

CVE details
CVE-2021-39162
Pomerium is an open source identity-aware access proxy. Envoy, which Pomerium is based on, can abnormally terminate if an H/2 GOAWAY and SETTINGS frame are received in the same IO event. This can lead to a DoS in the presence of untrusted upstream servers. 0.15.1 contains an upgraded envoy binary with this vulnerability patched. If only trusted upstreams are configured, there is not substantial risk of this condition being triggered.
CVE-2021-39206
Pomerium is an open source identity-aware access proxy. Envoy, which Pomerium is based on, contains two authorization related vulnerabilities CVE-2021-32777 and CVE-2021-32779. This may lead to incorrect routing or authorization policy decisions. With specially crafted requests, incorrect authorization or routing decisions may be made by Pomerium. Pomerium v0.14.8 and v0.15.1 contain an upgraded envoy binary with these vulnerabilities patched. This issue can only be triggered when using path prefix based policy. Removing any such policies should provide mitigation.
CVE-2021-39204
Pomerium is an open source identity-aware access proxy. Envoy, which Pomerium is based on, incorrectly handles resetting of HTTP/2 streams with excessive complexity. This can lead to high CPU utilization when a large number of streams are reset. This can result in a DoS condition. Pomerium versions 0.14.8 and 0.15.1 contain an upgraded envoy binary with this vulnerability patched.

Scanned versions: nixos-unstable: 34ad3ffe08a.
Cc @lukegb

envoy already at 1.21.1 so I guess we could close this 👍


engine(externalresource): add cleanPersistResource method for filemananger

What problem does this PR solve?

Issue Number: close #7486
What is changed and how it works?

add cleanPersistResource method for filemananger

Check List
Tests

Unit test
Integration test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
`None`

/run-check-issue-triage-complete
/run-all-tests

/cc @amyangfei
/cc @GMHDBJD

/run-all-tests

/run-verify

/run-all-tests

/cc @amyangfei

/run-all-tests

wait chaos test: https://github.com/pingcap/tiflow/actions/runs/3390924082

/merge

/run-verify


Leadspace content model updates

This brand updates the content model to match the other components' content models. I've added links to other components and added more columns.
Changelog
New

Added some columns to add more information
Added the 'gradient' and 'type' fields as those are configurable for the leadspace component in storybook

Changed

Changed primary and secondary calls to action to the component 'button group'

@mfearer94 Are we only add content model for the Left-aligned style options?

@JennySanchez It actually represents all of the options so maybe it should be it's own section near "Usage guidance". What do you think?

@photodow I think we've address all issues in this one.

@mfearer94 As discussed, As discussed, let's give the Content Guidelce its own section and set it up above the Usage Guidance.

@JennySanchez This is done now, please check the deploy link for final approval


About the data format for 3D and 2D joints

Hi authors,
I found that the original 3DPW dataset has:

3D joints with the shape of 24x3
2D joints with the shape of 18x3

However, your customized 3DPW dataset has:

3D joints with the shape of 24x4
2D joints with the shape of 24x3

Therefore, my question is "what is the fourth element of your customized 3D joints"?
Thank you!

Thanks for the questions.
In our code, we use a unified data format for 2D/3D joints for different datasets.
For 3D joints, the format is [x, y, z, v], where the fourth element indicates the visibility of the joint. For most cases (especially SMPL style 3D joints), v is always 1. We keep this format in order to future adaptation to other different 3D joints/mesh topology.
For 2D joints, the format is [x, y, v], following the same format.

Thanks so much for your quick reply!
I found that you already reorganized the original 3DPW dataset and managed your own 3DPW dataset, consisting of .tsv files.
The 3DPW dataset originally has train/validation/test split. However, in your customized 3DPW dataset, I only saw train.img.tsv and test.img.tsv.
Could you please clarify this?

Moreover, I also compared the original 3DPW dataset and your customized 3DPW dataset, and I found the difference.
I took the same person and the same frame. The data is much different:

In the original 3DPW dataset:

joint2d = [[761.0245361328125, 1427.6376953125, 1.0],
				[763.7735595703125, 1254.625, 1.0],
				[757.8124389648438, 1021.6619262695312, 1.0],
				[871.8953247070312, 1010.0325927734375, 1.0],
				[838.7183837890625, 1243.81982421875, 1.0],
				[812.2440185546875, 1417.615966796875, 1.0],
				[709.1945190429688, 1071.94677734375, 1.0],
				[708.8104248046875,<PHONE_NUMBER>882812, 1.0],
				[724.396728515625,<PHONE_NUMBER>734375, 1.0],
				[883.9208984375,<PHONE_NUMBER>726562, 1.0],
				[888.2723388671875,<PHONE_NUMBER>375, 1.0],
				[897.5230102539062, 1059.4345703125, 1.0],
				[807.9381103515625,<PHONE_NUMBER>796875, 1.0],
				[802.7290649414062,<PHONE_NUMBER>03125, 1.0],
				[810.5869140625, 1011.4450073242188, 1.0],
				[805.8743896484375,<PHONE_NUMBER>046875, 1.0],
				[802.6295166015625,<PHONE_NUMBER>226562, 1.0],
				[818.800537109375,<PHONE_NUMBER>945312, 1.0],
				[804.0947265625,<PHONE_NUMBER>96875, 1.0],
				[820.7557983398438,<PHONE_NUMBER>421875, 1.0],
				[833.2789916992188,<PHONE_NUMBER>8125, 1.0],
				[798.1824951171875,<PHONE_NUMBER>546875, 1.0],
				[843.4369506835938,<PHONE_NUMBER>265625, 1.0],
				[772.8783569335938,<PHONE_NUMBER>710938, 1.0]]

In your customized 3DPW dataset:

joint2d = [[ 7.67384253e-01  8.47698757e-02 -5.60344048e-01]
                               [ 8.28211824e-01  3.11791144e-03 -5.87908769e-01]
                               [ 7.10723322e-01 -9.30041110e-04 -5.61701921e-01]
                               [ 7.58508424e-01  1.81683114e-01 -5.69663679e-01]
                               [ 8.45361280e-01 -3.59436410e-01 -5.95123847e-01]
                               [ 6.94116843e-01 -3.71307514e-01 -5.74784826e-01]
                               [ 7.57282539e-01  3.13208635e-01 -5.72228007e-01]
                               [ 8.15533953e-01 -7.35199899e-01 -6.38437082e-01]
                               [ 7.13418712e-01 -7.46048192e-01 -6.23979217e-01]
                               [ 7.60892928e-01  3.61799676e-01 -5.52873324e-01]
                               [ 8.30624588e-01 -7.90706438e-01 -5.26462391e-01]
                               [ 7.28885027e-01 -7.93635708e-01 -5.09829213e-01]
                               [ 7.48760967e-01  5.54727070e-01 -6.02829374e-01]
                               [ 8.22302452e-01  4.70086415e-01 -5.97221059e-01]
                               [ 6.85288513e-01  4.64970268e-01 -5.87709265e-01]
                               [ 7.54457942e-01  6.29499406e-01 -5.69330585e-01]
                               [ 9.07146496e-01  4.77772425e-01 -6.03743600e-01]
                               [ 5.96054458e-01  4.70962621e-01 -5.83015465e-01]
                               [ 9.31566392e-01  2.32074144e-01 -6.41171805e-01]
                               [ 5.78144159e-01  2.32812816e-01 -6.19179812e-01]
                               [ 9.56104924e-01  6.07977247e-04 -6.08673423e-01]
                               [ 5.75637751e-01 -4.62294618e-03 -5.72327194e-01]
                               [ 9.68516244e-01 -7.55253650e-02 -6.00078079e-01]
                               [ 5.71770439e-01 -8.07533496e-02 -5.57852445e-01]]

These two vectors have not only different dimensions but also very different values. The same situation for joint3d.
Could you please clarify this difference?
Thank you so much, and hope to see your answer soon!

We don't use validation set in our experiments. We don't have validation tsv file.
When I look at the first sample in train.label.tsv, I see the expected annotations:
joint2d = [[761.0245361328125, 1427.6376953125, 1.0],
				[763.7735595703125, 1254.625, 1.0],
				[757.8124389648438, 1021.6619262695312, 1.0],
				[871.8953247070312, 1010.0325927734375, 1.0],
				[838.7183837890625, 1243.81982421875, 1.0],
				[812.2440185546875, 1417.615966796875, 1.0],
				[709.1945190429688, 1071.94677734375, 1.0],
				[708.8104248046875,<PHONE_NUMBER>882812, 1.0],
				[724.396728515625,<PHONE_NUMBER>734375, 1.0],
				[883.9208984375,<PHONE_NUMBER>726562, 1.0],
				[888.2723388671875,<PHONE_NUMBER>375, 1.0],
				[897.5230102539062, 1059.4345703125, 1.0],
				[807.9381103515625,<PHONE_NUMBER>796875, 1.0],
				[802.7290649414062,<PHONE_NUMBER>03125, 1.0],
				[810.5869140625, 1011.4450073242188, 1.0],
				[805.8743896484375,<PHONE_NUMBER>046875, 1.0],
				[802.6295166015625,<PHONE_NUMBER>226562, 1.0],
				[818.800537109375,<PHONE_NUMBER>945312, 1.0],
				[804.0947265625,<PHONE_NUMBER>96875, 1.0],
				[820.7557983398438,<PHONE_NUMBER>421875, 1.0],
				[833.2789916992188,<PHONE_NUMBER>8125, 1.0],
				[798.1824951171875,<PHONE_NUMBER>546875, 1.0],
				[843.4369506835938,<PHONE_NUMBER>265625, 1.0],
				[772.8783569335938,<PHONE_NUMBER>710938, 1.0]]

I couldn't find your provided example in our tsv file.
If you find the vector somewhere in our training pipeline (such as model outputs), it would be more explainable. Please note, following the literature, we did some coordinate normalizations for better training (see https://github.com/microsoft/MeshTransformer/blob/main/metro/datasets/human_mesh_tsv.py#L123).
During inference, we will undo the normalization in order to visualize the joints in the image (see https://github.com/microsoft/MeshTransformer/blob/main/metro/utils/renderer.py#L276).

Oh I am sorry for the mistake. The data I got must be:

In your customized 3DPW dataset:

joint2d = [[761.0245361328125, 1427.6376953125, 1.0],
				[763.7735595703125, 1254.625, 1.0],
				[757.8124389648438, 1021.6619262695312, 1.0],
				[871.8953247070312, 1010.0325927734375, 1.0],
				[838.7183837890625, 1243.81982421875, 1.0],
				[812.2440185546875, 1417.615966796875, 1.0],
				[709.1945190429688, 1071.94677734375, 1.0],
				[708.8104248046875,<PHONE_NUMBER>882812, 1.0],
				[724.396728515625,<PHONE_NUMBER>734375, 1.0],
				[883.9208984375,<PHONE_NUMBER>726562, 1.0],
				[888.2723388671875,<PHONE_NUMBER>375, 1.0],
				[897.5230102539062, 1059.4345703125, 1.0],
				[807.9381103515625,<PHONE_NUMBER>796875, 1.0],
				[802.7290649414062,<PHONE_NUMBER>03125, 1.0],
				[810.5869140625, 1011.4450073242188, 1.0],
				[805.8743896484375,<PHONE_NUMBER>046875, 1.0],
				[802.6295166015625,<PHONE_NUMBER>226562, 1.0],
				[818.800537109375,<PHONE_NUMBER>945312, 1.0],
				[804.0947265625,<PHONE_NUMBER>96875, 1.0],
				[820.7557983398438,<PHONE_NUMBER>421875, 1.0],
				[833.2789916992188,<PHONE_NUMBER>8125, 1.0],
				[798.1824951171875,<PHONE_NUMBER>546875, 1.0],
				[843.4369506835938,<PHONE_NUMBER>265625, 1.0],
				[772.8783569335938,<PHONE_NUMBER>710938, 1.0]]

In the original 3DPW dataset:

joint2d = [[8.169990e+02 6.940840e+02 8.994710e-01]
                               [8.064530e+02 8.138730e+02 9.828750e-01]
                               [7.282780e+02 8.140330e+02 9.386620e-01]
                               [7.127130e+02 9.444220e+02 8.730780e-01]
                               [7.127340e+02 1.064240e+03 9.139100e-01]
                               [8.845230e+02 8.138130e+02 9.476240e-01]
                               [8.898530e+02 9.389390e+02 9.635330e-01]
                               [8.950580e+02 1.048680e+03 8.936900e-01]
                               [7.648070e+02 1.064310e+03 8.733710e-01]
                               [7.596690e+02 1.252160e+03 8.256300e-01]
                               [7.645820e+02 1.424360e+03 7.860840e-01]
                               [8.532480e+02 1.059310e+03 8.713770e-01]
                               [8.428340e+02 1.231570e+03 8.600970e-01]
                               [8.066020e+02 1.408730e+03 8.674500e-01]
                               [8.064390e+02 6.885450e+02 1.951078e-01]
                               [8.376640e+02 6.884630e+02 1.843966e-01]
                               [7.651140e+02 6.991450e+02 1.813974e-01]
                               [8.479240e+02 6.939170e+02 3.753400e-02]]

By the way, the data for 3D joints is:

In your customized 3DPW dataset:

joint3d = [[-0.07414655387401581, 0.6259320974349976, 0.23802196979522705, 1.0],
				 [-0.08293654024600983, 0.2553229033946991, 0.11177857965230942, 1.0],
				 [-0.11118228733539581, -0.20798233151435852, -0.03652437776327133, 1.0],
				 [0.11696193367242813, -0.22830316424369812, 0.030360819771885872, 1.0],
				 [0.07074201852083206, 0.23932282626628876, 0.14836804568767548, 1.0],
				 [0.03360944241285324, 0.6109831929206848, 0.2613641917705536, 1.0],
				 [-0.1982978880405426, -0.10928139090538025, 0.02480170875787735, 1.0],
				 [-0.1994788944721222, -0.3582003712654114, 0.01969926245510578, 1.0],
				 [-0.17634113132953644, -0.5815433859825134, -0.05405966565012932, 1.0],
				 [0.13607390224933624, -0.5964640974998474, 0.006664540618658066, 1.0],
				 [0.1584412306547165, -0.36617332696914673, 0.08553362637758255, 1.0],
				 [0.18082615733146667, -0.12912505865097046, 0.108730249106884, 1.0],
				 [-0.017434636130928993, -0.6804583072662354, -0.047672443091869354, 1.0],
				 [-0.02729572169482708, -0.9356586933135986, -0.0475996695458889, 1.0],
				 [-0.0037099719047546387, -0.2259705662727356, 0.015443656593561172, 1.0],
				 [-0.018986718729138374, -0.6225076913833618, -0.03026910126209259, 1.0],
				 [-0.02061682939529419, -0.4550009071826935, 0.003700997680425644, 1.0],
				 [-0.005796360783278942, -0.7664101123809814, -0.11061951518058777, 1.0],
				 [-0.02451862022280693, -0.8751493692398071, -0.04619435593485832, 1.0],
				 [-0.012012489140033722, -0.8034844398498535, -0.1795082986354828, 1.0],
				 [0.01684357412159443, -0.8400061726570129, -0.1395934820175171, 1.0],
				 [-0.04841940104961395, -0.835761547088623, -0.1426447182893753, 1.0],
				 [0.049128368496894836, -0.8115767240524292, -0.05223245173692703, 1.0],
				 [-0.08516306430101395, -0.8038434386253357, -0.058558084070682526, 1.0]]

In the original 3DPW dataset:

joint3d = [[ 7.67384253e-01  8.47698757e-02 -5.60344048e-01]
                                 [ 8.28211824e-01  3.11791144e-03 -5.87908769e-01]
                                 [ 7.10723322e-01 -9.30041110e-04 -5.61701921e-01]
                                 [ 7.58508424e-01  1.81683114e-01 -5.69663679e-01]
                                 [ 8.45361280e-01 -3.59436410e-01 -5.95123847e-01]
                                 [ 6.94116843e-01 -3.71307514e-01 -5.74784826e-01]
                                 [ 7.57282539e-01  3.13208635e-01 -5.72228007e-01]
                                 [ 8.15533953e-01 -7.35199899e-01 -6.38437082e-01]
                                 [ 7.13418712e-01 -7.46048192e-01 -6.23979217e-01]
                                 [ 7.60892928e-01  3.61799676e-01 -5.52873324e-01]
                                 [ 8.30624588e-01 -7.90706438e-01 -5.26462391e-01]
                                 [ 7.28885027e-01 -7.93635708e-01 -5.09829213e-01]
                                 [ 7.48760967e-01  5.54727070e-01 -6.02829374e-01]
                                 [ 8.22302452e-01  4.70086415e-01 -5.97221059e-01]
                                 [ 6.85288513e-01  4.64970268e-01 -5.87709265e-01]
                                 [ 7.54457942e-01  6.29499406e-01 -5.69330585e-01]
                                 [ 9.07146496e-01  4.77772425e-01 -6.03743600e-01]
                                 [ 5.96054458e-01  4.70962621e-01 -5.83015465e-01]
                                 [ 9.31566392e-01  2.32074144e-01 -6.41171805e-01]
                                 [ 5.78144159e-01  2.32812816e-01 -6.19179812e-01]
                                 [ 9.56104924e-01  6.07977247e-04 -6.08673423e-01]
                                 [ 5.75637751e-01 -4.62294618e-03 -5.72327194e-01]
                                 [ 9.68516244e-01 -7.55253650e-02 -6.00078079e-01]
                                 [ 5.71770439e-01 -8.07533496e-02 -5.57852445e-01]]

Could you please elaborate on this difference and share with us your code for creating 3DPW tsv files?

I am not very sure about the format as you pointed out here. I think there are three possible reasons for this problem.

The joint order may be different.
We may use different normalizations (with image size and/or root coordinate).
We may use different coordinate systems.

As I can recall, I actually tried to normalize all these factors before. It has been a while, but I remember that our 3D joints will look similar to the original 3DPW ones as you post here.
Unfortunately, the tsv generation code is missing. The code was written 1 year ago, and I can't find it now. I need some time to dig it out. I may need to rewrite a new code when I have time. I will add it to the repo then.
Thanks a lot for your interests in our work :)

You mean you normalized both joint_2d and joint_3d before writing them into tsv file.
If that is right, why do you still normalize joint_2d and joint_3d in your dataloader code?

We did normalization in the dataloader. Please stay tuned for the tsv generation code!

As far as I figure out, you only provided the tsv generation code for pseudo-3d-dataset (https://github.com/microsoft/MeshTransformer/blob/main/metro/tools/tsv_demo.py)
There is no tsv code for 3DPW dataset. If you can provide it soon, it would be highly appreciated!
Thank you so much!

The 3dpw tsv example code can be found at https://github.com/microsoft/MeshTransformer/blob/main/metro/tools/tsv_demo_3dpw.py

The 3dpw tsv example code can be found at https://github.com/microsoft/MeshTransformer/blob/main/metro/tools/tsv_demo_3dpw.py

Can you provide the code to generate the TSV file of the human36m dataset? Thank you very much.

Hi, wjingdan
I am interested in the authors' code to generate the TSV file of the human36m dataset. Or do you know the difference between TSV file of human36m and the original human36m.
Thank you!

Hi all,
You may find the example script to reproduce Human3.6M tsv files below:
https://github.com/microsoft/MeshTransformer/blob/main/metro/tools/tsv_demo_h36m.py


Multi index table performance

Can somebody explain to me how multi index table fill with 10mil records inside with 9' uint64 fields?
main questions:

lookup operations by primary index and secondary - performance degradation.
if split data to multiple scopes in the table, can it improve the situation?

the multi_index table is a key-value structure in which key (= table id + primary key) are ordered and storing using a tree structure. fields are serialized first into byte stream, so the number of fields will not significantly affect performance. there's another key-value struct to store the mapping of (contract + scope + table name) => (table id)

secondary index are stored in another key-value structure in which key = (table id + secondary index position + secondary key +primary key) and value = (primary key). So performance degradation does happen because insertion/modification/removal need extra work to cater secondary indexing.

unlikely improve, because all key accesses have logarithmic time. Splitting data will not result in less number of total rows. However scope can allow you to have one extra level of data hierarchy.


Normalizing the simplex can screw up the simplex_min in enforce_bounds!

Fixed in https://github.com/jeff-regier/Celeste.jl/pull/302


Contact form Styling

the form should be a bit more structured (I have to thing how we can do it)
in the mail that confirms the sending of the mail the logo should appear, do you know how I can do that?
the favicon is hidden

I think this might work, but now it is not sending emails, so I cant test. Did you test with them? are they getting the answers?

favicon was not set up on the dev. Or did you mean something else?

The favicon also did not work on the real page.
I tested myself with the mails, and at the moment Ben is rechecking

can the warning texts be in orange instead of red?
can we make the checkboxes bigger (hight of the text fields
the botton „Durchsuchen“ should be styled like our bottons. It can also be the Download-Icon but 180° turned.
titles above the text fields in medium
more spacing between the elementgroups
if you choose one text field can teh outline become transparent orange instead of transparent blue?

can you add a reCAPTCHA or Akismet to the contactforms? It says it is not secure to use only mail inputs. Or what do you think about it?

I think there is a plugin directly for that there. We could install and try. The dev server is not working now, I dont know why .

text

I did all of the design requests, plus had an eye on spacings etc. I hope it will work good as well on iPhones, anyways I did the changes using chrome browser let's hope for the best.

Cool. Pull request and I merge it tomorrow in the morning and put it in the dev.


can't view gazebo video in qground control

I want to view gazebo video in qgc.
I follow the instance in: https://dev.px4.io/v1.9.0/en/simulation/gazebo.html
My Step is :
Enable the GStreamer Plugin (if disabled) by changing the BUILD_GSTREAMER_PLUGIN option to "ON" in /Tools/sitl_gazebo/CMakeLists.txt (as shown below):
option(BUILD_GSTREAMER_PLUGIN "enable gstreamer plugin" "ON")
make clean
make px4_sitl gazebo_typhoon_h480
I open qgc and in settings-> general -> video source
and its no video available. I can't find other choice.
my gazebo version is : 9.10
QGC version is : v3.5.4

I have solved , thanks

hi, I think I had the same problem as you, so i want to know how did you solve it. Thank you very much!


ComponentStatusChecker not tripping

It looks like ComponentStatusChecker is not flipping when components are actually down.
Steps To Reproduce

Have kuberhealthy running
Bring down one of the componentstatuses
Observe that no alerts are sent for six minutes

Expected behavior
ComponentStatusChecker should switch to "OK": false,
Versions

Kuberhealthy 1.1.0

ComponentStatusChecker removed in Kuberhealthy 2.0.0.  Closing this as we near a 2.0.0 release.


feat: Add LastConnected metric to device service common config

fixes #4684. Add LastConnected metric to device service common config.

If your build fails  due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

New Dependency Instructions (If applicable)

Codecov Report

Merging #4685 (596b81e) into main (b006ed3) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@           Coverage Diff           @@
##             main    #4685   +/-   ##
=======================================
  Coverage   41.55%   41.55%
=======================================
  Files         105      105
  Lines        9835     9835
=======================================
  Hits         4087     4087
  Misses       5396     5396
  Partials      352      352


Implement best practices for flux-app app

Coming from here.
The goal of this issue is to have the App eventually adhere to standard cloud-native best-practices. The points below are to be considered non-exhaustive. Feel free to add some that make sense and remove some that don't. If this issue does not make sense (e.g. is a duplicate or covers a deprecated app) please close it.
Expected outcome:

[ ] the app has properly set PDBs (as percentages)
[ ] the app can scale horizontally based on Custom Metrics (if it makes sense)
[ ] the app runs with more than 1 replica by default (if it needs HA)
[ ] the app does not use emptyDir volumes if not strictly necessary

It is possible to enable leader election in Flux components via the --enable-leader-election, but we do not need this at the moment for our split giantswarm / customer flux setup.
The emptyDir is needed for Flux to store artifacts and resources it applies to the clusters. There was an approach to use PVCs at an early stage of our Flux offering but it was deprecated  and we moved back to use the upstream recommendation. Cleaning up some leftover files for that via https://github.com/giantswarm/flux-app/pull/195.


Switch.OnCheckListener bug

If switch is already checked when you enter your Fragment for the FIRST time, your OnCheckListener is not registered, it's not triggering when you check the switch.  But when you check it any other time it's working. Really strange...

Same here

Same here 2

Same here 3

Is there a work around?

Yes, it is.

How can I use that fix? I'm a new user please help me I really need that. Thanks


keep protocol destroy logic unchanged

Codecov Report

Merging #5517 into 2.7.5-release will decrease coverage by 0.21%.
The diff coverage is 66.66%.

@@                 Coverage Diff                 @@
##             2.7.5-release    #5517      +/-   ##
===================================================
- Coverage            61.18%   60.97%   -0.22%
+ Complexity             422      420       -2
===================================================
  Files                  921      921
  Lines                37590    37586       -4
  Branches              5465     5450      -15
===================================================
- Hits                 22999    22917      -82
- Misses               12084    12151      +67
- Partials              2507     2518      +11

Impacted Files
Coverage Δ
Complexity Δ

...ava/org/apache/dubbo/config/DubboShutdownHook.java
61.76% <ø> (+2.67%)
0 <0> (ø)
:arrow_down:

.../apache/dubbo/config/bootstrap/DubboBootstrap.java
53.48% <66.66%> (-0.46%)
0 <0> (ø)

...rg/apache/dubbo/remoting/utils/PayloadDropper.java
30.76% <0%> (-38.47%)
0% <0%> (ø)

...bo/config/event/listener/LoggingEventListener.java
37.5% <0%> (-25%)
0% <0%> (ø)

.../apache/dubbo/rpc/protocol/AsyncToSyncInvoker.java
70.83% <0%> (-16.67%)
0% <0%> (ø)

...he/dubbo/common/threadpool/ThreadlessExecutor.java
52.38% <0%> (-11.91%)
0% <0%> (ø)

...che/dubbo/remoting/transport/mina/MinaChannel.java
43.42% <0%> (-10.53%)
16% <0%> (-1%)

...dubbo/remoting/exchange/support/DefaultFuture.java
75% <0%> (-7.76%)
0% <0%> (ø)

.../dubbo/remoting/transport/netty4/NettyChannel.java
61.38% <0%> (-6.94%)
0% <0%> (ø)

... and 25 more

Continue to review full report at Codecov.

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


port SUPERSTARTREKINS to python

The original BASIC presentation of this has some interesting archaeological hints of days when memory was low, users would print out hard copy instructions, and then proceed to load the actual game off of cassette.
For modern users, this would probably be most usefully turned into a README.txt file.

Hmm -- if you think it should be turned into a readme.txt perhaps we should? We could note that in the readme.md in the root folder?

Hmm -- if you think it should be turned into a readme.txt perhaps we should? We could note that in the readme.md in the root folder?

I'll convert it to the plainest of text files and call it maybe instructions.txt

I think that's a great idea, let's update the readme in the root as well so
nobody wastes time converting that "program" then?
On Sat, Mar 6, 2021 at 2:14 PM Dave LeCompte<EMAIL_ADDRESS>wrote:

Hmm -- if you think it should be turned into a readme.txt perhaps we
should? We could note that in the readme.md in the root folder?
I'll convert it to the plainest of text files and call it maybe
instructions.txt
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/coding-horror/basic-computer-games/pull/208#issuecomment-792072428,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALTWVPP4X6TX5C5ZKZZ7LDTCKSMRANCNFSM4YWCXGZQ
.


Btns reducers

For this part of the project:

I create reducers for the joining the mission and leaving the missions
change the status based on the mission_join property

Great work!


[FR] Integration limits

It would be sweet if it was possible to supply integration limits to automate the step of substituting them in and evaluating manually ^_^

I agree with the above comments. Right now I have a simple extension for my code
function SymbolicNumericIntegration.integrate(f, x, x0, x1)
	F = integrate(f, x)[1]
	F = substitute(F, x => x1) - substitute(F, x => x0)
end

Would a PR be of interest?

It would be interesting, but does this solution handle the possibility that either of x0 or x1 are symbolic variables? When I played around with it, substitute didn't work with symbolic variables.

Implemented in the new version (1.2).


Improve OData in the API

The objective is to enable de count operation.
Query already in place should not change.
Now enveloppe response is accessible
https://code-maze.com/aspnetcore-webapi-using-odata/

https://dev.azure.com/freddycoder/ErabliereAPI/_backlogs/backlog/ErabliereAPI Team/Epics?showParents=true&workitem=456


Items aren't actually deleted when the script is run

When the script runs, it claims it's deleting items, but no items are actually removed from Jama.  For example:
nlawrence$ python Main.py
deleting item with id: 1859 and documentKey: ['AGILE_-BUG-1
deleting item with id: 1860 and documentKey: ['AGILE_-BUG-2
Total number of items deleted: 2
ToTal number of items ignored: 0
done

And yet, those items still exist in my instance.  It looks like there's an issue in the delete code, where we're getting items instead of deleting them.  I'm working on a pull request now.

Fixed the bug causing items to not be deleted. Should work now. Thanks for flagging this @nlawrence22


GIX-1220: Add SNS action converters

Motivation
Users should understand the parameters in SNS proposal actions.
For that, we don't want to show optional parameters as [] | [T], instead as undefined | T.
Changes

Add converter toActionOptional that converts the Action of SNS proposals.
New types to be used in the converter function above: ActionOptional, TransferSnsTreasuryFundsOptional, ... Pattern is <Type>Optional.

Tests
No specific tests. Setting the return types ensures the converter does the job.

Tests that provide an input and expect an output.
Even if for nothing else, it's convenient to have example values to use in other tests.
I honestly don't see why tests here would be less useful than for anything else.
There is a lot of code and most of it looks like it wouldn't need tests but you never know where you needed the test until it fails. And if you don't have tests it will never fails.

I honestly don't see why tests here would be less useful than for anything else.

I can't make the test compile and fail. That's what I mean by tests not being useful. If I can't make the test fail and then fix it. What's the point of the test?
Does it make sense to write a test that can't compile and fail?
But for the sake of documentation, I can write them.

@dskloetd ready for another review

@dskloetd ready for another review. Name changed.

Actually, each of the fields should work as undefined. So ideally you'd have another test with every field undefined. Anyway, I'll leave the decision to you. Thanks for adding test coverage!


WebSocket host couldn't be converted to IP address

What happened?
After i launched Decentraland Desktop Client, and then i logged-in as Guest (same thing happened with Wallet), i can't go further from the loading scene with decentraland symbol. The log says
"ArgumentException: The host part could not be converted to an IP address.
Parameter name: url
at WebSocketSharp.Server.WebSocketServer..ctor (System.String url) [0x0005b] in :0
at WebSocketCommunication.StartServer (System.Int32 port, System.Int32 maxPort, System.Boolean withSSL) [0x0002c] in :0
at WebSocketCommunication..ctor (System.Boolean withSSL, System.Int32 startPort, System.Int32 endPort) [0x00032] in :0
at DCL.MainDesktop.InitializeCommunication () [0x00014] in <40dd36d2f5be4428ae2fccf259a43522>:0
at DCL.Main.Awake () [0x00099] in <8610165eba9f457ebe8df6997aeac3bb>:0
at DCL.MainDesktop.Awake () [0x0003b] in <40dd36d2f5be4428ae2fccf259a43522>:0
"
Please see the full log below :
Player.log
Steps to reproduce
Please email me if you can.
<EMAIL_ADDRESS>Operating System
Chrome, Windows 10
Wallet
Metamask
CPU
Intel Xeon(R) W-2245
GPU
NVIDIA Quadro P2200
RAM
32GB
Kernel Version
latest
Unity Version
latest
Realm
none
NameTag
HENAM#83e5

Can you test the following PR? https://github.com/decentraland/explorer-desktop/pull/126
After the CI passes:
You can open the following custom protocol to test: https://renderer-artifacts.decentraland.org/desktop/index.html?dcl://DESKTOP-BRANCH=fix/localhost-to-ip-number

Thanks for the reply.
With that protocol, finally i can log in.
Is this problem happened from my network settings?

Thanks for the reply. With that protocol, finally i can log in. Is this problem happened from my network settings?

It looks like. Your computer is not resolving localhost as <IP_ADDRESS>. And that's is weird.

Well, i thought there would be some hot fixes in these cases.
But that protocol works well with the new desktop client version.
Thanks again :D


hooks to integrate with cloud provider services

Though all major cloud providers provide managed FAAS soltutions there is value proposition for users to run Kubeless on Kubernetes clusters provisioned on cloud providers.
When running Kubeless on cloud providers, its very likely Kubeless need to integrate with services like API gateway, route 53, IAM etc to provide seamless experiance.
Core of Kubeless controller should be desinged with view that it can offload to specific functionality to provider specific plugin.

#507 has some nice requiremetns. Leveraging Kube2iam.

Kubeless moved away from monolith design, to more modular approach. There is a trigger controller for each of the event source. Closing this issue its not relevent anymore.


Adding VScode extensions: php-debug, intelphense, open in GH

It works well. Note that here is a 'Reload required' chip for PHP Debug. Clicking on that reloads the page and all looks well so no need to block this PR.

Thank you @weitzman
I found a better way to install latest version of that extension. It no longer has "Reload Required".


[4.5.3][4.6.0-20211212] wrong diagnostic on specifier-specific "type" and importsNotUsedAsValues="error"

Bug Report
🔎 Search Terms
importsNotUsedAsValues
🕗 Version
4.5.3, when specifier-specific type keyword was added.
⏯ Playground Link
The playground doesn't allow setting importsNotUsedAsValues
💻 Code
// this works

import type { VFC } from 'react';
export const Hello: VFC<{}> = () => Hello World;

and:
// this reports diagnostics

import { type VFC } from 'react';
export const Hello: VFC<{}> = () => Hello World;

should behave the same (no error)
🙁 Actual behavior
This import is never used as a value and must use 'import type' because 'importsNotUsedAsValues' is set to 'error'.ts(1371) on second piece of code.
🙂 Expected behavior
Both examples should not report diagnostics.
@andrewbranch I feel like this is your cup of tea. :)

I have never seen this syntax. Where did you get it from? All documentation I can find always uses import type, which then counts for all imported types from this statement. I don't think the type is a modifier for individual imports. I would actually expect this to be an error.

@MartinJohns it was added in 4.5: https://devblogs.microsoft.com/typescript/announcing-typescript-4-5/#type-on-import-names

Thank you, I definitely missed that one! Then I absolutely agree with your expected behaviour.

I think this is working as intended? When you use --importsNotUsedAsValues error, you are saying “If I write an import declaration, (a) always emit it to JS, and (b) make sure there is an apparent reason why I wrote it in such a way that it needs to be in the JS.” When you write import { type VFC } from "react", you are asking for import {} from "react" to be emitted to the JS. That request doesn’t pass muster with --importsNotUsedAsValues error. It sees an import that is going to be emitted to JS needlessly.
The logic goes like this:

import type { VFC } from "react" emits nothing (because what could it emit?)
import { type VFC } from "react" emits import {} from "react"

This subsequently gets removed under --importsNotUsedAsValues remove (the default) because it is an import that doesn't bring in anything that gets used in an emitting position. (In actuality, these two steps are just one swoop by the transformer, but I think it makes more sense to think of it as two.)

Does that clear it up?

Another helpful piece of the mental model:

import type operates at the ImportDeclaration level
import { type ... } operates at the ImportSpecifier level
importsNotUsedAsValues operates at the ImportDeclaration level (this is the one that’s easy to mix up)

...but it would be nice to avoid two import statements for the same module. That’s part of why TypeScript 4.5 allows a type modifier on individual named imports, so that you can mix and match as needed.
-- taken from https://devblogs.microsoft.com/typescript/announcing-typescript-4-5/#type-on-import-names

I still have to write 2 import statements if I have this flag set to error. I think this should be fixed

There are several oddities when working with the model you're describing, @andrewbranch
Consider the following code:
import { memo, type VFC, type HTMLAttributes } from 'react';

export const Main: VFC<HTMLAttributes<HTMLElement>> = memo((props) => Hello World);

If I remove usage and import specifier of memo, I must also remove the type keyword from the other two specifiers and re-add it as prefix of the import declaration.
I guess my (wrong) assumption was:
"If all specifiers of an import declaration are prefixed with type, it's the same as prefixing the entire import declaration with type"
I understand it's the same as to how the specifiers themselves behave in the module, but it's not the same  to whether the import declaration is removed or not.
I won't lie, this is not the most intuitive behavior.

"If all specifiers of an import declaration are prefixed with type, it's the same as prefixing the entire import declaration with type"

This is true under --importsNotUsedAsValues remove (the default). It sounds like that’s what you want.

@andrewbranch I don't think this was really clear in release notes, it sounded like just a syntatic sugar so we won't need another import statement. I thought if all members are type, then TSC would drop the entire import statement.
We can get this behaviour with --importsNotUsedAsValues remove, but is it possible to get it on TS v5+ using --verbatimModuleSyntax?
Considering the eslint rule people use for enforcing and auto fixing type imports also introduces this option as fixStyle without any documentation that it would change what TSC would emit, I think many people will fall into this trap.


[EventRequest] Table 1294 "Applied Payment Entry" - OnAfterFilterEntryAppliedToOtherStmtLines

Describe the request
Can you please add event OnAfterFilterEntryAppliedToOtherStmtLines in procedure FilterEntryAppliedToOtherStmtLines
Event Publisher would be
   [IntegrationEvent(false, false)]     local procedure OnAfterFilterEntryAppliedToOtherStmtLines(var AppliedPaymentEntry: Record "Applied Payment Entry")     begin     end;
The procedure would look like:
    procedure FilterEntryAppliedToOtherStmtLines()     begin         Reset();         SetRange("Statement Type", "Statement Type");         SetRange("Bank Account No.", "Bank Account No.");         SetRange("Statement No.", "Statement No.");         SetFilter("Statement Line No.", '<>%1', "Statement Line No.");         SetRange("Account Type", "Account Type");         SetRange("Account No.", "Account No.");         SetRange("Applies-to Entry No.", "Applies-to Entry No.");         OnAfterFilterEntryAppliedToOtherStmtLines(Rec);     end;
Additional context
We want to be able to apply additional filters to the record
Internal work item: AB#542664

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 22786.


Bug 1849164: don't store full manifests in installplan status (for bundle images)

Description of the change:
If a manifest comes from a bundle image, instead of storing the manifest itself in the installplan status, we now store a reference to the configmap that contains the manifest. When installing, OLM will look up the manifest and use the correct one.
One additional change was necessary - role/rolebinding name generation is now deterministic. This is because some resources for an installplan are generated by OLM, rather than read directly from the unpacked bundle, and we need identities for them so that we can track the the status of an individual step.
Steps that are references will look like this:
    - resolving: ibm-cloud-databases-redis.v1.0.0
      resource:
        group: rbac.authorization.k8s.io
        kind: ClusterRoleBinding
        manifest: >-
         {"kind":"ConfigMap","name":"cbd102757181a13f9cee81c42815586023b4840d95543e67c1d68f1572e4667","namespace":"openshift-marketplace","catalogSourceName":"aspera","catalogSourceNamespace":"openshift-marketplace","replaces":""}
        name: ibm-cloud-databases-redis.v1.0.079b98b8bd4-i7bdf84b456
        sourceName: aspera
        sourceNamespace: openshift-marketplace
        version: v1
      status: Created

where the configmap references the unpacked bundle for that step.
Motivation for the change:
It is possible to hit size limits in the installplan, if resolution results in lots of large manifests. Bundle images are already unpacked into configmaps on-cluster, so persisting the unpacked manifests in the installplan is not necessary.
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Docs updated or added to /docs
[ ] Commit messages sensible and descriptive

/retest

I will lgtm since this is an urgent bugfix
/lgtm

/hold
I'd like to test with the set of operators we discovered this with before merging

Let's see how the tests perform but I'm a little concerned about the potential for transient read errors (failed to find configmap) impacting the actual step resolution.

Resyncs should cover those cases, but I agree that this needs more stress testing to get numbers.

We are basically adding a roundtrip to the api-server for each object in the bundle.

The current implementation doesn't do any extra roundtripping - it reads the configmap data from the cache. It also only goes to the cache once per bundle (not once per object in the bundle).
I wanted to do a followup that lazy loads the data and only checks if the step needs some work done (so it would skip installed steps / bundles for a sync). The only reason I didn't do that here is because I would've needed to change the stepper interface a lot more than I did (the stepper would need access to the same cache/listers), and I was wary of backporting that.

The current implementation doesn't do any extra roundtripping - it reads the configmap data from the cache. It also only goes to the cache once per bundle (not once per object in the bundle).

That makes sense - forgot we have our informer cache to work with

I wanted to do a followup that lazy loads the data and only checks if the step needs some work done (so it would skip installed steps / bundles for a sync). The only reason I didn't do that here is because I would've needed to change the stepper interface a lot more than I did (the stepper would need access to the same cache/listers), and I was wary of backporting that.

That makes sense

IIRC, bundles are unpacked -- in their entirety -- into a single ConfigMap, which should run into the resource storage limit before the point that this fix will help.

There is a limit for how big a bundle can be right now, which is the amount that we can fit into a single configmap. This PR removes (well, extends greatly) the limit of how many bundles can be unpacked and installed via a single installplan. This limit was hit with 19 operators in a cluster.

@exdx @njhale Thanks for the thorough reviews - I've addressed all the feedback and I think it's ready to go

/retest

/cherry-pick release-4.5
/cherry-pick release-4.4

/hold cancel


Error: unable to automatically load instrument, deploy may failed

Hi,
when i was using pymoku on my windows PC, i received an error:
FileNotFoundError: [Errno 2] no such file or directory: 'C:\\Users\\...\pymoku\\data/mokudata-474.tar.gz'

Hi @OneSpare, @kaotigger.  Sorry for the slow response.
Make sure your pymoku install is up to date, and that you've fetch a copy of the instrument binaries:
pip install --upgrade pymoku
moku update fetch


V1.2 Add support for cancelling all appointments with Nric if patient is deleted

LGTM! Thanks @ThatGirlJam :D


Flake8

style cleanup

Coverage decreased (-0.3%) to 88.3% when pulling b387ace8c7e0eada349795012993defddccb3169 on piotr1212:flake8 into 0d5a0deac07e4bea822e1350c939f89acb370033 on graphite-project:master.

Wow ! What a huge effort!
Looks good, thanks!


Problem when starting the executor in the quickstart instructions

After successfully completing the previous steps, I have a problem (on Mac OS 11.6) when executing the line kind create cluster --name quickstart-armada-executor-0 --config ./docs/quickstart/kind-config-executor.yaml
The output I get is as follows:
Creating cluster "quickstart-armada-executor-0" ...
 ✓ Ensuring node image (kindest/node:v1.21.1) 🖼
 ✓ Preparing nodes 📦 📦
 ✓ Writing configuration 📜
 ✓ Starting control-plane 🕹
 ✓ Installing CNI 🔌
 ✓ Installing StorageClass 💾
 ✗ Joining worker nodes 🚜
ERROR: failed to create cluster: failed to join node with kubeadm: command "docker exec --privileged quickstart-armada-executor-0-worker kubeadm join --config /kind/kubeadm.conf --skip-phases=preflight --v=6" failed with error: exit status 1
Command Output: I0207 19:51:54.731041     134 join.go:395] [preflight] found NodeName empty; using OS hostname as NodeName
I0207 19:51:54.731094     134 joinconfiguration.go:74] loading configuration from "/kind/kubeadm.conf"
I0207 19:51:54.732689     134 controlplaneprepare.go:211] [download-certs] Skipping certs download
I0207 19:51:54.732760     134 join.go:465] [preflight] Discovering cluster-info
I0207 19:51:54.732771     134 token.go:78] [discovery] Created cluster-info discovery client, requesting info from "quickstart-armada-executor-0-control-plane:6443"
I0207 19:51:54.752636     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s 200 OK in 19 milliseconds
I0207 19:51:54.753547     134 token.go:221] [discovery] The cluster-info ConfigMap does not yet contain a JWS signature for token ID "abcdef", will try again
I0207 19:52:00.647507     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s 200 OK in 8 milliseconds
I0207 19:52:00.647967     134 token.go:221] [discovery] The cluster-info ConfigMap does not yet contain a JWS signature for token ID "abcdef", will try again
I0207 19:52:07.064834     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s 200 OK in 4 milliseconds
I0207 19:52:07.066638     134 token.go:103] [discovery] Cluster info signature and contents are valid and no TLS pinning was specified, will use API Server "quickstart-armada-executor-0-control-plane:6443"
I0207 19:52:07.066672     134 discovery.go:51] [discovery] Using provided TLSBootstrapToken as authentication credentials for the join process
I0207 19:52:07.066681     134 join.go:479] [preflight] Fetching init configuration
I0207 19:52:07.066684     134 join.go:517] [preflight] Retrieving KubeConfig objects
[preflight] Reading configuration from the cluster...
[preflight] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -o yaml'
I0207 19:52:07.077388     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/namespaces/kube-system/configmaps/kubeadm-config?timeout=10s 200 OK in 8 milliseconds
I0207 19:52:07.081036     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/namespaces/kube-system/configmaps/kube-proxy?timeout=10s 200 OK in 2 milliseconds
I0207 19:52:07.085272     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/namespaces/kube-system/configmaps/kubelet-config-1.21?timeout=10s 200 OK in 2 milliseconds
I0207 19:52:07.087304     134 interface.go:431] Looking for default routes with IPv4 addresses
I0207 19:52:07.087335     134 interface.go:436] Default route transits interface "eth0"
I0207 19:52:07.087639     134 interface.go:208] Interface eth0 is up
I0207 19:52:07.087783     134 interface.go:256] Interface "eth0" has 3 addresses :[<IP_ADDRESS>/16 fc00:f853:ccd:e793::4/64 fe80::42:acff:fe12:4/64].
I0207 19:52:07.087838     134 interface.go:223] Checking addr  <IP_ADDRESS>/16.
I0207 19:52:07.087845     134 interface.go:230] IP found <IP_ADDRESS>
I0207 19:52:07.087904     134 interface.go:262] Found valid IPv4 address <IP_ADDRESS> for interface "eth0".
I0207 19:52:07.087911     134 interface.go:442] Found active IP <IP_ADDRESS>
I0207 19:52:07.095085     134 kubelet.go:110] [kubelet-start] writing bootstrap kubelet config file at /etc/kubernetes/bootstrap-kubelet.conf
I0207 19:52:07.096477     134 kubelet.go:118] [kubelet-start] writing CA certificate at /etc/kubernetes/pki/ca.crt
I0207 19:52:07.096942     134 loader.go:372] Config loaded from file:  /etc/kubernetes/bootstrap-kubelet.conf
I0207 19:52:07.097464     134 kubelet.go:139] [kubelet-start] Checking for an existing Node in the cluster with name "quickstart-armada-executor-0-worker" and status "Ready"
I0207 19:52:07.099440     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 1 milliseconds
I0207 19:52:07.099979     134 kubelet.go:153] [kubelet-start] Stopping the kubelet
[kubelet-start] Writing kubelet configuration to file "/var/lib/kubelet/config.yaml"
[kubelet-start] Writing kubelet environment file with flags to file "/var/lib/kubelet/kubeadm-flags.env"
[kubelet-start] Starting the kubelet
[kubelet-start] Waiting for the kubelet to perform the TLS Bootstrap...
I0207 19:52:12.243315     134 loader.go:372] Config loaded from file:  /etc/kubernetes/kubelet.conf
I0207 19:52:12.254467     134 cert_rotation.go:137] Starting client certificate rotation controller
I0207 19:52:12.255638     134 loader.go:372] Config loaded from file:  /etc/kubernetes/kubelet.conf
I0207 19:52:12.257414     134 kubelet.go:188] [kubelet-start] preserving the crisocket information for the node
I0207 19:52:12.257449     134 patchnode.go:30] [patchnode] Uploading the CRI Socket information "unix:///run/containerd/containerd.sock" to the Node API object "quickstart-armada-executor-0-worker" as an annotation
I0207 19:52:12.766987     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 8 milliseconds
I0207 19:52:13.260669     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 2 milliseconds
I0207 19:52:13.762001     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:14.262096     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:14.763471     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 5 milliseconds
I0207 19:52:15.264339     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 5 milliseconds
I0207 19:52:15.763939     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 5 milliseconds
I0207 19:52:16.264853     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 5 milliseconds
I0207 19:52:16.762012     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:17.261037     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:17.763583     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 5 milliseconds
I0207 19:52:18.263518     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 5 milliseconds
I0207 19:52:18.762022     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:19.262607     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:19.762389     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:20.261950     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:20.762026     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:21.261297     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:21.762442     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:22.262276     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:22.761374     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:23.261551     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 2 milliseconds
I0207 19:52:23.762048     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:24.261624     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:24.760447     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 2 milliseconds
I0207 19:52:25.260436     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 2 milliseconds
I0207 19:52:25.762209     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:26.240283     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:26.739939     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:27.240642     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:27.740034     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:28.240642     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:28.739286     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:29.240073     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:29.740324     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:30.238566     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 2 milliseconds
I0207 19:52:30.738274     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 2 milliseconds
I0207 19:52:31.340967     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 104 milliseconds
I0207 19:52:31.737834     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 2 milliseconds
I0207 19:52:32.239393     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:32.739543     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:33.241116     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:33.739425     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:34.239281     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:34.739287     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:35.242942     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 6 milliseconds
I0207 19:52:35.739899     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:36.241927     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:36.740342     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:37.241349     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 5 milliseconds
I0207 19:52:37.740601     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:38.239817     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:38.738816     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:39.239670     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:39.739287     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:40.241099     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:40.740017     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:41.239873     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:41.739751     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:42.240711     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:42.739632     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:43.241524     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 5 milliseconds
I0207 19:52:43.739069     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:44.239922     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:44.742522     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 6 milliseconds
I0207 19:52:45.239714     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:45.739703     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:46.239909     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:46.738885     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
[kubelet-check] Initial timeout of 40s passed.
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp [::1]:10248: connect: connection refused.
I0207 19:52:47.239891     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:47.739054     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:48.240055     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:48.739532     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:49.240670     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:49.738704     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 2 milliseconds
I0207 19:52:50.239708     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:50.739670     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:51.240356     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:51.740047     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp [::1]:10248: connect: connection refused.
I0207 19:52:52.240384     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:52.739953     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:53.240284     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:53.740313     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:54.238937     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:54.739075     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 2 milliseconds
I0207 19:52:55.240347     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:55.739063     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 2 milliseconds
I0207 19:52:56.216199     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 2 milliseconds
I0207 19:52:56.717446     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:57.217777     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:57.718406     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 5 milliseconds
I0207 19:52:58.217264     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:58.716924     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:52:59.217671     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:52:59.716791     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:53:00.217001     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:53:00.716733     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:53:01.218274     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:53:01.716795     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
[kubelet-check] It seems like the kubelet isn't running or healthy.
[kubelet-check] The HTTP call equal to 'curl -sSL http://localhost:10248/healthz' failed with error: Get "http://localhost:10248/healthz": dial tcp [::1]:10248: connect: connection refused.

I0207 19:54:02.173082     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:54:02.673103     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:54:03.172527     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:54:03.673415     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:54:04.172388     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:54:04.672481     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:54:05.173427     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:54:05.673214     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:54:06.173152     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:54:06.673568     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:54:07.174415     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 5 milliseconds
I0207 19:54:07.673400     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:54:08.172994     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:54:08.672847     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:54:09.174040     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:54:09.673946     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:54:10.172132     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:54:10.673396     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:54:11.173336     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 4 milliseconds
I0207 19:54:11.672862     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 3 milliseconds
I0207 19:54:12.174565     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 5 milliseconds
I0207 19:54:12.177378     134 round_trippers.go:454] GET https://quickstart-armada-executor-0-control-plane:6443/api/v1/nodes/quickstart-armada-executor-0-worker?timeout=10s 404 Not Found in 2 milliseconds
timed out waiting for the condition
error uploading crisocket
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/join.runKubeletStartJoinPhase
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/join/kubelet.go:190
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run.func1
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:234
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).visitAll
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:421
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:207
k8s.io/kubernetes/cmd/kubeadm/app/cmd.newCmdJoin.func1
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/join.go:172
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).execute
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:850
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).ExecuteC
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:958
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).Execute
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:895
k8s.io/kubernetes/cmd/kubeadm/app.Run
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/kubeadm.go:50
main.main
	_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/kubeadm.go:25
runtime.main
	/usr/local/go/src/runtime/proc.go:225
runtime.goexit
	/usr/local/go/src/runtime/asm_amd64.s:1371
error execution phase kubelet-start
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run.func1
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:235
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).visitAll
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:421
k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow.(*Runner).Run
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/phases/workflow/runner.go:207
k8s.io/kubernetes/cmd/kubeadm/app/cmd.newCmdJoin.func1
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/cmd/join.go:172
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).execute
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:850
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).ExecuteC
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:958
k8s.io/kubernetes/vendor/github.com/spf13/cobra.(*Command).Execute
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/vendor/github.com/spf13/cobra/command.go:895
k8s.io/kubernetes/cmd/kubeadm/app.Run
	/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/app/kubeadm.go:50
main.main
	_output/dockerized/go/src/k8s.io/kubernetes/cmd/kubeadm/kubeadm.go:25
runtime.main
	/usr/local/go/src/runtime/proc.go:225
runtime.goexit
	/usr/local/go/src/runtime/asm_amd64.s:1371

Appears related to this. Hoping the kubernetes folks can fix this or offer us a reliable workaround. I haven't so far been able to work around it on Mac OS X

Uploaded a zip of my logs. Let's see what comes of it.

Thanks for continuing to look into this :) sadly I don't have a readily available Mac OS machine so your work is much appreciated.

The issue is now here

Works fine on OS X Monterey 12.3.1 and using k8s version v1.21.10
This PR adds fixes for quickstart - https://github.com/G-Research/armada/pull/957

This looks to be fixed with https://github.com/G-Research/armada/pull/957