text:
[Bug] Reading agent environment vars from file does not work

Rancher 2.6.1-RC1

Given the following txt file, named "proxy-vars.txt":

HTTP_PROXY=http://USERNAME:PASSWORD@10.0.1.1:8080/
HTTPS_PROXY=https://USERNAME:PASSWORD@10.0.0.1:8080/
NO_PROXY=master.hostname.example.com,10.1.0.0/16,172.30.0.0/16

Navigate to Cluster Manager -> Create RKE2 Cluster (any provider)
Scroll to Agent Environment Vars and select "Read from file"
Select the txt file

Result:
The content of the txt file is not correctly parsed into key/value pairs:

@Sean-McQ Is there a PR related to this that needs to be reviewed?

My checks PASSED
Validation Environment:

Rancher version: v2.6-head e322f8f pulled at 11/22/21 10:11am Arizona time
Rancher cluster type: single-node docker install
Docker version: 20.10
Downstream cluster type: n/a
Downstream K8s version: n/a
Validation steps:

Create any RKE2/K3S cluster.
On the form, go to the Cluster Configuration section > Agent Environment Vars
Create a text file locally on disk "proxy-vars.txt" with the following contents in the file:

HTTP_PROXY=http://USERNAME:PASSWORD@10.0.1.1:8080/
HTTPS_PROXY=https://USERNAME:PASSWORD@10.0.0.1:8080/
NO_PROXY=master.hostname.example.com,10.1.0.0/16,172.30.0.0/16

Click the "Read from file" button and upload the "proxy-vars.txt" file when prompted.
Notice, this now works correctly. I no longer experience the issue as reproduced earlier here https://github.com/rancher/dashboard/issues/4196#issuecomment-949766160
The file is parsed properly and we now have three entries each with proper key=value pairs. There is one extra entry but this seems to be benign.

And, when I submit the form to create the cluster, the POST to provisioning.cattle.io.clusters looks normal, except a benign additional entry is sent. I created a separate bug for that here:  https://github.com/rancher/dashboard/issues/4619

This appears to be because the UI is creating an additional entry when reading in the text file.
Additional Info:

authors: davidnuzik janeczku richard-cox


text:
Continuous Delivery Git Repo Auth Secrets are hard to pick

Detailed Description
Existing auth secrets in the Git Repo UI of Continuous Delivery are hard to pick, because the dropdown only shows the name of the secret (which is auto-generated when created through the same UI before) and the type. If you have multiple secrets, it's hard to tell which is the right one.
Context
Example screenshot

Proposed change:
The Secrets list contains an additional data column to identify the secrets easier. These could be included in the dropdown as well:

Verified on v2.6-head https://github.com/rancher/rancher/commit/a678d0e12fe21936f09ae0e906bc420e43d7d35c.
ENVIRONMENT DETAILS

Rancher Install: Helm
Rancher version: v2.6-head https://github.com/rancher/rancher/commit/a678d0e12fe21936f09ae0e906bc420e43d7d35c
Browser: Chrome

TEST RESULT
PASS
VERIFICATION STEPS

Setup Rancher and navigate to the UI in a browser.
Navigated to Cluster Explorer > Continuous Delivery > Git repo.
Create a new Git repo against a public (or private) Git repo.
Once done, attempted to create another Git repo and verified that the Git Authentication dropdown correctly shows your new repo.

Navigated to Cluster Management and attempt to provision a downstream RKE2 node driver cluster.
In Cluster Configuration click Registries and select Pull images for Rancher from a private registry.
Clicked the Authentication dropdown and verified that the Git repo is successfully shown:

source: gharchive/issue

authors: bashofmann markusewalker

repo: rancher/dashboard

license_type: permissive

license_source: github-api


text:
[forwardport of #2553] StatefulSet "Service Name" required, but not marked

This PR addresses issue #4811 by making 'Service Name' a required field when creating a StatefulSet
To test this pr

From your cluster navigate to Workload > StatefulSets
Click the Create button
The 'Service Name' field should now have a red 'required' asterisk

What do you mean by forwardport in the title?

What do you mean by forwardport in the title?

I copied the issue title. Removed now for clarity

source: gharchive/pull-request

authors: neillsom nwmac


text:
Fix stuck loading indicator (auth)

Fixes #7818
The Nuxt loading indicator does not get removed when we prevent the navigation in this use case - this PR forces the loading indicator to be removed.

@mantis-toboggan-md Sorry about that - tidied up now


text:
Examples

See https://github.com/rancher/elemental-toolkit/issues/1402

reworked it slightly, also tested locally :+1:

repo: rancher/elemental-toolkit


text:
Added script for automatic AUR release & added steps in .drone.yml

Finally had some time for the AUR integration.
What is done:

Added 2 new steps to .drone.yml, one for normal release-aur and one for the pre-elease versions pre-release-aur.
Both run the deploy-aur.sh script, located at the root directory, via an archlinux image. They also depend on release/pre-release, so the AUR package waits for the release pipepline to create the github release.
The deploy-aur.sh takes care of the archlinux bootstrap (installation of git, ssh etc.). After that, it puts the configured private key (saved in base64-format to the drone secrets) to a file and starts pulling the AUR Package repo. Via a some magic environment substition tricks, it then fetches all new sha256sums and finally generates a new PKGBUILD, which gets commited and pushed to the AUR.

TODO for you guys:

Create an account on https://aur.archlinux.org/
Generate a private/public key pair

Upload the public part to your AUR account
base64 the private key (cat ~/.ssh/your_key | base64 -w0) and add it as a secret to your drone installation

Once that's done, I will add you as the maintainer to both packages and we should be good to go :) If you don't want a third party (me) having access to the packages, we can also transfer the packages to your account. Maybe complicates debugging in case of problems, but I would completely understand.

Looking forward to your thoughts! Also, feel free to make necessary additions/corrections or just tell me 👍 :)

Reference Issue: #230
BTW, just saw my YAML formatter removed some extra lines. If that's unwanted, ping me and I will revert them 😅

Hi @JohnnyCrazy , thanks for this PR! .. and sorry for my late reply, I was off for a while now.
For this, I have to check with the RancherLabs folks, if they maybe already have an account on AUR and if they can add this secret to their drone environment.

No problem, take your time and feel free to ping me if you want anything updated/changed :)

Just giving you a quick update here: so far I don't have a "go" here :confused:

Just giving you a quick update here: so far I don't have a "go" here 😕

No worries, if it's not possible due to policies or other complications, I will find another automated solution, off the main repo :)

Hi @JohnnyCrazy , so it seems that Rancher doesn't own an AUR repo/account and probably won't create one only for k3d.
However, I just did so with an extra account only for k3d.
So let's just continue work on this :+1: Did you test this pipeline with drone already? Especially the substitution parts around $NEW_RELEASE?

Hi again 👋
I already tested on a private drone instance, if you give me tomorrow/the day after tomorrow I will give it an additional run and see if everything works out! 👍
Added you as maintainer as well!

I already tested on a private drone instance, if you give me tomorrow/the day after tomorrow I will give it an additional run and see if everything works out! +1

Sure! I'll talk to the Rancher folks today to get the private key added to their drone instance. If that doesn't work out, we might have to move this part of the pipeline to Travis (or GitHub Actions) though :thinking:

Added you as maintainer as well!

Received the mails, thank you!

It's me again @JohnnyCrazy :wave:
Unfortunately, Rancher cannot prioritize creating their own AUR Account right now, but it's in their backlog.
Additionally, internal policy forbids them to add the third-party (me) key for AUR to their (Drone) infrastructure.
So to get this going now, let's migrate this part of the pipeline to either Travis CI or GitHub Actions :+1:

Okay, this probably needs some additional checks if the release is already uploaded and available, since it probably runs in parallel with drone.
If it's okay for you time-wise, I could migrate it till sunday :)

superseded by #391

license: MIT


text:
Remove prometheus config from metrics checklist

Fix #548
This removes the check for additionalServiceMonitors added to the Prometheus config and instead checks for the existence of a ServiceMonitor that has a selector pointing to the kubewarden-controller. The new step for service monitors will not block the checklist from succeeding.
Also changed the colors of the checkmarks to be green.

I see some potential issues here:

service monitor doc link points to kubewarden, so examples have kubewarden namespace, not cattle-kubewarden-system, we should point to UI doc , which recommends to install rancher-managed monitoring?

shouldn't we check for kubewarden-policy-server-default? Is kubewarden-controller service monitor used for something?

maybe we could add button redirecting to one of those: (would feel more UI-ish) :)

Menu->Monitoring->Service Monitors or
Menu->More Resources->Service Monitors?

we should not show grafana before this check is complete, otherwise data are empty

Is kubewarden-controller service monitor used for something? I see no change when I remove it. Maybe we could check for any service monitor with namespaceSelector ===  namespace.

I see no difference when the service monitor is created and then removed, but if the service monitor is never created prometheus does not display any data. I think checking for any service monitor would suffice for the time being.

we should not show grafana before this check is complete, otherwise data are empty

This check was left as non-blocking due to internal discussion, we should re-discuss this subject.

After some internal discussion, it appears that only a ServiceMonitor per Policy Server is necessary for Prometheus to fetch data. So I have updated the PR to now search for a ServiceMonitor tied to the PolicyServer that is either being viewed or that is connected to the policy being viewed.
The checklist is searching all of the fetched ServiceMonitors based the kubewarden-controller namespace, and two matchLabels:

kubewarden/policy-server=<policy-server-id>
app=<policy-server-id

The label kubewarden/policy-server is added automatically to any PolicyServer deployment when a PS is created.
If the service monitor is not found, the checklist will appear as this is necessary for the metrics to contain any data. There is now a button within the ServiceMonitor step of the checklist to add the necessary Service Monitor.
https://github.com/rancher/kubewarden-ui/assets/40806497/59f0910d-d520-4936-83a1-cb57b61b4710

matchLabels section is wrong, data are empty
# we habe
    selector:
      matchLabels:
        kubewarden/policy-server: default

# this works
    selector:
      matchLabels:
        app: kubewarden-policy-server-default

I  think serviceMonitor matchLabel have to match policy-server service, for default one it's:
k describe svc -n cattle-kubewarden-system policy-server-default                                                                                0.425s
Name:              policy-server-default
Namespace:         cattle-kubewarden-system
Labels:            app=kubewarden-policy-server-default

Can we also make Edit Config enablement depend on OTEL? Enabling metrics without OTEL fails:
helm upgrade --history-max=5 --install=true --namespace=cattle-kubewarden-system --timeout=10m0s --values=/home/shell/helm/values-kubewarden-controller-2.0.3.yaml --version=2.0.3 --wait=true rancher-kubewarden-controller /home/shell/helm/kubewarden-controller-2.0.3.tgz
Error: UPGRADE FAILED: resource mapping not found for name: "kubewarden" namespace: "cattle-kubewarden-system" from "": no matches for kind "OpenTelemetryCollector" in version "opentelemetry.io/v1alpha1"
2023-11-21T08:09:00.679029215Z ensure CRDs are installed first

I've fixed the ServiceMonitor check/creation for matchLabels to be app=kubewarden-policy-server-<policy-server-id>. Also fixed the condition to the "Edit Config" button to be gated by the existence of the opentelemetry service.

e2e will pass when https://github.com/rancher/kubewarden-ui/pull/551 is merged.

authors: jordojordo kravciak

repo: rancher/kubewarden-ui


text:
How to init RancherOS instance using cloud_init.yml + vagrant + vm

I'm running RancherOS 0.4.3 on vagrant machine I was wondering how can I pass my cloud-init.yml when vagrant up to initialise my machine.

We've moved away from using vagrant and recommend using docker-machine. We will no longer be able to provide support to our vagrant setup.
FYI, even with docker-machine, you will not be able to pass in a cloud-config.yml.
Let me know if you have further questions.

Thanks you so much for you answer @deniseschannon !

repo: rancher/os


text:
[Rancher2] Single Node Using Docker fails with cgroups v2

Request Summary:
It seems to be a known issue that the single node docker install does not work on operating systems using the newer cgroups v2.
Therefore I would suggest adding a section to the installation page warning about that fact and pointing the users to a k3s + helm setup.
Maybe similar to how its done here: https://rancher.com/docs/rancher/v2.6/en/backups/restoring-rancher/#known-issues
Details:

Documentation Link

Some example issues from rancher/rancher

https://github.com/rancher/rancher/issues/37225
https://github.com/rancher/rancher/issues/37210

Hi, I found this doc bug but I also have the prerequisite fix when using cgroupv2, which kernel module to enable and more
we also fix the entrypoint rancher container
see: https://github.com/rancher/rancher/issues/36238#issuecomment-1232690242

I am interested into this issue, please do not close it.

authors: IceCodeNew dgiebert lerminou

repo: rancher/rancher-docs


text:
kube-proxy cannot support IPVS with default RKE configuration

Currently kube-proxy deployed by Rancher via RKE can only work in iptables or userspace modes, but not IPVS even though the feature gate is enabled by default since 1.10
The reason is that the kube-proxy container process doesn't have the /lib/modules host volume mounted, which is required to load the module (kube-proxy does a modprobe on ip_vs at start time and falls back to previous modes when it fails).
This is related to how the docker container is built in RKE BuildKubeProxyProcess function.
First approach to solve this would be to add the missing volume of /lib/modules as read-only mount in that function.
The second approach would be to not bootstrap the kube-proxy process in RKE but rather deploy it as a daemonset to the cluster via addon jobs. I personally would prefer this approach, since I believe it's the correct way to deploy it on most platforms. I don't see any advantages of having it being orchestrated statically outside of Kubernetes.
We can use the following base manifest as a reference:
https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/kube-proxy/kube-proxy-ds.yaml
Ideas?

I would say that this issue is specific to RKE and not Rancher 2.0 ?
But everything you said remains true whatsoever, and I'm having the exact same issue with a RKE (v0.17) deployed cluster (i.e. kube-proxy not using ipvs whereas it should be the default since 1.10).
Cheers,

@rdegez Indeed this must be fixed in RKE repository.
However I believe the issue must be tracked here, since this is a meta repository that should encompass all issues that end users can face with Rancher.

This being said, I'm not sure this kube-proxy mode can be parameterized with the Rancher API right now (rancherKubernernetesEngine) and no way to change it in the UI neither.
Perhaps an opportunity to discuss adding this.
Also I suppose it would make a good default for Rancher clusters with release 1.10+

Currently see the following error in kube-proxy container logs:
W1028 21:20:18.394612    7537 server.go:216] WARNING: all flags other than --config, --write-config-to, and --cleanup are deprecated. Please begin using a config file ASAP.
I1028 21:20:18.394649    7537 feature_gate.go:216] feature gates: &{map[]}
W1028 21:20:18.397319    7537 proxier.go:500] Failed to read file /lib/modules/4.4.0-1092-aws/modules.builtin with error open /lib/modules/4.4.0-1092-aws/modules.builtin: no such file or directory. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1028 21:20:18.398245    7537 proxier.go:513] Failed to load kernel module ip_vs with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1028 21:20:18.398988    7537 proxier.go:513] Failed to load kernel module ip_vs_rr with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1028 21:20:18.399689    7537 proxier.go:513] Failed to load kernel module ip_vs_wrr with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1028 21:20:18.400405    7537 proxier.go:513] Failed to load kernel module ip_vs_sh with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1028 21:20:18.401072    7537 proxier.go:513] Failed to load kernel module nf_conntrack_ipv4 with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
W1028 21:20:18.406726    7537 server_others.go:249] Flag proxy-mode="" unknown, assuming iptables proxy
I1028 21:20:18.417393    7537 server_others.go:143] Using iptables Proxier.

@alexandrem you can pass the proxy-mode parameter under extra_args for the kubeproxy service in the cluster.yml file while creating a cluster in the UI.
In the "Edit As Yaml" option in UI, add this under services:
    kubeproxy:
      extra_args:
        proxy-mode: ipvs

@prachidamle that's not enough though, 'cause you still need the kernel modules. I'm currently using this config to achieve the ipvs behaviour:
services:
  kubeproxy:
    extra_args:
      proxy-mode: ipvs
    extra_binds:
      - "/lib/modules:/lib/modules:ro"

You need to load ip_vs, ip_vs_rr, ip_vs_wrr, ip_vs_sh,nf_conntrack_ipv4 modules beforehand.

Tested with v2.3.3-head with UI index latest-2.3
Created a DO RKE cluster with specifying kubeproxy config as below in cluster.yml file
    kubeproxy:
      extra_args:
        proxy-mode: ipvs

The cluster creation succeeded and cluster was functional.
Docker inspect on the kubeproxy container on each of the hosts indicated the proxy-mode:ipvs as below
"Id": "ba7baee5768dec39e1b7b8ff58a3c3393c850b280c7bb3566a78af11a4345301",
        "Created": "2019-10-30T23:28:19.83651983Z",
        "Path": "/opt/rke-tools/entrypoint.sh",
        "Args": [
            "kube-proxy",
            "--cluster-cidr=10.42.0.0/16",
            "--hostname-override=test",
            "--kubeconfig=/etc/kubernetes/ssl/kubecfg-kube-proxy.yaml",
            "--v=2",
            "--healthz-bind-address=127.0.0.1",
            "--proxy-mode=ipvs"

Created nginx workloads and ping from each of the pod's IP to the cluster IP succeeded
Ping from each of the pods to other pods on different hosts was also successful.
Creation of cluster using RKE standalone tool with kubeproxy mode set to ipvs was also tested.
Cluster got created successfully and the kubeproxy container had the setting proxy-mode = ipvs

@ulm0 yes there is already a fix to bind-mount the volume coming in 2.3.3. My comment was about how to enable ipvs mode from Rancher UI while creating cluster in addition to this fix.

@soumyalj Hi, thanks for your comment. But I have a consider on there, I used rke==0.3.2 updated my cluster with the proxy-mode = ipvs parameter, but I didn't saw any role on worker nodes. So, I believe it was not working, so, what could we do?
[root@cont-32-rdc ~]# ipvsadm -l
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn

@soumyalj Hi, thanks for your comment. But I have a consider on here, I used rke==0.3.2 updated my cluster with the proxy-mode = ipvs parameter, but I didn't saw any role on worker nodes. So, Is there has any other thing I need to do?
[root@cont-32-rdc ~]# ipvsadm -l
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn

Finally, I followed @ulm0 solution, It seems worker for me.
ip addr

171: kube-ipvs0: <BROADCAST,NOARP> mtu 1500 qdisc noop state DOWN group default
    link/ether 7e:79:a9:34:20:dc brd ff:ff:ff:ff:ff:ff
    inet 10.43.239.13/32 brd 10.43.239.13 scope global kube-ipvs0
       valid_lft forever preferred_lft forever
    inet 10.43.45.167/32 brd 10.43.45.167 scope global kube-ipvs0
       valid_lft forever preferred_lft forever
    inet 10.43.155.51/32 brd 10.43.155.51 scope global kube-ipvs0
       valid_lft forever preferred_lft forever
    inet 10.43.87.60/32 brd 10.43.87.60 scope global kube-ipvs0
       valid_lft forever preferred_lft forever
    inet 10.43.187.3/32 brd 10.43.187.3 scope global kube-ipvs0
       valid_lft forever preferred_lft forever
    inet 10.43.65.194/32 brd 10.43.65.194 scope global kube-ipvs0
       valid_lft forever preferred_lft forever
    inet 10.43.0.1/32 brd 10.43.0.1 scope global kube-ipvs0
       valid_lft forever preferred_lft forever
    inet 10.43.47.236/32 brd 10.43.47.236 scope global kube-ipvs0
       valid_lft forever preferred_lft forever
    inet 10.43.25.101/32 brd 10.43.25.101 scope global kube-ipvs0
       valid_lft forever preferred_lft forever

ipvsadm -Ln

TCP  10.43.187.41:443 rr
  -> 10.42.3.11:443               Masq    1      0          0
TCP  10.43.213.72:80 rr
TCP  10.43.232.194:80 rr
  -> 10.42.2.22:8888              Masq    1      0          0
TCP  10.43.239.13:80 rr
  -> 10.42.2.57:8090              Masq    1      0          0
TCP  10.43.243.120:80 rr
  -> 10.42.3.30:80                Masq    1      0          0
TCP  127.0.0.1:31364 rr
TCP  127.0.0.1:31923 rr
  -> 10.42.1.22:80                Masq    1      0          0
TCP  127.0.0.1:32760 rr
  -> 10.42.1.40:3000              Masq    1      0          0
TCP  172.17.0.1:31923 rr
  -> 10.42.1.22:80                Masq    1      0          0
UDP  10.43.0.10:53 rr
  -> 10.42.2.40:53                Masq    1      0          24

Just add ipvs is not enough
E1105 02:58:17.277641  120955 server_others.go:259] can't determine whether to use ipvs proxy, error: IPVS proxier will not be used because the following required kernel modules are not loaded: [ip_vs_sh ip_vs_rr ip_vs_wrr]

kube-proxy do start with ipvs but it will fail back to iptables

@ntcong the fix to this issue will bind mount the required /lib/modules.

@soumyalj I think this should be considered for re-opening.
Because kube-proxy falls back to ip tables, I believe your test was invalid. Here's the logs from my kube-proxy with the same configuration, but without the mount mentioned by @ulm0:
W0506 19:21:27.159753   15477 proxier.go:513] Failed to load kernel module ip_vs with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
E0506 19:21:27.188407   15477 server_others.go:259] can't determine whether to use ipvs proxy, error: IPVS proxier will not be used because the following required kernel modules are not loaded: [ip_vs ip_vs_rr ip_vs_wrr ip_vs_sh]
I0506 19:21:27.188430   15477 server_others.go:266] Can't use ipvs proxier, trying iptables proxier
I0506 19:21:27.190084   15477 server_others.go:143] Using iptables Proxier.

@soumyalj I think this should be considered for re-opening.
Because kube-proxy falls back to ip tables, I believe your test was invalid. Here's the logs from my kube-proxy with the same configuration, but without the mount mentioned by @ulm0:
W0506 19:21:27.159753   15477 proxier.go:513] Failed to load kernel module ip_vs with modprobe. You can ignore this message when kube-proxy is running inside container without mounting /lib/modules
E0506 19:21:27.188407   15477 server_others.go:259] can't determine whether to use ipvs proxy, error: IPVS proxier will not be used because the following required kernel modules are not loaded: [ip_vs ip_vs_rr ip_vs_wrr ip_vs_sh]
I0506 19:21:27.188430   15477 server_others.go:266] Can't use ipvs proxier, trying iptables proxier
I0506 19:21:27.190084   15477 server_others.go:143] Using iptables Proxier.

I think you can executing shell commands manually like this on each node:
modprobe ip_vs
modprobe ip_vs_rr
modprobe ip_vs_wrr
modprobe ip_vs_sh
then restart kube-proxy
docker restart kube-proxy
check the interface, if you can see "kube-ipvs0", that is success.
ip add|grep ipvs
ipvsadm -Ln

authors: 20988902 Aisuko alexandrem kenperkins ntcong prachidamle rdegez soumyalj ulm0

repo: rancher/rancher


text:
Clusters created with Rancher are Unavailable after Rancher update

What kind of request is this (question/bug/enhancement/feature request):
issue
Result:
They are not unavailable intermittently but constantly. That is why I am opening different issue then #16649
I have two clusters created via Rancher UI. After update to 2.1.1 both clusters are Unavailable with message:
This cluster is currently Unavailable; areas that interact directly with it will not be available until the API is ready.
kubectl commands to the cluster however work
Other details that may be helpful:
I'v tried restoring to three new nodes, but the clusters are still Unavailable
Environment information

Rancher version (rancher/rancher/rancher/server 2.1.1):
Installation option (HA on 3 nodes):

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
Machine type (VM)
Kubernetes version (use kubectl version):

Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.1"

Docker (use docker info):

17.03.2-ce

Logs from cattle-cluster-agent
INFO: Environment: CATTLE_ADDRESS=10.42.6.195 CATTLE_CA_CHECKSUM=61e69e49f6f6142a19580dfeb6f8ed45c5f8eea5cfa2566e9c94f567b72a3e76 CATTLE_CLUSTER=true CATTLE_INTERNAL_ADDRESS= CATTLE_K8S_MANAGED=true CATTLE_NODE_NAME=cattle-cluster-agent-8676d8bf9d-jc24r CATTLE_SERVER=https://rancher.mydomain.com
INFO: Using resolv.conf: nameserver 10.43.0.10 search cattle-system.svc.cluster.local svc.cluster.local cluster.local mydomain.localdomain options ndots:5
INFO: https://rancher.mydomain.com/ping is accessible
INFO: Value from https://rancher.mydomain.com/v3/settings/cacerts is an x509 certificate
time="2018-11-21T14:32:34Z" level=info msg="Rancher agent version v2.1.1 is starting"
time="2018-11-21T14:32:34Z" level=info msg="Listening on /tmp/log.sock"
time="2018-11-21T14:32:34Z" level=info msg="Connecting to wss://rancher.mydomain.com/v3/connect/register with token rqb42q6b7pfq72m57h4gvr88v8fq57s5vvb9mfbrqvh2wmxmfqbhpd"
time="2018-11-21T14:32:34Z" level=info msg="Connecting to proxy" url="wss://rancher.mydomain.com/v3/connect/register"
time="2018-11-22T12:08:30Z" level=error msg="Failed to connect to proxy" error="read tcp 10.42.6.195:41328->5.39.110.248:443: i/o timeout"
time="2018-11-22T12:08:40Z" level=info msg="Connecting to wss://rancher.mydomain.com/v3/connect with token rqb42q6b7pfq72m57h4gvr88v8fq57s5vvb9mfbrqvh2wmxmfqbhpd"
time="2018-11-22T12:08:40Z" level=info msg="Connecting to proxy" url="wss://rancher.mydomain.com/v3/connect"

Logs from cattle-server
2018/11/22 12:23:54 [INFO] Handling backend connection request [c-p9r82]
2018/11/22 12:23:55 [INFO] 2018/11/22 12:23:55 http: multiple response.WriteHeader calls
2018/11/22 12:23:57 [INFO] 2018/11/22 12:23:57 http: multiple response.WriteHeader calls
2018/11/22 12:24:01 [INFO] 2018/11/22 12:24:01 http: multiple response.WriteHeader calls
2018/11/22 12:24:01 [INFO] error in remotedialer server [400]: read tcp 10.42.3.9:80->192.168.71.224:58615: i/o timeout

Any tips anyone?


text:
Reserved wheel greater than circumference of circle for a while when add a node

Version: Master 2.2 (3/4/19)
What kind of request is this (question/bug/enhancement/feature request):
Bug, Minor
Steps to reproduce (least amount of steps as possible):

Have a cluster with 1 node. Enable monitoring. View the Cluster page to see the wheels.
Add a node, quickly go back to the cluster page while the node is provisioned.

Result:
After a while you will see the CPU reserved wheel will probably circle around itself especially if your nodes only have a couple of CPUs. It looks like we don't have prometheus information yet so it's hard to see in the picture but we have 1.7 of 4 Reserved and 0.4 of 2 Used. This disparity likely is what causes the issue.

Once prometheus is up and we have info this is fixed without a refresh of the page. But it can look like this for 30-60 seconds.
Other details that may be helpful:
Master 2.2 (3/4/19) on HA Setup

What's happening is that as soon as the node appears we know how much is reservable, but it takes some time for Prometheus to have data for it.  (You can see below the hover that it's 1.7 of 4 reserved, so another 2gb node appeared)
So the scale of the wheel should go from 0 to max(usable, reservable) (in this case max(2,4) == 4).  That will make the "used" part only take up half of the wheel and its gray area stop at the top in this case, temporarily until prometheus stats come in.
I also think we should probably drop the black outline thing and the center dot in general.  They're too busy and nobody knows what they mean.  How about just a small marker at the min/max individual node point, if they're at least a far enough away from the average to be fully displayed? (maybe 5% different?  You'll need to play with it)
Top-quality artist's rendering:

@loganhz FYI I am now seeing this on latest master staying. It will never go away unless I manually refresh or leave the page and come back. Probably not completely necessary for v2.2 but if it's an easy fix would be nice to fix in my opinion:

sure, we will look at it today.

@davidnuzik fixed and moved into 2.2

This isn't the fix I was taking about, you're just capping it at 100%. Both wheels should be based on the same scale, from 0 to max(2,4) = 4 for the CPU example.

Then the inner wheel gray should end at the top of the wheel (2 is half of the max of 4) because the rest is not possible (yet), and the green fill 54% of that gray area (which is the same as 1.1/4 if the whole wheel).

Move it out from 2.2 as there is still something need to be changed.

Close it as the outline has been removed

authors: davidnuzik loganhz vincent99


text:
Host View: Provide list of used ports

It would be nice to be able to see all the used ports on a host by containers.

Duplicate of #1628


text:
[Bug] Authentication Proxy does not work with Skaffold (blocks on rollout status)

What kind of request is this (question/bug/enhancement/feature request):
Bug related to https://github.com/GoogleContainerTools/skaffold/issues/5810
Steps to reproduce (least amount of steps as possible):
Manage a cluster via rancher
Get the kubeconfig for the cluster and make sure your context is set to accessing the cluster via the rancher url (proxy mode) and not via the Authenticated Cluster Endpoint
Try using skaffold with the kubectl deployer and a deployment manifest (can be any simple deployment):
skaffold.yaml
apiVersion: skaffold/v2beta13
kind: Config
metadata:
  name: minimal-example
deploy:
  kubectl:
    manifests:
    - deployment.yaml

deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: minimal
spec:
  replicas: 3
  selector:
    matchLabels:
      app: minimal
  template:
    metadata:
      labels:
        app: minimal
    spec:
      containers:
      - name: minimal
        image: busybox
        command:
          - sleep
        args:
          - "10000"

Result:
Skaffold gets stuck at waiting for deployments to stabilize https://github.com/GoogleContainerTools/skaffold/issues/5810 and only converges after approximately 7 minutes
Other details that may be helpful:
Directly accessing the cluster via the api server authorized endpoint instead of the endpoint proxied by the rancher server works fine. So it appears that there is either missing functionality or some sort of weird caching behavior in play.
Happens for all kinds of downstream clusters such as k3s or rke spawned by rancher.
Environment information

Rancher version 2.5.8
Installation option (single install/HA): HA

Moving this back to test, as I can no longer reproduce in 2.6-head. Both contexts complete in around 7 seconds, whereas in v2.6.2, the proxy completes in about 30 seconds.

@Blackclaws , wondering if you can validate if this is working as expected on v2.6-head image? (https://hub.docker.com/r/rancher/rancher/tags).

I can try validating it on a standalone installation or I can wait until 2.6.3 is released to validate it on our production system.

@Blackclaws , thank you for getting back to me. It would be great if you could validate it on a standalone installation prior in the next week or so - so we're sure it's actually fixed. Is this something you can do?

I've tried it on our production system by upgrading a copy of that to head. Issue persists. I'll try it on a standalone system as well.

A compounding issue is that as of rancher 2.6 the authorized endpoint is also broken for Keycloak backed users:
https://github.com/rancher/rancher/issues/35187

@Blackclaws still working on this, but still having some issues reproducing. Would you mind sharing some of the following information regarding your setup?

What kind of clusters are these (AKS, imported etc.)?
What kubernetes version is being used?
What version of skaffold is being used?

Also any information regarding either skaffold or the command kubectl -v 10 --context test-cluster rollout status deployment minimal --namespace default --watch=false  blocking would be appreciated, as I haven't been able to reproduce comparable results with either.

Sure I'll help you as much as I can to reproduce this, I'll try to get a minimal example working as well if possible

RKE rancher launched clusters.
1.21.5 in production 1.22.4 in the test I did
Skaffold version 1.23.0

However skaffold version is not relevant as the blocking kubectl command itself shows the issue without even using skaffold.

It indeed seems fixed for new rancher setups. The existing production setup still has this issue. Setting up a new rancher starting at least from 2.5.10 doesn't show this issue, for whatever reason that may be.
Since I can't reproduce this on a new install it seems this issue has something to do with something that happened in the past with our system. I think closing this issue is probably the best right now. I'll just setup the production system again over the holidays. If the issue does crop back up I'll reopen a new issue, or you can keep this issue open for a while, your choice.

following the comment instructions here, I was also unable to reproduce this issue using rancher v2.6.4-rc3.

authors: Blackclaws jakefhyde slickwarren snasovich


text:
Host registration url is not generated when "Add Host" for custom is launched for the first time.

Rancher Version: v0.61.0-rc3
Docker Version:10.1.
OS: Ros - v0.4.4-dev-2
Steps to Reproduce: On fresh install of rancher-server , launch "Add Host" for custom.
Notice that UI is stuck when generating the registration url. When this page is relaunched , registration url shows up as expected.

This was broken by changes to only connect to the subscribe socket when in a /env/1aX/... URL, which was a bad idea.  So yeah, now it stays connected more.

Version - master 3/2
Verified fixed

authors: sangeethah tfiduccia vincent99


text:
Rancher is inaccessible

Hello Team
Request you to fix it as our team is facing issues in accessing Rancher for the past few weeks.
Thanks.

Useful
Info

Versions
Rancher v2.5.7 UI: v2.5.6

Route
undefined

Hello, can you add details to this issue? What do you see when you try to access rancher? Can you provide a screenshot with any sensitive/personal info redacted?

Also, I see that it says your UI is on v2.5.6 while rancher is on v2.5.7. Can you explain how you changed the UI version? It may be related.

.

.

authors: nimisha-rci rmweir


text:
[BUG] after rancher upgrade: pvc stays pending, wants to use csi driver instead of aws-ebs plugin

Rancher Server Setup

Rancher version: 2.6.9

Information about the Cluster

Kubernetes version: v1.24.8
Cluster Type: Downstream, AWS ec2 instances

Describe the bug
We recently updated rancher version from 2.5.15 to 2.6.9 and downstream cluster k8s version from 1.20.15 to 1.24.8
Now creation of a pvc leads to an error:
  Type    Reason                Age                    From                         Message
  ----    ------                ----                   ----                         -------
  Normal  ExternalProvisioning  118s (x26 over 7m52s)  persistentvolume-controller  waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator

To Reproduce
Update Rancher version from 2.5.15 to 2.6.9
Update downstream cluster k8s version from 1.20.15 to 1.24.8
request_pvc.yaml:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: scjo-test
  namespace: operations
spec:
  accessModes:
    - ReadWriteOnce
  volumeMode: Block
  resources:
    requests:
      storage: 10Gi

kubectl create -f request_pvc.yaml -n operations
persistentvolumeclaim/scjo-test created

Result
pvc stays in pending state:
kubectl describe pvc scjo-test -n operations
Name:          scjo-test
Namespace:     operations
StorageClass:  aws-ebs-gp2
Status:        Pending
Volume:
Labels:        <none>
Annotations:   volume.beta.kubernetes.io/storage-provisioner: ebs.csi.aws.com
               volume.kubernetes.io/storage-provisioner: ebs.csi.aws.com
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Block
Used By:       <none>
Events:
  Type    Reason                Age                    From                         Message
  ----    ------                ----                   ----                         -------
  Normal  ExternalProvisioning  118s (x26 over 7m52s)  persistentvolume-controller  waiting for a volume to be created, either by external provisioner "ebs.csi.aws.com" or manually created by system administrator

Expected Result
pvc should be bound, this output is from another cluster where no upgrades were done:
kubectl describe pvc scjo-test --context k8s-bo-prod-default -n operations
Name:          scjo-test
Namespace:     operations
StorageClass:  aws-ebs-gp2
Status:        Bound
Volume:        pvc-152904e0-71d7-45ea-86f7-4df1a1b38c78
Labels:        <none>
Annotations:   pv.kubernetes.io/bind-completed: yes
               pv.kubernetes.io/bound-by-controller: yes
               volume.beta.kubernetes.io/storage-provisioner: kubernetes.io/aws-ebs
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      10Gi
Access Modes:  RWO
VolumeMode:    Block
Used By:       <none>
Events:
  Type    Reason                 Age   From                         Message
  ----    ------                 ----  ----                         -------
  Normal  ProvisioningSucceeded  20s   persistentvolume-controller  Successfully provisioned volume pvc-152904e0-71d7-45ea-86f7-4df1a1b38c78 using kubernetes.io/aws-ebs

Additional info
No change was done on the storage classes and default storage class is gp2. There is also one for gp3 and io1.
I found nothing related in the release notes.
It seems that the only solution is to install the csi driver https://github.com/kubernetes-sigs/aws-ebs-csi-driver
Still, based on the information in https://ranchermanager.docs.rancher.com/v2.6/how-to-guides/new-user-guides/manage-clusters/create-kubernetes-persistent-storage/manage-persistent-storage/dynamically-provision-new-storage#docusaurus_skipToContent_fallback the aws-ebs plugin is still available in rancher, so my use case should work also without csi driver.

Just for info: After installation of https://github.com/kubernetes-sigs/aws-ebs-csi-driver it works again.
Still I wonder why the Rancher release notes don't mention this change.


text:
IP address fails to be injected for the ingress when it is created in a namespace that has "-"

Rancher Version: v1.1.0-dev5
Steps to reproduce the problem:
Create a namespace - "ingress-test" ( with "-" in it)
Created 2 services and ingress rule in this namespace.
Ingress gets created successfully and i also see the lb-ingress instance being programmed for the rules. But IP inject on the ingress object fails

ingress-controller logs:
6/21/2016 9:41:51 AMtime="2016-06-21T16:41:51Z" level=info msg="Event(api.ObjectReference{Kind:\"Ingress\", Namespace:\"ingress-test\", Name:\"ingress1\", UID:\"0ded6334-37cf-11e6-9fbe-020842bc4153\", APIVersion:\"extensions\", ResourceVersion:\"17637\", FieldPath:\"\"}): type: 'Normal' reason: 'CREATE' ingress-test/ingress1"
6/21/2016 9:41:51 AMtime="2016-06-21T16:41:51Z" level=info msg="LB [ingress-test-ingress1] is not ready yet, skipping endpoint update"

controller-manager.logs
6/21/2016 9:41:35 AMI0621 16:41:35.967148       1 rancher.go:107] GetLoadBalancer [lb-a04c8989237cf11e69fbe020842bc415] [Region1]
6/21/2016 9:41:36 AMI0621 16:41:36.473839       1 event.go:211] Event(api.ObjectReference{Kind:"ReplicationController", Namespace:"ingress-test", Name:"k8testrc1", UID:"04deea8e-37cf-11e6-9fbe-020842bc4153", APIVersion:"v1", ResourceVersion:"17581", FieldPath:""}): type: 'Normal' reason: 'SuccessfulCreate' Created pod: k8testrc1-5s4pd
6/21/2016 9:41:36 AMI0621 16:41:36.562793       1 event.go:211] Event(api.ObjectReference{Kind:"ReplicationController", Namespace:"ingress-test", Name:"k8testrc1", UID:"04deea8e-37cf-11e6-9fbe-020842bc4153", APIVersion:"v1", ResourceVersion:"17581", FieldPath:""}): type: 'Normal' reason: 'SuccessfulCreate' Created pod: k8testrc1-q8kec
6/21/2016 9:41:45 AMI0621 16:41:45.799788       1 rancher.go:107] GetLoadBalancer [lb-a0a9f83e437cf11e69fbe020842bc415] [Region1]
6/21/2016 9:41:45 AMI0621 16:41:45.888499       1 event.go:211] Event(api.ObjectReference{Kind:"ReplicationController", Namespace:"ingress-test", Name:"k8testrc2", UID:"0ab11629-37cf-11e6-9fbe-020842bc4153", APIVersion:"v1", ResourceVersion:"17611", FieldPath:""}): type: 'Normal' reason: 'SuccessfulCreate' Created pod: k8testrc2-yl72z
6/21/2016 9:41:45 AMI0621 16:41:45.892203       1 event.go:211] Event(api.ObjectReference{Kind:"ReplicationController", Namespace:"ingress-test", Name:"k8testrc2", UID:"0ab11629-37cf-11e6-9fbe-020842bc4153", APIVersion:"v1", ResourceVersion:"17611", FieldPath:""}): type: 'Normal' reason: 'SuccessfulCreate' Created pod: k8testrc2-gmgz5
6/21/2016 9:43:47 AMI0621 16:43:47.089384       1 servicecontroller.go:298] LB doesn't need update for service default/kubernetes
6/21/2016 9:43:47 AMI0621 16:43:47.093599       1 servicecontroller.go:298] LB doesn't need update for service ingress-test/k8test1
6/21/2016 9:43:47 AMI0621 16:43:47.145147       1 servicecontroller.go:298] LB doesn't need update for service ingress-test/k8test2

Sangeethas-MacBook-Pro:k8s sangeethahariharan1$ cat service2_ingress.yml
apiVersion: v1
kind: Service
metadata:
 name: k8test2
 labels:
   k8s-app: k8test2-service
spec:
 ports:
 - port: 80
   targetPort: 80
   protocol: TCP
   name: http
 selector:
   k8s-app: k8test2-service
---
apiVersion: v1
kind: ReplicationController
metadata:
 name: k8testrc2
spec:
 replicas: 2
 selector:
   k8s-app: k8test2-service
 template:
   metadata:
     labels:
       k8s-app: k8test2-service
   spec:
     terminationGracePeriodSeconds: 60
     containers:
     - name: testcontainer
       image: sangeetha/testnewhostrouting
       ports:
       - containerPort: 80
Sangeethas-MacBook-Pro:k8s sangeethahariharan1$ cat service1_ingress.yml
apiVersion: v1
kind: Service
metadata:
 name: k8test1
 labels:
   k8s-app: k8test1-service
spec:
 ports:
 - port: 81
   targetPort: 81
   protocol: TCP
   name: http
 selector:
   k8s-app: k8test1-service
---
apiVersion: v1
kind: ReplicationController
metadata:
 name: k8testrc1
spec:
 replicas: 2
 selector:
   k8s-app: k8test1-service
 template:
   metadata:
     labels:
       k8s-app: k8test1-service
   spec:
     terminationGracePeriodSeconds: 60
     containers:
     - name: testcontainer
       image: sangeetha/testnewhostrouting
       ports:
       - containerPort: 81
Sangeethas-MacBook-Pro:k8s sangeethahariharan1$ cat ingress_1.yml
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
 name: ingress1
spec:
 rules:
 - host: foo.bar.com
   http:
     paths:
     - path: /service3.html
       backend:
         serviceName: k8test1
         servicePort: 81
     - path: /name.html
       backend:
         serviceName: k8test2
         servicePort: 80
Sangeethas-MacBook-Pro:k8s sangeethahariharan1$

Tested with v1.2.0-pre1-rc4 and kubernetes 1.3.0 ( rancher/k8s:v1.3.0-rancher3).
This issue is not seen anymore.
Ip injection for ingress created in namespace that has "-" succeeds.


text:
LoadBalancer and Access Logs

Aggregating all issues here about the LB, I can't find a sane way to make access logs available on the load balancer.
Any one can help me with this? (specially making them available in the log stream of docker and / or pushing it to an ELK Stack)
i think the documentation could be updated about this also, since access logs seem to be quite important (of course one option would be to proxy the request through one more application, but is that really the solution?)

Duplicate of https://github.com/rancher/rancher/issues/2414

authors: Daxten deniseschannon


text:
No attempt made to start containers for global services.

Rancher Version: v1.3.0-rc1
Steps to reproduce the problem:
Created a environment with "kubernetes" templates.
Added 1 host to the setup.
Infra stacks are not able to start successfully.
There is no attempt made to start containers for netwrok-services stack. Both the services under this stack are global services.

Tested with Rancher Version: v1.3.0-rc1
This issue is not seen anymore


text:
Can't reach internal host from some other hosts

Rancher Versions:
Server: 1.5.3
healthcheck: 0.2.3
ipsec: 0.9.4
network-services: 0.8.11/0.5.3
scheduler: 0.7.5
Docker Version:
1.12.6
OS and where are the hosts located? (cloud, bare metal, etc):
custom provider
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
HA Rancher (3 nodes)+ External DB
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
I don't know where to start to reproduce the bug. I've a cluster with 100 machines registred.
I've created a HDFS Cluster stack and another service depending on hdfs (named hdfs)
All my infrastructure stack are green.
On various host, I can't reach HDFS Cluster by internal IP.
When I try to ping the hdfs host
ping hdfs
PING hdfs.rancher.internal (10.42.60.109) 56(84) bytes of data.

With no end...
But if I curl the public address, I can reach the port:
curl public_ip:50070
<some html>

How can I debug this ?

@XciD are you able to ping other ipsec containers? The output from this should be helpful
for i in `curl -s rancher-metadata/latest/self/service/containers/` ; do id=$(echo $i| cut -f1 -d=) ; name=$(echo $i| cut -f2 -d=) ; echo " ---- $name --------" ; ping -c2 `curl -s curl rancher-metadata/latest/self/service/containers/$id/primary_ip` ; done

Fixed by removing and readding the host.
Thanks for the command, will try this when reappear

authors: XciD aemneina


text:
Make TLS version and ciphers configurable

https://github.com/rancher/rancher/issues/15885

Because of the second tls.Config for ACME, I moved the settings.*.Get() to the lookup functions so they can be re-used.


text:
Patch the missing Monitoring metrics

Problem:

Cannot see the workload/container/pod metrics as ProjectMetricGraph has been deleted.
Although delete monitoring action from schema resources, UI still can
seen enableMonitoring action link

Solution:

Cannot delete ProjectMetricGraph directly.
Remove actions addition from Formatter

Issue:

https://github.com/rancher/rancher/issues/19516
https://github.com/rancher/rancher/issues/19528

LGTM

Can you check Drone failures @thxCode @orangedeng. Looks like the tests fail in the project creation area

LGTM

authors: alena1108 orangedeng thxCode


text:
Bump UI tags to v2.6.7-rc4

Bumping UI tags to v2.6.7-rc4

78017e64e3c3df400926f924781b3104bafc20d0

authors: VladimirSeleznev jakefhyde


text:
Add ChartDefaultURL to support custom rancher-charts repo in testing

Problem
When testing different fleet builds in Rancher, we need to set up a fork of rancher/charts (described here: https://github.com/rancher/fleet/blob/master/DEVELOPING.md#fleet-in-rancher---using-a-custom-fork).
However we don't want to (should not) create a test branch in rancher/charts directly, so we have to change the rancher code and change the hard coded URL.
Solution
This adds a setting for ChartDefaultURL (env var CATTLE_CHART_DEFAULT_URL), which will be used for rancher-charts when the controller is started and adds its repos.
Testing
Since we only use this variable for dev purposes, everything should work as before.

I think it's best to revert this merge.


text:
CI Runner Fix

Update provisioning test to find old drone containers and clean them up before starting rancher.

Changes were added via https://github.com/rancher/rancher/pull/41722, so this can be closed.


text:
rio up overrides services from different stacks without warning

Describe the bug
rio up with different stack names --name test1/2 overrides services from the previous deploy without a warning.
To Reproduce
Steps to reproduce the behavior:
Create a minimal Riofile:
services:
  nginx:
    image: nginx
    ports:
    - 80/http,webtest
    scale: 1

and run
rio up --name stack1
rio up --name stack2

The second up silently takes over stack1. This is not to problematic in this instance but would be worse if those were two completly different Riofiles
Expected behavior
A warning/error should be displayed.

Similar to https://github.com/rancher/rio/issues/733 but this case has same riofile

Another similar case:

rio up -f Riofile
rio up http://...

Both of these will use CWD as stack name and overwrite each other.

repo: rancher/rio


text:
Declare all script targets as phony

Signed-off-by: Stephen Kitt skitt@redhat.com

@skitt there's some conflict now. Github's UI get's stuck when trying to resolve here. Can you fix it? :)

@skitt there's some conflict now. Github's UI get's stuck when trying to resolve here. Can you fix it? :)

@mangelajo done!

authors: mangelajo skitt

repo: rancher/submariner


text:
Eks options

Adding region, instance type, and min and max node options to EKS config.
Issue:
https://github.com/rancher/rancher/issues/14064

lgtm

authors: StrongMonkey nathan-jenan-rancher

repo: rancher/types


text:
Updated python agent to include docker version fixes

bumping up the version.

LGTM

authors: cloudnautique sonchang

repo: rancherio/cattle

license_source: bigquery


text:
Support docker 1.7 volume plugin

Integrate our volmgr with docker 1.7 volume plugin.

#1278

repo: rancherio/rancher


text:
[UI] [Host] When I get an error for my access token, the error message doesn't disappear when I leave the Add Host page and come back.

Version: v0.13.1
Steps to Reproduce:

Try to add host with invalid DO token.
Don't add a host and click on Container page.
Click on 'Add Host' page again.

Result: All fields are reset, but the error message still remains.
Expected Result: Error Message would disappear from the UI.
Since the add host page resets everything upon loading, the error message also needs to be hidden on each loading of the page.

v0.16.0
Verified Fixed

authors: deniseschannon tfiduccia


text:
Changelogs for 1-Year shifting/acceleration and sensitivities calculation

Changes made to "Pathways to Net Zero - 1-Year Shifting.xlsx" (compared to the original "Pathways to Net Zero.xlsx"): for spreadsheets BREEZE, GALE, STORM, the following cells' formulae are changed:

H26 =H25 * (1 + RRI(COUNT($B$26:$B$55), H$25,H$55))
is changed to
H26 =H25 * (1 + RRI(COUNT($B$26:$B$55), H$25,H$55)) * (1 + RRI(COUNT($B$26:$B$55), H$25,H$55))
(double deployment for year 2021; all following years will be changed accordingly because H[n]=H[n-1] * (1 + RRI(COUNT($B$26:$B$55), H$25,H$55)) for all following n's)
P36 =P35 * (1 + RRI(COUNT($B$36:$B$55), P$35,P$55))
is changed to
P36 =P35 * (1 + RRI(COUNT($B$36:$B$55), P$35,P$55)) * (1 + RRI(COUNT($B$36:$B$55), P$35,P$55))
(double deployment for year 2031; all following years will be changed accordingly because P[n]=P[n-1] * (1 + RRI(COUNT($B$26:$B$55), H$25,H$55)) for all following n's)
X26:X54 =$X$55Deployment!D3:D31
is changed to
X26:X54 =$X$55Deployment!D4:D32
(shifting deployment rate from D3:D31 to D4:D32 from the "Deployment" spreadsheet)
Y26:Y54=$Y$55 * Deployment!D3:D31
is changed to
Y26:Y54=$Y$55 * Deployment!D4:D32
(shifting deployment rate from D3:D31 to D4:D32 from the "Deployment" spreadsheet)
(after the above modifications, the original "Pathways to Net Zero.xlsx" is saved as "Pathways to Net Zero - 1-Year Shifting.xlsx")

From the original "Pathways to Net Zero.xlsx" and the 1-Year shifted "Pathways to Net Zero - 1-Year Shifting.xlsx", copy the "Outputs" spreadsheet and save as "Pathways to Net Zero - Original - Outputs with Total capex opex revenue.xlsx" and "Pathways to Net Zero - 1-Year Shifting - Outputs with Total capex opex revenue.xlsx", and then in both newly saved spreadsheet, add new rows in grey to calculate total capex, opex, revenue among all technologies, for all 3 scenarios Breeze, Gale, Storm. And then copy only the key outputs values in grey and save them as "Pathways to Net Zero - Original - Outputs - Key outputs Only.xlsx" and "Pathways to Net Zero - 1-Year Shifting - Outputs - Key outputs Only.xlsx", which contain less enough information to be uploaded to GitHub netzerotc/environment/sensitivities/. Then extract only the summed total capex, total opex, total revenue, for all 3 scenarios, and save as "Pathways to Net Zero - Original - Total capex.xlsx", "Pathways to Net Zero - Original - Total revenue.xlsx", "Pathways to Net Zero - Original - Total opex.xlsx" for original, and save as "Pathways to Net Zero - 1-Year Shifting - Total capex.xlsx", "Pathways to Net Zero - 1-Year Shifting - Total revenue.xlsx", "Pathways to Net Zero - 1-Year Shifting - Total opex.xlsx" for 1-Year Shifting. Again, they are safe to be uploaded to GitHub.

Copy the key outputs values in grey in "Pathways to Net Zero - 1-Year Shifting.xlsx" - "Outputs" to "OGTC-ORE Catapult IEV pathways economic model v01.06 FINAL.xlsx" - "Pathway Inputs", switch to "Master Sheet" spreadsheet within the workbook, press F9 to update, save it as "OGTC-ORE Catapult IEV pathways economic model v01.06 FINAL - 1-Year Shifting F9 Update.xlsx", and then copy the rows containing total jobs (with and without induced) for all 3 scenarios to a new spreadsheet and save it as "IEV - 1-Year Shifting - Total Jobs.xlsx" (without induced jobs) and/or "IEV - 1-Year Shifting - Total Jobs Including Induced.xlsx" (with induced jobs). Switch to the original "OGTC-ORE Catapult IEV pathways economic model v01.06 FINAL.xlsx" and copy the original total jobs with and without induced to new spreadsheets and save as "IEV - Original - Total Jobs.xlsx" and "IEV - Original - Total Jobs Including Induced.xlsx". These 4 newly saved spreadsheets contain less enough information to be uploaded to GitHub netzerotc/environment/sensitivities/.

Adding total economic impact: in both "OGTC-ORE Catapult IEV pathways economic model v01.06 FINAL.xlsx" and "OGTC-ORE Catapult IEV pathways economic model v01.06 FINAL - 1-Year Shifting F9 Update.xlsx", add new rows to sum over economic impacts of all different technologies (in grey background only: without doubling counting the offshore wind to power/green H2 with the total offshore wind), and then save as "OGTC-ORE Catapult IEV pathways economic model v01.06 FINAL Original - Adding Total Economic Impact.xlsx" and "OGTC-ORE Catapult IEV pathways economic model v01.06 FINAL 1-Year Shifting - Adding Total Economic Impact.xlsx". Then similar to step 3 for total jobs above, copy the total economic impacts for 3 scenarios for original and 1-Year Shifting to new spreadsheets and save as "IEV - Original - Total Economic Impact.xlsx" and "IEV - 1-Year Shifting - Total Economic Impact.xlsx". Again, these 2 spreadsheets contain no sensitive information and can be uploaded to GitHub.

For carbon emissions cost/rewards, in terms of carbon tax for uncaptured carbon: from the spreadsheet "CCUS" of both "Pathways to Net Zero - 1-Year Shifting.xlsx" and "Pathways to Net Zero - Original.xlsx", copy row 57, 68, 79 of carbon tax for uncaptured carbon for 3 scenarios to new spreadsheets and save as "Pathways to Net Zero - Original - Carbon tax for uncaptured carbon.xlsx" and "Pathways to Net Zero - 1-Year Shifting - Carbon tax for uncaptured carbon.xlsx". These 2 newly saved spreadsheets contain no sensitive information and can be uploaded to GitHub.

Sensitivities calculations for total capex, total opex, total revenue, total jobs, emissions, total economic impacts:

For all except capex, sensitivities ratios are calculated by 1-Year shifted spreadsheet's n-th year's value divided by original spreadsheet's (n+1)-th year's value, for example, using "Pathways to Net Zero - Original - Total opex.xlsx" and "Pathways to Net Zero - 1-Year Shifting - Total opex.xlsx", 2022's value in 1-Year shifted spreadsheet is divided by 2023's value in original spreadsheet, and this is the sensitivity ratio for year 2022, and these are saved as "Pathways to Net Zero - Total opex Sensitivity Ratio for 1-Year Shifting.csv".
For total capex, sensitivities ratios are initially calculated as above, but then for the boundary year 2021, the 2021's value in 1-Year shifted spreadsheet is subtracted by 2021's value in the original spreadsheet, and then divided by 2022's value in original spreadsheet.
In summary:
Pathways to Net Zero - Total capex Sensitivity Ratio for 1-Year Shifting.csv
is calculated from:
Pathways to Net Zero - 1-Year Shifting - Total capex.xlsx
Pathways to Net Zero - Original - Total capex.xlsx
Pathways to Net Zero - Total opex Sensitivity Ratio for 1-Year Shifting.csv
is calculated from:
Pathways to Net Zero - 1-Year Shifting - Total opex.xlsx
Pathways to Net Zero - Original - Total opex.xlsx
Pathways to Net Zero - Total revenue Sensitivity Ratio for 1-Year Shifting.csv
is calculated from:
Pathways to Net Zero - Original - Total revenue.xlsx
Pathways to Net Zero - 1-Year Shifting - Total revenue.xlsx
IEV - Total Economic Impact Sensitivity Ratio for 1-Year Shifting.csv
is calculated from:
IEV - Original - Total Economic Impact.xlsx
IEV - 1-Year Shifting - Total Economic Impact.xlsx
Pathways to Net Zero - Total emissions (uncaptured carbon tax) Sensitivity Ratio for 1-Year Shifting.csv
is calculated from:
Pathways to Net Zero - Original - Carbon tax for uncaptured carbon.xlsx
Pathways to Net Zero - 1-Year Shifting - Carbon tax for uncaptured carbon.xlsx
IEV - Total Jobs Sensitivity Ratio for 1-Year Shifting.csv
is calculated from:
IEV - 1-Year Shifting - Total Jobs.xlsx
IEV - Original - Total Jobs.xlsx
IEV - Total Jobs Including Induced Sensitivity Ratio for 1-Year Shifting.csv
is calculated from:
IEV - Original - Total Jobs Including Induced.xlsx
IEV - 1-Year Shifting - Total Jobs Including Induced.xlsx
All these files contain no sensitive information and can be uploaded to GitHub.

Added relevant codes in env.py to read the original 6 rewards values into the Parameters.IEV_Rewards from the following 6 files:
Pathways to Net Zero - Original - Total capex.xlsx
Pathways to Net Zero - Original - Total opex.xlsx
Pathways to Net Zero - Original - Total revenue.xlsx
IEV - Original - Total Economic Impact.xlsx
Pathways to Net Zero - Original - Carbon tax for uncaptured carbon.xlsx
IEV - Original - Total Jobs.xlsx (or IEV - Original - Total Jobs Including Induced.xlsx)
Also added relevant codes in env.py to read the sensitivity ratios into the Parameters.IEV_RewardSensitivities from the following 6 files:
Pathways to Net Zero - Total capex Sensitivity Ratio for 1-Year Shifting.csv
Pathways to Net Zero - Total opex Sensitivity Ratio for 1-Year Shifting.csv
Pathways to Net Zero - Total revenue Sensitivity Ratio for 1-Year Shifting.csv
IEV - Total Economic Impact Sensitivity Ratio for 1-Year Shifting.csv
Pathways to Net Zero - Total emissions (uncaptured carbon tax) Sensitivity Ratio for 1-Year Shifting.csv
IEV - Total Jobs Sensitivity Ratio for 1-Year Shifting.csv (or IEV - Total Jobs Including Induced Sensitivity Ratio for 1-Year Shifting.csv)

Potential issues and questions:
The total capex is the sum of capex of offshore wind, green hydrogen, blue hydrogen, oil & gass, CCUS. When shifting the deployment by 1 year, the capex of green and blue hydrogen has the correct boundary behavior: 2021's new capex is close to 2021+2022 old capex, but for other technologies' capex, this is not true as we are not directly accelerating the deployment of them. When adding them together to get the total capex, it might not be reasonable to calculate the boundary year as above. Instead, it might be more reasonable to calculate them separately: non-accelerating techs' capex boundary calculated as without boundary using 2021's new, accelerating techs' capex boundary calculated by (2021's new - 2021's old), then sum these together, and then divided by 2022's old total capex. However, things will get even more complicated because starting from 2031, the deployment of "offshore wind capacity in GW" will start to accelerate by 1 year at the beginning, so this special treatment of boundary may have to do again for 2031.

Changelogs for approximating partial derivatives of jobs & economic impact w.r.t. capex using the IEV economic model:

In the original "Pathways to Net Zero.xlsx", duplicate the "Output" spreadsheet and rename it as "Outputs - capex+Delta100", and for all 3 scenarios, for green & hydrogen capex, manually add 100 to the original numbers starting from 2021, and for offshore wind capex, manually add 100 to the original numbers starting from 2031. This was done by first copying and pasting the links of the original numbers to a blank row, editing the formula by adding +100, dragging the cell to auto fill the +100 formula, and finally copying and pasting the values back to the original cells, and then delete the contents in the originally blank cells.

Save this modified spreadsheet as "Pathways to Net Zero - Original with new sheet Outputs - capex+Delta100.xlsx", and same as Step 3 & 4 in the post/comment above, copy key outputs values in grey in the Delta=100 applied spreadsheet "Outputs - capex+Delta100" above to the IEV model's workbook's "Pathway Inputs" spreadsheet, and then press F9 to update the total jobs and total economic impact in the "Master Sheet", and then save the updated IEV model workbook as "OGTC-ORE Catapult IEV pathways economic model v01.06 FINAL capex+Delta100 - Adding Total Economic Impact.xlsx". Both this workbook xlsx and the "Pathways to Net Zero - Original with new sheet Outputs - capex+Delta100.xlsx" have been uploaded to MS Teams.

Same as Step 3 & 4 in the post/comment above, extract the updated total jobs and total economic impact to new spreadsheets, and save them as "IEV - capex+Delta100 - Total Jobs.xlsx" and "IEV - capex+Delta100 - Total Economic Impact.xlsx", respectively. Similar to the post/comment above, these 2 saved spreadsheets contain no sensitive information and can be uploaded to GitHub.

Calculating/approximating the partial derivatives (details can be found in https://github.com/rangl-labs/netzerotc/issues/13#issuecomment-915383934) by $\frac{ r^{\mathrm{eco}}_k (\chi^{\mathrm{cap}}_k+\Delta, \chi^{\mathrm{op}}_k, r^{\mathrm{rev}}_k) - r^{\mathrm{eco}}_k (\chi^{\mathrm{cap}}_k, \chi^{\mathrm{op}}_k, r^{\mathrm{rev}}_k) }{ \sum \Delta }$, where the new $r^{\mathrm{eco}}_k (\chi^{\mathrm{cap}}_k+\Delta, \chi^{\mathrm{op}}_k, r^{\mathrm{rev}}_k)$ are saved in "IEV - capex+Delta100 - Total Jobs.xlsx" and "IEV - capex+Delta100 - Total Economic Impact.xlsx", respectively, and the total capex change is $\sum \Delta=200$ in the denominator from 2021, and $\sum \Delta=300$ from 2031. The calculated derivatives are saved in csv files "IEV - Total Jobs Derivative for capex+Delta100.csv" and "IEV - Total Economic Impact Derivative for capex+Delta100.csv", and they are uploaded to both MS Teams/General/Sensitivities Calculation/ and https://github.com/rangl-labs/netzerotc/tree/master/environment/sensitivities as they don't contain any sensitive information.

Similar to Step 7 in the post/comment above, added new lines to the env.py and test_reference_environment.py to read the saved csv and xlsx files to testing and actual calculation.

This approach is on hold, as we have successfully compiled the spreadsheets to Python

authors: jia-chenhua moriartyjm

repo: rangl-labs/netzerotc


text:
Create codec encode/decode example files

Any follow ups?
Please review #111 before this one.
Description
This PR creates example files for encode/decode codec types.
Why?
Completing first milestone.
How?

Create example for bitvec
Create example for bool
Create example for bytes
Create example for compact
Create example for option
Create example for result
Create example for signed integers
Create example for string
Create example for unsigned integers
Create example for vector

Testing Plan
Run dart run in polkadart_scale_codec/example/..

Missing example and tests for type Struct. Issue #107

Missing example and test for type Enum. Issue #108

Missing example and test for type Tuple. Issue #109

Missing README documentation. Issue #28

CI not passing.

Fixed.

repo: rankanizer/polkadart


text:
error running example on linux

When I try to run provided example on ubuntu with powershell 6 installed on it i getting folowing error:
<node-powershell>:: Process undefined started

<node-powershell>:: Command invoke started

Error: This socket is closed
    at Socket._writeGeneric (net.js:673:19)
    at Socket._write (net.js:725:8)
    at doWrite (_stream_writable.js:307:12)
    at writeOrBuffer (_stream_writable.js:293:5)
    at Socket.Writable.write (_stream_writable.js:220:11)
    at Socket.write (net.js:651:40)
    at /home/ed/git/alsocloud.visualstudio.com/ac-worker/node_modules/node-powershell/dist/Shell.js:133:36
    at Shell.invoke (/home/ed/git/alsocloud.visualstudio.com/ac-worker/node_modules/node-powershell/dist/Shell.js:130:20)
    at /home/ed/git/alsocloud.visualstudio.com/ac-worker/src/index.js:7:19
    at process._tickCallback (internal/process/next_tick.js:103:7)
    at Module.runMain (module.js:592:11)
    at run (bootstrap_node.js:394:7)
    at startup (bootstrap_node.js:149:9)
    at bootstrap_node.js:509:3

I addressed this in the powershell package. /cc https://github.com/IonicaBizau/powershell/pull/4 :boom:

Hey @edvail, @IonicaBizau
Please check out the new features entered in the last commit.
I just waited for Microsoft to get to 6.0.0.10-alpha version.
Thank you for your patience.  :+1:

authors: IonicaBizau edvail rannn505

license: mit


text:
Short cut for "new todo" is Ctrl-N instead of Cmd-N on macOS

Description
On macOS, when typing "Cmd-N", nothing happens. "Ctrl-N" produces the "new todo" window.
To Reproduce
See description.
Do you see any error entries in sleeks developer tools?
No errors - Cmd-N is ignored
Expected behavior
Cmd-N opens the "new todo" modal.
Desktop (please complete the following information):

OS: macOS 10.15 and 11
any version of sleek so far
Source: Github

@mazimmer the actual shortcut for opening the new todo window is just N. So technically it's a bug that Ctrl + N opens the window ;)

From 2.x on the shortcut will change to Ctrl/Cmd + N


text:
Nested class not generated right

I'm trying to express the following:
{
    "module":  "ping",
    "extra_args":  {
                       "var2":  "value2",
                       "var":  "value1"
                   }
}

I've done this in python like so:
@swagger.model
class AnsibleExtraArgsModel:
    resource_fields = {
        'arg_name' : fields.String,
        'arg_value' : fields.String,
        }

@swagger.model
class AnsibleCommandModel:
    resource_fields = {
        'module': fields.String,
        'extra_args': fields.List(fields.Nested(AnsibleExtraArgsModel.resource_fields)),
    }

However, the resulting swagger spec doesn't include the nested class:
{
    "apiVersion": "0.1",
    "apis": [
        {
            "description": null,
            "notes": null,
            "operations": [],
            "path": "/api/starttask"
        },
        {
            "description": null,
            "notes": null,
            "operations": [
                {
                    "method": "post",
                    "nickname": "nickname",
                    "notes": "Run ad-hoc Ansible command",
                    "parameters": [
                        {
                            "allowMultiple": false,
                            "dataType": "AnsibleCommandModel",
                            "description": "Inut object",
                            "name": "body",
                            "paramType": "body",
                            "required": true
                        }
                    ],
                    "responseClass": "AnsibleRequestResultModel",
                    "responseMessages": [
                        {
                            "code": 200,
                            "message": "Ansible command started"
                        },
                        {
                            "code": 400,
                            "message": "Invalid input"
                        }
                    ],
                    "summary": null
                }
            ],
            "path": "/ansiblecommand"
        },
        {
            "description": null,
            "notes": null,
            "operations": [],
            "path": "/ansibletaskstatus/{task_id}"
        }
    ],
    "basePath": "http://localhost",
    "description": "Auto generated API docs by flask-restful-swagger",
    "models": {
        "AnsibleCommandModel": {
            "description": null,
            "id": "AnsibleCommandModel",
            "notes": null,
            "properties": {
                "extra_args": {
                    "items": {
                        "$ref": null
                    },
                    "type": "array"
                },
                "module": {
                    "type": "string"
                }
            }
        },
        "AnsibleExtraArgsModel": {
            "description": null,
            "id": "AnsibleExtraArgsModel",
            "notes": null,
            "properties": {
                "arg_name": {
                    "type": "string"
                },
                "arg_value": {
                    "type": "string"
                }
            }
        },
        "AnsibleRequestResultModel": {
            "description": null,
            "id": "AnsibleRequestResultModel",
            "notes": null,
            "properties": {
                "task_id": {
                    "type": "string"
                }
            },
            "required": [
                "task_id"
            ]
        }
    },
    "produces": [
        "application/json"
    ],
    "resourcePath": "/",
    "spec_endpoint_path": "/api/spec",
    "swaggerVersion": "1.2"
}

How can I troubleshoot this?

I know this is an old issue, but it seems it still hasn't been resolved. The way I had it - partially - working was by adding @swagger.nested decorator, which in the above case would be:
@swagger.model @swagger.nested( extra_args=AnsibleExtraArgsModel.__name__,) class AnsibleCommandModel:     resource_fields = {         'module': fields.String,         'extra_args': fields.List(fields.Nested(AnsibleExtraArgsModel.resource_fields)),     }
and the swagger doc was generated correctly.
The problem I got - and that why I mentioned it worked partially - was that the nested decorator broke @classmethod decorator and SQLAlchemy select queries were not working.

I know this is an old issue, but it seems it still hasn't been resolved. The way I had it - partially - working was by adding @swagger.nested decorator, which in the above case would be:
@swagger.model
@swagger.nested(extra_args=AnsibleExtraArgsModel.name)
class AnsibleCommandModel:
resource_fields = {
'module': fields.String,
'extra_args': fields.List(fields.Nested(AnsibleExtraArgsModel.resource_fields)),
}
and the swagger doc was generated correctly.
The problem I got - and that why I mentioned it worked partially - was that the nested decorator broke @classmethod decorator and SQLAlchemy select queries were not working.

authors: robxrocks rtrokosz trondhindenes

repo: rantav/flask-restful-swagger


text:
Release excess crafting material before the craft is done.

Issue description:
In many crafts, some material is left over and not needed. It currently stays in the internal crafting memory hogging resources that can be used elsewhere.
What happens:
Excess resources are not accessible until craft finishes
What you expected to happen:
Resources that won't get used by the auto crafting system should be added to the storage.
Steps to reproduce:

Autocraft recipe that produces excess. For example sword.
Notice excess sticks and wood only appear after crafting is finished

...
Version (make sure you are on the latest version before reporting):

Minecraft:1.12.2
Forge:2815
Refined Storage:1.6.14

Sorry, this will be a wontfix. Only the root items go back in to the main inventory, from the initial craft.

authors: Darkere raoulvdberge

repo: raoulvdberge/refinedstorage


text:
Feature Request: Activate Redstone Signal During Specific Craft

I'd like to request some way to send a redstone signal if a certain item is crafting, whether it be a new block (which may be preferable) or by an option in the Crafter. This way, one can do something simple like turn on a light as an indicator or activate some complex redstone system for automating the Runic Altar (for example).

Never mind! I thought I'd pored through the wiki, but it looks like I wasn't looking hard enough.


text:
bind localhost only

hi,
oneshot is a cool tool ;-)
we can change the listening port : would it also be possible to change the address ? to bind only localhost for example (e.g. behind apache or nginx).
regards, lacsaP.

oneshot is a cool tool ;-)

Thanks!
This is a feature that should have been present since the very beginning, thanks for pointing it out!
I should have this implemented soon.

authors: patatetom raphaelreyna

repo: raphaelreyna/oneshot


text:
react-tv-cli not found

Please, publish the react-tv-cli package in the npm registry
https://www.npmjs.com/package/react-tv-cli

Published npmjs.com/package/react-tv-cli
Thanks

authors: marcelometal raphamorim

repo: raphamorim/react-tv


text:
[Testing] Use gpuci-build-environment#159 images for testing

Use the images generated with rapidsai/gpuci-build-environment#159 for testing to see if the gcc7 issues are resolved
NOTE: PR created in repo for use with existing test/build scripts; no need to merge PR. Created for tracking the testing process

Testing started - https://gpuci.gpuopenanalytics.com/job/rapidsai/job/docker/job/rapidsai-core-devel/201/

Local testing showed the rmm built successfully. This is to test all centos 7/8 combinations to see if there are any other blockers

So far this has passed all previous blockers

Closing due to successful testing

repo: rapidsai/docker


text:
Publish multiarch images w/o tests

Since nightly tests are not yet enabled, the build-multiarch-manifest job should run without the test job. This will ensure nightly images are pushed to Docker Hub.
Skipping CI since this job does not run on PRs.

/merge


text:
Fea/move to latest nvbench

Description
Move to latest version of nvbench which includes a fix for a CMake error when using static fmt with a conda env.
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[x] The cmake-format.json is up to date with these changes.

/merge

repo: rapidsai/rapids-cmake


text:
OpenWrt release

Follows https://github.com/rapiz1/rathole/issues/114
It will be useful if the release can be made using OpenWrt SDK and directly .ipk files. This can be done in a separate packaging repository.

Any progress here? :)

Nope. I'm not using OpenWrt currently and don't know how to package Rust program on that platform. Also it may be hard to distribute binary since the OpenWrt is so diverse. What do you think? Are you interested in setting up such repo?
---Original---
From: "Luo @.>
Date: Mon, Aug 15, 2022 15:05 PM
To: @.>;
Cc: "Yujia @.@.>;
Subject: Re: [rapiz1/rathole] OpenWrt release (Issue #133)
Any progress here? :)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Also openssl is an issue. However we can start with not delivering tls feature
---Original---
From: "Luo @.>
Date: Mon, Aug 15, 2022 15:05 PM
To: @.>;
Cc: "Yujia @.@.>;
Subject: Re: [rapiz1/rathole] OpenWrt release (Issue #133)
Any progress here? :)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

I can confirm that the armv7 Linux binary works on an armv7 based router running OpenWRT.
While OpenSSL is not installed by default is can be done as as replacement for WolfSSL.

@rapiz1  I am a FRP user , have been using it in prod since an year. But now i am stuck with FRP because of its large footprint ~10MB.
For an IoT device we need a lightweight reverse proxy exactly like Rathole , because frp is too expensive (on flash storage).
I would be willing to try out things and help on this thread to make rathole work on MediaTek Devices running OpenWRT.  Where should i start and how can i contribute from testing point of view ? (i am not a rust developer) but interested to contribute on testing as i have access to a lot of OpenWRT based hardware.  Are you available on discord/IRC/Slack etc to work in real-time.

@ksingh-scogo you can start by picking up the right binary release. we already have releases for multiple embedded platforms. Then, you can try to package it for openwrt.


text:
Includes rendered before content

With a marko page like this:
<include template="./header.marko"/>
    ${data.bodyText}
<include template="./footer.marko"/>
The rendered result is:
header content
footer content
body content
The expected result is:
header
body
footer

Hi @kobenauf, I am not able to reproduce the issue so there must be something else that is coming into play. What version of marko are you using?
I created a simple project to test with and everything renders as expected:
https://github.com/patrick-steele-idem/marko-issue-82
Please try to reproduce the problem in that project or share your own simple project to reproduce the problem. Thank you.

Thanks for creating that.  This has to be my misunderstanding of what include would do.  Stripping the extra code from my header and footer I found the issue was if I have an open tag in the header (i.e. a <body> tag) and a closing tag in the footer (</body>), Marko adds a closing tag to the header and drops the closing tag from the footer.
So it seems each included template has to be a stand-alone template, not depending on HTML tags opened or closed outside of that template.  Is that correct?

Correct, each standalone template needs to be independent and well-formed HTML since each template is parsed using an HTML parser. In practice this is really not a limitation but it does put a constraint on how to code your templates. I recommend using the layout taglib to piece together your page instead of includes. Please see: https://github.com/raptorjs/marko#layout-taglib
Please let me know if that does or does not work for you. I'm going to go ahead and close this issue, but we can discuss some more here if you would like or in the Gitter chat room: gitter.im/raptorjs/marko

authors: kobenauf patrick-steele-idem

repo: raptorjs/marko


text:
RuntimeError: Control Colourgains is not advertied by libcamera

from picamera2 import *
from time import sleep
from fractions import Fraction

with picamera2.Picamera2() as camera:

		config = camera.create_still_configuration(main={"size": (800, 600)})
		camera.configure(config)

		camera.set_controls({"ExposureTime": 60, "AnalogueGain": 1, "Colourgains": (1.8,1.8)})
		camera.start()
		camera.capture_file('1.jpg')
		print(camera.capture_metadata())

		camera.stop()

		camera.set_controls({"ExposureTime": 120, "AnalogueGain": 1, "Colourgains": (1.8,1.8)})
		camera.start()
		camera.capture_file('2.jpg')
		print(camera.capture_metadata())

		camera.stop()

		camera.close()

This script worked 3 days ago. now without any changing the following error occured:
  File "/home/pi/piHDR/exposurebracket.py", line 16, in <module>
    camera.set_controls({"ExposureTime": 60, "AnalogueGain": 1, "Colourgains": (1.8,1.8)})
  File "/usr/lib/python3/dist-packages/picamera2/picamera2.py", line 911, in set_controls
    self.controls.set_controls(controls)
  File "/usr/lib/python3/dist-packages/picamera2/controls.py", line 58, in set_controls
    self.__setattr__(k, v)
  File "/usr/lib/python3/dist-packages/picamera2/controls.py", line 33, in __setattr__
    raise RuntimeError(f"Control {name} is not advertied by libcamera")
RuntimeError: Control Colourgains is not advertied by libcamera

-.-

Hi, I believe it's "ColourGains" rather than "Colourgains". As far as I'm aware, "ColourGains" has always been correct (and "Colourgains" hasn't), though it's always possible there has been some kind of bug that treated things case-insensitively... Please let us know if there are still problems once you've changed over. Thanks!

Thanks, stupid mistake on my part.

import datetime
import os
import multiprocessing
import time
import shutil

from subprocess import call
from datetime import timezone, timedelta, datetime
from multiprocessing import Process
from time import sleep
from picamera2 import *

dt = datetime.now(timezone.utc)
utc_time = dt.replace(tzinfo=timezone.utc)
utc_timestamp = int(utc_time.timestamp())
utc_timestamps = str(utc_timestamp)

os.chdir("/home/pi/rawhdr/imgs/")
os.mkdir(f"{utc_timestamp}")

def generate_raw_series():
	os.system("libcamera-raw --ev -10 --awbgains 1.0,1.0 --gain 1.0 --analoggain 1.0 --denoise off --rawfull 1 --shutter 50 --mode 4056:3040:12:U -o 50.raw --segment 1")
	os.system("libcamera-raw --ev -10 --awbgains 1.0,1.0 --gain 1.0 --analoggain 1.0 --denoise off --rawfull 1 --shutter 150 --mode 4056:3040:12:U -o 150.raw --segment 1")
	os.system("libcamera-raw --ev -10 --awbgains 1.0,1.0 --gain 1.0 --analoggain 1.0 --denoise off --rawfull 1 --shutter 200 --mode 4056:3040:12:U -o 200.raw --segment 1")
	os.system("libcamera-raw --ev -10 --awbgains 1.0,1.0 --gain 1.0 --analoggain 1.0 --denoise off --rawfull 1 --shutter 350 --mode 4056:3040:12:U -o 350.raw --segment 1")
	os.system("libcamera-raw --ev -10 --awbgains 1.0,1.0 --gain 1.0 --analoggain 1.0 --denoise off --rawfull 1 --shutter 550 --mode 4056:3040:12:U -o 550.raw --segment 1")
	os.system("libcamera-raw --ev -10 --awbgains 1.0,1.0 --gain 1.0 --analoggain 1.0 --denoise off --rawfull 1 --shutter 900 --mode 4056:3040:12:U -o 900.raw --segment 1")
	os.system("libcamera-raw --ev -10 --awbgains 1.0,1.0 --gain 1.0 --analoggain 1.0 --denoise off --rawfull 1 --shutter 1450 --mode 4056:3040:12:U -o 1450.raw --segment 1")
	os.system("libcamera-raw --ev -10 --awbgains 1.0,1.0 --gain 1.0 --analoggain 1.0 --denoise off --rawfull 1 --shutter 2350--mode 4056:3040:12:U -o 2350.raw --segment 1")
	os.system("libcamera-raw --ev -10 --awbgains 1.0,1.0 --gain 1.0 --analoggain 1.0 --denoise off --rawfull 1 --shutter 3800 --mode 4056:3040:12:U -o 3800.raw --segment 1")
	os.system("libcamera-raw --ev -10 --awbgains 1.0,1.0 --gain 1.0 --analoggain 1.0 --denoise off --rawfull 1 --shutter 5150--mode 4056:3040:12:U -o 5150.raw --segment 1")
	os.system("libcamera-raw --ev -10 --awbgains 1.0,1.0 --gain 1.0 --analoggain 1.0 --denoise off --rawfull 1 --shutter 8950 --mode 4056:3040:12:U -o 8950.raw --segment 1")
	os.system("libcamera-raw --ev -10 --awbgains 1.0,1.0 --gain 1.0 --analoggain 1.0 --denoise off --rawfull 1 --shutter 14100 --mode 4056:3040:12:U -o 14100.raw --segment 1")
	os.system("libcamera-raw --ev -10 --awbgains 1.0,1.0 --gain 1.0 --analoggain 1.0 --denoise off --rawfull 1 --shutter 23050 --mode 4056:3040:12:U -o 23050.raw --segment 1")

generate_raw_series()

WARNING: consider inline headers with 'pause'/split/segment/circular
WARNING: expected % directive in output filename
As long as the exposure time between the raw frames is pretty much identical, isn't it enough to use --segment1?
(Do the raw frames differ greatly in terms of noise?)
Or am I thinking too short-sighted here?

Interessting the raw file capturing takes way longer that way.. ^^

What you have there looks to me like it should work fine. The frames for a single exposure should all be much the same. Obviously the noise will be random, but each frame should have the same "amount" of noise, statistically speaking. You might want to consider the -t argument to limit how long libcamera-raw runs.
I'm going to lock this thread if that's OK so that we can keep any further discussions on the existing open issue (or open a new one). Thanks!


text:
Pico W SDK CYW43 Driver calls "pio_sm_set_enabled" with hard-coded number instead of bus_data_t->pio_sm value

In file: pico-sdk/src/rp2_common/cyw43_driver/cyw43_bus_pio_spi.c
Function: cyw43_spi_transfer()
Line: 307
Function pio_sm_set_enabled() is called with hard-coded value of 0 for the PIO state machine number.
  pio_sm_set_enabled(bus_data->pio, 0, true);
-Probably should be-
  pio_sm_set_enabled(bus_data->pio, bus_data->pio_sm, true);
This could be a problem if another PIO program was installed on state machine 0 before the CYW43 driver was initialized.

Already fixed by #1080 ?

duplicate of #1077

authors: dlkeng kilograham lurch

repo: raspberrypi/pico-sdk


text:
Feature request: pico-stdio: Provide puts_raw analogue that doesn't write newline

It would be great to have access to stdio_put_string() version that doesn't append newline at the end - that would simplify logging and similar routines, and can help in some cases with custom stdio drivers.
int putchar_raw(int c) {
    char cc = (char)c;
    stdio_put_string(&cc, 1, false, true);
    return c;
}

int puts_raw(const char *s) {
    int len = (int)strlen(s);
    stdio_put_string(s, len, true, true);
    stdio_flush();
    return len;
}

//-+-+-+-+-+-+- suggestion -+-+-+-+-+-+-//
int put_string_raw(const char *s) {
    int len = (int)strlen(s);
    stdio_put_string(s, len, false, true);
    stdio_flush();
    return len;
}
//-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-//

If that's acceptable, I can send a PR.

seems ok, but name is probably confusing maybe writes_raw is a better name

putchar_raw and puts_raw have been added. Marking this as resolved.

putchar_raw and puts_raw have been added. Marking this as resolved.

I'm a bit confused. Both putchar_raw and puts_raw were already there. The request was to add writes_raw (put_string_raw).

You're right. My misunderstanding. Lets see what @kilograham says.

fixed

authors: cocasema kilograham peterharperuk


text:
nStakeMinAge still referenced in GetWeight

nStakeMinAge still referenced in GetWeight https://github.com/rat4/blackcoin/blob/protocolv3/src/kernel.cpp#L13-L20
GetWeight is referencded when comparing to GetStakeSplitAge in https://github.com/rat4/blackcoin/blob/protocolv3/src/wallet.cpp#L1948
GetStakeSplitAge is only referenced there.
GetStakeSplitAge is declared here https://github.com/rat4/blackcoin/blob/protocolv3/src/wallet.cpp#L28
Those are the only things stopping it from not using nStakeMinAge at all when its only using protocolv3.

I guess a workaround would be to make it ask "if (nCredit > GetStakeCombineThreshold())" when its using protocolv3 instead of "if (GetWeight(nBlockTime, (int64_t)txNew.nTime) < GetStakeSplitAge())".


text:
Some additions to set and map

This PR allows one to get a reference to a map's key (and by extension, a set's value). This is useful for using sets to implement string interning.

These should also have proxy implementations for BloomMap / BloomSet.

authors: Vurich maciejhirsz

repo: ratel-rust/toolshed


text:
How to save a simple logistic regression model?

Hi,
I was trying to build a logistic regression model on the preprocessed data. The model is built and test and validation .pkl files are created in the log folder. I tried to save the logistic regression model as a .pkl file as well. As a variable (save_weights) defined in the train function of the wrappers.py file for this and I set it to "True" to save the model as follow:
@gin.configurable(module='MLWrapper')
def train(self, train_dataset, val_dataset, weight,
patience=gin.REQUIRED, save_weights=True):
But I get the error of:
_pickle.PicklingError: Can't pickle <class 'sklearn.linear_model._logistic.LogisticRegression'>: it's not the same object as sklearn.linear_model._logistic.LogisticRegression
In call to configurable 'train' (<function MLWrapper.train at 0x141d17670>)
In call to configurable 'train_common' (<function train_common at 0x1414d1670>)
and I cannot find the issue. It seems that the LogisticRegression functions are different...
I appreciate it if you help me to find the problem and solve this issue.

The file environment.yml is not available anymore

authors: minasmz ricoms

repo: ratschlab/HIRID-ICU-Benchmark


text:
ko-BERT vocabulary 추출

개요
바이너리 형태의 Ko-BERT vocabulary를 huggingface 모듈이 읽을 수 있는 text 형태의 vocabulary로 추출한다

code
pip install mxnet gluonnlp sentencepiece

import gluonnlp as nlp
vocab = nlp.vocab.BERTVocab.from_sentencepiece("spiece", padding_token="[PAD]")
with open("vocab.txt", "w", encoding="utf-8") as f:
    for k, v in vocab.token_to_idx.items():
        f.writelines(k + "\n")

*code2
두번째 방법
from gluonnlp.data import SentencepieceTokenizer
sp = SentencepieceTokenizer("spiece")
with open("vocab2.txt", "w", encoding="utf-8") as f:
	for el in sp.tokens:
		f.writelines(el + "\n")

repo: ratsgo/ratsnlp


text:
decimal part when numbers are aggregated

When we map numerical dimensions to labels, we could have numbers with a very long decimal part due to the chosen aggregations (see image below). We could hardcode a rounding function, but sometimes users would like to keep the decimal part.
I have no idea on how to solve the issue

similar issue in sankey and alluvial diagrams (see #134 for details)

repo: rawgraphs/rawgraphs-charts


text:
ray-operator coding style change

Why are these changes needed?

Related issue number

Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[ ] Manual tests
[ ] This PR is not tested :(

@kevin85421, This is our newbie's first contribution. Please take a look when you are available.

Congratulations on your first PR, @LeoLiao123!

repo: ray-project/kuberay