OpenCM 9.04 problem with linux and ROS

Hello, I am using OpenCM9.04 for my project. I have passed through different difficulties.

PC1 with AMD64 architecture works fine with Robotis when I controlled with Windows 10. The motors aka dynamixels are pinged successfully and work fine.

I have downloaded and follow all the tutorials to build by using ROS and linux but when I ping the dynamixels so it dont find any dynamixels. I have also tried position control, but it gives error TxxRxx: The status packet is missing or some error about status packet

PC2 with aarch64 architecture: (Using Linux)
2.1) I have downloaded and follow all the tutorials to build by using ROS and linux but when I ping the dynamixels so it dont find any dynamixels. I have also tried position control, but it gives error TxxRxx: The status packet is missing or some error about status packet

2.2) I then used Arduino IDE to code OpenCm9.04 but when I port to arduino and installing OPENCM9.04 library it gives "opencm-gcc is not available for your operating system "
I want to know that is why OPENCM9.04 dont work with ROS and linux??? and also about opencm-gcc is not available?
Also when I am using my PC x86_64, i first use arduino to ping the dynamixel, during uploading it says "Enter Bootloader" then after some seconds it says done uploaing, application success. What do it mean "Enter Bootloader"? Does it entering the bootloader or ask from us. I have never faced this issue in windows.

Reply here please

Hi, @jawad-tech

Q2, Q3,
I then used Arduino IDE to code OpenCm9.04 but when I port to arduino and installing OPENCM9.04 library it gives "opencm-gcc is not available for your operating system "

I think it seems to be an architecture (32bit, 64bit) problem.
Did you install the dependency files as described below?

OpenCM9.04 install on linux

Also when I am using my PC x86_64, i first use arduino to ping the dynamixel, during uploading it says "Enter Bootloader" then after some seconds it says done uploaing, application success. What do it mean "Enter Bootloader"? Does it entering the bootloader or ask from us. I have never faced this issue in windows.

It is correct that the above log also appears in WINDOWS.
And this means "OpenCM 9.04 has entered the boot loader". I think this expression can cause misunderstanding. However, the person who created the boot loader indicated it, and changing the boot loader can cause many problems, which is difficult to fix.

Q) Can you answer this please?
I am using Linux ubuntu 16.04 (x86_64) to control the dynamixel servo controllers with Opencm board. I have successfully control the dynamixels with windows using arduino IDE but in linux i am facing some issues:
1.1) When i build the dynamixel-sdk C++ and python libraries to ping the servo, it says TxxRxxerror: No status packet
SO I have followed the issues on github.com dynamixel repository, and do not find the solution.
a) I have tried to reduce the value of timer from 16 msec to 8,4,2,1 msec but all in vain.
b) I am also facing problems, as I followed the tutorial from emanual robotis, when i download 99-dynamixel rule file and place in it the /etc/udev/rules.d but when i check the
cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
there is no directory. (I have ACM0 instead of USB so I changed the Kernel=/dev/ttyACM* instead of Kernel=/dev/ttyUSB*).
I have downloaded and follow all the tutorials to build by using ROS and linux but when I ping the dynamixels so it dont find any dynamixels. I have also tried position control, but it gives error TxxRxx: The status packet is missing or some error about status packet

@jawad-tech

but when i check the
cat /sys/bus/usb-serial/devices/ttyUSB0/latency_timer
there is no directory. (I have ACM0 instead of USB so I changed the Kernel=/dev/ttyACM* instead of Kernel=/dev/ttyUSB*).

ACMx does not have a latency_timer file. Therefore, the above setting is meaningless.
Please check the permissions of the port (eg dev / ttyACM0) connected to OpenCM9.04.

Yes i also tried
sudo chmod a+rw /dev/ttyACM0
and
sudo chmod 777 /dev/ttyACM0
The port is ok.
Still the same error.
What is the issue then?  Please Read my post and  give  answer to every question please.
Thanks
What is the possible cause of No status packet RX timeout?

i also did
modprobe -r ftdi_sio
modprobe ftdi_sio vendor = my usb vendor Id
product=my product id
When i check the port after it says
dialout 166 /tty/ACM0 it says like this

The current problem is that the opencm-gcc problem and the port are not working properly.

PC2 with aarch64 architecture: (Using Linux)

Please let me know the exact specifications for the above environment.
The opencm-gcc error does not occur in the linux 64bit environment I'm testing. In other words, I can not reproduce your situation.

What is the possible cause of No status packet RX timeout?

There is a possibility that data is not coming into the port mainly or data is lost/collided.
For more information about the SDK, please view the SDK manual or leave an issue in the SDK repository.

I want to know that is why OPENCM9.04 dont work with ROS and linux???

Please run the ROS example in OpenCM 9.04. OpenCM 9.04 also works in ROS and Linux environments. (Only for small resources)
And, please let me know the connection configuration between OpenCM 9.04 and PC.
I thought that you would not have a problem if you succeeded on Windows10, but please let me know.
And please let me know what code you are using in OpenCM 9.04. (Note that code that is not a basic example is hard to look at)

I am using the Dynamixel SDK ROS package as found in DYnamixel SDK package. I tried
rosrun dynamixel_workbench_toolbox find_dynamixel /dev/ttyACM0
It does not find any  dynamixel

I have found the answer to what I asked you here.
Your usage seems to be wrong.
We have left the answer in the issue below, so please check it out.

https://github.com/ROBOTIS-GIT/DynamixelSDK/issues/314

I understand your point and reached to the solution, but still i have to ask one question that
in my PC with x86_64
i executed
sudo apt-get install libncurses5-dev:i386 it Ran successfully and arduino on linux works cheers
but on my other PC with aarch64 architecture the libncurses5-dev exists but here you see Its the matter of cross compiling because my aarch64 IS different from amd i386 so i need a library for cross compiling.
Suggest me please

the libncurses5-dev:i386 doesn't work on my PC with  aarch64

@jawad-tech
The current OpenCM 9.04 compiler uses GNU-ARM-Embedded.
And the current version is 5-2016-q2-update.
There is a release note and README in the link above, which shows support for Arm architecture 64bit.
The README contains the following precautions.

For 64 bit system, 32 bit libc and libncurses are required to run the tools.

Currently I do not have a PC to test aarch64, so it is difficult to know which package to install and whether it works.
This is due to the dependencies of the operating system on the system, so I need to find out about it.

can you please try it and provide me a solution.
On Thursday, July 18, 2019, 3:08:48 PM GMT+8, Kei<EMAIL_ADDRESS>wrote:
@jawad-tech
The current OpenCM 9.04 compiler uses GNU-ARM-Embedded.
And the current version is 5-2016-q2-update.
There is a release note and README in the link above, which shows support for Arm architecture 64bit.
The README contains the following precautions.
For 64 bit system, 32 bit libc and libncurses are required to run the tools.
Currently I do not have a PC to test aarch64, so it is difficult to know which package to install and whether it works.
This is due to the dependencies of the operating system on the system, so I need to find out about it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@jawad-tech

can you please try it and provide me a solution.

Unfortunately, there is no environment that I can test. However, there is a suggestion that I made to the previous content. Please come to GitHub and check the issue. (Not mail)

actually i am a beginner in linux so need some expert opinion please. Kindly help me. I will also try with my rookie skills

Well itried to build the toolchain but it still stays that tolls_opencm are not present for your architecture, when i installed opencm from boards manager in arduino IDE.
the steps i followed to install the GNU-ARM-EMBEDDED are

sudo add-apt-repository ppa:team-gcc-arm-embedded/ppa
sudo apt-get update
sudo apt-get install gcc-arm-embedded

@jawad-tech
Have you tried the links below that I mentioned above?
The content you wrote is different from the link I gave you.

+Add: I can not test it myself, but I found the link below.
Running 32 bit applications on Aarch64 By James Kingdon, July 22, 2017

This issue has been closed as there weren't recent activities. Please feel free to reopen this thread if there's any opinion to throw. Thanks.


jdk11u-aix-ppc64-hotspot fails: "NUMBER_OF_FRAMES" is already defined with a different definition

Thank you for reporting a broken build! Please fill in the following details:

Jenkins link to the failing log:
https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-aix-ppc64-hotspot/1048/console
Which platforms (OS+arch) are affected:
AIX jdk11u
If you look at the historic logs, does the problem appear to be specific to one machine?
no
Link to any upstream project bug report (e.g. OpenJ9/JBS)

18:29:13  * For target support_test_hotspot_jtreg_native_support_libgetstacktr001_libgetstacktr001.o:
18:29:13  "./test/hotspot/jtreg/vmTestbase/nsk/jvmti/GetStackTrace/getstacktr001/getstacktr001.cpp", line 56.9: 1540-0848 (S) The macro name "NUMBER_OF_FRAMES" is already defined with a different definition.
18:29:13  "/usr/include/sys/mstsave.h", line 260.9: 1540-0425 (I) "NUMBER_OF_FRAMES" is defined on line 260 of "/usr/include/sys/mstsave.h".

https://bugs.openjdk.java.net/browse/JDK-8210205 Looks like a related upstream issue

Yeah building the GA code looks ok https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-aix-ppc64-hotspot/1052/

As JDK-8210205 is from a few years back, and says resolved - does anyone inform them that something (similar) has happened again?

@sxa @aixtools it looks like recent jdk11u commit
https://github.com/adoptium/jdk11u/commit/4b591db099860cf0b1908cff960e0087d68385fc#diff-885e678e7440a0827db43a64233bb824587515d72a1822d5c6b93250443845f6
caused it, as in jdk-11.0.13 these files were built by the c compiler, which compiles NUMBER_OF_FRAMES fine.
I think the failure for NUMBER_OF_FRAMES only occurs with the cpp compiler.

Possible that it does not fail with a regular C compiler, which might explain why the recent change passed. But considering the the file extension is .cpp - I would think when using the C compiler the files are ignored - and that is why it passed.
Probably a better log/commit statement and/or an inline comment - to prevent a future regression.

Looks like jdk11u C versions of the files (eg.getstacktr001.c) have always been NUMBER_OF_FRAMES, the fix in jdk(HEAD) http://hg.openjdk.java.net/jdk/jdk/rev/72291a181f8d should have been backported at the same time as changing C -> CPP

	I did not look that deeply in the include files and see whether this macro was always visible, or only with c++ builds. At least this gives an idea to why the macro name was changed back.
	Get Outlook for iOS

From: Andrew Leonard @.***>Sent: Wednesday, December 22, 2021 11:34 AMTo: adoptium/temurin-buildCc: Michael Felt; MentionSubject: Re: [adoptium/temurin-build] jdk11u-aix-ppc64-hotspot fails: "NUMBER_OF_FRAMES" is already defined with a different definition (Issue #2807)
Looks like jdk11u C versions of the files (eg.getstacktr001c) have always been NUMBER_OF_FRAMES, the fix in jdk(HEAD) http://hg.openjdk.java.net/jdk/jdk/rev/72291a181f8d should have been backported at the same time as changing C -> CPP
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Fix was merged upstream and build 1058 https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/jdk11u/job/jdk11u-aix-ppc64-hotspot/ was successful, therefore closing this issue.

Hurrah, just in time!


Don't register editor in Quick Open Recently Used Editor for short visits.

Very often I accidentally switch to the wrong editor using Ctrl-Tab (cycling through the recently used editors list), and immediately after i switch to the right one. Now that "wrong" editor will be at my next single Ctrl+Tab and so I almost always navigate to the wrong editor again, having to re-open the Ctrl-Tab list again to pick the right one.
Solution Proposal:
Don't register an editor in the least recently used list if I don't interact with it and/or for X amount of time spent on it. So accidental switches are discarded, and a single Ctrl+Tab takes me back to where I wanted instead of the wrong editor again.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


More intuitive demo, introducing The Mint

Codecov Report

Merging #55 into master will increase coverage by 0.15%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #55      +/-   ##
==========================================
+ Coverage   94.56%   94.71%   +0.15%
==========================================
  Files          13       12       -1
  Lines         589      549      -40
==========================================
- Hits          557      520      -37
+ Misses         32       29       -3

Impacted Files
Coverage Δ

src/lib.rs
100% <ø> (ø)
:arrow_up:

src/transaction.rs
97.26% <100%> (-1.37%)
:arrow_down:

src/accountant.rs
94.49% <100%> (ø)
:arrow_up:

src/accountant_stub.rs
89.41% <100%> (ø)
:arrow_up:

src/signature.rs
100% <100%> (ø)
:arrow_up:

src/log.rs
100% <100%> (ø)
:arrow_up:

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 a420a92...5dd567d. Read the comment docs.


_CastError (Null check operator used on a null value)

In Flutter, when testing on MacOS, I get a _CastError (Null check operator used on a null value) error on line 18 in excel_to_json.dart.

I am using the latest Flutter
I haven't made any edits to the code
I am uploading a standard .xlsx that is not empty
I use the provided example code.

Screenshots

Desktop (please complete the following information):

OS: macOS Monterey 12.6

Hi, thanks for reporting.
I'm analyzing what happened and what I can do to fix it.
As soon as I have more information, I'll come back here.

Thank you so much for taking a look. I really appreciate all the hard work
you've put into this. :-)
On Tue, Nov 1, 2022 at 9:57 PM Vitor Amaral de Melo <
@.***> wrote:

Hi, thanks for reporting.
I'm analyzing what happened and what I can do to fix it.
As soon as I have more information, I'll come back here.
—
Reply to this email directly, view it on GitHub
https://github.com/vitoramaral10/excel_to_json/issues/10#issuecomment-1299059048,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBEQTQXSP3DBJ6MDHHC7TWGFYZHANCNFSM6AAAAAARUDAANA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thank you for resolving this, @vitoramaral10 ! :-)


fix split fix

Edit: you already fixed it, but this solution is maybe shorter. Please have a look and decide what you prefer (and then close this PR :-)
--
The commit af85a999d3e8d27fa00899be2ef7997d9725ee92 introduced a regression: since it splits more often (and returns false), the right part is sometimes lost.
This was caught by the automated tests :-)
This is an attempt to fix it (there is probably a better way...)
I also added a test to show that the aforementioned commit did sole my original issue !

Nice this is even better. I've added this change manually to merge it without git problems, so I'm going to close this and push through my branch it you don't mind.

In general, don't put too much effort in text.go, it is going to be severly revised (see word breaking at https://github.com/tdewolff/canvas#planning)


How does one customise the layout?

I know in the readme it says with the open planet settings but I don't seem to have those, is that changed in a new openplanet update? A photo guide with highlights would be great! The plugin seems great but I need to customise it :) Disabled in the meantime.

What do you mean? They're in the "Dashboard" tab of the Openplanet settings dialog. What do you see there instead?

Gave it a go last night.. I'm ashamed. It was super simple, not sure what I was missing that other night, too tired I suppose. Perhaps I will make a PR later to add some instructions to the readme to other challenge people like me. Thanks for the plugin though it's super great! As is everything you do! Keep it up! (From one OSS dev to another :) )

Good to hear! I'd be curious to know what caused you not to see it, so perhaps I could fix it and make it easier to find in Openplanet itself. 🤔 But it sounds like you're not really sure either 😅


Make a release

There's a bunch of new functionality so it would be nice to have a new release.

Sure, I've got some in progress symbol and trait changes, but nothing that needs to delay a release.

Published 0.6.0


Support disabling storing message context

Describe the feature
In case whole conversation is short, it doesn't make sense to waste memory and CPU by keeping its context, it is sufficient to pass prior context manually.
For such use-cases it would be great if there was an option to disable context storing entirely.
If this is approved, I can prepare a PR.

This project is undergoing a major revamp; closing out old issues as part of the prep process.
The chatgpt package is pretty outdated at this point. I recommend that you use the openai package or the openai-fetch package instead.


Optimize Yolov8Neck

https://github.com/micromind-toolkit/micromind/blob/2ba9318feb698e157d4806225b707ab0ffb62c9f/micromind/networks/yolo.py#L366
Change all C2f blocks with XiConv (gamma=1), or every convolution inside the C2f with a XiConv (gamma = 3,4) with the same kernel and settings as the original.

Solved in https://github.com/micromind-toolkit/micromind/commit/e9af6c522cdd3fa33523d4b57fe2211eb5c455e8


[BUG] v2prov certificate rotation does not follow correct order of operations

Rancher Server Setup

Rancher version: release/v2.9
Installation option (Docker install/Helm Chart): dev

Information about the Cluster

Kubernetes version: v1.27+
Cluster Type (Local/Downstream): rke2 or k3s

User Information
n/a
Describe the bug
When performing certificate rotation steps, Rancher does not follow the documented steps to perform certificate rotation
To Reproduce
Initiate certificate rotation via UI or by incrementing Spec.RKEConfig.RotateCertificates.Generation on the Cluster object
Result

Rancher v2prov performs certificate rotation and restarts on the nodes in an apparently random order.
Rancher v2prov rotates the certificate files while the rke2 or k3s service is running, instead of stopping it first, rotating certificates, and then restarting, as described in the documentation.

Expected Result

Rancher v2prov should rotate certificates on server nodes first (etcd, then control-plane), then on agent nodes.
Rancher v2prov should stop the service, rotate certificates, then start it again.

Screenshots
Additional context

v2prov tests also use an unsupported non-HA configuration of 1-etcd, 1-controlplane, 1-agent, which combined with the apparently random order of node selection, can cause tests to take much longer.
        Jul 05 16:44:00 test-node-sknhb systemd[1]: Starting Rancher Kubernetes Engine v2 (server)...

        Jul 05 16:44:00 test-node-2z9lc rke2[379]: time="2024-07-05T16:44:00Z" level=error msg="Remotedialer proxy error; reconecting..." error="websocket: close 1006 (abnormal closure): unexpected EOF" url="wss://<IP_ADDRESS>:9345/v1-rke2/connect"
        Jul 05 16:44:00 test-node-2z9lc rke2[379]: time="2024-07-05T16:44:00Z" level=info msg="Closing 6 connections to load balancer server <IP_ADDRESS>:6443"
        Jul 05 16:44:01 test-node-2z9lc rke2[379]: time="2024-07-05T16:44:01Z" level=info msg="Connecting to proxy" url="wss://<IP_ADDRESS>:9345/v1-rke2/connect"
        Jul 05 16:44:01 test-node-2z9lc rke2[379]: time="2024-07-05T16:44:01Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="dial tcp <IP_ADDRESS>:9345: connect: connection refused"

        Jul 05 16:44:08 test-node-2z9lc rke2[379]: time="2024-07-05T16:44:08Z" level=error msg="Remotedialer proxy error; reconecting..." error="dial tcp <IP_ADDRESS>:9345: connect: connection refused" url="wss://<IP_ADDRESS>:9345/v1-rke2/connect"
        Jul 05 16:44:08 test-node-2z9lc rke2[379]: panic: runtime error: index out of range [2] with length 2
        Jul 05 16:44:08 test-node-2z9lc rke2[379]: goroutine 3203 [running]:
        Jul 05 16:44:08 test-node-2z9lc rke2[379]: github.com/k3s-io/k3s/pkg/agent/loadbalancer.(*LoadBalancer).nextServer(0xc0009ee000, {0xc000a92350?, 0xc000a92350?})
        Jul 05 16:44:08 test-node-2z9lc rke2[379]:         /go/pkg/mod/github.com/k3s-io/k3s@v1.28.10-0.20240517003114-1c33ee685998/pkg/agent/loadbalancer/servers.go:131 +0x2c5
        Jul 05 16:44:08 test-node-2z9lc rke2[379]: github.com/k3s-io/k3s/pkg/agent/loadbalancer.(*LoadBalancer).dialContext(0xc0009ee000, {0x46a46a8, 0xc00046ee00?}, {0x3e1b300, 0x3}, {0x0?, 0x2540be400?})
        Jul 05 16:44:08 test-node-2z9lc rke2[379]:         /go/pkg/mod/github.com/k3s-io/k3s@v1.28.10-0.20240517003114-1c33ee685998/pkg/agent/loadbalancer/loadbalancer.go:176 +0x2f3
        Jul 05 16:44:08 test-node-2z9lc rke2[379]: inet.af/tcpproxy.(*DialProxy).HandleConn(0xc00528e100, {0x46b7e10, 0xc0012dab88})
        Jul 05 16:44:08 test-node-2z9lc rke2[379]:         /go/pkg/mod/inet.af/tcpproxy@v0.0.0-20200125044825-b6bb9b5b8252/tcpproxy.go:359 +0xff
        Jul 05 16:44:08 test-node-2z9lc rke2[379]: inet.af/tcpproxy.(*Proxy).serveConn(0xc0000a3760?, {0x46b7e10?, 0xc0012dab88}, {0xc0052865a0, 0x1, 0xc000562960?})
        Jul 05 16:44:08 test-node-2z9lc rke2[379]:         /go/pkg/mod/inet.af/tcpproxy@v0.0.0-20200125044825-b6bb9b5b8252/tcpproxy.go:239 +0x30b
        Jul 05 16:44:08 test-node-2z9lc rke2[379]: created by inet.af/tcpproxy.(*Proxy).serveListener in goroutine 394
        Jul 05 16:44:08 test-node-2z9lc rke2[379]:         /go/pkg/mod/inet.af/tcpproxy@v0.0.0-20200125044825-b6bb9b5b8252/tcpproxy.go:221 +0x45
        Jul 05 16:44:08 test-node-2z9lc systemd[1]: rke2-server.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
        Jul 05 16:44:09 test-node-2z9lc systemd[1]: rke2-server.service: Failed with result 'exit-code'.

        Jul 05 16:44:20 test-node-sknhb rke2[14504]: time="2024-07-05T16:44:20Z" level=info msg="Static pod cleanup completed successfully"
        Jul 05 16:44:20 test-node-sknhb rke2[14504]: time="2024-07-05T16:44:20Z" level=info msg="Starting rke2 v1.28.10+rke2r1 (b0d0d687d98f4fa015e7b30aaf2807b50edcc5d7)"
        Jul 05 16:44:20 test-node-sknhb rke2[14504]: time="2024-07-05T16:44:20Z" level=fatal msg="starting kubernetes: preparing server: failed to get CA certs: Get \"https://<IP_ADDRESS>:9345/cacerts\": dial tcp <IP_ADDRESS>:9345: connect: connection refused"

This particular crash has should not occur if the proper order of etcd -> controlplane -> agent is followed, and has also been fixed in:

https://github.com/k3s-io/k3s/pull/10318

It seems the business logic for certificate rotation was added around the same time the docs for RKE2/K3s certificate rotation were written, and from what I can tell, it seems the v2prov engineer implementing this change was given outdated information regarding the expected procedure from the K3s/RKE2 side.

v2prov tests also use an unsupported non-HA configuration of 1-etcd, 1-controlplane, 1-agent, which combined with the apparently random order of node selection, can cause tests to take much longer.

This should be a supported configuration on the RKE2 side. It is a supported (albeit cautioned due to lack of redundancy) configuration on the Rancher side. @snasovich can we look into this to ensure the RKE2 team considers this configuration permutation part of their support matrix?
I'll experiment with changing certificate rotation logic in a manner to reflect the documentation per: https://docs.rke2.io/security/certificates#rotating-client-and-server-certificates-manually

I would defer to the QA team on what we test/support, but I would generally expect something along the lines of:

1 etcd+cp, 1 worker
3 etcd+cp, N workers
3 etcd, 2 cp, N workers

We actually do validate the exact case mentioned: 1 etcd, 1 cp, 1 worker. This is the standalone test we do each release cycle, and make the assumption that if that works, the other cases should follow.

OK, thats good to know. I certainly wouldn't recommend anyone use that in production if they were looking for HA, but I agree that it should at least be functional.
@rancher-max when QA validates cert rotation, what procedure do they follow for the 1/1/1 cluster?

We do etcd-only, then cp-only, then worker always

Pushed out v2.9-Next1 due to QA capacity

Ticket #46034 - Test Results - :x: RE-OPENED
Verified on Rancher v2.9-4eb37b98a2e548500ed9e3f57922c0d598ecb46b-head:

Scenario
Test Case
Result

1.
Execute cert-rotation 3 times on downstream RKE2 w/ 3 etcd, 2 cp, 3 wkr
✅

2 .
Execute cert-rotation 3 times on downstream RKE2 w/ 1 etcd, 1 cp, 1 wkr
✅

3.
Execute cert-rotation 3 times on downstream K3s w/ 3 etcd, 2 cp, 3 wkr
:x:

4 .
Execute cert-rotation 3 times on downstream K3s w/ 1 etcd, 1 cp, 1 wkr
✅

Scenario 1 - ✅

Fresh install of Rancher v2.9-head
Provision a downstream RKE2 cluster w/ k8s v1.30.4+rke2r1 - [3 etcd, 2 cp, 3 wkr]
Initiate cert-rotation + monitor logs
Verified - cert-rotation executed etcd pool => cp pool => wkr pool, and nodes were brought back up etcd pool => cp pool => wkr pool
Initiate cert-rotation 2 more times + monitor logs
Verified - cert-rotation order as expected each time; 3/3 pass

Scenario 2 - ✅

Fresh install of Rancher v2.9-head
Provision a downstream RKE2 cluster w/ k8s v1.30.4+rke2r1 - [1 etcd, 1 cp, 1 wkr]
Initiate cert-rotation + monitor logs
Verified - cert-rotation executed etcd pool => cp pool => wkr pool, and nodes were brought back up etcd pool => cp pool => wkr pool
Initiate cert-rotation 2 more times + monitor logs
Verified - cert-rotation order as expected each time; 3/3 pass

Scenario 3 - :x:

Fresh install of Rancher v2.9-head
Provision a downstream K3s cluster w/ k8s v1.30.4+k3s1 - [3 etcd, 2 cp, 3 wkr]
Initiate cert-rotation + monitor logs
Veri-FAILED - cert-rotation is executed in expected order etcd pool => cp pool => wkr pool, and nodes were brought back up etcd pool => cp pool => wkr pool, as expected, however, once the worker pool came back up, the cluster flashed active momentarily, before entering an updating state, with the following error:

Failing etcd machine(s) jkeslarrr-k3s-ha3-pool1-8jqcc-flpvw,jkeslarrr-k3s-ha3-pool1-8jqcc-jnxbb

Screenshots:
Cluster Mangement

Cluster Details

Rancher logs:
2024/09/05 21:56:47 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool2-hntkb-mcg8c] certificate rotation
2024/09/05 21:56:48 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool2-hntkb-mcg8c] certificate rotation
2024/09/05 21:56:48 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool2-hntkb-mcg8c] certificate rotation
2024/09/05 21:56:52 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: starting [jkeslarrr-k3s-ha3-pool3-qrrzq-9pg2w] certificate rotation
2024/09/05 21:56:52 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool3-qrrzq-9pg2w] certificate rotation
2024/09/05 21:56:52 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool3-qrrzq-9pg2w] certificate rotation
2024/09/05 21:56:52 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool3-qrrzq-9pg2w] certificate rotation
2024/09/05 21:56:52 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool3-qrrzq-9pg2w] certificate rotation
2024/09/05 21:56:53 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool3-qrrzq-9pg2w] certificate rotation
2024/09/05 21:56:55 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: starting [jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4] certificate rotation
2024/09/05 21:56:55 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4] certificate rotation
2024/09/05 21:56:56 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4] certificate rotation
2024/09/05 21:56:56 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4] certificate rotation
2024/09/05 21:56:56 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4] certificate rotation
2024/09/05 21:56:56 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4] certificate rotation
2024/09/05 21:56:56 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4] certificate rotation
2024/09/05 21:56:56 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4] certificate rotation
2024/09/05 21:56:59 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: starting [jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w] certificate rotation
2024/09/05 21:56:59 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w] certificate rotation
2024/09/05 21:56:59 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w] certificate rotation
2024/09/05 21:57:00 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w] certificate rotation
W0905 21:57:02.471446      44 reflector.go:547] pkg/mod/k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232: failed to list *v1.LimitRange: starting
I0905 21:57:02.471607      44 trace.go:236] Trace[62180307]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232 (05-Sep-2024 21:56:47.459) (total time: 15011ms):
Trace[62180307]: ---"Objects listed" error:starting 15011ms (21:57:02.471)
Trace[62180307]: [15.011713607s] [15.011713607s] END
E0905 21:57:02.471646      44 reflector.go:150] pkg/mod/k8s.io/client-go@v0.30.1/tools/cache/reflector.go:232: Failed to watch *v1.LimitRange: failed to list *v1.LimitRange: starting
2024/09/05 21:57:03 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: waiting for [jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w] certificate rotation
2024/09/05 21:57:03 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: certificate rotation done
2024/09/05 21:57:03 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring bootstrap node(s) jkeslarrr-k3s-ha3-pool1-8jqcc-5q5nc: waiting for plan to be applied
2024/09/05 21:57:03 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring bootstrap node(s) jkeslarrr-k3s-ha3-pool1-8jqcc-5q5nc: waiting for plan to be applied
2024/09/05 21:57:03 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring bootstrap node(s) jkeslarrr-k3s-ha3-pool1-8jqcc-5q5nc: waiting for plan to be applied
2024/09/05 21:57:03 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring bootstrap node(s) jkeslarrr-k3s-ha3-pool1-8jqcc-5q5nc: waiting for plan to be applied
2024/09/05 21:57:04 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring bootstrap node(s) jkeslarrr-k3s-ha3-pool1-8jqcc-5q5nc: waiting for plan to be applied
2024/09/05 21:57:08 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: jkeslarrr-k3s-ha3-pool1-8jqcc-5q5nc
2024/09/05 21:57:09 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring etcd node(s) jkeslarrr-k3s-ha3-pool1-8jqcc-flpvw,jkeslarrr-k3s-ha3-pool1-8jqcc-jnxbb
2024/09/05 21:57:09 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring etcd node(s) jkeslarrr-k3s-ha3-pool1-8jqcc-flpvw,jkeslarrr-k3s-ha3-pool1-8jqcc-jnxbb
2024/09/05 21:57:09 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring etcd node(s) jkeslarrr-k3s-ha3-pool1-8jqcc-flpvw,jkeslarrr-k3s-ha3-pool1-8jqcc-jnxbb
2024/09/05 21:57:10 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring etcd node(s) jkeslarrr-k3s-ha3-pool1-8jqcc-flpvw,jkeslarrr-k3s-ha3-pool1-8jqcc-jnxbb
2024/09/05 21:57:13 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring etcd node(s) jkeslarrr-k3s-ha3-pool1-8jqcc-jnxbb: waiting for plan to be applied
2024/09/05 21:57:13 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring etcd node(s) jkeslarrr-k3s-ha3-pool1-8jqcc-jnxbb: waiting for plan to be applied
2024/09/05 21:57:13 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring etcd node(s) jkeslarrr-k3s-ha3-pool1-8jqcc-jnxbb: waiting for plan to be applied
2024/09/05 21:57:18 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: jkeslarrr-k3s-ha3-pool1-8jqcc-flpvw,jkeslarrr-k3s-ha3-pool1-8jqcc-jnxbb
2024/09/05 21:57:18 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring control plane node(s) jkeslarrr-k3s-ha3-pool2-hntkb-489c8,jkeslarrr-k3s-ha3-pool2-hntkb-mcg8c
2024/09/05 21:57:18 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring control plane node(s) jkeslarrr-k3s-ha3-pool2-hntkb-489c8,jkeslarrr-k3s-ha3-pool2-hntkb-mcg8c
2024/09/05 21:57:18 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring control plane node(s) jkeslarrr-k3s-ha3-pool2-hntkb-489c8,jkeslarrr-k3s-ha3-pool2-hntkb-mcg8c
2024/09/05 21:57:18 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring control plane node(s) jkeslarrr-k3s-ha3-pool2-hntkb-489c8,jkeslarrr-k3s-ha3-pool2-hntkb-mcg8c
2024/09/05 21:57:25 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring control plane node(s) jkeslarrr-k3s-ha3-pool2-hntkb-mcg8c: waiting for plan to be applied
2024/09/05 21:57:25 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring control plane node(s) jkeslarrr-k3s-ha3-pool2-hntkb-mcg8c: waiting for plan to be applied
2024/09/05 21:57:25 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring control plane node(s) jkeslarrr-k3s-ha3-pool2-hntkb-mcg8c: waiting for plan to be applied
2024/09/05 21:57:25 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring control plane node(s) jkeslarrr-k3s-ha3-pool2-hntkb-mcg8c: waiting for plan to be applied
2024/09/05 21:57:26 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring control plane node(s) jkeslarrr-k3s-ha3-pool2-hntkb-mcg8c: waiting for plan to be applied
2024/09/05 21:57:26 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring control plane node(s) jkeslarrr-k3s-ha3-pool2-hntkb-mcg8c: waiting for plan to be applied
2024/09/05 21:57:26 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring control plane node(s) jkeslarrr-k3s-ha3-pool2-hntkb-mcg8c: waiting for plan to be applied
2024/09/05 21:57:27 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring control plane node(s) jkeslarrr-k3s-ha3-pool2-hntkb-mcg8c: waiting for plan to be applied
2024/09/05 21:57:30 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring control plane node(s) jkeslarrr-k3s-ha3-pool2-hntkb-mcg8c: waiting for plan to be applied
2024/09/05 21:57:30 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: jkeslarrr-k3s-ha3-pool2-hntkb-489c8,jkeslarrr-k3s-ha3-pool2-hntkb-mcg8c
2024/09/05 21:57:30 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring worker node(s) jkeslarrr-k3s-ha3-pool3-qrrzq-9pg2w,jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4,jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w
2024/09/05 21:57:30 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring worker node(s) jkeslarrr-k3s-ha3-pool3-qrrzq-9pg2w,jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4,jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w
2024/09/05 21:57:31 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring worker node(s) jkeslarrr-k3s-ha3-pool3-qrrzq-9pg2w,jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4,jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w
2024/09/05 21:57:37 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring worker node(s) jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4,jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w
2024/09/05 21:57:37 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring worker node(s) jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4,jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w
2024/09/05 21:57:37 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring worker node(s) jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4,jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w
2024/09/05 21:57:41 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring worker node(s) jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4,jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w
2024/09/05 21:57:41 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring worker node(s) jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4,jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w
2024/09/05 21:57:41 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring worker node(s) jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4,jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w
2024/09/05 21:57:41 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring worker node(s) jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4,jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w
2024/09/05 21:57:45 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring worker node(s) jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w: waiting for plan to be applied
2024/09/05 21:57:45 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring worker node(s) jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w: waiting for plan to be applied
2024/09/05 21:57:45 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring worker node(s) jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w: waiting for plan to be applied
2024/09/05 21:57:45 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring worker node(s) jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w: waiting for plan to be applied
2024/09/05 21:57:49 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: configuring worker node(s) jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w: waiting for plan to be applied
2024/09/05 21:57:50 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: jkeslarrr-k3s-ha3-pool3-qrrzq-9pg2w,jkeslarrr-k3s-ha3-pool3-qrrzq-ks8w4,jkeslarrr-k3s-ha3-pool3-qrrzq-tlm4w
2024/09/05 21:57:50 [ERROR] error syncing 'auth-user-info-resync-cron': handler mgmt-auth-settings-controller: error refreshing cron time: refresh cron time must be provided, requeuing
2024/09/05 21:57:50 [ERROR] error syncing 'azure-group-cache-size': handler mgmt-auth-settings-controller: error updating group cache size with azure: azure-group-cache-size must be provided, requeuing
2024/09/05 21:57:55 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: failing etcd machine(s) jkeslarrr-k3s-ha3-pool1-8jqcc-flpvw,jkeslarrr-k3s-ha3-pool1-8jqcc-jnxbb
2024/09/05 21:57:55 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: failing etcd machine(s) jkeslarrr-k3s-ha3-pool1-8jqcc-flpvw,jkeslarrr-k3s-ha3-pool1-8jqcc-jnxbb
2024/09/05 21:57:56 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: failing etcd machine(s) jkeslarrr-k3s-ha3-pool1-8jqcc-flpvw,jkeslarrr-k3s-ha3-pool1-8jqcc-jnxbb
2024/09/05 21:58:00 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: failing etcd machine(s) jkeslarrr-k3s-ha3-pool1-8jqcc-flpvw,jkeslarrr-k3s-ha3-pool1-8jqcc-jnxbb
2024/09/05 21:58:00 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: failing etcd machine(s) jkeslarrr-k3s-ha3-pool1-8jqcc-flpvw,jkeslarrr-k3s-ha3-pool1-8jqcc-jnxbb
2024/09/05 21:58:05 [INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/05 21:58:05 [INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/05 21:58:05 [INFO] Handling backend connection request [c-m-6cd5dtzx]
2024/09/05 21:58:05 [INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF
2024/09/05 21:58:05 [ERROR] Failed to handle tunnel request from remote address <IP_ADDRESS>:32964: response 401: failed authentication
2024/09/05 21:58:05 [INFO] Handling backend connection request [stv-cluster-c-m-6cd5dtzx]
2024/09/05 21:58:09 [ERROR] Failed to handle tunnel request from remote address <IP_ADDRESS>:48106: response 401: failed authentication
2024/09/05 21:58:09 [INFO] Handling backend connection request [stv-cluster-c-m-6cd5dtzx]
2024/09/05 21:58:10 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: failing etcd machine(s) jkeslarrr-k3s-ha3-pool1-8jqcc-flpvw,jkeslarrr-k3s-ha3-pool1-8jqcc-jnxbb
2024/09/05 21:58:10 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: failing etcd machine(s) jkeslarrr-k3s-ha3-pool1-8jqcc-flpvw,jkeslarrr-k3s-ha3-pool1-8jqcc-jnxbb
2024/09/05 21:58:11 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: failing etcd machine(s) jkeslarrr-k3s-ha3-pool1-8jqcc-flpvw,jkeslarrr-k3s-ha3-pool1-8jqcc-jnxbb
2024/09/05 21:58:11 [INFO] [planner] rkecluster fleet-default/jkeslarrr-k3s-ha3: failing etcd machine(s) jkeslarrr-k3s-ha3-pool1-8jqcc-flpvw,jkeslarrr-k3s-ha3-pool1-8jqcc-jnxbb

Additional Context:
I attempted this scenario 3 times, and all lead to the same results.  consistently reproducible on v2.9-head.
In an effort to further troubleshoot, I attempted this same scenario 3 times on v2.9.1 and the results were as follows:
Attempt 1 - ✅
Attempt 2 - :x: Hit issue
Attempt 3 - ✅ resolved issue w/ attempt 2 and cluster came back up active and stable

Scenario 4 - ✅

Fresh install of Rancher v2.9-head
Provision a downstream K3s cluster w/ k8s v1.30.4+k3s1 - [1 etcd, 1 cp, 1 wkr]
Initiate cert-rotation + monitor logs
Verified - cert-rotation executed etcd pool => cp pool => wkr pool, and nodes were brought back up etcd pool => cp pool => wkr pool
Initiate cert-rotation 2 more times + monitor logs
Verified - cert-rotation order as expected each time; 3/3 pass


added expires_date_attrs

This Gem receipt:
"expires_date": "2016-01-16 05:51:35 Etc/GMT",
"expires_date_ms": "1452923495000",
"expires_date_pst": "2016-01-15 21:51:35 America/Los_Angeles",

But, real receipt:
"expires_date_formatted": "2016-01-16 05:51:35 Etc/GMT",
"expires_date": "1452923495000",
"expires_date_formatted_pst": "2016-01-15 21:51:35 America/Los_Angeles",

So, I added expires_date_attrs.

Hi @yoshitetsu, thank's for your contribution, although I'm afraid I can't merge this.
The expires date properties you are referring to is only present on a transactionReceipt, this gem only mocks grand unified receipts from the appStoreReceiptUrl method.

@marcgreenstock
OK! I'll close this PR.


Added Huey support

Huey support added for scheduling and managing automated tasks
https://github.com/coleifer/huey

-requires huey, gevent,


[AIRFLOW-1659] Fix invalid obj attribute bug in file_task_handler.py

Dear Airflow maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[ ] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-1659

Description

[ ] Here are some details about my PR, including screenshots of any UI changes:
I believe there's a bug in the FileTaskHandler class, self.timeout is not a valid attribute, should revert back to using local var timeout.

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

cc: @Fokko @criccomini

Codecov Report

Merging #2645 into master will not change coverage.
The diff coverage is 0%.

@@           Coverage Diff           @@
##           master    #2645   +/-   ##
=======================================
  Coverage   71.75%   71.75%
=======================================
  Files         152      152
  Lines       11749    11749
=======================================
  Hits         8431     8431
  Misses       3318     3318

Impacted Files
Coverage Δ

airflow/utils/log/file_task_handler.py
75.9% <0%> (ø)
:arrow_up:

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 b3e985a...0e3a59f. Read the comment docs.

LGTM

Thanks


Document DDoS protection setup

DDoS protection service is enabled for our cluster in Radix.
This should be stated in the Archtecture contract as well as the Runbook.
Tasks

[ ]  Add note about DDoS protection in archtecture contract
[ ] Add note about DDoS protection in Runbook for energyvision

Relates to #1550

We already have this documented in the runbook. Under the "Network security" subitem. @nilsml can we close this?

Agree, we can close this


Add test to ensure plugin plays nicely with others

i.e. plays nicely with other Creek plugins that also register the creek extension.
Reviewer checklist

[ ] Ensure relevant issues are linked (description should include text like "Fixes #")
[ ] Ensure any appropriate documentation has been added or amended

Coverage increased (+0.6%) to 98.315% when pulling eeff63dff27effbff7fbe2ede1d2f94a29a8ab46 on play_nicely into d8177ba7e62847c417c4ab522e57017bad677c61 on main.


Just a very small note of "original.jpeg" binary file

https://github.com/lucacasonato/fresh/blob/main/www/static/illustration/original.jpeg
For now, the image is used on the front page and it's a .jpeg...!
This means when the user agent uses some weird background-color, it's kind look weird, too...!
I just one to add a // TODO:  somewhere, so...!
Please todo this...?
Great project, btw...!
Screenshot from my mac using the plash app

I am happy to take a PR that forces the page background color to white.

I am happy to take a PR that forces the page background color to white.

That sounds like a bad idea for people that rely on dark themes for accessibility reasons. Why not just make it a png/webp and make the bg transparent?

I am happy to take a PR that forces the page background color to white.

That sounds like a bad idea for people that rely on dark themes for accessibility reasons. Why not just make it a png/webp and make the bg transparent?

This really sounds better, can you take the PR...?


use larger read buffers

I was mildly surprised Moonfire NVR's CPU usage didn't go down noticeably when switching from ffmpeg to retina. There's not much CPU used in retina's code itself but I think it's making too many syscalls because it's using buffers that have too little available space. The histogram below counts reads that filled the buffer (and thus will require a follow-up syscall) bucketed by the available space in the buffer when the read started:
[slamb@nuc ~]$ cat recvsize.bt
#!/usr/bin/bpftrace

tracepoint:syscalls:sys_enter_recvfrom /pid == (uint64) $1/ {
    @sizes[tid] = (int64) args->size;
}

tracepoint:syscalls:sys_exit_recvfrom /pid == (uint64) $1/ {
    if (@sizes[tid] > 0 && args->ret == @sizes[tid]) {
        @full_read_sizes = hist(@sizes[tid]);
    }
    delete(@sizes[tid]);
}

interval:s:60 { exit() }
[slamb@nuc ~]$ sudo ./recvsize.bt "$(pidof moonfire-nvr)"
Attaching 3 probes...

@full_read_sizes:
[1]                    1 |                                                    |
[2, 4)                 0 |                                                    |
[4, 8)                 6 |                                                    |
[8, 16)               16 |                                                    |
[16, 32)              47 |                                                    |
[32, 64)             125 |                                                    |
[64, 128)            267 |@                                                   |
[128, 256)           531 |@@@                                                 |
[256, 512)          1119 |@@@@@@                                              |
[512, 1K)           8319 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@|
[1K, 2K)            3132 |@@@@@@@@@@@@@@@@@@@                                 |
[2K, 4K)             149 |                                                    |
[4K, 8K)              42 |                                                    |

That's ~230 times per second the buffer filled (across 12 video streams); in most cases it was reading into a buffer with less than 1 KiB available.
I'm letting tokio_util::codec::Framed do the buffer management now, but I think I should do it myself instead. Or at least call reserve(4096) before returning from Codec::decode (regardless of whether it was able to pull a full message).

Actually, that's a lot better than ffmpeg already. /shruggie With ffmpeg for a minute, there are ~8000 times per second the buffer filled.
$ sudo ./recvsize.bt "$(pidof moonfire-nvr)"
Attaching 3 probes...

@full_read_sizes:
[1]               161433 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@|
[2, 4)            159932 |@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ |
[4, 8)                59 |                                                    |
[8, 16)            12876 |@@@@                                                |
[16, 32)            5692 |@                                                   |
[32, 64)           27575 |@@@@@@@@                                            |
[64, 128)          11172 |@@@                                                 |
[128, 256)          6422 |@@                                                  |
[256, 512)          7465 |@@                                                  |
[512, 1K)          10387 |@@@                                                 |
[1K, 2K)           78285 |@@@@@@@@@@@@@@@@@@@@@@@@@                           |

Looking at actual CPU rates (by diffing /sys/fs/cgroup/cpu/system.slice/moonfire-nvr.service/cpuacct.usage):

config
cpu usage (% of one core)

ffmpeg
16%

retina, multi-threaded tokio runtime, 4 threads
21%

retina, multi-threaded tokio runtime, 1 thread
14%

retina, current thread tokio runtime
12%

tl;dr version of investigating where that CPU is going: has more to do Moonfire NVR's current tokio and thread setup than with retina.
flamegraph says tokio wastes a bit of CPU on sched_yield here; it's less with fewer threads, and it goes away with the current-thread runtime. I think this sched_yield loop is silly and maybe will eventually convince tokio folks of that.
There's also a fair bit of thread handoffs because currently I'm using retina in the tokio threads and handing off to a thread per stream every frame to write data. Eventually I'll have one writer thread per sample file directory (2 instead of 12 in this deployment) and only write once per GOP (every 1 or 2 seconds instead of every 1/10th to 1/30th of a second), which will reduce memory.


FAILED TO GENERATE PAYLOAD

Checking Dependencies...
[+] All Dependencies are Installed on this system ;)
[*] Generating Please wait for a while...
[*] Encrypting Source Codes...
[+] Operation Completed Successfully!
0009:err:module:__wine_process_init failed to load L"C:\ProgramFilesx86\Python37-32\Lib\venv\scripts\nt\pyinstaller", error c000012f
[*] Deleting Junk Files...
rm: 'build/' silinemedi: Böyle bir dosya ya da dizin yok
rm: 'deneme22.spec' silinemedi: Böyle bir dosya ya da dizin yok
[+] Junk Files Removed Successfully!
[!] Failed To Generate Your Payload :(, Please Try Again!
[:D] Please Contact us on https://github.com/PushpenderIndia/technowlogger
Im tired of this. please help

Type: pyinstaller in your command prompt, if you are getting error, then you have to install it, this error means that pyinstaller is missing from your system
Use this cmd to install pyinstaller: pip install pyinstaller


Error: Error calculating min/max zoom: Bounds invalid

I am using Mapbox Studio 0.2.7. I am seeing an error, but I'm not sure how to fix it.
Repro steps

Launch Mapbox studio
Click "projects"
Create a new project
Select "Blank source"
Click "+ New layer"
Choose a geojson file that contains the following:

{
  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "geometry": {
        "type": "Polygon",
        "coordinates": [
          [
            [
              -0.004,
              -0.004
            ],
            [
              0.004,
              -0.004
            ],
            [
              0.004,
              0.004
            ],
            [
              -0.004,
              0.004
            ],
            [
              -0.004,
              -0.004
            ]
          ]
        ]
      },
      "properties": {}
    }
  ]
}

Expected: I see my feature in the source viewer.
Actual: I get the following error:

Error: Error calculating min/max zoom: Bounds invalid

I may be doing something wrong, but if this is user error, the error message is not helpful in explaining what's wrong with my data. The same data works fine when I paste it in to geojson.io.
Thanks for your help!

@NickHeiner I can replicate with the latest dev build of Mapbox Studio.
Looking into it ....

Awesome. Thanks.

@BergWerkGIS is this still replicable? Is it due to https://github.com/mapbox/mapnik-omnivore/issues/88?
Note: removed this from the v0.2.8 milestone since that release has already flown.

@springmeyer yes, due to https://github.com/mapbox/mapnik-omnivore/issues/88 but originates from sphericalmercator.
Haven't checked yet, but might have been solved by https://github.com/mapbox/node-sphericalmercator/commit/99b17908aba7863f03e60a9143e789c30408d54f?diff=split


feat: explicit names for meetecho recordings

fixes #3454

we may need to use (build on top of) the recording url endpoint for non-meetecho generated youtube videos (e.g. those for MOQ right now).


Another bunch of fixes to make dock play with pulp nicely

@twaugh Tim, can you please review?

Looks good, could squash the last three together if you like (fine if not).

Sorry, wasn't paying attention to this PR for past 2 hours.


cardano-db-sync-extended: Identity Connect Attempt Exception

Hi,
after updating to version 3.2.0 I am receiving the following error upon running docker-compose up --build -d && docker-compose logs -f
cardano-db-sync-extended_1  | [db-sync-node.Subscription:Notice:41] [2021-02-13 11:41:15.53 UTC] Identity Starting Subscription Worker, valency 1
cardano-db-sync-extended_1  | [db-sync-node.Subscription:Notice:173] [2021-02-13 11:41:15.53 UTC] Identity Connection Attempt Start, destination LocalAddress "/node-ipc/node.socket"
cardano-db-sync-extended_1  | [db-sync-node.Subscription:Error:173] [2021-02-13 11:41:15.53 UTC] Identity Connection Attempt Exception, destination LocalAddress "/node-ipc/node.socket" exception: Network.Socket.connect: <socket: 13>: does not exist (No such file or directory)
cardano-db-sync-extended_1  | [db-sync-node.ErrorPolicy:Warning:4] [2021-02-13 11:41:15.53 UTC] IP LocalAddress "/node-ipc/node.socket" ErrorPolicySuspendPeer (Just (ConnectionExceptionTrace Network.Socket.connect: <socket: 13>: does not exist (No such file or directory))) 20s 20s
cardano-db-sync-extended_1  | [db-sync-node.Subscription:Warning:41] [2021-02-13 11:41:15.56 UTC] Identity Failed to start all required subscriptions
cardano-db-sync-extended_1  | [db-sync-node.Subscription:Notice:41] [2021-02-13 11:41:16.56 UTC] Identity Restarting Subscription after 1.026282484s desired valency 1 current valency 0

The error happens for both, docker-compose.yml as well as docker-compose.dev.yml.
I am running it locally on my laptop.
Ubuntu 18.04.5 LTS
Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
8 GB RAM
Any help is appreciated.

That's expected on startup when cardano-node is still initialising and can sometimes take a minute or two. Did it resolve?

Nope, I ran it multiple times and waited 10-15 minutes. Using the docker-compose.yml file my laptop started to get unresponsive and was under high workload. Maybe the specs of my laptop are too small to facilitate the initialisation of the cardano-node.

What's your machine spec?

Specs are:
Ubuntu 18.04.5 LTS
Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
4 Cores
8 GB RAM
500 GB SSD, 55% occupied.
Any other specs that are of interest?

Moving to 3.2.0 introduces a new version of cardano-db-sync that requires the local state to be rebuilt.
https://github.com/input-output-hk/cardano-graphql/wiki/Docker#rebuild-cardano-db
Was this performed?
`

I did this when moving to version 3.0.0, but not for 3.2.0. I will try to see if this helps.

Rebuilding with cgql docker rebuild-service did not help. I now managed to get it fixed by rebuilding the whole project and downloading the whole blockchain again. The error still pops up for the first few minutes on startup, like you mentioned before, but afterwards it is fine.


rng-tools

baseado no comando do repositorio base ;)

I don't feel like it's necessary. I'm trying to keep the script size under control, mainly for ease of reading and understanding it. If ain't a problem I have dealt with, I rather not try to solve it. Entropy hasn't been one.


Regression: webpack watch mode no longer works

Type of issue

Regression (a behavior that used to work and stopped working in a new release)

The issue refers to the:

example nitro project (project-nitro)
example nitro project with twig engine (project-nitro-twig)
example nitro project with typescript jsCompiler (project-nitro-typescript)

Environment
Node.js v12.16.3
win32 10.0.18363
Nitro Version 5.2.9 / 5.3.0

Expected behavior
Webpack recompilation and hot reloading for css an js works in dev mode
Current behavior
Webpack recompilation and hot reloading for css and js does not work in dev mode (npm start)

It turns out that the problem is not directly caused by a directly used package.
Works with package-lock.json on the 5.2.9 release date, currently does not work when reinstalling.

Workaround published in 5.3.1

Solution only works in monorepo

In Nitro version 5.3.3 the webpack watcher works again in your project.
Without an update you can also simply add the package "watchpack" in version 1.6.1 as devDependency: "watchpack": "1.6.1"


Fix source directive in podfile (S3TransferManager-Sample Swift)

The specs repo at ssh://git.amazon.com:2222/pkg/AWSCocoaPodsSpecs is not publicly accessible.
This appears to be the only Podfile that was affected.

Thank you for the pull request!


dry up transactor try catch

What does this PR do and why?
creating new PR pointed at main
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the changes.
Acceptance checklist

[ ] I have evaluated the Approval Guidelines for this PR.
[ ] I have tested this PR in all supported browsers.
[ ] I have tested this PR in dark mode and light mode (if applicable).

Current dependencies on/for this PR:

main

PR #1755   👈

This comment was auto-generated by Graphite.


[MODCPCT-69]Create an upgrade process for existing Z39.50 target prof…

https://issues.folio.org/browse/MODCPCT-69
Update library-of-congress.json and  oclc-worldcat.json - reflect the schema changes described in MODCPCT-71, set create/update jobprofileId as default and specify them in the list for allowed jobProfiles
Add migration script for existing profiles: reflect the same changes as above
change createJobProfileId --> defaultCreateJobProfileId
change updateJobProfileId --> defaultUpdateJobProfileId
add array for createJobProfileIds
add array for updateJobProfileIds

Hi @KyryloShulzhenko, we decided to make it a non-breaking change, please reflect the changes described in https://issues.folio.org/browse/MODCPCT-71 in this PR. Thank you!


build(sw.js): service worker not generating locally for testing

Environment:
Local Development
Steps to Recreate:
Run npm run build and the results the expected results will be a sw.js file and workblox folder generating under the compiled www folder.
When running any other configured commands, it removes both the sw.js file and workblox folder from the www. In addition to, running any command outside of npm run build will not generate either of these.
Expected Result:
These files should not be removed and instead be generated under the www folder when testing locally.

Closing issue.


how to replace the training process of CNN(resnet101) with a pretrained one ?

Hi @OmarMohammed88
you can change this line in the tutorial notebook to your pretrained model.
self.backbone = resnet101()

thank u very much ..
Another question, what is the type of decoding did u use, is it Beam search or greedy or best path decoding?

I used the normal one which is greedy

is it possible to change the algorithm if so, how can I assess that component?

You have to write your own beam search function using the probabilities of output vocab.


Support for CNI-Genie or Multus CNI Plugins

Do we support CNI-Genie or Multus CNI plugins today?

Yes we do, in few days I will create step by step guide for it.

And I assume that means support of multiple interfaces and multiple ip's?

@sheetaljoshi yes it does, we do have support for CNI-Genie, but you need patched / improved version from http://github.com/mirantis/CNI-Genie because not all patches landed in upstream yet.
In theory you're allowed to use any CNI plugins, but we checked calico, flannel, sriov, contrail.
I'm pretty sure that @lukaszo can provide more details if you need them all, or just wait for docs that are landing soon.

@pigmej @lukaszo I am trying to run with CNI Genie, with canal and weave-weave but virtlet-ds is stuck at PoDInitializing with master libvirt-ds.yaml and at Init stage with wget https://github.com/Mirantis/virtlet/releases/download/v0.9.4/virtlet-ds.yaml. Any change if we have documents published yet?

@sheetaljoshi I apologise for a late response. I've created document with an example describing how to use CNI-Genie with Virtlet  https://github.com/Mirantis/virtlet/blob/master/docs/multiple-interfaces.md I hope it helps

No, only CNI-Genie is supported. Multus may or may not work. We've never tried it.

Thank you.
How does virlet know about multiple interfaces and IP addresses? In our experimentation, we are using flannel as first CNI and OVN as next CNI.  OVN CNI is creating multiple interfaces by creating multiple veth pairs and adding appropriate IP addresses.  In case of docker based PODS, we see that PODS showing up all interfaces with right IP addresses - That is flannel interface and OVN interfaces are shown properly.
When we bring up VM using virtlet, it is showing only interface related to flannel. It is not showing interfaces created by OVN.  Based on some debugging, we see that OVN CNI is getting control from Multus and we also ensured that it is indeed adding veth pairs successfully.
We thought that virtlet figures out the number of interfaces and corresponding IP addresses by looking at the interfaces in the network namespace, create as many number of tap interfaces before VM is brought up.   Please let us know how virtlet recognizes the interfaces and any other points you can think of for us to debug this further.

Virtlet uses information returned from CNI plugin in form of https://github.com/containernetworking/cni/blob/master/SPEC.md#result which should contain a list of interfaces with data like ip addresses and routes to be set through them.
So probably the only information returned there (by multus?) was info about interface created/configure by flannel. This means that thing used to multiplex calls to different CNI plugins, need to be updated to fulfill CNI specification (because looks like there is some assumptions about how it's used by docksershim, while rest of it is ignored).
Maybe you should try instead of Multus CNI-Genie, which know how to properly use chain of cni plugins, collects all results and merges them before returning to CRI compliant runtime, which is calling it?

I can already see that multus is not joining the results https://github.com/intel/multus-cni/blob/master/multus/multus.go#L258

Thank you. So, it appears to be Multus issue.

It shouldn't be called by kubelet, only virtlet. Can you attach full virtlet log? From virtlet container in virtlet pod.

If routes/dns settings will be visible in cni result - virtlet will pass them to vm for sure, in two ways - using cloud init network configuration passed inside of cdrom image and using dhcp server.
One note - dhcp server option is unavailable for sr-iov devices.

Okay.  Is there any configuration to select one of the options. We would like DHCP Server to provide both routes and DNS server settings along with IP address.?

DHCP is serving ip/dns data always for veth based devices created by cni plugins so your requirement should be fulfilled already.
cloud init based network configuration is also always prepared (user can select a data source type - nocloud, or config drive, both are similar and based on cdrom image).

Yes we do, in few days I will create step by step guide for it.

The guide site is 404, could you please tell me the new address of the guide to setup sriov?

PTAL on https://docs.virtlet.cloud/101/network/#multiple-interfaces

@saddepalli Hi, By using multus cni, is the sriov device plugin and sriov cni work correctly with virtlet?

We’ve checked cni-genie by ourselves. I don’t know about multus but in theory it should work fine.


Discrepancy in TOKEN_ALL_ACCESS value between repo and crate

I'm sorry if this issue is out of place - I don't think it belongs here but I couldn't find a better place to ask.
I've been using the latest version of the windows crate, (currently 0.44.0) and was having trouble with a call to DuplicateTokenEx.  Upon inspection, I found the value of TOKEN_ALL_ACCESS was 983295 (F00FF).

The value I expected was 983551 (F01FF).  This is the value within this repo, so why are they different?

This sounds like https://github.com/microsoft/win32metadata/issues/1410

Yep, you should see that fix in the next published version of the windows and windows-sys crates.


Request for CDN: Convert TypeScript triple-slash directive to x-typescript-types http header

Some JavaScript files contain the following line:
/// <reference types="./types.d.ts" />

It would be cool if cdn.pika.dev provide TypeScript header file based on this file.

Done! This is ready to go out tomorrow, but can you share a package where you've seen this where you'd like it fixed, so that I can confirm before deploying?

but can you share a package where you've seen this where you'd like it fixed

@tsfun/pipe

index.js
index.mjs

Fixed! Thanks for filing!

@FredKSchott curl -I https://cdn.pika.dev/... in my machine no longer return x-typescript-types. What's happening?
curl -I https://cdn.pika.dev/fp-ts | grep -i x-typescript-types
curl -I https://cdn.pika.dev/@tsfun/pipe | grep -i x-typescript-types
curl -I https://cdn.pika.dev/@tsfun/all | grep -i x-typescript-types

I can see the headers just fine, but with curl -v instead of curl -I. Also in Deno and the browser.
 curl -v https://cdn.pika.dev/fp-ts
// ...
< x-import-url<EMAIL_ADDRESS>< x-pinned-url<EMAIL_ADDRESS>< x-typescript-types: /-/fp-ts@v2.5.3-ryjcXA22li16wd7sbqeF/dist=es2017,mode=types/index.d.ts

I don't know enough about curl to know the difference and why it would show with one but not the other, but are you sure that this was working before?

curl -i works too.

but are you sure that this was working before?

Yes, last time I tried (curl -I) was about a month ago.

huh. Well, I'm stumped 😅. Any ideas why that could be?

huh. Well, I'm stumped . Any ideas why that could be?

I don't have any idea either. The best guess I can make is curl somehow changed since I upgraded my system yesterday.

Oh! i think i found it in the manual:
     -I, --head
              (HTTP FTP FILE) Fetch the headers only! HTTP-servers feature the command HEAD which this  uses  to  get
              nothing but the header of a document. When used on an FTP or FILE file, curl displays the file size and
              last modification time only.

We should implement a HEAD method. I'm not sure if we were doing that before tho, but it sounds like that's what is up.

I see now. I just try again but with -X GET and it works:
curl -I -X GET https://cdn.pika.dev/@tsfun/all | grep -i x-typescript-types

Regarding this X-TypeScript-Types header:
curl -I -X GET https://cdn.pika.dev/semver
Returned this in the header:
x-typescript-types: /-/semver@v7.1.3-ADApQhGtlqxCaVKMLXbi/dist=es2017,mode=types/index.d.ts
But subsequent curl to this d.ts file returned 502:
curl -I -X GET https://cdn.pika.dev/-/semver@v7.1.3-ADApQhGtlqxCaVKMLXbi/dist=es2017,mode=types/index.d.ts
However, @types/semver is a valid package on https://npmjs.com.
Maybe the d.ts file conversion somehow failed or did not exist?
If that so, is it possible to not include it in the X-TypeScript-Types header in the first request?

@shian15810
SemVer does not support ESM anyway, so it does not matter much. I recommend you to use these packages instead, the blue "TS" bag indicates that the package has TypeScript support.
I also recommend you to use https://pika.dev to search for packages, so that you may not which one supports ESM and TypeScript.

@KSXGitHub
Yeah, thanks for the info!
The content of<EMAIL_ADDRESS>is actually valid ESM, can be imported by both deno and node ("type": "module").
Only that the 502 is causing deno to crash:
error: Uncaught Error: Import 'https://cdn.pika.dev/-/semver@v7.1.3-ADApQhGtlqxCaVKMLXbi/dist=es2017,mode=types/index.d.ts' failed: 502 Bad Gateway
Also, pouchdb is valid ESM according to https://www.pika.dev/search?q=pouchdb.
However, importing it in deno is causing deno to crash too:
Import<EMAIL_ADDRESS>failed: 500 Internal Server Error
Viewing this URL in browser is showing: Build Error: This package could not be built.
Anyway, both 500 and 502 are harmful to Pika's backend, could possibly led to server crash.

@shian15810 It seems there are 2 issues to create, one for Pika (as the issue you are describing is not related to this issue), and one for Deno (as Deno shouldn't crash on error).

Actually, according to the philosophy of fail-fast, deno has nothing to do with this, it should just crash. Just like if you do import unknown from 'https://not/valid/url.ts', it should just crash telling you that the URL couldn't be imported.
I will create another issue for the 502.
Thanks!

it should just crash

I thought you were talking about Deno's Rust code crashing, but re-reading your comment, I realized that it throws an error. Then it is the correct behavior. However, this behavior [crashing when TypeScript definition is not found] is only desired when developing TypeScript, as type definition are not essential to JavaScript. So I think you should still open an issue on Deno titled "For pure JavaScript code, Deno should not crash when TypeScript definition is not found".

on the pika CDN side of things, this has been fixed! Try again with Deno just in case to confirm.
502 error meant that there was something bad going on on our CDN. It came down to this line:
// https://unpkg.com/browse/<EMAIL_ADDRESS>import semverParse = require('./functions/parse');

That's not valid ESM, so our ESM import parser failed. Doing some magic now on our end to handle this as if it were a valid import statement. Thanks for filing!

@FredKSchott Thanks for the fast resolution! Keep up the good work!
@KSXGitHub Agreed with you! I will create an issue on deno at free time.


TestNG Extent Report HTML is not rendering properly

Hi Kaushik,
We have TestNG test reports generated by Extent Reports. We tried to publish the report using your extension. Unfortunately its not rendering properly. PFB images
Actual Report

Published report using extension

Any suggestion to fix this issue would help us.
Thanks

Hi as mentioned in the documentation, you will need to build functionality to support something like testng. This extension fully supports jmeter and simple one pager html reports

Hi as mentioned in the documentation, you will need to build functionality to support something like testng. This extension fully supports jmeter and simple one pager html reports


Backend builds sometimes fail with duplicate generated schemas

Sometimes jobs fail like:
$ sbt test && node ./out/tests/runTest.js
[info] welcome to sbt 1.8.2 (Temurin Java 1.8.0_362)
[info] loading settings for project daffodil-vscode-build from plugins.sbt ...
[info] loading project definition from /Users/runner/work/daffodil-vscode/daffodil-vscode/project
[info] loading settings for project daffodil-debugger from build.sbt ...
[info] set current project to daffodil-debugger (in build file:/Users/runner/work/daffodil-vscode/daffodil-vscode/)
[info] Compiling 1 XSD file(s) to /Users/runner/work/daffodil-vscode/daffodil-vscode/server/core/target/scala-2.12/src_managed_cxf
parsing a schema...
Error:  'DFDLExpression' is already defined
  line 38 of file:/Users/runner/work/daffodil-vscode/daffodil-vscode/server/core/target/scala-2.12/resource_managed/xsd/org/apache/daffodil/xsd/DFDL_part1_simpletypes.xsd
...

Workaround was committed as #508.
More info:

XSD schemas are extracted from the daffodil dependencies and used to generate Java sources via JAXB.
sbt test seems to non-deterministically regenerate the Java sources. If you run it 3 times starting from a clean repo, the sources are generated 2 times, so some dependency task is being invalidated and thus rerun.
I believe CI disk state is persisted across builds.

cc: @scholarsmate @Shanedell

@arosien Sometimes jobs fail, eg failed job, something like:
$ sbt test && node ./out/tests/runTest.js
[info] welcome to sbt 1.8.2 (Temurin Java 1.8.0_362)
[info] loading settings for project daffodil-vscode-build from plugins.sbt ...
[info] loading project definition from /Users/runner/work/daffodil-vscode/daffodil-vscode/project
[info] loading settings for project daffodil-debugger from build.sbt ...
[info] set current project to daffodil-debugger (in build file:/Users/runner/work/daffodil-vscode/daffodil-vscode/)
...
[info] Compiling 1 XSD file(s) to /Users/runner/work/daffodil-vscode/daffodil-vscode/server/core/target/scala-2.12/src_managed_cxf
parsing a schema...
Error:  IOException thrown when processing "file:/Users/runner/work/daffodil-vscode/daffodil-vscode/server/core/target/scala-2.12/resource_managed/xsd/org/apache/daffodil/xsd/xml.xsd". Exception: java.io.FileNotFoundException: /Users/runner/work/daffodil-vscode/daffodil-vscode/server/core/target/scala-2.12/resource_managed/xsd/org/apache/daffodil/xsd/xml.xsd (No such file or directory).
unknown location

Error:  IOException thrown when processing "file:/Users/runner/work/daffodil-vscode/daffodil-vscode/server/core/target/scala-2.12/resource_managed/xsd/org/apache/daffodil/xsd/tdml.xsd". Exception: java.io.FileNotFoundException: /Users/runner/work/daffodil-vscode/daffodil-vscode/server/core/target/scala-2.12/resource_managed/xsd/org/apache/daffodil/xsd/tdml.xsd (No such file or directory).
unknown location
...

Are the possibly related?

I feel like yarn test (which does sbt test) should be before the yarn package (which does the universal:packageBin). This isn't necessarily related to this issue, but it seems better for the build to fail fast with unit tests before any packaging and integration tests.

I feel like these lines
https://github.com/apache/daffodil-vscode/blob/main/build.sbt#L180-L182
are dubious and are perhaps adding the re-generation of sources to the Test scope, when the Compile scope already defines them, causing the duplication during builds.

@arosien Sometimes jobs fail, eg failed job, something like:
$ sbt test && node ./out/tests/runTest.js
[info] welcome to sbt 1.8.2 (Temurin Java 1.8.0_362)
[info] loading settings for project daffodil-vscode-build from plugins.sbt ...
[info] loading project definition from /Users/runner/work/daffodil-vscode/daffodil-vscode/project
[info] loading settings for project daffodil-debugger from build.sbt ...
[info] set current project to daffodil-debugger (in build file:/Users/runner/work/daffodil-vscode/daffodil-vscode/)
...
[info] Compiling 1 XSD file(s) to /Users/runner/work/daffodil-vscode/daffodil-vscode/server/core/target/scala-2.12/src_managed_cxf
parsing a schema...
Error:  IOException thrown when processing "file:/Users/runner/work/daffodil-vscode/daffodil-vscode/server/core/target/scala-2.12/resource_managed/xsd/org/apache/daffodil/xsd/xml.xsd". Exception: java.io.FileNotFoundException: /Users/runner/work/daffodil-vscode/daffodil-vscode/server/core/target/scala-2.12/resource_managed/xsd/org/apache/daffodil/xsd/xml.xsd (No such file or directory).
unknown location

Error:  IOException thrown when processing "file:/Users/runner/work/daffodil-vscode/daffodil-vscode/server/core/target/scala-2.12/resource_managed/xsd/org/apache/daffodil/xsd/tdml.xsd". Exception: java.io.FileNotFoundException: /Users/runner/work/daffodil-vscode/daffodil-vscode/server/core/target/scala-2.12/resource_managed/xsd/org/apache/daffodil/xsd/tdml.xsd (No such file or directory).
unknown location
...

Are the possibly related?

That message looks like there is a "clean" or something removing the files, possibly from another build going on??
I know when launching the extension in VS Code it runs yarn watch, which seems to fork the sbt builds, so maybe one of  the yarn commands does this concurrent with one of the sbt CI steps.

I feel like these lines
https://github.com/apache/daffodil-vscode/blob/main/build.sbt#L180-L182
are dubious and are perhaps adding the re-generation of sources to the Test scope, when the Compile scope already defines them, causing the duplication during builds.

Been testing this in a branch and got a bunch of clean builds in a row, had to add Global / lintUnusedKeysOnLoad := false to build.sbt though to get rid of a linting error that happens when I removed those three lines.  Not sure if that line is good to keep though.   Was also able to get rid of the rm **/target in the CI.yml and still get good builds.

I feel like these lines
https://github.com/apache/daffodil-vscode/blob/main/build.sbt#L180-L182
are dubious and are perhaps adding the re-generation of sources to the Test scope, when the Compile scope already defines them, causing the duplication during builds.

Been testing this in a branch and got a bunch of clean builds in a row, had to add Global / lintUnusedKeysOnLoad := false to build.sbt though to get rid of a linting error that happens when I removed those three lines. Not sure if that line is good to keep though. Was also able to get rid of the rm **/target in the CI.yml and still get good builds.

@NolanMatt push a branch and make a (draft) PR!

@arosien, @NolanMatt is having a difficult time investigating the problem since it works for him locally and intermittently in CI. He indicated that you are able to reproduce issue locally, so I'll reassign it to you.


NewMemberCid not being read/used for install during migrate script

Passing the -NewMemberCid flag with a child CID value in a parent/child flight control environment does not actually install the new falcon sensor into the requested Child Cid. Instead, the sensor is installed into the parent CID, which is not the desired behavior. A workaround is available where passing the -NewFalconCid value with the CID-checksum of the child CID actually does install the sensor in the correct child CID. However, the -NewFalconCid parameter should not be required as the code is written, especially if the -NewMemberCid flag is included in the request.
As written, if the $NewFalconCid parameter is NOT included, it calls /sensors/queries/installers/ccid/v1 to retrieve the CID-checksum value for the sensor install. However, in that request, the -MemberCid parameter (which would map to -NewMemberCid, if used) must be getting passed.

Thank you for this detailed report on the issue.

Re-opening since we did more troubleshooting and found the existing PR does not address this issue. A new PR with the correct fix is on the way.


"Cannot read property" on completing python files

I was working on a python file today and noticed I wasn't getting completions. After googling, I saw that the atom package only has c-family languages enabled by default, so I open settings and add 'python' to the list of languages to autocomplete.
Unfortunately, now when I try to autocomplete I get this error:
TypeError: Cannot read property 'substr' of undefined
    at converters.python (/home/jgf/.atom/packages/you-complete-me/lib/get-completions.coffee:54:50)
    at Array.map (native)
    at convertCompletions (/home/jgf/.atom/packages/you-complete-me/lib/get-completions.coffee:64:15)
    at process._tickCallback (node.js:392:9)

I am running the latest YCMD available, from the master branch, and 0.7.8 for the Atom you-complete-me package.
Any help would be appreciated.

Also, when I open cc files I get this error:
TypeError: Not a buffer
    at TypeError (native)
    at new Hmac (crypto.js:87:16)
    at Object.Hmac (crypto.js:85:12)
    at generateHmac (/home/jgf/.atom/packages/you-complete-me/lib/handler.coffee:103:12)
    at signMessage (/home/jgf/.atom/packages/you-complete-me/lib/handler.coffee:114:65)
    at /home/jgf/.atom/packages/you-complete-me/lib/handler.coffee:165:7

The only change that's happened recently is that the atom you-complete-me package updated.

Something similar is observed with .cpp files:
TypeError: Not a buffer
    at TypeError (native)
    at new Hmac (crypto.js:87:16)
    at Object.Hmac (crypto.js:85:12)
    at generateHmac (/home/kaushikcfd/.atom/packages/you-complete-me/lib/handler.coffee:103:12)
    at signMessage (/home/kaushikcfd/.atom/packages/you-complete-me/lib/handler.coffee:114:65)
    at /home/kaushikcfd/.atom/packages/you-complete-me/lib/handler.coffee:165:7

@bocajnotnef Refer to the solution of Issue #65 . And please inform if it works.

fixed


Bump Dependencies #1830038159

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/1830038159

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jenkins-is-staging seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Add fastlane

@aol-public/mobile-sdk-team: Ready for review.
JIRA Issue

Bad name for a PR. No description.
Avoid copy-pasting when possible - you have added a lot of code which is useless for this task.
Please do a cleanup. Having less code - is better.


Are the response checks too strict?

I tried to use this library to be connected to https://www.switch.ch/edu-id/docs/services/. Depending of the configuration, the EntityID of the Issuer can be different from the IDP which is required by python3-saml (https://github.com/onelogin/python3-saml/blob/59dd034a9a04246fc2b3cf462216aaa5a776f1f9/src/onelogin/saml2/response.py#L216).
Moreover, this check https://github.com/onelogin/python3-saml/blob/59dd034a9a04246fc2b3cf462216aaa5a776f1f9/src/onelogin/saml2/response.py#L307 also failed.
I did not find in the SAML documentation that these checks are required (https://www.oasis-open.org/committees/download.php/56782/sstc-saml-profiles-errata-2.0-wd-07.pdf).
Do you think that these checks can be optional by configuration?
Many thanks in advance.

Any news? Do you think that my post if irrelevant?

See https://github.com/SAML-Toolkits/python3-saml/issues/329#issuecomment-1353685748

I agree, there is nothing in the SAML2 specification that mandates that the Service Provider needs to check that the Issuer has the same entityID as was used when the user was sent to the Identity Provider. Neither the Shibboleth SP, nor SimpleSAML have these checks (SimpleSAML had this check but then removed it they were made aware that this check is not according to the standard and that these obsolete checks in fact prevent some legit use-cases).

@lhaemmerle
The situation described on the SSP ticket is totally different than the use case here.
On SSP the exception happened when the SP sent an AuthNRequest to IdP A, stored. In the status the IdP Entity ID and then while processing the SAMLResponse, checked that the Issuer of such Response matched the IdP Entity ID stored.
php-saml does not store such initial IdP Entity ID and do later any check. The check you reference in this ticket is done between the Entity ID lf the IdP that generated the SAMLResponse received and the Entity ID of the IdPs that are trusted, a legit check.
SSP and Shibboleth do also this check, otherwise, how SAML settings/metadata of such IdP are retrieved to be managed by the toolkit during the SAMLResponse validation? If they dont recognize the Entity ID, they raise an exception.


ResolveBug

Environment (please complete the following information):

OS (e.g., Windows 10):
Extension version (e.g., 1.2.3):

Describe the bug:

Repro steps:

Expected behavior:

Additional context:

Resolve Bug


⚠ SceneTime has degraded performance

In 6f519ba, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 9527 ms

Resolved: SceneTime performance has improved in 34d5b85.


Add a /data handler to return WOF records from a whonsonfirst/go-reader interface

Basically we need a way for the web application to fetch SPR records from the /point-in-polygon endpoint and then fetch the WOF GeoJSON records over the wire.
As of this writing the application defaults to requesting ?format=geojson records but these are often large and take to long to deliver. Better instead to do a quick PIP query and then inflate the records on the fly.

Use this:
https://github.com/whosonfirst/go-http-whosonfirst-data

This is no longer relevant following the use of whosonfirst/go-whosonfirst-spr-geojson.


Turns messages into functions

This is a fix for https://github.com/unindented/custom-immutable-matchers/issues/39
Can you advise on your test & build process?
A CONTRIBUTING.md would be very helpful.

Ran into this problem when migrating a large code base from Jasmine to Jest 22 :)
Would be good to get this in if possible 🎉


"Load more results" button appears below an empty search gallery

Describe the bug
This bug is rather subtle.
Toggling between the (empty) search section and the bookmarks section would not render the the "Load more results" button.

This button would appear if you open image-detail of any image while in the bookmarks section, and then toggle back to the search section. Also, clicking the button makes a render request with an empty search query (https://api.creativecommons.engineering/v1/images?q=&page=1&page_size=20&license=&source=&extension=&categories=&size=&aspect_ratio=&mature=false)

Expected behavior
The button should not appear in the second case.

Hi @makkoncept
Is it okay if I take this up?
Best,
Vivek

Hi @makkoncept
I fixed the bug by changing 2 lines of code. But when I try running ES Lint, I get this....
ESLint: 5.16.0.
No files matching the pattern "'./src/**/*.js'" were found.
Please check for typing mistakes in the pattern.

What do you think I should do?
Thanks.

Hi @vivek32ta, I am not able to mimic the error on my machine. Can you provide the following information for better debugging? Before that, you can delete the node_modules/ and reinstall the dependencies and check if the error persists.

Have you changed the project directory structure? Please paste the screenshot of the file structure of the project as shown in your editor.

On your terminal, explicitly run the command from the root of the project: eslint './src/**/*.js/'. Please paste the output.

What is your Operating system? Also, tell the node and the npm version.

Hey @makkoncept,
I figured it out. I'm using windows so single quotes don't identify as strings in command prompt. So I changed the eslint command in package.json with double quotes to....
eslint \"./src/**/*.js\" \"./tests/**/*.js\"
ES Lint works fine now.


Formatting issue in JavaDocs parsing a multiline method invocation in @see.

Discovered by @pway99
    @Test
    fun seeWithMultilineMethodInvocation(jp: JavaParser) = assertParsePrintAndProcess(
        jp,
        CompilationUnit,
        """
            import java.lang.Math;

            interface Test {
                /**
                 * @see Math#pow(double,
                 * double)
                 * @see Math#pow(double, double)
                 */
                boolean test();
            }
        """.trimIndent()
    )

Note:
The formatting issue exists in every annotation that allows a reference to a J type.
J types like J.MethodInvocation contain Space(s) and may exist on multiple lines in java.
method('\n'
    arg0,'\n'
    arg1);

The Javadoc parser filters out the margin '*' and converts the method invocation into a DC.Link.
*   method('\n'
*       arg0,'\n'
*       arg1);

=> method('\n'    arg0,'\n'    arg1)
A Linebreak in the java doc visitors contains both the new line characters and margin of the java doc.
    *   method('\n' // line break for this new line will be '\n', 'space characters','*'
    *       arg0,

But a J type represents whitespace as Space.
Both a Space and Linebreak are created, which causes formatting issues during print.

Putting the issue back into the backlog until we know there is a need for the changes.

Note: Updating how method invocations work in JavaDocs will fix {@link ...} as well.
ref: https://github.com/openrewrite/rewrite/issues/1696


Fix accessing UIViewManager configs

Summary
This PR should remove the warning regarding UIViewManager accessing  LottieAnimationView directly.
See the source comments for more information:
https://github.com/facebook/react-native/blob/fc94ade11c09bc5ed027f7ebd58341d851d4c3fb/Libraries/ReactNative/UIManagerProperties.js#L15
Closes #437
Test Plan
Compatibility

OS
Implemented

iOS
✅

Android
✅

Checklist

[x] I have tested this on a device and a simulator
[x] I mentioned this change in CHANGELOG.md

Thank you for your hard work addressing these config fixes.   How soon can we expect a merge?

thanks @andrewtremblay !


Fix the gh action that detects the drift

fix the action syntax (was failing on this https://github.com/giantswarm/cluster-api-provider-vsphere-app/actions/runs/5668441144)
this has been tested on my fork:

https://github.com/jkremser/cluster-api-provider-vsphere-app/pull/1
https://github.com/jkremser/cluster-api-provider-vsphere-app/pull/2

@vxav I think so.  My intention was always to rebase this change and test and merge but I couldn't find a change. SORRRYYYYY


Add matrix

From what I can understand simply adding the fields to the template and event .toml should suffice.
We can merge and test

Once again, has to go to BBW 🤦  😄


feat: pre-login mobile app exploration

Description
This PR adds support for pre-login exploration.

Feature is implemented behind a feature flag preLoginExperienceEnabled
User will be able to navigate to Signup, SignIn, DiscoveryCourses & SearchCourses screen
Back button is added on required screens for back navigation
Navigation from SignIn to Signup is removed
Screen Orientation supported

Here is the video of the implemented feature
https://github.com/openedx/openedx-app-android/assets/30689349/cc6671ac-893f-4593-816a-b1c06cb9eb8a

Agree with the feedback provided by @farhan-arshad-dev.
It would be beneficial to address those concerns before moving forward.

@k1rill @farhan-arshad-dev @HamzaIsrar12,
let's focus on this PR, waiting for your review/approval.

@k1rill ready for another pass

@volodymyr-chekyrta the PR is approved now you can merge it. 🚀

@omerhabib26, I found one problem, could you please check why it is crashing?
The video is attached below.
https://github.com/openedx/openedx-app-android/assets/127732735/26e61930-5179-4912-a2ca-d318a02b2774

Also, there is a crash when trying to open any course.
java.lang.IllegalStateException: Fragment DiscoveryFragment{a096e35} (d8cc59a3-8b4b-4a42-9f65-50d120962281 id=0x7f0a00b8 tag=DiscoveryFragment) is not a child Fragment, it is directly attached to org.openedx.app.AppActivity@c8a8e38
https://github.com/openedx/openedx-app-android/assets/127732735/6524ad19-a10d-417a-9ba2-a11d1a045879

Same problem as in iOS - the user sees an error message when trying to enroll. Perhaps should redirect the user to log in or hide the "Enroll" button.

This is a known behavior and is not a part of the ticket scope.

@omerhabib26, I found one problem, could you please check why it is crashing? The video is attached below. https://github.com/openedx/openedx-app-android/assets/127732735/26e61930-5179-4912-a2ca-d318a02b2774

It was intermittent but fixed now.

@volodymyr-chekyrta PR is ready for final pass

No other issues; we can merge it after renaming the Logistration file and resolving conflicts.


[WIP] Update calico manifests to v3.11

Following the guide here:
https://docs.projectcalico.org/v3.1/getting-started/kubernetes/installation/calico
I made the changes to the calico yaml templates required for 3.11
Making sure to continue to mount in the etcd tls files as before.
What this PR does / why we need it:
Updates tarmak's calico deployment to 3.11.
We need this so that calico uses etcd 3 as etcd 3 is easier to backup.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged):
Special notes for your reviewer:
Release note:

Upgrade calico cni plugin to from v2.6 to 3.11

/test puppet-tarmak-acceptance-centos v1.6

/test puppet-tarmak-acceptance-centos v1.6

/test puppet

/test puppet

/test puppet

/retest

/retest

/retest

The problems we have seen have been down to the fact that the controller hasn't been updated :see_no_evil:
/lgtm