text:
Switch on apply fixes

Overview
Changes:

Added test for cmip6 decadal.
Use fixes by default.
Uses check_apply_fixes() to check if a fix is available and will be applied.

Updates apply_fixes parameter accordingly and this will be documented in the provenance.

The cmip6 decadal is xfailed because the cmip6 decdal is not in the c3s-cmip6 catalog. Need disable the catalog check in roocs.ini to run the test:
[project:c3s-cmip6]
use_catalog = False

Related Issue / Discussion
Fix #201
Additional Information

should we move apply_fixes into roocs.ini config instead of having it as parameter in the wps process? The  apply_fixes decision is made by rook/daops ... not by the user.

source: gharchive/pull-request

repo: roocs/rook

license_type: permissive

license_source: github-api


text:
🛑 XRAY 🇺🇸 United States USF 1 is down

In 9e0ad71, XRAY 🇺🇸 United States USF 1 (https://usx-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇺🇸 United States USF 1 is back up in 8109d39.

source: gharchive/issue

repo: roosterkid/opentunnel-status-server

license: MIT


text:
🛑 SSH 🇮🇩 Indonesia IDA 1 is down

In 2adbcb8, SSH 🇮🇩 Indonesia IDA 1 (http://ids-2.opensvr.net:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇮🇩 Indonesia IDA 1 is back up in ed8ec80.


text:
🛑 SSH 🇩🇪 Germany DEO 2 is down

In 7c4f003, SSH 🇩🇪 Germany DEO 2 (http://des-2.opensvr.net:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇩🇪 Germany DEO 2 is back up in c6c5dff.


text:
🛑 TROJAN 🇬🇧 United Kingdom UKO 2 is down

In 66453c9, TROJAN 🇬🇧 United Kingdom UKO 2 (https://ukt-2.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇬🇧 United Kingdom UKO 2 is back up in 3ea4906.


text:
🛑 TROJAN 🇮🇩 Indonesia IDJ 1 is down

In 655c005, TROJAN 🇮🇩 Indonesia IDJ 1 (https://idt-1.opensvr.net/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇮🇩 Indonesia IDJ 1 is back up in 26723c3.


text:
🛑 OVPN 🇫🇷 France FRO 1 is down

In 79e73c5, OVPN 🇫🇷 France FRO 1 (http://fro-1.opensvr.net:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: OVPN 🇫🇷 France FRO 1 is back up in 7b4fe6e.


text:
🛑 XRAY 🇩🇪 Germany DEH 1 is down

In 38d1d7f, XRAY 🇩🇪 Germany DEH 1 (https://dex-1.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: XRAY 🇩🇪 Germany DEH 1 is back up in da89516.


text:
🛑 SSH 🇫🇷 France FRO 2 is down

In 284aeef, SSH 🇫🇷 France FRO 2 (http://frs-2.optnl.com:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇫🇷 France FRO 2 is back up in 54e6f3b.


text:
🛑 SSH 🇱🇺 Luxembourg LUF 2 is down

In 61ff99f, SSH 🇱🇺 Luxembourg LUF 2 (http://lus-2.optnl.com:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇱🇺 Luxembourg LUF 2 is back up in 29354f9.


text:
🛑 TROJAN 🇳🇱 Netherlands NLB 1 is down

In 43faaab, TROJAN 🇳🇱 Netherlands NLB 1 (https://nlt-1.optnl.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TROJAN 🇳🇱 Netherlands NLB 1 is back up in c157649.


text:
🛑 SSH 🇷🇺 Russia RUH 1 is down

In 09a0fa2, SSH 🇷🇺 Russia RUH 1 (http://rus-1.optnl.com:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇷🇺 Russia RUH 1 is back up in b432be7.


text:
🛑 V2RAY 🇺🇸 United States USF 3 is down

In b17a07e, V2RAY 🇺🇸 United States USF 3 (https://usv-3.openv2ray.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: V2RAY 🇺🇸 United States USF 3 is back up in dfeb8b0.


text:
🛑 SSH 🇮🇩 Indonesia IDA 1 is down

In d4eeb81, SSH 🇮🇩 Indonesia IDA 1 (http://ids-2.opensvr.net:8080/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SSH 🇮🇩 Indonesia IDA 1 is back up in 3b18963.


text:
Lag when children's props are updated? (websocket in background)

I have a websocket updating props on a regular basis (each 1sec or so). At each update, the drawer motion becomes laggy. The performance impact is very noticeable.
If I cut the websocket connection (and thus the regular props updates), everything becomes (very!) fluid again.
Tested on Android only. The performance drop is especially visible by using a real device.

It sounds like you are asking react to do a lot of work every time you get some new data from the websocket. There are a few things you can do:

add the useInteractionManager prop and then use InteractionManager to pause actions from your websocket.
Debug why the websocket actions are so expensive. Are you using redux? You might try adding your connect's further down that way smaller pieces of the dom need to rerender.

Thanks a lot for your answer @rt2zz. Yeah, that's what I think too. There is room for optimisation because a MapView component is being re-rendered too often (and that seems to be quite heavy). I'll try InteractionManager if I don't manage to optimize.
The weird thing is that when I pan the map, the motion is perfectly fluid even when the app is re-rendered... but when I do the same experiment with the drawer, it lags.
I was expecting to see a "general" drop in framerate caused by the multiple renderings, but so far only the drawer seems to be impacted.

The drawer interaction is heavily JS based, and performance is tricky accordingly. There is room for optimization with Animated api, but that is still a ways off.

@rt2zz: So, I've try to use useInteractionManager={true}. Panning the Drawer indeed stops the state updates (after a little delay, which is weird?), but it seems that the 'toggle' action does not, or at least, not instantaneously, so the animation stutters.

repo: root-two/react-native-drawer

license: mit

license_source: bigquery


text:
Up-Down Drawer instead of Left-Right. It´s possible?

Hello, this is not an issue, it's a query.
There is a way to use this component so the panel appears from the top of the app, instead of right-left sides? (Like the notifications panel of Android). I know this is not the drawer normal behavior.
Thanks!

There is not currently, there is nothing preventing this from being implemented, it would simply require a lot more conditional logic when setting positions.

Any progress on this? This would be awesome

+1

+1

+1


text:
安装k8s1.7的kube-dns报错

环境
centos 7 ,docker ce
版本和配置信息

kubernetes版本：1.7.2

docker版本： 17.03.1-ce

网络插件：calico

存储类型：

操作
按手册安装k8s1.7
dns无法启动
日志
日志或报错信息
kubectl get pod -n kube-system
NAME                                        READY     STATUS             RESTARTS   AGE
calico-node-hdbcp                           2/2       Running            4          8h
calico-node-wpztr                           2/2       Running            4          8h
calico-policy-controller-3271399580-zkwlc   1/1       Running            2          8h
kube-dns-3717118248-7r42p                   1/3       CrashLoopBackOff   42         8h
kube-dns-929211172-0q9m1                    0/3       CrashLoopBackOff   62         8h

[root@master ~]# kubectl describe pod kube-dns-3225369854-3bm8l  -n kube-system
Name:           kube-dns-3225369854-3bm8l
Namespace:      kube-system
Node:           192.168.88.133/192.168.88.133
Start Time:     Tue, 03 Apr 2018 18:06:49 +0800
Labels:         k8s-app=kube-dns
                pod-template-hash=3225369854
Annotations:    kubernetes.io/created-by={"kind":"SerializedReference","apiVersion":"v1","reference":{"kind":"ReplicaSet","namespace":"kube-system","name":"kube-dns-3225369854","uid":"9d621556-3726-11e8-be48-000c29a8...
                scheduler.alpha.kubernetes.io/critical-pod=
Status:         Running
IP:             10.233.219.83
Created By:     ReplicaSet/kube-dns-3225369854
Controlled By:  ReplicaSet/kube-dns-3225369854
Containers:
  kubedns:
    Container ID:       docker://43e3e960cd7c662971bb73708852037b94c4b96da09fcf406328974c1eac8f3d
    Image:              gcr.io/google_containers/k8s-dns-kube-dns-amd64:1.14.5
    Image ID:           docker://sha256:512cd7425a731bee1f2a3e4c825fc1cfe516c8b7905874f24bee6da12801d663
    Ports:              10053/UDP, 10053/TCP, 10055/TCP
    Args:
      --domain=cluster.local.
      --dns-port=10053
      --config-dir=/kube-dns-config
      --v=2
    State:              Running
      Started:          Tue, 03 Apr 2018 19:25:59 +0800
    Last State:         Terminated
      Reason:           Error
      Exit Code:        255
      Started:          Tue, 03 Apr 2018 19:19:57 +0800
      Finished:         Tue, 03 Apr 2018 19:20:57 +0800
    Ready:              False
    Restart Count:      17
    Limits:
      memory:   170Mi
    Requests:
      cpu:      100m
      memory:   70Mi
    Liveness:   http-get http://:10054/healthcheck/kubedns delay=60s timeout=5s period=10s #success=1 #failure=5
    Readiness:  http-get http://:8081/readiness delay=3s timeout=5s period=10s #success=1 #failure=3
    Environment:
      PROMETHEUS_PORT:  10055
    Mounts:
      /kube-dns-config from kube-dns-config (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-dns-token-14rf9 (ro)
  dnsmasq:
    Container ID:       docker://6610470a5ab6d00b9dcae757b3732774f2e3600616e2d11acf819ff0d074f37b
    Image:              gcr.io/google_containers/k8s-dns-dnsmasq-nanny-amd64:1.14.5
    Image ID:           docker://sha256:459944ce8cc4f08ebade5c05bb884e4da053d73e61ec6afe82a0b1687317254c
    Ports:              53/UDP, 53/TCP
    Args:
      -v=2
      -logtostderr
      -configDir=/etc/k8s/dns/dnsmasq-nanny
      -restartDnsmasq=true
      --
      -k
      --cache-size=1000
      --no-negcache
      --log-facility=-
      --server=/cluster.local./127.0.0.1#10053
      --server=/in-addr.arpa/127.0.0.1#10053
      --server=/ip6.arpa/127.0.0.1#10053
    State:              Waiting
      Reason:           CrashLoopBackOff
    Last State:         Terminated
      Reason:           Error
      Exit Code:        137
      Started:          Tue, 03 Apr 2018 19:23:20 +0800
      Finished:         Tue, 03 Apr 2018 19:25:30 +0800
    Ready:              False
    Restart Count:      20
    Requests:
      cpu:              150m
      memory:           20Mi
    Liveness:           http-get http://:10054/healthcheck/dnsmasq delay=60s timeout=5s period=10s #success=1 #failure=5
    Environment:        <none>
    Mounts:
      /etc/k8s/dns/dnsmasq-nanny from kube-dns-config (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-dns-token-14rf9 (ro)
  sidecar:
    Container ID:       docker://6bb619a8c1c3780c7553a7a6ef911d118f007fdbea49990a348c8b490336ac43
    Image:              gcr.io/google_containers/k8s-dns-sidecar-amd64:1.14.5
    Image ID:           docker://sha256:fed89e8b4248a788655d528d96fe644aff012879c782784cd486ff6894ef89f6
    Port:               10054/TCP
    Args:
      --v=2
      --logtostderr
      --probe=kubedns,127.0.0.1:10053,kubernetes.default.svc.cluster.local.,5,A
      --probe=dnsmasq,127.0.0.1:53,kubernetes.default.svc.cluster.local.,5,A
    State:              Running
      Started:          Tue, 03 Apr 2018 18:06:53 +0800
    Ready:              True
    Restart Count:      0
    Requests:
      cpu:              10m
      memory:           20Mi
    Liveness:           http-get http://:10054/metrics delay=60s timeout=5s period=10s #success=1 #failure=5
    Environment:        <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-dns-token-14rf9 (ro)
Conditions:
  Type          Status
  Initialized   True
  Ready         False
  PodScheduled  True
Volumes:
  kube-dns-config:
    Type:       ConfigMap (a volume populated by a ConfigMap)
    Name:       kube-dns
    Optional:   true
  kube-dns-token-14rf9:
    Type:       Secret (a volume populated by a Secret)
    SecretName: kube-dns-token-14rf9
    Optional:   false
QoS Class:      Burstable
Node-Selectors: <none>
Tolerations:    CriticalAddonsOnly
Events:
  FirstSeen     LastSeen        Count   From                    SubObjectPath                   Type            Reason                  Message
  ---------     --------        -----   ----                    -------------                   --------        ------                  -------
  1h            1h              1       default-scheduler                                       Normal          Scheduled               Successfully assigned kube-dns-3225369854-3bm8l to 192.168.88.133
  1h            1h              1       kubelet, 192.168.88.133                                 Normal          SuccessfulMountVolume   MountVolume.SetUp succeeded for volume "kube-dns-config"
  1h            1h              1       kubelet, 192.168.88.133                                 Normal          SuccessfulMountVolume   MountVolume.SetUp succeeded for volume "kube-dns-token-14rf9"
  1h            1h              1       kubelet, 192.168.88.133 spec.containers{sidecar}        Normal          Created                 Created container
  1h            1h              1       kubelet, 192.168.88.133 spec.containers{sidecar}        Normal          Pulled                  Container image "gcr.io/google_containers/k8s-dns-sidecar-amd64:1.14.5" already present on machine
  1h            1h              1       kubelet, 192.168.88.133 spec.containers{sidecar}        Normal          Started                 Started container
  1h            36m             7       kubelet, 192.168.88.133 spec.containers{kubedns}        Warning         Unhealthy               Liveness probe failed: HTTP probe failed with statuscode: 503
  1h            3m              21      kubelet, 192.168.88.133 spec.containers{dnsmasq}        Normal          Pulled                  Container image "gcr.io/google_containers/k8s-dns-dnsmasq-nanny-amd64:1.14.5" already present on machine
  1h            3m              21      kubelet, 192.168.88.133 spec.containers{dnsmasq}        Normal          Created                 Created container
  1h            3m              21      kubelet, 192.168.88.133 spec.containers{dnsmasq}        Normal          Started                 Started container
  1h            1m              85      kubelet, 192.168.88.133 spec.containers{dnsmasq}        Warning         Unhealthy               Liveness probe failed: HTTP probe failed with statuscode: 503
  1h            1m              21      kubelet, 192.168.88.133 spec.containers{dnsmasq}        Normal          Killing                 Killing container with id docker://dnsmasq:pod "kube-dns-3225369854-3bm8l_kube-system(b97de61f-3726-11e8-be48-000c29a825ba)" container "dnsmasq" is unhealthy, it will be killed and re-created.
  1h            47s             283     kubelet, 192.168.88.133 spec.containers{kubedns}        Warning         BackOff                 Back-off restarting failed container
  1h            32s             18      kubelet, 192.168.88.133 spec.containers{kubedns}        Normal          Pulled                  Container image "gcr.io/google_containers/k8s-dns-kube-dns-amd64:1.14.5" already present on machine
  1h            32s             18      kubelet, 192.168.88.133 spec.containers{kubedns}        Normal          Started                 Started container
  1h            32s             18      kubelet, 192.168.88.133 spec.containers{kubedns}        Normal          Created                 Created container
  1h            2s              108     kubelet, 192.168.88.133 spec.containers{kubedns}        Warning         Unhealthy               Readiness probe failed: Get http://10.233.219.83:8081/readiness: dial tcp 10.233.219.83:8081: getsockopt: connection refused
  1h            2s              324     kubelet, 192.168.88.133                                 Warning         FailedSync              Error syncing pod
  1h            2s              182     kubelet, 192.168.88.133 spec.containers{dnsmasq}        Warning         BackOff                 Back-off restarting failed container

[root@master ~]# kubectl logs kube-dns-3225369854-3bm8l  -n kube-system kubedns
I0403 11:25:59.693610     404 dns.go:48] version: 1.14.4-2-g5584e04
I0403 11:25:59.694732     404 server.go:70] Using configuration read from directory: /kube-dns-config with period 10s
I0403 11:25:59.694791     404 server.go:113] FLAG: --alsologtostderr="false"
I0403 11:25:59.694798     404 server.go:113] FLAG: --config-dir="/kube-dns-config"
I0403 11:25:59.694803     404 server.go:113] FLAG: --config-map=""
I0403 11:25:59.694806     404 server.go:113] FLAG: --config-map-namespace="kube-system"
I0403 11:25:59.694810     404 server.go:113] FLAG: --config-period="10s"
I0403 11:25:59.694814     404 server.go:113] FLAG: --dns-bind-address="0.0.0.0"
I0403 11:25:59.694817     404 server.go:113] FLAG: --dns-port="10053"
I0403 11:25:59.694822     404 server.go:113] FLAG: --domain="cluster.local."
I0403 11:25:59.694834     404 server.go:113] FLAG: --federations=""
I0403 11:25:59.694838     404 server.go:113] FLAG: --healthz-port="8081"
I0403 11:25:59.694841     404 server.go:113] FLAG: --initial-sync-timeout="1m0s"
I0403 11:25:59.694844     404 server.go:113] FLAG: --kube-master-url=""
I0403 11:25:59.694848     404 server.go:113] FLAG: --kubecfg-file=""
I0403 11:25:59.694850     404 server.go:113] FLAG: --log-backtrace-at=":0"
I0403 11:25:59.694855     404 server.go:113] FLAG: --log-dir=""
I0403 11:25:59.694858     404 server.go:113] FLAG: --log-flush-frequency="5s"
I0403 11:25:59.694861     404 server.go:113] FLAG: --logtostderr="true"
I0403 11:25:59.694864     404 server.go:113] FLAG: --nameservers=""
I0403 11:25:59.694866     404 server.go:113] FLAG: --stderrthreshold="2"
I0403 11:25:59.694869     404 server.go:113] FLAG: --v="2"
I0403 11:25:59.694872     404 server.go:113] FLAG: --version="false"
I0403 11:25:59.694877     404 server.go:113] FLAG: --vmodule=""
I0403 11:25:59.695182     404 server.go:176] Starting SkyDNS server (0.0.0.0:10053)
I0403 11:25:59.695397     404 server.go:198] Skydns metrics enabled (/metrics:10055)
I0403 11:25:59.695421     404 dns.go:147] Starting endpointsController
I0403 11:25:59.695438     404 dns.go:150] Starting serviceController
I0403 11:25:59.695537     404 logs.go:41] skydns: ready for queries on cluster.local. for tcp://0.0.0.0:10053 [rcache 0]
I0403 11:25:59.695557     404 logs.go:41] skydns: ready for queries on cluster.local. for udp://0.0.0.0:10053 [rcache 0]
E0403 11:25:59.701769     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:25:59.703823     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:00.195827     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:00.696224     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:00.716004     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:00.722910     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:01.195797     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:01.696480     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:01.730452     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:01.733974     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:02.195709     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:02.696031     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:02.749660     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:02.753364     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:03.195746     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:03.695832     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:03.756014     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:03.760140     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:04.195750     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:04.695702     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:04.781707     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:04.782585     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:05.196220     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:05.695898     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:05.788682     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:05.790751     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:06.196234     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:06.695989     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:06.799615     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:06.800614     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:07.195974     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:07.695837     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:07.821825     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:07.822225     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:08.195848     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:08.695953     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:08.827145     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:08.830953     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:09.195782     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:09.695680     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:09.832579     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:09.837539     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:10.196220     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:10.695709     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:10.850052     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:10.856247     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:11.196106     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:11.696174     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:11.862723     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:11.874039     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:12.196176     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:12.695994     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:12.883398     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:12.889365     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:13.196003     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:13.695812     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:13.888907     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:13.898452     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:14.195962     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:14.695746     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:14.904929     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:14.908909     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:15.195788     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:15.696278     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:15.910686     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:15.917868     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:16.195715     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:16.697440     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:16.916675     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:16.923854     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:17.195801     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:17.700308     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:17.928508     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:17.937969     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:18.195718     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:18.695952     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:18.944899     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:18.953167     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:19.195998     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:19.696211     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:19.950978     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:19.959280     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
I0403 11:26:20.195961     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
I0403 11:26:20.695946     404 dns.go:174] Waiting for services and endpoints to be initialized from apiserver...
E0403 11:26:20.962709     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Service: Get https://10.254.0.1:443/api/v1/services?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1
E0403 11:26:20.973488     404 reflector.go:199] k8s.io/dns/vendor/k8s.io/client-go/tools/cache/reflector.go:94: Failed to list *v1.Endpoints: Get https://10.254.0.1:443/api/v1/endpoints?resourceVersion=0: x509: certificate is valid for 127.0.0.1, 192.168.88.133, 192.168.88.134, not 10.254.0.1

已经解决，是因为api-server的认证问题，不在dns上，在api的配置上，证书少了一行。

@tianjiangtao999 请问您是怎么解决的 我这边也出现了这个问题

repo: rootsongjc/kubernetes-handbook


text:
add scp command

This adds support for the scp command similar to ssh, sftp, and ftp, but with a joke relating to the SCP Foundation.

Thank you!

authors: LemmaEOF ledwards

repo: rootvc/cli-website


text:
catch error on vulnerability

a vulnerable dependency (normalize-url for npm) broke the install script, auto trying npm audit fix here to iron it out

@dennisreimann wanna take a look?
General Info: At the moment I am preparing a RC1 for 1.7.1 which target is to test run the c-lightning integration and new setup refactoring. I will go thru the waiting PRs for v1.7.1 after that testrun and have them in later Release Candidates. This can still take some days .. because there is much going on at the moment.

I don't think this is the right way to solve this issue and it should rather be fixed by providing a valid dependency tree in the package itself. However, npm audit does not report a vulnerability for the current stacking-sats-kraken version for me.

it did for me when I setup a new pi 4 with v1.7 though, so I figured as npm dependecies could break any time this may help for future stuff and keep the install script not breaking. fixing the tree needs to be done each time again.
redproducing on the fresh pi:

./config.scripts/bonus.stacking-sats-kraken.sh off
./config.scripts/bonus.stacking-sats-kraken.sh on

found 1 high severity vulnerability
run npm audit fix to fix them, or npm audit for details

$ npm audit

                       === npm audit security report ===

# Run  npm update normalize-url --depth 4  to resolve 1 vulnerability
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ High          │ Regular Expression Denial of Service                         │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ normalize-url                                                │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ kraken-api                                                   │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ kraken-api > got > cacheable-request > normalize-url         │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://npmjs.com/advisories/1755                            │
└───────────────┴──────────────────────────────────────────────────────────────┘

found 1 high severity vulnerability in 32 scanned packages
  run `npm audit fix` to fix 1 of them.

this gives error code 1… next time could be another package of the tree and still be fixed.

IMO the correct way to handle it would be to turn the audit of with the --no-audit flag, i.e. npm install --no-audit.
If you look at the advisory, the vulnerability would be a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.
Neither stacking-sats-kraken nor kraken-api make use of data: URLs though, so I don't think that is an issue.

Here's a PR with an updated version:  #2483

With PR #2483 merged ... is this PR still relevant?

It can be closed.

authors: cstenglein dennisreimann rootzoll vv01f

repo: rootzoll/raspiblitz


text:
potential offset param problem on /list/country route

res <- cli$get("list/country", query = list(country = "Canada", limit=1000))

everything is fine, but I get an error when I try adjusting the offset:
res <- cli$get("list/country", query = list(country = "Canada", offset=10))

The error is a 400, and the message is:
 "PG::InvalidColumnReference: ERROR:  for SELECT DISTINCT, ORDER BY expressions must appear in select list\nLINE 4:             AND is_new_world = 1) ORDER BY scrubbed_species_...\n                                                   ^\n: SELECT COUNT(DISTINCT count_column) FROM (SELECT DISTINCT 1 AS count_column FROM \"species_by_political_division\" WHERE (country in ('Canada')\n            AND scrubbed_species_binomial IS NOT NULL\n            AND (is_cultivated = 0 OR is_cultivated IS NULL)\n            AND is_new_world = 1) ORDER BY scrubbed_species_binomial OFFSET $1) subquery_for_count"

not sure whats going on here, investigated, but not sure what problem is yet

repo: ropensci/bienapi


text:
Rename extrication paths

I'm pretty sure "extrication paths" does not mean anything.
@shaun-edwards How would you call a trajectory that is not machining when you just want to move the tool from one point to another.
This corresponds to the red trajectory on the image:

The green trajectories are removing material from the object.
The red trajectories are just moving the robot between green trajectories.
Is there a specific/technical term for that?

@gavanderhoorn An idea?

No, not immediately. I've heard ppl refer to them as non-toolpath motion, or freespace motion, but I'm pretty sure that that isn't official terminology.

Btw

I'm pretty sure "extrication paths" does not mean anything.

that's not entirely true: see wikipedia/Vehicle extrication fi.
The term is also used to describe motions that a robot uses to get out of a certain situation, fi in rescue robotics (here fi).

I don't have time for a renaming.

authors: VictorLamoine gavanderhoorn

repo: ros-industrial-consortium/bezier


text:
Installing error for clearpath-platform

Hi,
I have an issue to building clearpath-platform.
| install: cannot stat '/home/bchoi/nvidia-yocto-bsp/bchoi-build/tmp/work/armv8a-oe4t-linux/clearpath-platform/0.2.7-1-r0/build/liblighting_lib.so': No such file or directory
| WARNING: exit code 1 from a shell command.
ERROR: Task (/home/bchoi/nvidia-yocto-bsp/sources/meta-ros/meta-ros2-humble/generated-recipes/clearpath-common/clearpath-platform_0.2.7-1.bb:do_install) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4118 tasks of which 4117 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /home/bchoi/nvidia-yocto-bsp/sources/meta-ros/meta-ros2-humble/generated-recipes/clearpath-common/clearpath-platform_0.2.7-1.bb:do_install
Summary: There was 1 ERROR message, returning a non-zero exit code.

it is because of bbappend file on the meta-ros2-humble/recipes-bbappends/clearpath-common/clearpath-platform_0.2.7-1.bbappend which try to install liblighting_lib.so.
   do_install:append() {
       install -d ${D}${libdir}
       install -D -m 0644 ${B}/liblighting_lib.so ${D}/${libdir}
   }

By the way, I think lighting_node do not link it any more in the CMakeLists.txt
 34 # Lighting
 35 set(LIGHTING_EXECUTABLE lighting_node)
 36 set(LIGHTING_LIB clearpath_platform_lighting)
 37 set(LIGHTING_DEPENDENCIES
 38     clearpath_platform_msgs
 39     sensor_msgs
 40     rclcpp
 41 )
 42
 43 add_library(
 44   ${LIGHTING_LIB}
 45   SHARED
 46   src/lighting/lighting.cpp
 47   src/lighting/sequence.cpp
 48   src/lighting/color.cpp
 49 )
 50
 51 ament_target_dependencies(${LIGHTING_LIB} ${LIGHTING_DEPENDENCIES})
 52
 53 target_include_directories(
 54   ${LIGHTING_LIB}
 55   PRIVATE
 56   include
 57 )
 58
 59 add_executable(${LIGHTING_EXECUTABLE} src/lighting/main.cpp)
 60 target_link_libraries(${LIGHTING_EXECUTABLE} ${LIGHTING_LIB})

So, I think we do not need to bbappend file to install manually for lighting_node.
Can you please check it?
BR,
Mark

Thanks for reporting this, Mark.  I see you are using Humble, which Yocto release are you using?

Yes I am using humble now.  the commit id is 9a857afebc18e0f426d87226bd085727ea9ce4ae .

authors: bchoineubility robwoolley

repo: ros/meta-ros


text:
kirkstone: ros2 humble: canopen-interfaces_0.2.11-2: problems when populating sdk

Hi there,
I've managed to create a patch that integrates ROS2 humble into the SDK, and am now trying to compile canopen-core as part of the libraries on the target. I am running into issues with canopen-interfaces and get the following build error:
| -- Found rosidl_default_generators: 1.2.0 (build/tmp/work/armv8a-linux/canopen-interfaces/0.2.11-2-r0/recipe-sysroot/usr/share/rosidl_default_generators/cmake)
| CMake Error at build/tmp/work/armv8a-linux/canopen-interfaces/0.2.11-2-r0/recipe-sysroot/usr/share/rosidl_default_generators/cmake/ament_cmake_export_dependencies-extras.cmake:21 (find_package):
|   By not providing "Findrosidl_cmake.cmake" in CMAKE_MODULE_PATH this project
|   has asked CMake to find a package configuration file provided by
|   "rosidl_cmake", but CMake did not find one.
|
|   Could not find a package configuration file provided by "rosidl_cmake" with
|   any of the following names:
|
|     rosidl_cmakeConfig.cmake
|     rosidl_cmake-config.cmake
|
|   Add the installation prefix of "rosidl_cmake" to CMAKE_PREFIX_PATH or set
|   "rosidl_cmake_DIR" to a directory containing one of the above files.  If
|   "rosidl_cmake" provides a separate development package or SDK, be sure it
|   has been installed.

It seems like adding rosidl-cmake as a build dependency would resolve this error, but it does not, and I end up getting an error downstream where the .srv files are not build properly and cannot be found by canopen-core. I am a bit stuck on what to try next - the .bbappend file applied to the canopen-interfaces recipe for ROS2 Rolling did not resolve the problem, either, and gives me a wall of error text, including the following:
| FAILED: libcanopen_interfaces__rosidl_generator_c.so
Has anyone encountered similar problems with ros2-canopen?

Thanks Mark, this worked for me! I greatly appreciate your help.


text:
laser_geometry: 1.6.4-0 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository laser_geometry to 1.6.4-0:

upstream repository: https://github.com/ros-perception/laser_geometry.git
release repository: https://github.com/ros-gbp/laser_geometry-release.git
distro file: melodic/distribution.yaml
bloom version: 0.6.4
previous version for package: null

laser_geometry
* Fix segfault when laserscan ranges[] is empty
* Contributors: Timm Linder, Vincent Rabaud

💩

repo: ros/rosdistro


text:
add rule for python3-lxml for mac os

@mjcarroll based on https://github.com/ros2/ros2/issues/656#issuecomment-472614723 it looks like this definition will be needed for users using rosdep on MacOS. Is that right ?

With macOS: The dependency should be resolved either with rosdep [...]

lgtm, though will it be python3 by default?

Yeah I had the same concern but saw that matplotlib below had a pip entry so assumed it worked in some cases.
I don't have any macOS machine available to try it on.
Looking at the wheels available it looks like there are separate binaries for python2 and 3, so it will likely be python2 :/

I'll assume that this will actually be the Python 2 version and close this PR.


text:
catkin_virtualenv: 0.5.1-1 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository catkin_virtualenv to 0.5.1-1:

upstream repository: https://github.com/locusrobotics/catkin_virtualenv.git
release repository: https://github.com/locusrobotics/catkin_virtualenv-release.git
distro file: melodic/distribution.yaml
bloom version: 0.8.0
previous version for package: 0.4.1-1

catkin_virtualenv
* catkin-pkg-modules has disappeared off pypi (#46 <https://github.com/locusrobotics/catkin_virtualenv/issues/46>)
  * catkin-pkg-modules has disappeared off pypi, but catkin-pkg is still there
  * Version all requirements
* Contributors: Paul Bovbel

This failed CI because the source and doc entries are both pointing at a devel branch which no longer seems to exist.  @paulbovbel is that on purpose?  If so, you should probably update the source and doc entries in a separate PR first, then we can re-kick this one.

All right, this one can be rebased now that #22262 has been merged.

@paulbovbel: would Kinetic need a new release as well?

authors: clalancette gavanderhoorn paulbovbel


text:
rosidl_runtime_py: 0.9.1-3 in 'rolling/distribution.yaml' [bloom]

Increasing version of package(s) in repository rosidl_runtime_py to 0.9.1-3:

upstream repository: https://github.com/ros2/rosidl_runtime_py.git
release repository: https://github.com/ros2-gbp/rosidl_runtime_py-release.git
distro file: rolling/distribution.yaml
bloom version: 0.10.7
previous version for package: 0.9.1-2

rosidl_runtime_py
* Add pytest.ini so local tests don't display warning (#12 <https://github.com/ros2/rosidl_runtime_py/issues/12>)
* Contributors: Chris Lalancette

@audrow did you intentionally only increased the debinc number?

authors: audrow ivanpauno


text:
plotjuggler: 3.5.1-3 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository plotjuggler to 3.5.1-3:

upstream repository: https://github.com/facontidavide/PlotJuggler.git
release repository: https://github.com/facontidavide/plotjuggler-release.git
distro file: noetic/distribution.yaml
bloom version: 0.11.1
previous version for package: 3.5.0-1

plotjuggler
* Dev/ros1 ros2 snap (#698 <https://github.com/facontidavide/PlotJuggler/issues/698>)
* update nlohmann json to fix #640 <https://github.com/facontidavide/PlotJuggler/issues/640>
* should prevent error #696 <https://github.com/facontidavide/PlotJuggler/issues/696>
* Merge branch 'improved_zoomout' into main
* cleanup after #702 <https://github.com/facontidavide/PlotJuggler/issues/702>
* Statistics dialog improvements and bug fixes (#702 <https://github.com/facontidavide/PlotJuggler/issues/702>)
* Include std::thread instead of QThread, since it is being utilized in the mqtt plugin instead of QThread. (#700 <https://github.com/facontidavide/PlotJuggler/issues/700>)
* fix zmq compilation
* cherry picking from #698 <https://github.com/facontidavide/PlotJuggler/issues/698>
* increase playback step precision (#692 <https://github.com/facontidavide/PlotJuggler/issues/692>)
* Fix typo in ColorMap warning (#693 <https://github.com/facontidavide/PlotJuggler/issues/693>)
* Set buttonBackground icon in .ui file (#694 <https://github.com/facontidavide/PlotJuggler/issues/694>)
* Update README.md
* Fix #697 <https://github.com/facontidavide/PlotJuggler/issues/697>
* update sol2 and fix #687 <https://github.com/facontidavide/PlotJuggler/issues/687>
* try to improve the linked zoomout
* Contributors: Bartimaeus-, Davide Faconti, Guillaume Beuzeboc, Hugal31, ozzdemir

Holding for Noetic sync

authors: cottsay facontidavide


text:
cras_ros_utils: 2.0.10-2 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository cras_ros_utils to 2.0.10-2:

upstream repository: https://github.com/ctu-vras/ros-utils
release repository: https://gitlab.fel.cvut.cz/cras/ros-release/ros-utils.git
distro file: noetic/distribution.yaml
bloom version: 0.11.2
previous version for package: 2.0.5-1

cras_cpp_common

No changes

cras_py_common
* Fix test bug.
* Contributors: Martin Pecka

cras_topic_tools

No changes

This pull request has been mentioned on ROS Discourse. There might be relevant details there:
https://discourse.ros.org/t/preparing-for-noetic-sync-2022-11-30/28556/2

Holding for Noetic sync


text:
jacro: 0.2.0-1 in 'jazzy/distribution.yaml' [bloom]

Increasing version of package(s) in repository jacro to 0.2.0-1:

upstream repository: https://github.com/JafarAbdi/jacro.git
release repository: https://github.com/JafarAbdi/jacro-release.git
distro file: jazzy/distribution.yaml
bloom version: 0.12.0
previous version for package: null

jacro
* Replace minijinja with jinja2
* Contributors: JafarAbdi

See https://github.com/ros/rosdistro/pull/43494#pullrequestreview-2443488069 ; while you don't have to house the jazzy release and the rolling release in the same release repository, it is probably a good idea to do so.

Replaced by https://github.com/ros/rosdistro/pull/43992

authors: JafarAbdi clalancette


text:
Run relevant test_tracetools tests with all instrumented rmw impls

Fixes #131
This is equivalent similar to #116 but for Jazzy.
See explanation in #132. For Jazzy, rmw_connextdds is supported (compared to Iron), but rmw_fastrtps_dynamic_cpp is not (compared to Rolling).

I don't think we have a manual version of the Jci__nightly-fastrtps-dynamic_ubuntu_noble_amd64 job, so I'll just run manual CI:

Linux
Linux-aarch64
Linux-rhel
Windows

I did test locally by setting RMW_IMPLEMENTATIONS=rmw_fastrtps_dynamic_cpp when running colcon build and the tests were skipped.

I think the failure in test_pub_sub__rmw_connextdds on RHEL is a flake and should be resolved by backporting #125 to Jazzy.

I think the failure in test_pub_sub__rmw_connextdds on RHEL is a flake and should be resolved by backporting #125 to Jazzy: #135.

Done. I rebased this. Re-running CI just to be sure:

Linux
Linux-aarch64
Linux-rhel
Windows

@clalancette @fujitatomoya can one of you review this?


text:
Moxy cannot handle synthetic accessor methods

Describe the bug
When encountering a synthetic accessor method (for example on an inner class) Moxy throws an NPE.
To Reproduce
package com.roscopeco.moxy.regression;

import com.roscopeco.moxy.Moxy;
import org.junit.jupiter.api.Test;

import static org.assertj.core.api.Assertions.assertThat;

class TestRegressionMoxy11 {
    public static class ClassWithNested {
        public static class Inner {
            private int theField;
        }

        public Inner test() {
            Inner inner = new Inner();
            inner.theField = 5;
            return inner;
        }

    }

    @Test
    void testMoxyBug11() {
        ClassWithNested.Inner inner = Moxy.mock(ClassWithNested.Inner.class);   /* NPE Here */
        assertThat(inner).isNotNull();
    }
}

Expected behavior
The synthetic method should be ignored (i.e. not mocked).
Stacktraces
com.roscopeco.moxy.api.MockGenerationException: Unrecoverable error: exception during mock generation

	at com.roscopeco.moxy.impl.asm.ASMMoxyEngine.mock(ASMMoxyEngine.java:189)
	at com.roscopeco.moxy.Moxy.mock(Moxy.java:430)
	at com.roscopeco.moxy.Moxy.mock(Moxy.java:387)
	at com.roscopeco.moxy.Moxy.mock(Moxy.java:353)
	at com.roscopeco.moxy.regression.TestRegressionMoxy11.testMoxyBug11(TestRegressionMoxy11.java:24)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:436)
	at org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:115)
	at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$6(TestMethodTestDescriptor.java:170)
	at org.junit.jupiter.engine.execution.ThrowableCollector.execute(ThrowableCollector.java:40)
	at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:166)
	at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:113)
	at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:58)
	at org.junit.platform.engine.support.hierarchical.HierarchicalTestExecutor$NodeExecutor.lambda$executeRecursively$3(HierarchicalTestExecutor.java:112)
	at org.junit.platform.engine.support.hierarchical.SingleTestExecutor.executeSafely(SingleTestExecutor.java:66)
	at org.junit.platform.engine.support.hierarchical.HierarchicalTestExecutor$NodeExecutor.executeRecursively(HierarchicalTestExecutor.java:108)
	at org.junit.platform.engine.support.hierarchical.HierarchicalTestExecutor$NodeExecutor.execute(HierarchicalTestExecutor.java:79)
	at org.junit.platform.engine.support.hierarchical.HierarchicalTestExecutor$NodeExecutor.lambda$executeRecursively$2(HierarchicalTestExecutor.java:120)
	at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
	at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
	at java.util.Iterator.forEachRemaining(Iterator.java:116)
	at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
	at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
	at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
	at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
	at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
	at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
	at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
	at org.junit.platform.engine.support.hierarchical.HierarchicalTestExecutor$NodeExecutor.lambda$executeRecursively$3(HierarchicalTestExecutor.java:120)
	at org.junit.platform.engine.support.hierarchical.SingleTestExecutor.executeSafely(SingleTestExecutor.java:66)
	at org.junit.platform.engine.support.hierarchical.HierarchicalTestExecutor$NodeExecutor.executeRecursively(HierarchicalTestExecutor.java:108)
	at org.junit.platform.engine.support.hierarchical.HierarchicalTestExecutor$NodeExecutor.execute(HierarchicalTestExecutor.java:79)
	at org.junit.platform.engine.support.hierarchical.HierarchicalTestExecutor$NodeExecutor.lambda$executeRecursively$2(HierarchicalTestExecutor.java:120)
	at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
	at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
	at java.util.Iterator.forEachRemaining(Iterator.java:116)
	at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
	at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
	at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
	at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
	at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
	at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
	at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
	at org.junit.platform.engine.support.hierarchical.HierarchicalTestExecutor$NodeExecutor.lambda$executeRecursively$3(HierarchicalTestExecutor.java:120)
	at org.junit.platform.engine.support.hierarchical.SingleTestExecutor.executeSafely(SingleTestExecutor.java:66)
	at org.junit.platform.engine.support.hierarchical.HierarchicalTestExecutor$NodeExecutor.executeRecursively(HierarchicalTestExecutor.java:108)
	at org.junit.platform.engine.support.hierarchical.HierarchicalTestExecutor$NodeExecutor.execute(HierarchicalTestExecutor.java:79)
	at org.junit.platform.engine.support.hierarchical.HierarchicalTestExecutor.execute(HierarchicalTestExecutor.java:55)
	at org.junit.platform.engine.support.hierarchical.HierarchicalTestEngine.execute(HierarchicalTestEngine.java:43)
	at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:170)
	at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:154)
	at org.junit.platform.launcher.core.DefaultLauncher.execute(DefaultLauncher.java:90)
	at com.intellij.junit5.JUnit5IdeaTestRunner.startRunnerWithArgs(JUnit5IdeaTestRunner.java:74)
	at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
	at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
	at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)
Caused by: java.lang.NullPointerException
	at com.roscopeco.moxy.impl.asm.visitors.MoxyMockClassVisitor.visitEnd(MoxyMockClassVisitor.java:138)
	at org.objectweb.asm.ClassReader.accept(ClassReader.java:683)
	at org.objectweb.asm.ClassReader.accept(ClassReader.java:391)
	at com.roscopeco.moxy.impl.asm.ASMMoxyEngine.createMockClassNode(ASMMoxyEngine.java:537)
	at com.roscopeco.moxy.impl.asm.ASMMoxyEngine.getMockClass(ASMMoxyEngine.java:203)
	at com.roscopeco.moxy.impl.asm.ASMMoxyEngine.getMockClass(ASMMoxyEngine.java:242)
	at com.roscopeco.moxy.impl.asm.ASMMoxyEngine.mock(ASMMoxyEngine.java:184)
	... 58 more

Environment (please complete the following information):

Moxy version 0.92
OS: Any
JVM Vendor: Any
JVM Version: 1.8

Additional context
Fixable by making mv.visitCode() and mv.visitEnd() conditional on non-null return from visitMethod in MoxyMockClassVisitor#visitEnd.

Fixed in develop, for patch release 0.92.1

repo: roscopeco/moxy


text:
Add --profile option to commands

supersedes https://github.com/rossumai/elisctl/pull/53

closes https://github.com/rossumai/elisctl/issues/50

repo: rossumai/elisctl


text:
parse unexpected panics

Hey :wave:
When a test panics (not due to an assertion failure - in my case due to an unwrap on Err), neotest-rust can't parse the output.
So I added another attempt at parsing in case message == nil. It's a bit hacky, but seems to work, at least in my case. :sweat_smile:
I've added a spec in which I copied the test output of my test case that was failing.
Unfortunately, I can't run make test locally, because I'm on NixOS and it tries to install the tree-sitter parser to the nix store.

Reverting this because I believe it was actually fixed by #64!


text:
Multiline for paragraphs?

Hi there,
Trying multiline annotations, when the target element is a <span> everything works as expected, but when I apply it to a <p> element the full block is highlighted, multiline highlight isn't shown, is this the intended behavior? only inline elements can be multiline highlighted? I think it would be nice to annotate in multiline all text inside a <p>, so this is a feature request :)
Thank for the cool piece of software, it's nice rough-stuff.

Hum... Just found https://github.com/rough-stuff/rough-notation/issues/9#issuecomment-635865172, so, I suppose this is my answer, sorry for not looking at it before submitting, shame on me ;)

repo: rough-stuff/rough-notation


text:
Using the BottomBar hides buttons on main layout?

Hi,
Great library, the BottomBar is awesome! I do have one issue that I can't seem to get around.
I have a layout which has a swipeable card, below it two buttons, and below that the BottomBar. Very similar to Tinder's layout. However, when I use the BottomBar, the two buttons are not displayed, any ideas why?
Here is the code in my activity onCreate():
setContentView(R.layout.activity_main);
ButterKnife.inject(this);

mBottomBar = BottomBar.attach(MainActivity.this, savedInstanceState);
        mBottomBar.setItems(R.menu.bottombar_menu);

        mBottomBar.setOnMenuTabClickListener(new OnMenuTabClickListener() {
            @Override
            public void onMenuTabSelected(@IdRes int menuItemId) {
                if (menuItemId == R.id.toolbar_jobs) {

                } else if (menuItemId == R.id.toolbar_messages) {

                } else if (menuItemId == R.id.toolbar_recentJobs) {

                } else if (menuItemId == R.id.toolbar_employerPools) {

                }
            }

            @Override
            public void onMenuTabReSelected(@IdRes int menuItemId) {
                if (menuItemId == R.id.toolbar_jobs) {
                    // The user reselected item number one, scroll your content to top.
                } else if (menuItemId == R.id.toolbar_messages) {

                } else if (menuItemId == R.id.toolbar_employerPools) {

                } else if (menuItemId == R.id.toolbar_recentJobs) {

                }
            }
        });

        // Setting colors for different tabs when there's more than three of them.
        // You can set colors for tabs in three different ways as shown below.
        mBottomBar.getBar().setBackgroundColor(getResources().getColor(R.color.laborswipe_darkgray));
        mBottomBar.setActiveTabColor(getResources().getColor(R.color.laborswipe_lightgray));

        // Make a Badge for the second tab, with red background color and a value of "13".
        BottomBarBadge unreadMessages = mBottomBar.makeBadgeForTabAt(1, getResources().getColor(R.color.laborswipe_orange), 5);

        // Control the badge's visibility
        unreadMessages.show();
        //unreadMessages.hide();

        // Change the displayed count for this badge.
        //unreadMessages.setCount(4);

        // Change the show / hide animation duration.
        unreadMessages.setAnimationDuration(200);

        // If you want the badge be shown always after unselecting the tab that contains it.
        unreadMessages.setAutoShowAfterUnSelection(true);

        // If you don't want this badge to be hidden after selecting the tab contains it.
        unreadMessages.setAutoShowAfterUnSelection(false);

My activity_main looks like this:
<merge
    xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    xmlns:tools="http://schemas.android.com/tools">

    <com.lorentzos.flingswipe.SwipeFlingAdapterView
        android:id="@+id/frame"
        android:background="@color/laborswipe_lightgray"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        tools:context=".MainActivity"
        android:layout_gravity="top"   />

    <LinearLayout
        android:id="@+id/actions"
        android:layout_width="wrap_content"
        android:layout_height="wrap_content"
        android:layout_gravity="center_horizontal|center"
        android:layout_marginTop="10dp"
        android:layout_marginBottom="20dp"
        tools:context=".MainActivity">

        <Button
            android:layout_height="wrap_content"
            android:layout_width="wrap_content"
            android:id="@+id/btn_dismiss"
            android:layout_margin="10dp"
            android:text="DISMISS"
            android:textColor="@color/laborswipe_darkgray"
            android:background="?android:attr/selectableItemBackground"
            android:drawableTop="@drawable/ic_leftarrow" />

        <Button
            android:layout_height="wrap_content"
            android:layout_width="wrap_content"
            android:id="@+id/btn_apply"
            android:layout_margin="10dp"
            android:text="APPLY"
            android:textColor="@color/laborswipe_darkgray"
            android:drawableTop="@drawable/ic_rightarrow"
            android:background="?android:attr/selectableItemBackground"/>
    </LinearLayout>

</merge>

What am I missing? I tried playing around with the attach() method and attaching to the layout of the buttons but that still did not work....any help is much appreciated! Thanks!

Anyone? I still can't resolve this :(

repo: roughike/BottomBar


text:
:package: meshio

Hello. I think using meshio is makes this script more simple. I did a test here.  You can also read various file format of mesh from this package in the same way. Thank you very much for reading and good luck for your great project.

Oh nice ! I did not know that package.


text:
WebAudio backend doesn't stream audio, but downloads entire piece, decodes entire piece and only then starts playing [infamous audio lag problem]

If you check js/rpg_core/WebAudio.js, you'll find this function which is called every time a sound is created & triggered for playback (including new music pieces):
WebAudio.prototype.initialize = function(url) {
    if (!WebAudio._initialized) {
        WebAudio.initialize();
    }
    this.clear();
    this._load(url);
    this._url = url;
};

You can see it calls _load, which triggers an Ajax request:
WebAudio.prototype._load = function(url) {
    if (WebAudio._context) {
        var xhr = new XMLHttpRequest();
        if(Decrypter.hasEncryptedAudio) url = Decrypter.extToEncryptExt(url);
        xhr.open('GET', url);
....

In the receive callback of the Ajax request, _onXhrLoad simply decodes the received audio after the Ajax request completed in its entirety (full download required first):
WebAudio.prototype._onXhrLoad = function(xhr) {
    var array = xhr.response;
    if(Decrypter.hasEncryptedAudio) array = Decrypter.decryptArrayBuffer(array);
    this._readLoopComments(new Uint8Array(array));
   WebAudio._context.decodeAudioData(array, function(buffer) {
...

.. and only after that, WebAudio.prototype._onLoad is called which finally informs all load listeners.
As you can see in the play function, the load listeners are used to start playing the actual sound, so before reaching this stage no audio can be heard:
WebAudio.prototype.play = function(loop, offset) {
    if (this.isReady()) {
        offset = offset || 0;
        this._startPlaying(loop, offset);
    } else if (WebAudio._context) {
        this._autoPlay = true;
        this.addLoadListener(function() {
            if (this._autoPlay) {
                this.play(loop, offset);
            }
        }.bind(this));
    }
};

In conclusion, this means any sound or music piece is first download as a whole, then decoded as a whole and only then it starts playing. This process can take many actual seconds, I observed delays up to 6-7 seconds for a song to start playing even in a local(!) game where no download and only decoding is required. In HTML5-delivered web games, the problem is obviously potentially a lot worse.
This is the infamous audio lag problem that plagues RPG Maker MV for all things audio. Therefore, as a conclusion this code really should be changed so that:

decoding starts before the download is completed
playback starts before decoding is completed

Then, all audio lag problems with sounds and music should be solved, except for cases with a really sluggy internet connection in HTML5 games. Those can only ever work nicely if everything is preloaded completely, which is by the way also what this plugin workaround hack does: https://forums.rpgmakerweb.com/index.php?threads/webaudio-cache-experimental.51422/ but obviously this is bad for regular desktop games since it will need more memory and increase loading time by a lot, so this isn't a good solution.

WebAudio is also the default audio backend for anything but sometimes mobile I think, so this affects all desktop RPG Maker MV games (which is I would argue the most important release platform). I don't know how the Html5Audio backend fares in comparison, so this would need a separate investigation.

We know about the problem.(see road map)
And We found the problem is hard to solve in current browser feature.
If you have idea for implement streaming, please PR.
BTW, I don't know why the original script doesn't use MediaElementAudioSourceNode.
does anyone know that?

I asked original author why it doesn't.

The answer returns.
The API is not usable when development starts.
But for now, It may be usable (needs investigation)
So we consider about using the API.

authors: JonasT liply

repo: rpgtkoolmv/corescript


text:
🛑 Evon Ceramics is down

In cfef1ff, Evon Ceramics (http://evonceramics.com/) was down:

HTTP code: 502
Response time: 545 ms

Resolved: Evon Ceramics is back up in 2348c22.

repo: rpharaniya/websites-uptime-monitor


text:
🛑 Umiya Agro Solvex is down

In 0675a30, Umiya Agro Solvex (https://umiyaagrosolvex.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Umiya Agro Solvex is back up in 03c7c0a after 5 minutes.


text:
Compiling on RPI4 using ws2811_sim.go

As stated, when compiling on a RPI4 it is using ws2811_sim.go.
I attempted to fix this by forking and changing the build constraints to be:

ws2811_arm.go to // +build arm arm64
ws2811_sim.go to // +build !arm,!arm64

After trying quite a few combinations of build constraints it is still falling into using sim.
My understanding of build constraints is limited, so I'm sure there is something simple I am overlooking.
I have verified that it is a build constraint, and not my failure to install the C library by combining all of the necessary code into ws2811.go and my code controls my neopixel array as expected.
go env:
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/home/sonnen/.cache/go-build"
GOENV="/home/sonnen/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/sonnen/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go-1.14"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go-1.14/pkg/tool/linux_arm64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/sonnen/projects/lights/lights_go/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build382712525=/tmp/go-build -gno-record-gcc-switches"

Thank you for your feedback. I haven't implemented the code for the ARM64 architecture yet because, until now, nobody seemed to need it. But with your issue, I will look into the matter.

Hey no problem. Thank you for the quick response. If there is any way I can help troubleshoot, or documentation you could point me to I could try to implement it and submit a PR.
I'm not sure why changing the build flags wasn't working. Is it something to do with the file name as well?

I don't think that the file names are relevant and what you did seems OK to me. I have to make some experiments. Are you compiling on the RPi 4 directly or are you cross-compiling ? And what OS/version do you have on the RPi 4 (Ubuntu, Pi OS) ?

Actually the file name might be relevant :
https://golang.org/cmd/go/#hdr-Build_constraints
----- BEGIN CITATION -----
If a file's name, after stripping the extension and a possible _test suffix, matches any of the following patterns:
*_GOOS
*_GOARCH
*_GOOS_GOARCH

(example: source_windows_amd64.go) where GOOS and GOARCH represent any known operating system and architecture values respectively, then the file is considered to have an implicit build constraint requiring those terms (in addition to any explicit constraints in the file).
----- END CITATION -----

So you can try to rename ws2811_arm.go to ws2811_hw.go (for Hardware)

Looks like the file name was the missing piece. I caught that in the docs after struggling all night trying to get it to work.

Thank you @onnenon. I just merged your PR in the master branch. Please, let me know if I need to do something else. If you are happy with the solution, could you please leave a comment and close this issue ? Thank you in advance.

Hey thank you. PR #14 resolves this. I'll go ahead and close it.

Hi @supcik! Just learning go and spent more time then I should have figuring out why I could not get a hello world app to run natively on a Raspberry pi 4. Turns out go mod is pulling v1.0.6 and I was reading master :)
Could you publish v1.0.7 when you have a chance?

Thank you @finack for your message. I just published the tag v1.0.7. Could you please let me know if you can now use the module without @master ?

Hi @supcik! got get pulled down the latest, v1.0.8! Thanks for the update!

👍🏼

authors: finack onnenon supcik


text:
loading .D64 files?

Hello,
I've installed ESP32TinyC64 on my TTGO VGA, it works fine, but is it possible to load .d64 files into it, from the SD card reader? I don't find this mentioned in the doc...

The project is realised for a basic ESP32, i.e. a TTGO VGA32 v1.2, which lacks PSRAM and SD module.
The C64 disk controller emulation is basic, as simple as the Toy C64 emulator it is based on. It is so basic that it wouldn't even make sense to include it, but still, it has been included in the project. Since the Toy C64 also lacks many options, worrying about whether you have .D64 support from SD is illogical, since 90% of the software will not work properly, even if you run it from FLASH.
If you take a closer look at the Toy C64, you will understand what I am talking about:
https://github.com/zhmu/toy-c64emu

license: WTFPL


text:
(just trying to get CI to run again)

I can't reproduce the fails locally!

ahhh it passed!?

repo: rrbutani/bazel-toolchain


text:
Some improvements

Refactoring Web project.
Adding search on enter key down.

@nramirez you should add yourself to the AUTHORS file

authors: nramirez rroa

repo: rroa/marvel-csharp


text:
APP-643 HC: Check minimum versions for Agent, Key Manager and POD

Support for check minimum versions for Agent, Key Manager and POD

LGTM. @dnsymphony could you review please?

@dnsymphony I'm closing this PR because the code is included on the PR #5

authors: cmarcondes-daitan rsanchez-daitan


text:
Inventory system

Flexible inventory system

@WhiteKing78 to create the art for the invetory system

repo: rsaz/mankind


text:
Experiment with various tips for speeding up plotting

https://matplotlib.org/api/animation_api.html#funcanimation
https://github.com/pyqtgraph/pyqtgraph
https://stackoverflow.com/questions/40126176/fast-live-plotting-in-matplotlib-pyplot

Closing for now in favor of adaptive plotting rates

repo: rsokl/liveplot


text:
Consider providing register_listener as a public API on Configuration

I'm trying to write a helper for some rspec tests that listens to all the pass/fail/pending messages and inspects example metadata as you might in a formatter, however I have no intention of ever outputting any sort of progress indication from this helper (because it's aggregating data in such a way that there is no meaningful intermediate state).  This makes it exceeding difficult to make the operation of this helper transparent to the user because that there's no way I can see to distinguish a formatter which doesn't want to be involved in the output from one that does.  In other words, I'd like the behavior of a formatter but with the ability to not override the default formatter. If the CLI or the configuration defines another formatter, then there's no problem (because mine would simply be added to them).
Currently I can achieve the behavior I want by using the (private) reporter from a configuration and then its (public) register_listener api (I don't appear to need any other part of the reporter interface).  But I can't see any way to achieve the same result using only public interfaces.
I've searched previous issues (although not exhaustively) and didn't see anything particularly helpful.  However, I've seen people advise using the reporter interface on Configuration in a few places despite the fact that it's marked private, perhaps the easier way is just for it to be made public (or for me to treat it as such)?

Thanks for asking about our public APIs :).
This makes sense to me.  And perhaps RSpec.configuration.reporter should be public. I'm surprised it's not.
@JonRowe what do you think?  You've done the most work here.

I'm kind of surprised Configuration#reporter is private, my intent has been for it to be public, PR incoming...

Very cool. Thanks guys!

authors: JonRowe fireyone29 myronmarston

repo: rspec/rspec-core


text:
stub_const fails to set name of stubbed Class if example is not in context

Hello!
I found strange issue with stub_const helper:
Given lib/conveyor.rb
module Conveyor
  class NotFound < ArgumentError; end

  def self.find_module(key)
    raise NotFound.new(key)
  end

  def self.registered_modules
    []
  end

  def self.register(klass)
    return if registered_modules.include? klass
    mod = Module.new do
      define_method :find_module do |key|
        (key.to_s == klass.name.underscore.match(/\/(\w*)$/)[1]) ? klass : super(key)
      end

      define_method :registered_modules do
        super() + [klass]
      end
    end
    singleton_class.prepend mod
  end
end

lib/conveyor_modules.rb
module ConveyorModules
  class Base
  end
end

spec/test_spec.rb
require 'spec_helper'
require 'active_support/all'
require_relative '../lib/conveyor'
require_relative '../lib/conveyor_modules/base'

RSpec.describe Conveyor do
  describe '.register' do
    let!(:module_not_found) { stub_const 'Conveyor::NotFound', Class.new(ArgumentError) }

    let!(:s_module) { stub_const 'ConveyorModules::Foos', Class.new(ConveyorModules::Base) }

    before do
      subject.register s_module
    end

    context 'when key does not match' do
      it 'passes the .find_module message down the chain' do
        expect{subject.find_module 'not_foos'}.to raise_exception(module_not_found)
      end
    end

    it 'returns all registered modules' do
      expect(subject.registered_modules).to eq([s_module])
    end

    # context 'foo' do
    #   it 'returns all registered modules' do
    #     expect(subject.registered_modules.map(&:name)).to eq([s_module, s_module].map(&:name))
    #   end
    # end
  end
end

rspec -fd returns that:
Conveyor
  .register
    returns all registered modules
    when key does not match
      passes the .find_module message down the chain (FAILED - 1)

Failures:

  1) Conveyor.register when key does not match passes the .find_module message down the chain
     Failure/Error: expect{subject.find_module 'not_foos'}.to raise_exception(module_not_found)

       expected Conveyor::NotFound, got #<NoMethodError: undefined method `underscore' for nil:NilClass> with backtrace:
         # ./lib/conveyor.rb:16:in `block (2 levels) in register'
         # ./lib/conveyor.rb:16:in `block (2 levels) in register'
         # ./spec/test_spec.rb:19:in `block (5 levels) in <top (required)>'
         # ./spec/test_spec.rb:19:in `block (4 levels) in <top (required)>'
     # ./spec/test_spec.rb:19:in `block (4 levels) in <top (required)>'

Finished in 0.01177 seconds (files took 0.15501 seconds to load)
2 examples, 1 failure

Failed examples:

rspec ./spec/test_spec.rb:18 # Conveyor.register when key does not match passes the .find_module message down the chain

if commented example (with context) is uncommented, and same without context is commented, that suite passes
# it 'returns all registered modules' do
#   expect(subject.registered_modules).to eq([s_module])
# end

context 'foo' do
  it 'returns all registered modules' do
    expect(subject.registered_modules.map(&:name)).to eq([s_module, s_module].map(&:name))
  end
end

if we decide to use one without context, but explicitly call s_module.name in before clause it works just fine too
before do
  s_module.name
  subject.register s_module
end

it 'returns all registered modules' do
  expect(subject.registered_modules).to eq([s_module])
end

# context 'foo' do
#   it 'returns all registered modules' do
#     expect(subject.registered_modules.map(&:name)).to eq([s_module, s_module].map(&:name))
#   end
# end

So, it seems to me when it's out of context it executes first and somehow messes with the RSpec, and when we call name explicitly, that fixes the bug. Ruby sets name to the module when it is assigned to constant, so RSpec somewhere assigns it(or mimics that behavior), and when without context and name is not explicitly called that assign is not triggered anywhere.
I figured that when run all 3 examples without mapping :name to last one:
spec/test_spec.rb
it 'returns all registered modules' do
  expect(subject.registered_modules).to eq([s_module])
end

context 'foo' do
  it 'returns all registered modules' do
    expect(subject.registered_modules).to eq([s_module, s_module])
  end
end

produces output
Conveyor
  .register
    returns all registered modules
    when key does not match
      passes the .find_module message down the chain (FAILED - 1)
    foo
      returns all registered modules (FAILED - 2)

Failures:

  1) Conveyor.register when key does not match passes the .find_module message down the chain
     Failure/Error: expect{subject.find_module 'not_foos'}.to raise_exception(module_not_found)

       expected Conveyor::NotFound, got #<NoMethodError: undefined method `underscore' for nil:NilClass> with backtrace:
         # ./lib/conveyor.rb:16:in `block (2 levels) in register'
         # ./lib/conveyor.rb:16:in `block (2 levels) in register'
         # ./spec/test_spec.rb:19:in `block (5 levels) in <top (required)>'
         # ./spec/test_spec.rb:19:in `block (4 levels) in <top (required)>'
     # ./spec/test_spec.rb:19:in `block (4 levels) in <top (required)>'

  2) Conveyor.register foo returns all registered modules
     Failure/Error: expect(subject.registered_modules).to eq([s_module, s_module])

       expected: [ConveyorModules::Foos, ConveyorModules::Foos]
            got: [#<Class:0x00000002c493c8>, ConveyorModules::Foos, ConveyorModules::Foos]

       (compared using ==)

       Diff:
       @@ -1,2 +1,2 @@
       -[ConveyorModules::Foos, ConveyorModules::Foos]
       +[#<Class:0x00000002c493c8>, ConveyorModules::Foos, ConveyorModules::Foos]

     # ./spec/test_spec.rb:29:in `block (4 levels) in <top (required)>'

Finished in 0.01312 seconds (files took 0.1532 seconds to load)
3 examples, 2 failures

Failed examples:

rspec ./spec/test_spec.rb:18 # Conveyor.register when key does not match passes the .find_module message down the chain
rspec ./spec/test_spec.rb:28 # Conveyor.register foo returns all registered modules

Do not pay attention to difference like [s_module, s_module] != [s_module] and mapping :name, i know why those fail, that is not the point of report.
Test suite is available here: https://github.com/wyde19/rspec_fail

Thanks for the report! There's a lot going on here and I couldn't quite grok it all on a first pass. I'll try digging in more when I have some more time, but also if there is anything incidental in here you could remove that would be really helpful! For example:

Is the third example required?
The commented example and the uncommented one aren't the same. (So context might not be the defining characteristic?) Does this still repro if you make them the same?
There's a lot going on in the .register method. How much for that is required for a repro?

I suspect this will be related to Rails autoloading, (brought in by require 'active_support/all' and how that interacts with the missing constant.

@xaviershay I was trying to implement some extendable pipeline. Conveyor class is prepended by modules for each plug-in into pipeline, one finds respective to the key class in the pipeline and the other returns all pipeline modules.
Third example (if you are talking about it 'passes the .find_module message down the chain' do) is the one that fails. You see, when anonimous class is registered in pipeline, not matching anything key does not reach the root method (the Conveyor.find_module defined statically on Conveyor. Instead, it reaches one of the methods of prepended module, which have anonimous class enclosed in it, tries to call name.underscore on it and crashes into NoMethodError for nil:NilClass)
The commented example is the same from the issue's point of view. They differ in array size, in converting to string, but those are because when we register new module in before, we have unique s_module everytime (because of let) and so safeguard in methodregister does not work, it still registers the same (but not from the ruby point of view) class over and over. Hence comparison by class names, not factial objects, hence different size of array in different examples. Play with it yourself, you'll see what I mean.
That all originally was part of library in project at my work and I cut pretty much all I could to isolate the problem and still cause it to reproduce. All .register does, as I described above is overrides 2 methods on conveyor both of them are tested in examples. I tried to reproduce similar situation, but simply enclosed in method, defined in module in .register klass.name.nil? and tested against that. Does not reproduce.

@JonRowe probably not. You see, activesupport is there for inflections, namely klass.name.underscore which caused the error leading to discovery of the bug. There is no autoload expressions in the test app, moreover, no class extends or includes any activesupport class. Hence, only core extensions work. I could probably try to include core extensions only, but I didn't -- thought didn't cross my mind.

@wyde19 I'm not talking about the Ruby autoload declaration, but the fact active_support hijacks const_missing to load files, if you wish to use inflections I suggest you load only the inflections rather than require 'active_support/all'.
I suspect if you do a --backtrace you'll see active support lines in your tack trace.

To get around issues with autoloading I ended up doing this instead of using stub_const:
after(:each) do
  Base::Class.send(:remove_const, 'DISPATCH_STRATEGY')
  Base::Class.const_set('DISPATCH_STRATEGY', :original_value)
end

%i[a_value another_value original_value].each do
  it "should work for all 3 constants" do
    Base::Class.send(:remove_const, 'DISPATCH_STRATEGY')
    Base::Class.const_set('DISPATCH_STRATEGY', kind)
  end
end

Not sure if there will be any issues down the track but it seems to work ok (... and no flakey tests yet!)

Closing due to inactivity, and a reasonable workaround? during the monorepo migration.

authors: JonRowe istolpov wtfiwtz wyde19 xaviershay

repo: rspec/rspec-mocks


text:
Add syntax highlighting and mathJax for ui.markdown

+1 For adding math and syntax highlighting for ui.markdown
https://github.com/rstudio/py-shiny/blob/e47ecb538981e30b49d2b06fa3cca53e850ed35f/shiny/ui/_markdown.py#L56-L62

It looks like the markdown parser we're using is expecting us to use highlight.js because it will add the language class to the code block:
>>> ui.markdown("""```python
... def foo():
...     pass
... ```""")

def foo():
    pass

Indeed, if we add highlight.js, it will apply syntax highlighting. Here's a (meta) example in shinylive.
Since we have #522 about mathjax, would you mind if I reframed this issue about making it easier to work with highlight.js in shiny?

That sounds good @nealrichardson

Nice! Thanks @wch. Any chance this could be simplified to an argument in the call to ui.markdown (e.g., highlight=True)

I think you need more arguments than just highlight=True: at a minimum, you probably want to select the theme, of which there are many. So IMO we'll want to support this more fully than what is basically a workaround we've explored here.

authors: nealrichardson vnijs

repo: rstudio/py-shiny


text:
Add a machine learning example

Demo:
At Age = 0

At Age = 21

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

https://github.com/PARKER-X/shinny_ml

I think i need to close this pr

Closed!

authors: CLAassistant PARKER-X


text:
Error setting spark_config params

When connecting to yarn cluster, the only param accepted is sparklyr.driver.memory. I'm setting sparklyr.num.executors and a set of other params that are being ignored by Spark config. What am I doing wrong?

@keccah The properties you intend to pass to spark-submit can be pass with the prefix sparklyr.shell. (for a list of available parameters see https://spark.apache.org/docs/latest/submitting-applications.html#launching-applications-with-spark-submit). For the --num-executors parameter you would want to pass is as:
config <- spark_config()
config[["sparklyr.shell.num-executors"]] <- 2
sc <- spark_connect(master = "local", config = config)

To set parameters in the SparkContext, you can pass them with the prefix spark., so, for all these properties (http://spark.apache.org/docs/latest/configuration.html#available-properties) can be passed as:
config <- spark_config()
config[["spark.executor.memory"]] <- "2G"
sc <- spark_connect(master = "local", config = config)

@keccah let us know if the suggestion above did not resolve this issue. I would also recommend upgrading to the latest version of sparklyr by running devtools::install_github("rstudio/sparklyr") followed by a restart of your r session. In the meantime, I'll be closing this issue but feel free to activate if this code doesn't work as your would expect.

Still not working. The params are not being passed to Spark.

I'm using yarn-client as master.
First I set a number of environment variables: HADOOP_CONF_DIR, HADOOP_USER_NAME, SPARK_HOME
Then I write:
config <- spark_config() config[["sparklyr.shell.num-executors"]] <- 4 config[["sparklyr.shell.executor-memory"]] <- "16G" config[["sparklyr.shell.driver-memory"]] <- "4G" config[["sparklyr.shell.executor-cores"]] <- 5 sc <- spark_connect(master = "yarn-client", hadoop_version = "2.4", config = config)
The connection is made and Spark UI opens but without the parameters I'm passing.

This works. But only in SparkR (not Sparklyr).
Sys.setenv('SPARKR_SUBMIT_ARGS'='"-v" "--packages" "com.databricks:spark-csv_2.10:1.3.0" "--conf" "spark.driver.memory=4g" "--conf" "spark.executor.memory=16g" "--conf" "spark.executor.cores=5" "--conf" "spark.executor.instances=4" "sparkr-shell"')
Not I get all my parameters.

I tried the same thing in sparklyr but --conf was passing only one parameter no matter what.

@keccah I believe you want to use this instead:
config <- spark_config()
config[["spark.executors.instances"]] <- 4
config[["spark.executor.memory"]] <- "16G"
config[["spark.driver.memory"]] <- "4G"
config[["spark.executor.cores"]] <- 5
sc <- spark_connect(master = "yarn-client", config = config)

There are a couple different ways to pass parameters into Spark:

Passing them through the shell, using sparklyr.shell.*
Passing them through the SparkContext, using spark.*
Passing them through the HiveContext or SessionContext, using spark.sql.*

Let us know how this goes.

@keccah I am running on Google Dataproc, and followed @javierluraschi's instructions as follows:
config <- spark_config()
config[["spark.executor.memory"]] <- "4G"
sc <- spark_connect(master = "yarn-client", config = config)
With this settings and connection, I ran a job and disconnected, and then checked the environment in the job status; it was set correctly:

Let us know what environment you are running on, may be there is a difference.

I did exactly as @javierluraschi did. Still not working. T_T

@javierluraschi and @fereshtehRS it worked!

I wonder though if there's anyway to make the query using "spark_read_parquet" and not uploading the table to memory until I do any collect command.

Nice :)
Did you have to do anything special to make it work?
I don't know the answer to your question; leave it to @javierluraschi to answer.

@keccah you can load the data with spark_read_parquet(sc, name, path, memory = FALSE). By default, sparklyr loads all data into memory.

authors: fereshtehRS javierluraschi keccah

repo: rstudio/sparklyr


text:
Bump Python to 3.12

Is your feature request related to a problem? Please describe.
Currently running into issues when using this package together with other packages that are requiring Python 3.12.
Describe the solution you'd like
Can the Python version be bumped to 3.12?

Bumped to 3.12 in v0.13.0

repo: rtdip/core


text:
Seaching camel-case words returns invalid results

Entering a ReadTimeout (camel-case) is interpret as read timeout.
I found a way to reproduce this issue in requests project:

read timeout (separated words), returns 2 hits: https://requests.readthedocs.io/en/master/search/?q=read+timeout

ReadTimeout (one word), returns the exact 2 hits: https://requests.readthedocs.io/en/master/search/?q=ReadTimeout

Although, in the second example, it should return something about https://requests.readthedocs.io/en/master/api/#requests.ReadTimeout as https://requests.readthedocs.io/en/master/search/?q=TooManyRedirects does.

Finally, readtimeout (lower case) returns exactly the result that I would want for ReadTimeout (camel case): https://requests.readthedocs.io/en/master/search/?q=readtimeout

I noted two more things here:

the results that you can see in the images, all of them are in Italic but the last one is highlighted in yellow
only the last image has reStructuredText on its response

@humitos Tried reproducing this but the search results vary in my local deployment where I have built the docs of requests using the Github URL of my fork.
Search query read timeout:

Search query ReadTimeout:

Search query readtimeout:

Am I missing something?

I think you need to setup elastic search on your local instance

I have the exact version as mentioned in the docs setup already.

@safwanrahman were you able to test this out with the new changes you were making to the whole search? Did you notice any difference with current production version?

@humitos I did not get chance, I will look into it as soon as we deploy.

I suspect its related to the Domain object indexing. requests.ReadTimeout is a domain object. As we are not indexing domain object separately, it will not work on the upgraded search also.
It will  be fixed with #4289

authors: humitos invinciblycool safwanrahman stsewd


text:
Remove deprecated build URLs

Once #4568 gets merged, deployed and after 31st January we can remove all of these URLs and all the code associated to them since they will stop working and won't be used anymore.
Similar PR for corporate site at https://github.com/rtfd/readthedocs-corporate/pull/433

I am interested in sending a PR for this.
But, I am not able to find what exactly needs to be removed.
Can I get some help on this to get started.

@dojutsu-user there is a PR open for this https://github.com/rtfd/readthedocs.org/pull/5479

@stsewd
Thanks for that.

authors: dojutsu-user humitos stsewd


text:
Odd issue, have multiple accounts with same email address, GitHub sync only works with one =(

Hello and thanks for this amazing service. One problem that I have is that I seem to have created a new account by logging in with my email address instead of my username. I'm not sure exactly how I can see the email addresses that are associated with an account, and this might just be an issue with my own stupidity.
One account I synced my GitHub with and thus seemed to render the other account useless on trying to do this. The accounts are as follows https://readthedocs.org/profiles/JoshuaEstes/ (Synced with GitHub) and https://readthedocs.org/profiles/f1gm3nt/ (Not Synced with GitHub). Let me know if there is anything else you need from me. Great work guys!

This ticket has be lingering for a long time, closing and merging into #1875. Feel free to follow there if this is still an issue.

authors: JoshuaEstes agjohnson


text:
:github_url: as a theme option

I am trying to reproduce locally the output I get in RTD (see readthedocs-docker-images#47). According to the README here, it seems that I need to manually add :github_url: to each page in order to have 'Edit on GitHub' instead of 'View page source'. I would expect this option to be available as a theme option, so that the same sources produce the same result in RTD and locally.

You can reproduce this locally by changing your conf.py:
html_context = {
  'display_github': True,
  'github_user': 'username',
  'github_repo': 'reponame',
  'github_version': 'master'
}

Related to #156.

Thanks a lot. That's exactly what I needed. However, I had to slightly modify it:
'display_github': True,
'github_user': 'username',
'github_repo': 'reponame',
'github_version': 'branch/doc/'

Note the subdir after the branch/version, and the trailing slash.
I close this, because the question is solved. But you might want to reopen it to keep track of the pending documentation.

This is a duplicate of #465

You don't need to have a slash in github_version, see example here:
https://github.com/readthedocs/sphinx_rtd_theme/issues/231#issuecomment-126447493
I'll add a comment on #465.

authors: 1138-4EB Blendify jessetan peterjc


text:
Identify react elements properly on IE 11

This was failing on IE 11 but now it is working properly.

Coverage decreased (-0.01%) to 96.1% when pulling 8ae4ffc2ea8fb199165ec91059d5619484ba8c98 on bjonamu:master into 2d870b14a01e222493c686a7644181185f859558 on rtfeldman:master.

authors: bjonamu coveralls

repo: rtfeldman/seamless-immutable