text:
[UI] Cluster Templates - When clone template and attempt to save, get error

Version: master-head (7/22/19)
What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Create a clone template. Name the revision something; I called mine "test3"
Attempt to clone the (either from default or from revision) template and save. Now attempt to cancel as well.

Result:
UI shows an error:

Browser dev console reports a warning:

Cancel button also does not work:

Press browser back button, view cluster templates, it actually created it:

Closing in favor of https://zube.io/rancher/rancher-engineering/c/23693


text:
Cluster provisioned with core dns node selector does not have core-dns pods deployed on the nodes

Version: master-head
Steps:

Create a custom cluster by providing node selector for core dns in the yml file.

  dns:
    node_selector:
      app: dns
    provider: coredns

The core-dns pods do not get deployed on the nodes even with the label app:dns

> kubectl get pod --namespace kube-system
NAME                                      READY   STATUS      RESTARTS   AGE
canal-4x6b7                               2/2     Running     0          161m
canal-7qtwd                               2/2     Running     0          97m
canal-drjd5                               2/2     Running     0          90m
metrics-server-59c6fd6767-cgjxm           1/1     Running     0          161m
rke-coredns-addon-deploy-job-52nmd        0/1     Error       0          160m
rke-coredns-addon-deploy-job-5jd9c        0/1     Error       0          161m
rke-coredns-addon-deploy-job-6d87g        0/1     Error       0          159m
rke-coredns-addon-deploy-job-6pxmc        0/1     Error       0          147m
rke-coredns-addon-deploy-job-9cfhd        0/1     Error       0          161m
rke-coredns-addon-deploy-job-9hv4t        0/1     Error       0          161m
rke-coredns-addon-deploy-job-9vf69        0/1     Error       0          141m
rke-coredns-addon-deploy-job-tm7jp        0/1     Error       0          153m
rke-coredns-addon-deploy-job-xpcjm        0/1     Error       0          161m
rke-ingress-controller-deploy-job-xchgw   0/1     Completed   0          161m
rke-metrics-addon-deploy-job-c862q        0/1     Completed   0          161m
rke-network-plugin-deploy-job-5lhss       0/1     Completed   0          161m

Tested with master-head build from Sep 4th
Created a custom cluster with nodeselector specified for core-dns.
dns:
    provider: coredns
    node_selector:
      app: dns

One of the nodes had the label app:dns. The coredns pod was successfully deployed on the node with the label
> kubectl get all --namespace kube-system
NAME                                          READY   STATUS      RESTARTS   AGE
pod/canal-69clr                               2/2     Running     0          123m
pod/canal-cnxkn                               2/2     Running     0          137m
pod/canal-hkpf9                               2/2     Running     0          135m
pod/coredns-autoscaler-84766fbb4-8qts9        1/1     Running     0          137m
pod/coredns-fb59784d-tr76s                    1/1     Running     0          137m
pod/metrics-server-59c6fd6767-ck8vj           1/1     Running     0          137m
pod/rke-coredns-addon-deploy-job-84v5v        0/1     Completed   0          137m
pod/rke-ingress-controller-deploy-job-gxrtr   0/1     Completed   0          137m
pod/rke-metrics-addon-deploy-job-7qcth        0/1     Completed   0          137m
pod/rke-network-plugin-deploy-job-dw4pv       0/1     Completed   0          137m

source: gharchive/issue

repo: rancher/rancher

license_type: permissive

license_source: github-api


text:
RKE2 with cilium and project network isolation breaks ingress controller to pod communication

Rancher Server Setup

Rancher version: v2.6.0-rc3
Installation option (Docker install/Helm Chart): Helm

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): v1.21.3+k3s1

Proxy/Cert Details: no proxy, Let's Encrypt certificate

Information about the Cluster

Kubernetes version: RKE2: v1.21.3+rke2r2
Cluster Type (Local/Downstream): downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): tested with digital ocean infrastructure provider

Describe the bug
When you create a RKE2 cluster with cilium as a CNI and activate project network isolation. The communication between the ingress controller and the Pods does not work anymore, when the ingress controller and workload pod are not on the same node.
To Reproduce

Create a multi node RKE2 custom cluster
Choose Cilium CNI
Activate project network isolation
Create a workload (e.g.) an nginx and an ingress
Try to reach the ingress, make sure that you connect to an ingress controller Pod that is not on the same node as the nginx pod.

Result
The nginx ingress controller will get a gateway timeout when communication with the pod:
curl 35.158.100.209 -H 'Host: nginx.example'

<title>504 Gateway Time-out</title>

504 Gateway Time-out

nginx

Expected Result
The communication works out of the box.
Additional context
Similar issue with calico as a CNI: https://github.com/rancher/rancher/issues/33979
For cilium the host network -> pod traffic needs to be whitelisted differently as well. Upstream issue for this: https://github.com/cilium/cilium/issues/10405.
A working CiliumNetworkPolicy for this:
apiVersion: cilium.io/v2
kind: CiliumNetworkPolicy
metadata:
  name: hn-nodes
  namespace: default
spec:
  endpointSelector: {}
  ingress:
    - fromEntities:
      - remote-node

Need initial investigations to come up with LOE.

After talking this over  we have decided to not add the CiliumNetworkPolicy.  The reason being users have to opt into the cilium CNI and network isolation.  By default Cilium does not enable cross node communication as of 1.7.  Enabling this by default would be breaking from the upstream behavior and could be undesirable.  Given it is not intuitive but may be desired  I have made an issue to add a notification to the  dashboard informing users of this behavior.
https://github.com/rancher/dashboard/issues/5105
https://github.com/rancher/docs/issues/3868

authors: bashofmann paynejacob snasovich


text:
Data is empty after upgrade

Old Version：v2.4.5
New Version：v2.6
I upgraded my single docker rancher to the latest version according to the official requirements, but it seems that the data volume mounted from the old version did not let my newly upgraded rancher have any previous data
this is my operation for updating.
docker stop <RANCHER_CONTAINER_NAME>
docker create --volumes-from <RANCHER_CONTAINER_NAME> --name rancher-data rancher/rancher:<RANCHER_CONTAINER_TAG>
docker pull rancher/rancher:latest
docker run -d --volumes-from rancher-data
--restart=unless-stopped
-p 80:80 -p 443:443
--privileged
rancher/rancher:<RANCHER_VERSION_TAG>
--acme-domain <YOUR.DNS.NAME>
before update

after update

@chenFe-1 Was this an upgrade to Rancher v2.6.3?

This is likely due to changes in 2.5 not being applied to your data volume.  When upgrading rancher we do not support skipping minor versions.
https://www.suse.com/support/kb/doc/?id=000020061#:~:text=Rancher%3A perform one minor version jump at a time

authors: chenFe-1 paynejacob thedadams


text:
rancher v2.6.3 crash in docker at debian 11

Rancher Server Setup

Rancher version: 2.6.3
Installation option (Docker install/Helm Chart): Docker
Proxy/Cert Details:

when i run shell:
docker run -d --privileged --restart=unless-stopped \
  -p 80:80-p 443:443\
  -v /root/rancher-container:/var/lib/rancher \
  rancher/rancher:stable

it not work, docker container info:
2022/01/16 14:00:56 [INFO] Rancher version v2.6.3 (3c1d5fac3) is starting
2022/01/16 14:00:56 [INFO] Rancher arguments {ACMEDomains:[] AddLocal:true Embedded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:false Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Features: ClusterRegistry:}
2022/01/16 14:00:56 [INFO] Listening on /tmp/log.sock
2022/01/16 14:00:56 [INFO] Waiting for k3s to start
time="2022-01-16T14:00:56Z" level=info msg="Acquiring lock file /var/lib/rancher/k3s/data/.lock"
time="2022-01-16T14:00:56Z" level=info msg="Preparing data dir /var/lib/rancher/k3s/data/e61cd97f31a54dbcd9893f8325b7133cfdfd0229ff3bfae5a4f845780a93e84c"
2022/01/16 14:00:57 [INFO] Waiting for k3s to start
2022/01/16 14:00:58 [INFO] Waiting for k3s to start
2022/01/16 14:00:59 [INFO] Waiting for server to become available: an error on the server ("apiserver not ready") has prevented the request from succeeding
2022/01/16 14:01:01 [INFO] Waiting for server to become available: an error on the server ("apiserver not ready") has prevented the request from succeeding
2022/01/16 14:01:03 [INFO] Waiting for server to become available: an error on the server ("apiserver not ready") has prevented the request from succeeding
2022/01/16 14:01:05 [INFO] Running in single server mode, will not peer connections
2022/01/16 14:01:05 [INFO] Applying CRD features.management.cattle.io
2022/01/16 14:01:05 [INFO] Waiting for CRD features.management.cattle.io to become available
2022/01/16 14:01:06 [INFO] Done waiting for CRD features.management.cattle.io to become available
2022/01/16 14:01:08 [INFO] Applying CRD navlinks.ui.cattle.io
2022/01/16 14:01:08 [INFO] Applying CRD clusters.management.cattle.io
2022/01/16 14:01:08 [INFO] Applying CRD apiservices.management.cattle.io
2022/01/16 14:01:08 [INFO] Applying CRD clusterregistrationtokens.management.cattle.io
2022/01/16 14:01:08 [INFO] Applying CRD settings.management.cattle.io
2022/01/16 14:01:08 [INFO] Applying CRD preferences.management.cattle.io
2022/01/16 14:01:08 [INFO] Applying CRD features.management.cattle.io
2022/01/16 14:01:08 [INFO] Applying CRD clusterrepos.catalog.cattle.io
2022/01/16 14:01:08 [INFO] Applying CRD operations.catalog.cattle.io
2022/01/16 14:01:08 [INFO] Applying CRD apps.catalog.cattle.io
2022/01/16 14:01:08 [INFO] Applying CRD fleetworkspaces.management.cattle.io
2022/01/16 14:01:08 [INFO] Applying CRD bundles.fleet.cattle.io
2022/01/16 14:01:08 [INFO] Applying CRD clusters.fleet.cattle.io
2022/01/16 14:01:09 [INFO] Applying CRD managedcharts.management.cattle.io
2022/01/16 14:01:09 [INFO] Applying CRD clusters.provisioning.cattle.io
2022/01/16 14:01:09 [INFO] Applying CRD clusters.provisioning.cattle.io
2022/01/16 14:01:09 [INFO] Applying CRD rkeclusters.rke.cattle.io
2022/01/16 14:01:09 [INFO] Applying CRD rkecontrolplanes.rke.cattle.io
2022/01/16 14:01:09 [INFO] Applying CRD rkebootstraps.rke.cattle.io
2022/01/16 14:01:09 [INFO] Applying CRD rkebootstraptemplates.rke.cattle.io
2022/01/16 14:01:09 [INFO] Applying CRD rkecontrolplanes.rke.cattle.io
2022/01/16 14:01:09 [INFO] Applying CRD custommachines.rke.cattle.io
2022/01/16 14:01:09 [INFO] Applying CRD clusters.cluster.x-k8s.io
2022/01/16 14:01:10 [INFO] Applying CRD machinedeployments.cluster.x-k8s.io
2022/01/16 14:01:10 [INFO] Applying CRD machinehealthchecks.cluster.x-k8s.io
2022/01/16 14:01:10 [INFO] Applying CRD machines.cluster.x-k8s.io
2022/01/16 14:01:10 [INFO] Applying CRD machinesets.cluster.x-k8s.io
2022/01/16 14:01:10 [INFO] Waiting for CRD machinesets.cluster.x-k8s.io to become available
2022/01/16 14:01:11 [INFO] Done waiting for CRD machinesets.cluster.x-k8s.io to become available
2022/01/16 14:01:11 [INFO] Creating CRD authconfigs.management.cattle.io
2022/01/16 14:01:11 [INFO] Creating CRD groupmembers.management.cattle.io
2022/01/16 14:01:11 [INFO] Creating CRD groups.management.cattle.io
2022/01/16 14:01:11 [INFO] Creating CRD tokens.management.cattle.io
2022/01/16 14:01:11 [INFO] Creating CRD userattributes.management.cattle.io
2022/01/16 14:01:11 [INFO] Creating CRD users.management.cattle.io
2022/01/16 14:01:11 [INFO] Waiting for CRD userattributes.management.cattle.io to become available
2022/01/16 14:01:12 [INFO] Done waiting for CRD userattributes.management.cattle.io to become available
2022/01/16 14:01:12 [INFO] Waiting for CRD users.management.cattle.io to become available
2022/01/16 14:01:12 [INFO] Done waiting for CRD users.management.cattle.io to become available
2022/01/16 14:01:12 [INFO] Waiting for CRD tokens.management.cattle.io to become available
2022/01/16 14:01:13 [INFO] Done waiting for CRD tokens.management.cattle.io to become available
2022/01/16 14:01:14 [INFO] Creating CRD apps.project.cattle.io
2022/01/16 14:01:14 [INFO] Creating CRD apprevisions.project.cattle.io
2022/01/16 14:01:14 [INFO] Creating CRD catalogs.management.cattle.io
2022/01/16 14:01:14 [INFO] Creating CRD pipelineexecutions.project.cattle.io
2022/01/16 14:01:14 [INFO] Creating CRD clusterroletemplatebindings.management.cattle.io
2022/01/16 14:01:14 [INFO] Creating CRD catalogtemplates.management.cattle.io
2022/01/16 14:01:14 [INFO] Creating CRD pipelinesettings.project.cattle.io
2022/01/16 14:01:14 [INFO] Creating CRD dynamicschemas.management.cattle.io
2022/01/16 14:01:14 [INFO] Creating CRD catalogtemplateversions.management.cattle.io
2022/01/16 14:01:14 [INFO] Creating CRD pipelines.project.cattle.io
2022/01/16 14:01:14 [INFO] Creating CRD sourcecodecredentials.project.cattle.io
2022/01/16 14:01:14 [INFO] Creating CRD clusteralerts.management.cattle.io
2022/01/16 14:01:14 [INFO] Creating CRD etcdbackups.management.cattle.io
2022/01/16 14:01:14 [INFO] Creating CRD clusteralertgroups.management.cattle.io
2022/01/16 14:01:14 [INFO] Creating CRD globalrolebindings.management.cattle.io
2022/01/16 14:01:14 [INFO] Creating CRD sourcecodeproviderconfigs.project.cattle.io
2022/01/16 14:01:14 [INFO] Creating CRD clustercatalogs.management.cattle.io
2022/01/16 14:01:14 [INFO] Creating CRD sourcecoderepositories.project.cattle.io
2022/01/16 14:01:14 [FATAL] creating CRD store Post "https://127.0.0.1:6443/apis/apiextensions.k8s.io/v1/customresourcedefinitions?timeout=15m0s": read tcp 127.0.0.1:48196->127.0.0.1:6443: read: connection reset by peer
2022/01/16 14:01:28 [INFO] Rancher version v2.6.3 (3c1d5fac3) is starting
2022/01/16 14:01:28 [INFO] Rancher arguments {ACMEDomains:[] AddLocal:true Embedded:false BindHost: HTTPListenPort:80 HTTPSListenPort:443 K8sMode:auto Debug:false Trace:false NoCACerts:false AuditLogPath:/var/log/auditlog/rancher-api-audit.log AuditLogMaxage:10 AuditLogMaxsize:100 AuditLogMaxbackup:10 AuditLevel:0 Features: ClusterRegistry:}
2022/01/16 14:01:28 [INFO] Listening on /tmp/log.sock
2022/01/16 14:01:28 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6443/version?timeout=15m0s": dial tcp 127.0.0.1:6443: connect: connection refused
2022/01/16 14:01:30 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6443/version?timeout=15m0s": dial tcp 127.0.0.1:6443: connect: connection refused
2022/01/16 14:01:32 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6443/version?timeout=15m0s": dial tcp 127.0.0.1:6443: connect: connection refused
2022/01/16 14:01:34 [INFO] Waiting for server to become available: Get "https://127.0.0.1:6443/version?timeout=15m0s": dial tcp 127.0.0.1:6443: connect: connection refused
2022/01/16 14:01:36 [INFO] Waiting for server to become available: an error on the server ("apiserver not ready") has prevented the request from succeeding
2022/01/16 14:01:38 [INFO] Waiting for server to become available: an error on the server ("apiserver not ready") has prevented the request from succeeding
2022/01/16 14:01:40 [INFO] Waiting for server to become available: an error on the server ("apiserver not ready") has prevented the request from succeeding
2022/01/16 14:01:42 [INFO] Waiting for server to become available: an error on the server ("apiserver not ready") has prevented the request from succeeding
2022/01/16 14:01:44 [INFO] Waiting for server to become available: an error on the server ("apiserver not ready") has prevented the request from succeeding
2022/01/16 14:01:46 [INFO] Running in single server mode, will not peer connections
2022/01/16 14:01:46 [INFO] Applying CRD features.management.cattle.io
2022/01/16 14:01:46 [INFO] Applying CRD navlinks.ui.cattle.io
2022/01/16 14:01:46 [INFO] Applying CRD clusters.management.cattle.io
2022/01/16 14:01:47 [INFO] Applying CRD apiservices.management.cattle.io
2022/01/16 14:01:47 [INFO] Applying CRD clusterregistrationtokens.management.cattle.io
2022/01/16 14:01:47 [INFO] Applying CRD settings.management.cattle.io
2022/01/16 14:01:47 [INFO] Applying CRD preferences.management.cattle.io
2022/01/16 14:01:47 [INFO] Applying CRD features.management.cattle.io
2022/01/16 14:01:47 [INFO] Applying CRD clusterrepos.catalog.cattle.io
2022/01/16 14:01:47 [INFO] Applying CRD operations.catalog.cattle.io
2022/01/16 14:01:47 [INFO] Applying CRD apps.catalog.cattle.io
2022/01/16 14:01:47 [INFO] Applying CRD fleetworkspaces.management.cattle.io
2022/01/16 14:01:47 [INFO] Applying CRD managedcharts.management.cattle.io
2022/01/16 14:01:47 [INFO] Applying CRD clusters.provisioning.cattle.io
2022/01/16 14:01:48 [INFO] Applying CRD clusters.provisioning.cattle.io
2022/01/16 14:01:48 [INFO] Applying CRD rkeclusters.rke.cattle.io
2022/01/16 14:01:48 [INFO] Applying CRD rkecontrolplanes.rke.cattle.io
2022/01/16 14:01:48 [INFO] Applying CRD rkebootstraps.rke.cattle.io
2022/01/16 14:01:48 [INFO] Applying CRD rkebootstraptemplates.rke.cattle.io
2022/01/16 14:01:48 [INFO] Applying CRD rkecontrolplanes.rke.cattle.io
2022/01/16 14:01:48 [INFO] Applying CRD custommachines.rke.cattle.io
2022/01/16 14:01:48 [INFO] Applying CRD clusters.cluster.x-k8s.io
2022/01/16 14:01:48 [INFO] Applying CRD machinedeployments.cluster.x-k8s.io
2022/01/16 14:01:48 [INFO] Applying CRD machinehealthchecks.cluster.x-k8s.io
2022/01/16 14:01:48 [INFO] Applying CRD machines.cluster.x-k8s.io
2022/01/16 14:01:48 [INFO] Applying CRD machinesets.cluster.x-k8s.io
2022/01/16 14:01:49 [INFO] Creating CRD pipelinesettings.project.cattle.io
2022/01/16 14:01:49 [INFO] Creating CRD catalogtemplates.management.cattle.io
2022/01/16 14:01:49 [INFO] Creating CRD globalroles.management.cattle.io
2022/01/16 14:01:49 [INFO] Creating CRD sourcecoderepositories.project.cattle.io
2022/01/16 14:01:49 [INFO] Creating CRD clustercatalogs.management.cattle.io
2022/01/16 14:01:49 [INFO] Creating CRD kontainerdrivers.management.cattle.io
2022/01/16 14:01:49 [INFO] Creating CRD clusterloggings.management.cattle.io
2022/01/16 14:01:49 [INFO] Creating CRD nodedrivers.management.cattle.io

OS:
Distributor ID:	Debian
Description:	Debian GNU/Linux 11 (bullseye)
Release:	11
Codename:	bullseye

docker info:
Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Docker Buildx (Docker Inc., v0.7.1-docker)
  scan: Docker Scan (Docker Inc., v0.12.0)

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 1
 Server Version: 20.10.12
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 7b11cfaabd73bb80907dd23182b9347b4245eb5d
 runc version: v1.0.2-0-g52b36a2
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: default
  cgroupns
 Kernel Version: 5.10.0-10-amd64
 Operating System: Debian GNU/Linux 11 (bullseye)
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 3.839GiB
 Name: k3s-master
 ID: 3J4W:HOP5:QZCR:EX3M:E26K:RRIM:7U3G:FAAP:WHSH:AMNA:DS5J:SBPG
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Registry Mirrors:
  https://6629mu38.mirror.aliyuncs.com/
 Live Restore Enabled: false

i use virtualbox and start virtual machine, theres the network config:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 08:00:27:cd:58:ac brd ff:ff:ff:ff:ff:ff
inet 10.0.2.15/24 brd 10.0.2.255 scope global dynamic enp0s3
valid_lft 81557sec preferred_lft 81557sec
inet6 fe80::a00:27ff:fecd:58ac/64 scope link
valid_lft forever preferred_lft forever
3: enp0s8: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 08:00:27:ab:35:ae brd ff:ff:ff:ff:ff:ff
inet 192.168.56.115/24 brd 192.168.56.255 scope global dynamic enp0s8
valid_lft 432sec preferred_lft 432sec
inet6 fe80::a00:27ff:feab:35ae/64 scope link
valid_lft forever preferred_lft forever
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:dd:27:ee:00 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
inet6 fe80::42:ddff:fe27:ee00/64 scope link
valid_lft forever preferred_lft forever
5: flannel.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN group default
link/ether f2:bf:0a:a5:6d:5b brd ff:ff:ff:ff:ff:ff
inet 10.42.0.0/32 scope global flannel.1
valid_lft forever preferred_lft forever
inet6 fe80::f0bf:aff:fea5:6d5b/64 scope link
valid_lft forever preferred_lft forever
6: cni0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default qlen 1000
link/ether 46:cf:fd:69:3f:9e brd ff:ff:ff:ff:ff:ff
inet 10.42.0.1/24 brd 10.42.0.255 scope global cni0
valid_lft forever preferred_lft forever
inet6 fe80::44cf:fdff:fe69:3f9e/64 scope link
valid_lft forever preferred_lft forever
7: vethee6e50e5@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
link/ether ee:88:e7:68:76:89 brd ff:ff:ff:ff:ff:ff link-netns cni-1e3bc984-8346-585c-e75b-17b7d8d89ecb
inet6 fe80::ec88:e7ff:fe68:7689/64 scope link
valid_lft forever preferred_lft forever
8: veth12ce44c7@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
link/ether 5a:ab:60:7a:2b:5b brd ff:ff:ff:ff:ff:ff link-netns cni-9845c9f3-850f-f1dc-e7d5-17a55c50b1dd
inet6 fe80::647c:6cff:fe6a:d81f/64 scope link
valid_lft forever preferred_lft forever
9: veth33b66dbf@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
link/ether ea:82:0a:ad:3e:60 brd ff:ff:ff:ff:ff:ff link-netns cni-785c062e-7c53-e0e8-61dd-18548edeb5cb
inet6 fe80::b891:8fff:feef:8038/64 scope link
valid_lft forever preferred_lft forever
10: veth23eeea81@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
link/ether 1a:ca:5a:0c:f8:6c brd ff:ff:ff:ff:ff:ff link-netns cni-66cd019e-056d-328e-0345-743fa6c4bc8d
inet6 fe80::dc7c:97ff:fea0:3133/64 scope link
valid_lft forever preferred_lft forever
11: veth3f80087d@if3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue master cni0 state UP group default
link/ether 02:c8:e0:2a:76:30 brd ff:ff:ff:ff:ff:ff link-netns cni-994da0af-40ec-0fc2-f772-1c19337ec1bb
inet6 fe80::8b2:e8ff:fef0:2a7e/64 scope link
valid_lft forever preferred_lft forever

Hello, I am having this issue also. I found a couple of other issues opened that may be related:
https://github.com/rancher/rancher/issues/35930
https://github.com/rancher/rancher/issues/35927
https://github.com/rancher/rancher/issues/36047

oh, i get it #35201 and try to switch the cgroup v2 to v1, its work. thx!

oh, i get it #35201 and try to switch the cgroup v2 to v1, its work. thx!

How did you switch it exactly?  I'm in the same situation but can't find any straightforward guidance on how to change this

To switch cgroup to v1, you need to:

On systemd-based systems, cgroup v2 can be enabled by adding systemd.unified_cgroup_hierarchy=1 to the kernel cmdline. To revert the cgroup version to v1, you need to set systemd.unified_cgroup_hierarchy=0 instead.

Info found here: https://docs.docker.com/config/containers/runmetrics/
For Raspberry PI, basically you add systemd.unified_cgroup_hierarchy=0 next to the cgroup_enable=cpuset cgroup_enable=memory cgroup_memory=1 in your cmdline.txt and reboot.

authors: ncrosty58 sceniclife zigaai


text:
Cannot deploy f5 (external-lb) from catalog

Rancher Version: v1.1.0-dev1-rc1
Steps to Reproduce:

Add f5 catalog [URL ==> https://github.com/prachidamle/my-rancher-catalog]
Deploy the f5 catalog [f5 BigIP LB Stack]

Results: Deployment un-successful.
Activating (yaml: [while parsing a quoted scalar] did not find expected hexdecimal number at line 23, column 24). It remains in this state and the service does not get added.

Seems like Rancher Compose - v0.8.0-rc3 has stricter yaml validation, causing this failure

This is fixed now - It was erroring out on a single quote used in rancher-compose.yml file

Verified after the fix in rancher-compose.yml file.

authors: prachidamle soumyalj


text:
[BUG] [UI] v2.9.3-rc1 Harvester cloud credentials are not correctly displayed if the expiration timestamp is "0"

Rancher Server Setup

Rancher version: v2.9.3-rc1
Installation option (Docker install/Helm Chart):

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): Helm

Proxy/Cert Details: N/A

Information about the Cluster

Kubernetes version: v1.27.16+k3s1 (rancher-vcluster plugin on Harvester)
Cluster Type (Local/Downstream):

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): local

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions: admin

Describe the bug
During an upgrade from a previous version of Rancher to v2.9.3(-rc1), cloud credentials for Harvester cluster will receive a new annotation rancher.io/expiration-timestamp to allow easy renewal via the UI.
There may be cloud credentials for a Harvester cluster (used for virtualization management) which reference an expired or non-existent token, since tokens may be deleted by users or get purged when they expire.
These cloud credentials receive the value "0" for the annotation rancher.io/expiration-timestamp - indicating that the token has expired.
Unlike regular (non-zero) expiration timestamps, this is incorrectly displayed in the UI as not-expired.
To Reproduce
Variant 1:

Install Rancher v2.9.2
Install Harvester (e.g. v1.3.2)
Import Harvester into Rancher for virtualization management
Create cloud credential for Harvester
Delete the token for the cloud credential or wait until it is expired
Upgrade to Rancher v2.9.3(-rc1)

Result
The cloud credential is not displayed as expired
e.g.:

Expected Result
The cloud credential should be clearly displayed as expired
e.g.:

Screenshots
See above.
Additional context
https://github.com/rancher/rancher/pull/47649
https://github.com/rancher/rancher/issues/47583
https://github.com/rancher/rancher/issues/47583
https://github.com/rancher/rancher/issues/44912

Verified as fixed in v2.10.0-alpha7
:green_circle: Cloud credential showing up normal, when the expiration is far enough in the future:

:green_circle: Cloud credential showing a warning, when the expiration is in the near future:

:green_circle: Cloud credential showing an indication when expiration timestamp is "0" (i.e. the token has expired):


text:
Panic in AuthService when upgrading openLDAP enabled setup from 1.6.5-> 1.6.6-rc2.

Setup:
Rancher server setup ->1.6.5
Have openLDAP enabled
Upgrade to  1.6.6-rc2
Once rancher-server is upgraded , there is constant Panic seen in AuthService
Not able to access "Admin"-> AccessControl tab from UI.
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x50 pc=0x80ad14]

goroutine 1 [running]:
github.com/rancher/rancher-auth-service/vendor/github.com/urfave/cli.HandleAction.func1(0xc420207988)
	/go/src/github.com/rancher/rancher-auth-service/vendor/github.com/urfave/cli/app.go:472 +0x28d
panic(0xb89c40, 0x11accd0)
	/usr/local/go/src/runtime/panic.go:489 +0x2cf
github.com/rancher/rancher-auth-service/server.UpgradeCase(0xc420105488, 0x1)
	/go/src/github.com/rancher/rancher-auth-service/server/auth_server.go:652 +0x8b4
main.StartService(0xc4200c2280)
	/go/src/github.com/rancher/rancher-auth-service/main.go:135 +0x1a7
reflect.Value.call(0xb35940, 0xc50bf0, 0x13, 0xc300a9, 0x4, 0xc420055928, 0x1, 0x1, 0xc4200558b0, 0xc1b3c0, ...)
	/usr/local/go/src/reflect/value.go:434 +0x91f
reflect.Value.Call(0xb35940, 0xc50bf0, 0x13, 0xc420055928, 0x1, 0x1, 0xb84b00, 0xc4200119b0, 0xc3376e)
	/usr/local/go/src/reflect/value.go:302 +0xa4
github.com/rancher/rancher-auth-service/vendor/github.com/urfave/cli.HandleAction(0xb35940, 0xc50bf0, 0xc4200c2280, 0x0, 0x0)
	/go/src/github.com/rancher/rancher-auth-service/vendor/github.com/urfave/cli/app.go:481 +0x198
github.com/rancher/rancher-auth-service/vendor/github.com/urfave/cli.(*App).Run(0xc4200fc000, 0xc4200104b0, 0x3, 0x3, 0x0, 0x0)
	/go/src/github.com/rancher/rancher-auth-service/vendor/github.com/urfave/cli/app.go:240 +0x560
main.main()
	/go/src/github.com/rancher/rancher-auth-service/main.go:116 +0xcfb

Rancher server setup ->1.6.5
Have openLDAP enabled
Upgrade to 1.6.6-rc3
Once rancher-server is upgraded , there is no panic seen in  AuthService .
Able to access "Admin"-> AccessControl tab from UI successfully.


text:
WIP: Add EnableRBAC to AKS cluster creation

Fixes: rancher/rancher#15230
Requires: https://github.com/rancher/kontainer-engine/pull/80

LGTM

TF Is unrelated and I opened anew issue for it: https://github.com/rancher/rancher/issues/15471

closing in favor of https://github.com/rancher/rancher/pull/15514

source: gharchive/pull-request

authors: cjellick maxkorp nathan-jenan-rancher


text:
add azure drivers

@cjellick @ibuildthecloud @will-chan

For the record, we are holding off on azure for now. do not merge.

repo: rancherio/go-rancher

license_source: bigquery


text:
Failures on OSX

I've been getting failures on OSX. They seem like random failures because they only seemed to appear on some branches even when the checkouts are identical. I think I've narrowed it down to an issue with "close_windows_when_empty" setting, but not sure yet what the best to solve it is or why it's happening.
In build 3126 if close_windows_when_empty is true then Sublime Text won't open. It seems like ST is crashing, it's not, it's just opening and then instantly closing due to a bug with that setting.
The install_sublime_text.sh script anticipates this:
https://github.com/randy3k/UnitTesting/blob/1f97a12a8dc0a1a920a4e644a5be0769e4c8e010/sbin/install_sublime_text.sh#L90
if [ ! -f "$STP/User/Preferences.sublime-settings" ]; then
    echo creating sublime package directory
    mkdir -p "$STP/User"
    # make sure a new window will be opened
    echo '{"close_windows_when_empty": false }' > "$STP/User/Preferences.sublime-settings"
fi

However, on some branches on OSX it looks like that settings file isn't being created which causes failures. It looks like it's an issue on older branches which makes me think it's some issue with Travis caching that settings file and the code above won't create the settings if the preferences file already exists.
For example:
On this master branch there are failures: master
When I create a new branch off the master branch it runs fine: upgrades
Combing through the log file the master branch is missing the message "creating sublime package directory" which means the above is not being executed and so I'm guessing it's failing because "close_windows_when_empty" isn't being set to false.
This is at least my initial guess. I can't see anything else it could be.

My guess is https://github.com/randy3k/UnitTesting/blob/1f97a12a8dc0a1a920a4e644a5be0769e4c8e010/sbin/install_sublime_text.sh#L53 opens and closes sublime text. If it closes faster enough, the Preference file won't be created and the close_windows_when_empty settings will be correctly applied.
We just need to just that last session to the front.

hope 63fb79211556f2cdd44a3d751db874ee6ac7d591 and 0.10.6 will fix it.

Let me know if the latest release fix the random error. It should actually be discovered earlier, however we don't have enough users to allow such.

How can I go about testing it. There doesn't seem to be an easy way to select to use the latest master branch of UnitTesting. It would be nice to be able rerun failing builds with the latest version UnitTesting. We can set environment variables in Travis e.g. you can set UNIT_TESTING_MASTER=true and then rerun the build. If UnitTesting could use an environment variable like this it will make it easier to toggle the latest version on for testing.

I have just tagged a release, it should use the latest version now. To use a different tag, check this https://github.com/randy3k/AutoWrap/blob/master/.travis.yml
I will improve the docs once I have time...

Yes it's fixed. I reran the failing builds using UnitTesting master and they all pass now. Thanks.
The UNITTESTING_TAG environment variable is exactly what I was looking for. With that you can set the tag or branch of UnitTesting to use without needing to modify the build itself. You can add the environment variable in the Travis Ci setting panel. Rerunning a build are setting that will use the latest UnitTesting. Very useful because it saves having to needlessly edit the build itself.

Thanks for bringing up this, I didn't realize there is such a usage.

license: mit


text:
[ci skip] Fix the documentation for Worksheet#cols

A small documentation fix adding a missing quote mark and curly bracket.

Any chance I could get you to fix the is => if typo as well?

@randym I am not sure about the /is/if/ replacement. I removed the is so the sentence can be read as warn - row 1 does not have a cell at 2.
Let me know if it is good. Thanks

authors: randym repinel

repo: randym/axlsx


text:
Ability to record multiple events when dispatching one action

First off, this library is awesome. We (@segmentio) use this in-house and love it! Awhile back, I started building a Redux middleware similar to this and was pleasantly surprised when a friend pointed this out. You guys rock!
Now... I've found that we often want to fire off two analytics.js events in a single action. For example, given this chunk of code:
// signup: create a user and a workspace
const { user, workspace } = await api.createUserAndWorkspace(emailAddress)
dispatch({
  type: 'SIGNED_UP', // whatever
  payload: { // arbitrary... stuff the reducer needs
    workspace_id: workspace.id,
    user_id: user.id
  }
})

We'd want to track two things:
analytics.identify({ email: emailAddress }) // identify the new user
analytics.track('Workspace Created', { user_id: user.id, workspace_id: workspace.id }) // record the workspace creation

Is this something you've incountered? If so, how have you handled it? All of the options I've explored seem more complicated/leaky than just calling window.analytics.identify() directly :/

Great to hear @stephenmathieson. Yup, it's always always been either identity or alias (for Mixpanel). If you're using 1.4.0+, you should be able to use the array syntax. Tonight's 1.5.0 brings equal support for this feature to custom mappers. This will be better documented in the future. 😉
Let me know if this works for your use case.

I can't believe I missed that. Thanks a ton - this is perfect!

authors: bertrandk stephenmathieson

repo: rangle/redux-segment


text:
Storage Drawer API is out of date and can cause mod issues

This comes from an issue submitted to SD:
https://github.com/jaquadro/StorageDrawers/issues/492
I removed the SD api from my RS jar and so far everything is working normal.
RS: 1.4.14
MC: 1.11.2

I don't really know what's wrong, because AFAIK what RefinedStorage is doing with the API is fine.  But for some reason its version is getting picked as the definitive version in some cases, and it's out of date.

@jaquadro Can you please make it so that I can include the API with Gradle? That avoids issues as these.

Instead of including it in the jar task, could you try referencing them in sourceSets.api.java?  That's what I did for Thaumcraft/RefinedRelocation/Waila APIS -  https://github.com/jaquadro/StorageDrawers/blob/1.7.10/build.gradle#L40.  Just make sure any usage of the interfaces are completely gated behind a mod check.
If you're specifically looking for a Maven repo, I've never figured out how that's handled, though I guess CurseForge offers that for all hosted mods now?

Thanks, I will look into the source sets stuff.
Regarding hosting, I personally use a free service called Bintray. I auto-upload binaries to them (see my build.gradle) and the resulting jars are stored there.
From Bintray, you can then choose to make the API jar available for others, and they can include it in their mod then.

Fixed with Refined Storage 1.4.15.

authors: jaquadro raoulvdberge xannor

repo: raoulvdberge/refinedstorage


text:
Disable RockyLinux Tests for DGL, Disable CUDA All 11.4 Tests

Disables RockyLinux tests for DGL due to GLIBCXX version issues.  Disables 11.4 tests since they are incompatible with PyTorch.

/merge

authors: alexbarghi-nv vyasr

repo: rapidsai/cugraph-gnn


text:
Replace Python getter functions with properties in async API

To make the async API more consistent and Pythonic, replace various getter functions with @property.
Closes #129

/merge

repo: rapidsai/ucxx


text:
Manually link Algorithm and Table

Pandoc is supposed to support this, but it doesn't look possible. See #70.

Closed by 140434a819de3d6674314574ea1de0b0f646dea8.

repo: rapodaca/dialect

license: MIT


text:
Add BundleAssetMatcher to match bundles of assets for p2p trades

Rarible has an extensible DEX which allows for custom asset matcher implementations.
In order to add the ability for Rarible DEX to allow for matching bundles of assets that can be used for p2p trades, I propose below shown BundleAssetMatcher.sol
// SPDX-License-Identifier: MIT

pragma solidity 0.7.6;
pragma abicoder v2;

import "@rarible/lib-asset/contracts/LibAsset.sol";

contract BundleAssetMatcher {

    bytes4 constant public BUNDLE_ASSET_CLASS = bytes4(keccak256("BUNDLE"));

    function matchAssets(LibAsset.AssetType memory leftAssetType, LibAsset.AssetType memory rightAssetType) internal view returns (LibAsset.AssetType memory) {
        bytes4 classLeft = leftAssetType.assetClass;
        bytes4 classRight = rightAssetType.assetClass;

        if (classLeft == BUNDLE_ASSET_CLASS) {
            if (classRight == BUNDLE_ASSET_CLASS) {
                bytes32 leftHash = keccak256(leftAssetType.data);
                bytes32 rightHash = keccak256(rightAssetType.data);
                if (leftHash == rightHash) {
                    return leftAssetType;
                }
                return LibAsset.AssetType(0, EMPTY);
            }
        }
    }
}

This simple AssetMatcher implementation can be deployed and registered as a matcher in the matchers mapping of the AssetMatcher contract.
Below is an accompanying BundleTransferProxy. There are ways to make this proxy more efficient by using safeBatchTransferFrom in the case of ERC1155 assets and packing arrays of asset details in the structs. But I have tried to keep this proxy as simple as possible.
This BundleTransferProxy has to be registered in the proxies array with the bytes4 key as bytes4(keccak256("BUNDLE")) in the TransferExecutor contract. Also, we would need to call the addOperator method on BundleTransferProxy so set Rarible contract(s) an operator.
// SPDX-License-Identifier: MIT

pragma solidity >=0.6.9 <0.8.0;

import "../roles/OperatorRole.sol";
import "@rarible/exchange-interfaces/contracts/ITransferProxy.sol";
import "@openzeppelin/contracts-upgradeable/token/ERC20/IERC20Upgradeable.sol";
import "@openzeppelin/contracts-upgradeable/token/ERC721/IERC721Upgradeable.sol";
import "@openzeppelin/contracts-upgradeable/token/ERC1155/IERC1155Upgradeable.sol";

contract BundleTransferProxy is ITransferProxy, Initializable, OperatorRole {

    struct ERC20Details {
        IERC20Upgradeable token;
        uint256 amount;
    }

    struct ERC721Details {
        IERC721Upgradeable token;
        uint256[] id;
    }

    struct ERC1155Details {
        IERC1155Upgradeable token;
        uint256 id;
        uint256 amount;
        bytes calldata data;
    }

    function __ERC20TransferProxy_init() external initializer {
        __Ownable_init();
    }

    function transfer(LibAsset.Asset calldata asset, address from, address to) external onlyOperator {
        // unpack the asset data
        ERC20Details[] memory erc20Details;
        ERC721Details[] memory erc721Details;
        ERC1155Details[] memory erc1155Details;

        (erc20Details, erc721Details, erc1155Details) = abi.decode(
            asset.assetType.data,
            (ERC20Details[], ERC721Details[], ERC1155Details[])
        );

        // transfer ERC20 assets
        for (uint256 i = 0; i < erc20Details.length; i++) {
            require(
                erc20Details[i].token.transferFrom(from, to, erc20Details[i].amount),
                "failure while transferring"
            );
        }

        // transfer ERC721 assets
        for (uint256 i = 0; i < erc721Details.length; i++) {
            erc721Details[i].token.safeTransferFrom(from, to, erc721Details[i].id);
        }

        // transfer ERC1155 assets
        for (uint256 i = 0; i < erc1155Details.length; i++) {
            erc1155Details[i].token.safeTransferFrom(from, to, erc1155Details[i].id, erc1155Details[i].amount, erc1155Details[i].data);
        }
    }
}

Hi, nice to meet You!
Tank`s for your work. I like results, that You achive, but can you add some test for metods transfer and matchAssets?
Without tests difficult to understand can metod run on the EVM correct or not, do You agree?

@SKonstantinS Sure. I'll add some tests.

Create task, close issue

authors: SKonstantinS vasa-develop

repo: rarible/protocol-contracts


text:
Connection timeout on production...

I saw tons of posts about the problem, I believe that is something on my environment, because under development everything works fine. The first problem on test under production (centOS7) was the protocol, I need to move from ws to wss.
My push-server.php
<?php
    require __DIR__ . '/vendor/autoload.php';
    require __DIR__ . '/Logger.php';
    require __DIR__ . '/Pusher.php';
    cli_set_process_title('push-server-ivdk');
    Logger::write('*** Inicializando pusher ***');
    $loop   = React\EventLoop\Factory::create();
    $pusher = new Pusher;
    $context = new React\ZMQ\Context($loop);
    $pull = $context->getSocket(ZMQ::SOCKET_PULL);
    $pull->bind('tcp://127.0.0.1:5555');
    $pull->on('message', array($pusher, 'onEntry'));
    $webSock = new React\Socket\Server('0.0.0.0:8080', $loop);
    $webServer = new Ratchet\Server\IoServer(new Ratchet\Http\HttpServer(new Ratchet\WebSocket\WsServer(new Ratchet\Wamp\WampServer($pusher))), $webSock);
    $loop->run();
?>

I did changes on Pusher.php to get the maximum information about the life cycle, but only constructor of class really write something on my PID file (as a log).
<?php
use Ratchet\ConnectionInterface;
use Ratchet\Wamp\WampServerInterface;

class Pusher implements WampServerInterface
{
    protected $subscribedTopics = array();

    function __construct()
    {
        $this->writePid('Inicializado');
    }

    public function onUnSubscribe(ConnectionInterface $conn, $topic)
    {
        $this->writePid(__FUNCTION__ . ':' .  print_r($topic,true) . ',' . print_r($conn, true));
    }

    public function onOpen(ConnectionInterface $conn)
    {
        $this->writePid(__FUNCTION__ . ':' . print_r($conn, true));
    }

continue....

I started the push-server.php , but in fact I cannot see 8080 port able to LISTEN:
Proto Recv-Q Send-Q Local Address           Foreign Address         State
tcp        0      0 0.0.0.0:nfs             0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:zabbix-agent    0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:60296           0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:sunrpc          0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:webcache        0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:mountd          0.0.0.0:*               LISTEN
tcp        0      0 localhos:personal-agent 0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:42005           0.0.0.0:*               LISTEN
tcp        0      0 localhost:smtp          0.0.0.0:*               LISTEN
tcp        0      0 0.0.0.0:31199           0.0.0.0:*               LISTEN
tcp6       0      0 [::]:nfs                [::]:*                  LISTEN
tcp6       0      0 [::]:zabbix-agent       [::]:*                  LISTEN
tcp6       0      0 [::]:41230              [::]:*                  LISTEN
tcp6       0      0 [::]:sunrpc             [::]:*                  LISTEN
tcp6       0      0 [::]:mountd             [::]:*                  LISTEN
tcp6       0      0 [::]:http               [::]:*                  LISTEN
tcp6       0      0 [::]:https              [::]:*                  LISTEN
tcp6       0      0 [::]:47422              [::]:*                  LISTEN
tcp6       0      0 [::]:31199              [::]:*                  LISTEN
udp        0      0 0.0.0.0:43563           0.0.0.0:*
udp        0      0 0.0.0.0:sunrpc          0.0.0.0:*
udp        0      0 0.0.0.0:793             0.0.0.0:*
udp        0      0 localhost:795           0.0.0.0:*
udp        0      0 0.0.0.0:nfs             0.0.0.0:*
udp        0      0 0.0.0.0:mountd          0.0.0.0:*
udp        0      0 0.0.0.0:37111           0.0.0.0:*
udp6       0      0 [::]:39569              [::]:*
udp6       0      0 [::]:57398              [::]:*
udp6       0      0 [::]:sunrpc             [::]:*
udp6       0      0 [::]:793                [::]:*
udp6       0      0 [::]:nfs                [::]:*
udp6       0      0 [::]:mountd             [::]:*
Active UNIX domain sockets (only servers)
Proto RefCnt Flags       Type       State         I-Node   Path
unix  2      [ ACC ]     STREAM     LISTENING     2832250562 /var/lib/gssproxy/default.sock
unix  2      [ ACC ]     STREAM     LISTENING     2832291649 /var/run/rpcbind.sock
unix  2      [ ACC ]     SEQPACKET  LISTENING     2832311620 /run/udev/control
unix  2      [ ACC ]     STREAM     LISTENING     2832291653 /run/dbus/system_bus_socket
unix  2      [ ACC ]     STREAM     LISTENING     2832284354 /run/systemd/private
unix  2      [ ACC ]     STREAM     LISTENING     2832250563 /run/gssproxy.sock
unix  2      [ ACC ]     STREAM     LISTENING     2832284384 /run/systemd/journal/stdout
unix  2      [ ACC ]     STREAM     LISTENING     2832314598 /run/saslauthd/mux

And my javascript caller:
function iniciarSocket()
{
	var hash = document.querySelector('meta[name="pusher"]').getAttribute('content');
	if (hash == undefined || hash == '')
	{
		console.err('Hash invalido para iniciar pusher');
		return;
	}

	var protocol = location.hostname == 'localhost' ? 'ws://' : 'wss://';
	var host = location.hostname;
	var port = '8080';
	var url = protocol + host + ':' + port ;
	console.log('Iniciando websocket em ' + url);
	var conn = new ab.Session(url,
            function() {
    			var hash = document.querySelector('meta[name="pusher"]').getAttribute('content');
        		console.log('Inscrevendo-se com hash ' + hash + ' em ' + url);
                conn.subscribe(hash, function(topic, data) {
                    console.log(data);
					}
                });
            },
            function() {
                console.warn('Conexao fechada em ' + new Date().toUTCString());
            },
            {'skipSubprotocolCheck': true}
        );
}

In fact, if I cannot see the port opened / listen on server, probably I had some problem, but actually I cannot see what it is, remember that I put libevents and zeromq under the server , and php_zmq on server (everything was installled).
Someone can help me ?

Guys any idea ???
I did a test recently,

connect via SSH on server,
run a telnet name/ip 8080 (the connection works fine)
call  my script to broadcast the message
my telnet connection receive events

So , probably my problem is related to network setting or something like this, because internally I'm able to execute the workflow, but externally not. Any tip ?!?!

repo: ratchetphp/Ratchet


text:
[Feature] Providing docker images for linux aarch/aarch64 platform

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Providing docker images of kuberay-apiserver and kuberay-operator for linux aarch/aarch64 platform
Use case
On Linux aarch/aarch64 platform, the kuberay-apiserver&kuberay-operator images docker pulled are for amd/amd64 architecture rather than aarch/aarch64.
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

#1716

repo: ray-project/kuberay


text:
[Doc] Add gofumpt lint instructions

Why are these changes needed?
Previously there were no instructions about the gofumpt linter.  External contributors had to figure it out themselves when the Lint step failed in CI for their PR.
This PR adds the linting instructions to the development documentation.  These instructions were originally written by @shrekris-anyscale.

Related issue number

Checks

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

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

This PR only updates the doc and has no relationship with the CI.


text:
GoDoc enter floating window

Is there a way to run GoDoc say 2 times, and make my cursor enter the floating window?, kind of like the default behavior of hover

What about creating a map to make the same as Ctrl+ww?

feels hacky

In fact, as @edgardleal suggested, it is more of a recommended way to move around between windows, check help CTRL-W and help CTRL-W_w.
Also, each time you run GoDoc it will destroy previous results. I do not see an easy workflow to show multiple floating GoDoc windows in neovim.

authors: aldevv edgardleal ray-x


text:
How to integrate with your go.nvim

I used to your go.nvim plugin because it works slightly better for me.
Is there a way to use it together with navigator?

handy for using the gopls installed with nvim-lsp-installer:
local path = require 'nvim-lsp-installer.path'
local install_root_dir = path.concat {vim.fn.stdpath 'data', 'lsp_servers'}

require('go').setup({
  gopls_cmd = {install_root_dir .. '/go/gopls'},
  filstruct = 'gopls',
  lsp_codelens = false, -- use navigator
  dap_debug = true,
  dap_debug_gui = true
})

Hi, thanks for all the plugins,
I am using navigator, and I would like to use the extra lsp config for go from go.nvim but keep navigator for LSP related keymap/UI etc.
Is this param lsp_codelens = false, -- use navigator still relevant to do in go.nvim ?

Check this setup:
https://github.com/ray-x/nvim/blob/6dcf5a7abc1f0489299252bcb20e56a71fa4fa5f/lua/modules/lang/config.lua#L223-L236
And disable startup gopls/lsp in go.nvim by setting lsp_cfg = false (default)
lsp_codelens = false (as navigator also supports codelens)

Thanks, I already tried to to disable lsp_cfg and I made sure go.nvim is loaded after navigator. Is there a clean way to still use the inlay hints from go.nvim  ?

authors: mattbailey ray-x sp4ke stndrf


text:
[Apple Mail] Archive function

Extension
https://www.raycast.com/yug2005/mail
Description
Just add the optional command to archive an email when it is showing the list of emails. Currently the extension shows a lot of options, ["move to span", "delete", "mark as unread", ...].
Who will benefit from this feature?
A lot of people including me, like to archive mails after they are read or no more relevant.
Anything else?

Dupe of #11040

repo: raycast/extensions


text:
[Amazon AWS] Frequency sorting for Console command

Extension
https://www.raycast.com/Falcon/aws
Description
Console command is a perfect candidate for frecency sorting, that way the most used service console links will appear at the top.
Who will benefit from this feature?
Anyone using console command to visit service consoles
Anything else?
No response

@raycastbot assign me


text:
Adding the new Gemini models.

Description

Screencast

Checklist

[ ] I read the extension guidelines
[ ] I read the documentation about publishing
[ ] I ran npm run build and tested this distribution build in Raycast
[ ] I checked that files in the assets folder are used by the extension itself
[ ] I checked that assets used by the README are placed outside of the metadata folder

If I'm not mistaken, then it's already being done here: https://github.com/raycast/extensions/pull/15949

CC @EvanZhouDev

If I'm not mistaken, then it's already being done here: #15949

Hi pernielsentikaer
Definitely you are correct.
I've added the new models to the implementation of this PR.

Apologies!

authors: arthrod d0zingcat pernielsentikaer


text:
Add font-awesome extension

Description
Add a new action to copy the font awesome glyph to the clipboard (#5050)
Screencast
https://user-images.githubusercontent.com/1195174/222089887-16f4f733-2d7f-4061-bd9c-99db99b71735.mov
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Not quite sure what I did wrong to get the label "new extension", this is supposed to be an update to the existing fontawesome extension

Looks like npx ray publish uses the name of the extension as set in package.json to determine the folder. Which in this case is not the correct folder name. Will manually re-submit


text:
Add ping extension

Description

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Anyway, thank you.


text:
tldr for own custom scripts?

Hey again, how should one go about creating a custom .md file that just doesn't qualify for the public repo?
Say I have a custom shell script I wrote and use twice a month (and I never remember the parameters), tldr would be the perfect tool to just remind myself of the script's usage.
Can I add my own pages, currently? Won't they get deleted from the cache?
Edit: So it turns out adding my own .md under /common doesn't work, possibly because tldr looks up the online repo and decides the command doesn't exist.

Yeah, tldr is looking in the index.json file first for the page. I've just pushed an update to look for the page in $configdir/local/ first. The commit message contains details:  https://github.com/raylee/tldr/commit/92e0545048b9bb702aca62b7df30fe299defb5c9

If the new version doesn't work for you, please re-open this issue. Thanks!

authors: raylee tmarplatt

repo: raylee/tldr


text:
Platform DRM

PLATFORM_DRM added to source and examples makefiles and to cmake build system
SUPPORT_MOUSE_CURSOR_RPI changed to SUPPORT_MOUSE_CURSOR_DRM, mouse cursor code added from @chriscamacho
public SetGraphicDeviceName(...) added to let the user select the graphics device to use (useful only for PLATFORM_DRM)
Config flag FLAG_INTERLACED_HINT added to let the DRM mode selection allow to choose also interlaced graphics mode, otherwise only a progressive mode is choosen

Please tell me if should any comments, changes etc.!
On Raspberry Pi 1-4 SetGraphicDeviceName(...) shouldn't be needed, it should select automatically the available one. On other Linux distributions the device name could differ, e. g. depending of the grapics card manufacturer.

The Travis CI needs additional build jobs for PLATFORM_DRM and preinstalled libgbm, libdrm and maybe libmesa or whatever provides EGL and OpenGL ES libraries. It should work on any Linux distribution that provides GBM and DRM which is any modern Linux distribution as far as I know.

@kernelkinetic Added two review comments.
About Travis CI, no worries, that script should be reviewed.

@raysan5 I would prefer the automatic selection if no DEFAULT_GRAPHIC_DEVICE_DRM is defined. So one can choose a specific device if necessary and it works out of the box otherwise. I'll also look if I can automatically select by checking all available interfaces if they can render, that's just a flag to check if I'm remembering it correctly. Anyways, I think I'll send a commit tomorrow ☺

Go bindings, not that it matters much, would prefer function, nice and clear, and can be accessed easily. Users can also pass CGO_CFLAGS='-DDEFAULT_GRAPHIC_DEVICE_DRM="/dev/dri/card1"' if and when they need,  but if it can be done with some detection/checking the best. I guess rare would be the cases where the user really wants to pick.

This commit uses the DEFAULT_GRAPHIC_DEVICE_DRM string if it's defined and otherwise tries for /dev/dri/card1 and if that fails for /dev/dri/card0 to support Raspberry Pi 0..4.
I've also implemented automatic selection of the render device but it seems that there are some quirks in Raspberry Pi driver implementation which makes it working on Linux but not on Raspberry Pi or vice versa. So at the moment this commit is what gives the most flexibility so far.

Merged! :D
Thanks to all the contributors for this amazing work!

license: Zlib


text:
[split] rcore, web, desktop, android changes (batch 4)

PR changes

Fixes ToggleBorderlessWindowed duplicated glfwSetWindowSize calls as per https://github.com/raysan5/raylib/pull/3216#discussion_r1334832946.
On rcore_desktop.c: L714.

First and second passes to remove unneeded platform macros for PLATFORM_ANDROID.
On rcore_android.c: L148-L477, L479, L483-L642, L656-L658, L662-L664, L679, L683-L685, L687, L702-L755, L758, L770, L774, L792, L794-L808, L831, L835-L837, L839, L849, L851.

See item 2 above.

Removes unneeded platform macros for PLATFORM_DESKTOP.
On rcore_desktop.c: L1153, L1157.

Relocate GetGamepadName.
On rcore_android.c: from L1631-L1636 to R1052-R1058.
On rcore_desktop.c: from L1500-L1508 to R1515-R1523.
On rcore_web.c: R1038-L1052.
Added tracelog error message to GetGamepadName.
On rcore_android.c: R1055.
Added tracelog error message to SetGamepadMappings.
On rcore_android.c: R1069.
On rcore_web.c: R1065.

Added the missing comment about gamepad on web.
On rcore_web.c: R1044.

Status

#3339

Environment

Compiled with emscripten/emsdk on Linux (Mint 21.1 64-bit).
Tested on Firefox (115.1.0esr 64-bit) and Chromium (115.0.5790.170 64-bit) both running on Linux Mint (21.1 64-bit).

Edits
1: added line marks.
2: added first pass.
3: added second pass; added line marks.
4: added removal of platform macros for desktop; editing; formatting.
5: added relocate and updates.
6: added missing comment.

@ubkp thanks again for all those reviews! Please, let me know when the batch is ready for merging!

@raysan5 I think it's ready. Please merge it. :+1:

@ubkp thanks! merged!


text:
Add parabolic primitive

Add support for a parabolic primitive to enable parabolic lenses.

Completed and merged in commit 9c5937e42ebb86082db7d4a8940ad7e818858436.

authors: CnlPepper mattngc

repo: raysect/source


text:
feat: allow configuring cors middleware

few session variables are also exposed as config

Pull Request Test Coverage Report for Build 6033273958

5 of 8 (62.5%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 48.335%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cmd/serve.go
0
1
0.0%

config/config.go
5
7
71.43%

Totals

Change from base Build 6032957703:
0.02%

Covered Lines:
5500

Relevant Lines:
11379

💛  - Coveralls

authors: coveralls kushsharma

repo: raystack/frontier


text:
Lora files not being correctly applied

I just set up Dream Factory on top of my automatic1111 and noticed that Lora files seem to not be working correctly. Using Auto1111 on the same machine I can use the same prompts and seeds with a lora model and get drastically different results from what dream factory produces. It appears that the loras are not being applied at all?
I have tried inserting them in the prompt in the following ways:
<lora:[filename]:[strength]>  ((the way it works in Auto1111 by default & the way it's copied out of the clipboard))
<[filename]:[strength]>  ((as suggested in issue #28 ))
lora:[filename]:[strength] ((just to test))
Also noticed that in the gallery when you are reviewing the prompts the lora part is missing from the preview like it has been commented out in some way as well. I have verified that the files & prompts are working correctly in Auto1111 but not for dream factroy, is there a config that needs to be added for dream factory for loras to work properly?
Any help is appreciated, really enjoy being able to use dreamfactory so far

I'm using a few LoRAs daily and they're definitely being applied (I run the same prompt/seed with several different loras appended to the end, and they all look radically different in the manner I'd expect to see from each lora). I haven't tested the results against images directly generated with Auto1111; it's possible the API call may be slightly different from native - I'll run a few tests tomorrow.
If you're recently updated Dream Factory, do a hard refresh of your gallery page (control-F5 in Chrome, or clear your browser cache in other browsers). The gallery had a bug where it was treating lora embeddings as HTML and not displaying them, even though they were present in the metadata - it was fixed a few weeks ago; here is an image that just came out of one of my machines; you can see the lora in the prompt:

Ok, ran a test today and am getting the same image from Dream Factory as I am from Auto1111 natively when using loras. I'm using --xformers so there may be some very minor differences, but that is expected.
From Dream Factory:

From Auto1111:

Settings:
The easter bunny painting colorful easter eggs, <lora:warcraftTheLora_v10:0.6>
1536x1024 w/ hires fix enabled, scale 8.4, DDIM @ 55 steps, seed 196862028

For reference, this is the image I get if I keep everything the same but remove the lora reference:

It looks like everything is working properly. In Auto1111, do you see your lora files when you click "show extra networks" from the txt2img tab?

I tried a similar test this afternoon, please let me know if there is something bone headed I've done
Generated an image with Dream factory using the following .prompt file
# *****************************************************************************************************
# Dream Factory random prompt file
# created 2023-03-06 at 17:55:10 via the integrated prompt editor
# *****************************************************************************************************
# these are the default configuration parameters set in your config.txt file
# you may override anything in this section if you wish, otherwise skip down to the [prompts] section(s) below
[config]

!MODE = random							# random mode; queue random prompts from [prompts] sections below
!DELIM = " "							# delimiter to use between prompt sections, default is space
!WIDTH = 512							# output image width
!HEIGHT = 512							# output image height
!HIGHRES_FIX = no				        # fix for images significantly larger than 512x512, if enabled uses !STRENGTH setting
!STEPS = 20							# number of steps, more may improve image but increase generation time
!SAMPLER = Euler a            			# sampler to use; press ctrl+h for reference
!SAMPLES = 1					      	# number of images to generate per prompt
!MIN_SCALE = 7							# minimum guidance scale, default = 7.5
!MAX_SCALE = 7							# maximum guidance scale, set min and max to same number for no variance
!RANDOM_INPUT_IMAGE_DIR =				# specify directory of images here; a random image will be picked per prompt
!MIN_STRENGTH = 0.75					# min strength of starting image influence, (0-1, 1 is lowest influence)
!MAX_STRENGTH = 0.75					# max strength of start image, set min and max to same number for no variance
!CKPT_FILE = mdjrny-v4.safetensors     # model to load, press ctrl+h for reference

# optional integrated upscaling

!USE_UPSCALE = no						# upscale output images?
!UPSCALE_AMOUNT = 2.0					# upscaling factor
!UPSCALE_CODEFORMER_AMOUNT = 0.0		# how visible codeformer enhancement is, 0-1
!UPSCALE_GFPGAN_AMOUNT = 0.0			# how visible gfpgan enhancement is, 0-1
!UPSCALE_KEEP_ORG = no				# keep the original non-upscaled image (yes/no)?

# optional negative prompt

!NEG_PROMPT =

# *****************************************************************************************************
# prompt section
# *****************************************************************************************************
[prompts]

The easter bunny painting colorful easter eggs, <lora:rabbitRabbit_v10:0.7>

# put your prompts here; one per line
# you may also add additional [prompt] sections below, see 'example-random.prompts' for details

This is the following image generated

Using the Seed: 4128928803 I generated the image via A1111 using the following prompt
The easter bunny painting colorful easter eggs, <lora:rabbitRabbit_v10:0.7>
Steps: 20, Sampler: Euler a, CFG scale: 7, Seed: 4128928803, Size: 512x512, Model hash: aba96b389d, Model: mdjrny-v4

Using the same seed in A1111 I generated another imaged with the following prompt
The easter bunny painting colorful easter eggs,
Steps: 20, Sampler: Euler a, CFG scale: 7, Seed: 4128928803, Size: 512x512, Model hash: aba96b389d, Model: mdjrny-v4

The image generated from Dream factory matches the image from A1111 without the Lora prompt, However after checking for updates (was up to date) and clearing my browser cache I can now see the lora prompt inside dream factory gallery
Additionally I can see the Lora model inside A1111 when I click show extra networks

Still fairly new to stable diffusion / Automatic1111 etc so there is a potential for configs to be incorrect ect. any guidance on where to check would be appreciated
Below is the confix.txt file from the dream factory dir, the D:\AI\stable-diffusion-webui is actually my install location for Automatic1111
###############################################################################
### Dream Factory default configuration file
###############################################################################

# Path to installed Automatic1111 stable diffusion repo (e.g.: C:\Applications\stable-diffusion-webui).
# You must populate this with a working SD installation for Dream Factory to operate!
SD_LOCATION = D:\AI\stable-diffusion-webui

# Specify which GPU(s) to use here; auto will attempt to use all detected devices
# to specify individual GPUs, use a comma-separated list of device IDs.
# e.g. USE_GPU_DEVICES = 0, 1, 2
USE_GPU_DEVICES = 0, 1

# Starting port that SD instances will use; additional GPUs will each increment this
# by one when deciding which port to operate on - e.g. if you leave this at 7861 and
# have 3 GPUs, then ports 7861, 7862, and 7863 will be used by SD instances.
# These are not accessible outside of the local machine Dream Factory operates on and
# there is generally no reason to change this.
SD_PORT = 7861

# If you have multiple GPUs, this is how many are allowed to initialize at once.
# Initialization only happens once at startup, but it very memory-intensive (system RAM,
# not VRAM). Each GPU will use nearly 10GB of system RAM during initialization, so
# allowing them all to init simultaneously may cause issues depending on system resources.
GPU_INIT_STAGGER = 1

# Directory containing your prompt files.
# Locations are relative to Dream Factory's installation directory unless specified.
PROMPTS_LOCATION = prompts

# Directory containing your wildcard files.
WILDCARD_LOCATION = prompts\wildcards

# Directory where output images will be created.
OUTPUT_LOCATION = output

# Use the webserver (yes/no)? This is required to use the browser interface.
WEBSERVER_USE = yes

# Port the webserver listens on.
# Note that ports under 1024 require root permission on Linux.
WEBSERVER_PORT = 8080

# Set this to yes if you want to be able to access the webserver UI from other computers.
# At the default "no" setting the web UI is inaccessible anywhere except at the local computer running the server!
WEBSERVER_NETWORK_ACCESSIBLE = no

# Enable webserver authentication?
# This is the most basic form of HTTP authentication and should not be considered secure!
# However if you're going to make this accessible via WAN/internet it's better than nothing.
WEBSERVER_USE_AUTHENTICATION = no

# Webserver login credentials; make sure to change these if you're using authentication!
WEBSERVER_AUTH_USERNAME = admin
WEBSERVER_AUTH_PASSWORD = password

# Automatically attempt to open the server interface in your browser (yes/no)?
# This has caused some confusion, but it literally does just that - it'll pop open Chrome
# or whatever your default browser is, with Dream Factory loaded. Doesn't work all on OSes.
WEBSERVER_OPEN_BROWSER = yes

# Log webserver messages to the console (yes/no)? For debugging, leave it disabled unless you like spam.
WEBSERVER_CONSOLE_LOG = no

# Gallery maximum images to display.
GALLERY_MAX_IMAGES = 200

# Gallery refresh interval in seconds; set to zero to disable auto-refresh of gallery.
GALLERY_REFRESH = 30

# Optional folder to display in the gallery (and alias to refer to it)
GALLERY_USER_FOLDER =
GALLERY_USER_FOLDER_ALIAS = favorites

# The editor won't attempt to apply context-sensitive color styling to prompt files over this character limit.
# Values above 200000 will significantly increase loading time for prompt files that exceed that character threshold.
# If you're working with massive .prompt files, it's best to edit them using an external editor.
EDITOR_MAX_STYLING_CHARS = 80000

# You can set your own defaults for prompt file settings below.
# Settings specified in individual prompt files will always override these.

PF_WIDTH = 512             			# output image width, default is 512
PF_HEIGHT = 512            			# output image height, default is 512
PF_HIGHRES_FIX = no					# helps a lot when generating images significantly larger than 512x512 at the cost of speed
PF_SAMPLER = DPM++ 2M Karras		# sampler to use (create a new prompt file using the web UI to see a full list of options)
PF_STEPS = 20              			# number of steps, default = 50
PF_SCALE = 7.5              		# guidance scale, default = 7.5
PF_SAMPLES = 1						# number of images to generate per prompt
PF_USE_UPSCALE = no					# use ESRGAN to upscale output images?
PF_UPSCALE_AMOUNT = 2.0				# upscaling factor (2 means you'll get an image with double the width and height of the original)
PF_UPSCALE_CODEFORMER_AMOUNT = 0.0	# visibility of codeformer face enhancement (0 = off, 1 = full effect)
PF_UPSCALE_GFPGAN_AMOUNT = 0.0		# visibility of gfpgan face enhancement (0 = off, 1 = full effect)
PF_UPSCALE_KEEP_ORG = no			# keep the original non-upscaled image (yes/no)?
PF_NEG_PROMPT = 					# if you have a 'catch all' negative prompt you typically use, enter it here
PF_FILENAME =						# set a default custom filename: https://github.com/rbbrdckybk/dream-factory#filename

# Set a default .ckpt file here so that whenever you set !CKPT_FILE to nothing (e.g. '!CKPT_FILE = '), this default
# will be loaded. If you don't set anything here, !CKPT_FILE= will just use whatever happens to be loaded in Auto1111.
PF_CKPT_FILE =

# automatically insert the trigger word when using custom models?
# off = disable this
# start = at the start of the prompt (the default)
# end = at the end of the prompt
# first_comma = after the first comma (or end if prompt contains no commas)
# you must edit the model-triggers.txt file (auto-generated after first run) for these to work
PF_AUTO_INSERT_MODEL_TRIGGER = start

# Set the number of prompts to queue at once when using prompt files set to random mode.
# The only real reason you'd want to change this is if you're specifying multiple models (with !CKPT_FILE = model1, model2, etc).
# In random mode the models will rotate every time a batch of prompts is queued, so you can effectively control how often
# your models will switch by setting this.
RANDOM_QUEUE_SIZE = 50

I am stumped - everything looks fine in your config.txt and your prompt file, but to be 100% sure, I copied it and ran it myself. I downloaded the same rabbit LoRA and the midjourney-v4 model as well.
Dream Factory gives me the same image that Auto1111 generated for you (see below), so it seems to be working properly here. Is your Auto1111 repo up to date (from the command line in the Auto1111 base directory, you can type git pull to grab the latest version)? It's possible there is an issue with the Auto1111 API call in older versions, but I'm just guessing at this point.
I tested with --xformers enabled and disabled (I get the same image on both sides regardless), and I don't have anything else in my Auto1111 startup script.
If your Auto1111 is up to date, I'm honestly not sure what else could possibly cause this.

The prompt file I used is an exact copy of yours; I just added the !SEED you used and turned off model trigger insertion:

I guess I'll reinstall both Auto1111 and Dream factory to see if that resolves my issue, checked Auto1111 directory and it's up to date.

Uninstalled all remnants of Auto1111 & Dream factory, found some old python 2.x.x installs from old dev work, uninstalled them, uninstalled Anaconda, uninstalled python 3.10.6. Reinstalled everything clean and still experiencing the same problem. Only thing of notice is when running setup.py for the first time received the following error. Any suggestions for remedy or config files or logs I need to provide?
Personally stumped at this, any suggestions would be great :)

On the setup.py installation error, you can try re-running with the shell option to fix; depending on your environment it might not be able to find a needed executable (git, etc). If you add the --verbose option it'll echo everything to the screen so you can see any errors that might pop up:
python setup.py --shell --force --verbose

Honestly I'm completely at a loss as to why LoRA embeddings in your Dream Factory prompts don't seem to be having any effect. I have 4 installations running DF (mixed windows/linux environments with various dissimilar hardware) and loras are working in all of them and I haven't had any other reports of loras not working.
Some things you can try, although I'm honestly not sure they'll be all that helpful:

In your DF config.txt, try enabling console logging for the webserver and see if you see any errors when running prompt files containing loras:

WEBSERVER_CONSOLE_LOG = yes

Also in your DF config.txt, try switching the Auto1111 port to 7860 (the default that Auto1111 uses when running it normally), then start Auto1111 manually (and wait for it to fully load), and finally start DF. DF will see that Auto1111 is already running on port 7860 and use it, which will allow you to monitor the Auto1111 console to see if there are any errors popping up there:

SD_PORT = 7860

If you're running any command line arguments in your Auto1111 startup script (webui-user.bat in your Auto1111 root directory for Windows), disable them to see if that makes a difference. I'm running --xformers and --no-half-vae on some of my machines, but there are many options I haven't tested.

So after a fair amount of testing and a lot of testing later, I seem to have found a solution,
Reference: https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/7984
added command line arg --api to webui-users.bat
and in  webui.py added modules.script_callbacks.before_ui_callback()  on line 190 in def api_only()
for whatever reason this has solved my problems.
Small side note, I installed dreamfactory onto a completely new machine and experienced all same problems and resolved them with this same solution.
Really appreciate all the help, if you need any additional information from me please let me know happy to help!
Thanks!

Aha - glad you found the issue! Very strange that none of my Auto1111 installations have the issue, but hopefully he'll patch a fix into an upcoming release so others don't experience the problem. At least I'll be able to point others to the resolution if anyone else mentions it - thanks for the info!

@TheHaBachi, looks like this has been fixed if you want to test, its working for me.

authors: Koneko349 TheHaBachi rbbrdckybk

repo: rbbrdckybk/dream-factory


text:
Decouple Storybook, easily

I’ve got already an existing react component which requires authentication and does a lot of other things, and I had a hard time trying to get react-trello into this project.
Ultimately I failed, for one, it was to to hard to put the entire react-trello structure in our big existing React (v15) project, the other reason was that I was not able to decouple Storybook from react-trello. In the end, I copied the structure from react-trello-example and into my existing project and added react-trello as a dependency in package.json. Is this actually the correct way?
However, it would be nice to work directly with the "official" react-trello project, and testing with Storybook. But at some point, when your’re done, to get rid of Storybook.
Thanks for all,
Kalaschnik

@Kalaschnik The release version of this library does not include the storybook. I am not sure I understand your question. To make it more clear for you to understand the usage, I have added a code sandbox example here: https://codesandbox.io/s/1o3zj95m9j

@rcdexta What do you mean by the release version of this library? react-trello-example? I actually have the same setup as you provided in the sandbox. So it is actually the intended way to use this project with react-trello-example and put react-trello as a dependency in package.json?

authors: Kalaschnik rcdexta

repo: rcdexta/react-trello


text:
feature: translate trello to ptBR

Hello guys,
a time ago i opened an Pull Request but i lost the acess.
Then i'm sending another PR to translate react-trello to PT-BR

Hi!
Nice job!
Could you add language to the list in README also? https://github.com/rcdexta/react-trello#i18n-support

@mateusbays thank you for PR!
Did you see this? https://github.com/rcdexta/react-trello/pull/524

authors: dapi mateusbays


text:
continuous deployment, repo organization

[x] repository reorg, pending https://github.com/tgrospic/rnode-client-js/issues/14
[x] continuous deployment of this repo for beta testing / review: https://rv2020-beta.netlify.app/

we plan for the the coop to have its own fork with continuous deployment; that's out of scope of this issue

[ ] add link / redirect from earlier site(s)

So far, I have been using drag-and-drop to netlify after running npm build:web manually after selected commits to deploy https://rv2020-m3.netlify.app/ballot.html.
I'd like to have the master branch automatically deployed (a) to reduce maintenance burden but also (b) to make the process more transparent so that voters can have confidence about what software they're using. This example looks just right:

Static Site Generators with Node.js

I'd also like to publish release artifacts so that folks can just download the static site and host it locally for increased confidence.
I'm not currently using this repo for the rv2020-m3 source code; I'm using https://github.com/rchain-community/rnode-client-js , a fork of https://github.com/tgrospic/rnode-client-js . The scope of rnode-client-js is evolving; it started before rnode supported sufficiently browser-compatible APIs to eliminate the need for a back end for RChain dApps. (https://github.com/tgrospic/rnode-client-js/issues/14 ) So only a subset of the code there is relevant to the voting dApp.
Meanwhile, I re-used this repo for my rchat mirror-postgres-to-RChain prototype. I suppose that belongs in a repo called pg2rho or rchain-db-sync or rchain-django-sync or some such.
The o2r materials were based on the idea of migrating discord credentials to rchain using OAuth (hence o2r); since the coop is using REV address credentials, that's no longer relevant.

I made a dust3 branch just for the dust voting app: 5eb8722
And I actually reset master to match dust3.
What was formerly master, 4131818, is now in the rchat-mirror branch.

@dckc maybe you can use GitHub action to automatically publish site with github-pages similar to rnode-client-js.
https://github.com/tgrospic/rnode-client-js/blob/master/.github/workflows/github-pages.yml

@tgrospic writes:

@dckc maybe you can use GitHub action to automatically publish site with github-pages similar to rnode-client-js.

yes, that's the idea in the "Static Site Generators with Node.js" link above.
I gather @ian-bloom is testing it.

Darn; the repo reorg messes up the git blame history.
What I should do is prune my fork of rnode-client-js down to the stuff that's relevant here and then make that a dependency.

@dckc I'll be finish with the split of web and grpc part in a couple of days. rnode-client-js will be just web part with helpers.

Ian suggests a fork under the rchain org and deployment using github pages under a URL of the secretary's choosing. Sounds great to me!

A goal of this issue is to not host the general wallet functionality with the voting dApp.

@tgrospic thanks to your work on https://github.com/tgrospic/rnode-client-js/issues/14 , I was able to do a satisfactory reorg. Please review #53 . To see it in action, visit https://rv2020-beta.netlify.app/
It's based on a few small tweaks to rnode-client-js in https://github.com/rchain-community/rnode-client-js/tree/rv2020-snowpack ; I guess I owe you a PR or something.

@ian-bloom I went ahead and set up continuous deployment to https://rv2020-beta.netlify.app/
netlify is also set up to do preview deploys for PRs to this repo.
The "production branch" is set to m3g until #53 lands.

I should redirect the earlier sites.

[ ] merge / rebase tally work by @jimscarver

https://github.com/rchain-community/rv2020/blob/6977425c75643721f4ec06200bfe1dfda3bbdd59/src/web/tally.sh

and lo, there was https://github.com/rchain/rvote

authors: dckc tgrospic


text:
String Read and Write

I am converting a Windows8 websocket client to Xamarin and need PCL support. I found this project, but the implementation is very different from the MessageWebSocket.
Can the documentation be updated to demonstrate the reading and writing of string messages ? I noticed there was a helper project, but, It requires using a json format which my server will not support.

Hi,
As you would have gathered, sockets just shuffle bytes back and forward. In order to send and receive strings you need to implement a basic protocol that both sides can follow in order to communicate (here is the extensive websocket protocol!). For strings, the two most popular options are:

terminate each message with a delimiter
precede each message with its length.

I'm a fan of the second option. I've outlined them both in here in issue #6, that should be enough to get you going.
At some stage I may add documentation to cover cases like this, but in the meantime, these are just plain sockets so there is plenty out there on the net if you want to read further. The helper project will definitely add a StringMessenger-like class in the future.

Putting together some samples for LINQPad, here's an implementation of the string protocol as extension methods on ITcpSocketClient. You can use SendStringAsync and ReceiveStringAsync to send and receive string messages up to Int32.MaxValue length.
// Implements a basic string reading/writing protocol
// bytes 1 - sizeof(int32) 	: message length
// subsequent bytes			: message
public static class StringHelpers
{
	public static async Task<string> ReceiveStringAsync(this ITcpSocketClient c)
	{
		// get the length of the next message
		var sizeOfInt = sizeof(Int32);
		var sizeBuf = new byte[sizeOfInt];

		await c.ReadStream
			   .ReadAsync(sizeBuf, 0, sizeOfInt)
			   .ConfigureAwait(false);

		var msgLength = BitConverter.ToInt32(sizeBuf, 0);

		// get the actual message
		var msgBuf = new byte[msgLength];
		await c.ReadStream
			   .ReadAsync(msgBuf, 0, msgLength)
			   .ConfigureAwait(false);

		// convert to string
		var msg = Encoding.UTF8.GetString(msgBuf, 0, msgLength);

		return msg;
	}

	public static Task SendStringAsync(this ITcpSocketClient c, string s)
	{
		// convert to utf8 bytes
		var msgBytes = Encoding.UTF8.GetBytes(s);
		var msgLength = msgBytes.Length;
		var msgLengthBytes = BitConverter.GetBytes(msgLength);

		// prepare the bytes to send
		var allBytes = Enumerable.Concat(msgLengthBytes, msgBytes).ToArray();

		// send
		return c.WriteStream.WriteAsync(allBytes, 0, allBytes.Length);
	}
}

authors: NVentimiglia rdavisau

repo: rdavisau/sockets-for-pcl


text:
Fix tests 27, 28, and 30

Fix 3 tests that are failing due to a missing tmp directory.
Enhance run-test.perl to track the total number of tests and the number of tests that passed.

LGTM

authors: dbooth-boston glenna-m

repo: rdf-pipeline/framework


text:
res.dataset() is not a function when no factory is provided

I think this is confusing. Since this detects whether a factory is provided or not, calling .dataset() without a factory should throw something more explicit than TypeError: res.dataset is not a function

see #5

authors: bergos vhf

repo: rdfjs-base/fetch-lite


text:
http status

http status

somple


text:
Lightning Router removing trailing / on paths

Trying to navigate to paths like: /entity/movie/5025533520783917112/ fail due to the route not being created correctly. Its removing the trailing slash...

Thanks for the bug report. The reason we strip the trailing slash is to determine how much floors a link has: https://github.com/rdkcentral/Lightning-SDK/blob/0accb42cf6479e711a5c604d6ccc140050b44b7d/src/Router/utils/route.js#L31
and this is again being used to match a hash against configured routes: https://github.com/rdkcentral/Lightning-SDK/blob/0accb42cf6479e711a5c604d6ccc140050b44b7d/src/Router/utils/route.js#L40
We're now testing a fix for this issue and will notify you when it's available in master:
https://github.com/rdkcentral/Lightning-SDK/commit/e111f4b38a134f7695369e930e47491b86550bcb

Fixed in v4.4.0

authors: chiefcll erikhaandrikman

repo: rdkcentral/Lightning-SDK


text:
replaced video tag with audio tag for all fmp4_mp3 tests

added patch which replaced video tag with audio tag for all fmp4_mp3 tests

1.In test.js, we can see one more place we called  this.getNewVideoTag();. may I know in which case this function call is triggered.
TestExecutor.prototype.onfinished = function() {
2.There is a definition for getNewVideotag() in test.js. what is the used of that function..do we need similar function for Audio.
TestExecutor.prototype.getNewVideoTag = function() {
// Override this function to anchor one to the DOM.
return document.createElement('video');
};

repo: rdkcentral/MVT


text:
CPU and RAM Values Missing in Main Pods Screen

Issue: On the main screen that lists all the pods, the columns for CPU and RAM usage are not showing any values. This makes it difficult to see resource consumption for the pods.
Steps to reproduce:

Open KubePulse.
Navigate to the screen listing all the pods.
Filter by namespace
Check the columns for CPU and RAM usage.

Observed behavior: The CPU and RAM usage columns are empty for all pods.
Expected behavior: The CPU and RAM usage values should be visible for each pod to help users monitor resource consumption effectively.

Closed

repo: rdmnl/kubepulse


text:
npm run eject stops when choosin option "React Native: I'd like a regular React Native project."

READ THIS FIRST, PLEASE!
The App Store version of the Expo iOS client recently had to remove the QR code scanner from the app. If you intend to load your app on a physical iOS device, please install the latest version of react-native-scripts to your app (yarn add react-native-scripts@latest or npm install react-native-scripts@latest). It adds the "s" key to the interactive prompt, which asks you to enter an email address or phone number and then sends the URL to your device.
Read more at https://blog.expo.io/upcoming-limitations-to-ios-expo-client-8076d01aee1a. We apologize for any inconvenience this may cause you!
Required format for issues
Please make our job easier by filling this template out to completion. If you're requesting a feature instead of reporting a bug, please feel free to skip the Environment and Reproducible Demo sections.
Description
1-2 sentences describing the problem you're having or the feature you'd like to request
Expected Behavior
What action did you perform, and what did you expect to happen?
Observed Behavior
What actually happened when you performed the above actions?
If there's an error message, please paste the full terminal output and error message in this code block:
Error text goes here!

Environment
Please run these commands in the project folder and fill in their results:

npm ls react-native-scripts:
npm ls react-native:
npm ls expo:
node -v:
npm -v:
yarn --version:
watchman version:

Also specify:

Operating system:
Phone/emulator/simulator & version:

Reproducible Demo
Please provide a minimized reproducible demonstration of the problem you're reporting.
Issues that come with minimal repro's are resolved much more quickly than issues where a maintainer has to reproduce themselves.

After I choose "React Native: I'd like a regular React Native project." in eject contextual menu I just see https://gyazo.com/aadb0faa59c6b4c3e044d62d07cd4334 and I can't write anything in terminal except ctrl+c that exit package execution. I wait for a long time but nothing happens... It just pause.

any process?

Yes,  it seems that there is some bug with Visual Studio Code terminal. I try run command npm run eject from git bash terminal and everything works as it should.

It doesn't work for me eve when I use command line.

authors: Darker lenvonsam tretyakdnua

repo: react-community/create-react-native-app


text:
Not able to set initial state with custom time: "18:10"

I am trying to set initial state in React application with custom date, which I passed from setState.
Its getting blank.
Please help to fix this asap.

I am setting my custom time with moment set attribute.
defaultValue={moment().set('hour', 18).set('minute', 10)}

repo: react-component/time-picker


text:
cropBoxData, initialCropBoxData, setCropBoxData not working

Before creating a bug/issue here please check that it is not part of cropperjs and does not exist in the cropperjs repo.
Describe the bug
Despite reading the documentation for cropperjs in react-cropper ^2.1.8 there seems to be no way to set the crop data upon instantiation: the cropper will always revert to its default view.  The same issue appears in this 9-month-old Stack Overflow question
To Reproduce
Steps to reproduce the behavior:
const { cropData } = props
const [cropper, setCropper] = useState()

...

 <Cropper
          // these are the props I attempt to pass in
          cropBoxData={cropData}
          cropData={cropData}
          initialCropBoxData={cropData}
          cropped={cropData}
          //
          onInitialized={instance => {
            setCropper(instance)
            instance.setCropBoxData(cropData)
          }}
          zoomable={false}
          {...{ autoCropArea, aspectRatio, src }}
        />

when logging cropData it appears as
{
	height: 212.08120117187502,
	left: 46.69999999999999,
	maxHeight: 467,
	maxLeft: 343.2551635742187,
	maxTop: 254.91879882812498,
	maxWidth: 467,
	minHeight: 0,
	minLeft: 0,
	minTop: 0,
	minWidth: 0,
	oldLeft: 46.69999999999999,
	oldTop: 46.69999999999999,
	top: 46.69999999999999,
	width: 123.74483642578127
}

but renders as
{
	height: 467,
	left: 0,
	maxHeight: 467,
	maxLeft: 0,
	maxTop: 0,
	maxWidth: 467,
	minHeight: 0,
	minLeft: 0,
	minTop: 0,
	minWidth: 0,
	oldLeft: 0,
	oldTop: 0,
	top: 0,
	width: 467
}

Expected behavior
I expect that if I crop an image to {top: 0, left: 0, width: 10, height: 10} and pass that in via the cropBoxData prop, that when I create the Cropper component it appears with that crop area, and not at the autoCropArea size
Screenshots
When re-opening the cropper I expect to see this

but instead see this

Desktop (please complete the following information):

OS: MaxOS 13.1 Ventura
Browser: Chrome
Version: 08.0.5359.124

Additional context
Previous versions of react-cropper worked fine, but I need to upgrade from React 16 to React 17 and this is a breaking change.

I'm able to achieve the effect I want with the following:
  useEffect(() => {
    if (cropper && cropData) cropper.setCropBoxData(cropData)
  }, [cropper])

so perhaps the application of the crop box data wasn't firing as expected; still, cropBoxData doesn't appear effective in any way

un-staling - hoping someone else can comment on the issue?

repo: react-cropper/react-cropper


text:
Restore appwrite.json path

I got an error. I realised the error was related to the schematic file path. That's how I fixed it.
Os : Windows
Command : npm run appwrite:restore
Related File : restore.msj
Line : 12
const schema = require(path.join(process.cwd(), "./appwrite.json"));

to
const schema = require(path.join(process.cwd(), "./schema/appwrite.json"));

Why don't you simple copy appwrite.json to the root?

Yes I can do that, but the fetch command places it in this folder
appwrite_fetch.bat
@echo off
if exist .\schema rmdir .\schema /s /q
mkdir .\schema
cd .\schema

authors: SafakB tripolskypetr

repo: react-declarative/appwrite-backup-tool