bug wwhen using LPE

https://github.com/PX4/Firmware/blob/master/src/modules/local_position_estimator/BlockLocalPositionEstimator.cpp#L392
I encountered a serious bug when using LPE, during transition from mc -> fw, the whole system is blocked, I tried command "top" in console, it's also dead, nothing showed but:
"[lpe] reinit x"
"[lpe] reinit x"
"[lpe] reinit x"
"[lpe] reinit x"
"[lpe] reinit x"
"[lpe] reinit x"
"[lpe] reinit x"
....
...
...
....
...
then at the same time, the data link is lost.
@LorenzMeier
@jgoppert
@mhkabir
@sanderux

This could suggest there is a nan being fed to lpe via a sensor. Do you have a log file?

You mean that it's some sensor continuously sends NAN data to LPE?
If so, why the whole system is blocked? It looks like that only the LPE is running....
And as the system is blocked, sorry I don't have the log for the bug.
@jgoppert

@JohnSnowball how can I try to reproduce this. Are you running in SITL?

That's a long strory...A few weeks ago, I suffered a crush with a standard vtol:
http://discuss.px4.io/t/standard-vtol-lost-control-during-alt-hold-mode/1008/3
Then I made a matlab program to try to reproduce that bug.
And this time, I encountered the bug in the issue(no crash, just simulation).
The plane has something in common with last crush:

the whole system blocked
the data link is lost and can't regain by itself.
things happen during transition mc -> fw

@JohnSnowball  I just tried vtol simulation in gazebo and transitioned to vtol and back, I can't reproduce the bug on master. What is the git hash of your software version?
build command:
make posix_sitl_default gazebo_standard_vtol

INFO  [simulator] Got initial simuation data, running sim..
INFO  [pwm_out_sim] MODE_8PWM
INFO  [tone_alarm] startup
WARN  [vtol_att_control] failed setting min values
WARN  [vtol_att_control] failed setting max values
WARN  [vtol_att_control] failed setting min values
.
.
INFO  [mavlink] mode: Normal, data rate: 2000000 B/s on udp port 14556 remote port 14550
INFO  [mavlink] mode: Onboard, data rate: 2000000 B/s on udp port 14557 remote port 14540
INFO  [sdlog2] [blackbox] rootfs/fs/microsd/log/2016-09-25
WARN  [sdlog2] sdlog2: failed setting sched params
INFO  [sdlog2] [blackbox] recording: 07_27_05.px4log
INFO  [mavlink] MAVLink only on localhost (set param MAV_BROADCAST = 1 to enable network)
pxh> INFO  [mavlink] partner IP: <IP_ADDRESS>
INFO  [local_position_estimator] [lpe] baro init 0 m std 0 cm
INFO  [local_position_estimator] [lpe] z resume
INFO  [local_position_estimator] [lpe] gps init lat  47.40 lon   8.55 alt 488.1 m
INFO  [local_position_estimator] [lpe] xy resume
INFO  [commander] home: 47.3977419, 8.5455939, 488.09
INFO  [tone_alarm] home_set

pxh> INFO  [tone_alarm] neutral
commander takeoff
pxh> INFO  [commander] Taking off
INFO  [tone_alarm] positive
INFO  [commander] home: 47.3977440, 8.5455936, 488.18
INFO  [tone_alarm] arming
INFO  [commander] Takeoff detected

pxh> commander tran[Wrn] [Publisher.cc:140] Queue limit reached for topic /gazebo/default/standard_vtol/gazebo/command/motor_speed, deleting message. This warning is printed only once.
sition
pxh> WARN  [vtol_att_control] failed setting max values
WARN  [vtol_att_control] failed setting min values

pxh>
pxh>
pxh> commander status
WARN  [commander] type: forward motion
WARN  [commander] safety: USB enabled: [NO], power state valid:  [OK]
WARN  [commander] avionics rail:  -1.00 V
WARN  [commander] home: lat = 47.3977440, lon = 8.5455936, alt = 488.18, yaw: 0.01
WARN  [commander] home: x = 0.2309987, y = -0.0242839, z = -0.10
WARN  [commander] datalink: OK
WARN  [commander] main state: 10
WARN  [commander] nav state: 17
WARN  [commander] arming: ARMED
pxh>
pxh>
pxh> commander transition
pxh> WARN  [vtol_att_control] failed setting max values
WARN  [vtol_att_control] failed setting min values

pxh>
pxh>
pxh> commander status
WARN  [commander] type: symmetric motion
WARN  [commander] safety: USB enabled: [NO], power state valid:  [OK]
WARN  [commander] avionics rail:  -1.00 V
WARN  [commander] home: lat = 47.3977440, lon = 8.5455936, alt = 488.18, yaw: 0.01
WARN  [commander] home: x = 0.2309987, y = -0.0242839, z = -0.10
WARN  [commander] datalink: OK
WARN  [commander] main state: 10
WARN  [commander] nav state: 17
WARN  [commander] arming: ARMED

@jgoppert
The firmware version is master a few weeks ago.
It's not SITL, the sensor data comes from the Matlab program. I guess it's the bad sensor data which caused the bug.
But if so, why the whole system is blocked and data link is lost?
At least the LPE is still runing during the bug, why data link is lost? I see no relation between bug an data link lost.

The fastest that LPE will run is 100 Hz. I'm guessing that the accelerometer data is returning NaN. There is no check for this in the predict function. Then on the next step it detects the NaN in the state for LPE and re-initializes it. There is no reason that this would block the data link to my knowledge. Possibly your matlab program is not sending any valid data at that point and it sends a NaN somewhere else in the system that locks a more vital process.

@JohnSnowball have you tried running ekf2 and seeing if you get the same error?

@jgoppert  I reproduced the bug twice again! I hope you could take a look at the log file, especially for the accelerometer data as I can't confirm that was NAN data.
http://logs.uaventure.com/view/79xk2ELByoFru3wzyX4PMH
http://logs.uaventure.com/view/6purs8A3QRwjgWmaxN8NYM
If you think it's not NAN data,  I can make a NAN data manually and send it by matlab.
breaklog.zip

btw, I never used ekf2, as I can't understand the code, it seems too different from a normal ekf predict->correct process.

Can you also reproduce it on latest master?

@jgoppert ok, but it will take a little bit time.

@jgoppert
I did another test, and got 2 more things make me confused....
I tried to use pos_estimator_inav to replace LPE to see if it works well.

SYS_MC_EST_GROUP, this parameter, I can't modify it in QGC, everytime I change it and restart px4, this value goes back to LPE. Finally, I modify this value through console.... Why I can't change that value with QGC? Shall I make some modification somewhere else?
The bug can't be reproduced with pos_estimator_inav, I guess it's LPE that requires better data quality, it can't handle bad data as well as inav. I wish you could give some comment.

And, if my plane doesn't have enough control ability, should I choose pos_estimator_inav instead of LPE?

You should be able to set mc est group in qgc and it should stick after reboot. I saw a similar issue on master a few weeks ago. Please try updating to latest master.

@jgoppert  hi, I found that bug is not in LPE, it's caused by other thread. I opened another issue, could you take some time to read that?
https://github.com/PX4/Firmware/issues/5553


Question about performance

Hi，
I am using goflow2 by docker image，now，i test the performance.
about 50Kp/s（about 50Mb/s）, goflow2 working fine. but when i increase the pps, it appears some problem.
onenetflow packets contains one flow info in a packet.
Server configuration

24 cpus enable hyperthreading,128g memory.
Centos 7.2
Docker version 24.0.7, build afdd53b
core.rmem_max = 91299200
Interface configuration: Speed:1000Mb/s，ethtool -g: Current hardware settings:RX:4096.
kcg used, goflow version is v2.1.1.
5 tuple contained in payload, all the netflow packets sent by only a netflow exporter.

Command start goflow2
docker run -d --name goflow2 --network conf_mynet -p 8080:8080 -p 6343:6343/udp -p 2055:2055/udp art.sinovatio.com/public-docker/netsampler/goflow2:v2.1.1 --transport.kafka.brokers=kafka:9092 --transport=kafka --transport.kafka.topic=flows --transport.kafka.hashing=true --format=bin --listen "netflow://:2055/?count=24&workers=48&blocking=false&queue_size=10000000"
Two questions.

About 100Kp/s（about 100Mb/s）, no packets droped by interface , but goflow2 got less than the packets i sent. i send 10 million packets total, goflow2 show it got 9.98 million packets on 8080/metrics，no dropped packets count show.  Please help analyze where packets may be lost.
About 500Kp/s（about 500Mb/s）,  i send 10 million packets total, about 5 million packets droped by interface(i got it by "ethtool -S",and show "rx_missed_errors" count increased about 5 million), but no packets droped by interface when i closed goflow2 and sent the same packets again. Please help analyze the reason and how to fix it.

Thanks!

Hello,
What tool are you using to generate those packets? Is it on the same machine?
What indicates packet drops:

flow_dropped_packets_total on 8080/metrics
UDP errors from the kernel

Which metric are you using to count the packets? Does it include templates?
In both your questions, did flow_dropped_packets_total return anything?
Would you also be able to count the number of packets using the data in Kafka? Possibly counting the sequence number?
Please provide the average CPU and memory usage.
KCG is a nice bootstrap stack but the toolings on the system may use more resources than necessary. Have you tried running just GoFlow2?
In terms of improvements, have you increased/reduced the number of workers?
I think with these amounts of packets, it is advisable to load-balance across multiple machines and scale horizontally: chasing extra packets might not be possible or worth it.

Hi,
I used npb to generate those packets( same packets , goflow2 50Kp/s no problem, the packets is no problem ) , it is directly connected through network cables between npb interface and server interface.  at the beginning, flow_dropped_packets_total  appeared, after we increase the count, workers and queue size, flow_dropped_packets_total never appeared again.
UDP errors from the kernel
----How to get this statistic？is "netstat -su"？
Which metric are you using to count the packets? Does it include templates?
---goflow2_flow_traffic_packets_total
In both your questions, did flow_dropped_packets_total return anything?
---- no
Would you also be able to count the number of packets using the data in Kafka? Possibly counting the sequence number?
----yes ,i count the number in the partition, the records count equals goflow2_flow_traffic_packets_total
Please provide the average CPU and memory usage.
----It seems like the server resources are not fully utilized

I think with these amounts of packets, it is advisable to load-balance across multiple machines and scale horizontally: chasing extra packets might not be possible or worth it.
----the performance.md says  "This software has been tested with hundreds of thousands of flows per second on common hardware",  can goflow2 process 50Kp/s(means 50Kf/s) neflow packets ?

This problem involve many parts that are not just GoFlow2.
I don't think I can help without having control of the environment and the knowledge of these tools and unfortunately I do not have enough time. I would need the exact CLI args used, packet counts observed, resource graphs.
I'm suspecting the tool emitting the flows may also be dropping on the outbound path and are never received. This would have to be tested independently using tcpdumps or sampling locally.

Docker may also play a part as well with the forwarding and NAT-ing.

----the performance.md says "This software has been tested with hundreds of thousands of flows per second on common hardware", can goflow2 process 50Kp/s(means 50Kf/s) neflow packets ?

In theory yes, and per your specs there should be more capacity available but GoFlow2 can have specific outputs, serializations and other tools running may impact its performance.
The only advice I can give would be to scale horizontally, load-balance the flows (since IPFIX/NetFlow, on a per sampler basis) and dedicate those machines to flow decoding. Kafka and ClickHouse should be setup on other machines.
htop and observing the distribution of compute on CPUs will help tuning the buffers and workers count adapted to your environment.
Counting the flow sequence inside ClickHouse using SQL (not just Kafka) will help isolating which packets were dropped.
Comparing with other tools like Akvorado could also provide insights on where the packets are dropped.


Rebalance Sulfur

Reduce Hydrogen sulfide gas from stage 1 washing. Best way of getting sulfur shouldn't just be spamming this.
Buff lime filtering to compensate.
Check that early game isn't too painful, now that Water treatment isn't a startup tech KiwiHawk/SeaBlock#85 (Will this need to be reversed?)

Currently, with tier 1 buildings to produce 1k Sulfuric acid/s

From washing: 802 buildings. 95.9MW
From lime filters: 1079 buildings.  143.2MW

Currently, with tier 1 buildings to produce 1k Sulfuric acid/s

From washing: 802 buildings. 95.9MW
From lime filters: 1079 buildings.  143.2MW

With changes, with tier 1 buildings to produce 1k Sulfuric acid/s

From washing: 1601 buildings. 153.7MW
From lime filters: 630 buildings. 97.9MW (+ 0.7 aluminium ore, 0.7 silver ore)

With changes, with tier 1 buildings to produce 1k Sulfuric acid/s

From washing: 1601 buildings. 153.7MW
From lime filters: 630 buildings. 97.9MW (+ 0.7 aluminium ore, 0.7 silver ore)


resolve nested export from priority list do not default resolve import

I updated multiple other packages and files during the time this PR was made and unfortunately I can't find that package which caused the issue for which this PR was made and therefore I cannot add a proper test...
Here is what I remember (sorry. wordy),

node.js' native meta.import.resolve appears to handle any package.json with "exports" as a "module" type package, as indicated by some of the unit tests already found in resolvewithplus. An issue resolved here is that nested export patterns like the dot expression here "export": { ".": { "import": "...", "require": "..." } } were not resolving the correct value according to the package.type and meta.import.resolve returns the "import" definition even when no package.json type is defined,
node.js' native meta.import.resolve resolved nested export named properties according to best-match rather than the order of defintions. eg, "export": { ".": { ... }, "lib/feature": "..." } if both "." and "./lib/feature" matched the imported moduleId "./lib/feature" definition would be returned regardless of the order it was defined relative to "."
using custom "priority" options with resolvewithplus did not work for nested dot expressions, where previously the import definition would be returned first always.

The import/export patterns that were copied from the nodejs documentation to unit-tests here... those tests still pass here with no changes. Those tests and many others compare the resolvewithplus results with import.meta.resolve results and those tests still pass.  Any regressions added here are probably edge-case.

this branch was cloned into a local copy of esmock and the esmock tests pass as well... going to merge and publish this


use tox, github actions

Testing out #97

Codecov Report

Merging #99 (f74ec27) into master (f51f714) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #99   +/-   ##
=======================================
  Coverage   93.25%   93.25%
=======================================
  Files          12       12
  Lines        1082     1082
=======================================
  Hits         1009     1009
  Misses         73       73

Flag
Coverage Δ

unittests
93.25% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

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

cheers 🍷 @vincentsarago


Traefik cannot find kubernetes secrets

Do you want to request a feature or report a bug?
Bug
What did you do?
Deployed traefik with kubernetes backend, aiming to use certificates stored in kubernetes secrets
What did you expect to see?
Traefik using the certificate from kubernetes secret
What did you see instead?
Traefik using it's own default certificate and logging that the kubernetes secret doesn't exist. I let it run overnight to allow plenty of time for the secrets sync, but without luck
Output of traefik version: (What version of Traefik are you using?)
Version:      v1.6.0-rc3
Codename:     tetedemoine
Go version:   go1.10
Built:        2018-03-28_04:04:00PM
OS/Arch:      linux/amd64

What is your environment & configuration (arguments, toml, provider, platform, ...)?
apiVersion: v1
kind: Service
metadata:
  name: external-ingress-proxy
  namespace: sys-ingress-pub
spec:
  selector:
    app: external-ingress-proxy
  type: NodePort
  ports:
  - name: http
    port: 80
    nodePort: 30180
  - name: https-proto
    port: 443
    nodePort: 30143
  selector:
    k8s-app: external-ingress-proxy
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: external-ingress-proxy
  namespace: sys-ingress-pub
  labels:
    k8s-app: external-ingress-proxy
spec:
  replicas: 1
  selector:
    matchLabels:
      k8s-app: external-ingress-proxy
  revisionHistoryLimit: 8
  template:
    metadata:
      labels:
        k8s-app: external-ingress-proxy
        name: external-ingress-proxy
    spec:
      terminationGracePeriodSeconds: 60
      containers:
      - image: traefik:1.6.0-rc3-alpine
        name: traefik
        ports:
        - containerPort: 80
        - containerPort: 443
        - containerPort: 8080
        args:
        - --web
        - --web.metrics
        - --web.metrics.prometheus
        - --logLevel=INFO
        - --kubernetes
        - --kubernetes.labelselector=kubernetes.io/ingress.class=traefik-public
        - --entryPoints=Name:http-redirect Address::80 Redirect.EntryPoint:https-proto
        - --entryPoints=Name:https-proto Address::443 TLS
        - --defaultentrypoints=http-redirect,https-proto

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: nginx
  namespace: sys-mon
  annotations:
    kubernetes.io/tls-acme: "true"
    kubernetes.io/ingress.class: traefik
  labels:
    kubernetes.io/ingress.class: traefik-public
spec:
  tls:
  - secretName: traefik-test-tls-cert
  rules:
  - host: myservice.io
    http:
      paths:
      - path: /
        backend:
          serviceName: nginx
          servicePort: 80
---
apiVersion: v1
kind: Service
metadata:
  name: nginx
  namespace: sys-mon
  labels:
    name: nginx
spec:
  selector:
    app: nginx
  ports:
  - name: web
    port: 80
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx
  namespace: sys-mon
spec:
  replicas: 1
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      name: nginx
      namespace: sys-mon
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx
        ports:
        - name: web
          containerPort: 80

RBAC clusterrolebinding:
Name:         traefik-test
Labels:       <none>
Annotations:  <none>
Role:
  Kind:  ClusterRole
  Name:  cluster-admin
Subjects:
  Kind            Name     Namespace
  ----            ----     ---------
  ServiceAccount  default  sys-ingress-pub

The secret with the cert:
Name:         traefik-test-tls-cert
Namespace:    sys-mon
Labels:       <none>
Annotations:  <none>
Type:  kubernetes.io/tls
Data
====
tls.crt:  1034 bytes
tls.key:  1704 bytes

If applicable, please paste the log output at DEBUG level (--logLevel=DEBUG switch)
time="2018-04-04T08:57:49Z" level=warning msg="web provider configuration is deprecated, you should use these options : api, rest provider, ping and metrics"
time="2018-04-04T08:57:49Z" level=info msg="Traefik version v1.6.0-rc3 built on 2018-03-28_04:04:00PM"
time="2018-04-04T08:57:49Z" level=info msg="\nStats collection is disabled.\nHelp us improve Traefik by turning this feature on :)\nMore details on: https://docs.traefik.io/basics/#collected-data\n"
time="2018-04-04T08:57:49Z" level=info msg="Preparing server https-proto &{Address::443 TLS:0xc420402280 Redirect:<nil> Auth:<nil> WhitelistSourceRange:[] WhiteList:<nil> Compress:false ProxyProtocol:<nil> ForwardedHeaders:0xc420485b80} with readTimeout=0s writeTimeout=0s idleTimeout=3m0s"
time="2018-04-04T08:57:51Z" level=info msg="Preparing server traefik &{Address::8080 TLS:<nil> Redirect:<nil> Auth:<nil> WhitelistSourceRange:[] WhiteList:<nil> Compress:false ProxyProtocol:<nil> ForwardedHeaders:0xc420485f40} with readTimeout=0s writeTimeout=0s idleTimeout=3m0s"
time="2018-04-04T08:57:51Z" level=info msg="Starting server on :443"
time="2018-04-04T08:57:51Z" level=info msg="Preparing server http-redirect &{Address::80 TLS:<nil> Redirect:0xc4203ca1c0 Auth:<nil> WhitelistSourceRange:[] WhiteList:<nil> Compress:false ProxyProtocol:<nil> ForwardedHeaders:0xc420485a40} with readTimeout=0s writeTimeout=0s idleTimeout=3m0s"
time="2018-04-04T08:57:51Z" level=info msg="Starting server on :8080"
time="2018-04-04T08:57:51Z" level=info msg="Starting provider *kubernetes.Provider {\"Watch\":true,\"Filename\":\"\",\"Constraints\":[],\"Trace\":false,\"TemplateVersion\":0,\"DebugLogGeneratedTemplate\":false,\"Endpoint\":\"\",\"Token\":\"\",\"CertAuthFilePath\":\"\",\"DisablePassHostHeaders\":false,\"EnablePassTLSCert\":false,\"Namespaces\":null,\"LabelSelector\":\"kubernetes.io/ingress.class=traefik-public\",\"IngressClass\":\"\"}"
time="2018-04-04T08:57:51Z" level=info msg="Starting server on :80"
time="2018-04-04T08:57:51Z" level=info msg="Creating in-cluster Provider client"
time="2018-04-04T08:57:52Z" level=error msg="Error configuring TLS for ingress sys-mon/nginx: secret sys-mon/traefik-test-tls-cert does not exist"
time="2018-04-04T08:57:52Z" level=info msg="Server configuration reloaded on :80"
time="2018-04-04T08:57:52Z" level=info msg="Server configuration reloaded on :443"
time="2018-04-04T08:57:52Z" level=info msg="Server configuration reloaded on :8080"
time="2018-04-04T09:07:51Z" level=warning msg="Error checking new version: GET https://api.github.com/repos/containous/traefik/releases: 403 API rate limit exceeded for <IP_ADDRESS>. (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.); rate reset in 20m5.628041774s"
time="2018-04-04T09:07:52Z" level=error msg="Error configuring TLS for ingress sys-mon/nginx: secret sys-mon/traefik-test-tls-cert does not exist"
time="2018-04-04T09:17:52Z" level=error msg="Error configuring TLS for ingress sys-mon/nginx: secret sys-mon/traefik-test-tls-cert does not exist" W0404 09:20:39.482673       1 reflector.go:341] github.com/containous/traefik/vendor/k8s.io/client-go/informers/factory.go:86: watch of *v1.Endpoints ended with: too old resource version: 5095910 (5096509)
time="2018-04-04T09:27:52Z" level=error msg="Error configuring TLS for ingress sys-mon/nginx: secret sys-mon/traefik-test-tls-cert does not exist"
time="2018-04-04T09:37:52Z" level=error msg="Error configuring TLS for ingress sys-mon/nginx: secret sys-mon/traefik-test-tls-cert does not exist" W0404 09:45:27.582778       1 reflector.go:341] github.com/containous/traefik/vendor/k8s.io/client-go/informers/factory.go:86: watch of *v1.Endpoints ended with: too old resource version: 5098162 (5098951)
time="2018-04-04T09:47:52Z" level=error msg="Error configuring TLS for ingress sys-mon/nginx: secret sys-mon/traefik-test-tls-cert does not exist"
time="2018-04-04T09:57:52Z" level=error msg="Error configuring TLS for ingress sys-mon/nginx: secret sys-mon/traefik-test-tls-cert does not exist"
time="2018-04-04T10:07:52Z" level=error msg="Error configuring TLS for ingress sys-mon/nginx: secret sys-mon/traefik-test-tls-cert does not exist"

Ran some initial tests via minikube. I think we may be observing two issues here:

The label selector seems to apply to all objects and not just Ingresses. This looks lika a regression from #2867 to me when we applied the label selector filter to the single, per-namespace factory (and not excluded the non-Ingress objects) /cc @yue9944882
The secret is not picked up, even when I remove the label selector. The error message just keeps popping up.

Submitted a PR to fix the label selector issue.

@hectorhuertas when I remove the label selector and apply all of your manifests to a minikube-based cluster, I see the TLS error message disappearing rather quickly and HTTPS working:
$ curl -k -L -H 'Host: myservice.io' https://<IP_ADDRESS>:30143/
<!DOCTYPE html>

<title>Welcome to nginx!</title>

Welcome to nginx!

If you see this page, the nginx web server is successfully installed and
working. Further configuration is required.

For online documentation and support please refer to
nginx.org.

Commercial support is available at
nginx.com.

Thank you for using nginx.

Do you have the possibility to check again without the label selector (or with the label selector and the Docker image timoreimann/traefik:labelsel-fix containing the fix from the PR)?
By the way: You have the selector defined twice in your Traefik service manifest -- once with the wrong label (app) and the other time with the correct one (k8s-app). Luckily, the correct one comes last and overrides the first one. You may want to fix that in your manifests.

I have removed the wrong duplicated app selector and applied the configuration with the label selector, using your timoreimann/traefik:labelsel-fix image.
I get the same results as you: the TLS error message disappearing rather quickly and HTTPS working
Thanks for the super quick fix!

hi,
i have the same problem. tried your timoreimann/traefik:labelsel-fix image but error still occurs:
traefik-ingress-lb time="2018-04-07T19:42:50Z" level=info msg="Traefik version 75856d006cf526203121b36f1c31cc40ad6cf4be built on 2018-04-05_11:52:33PM"
...
traefik-ingress-lb time="2018-04-07T19:42:50Z" level=error msg="Error configuring TLS for ingress default/httpbin: secret default/httpbin does not exist"

but
➜  ~ kubectl describe secret -n default httpbin
Name:         httpbin
Namespace:    default
Labels:       <none>
Annotations:  <none>

Type:  kubernetes.io/tls

Data
====
tls.crt:  3826 bytes
tls.key:  1679 bytes

the secret is created by cert-manager but this shouldn't have any impact.

@ulrichSchreiner did you wait long enough? It could theoretically take up to several minutes before the certificate is recognized.
If you did, please create a new issue along with all relevant manifests and DEBUG level logs. Thanks.

@ulrichSchreiner the certificates problem is fixed by #3136

Hello @ulrichSchreiner ,
Many thanks for your feedback.
Actually, Træfik really adds TLS certificates only on TLS EntryPoints.
However, if the defined frontend has no defined EntryPoint (option traefik.frontend.entryPoints), Træfik tries to add the service and its certificates to the defaultEntryPoints.
If no defaultEntryPoints have been defined, Træfik will add the service to the http entryPoint but it will not add the certificates. It will just append the DEBUG message Certificates not added to non-TLS entryPoint http. in Træfik logs.
Create the defaultEntryPoints list or a traefik.frontend.entryPoints list with your TLS EntryPoint are the good way to add correctly your certificates to this EntryPoint.

Did someone already try this with multiple certificates? I have two different hostnames with separate certificates (Catch all certs). The first ingress works fine, for the second one I only get the TRAEFIK DEFAULT CERT. I'm also testing on the above image, so not sure where the problem is. I've also noticed fequent reloading of the configuration about every 5 seconds - is this normal? :thinking:

Hello @kordianbruck ,
Many thanks for your interest in the project.
If you think there is an bug in Træfik, can you open a new issue and provide all the information about your configuration?
Moreover, for more help, you can  join our Slack workspace for more community #support.

I close the issue because is original bug is fixed.
If you have a similar problem, feel free to join our Slack workspace for more community #support or open a new issue.

Hmm, it sounds like this is fixed but I am hitting the same issue today with 1.6.4. I am not specifying any custom labels to match for the Ingress with kubernetes.labelSelector (I have installed via the helm chart).
My config file looks like this:
# traefik.toml
logLevel = "INFO"
defaultEntryPoints = ["http","https"]
[entryPoints]
  [entryPoints.http]
  address = ":80"
  compress = true
  [entryPoints.https]
  address = ":443"
  compress = true
    [entryPoints.https.tls]
      minVersion = "1.2"
      [[entryPoints.https.tls.certificates]]
      CertFile = "/ssl/tls.crt"
      KeyFile = "/ssl/tls.key"
[kubernetes]
[web]
address = ":8080"

I ran into the same issue on 1.7.4 installed by helm (with ssl.enabled set to true) and manually created and set the service account.
After a lot of trial and error I found that removing http from defaultEntryPoints from traefik's configmap seemed to fix the problem!

@dNetGuru if you do that, then ingresses will not bind to HTTP, and you'd have to explicitly add "http" entrypoint via Annotations
And ingress.kubernetes.io/ssl-redirect: "true" will be meaningless, without explicit "http" entrypoint on ingress.

I was running into the same issue, and the only relief was the ORDERING of the defaultentrypoints=https,http.
If I set defaultentrypoints=http,https it will not work. https has to go first. Nothing else helps, traefik chokes with this very misleading error message that it cannot find the certificates. *sigh
traefik version 1.7.9 hope this helps to anyone coming from Google.

@Overbryd, also using traefik 1.7.9
even though error is displayed at first, traefik does the right thing, after it takes a moment to find certificates

@ulrichSchreiner did you wait long enough? It could theoretically take up to several minutes before the certificate is recognized.

hum, you can check namespaces accross traefik and secret


Updated validations.py python scripts

Fixed the behavior of validate_user function in validations.py
Closes: #1
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


Backend validation for 0 quantity grouped product.

Issue Reference
https://github.com/bagisto/bagisto/issues/6429
Description
Back end validation for zero quantity grouped product.

@papnoisanjeev
I think the pr is already created for this issue. https://github.com/bagisto/bagisto/pull/6522
@devansh-webkul Please look into it

Closing as already default 1 quantity is going if someone bypass  0 anyway.


Polish localization and English typo fix

I don't know how to implement it into the program, so I'll just leave it here for someone to implement it.
Also, I fixed a typo in English locale. The word connection was missing an e. Again I'll leave it here.

Thanks for your work.
To implement in the project (and get credited automatically 😅) you just need to fork the project, edit/change/add your contributions in your forked project, and then submit a pull request to get your changes submitted in this project. Hope it helps

I could do this for the typo in English, but when I just put the Polish file in, it didn't do anything, so I assumed I had to change some code for it to work, and I rather not mess with that up, unless it should work, and I just did something wrong with the file itself.

Oh wait, I just reinstalled the whole program, and it started working! I'll make pull request shortly!

Thank you for your help and feedback 👍

You're welcome!


release(prod): bump miner to 2<IP_ADDRESS> GA

Why

Bump to 2<IP_ADDRESS> GA
How

Bump up latest GA in hm-miner
https://github.com/NebraLtd/hm-miner/commit/0d4ce82e61a6d2fcb4a029c9d51b6de8c0443e48
References

Ref #246
Closes: #251
https://engineering.helium.com/2021/11/19/blockchain-release-sync-and-snapshot-improvements.html

Draft until tested on testnet. Pushed to testnet around 3.00 AM UTC 20th November 2021

@KevinWassermann94 if you are happy with this on testnet, we could push to mainnet so that hotspots pull in the latest snapshot to get past the stuck block

Running fine on testnet. I suspect another GA shortly though

Yep agreed. Also, this probably won't help due to another stuck block.
Will see how things play out today

Will push this while we test the new GA out on testnet


fix(clusters): fix tls renew query

Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1027
#1026  👈
#1025
#1023
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @MasterPtato and the rest of your teammates on  Graphite


Speedup test_ucf101

Rough improvement: ~40%

Before: 110.86sec - reference
After: 67.17sec - reference

The above are rough estimations based on a couple or runs.

The failing tests are not related to this PR.


⚠ ClamAV has degraded performance

In 26526d4, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 216 ms

Resolved: ClamAV performance has improved in 1bd7a3f.


Removing a cluster from the Dashboard view looks like the User is deleting the cluster altogether

Description
When I wanted to remove one of the clusters connected to my Kyma Dashboard from its view, the message that popped up asked me whether I wanted to delete the cluster and it baffled me for a second, because it looked like pressing Delete would delete the cluster (as in, destroy it), while the actual behaviour and intention is to just remove it from the view.
The message and button should be changed into something clearer and unambiguous. For example,

Remove {CLUSTER_NAME} (the pop-up title),
Are you sure you want to remove Cluster {CLUSTER_NAME} from the Dashboard? (the message), and
Remove (the button).

Kyma Dashboard version: PR 1369
Expected result
The message and button is clear and unambiguous. For example,

Remove {CLUSTER_NAME} (the pop-up title),
Are you sure you want to remove Cluster {CLUSTER_NAME} from the Dashboard? (the message), and
Remove (the button).

Actual result
The message suggests that pressing Delete would delete the cluster (as in, destroy it), while the actual behaviour and intention is to just remove it from the view.
Steps to reproduce

Open a Kyma Dashboard and navigate to Clusters Overview.
Connect a cluster (if not already connected).
Click the trash can button to remove the cluster from the Dashboard.
Read the message in the pop-up window.*

*If you previously checked the Don't ask again box, this box might not appear for you.

@grego952 feel free to pick this anytime. This is for the moment mostly a text description topic

@valentinvieriu that's what I thought too, but it requires some distinction in the code between remove and delete so I think one of the devs should take a look at it first.

@valentinvieriu , @majakurcius , should we reopen this issue? The stalebot closed it and I don't see any results provided


Feat: sno leader election config

Leader election in SNO clusters have limited resources where requests can put un-needed pressure on the kube-apiserver. This PR increases the retry period and lease duration on leader election and exposes some helper functions to determine topology and SNO leader election defaults, on operator start up.

To give a bit more context. Some of the numbers I was seeing are pasted below along with the queries ran against prometheus. The methodology was to create two 4.9 SNO-DU clusters (leader-election-new and leader-election-oc), both had CVO scaled down, and the only modification was that leader-election-new was running 11 operators that were rebuilt with the modified library-go running with the new leader-election numbers. I was seeing some small reductions, so I figured if we extrapolate that to the rest of the core operators we would see better gains in SNO-DU clusters, where we have very limited resources (currently management workloads are pinned to 2 cores).
Things I tried to verify was the downtime support for APIServer in SNO clusters described in this bz, rolling out APIServer didn't cause any restarts on the operators. Similarly rolling out the operator didn't cause any restarts and the operands behaved correctly with out any restarts as well.
Queries Ran
95th Quantile Over Time (CPU Usage) - API Server

Unchanged
Changed
Delta

478.90296182259607
462.6560489574072
-3.39

quantile_over_time(
  .95,
  sum(
    rate(container_cpu_usage_seconds_total{
      container!="POD",
      pod=~"kube-apiserver-leader-election-oc-49|kube-apiserver-leader-election-new-49",
      namespace="openshift-kube-apiserver"}[5m]
    )
  )[6h:]
) * 1000

Average Over Time (CPU Usage) - API Server

Unchanged
Changed
Delta

429.08792083196755
395.3039245479713
-7.87

avg_over_time(
  sum(
    rate(container_cpu_usage_seconds_total{
      container!="POD",
      pod=~"kube-apiserver-leader-election-oc-49|kube-apiserver-leader-election-new-49",
      namespace="openshift-kube-apiserver"}[5m]
    )
  )[6h:]
) * 1000

95th Quantile Over Time (CPU Usage) - Operators

Unchanged
Changed
Delta

192.51093951592614
174.9938822722223
-9.10

quantile_over_time(
  .95,
  sum(
    rate(container_cpu_usage_seconds_total{
      container!="POD",
      namespace=~"openshift-apiserver-operator|openshift-authentication-operator|openshift-cluster-storage-operator|openshift-console-operator|openshift-controller-manager-operator|openshift-etcd-operator|openshift-kube-apiserver-operator|openshift-kube-controller-manager-operator|openshift-kube-scheduler-operator|openshift-kube-storage-version-migrator-operator|openshift-service-ca-operator"
      }[5m]
    )
  )[6h:]
) * 1000

Average Over Time (CPU Usage) - Operators

Unchanged
Changed
Delta

173.11949276437636
159.50446507412303
-7.86

avg_over_time(
  sum(
    rate(container_cpu_usage_seconds_total{
      container!="POD",
      namespace=~"openshift-apiserver-operator|openshift-authentication-operator|openshift-cluster-storage-operator|openshift-console-operator|openshift-controller-manager-operator|openshift-etcd-operator|openshift-kube-apiserver-operator|openshift-kube-controller-manager-operator|openshift-kube-scheduler-operator|openshift-kube-storage-version-migrator-operator|openshift-service-ca-operator"
      }[5m]
    )
  )[6h:]
) * 1000

Summarizing the overall benefit to an SNO cluster over X timeframe will be helpful for weighing the tradeoff of slightly lower CPU cost at the expense of latency of lease reacquisition.

Sure thing, a quick summary with some new numbers. I ran the clusters under load. I used kube-burner to spin up some traffic against the API Server and just have some workloads in the cluster. The latest numbers show a pretty consistent picture of a small reduction in CPU consumption by the Changed Operators. On average by increasing leader election to 60s I'm seeing a reduction of 1-2 millicores per operator, extrapolating that to the 30 operators we run we could see 30millicore reduction on on average on the low end and 60millicore on the high end. That is a very small reduction but the gain is meaningful in environments where there is significant reduction in resources. Some DU configurations for example are pinning management workloads to 2 cores. This gives them very little breathing room and any measurable reduction is useful to provide more resources for Crio and Kubelet to operate. This does mean we reduce the responsiveness of our operators during rollouts, but the gain would mean that if need be we can support another operator in those limited environments.
In short, with the current numbers, we would have a worst non-graceful case of 330s before the new operator takes leader and a best graceful case of 60s which would mean a latency in lease reacquisition. The upside is that this would afford resource starved deployments some more breathing room in SNO environments (all be it small), which would offer Kubelet and Crio more room or potentially allow running another operator.
As always with things of this nature, another pair of eyes would be fantastic on the numbers, queries and the methodology. Any input is greatly appreciated.

/test unit

/test unit

/approve
please squash before merge.

diff of diffs is clean https://github.com/openshift/library-go/compare/aa75fd24bdd8b2b1c798a1237bc27364a16bfac0..2612981f3019479805ac8448b997266fc07a236a
/lgtm


How to change Signaling server

Hi Oney the genius,
We have used your react-native-webrtc and successfully running the app in mobiles.
And we have downloaded the signaling server you have provided (https://github.com/oney/react-native-webrtc-server) and started it successfully.
Both are working fine.
Now how to integrate our signaling server in the app.
We have tried changing io.connect('http://react-native-webrtc.herokuapp.com', {transports: ['websocket']}); with io.connect('https://ourip:outport', {transports: ['websocket']});
But it is not working.
Do we need to change anything else.
Do you have any documentation or steps to do that
Thanks in advance.

Your server is using code from https://github.com/oney/react-native-webrtc-server, right?
Can you check socket connection of the app?
var socket = io.connect('http://react-native-webrtc.herokuapp.com', {transports: ['websocket']});
socket.on('connect', (data) => {
  console.log('connect');
});
socket.on('disconnect', (data) => {
  console.log('disconnect');
});
socket.on('reconnect', (data) => {
  console.log('reconnect');
});
socket.on('reconnectAttempt', (data) => {
  console.log('reconnectAttempt');
});
socket.on('error', (data) => {
  console.log('error', data);
});

Give some logs to me.
Make sure your https is working.

Thank you for your quick response.
Yes i have used the same code. And it is working in https. And i have tested it in browser using my local url (https://<IP_ADDRESS>:4443) as well. It is working fine.
And in (Android) App If i use var socket = io.connect('http://react-native-webrtc.herokuapp.com', {transports: ['websocket']}); in my app it is working fine.
But if i change it to var socket = io.connect('https://<IP_ADDRESS>:4443', {transports: ['websocket']}); it shows only 'Initializing' with black video screen in the App.
I debug the code and put some logs and i found that in connect method of socket.io.js gives
'Error: websocket error' in line no 4564

Please just use
var socket = io.connect('https://<IP_ADDRESS>:4443');

Thank you very much for your support.
But if i try like that. It gives different error  Error: xhr poll error
And i googled it and seen people are suggesting to set process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0"; OR rejectUnauthorized: false. But i dont know where to set.
Is that right?
Can you please help me to fix this xhr poll error

I believe this is about socket.io rather than react-native-webrtc.
Please go https://github.com/oney/react-native-webrtc-server/issues to open new issue, I am pleased to give some helps.


Windows: Closing development leaves phantom processes

Original Discussion: https://www.pika.dev/npm/snowpack/discuss/295
/cc @Ciantic, @FredKSchott
Tracked it down to readline not properly triggering execa cleanup.
@Ciantic if we can't get execa's automatic cleanup triggering, we can try to connect our own exit listener to call .kill() on the execa processes manually.

I opened an issue to here https://github.com/sindresorhus/execa/issues/429 with my smaller repro.

@Ciantic any luck? I'm going to go ahead and close this since we are no longer doing any capturing of SIGKILL commands or the like that could be causing this on our end. If there is an issue here, then it's inside of execa, and hopefully they're able to reproduce and fix.

I will try to reproduce this again. But last with tests I was able to reproduce this in Windows 10 Virtual Machine, so it did definitely exist, and it was reproducible most of the time.
I actually switched using WSL (Linux Environment) because of this, so I didn't dig any deeper.


MM-38366 - trial started carousel benefits modal

Summary
This PR adds improvements to the start trial modal by showing another modal with all the benefits once the user clicks the option to start the trial.

Pending unit tests to benefits modal and carousel component.

Ticket Link
https://mattermost.atlassian.net/browse/MM-38366
Related Pull Requests
https://github.com/mattermost/mattermost-webapp/pull/9149
Screenshots
https://user-images.githubusercontent.com/10082627/137567608-b44ee066-34cb-4f1d-9acb-c04bff9211ce.mp4
Release Note
NONE

Not urgent - what would be the best place for me to try it out? I tried the above test server, but it's for a Cloud environment instead of Self-Hosted?

This should work with the Setup Cloud Test Server tag (instead of the CWS one)

Looks like we haven't yet added the "Learn More" CTA in the main menu, is that coming in a separate PR?

https://www.figma.com/file/E2sh7Ny5wlyDhqpgbwowxm/Enterprise-changes?node-id=0%3A1

hey @jasonblais , yes, it is implemented as part as this change, but there is a problem with the current implementation. I will push asap a fix for it, I have already a fix for it locally.

Error trying doing the automated Cherry picking. Please do this manually
+++ Updating remotes...
Fetching upstream
Failed to add the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts (/app/.ssh/known_hosts).
From github.com:mattermost/mattermost-webapp
   541d698e1..2f5ae13d7  MM-38091               -> upstream/MM-38091
 * [new branch]          MM-38366-trial-started-carousel-modal-final-validation -> upstream/MM-38366-trial-started-carousel-modal-final-validation
 * [new branch]          MM-38941_tutorial-tip-punchouts -> upstream/MM-38941_tutorial-tip-punchouts
   686f766a3..9f9ca11ca  MM-38972-luxon-i18n-defaults -> upstream/MM-38972-luxon-i18n-defaults
   bb90fd3b6..2667bab39  MM-39292_actions-to-ts -> upstream/MM-39292_actions-to-ts
   12c4f66f1..933638e18  cloud                  -> upstream/cloud
 * [new branch]          fix-playbooks-link     -> upstream/fix-playbooks-link
   b7181337e..474cd7eb1  master                 -> upstream/master
   9ae569195..72985f075  release-5.37           -> upstream/release-5.37
   b479e0b33..1f83feaab  release-5.38           -> upstream/release-5.38
   783f6a2e3..40812fc4d  release-5.39           -> upstream/release-5.39
   34861f3da..4695d1a54  release-6.0            -> upstream/release-6.0
   d8c1022d9..49a11dd6c  team-sidebar-in-products -> upstream/team-sidebar-in-products
   94e3922ba..65df69542  updated-tutorial-for-gh -> upstream/updated-tutorial-for-gh
Fetching origin
Failed to add the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts (/app/.ssh/known_hosts).
+++ Updating remotes done...
!!! 'upstream/release-6.1' not found. The second argument should be something like upstream/release-0.21.
    (In particular, it needs to be a valid, existing remote branch that I can 'git checkout'.)

+++ Returning you to the master branch and cleaning up.

/cherry-pick cloud


Add nightly deps workflow

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%.  Consider uploading reports for the commit 5ea2964 to get more accurate results

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #50   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           34        34
  Lines          669       669
  Branches        47        47
=========================================
  Hits           669       669

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Switching workspaces via Openbox keybindings leads to missed X events

First of all, thank you for your work on cortile! This is an excellent addition to classic WMs like Openbox and Xfwm.
Unfortunately, I'm experiencing frequent hiccups on my setup that can mostly be attributed to cortile not receiving all events from the X connection occasionally. I'm running LXQt with Openbox on NixOS using a multi-monitor setup with 2 monitors.
The issue happens when switching workspaces via Openbox's keybindings. Sometimes (roughly every 5~10 switches), cortile does not register the workspace change. This leads to all kinds of glitches because cortile doesn't update its internal state properly, so cycling the tiling mode applies to the wrong workspace, windows not snapping back into position etc.
While trying to identify the problem I added more log output to cortile at places where X events are initially received and processed. I noticed that occasionally some events are never received by cortile at all, for example the _NET_CURRENT_DESKTOP property change from the root window when changing the workspace.
At first I thought it was about my picom config and all the stuff going on (fade animation, blur) that choked the X connection and event queue somehow but then I noticed it doesn't happen when changing the workspace via external means (wmctrl or the workspace switcher of the LXQt panel) instead of Openbox's keybindings. See the reproduction steps below.
For the time being I can resort to wmctrl and other external means for workspace switching but it would be great to get to the bottom of this and fully support Openbox's native behavior.
Unfortunately, I have no clue yet why this is happening at all. Since the workspace indicator of LXQt's panel keeps updating correctly everytime (it also listens to the same X events afaik) it does not seem like the X events are not emitted in general, just that cortile doesn't receive them occasionally when they originate from Openbox keybinding actions.
How to reproduce
Consider the following Openbox keybindings:
<keybind key="A-1">
  <action name="GoToDesktop">
    <to>1</to>
  </action>
</keybind>
<keybind key="A-2">
  <action name="GoToDesktop">
    <to>2</to>
  </action>
</keybind>
<keybind key="A-Escape">
  <action name="GoToDesktop">
    <to>last</to>
  </action>
</keybind>

To reproduce:

Switch to the second workspace and change the tiling layout in cortile so that the tray icon displays a different layout than on workspace 1.
Continuously switch between workspace 1 and 2 by either alternating between Alt+1 and Alt+2 keypresses or repeatedly press Alt+Escape to switch back and forth.

Eventually, cortile will miss events which is visible by the tray icon not updating the layout indicator after changing the workspace. For example, if workspace 2 was set to maximized and the keypress switched to workspace 1, the icon will keep displaying the maximized layout.
Now in contrast, binding Alt+1 and Alt+2 outside of Openbox (e.g. via LXQt's hotkey handler) to wmctrl -s 0 and wmctrl -s 1 respectively or using the scroll wheel on the workspace indicator of the LXQt panel to continuously switch workspaces back and forth does not seem to trigger the issue at all.

Thanks for your efforts and detailed description, nailing the problem down:

I noticed that occasionally some events are never received by cortile at all, for example the _NET_CURRENT_DESKTOP property change from the root window when changing the workspace.

At first I thought it was about my picom config and all the stuff going on (fade animation, blur) that choked the X connection and event queue somehow but then I noticed it doesn't happen when changing the workspace via external means (wmctrl or the workspace switcher of the LXQt panel) instead of Openbox's keybindings.

This could be an upstream issue, that can only be fixed in the xgb or xgbutil library which cortile relies on.
Trying to reproduce this bug on an environment will cost me some time, so I would kindly ask you to run the minimal example below to confirm that this is caused by xgb dependencies.

minimal example
main.go
Please build via go build main.go and run the binary.
package main

import (
	"fmt"

	"github.com/BurntSushi/xgb/xproto"

	"github.com/BurntSushi/xgbutil"
	"github.com/BurntSushi/xgbutil/ewmh"
	"github.com/BurntSushi/xgbutil/xevent"
	"github.com/BurntSushi/xgbutil/xprop"
	"github.com/BurntSushi/xgbutil/xwindow"
)

func main() {
	X, err := xgbutil.NewConn()
	if err != nil {
		fmt.Println("Connection to X server failed")
		return
	}

	root := xwindow.New(X, X.RootWin())
	root.Listen(xproto.EventMaskSubstructureNotify | xproto.EventMaskPropertyChange)

	fmt.Println("Listen")

	xevent.PropertyNotifyFun(StateUpdate).Connect(X, root.Id)
	xevent.Main(X)
}

func StateUpdate(X *xgbutil.XUtil, e xevent.PropertyNotifyEvent) {
	aname, err := xprop.AtomName(X, e.Atom)

	fmt.Println(aname)

	if err != nil {
		fmt.Println("Error retrieving atom name")
		return
	}

	if IsInList(aname, []string{"_NET_CURRENT_DESKTOP"}) {
		fmt.Println("--------- _NET_CURRENT_DESKTOP --------->", CurrentDesktopGet(X))
	}
}

func IsInList(item string, items []string) bool {
	for i := 0; i < len(items); i++ {
		if items[i] == item {
			return true
		}
	}
	return false
}

func CurrentDesktopGet(X *xgbutil.XUtil) uint {
	currentDesk, err := ewmh.CurrentDesktopGet(X)

	if err != nil {
		fmt.Println("Error retrieving current desktop")
	}

	return currentDesk
}

While trying to identify the problem I added more log output to cortile at places where X events are initially received and processed.

The minimal example should include the cortile implementations (root.go) you mentioned, where the issue original arises.
Please let me know, if the --------- _NET_CURRENT_DESKTOP ---------> output still reports the wrong (previous) workspace. It may be some race condition where _NET_CURRENT_DESKTOP fires, but ewmh.CurrentDesktopGet(X)  still reports the old state.

Thanks for creating the minimal example! I tried it and running it at the same time as cortile, I cannot reproduce the issue in the minimal example whereas it keeps happening in cortile.
As a next step I added the code below to the example to include event listener callbacks for all clients/windows mimicking what cortile does. I thought that maybe having a lot of listeners to different X clients in a single program might be the reason for the issues.
But even with the code shown below added, the example still registers each and every workspace change correctly while at the same time cortile frequently fails to do so. The root cause must be something else ...

code patch for attaching client handlers in the minimal example
@@ -25,9 +25,42 @@ func main() {
fmt.Println("Listen")

xevent.PropertyNotifyFun(StateUpdate).Connect(X, root.Id)
+    windows, err := ewmh.ClientListStackingGet(X)
+    if err != nil {
+		fmt.Println("Error retrieving client list: ", err)
+	}
+    for _, win := range windows {
+        fmt.Println("attaching window handlers")
+        attachClientHandlers(X, xwindow.New(X, win))
+    }
xevent.Main(X)
}

+func attachClientHandlers(X *xgbutil.XUtil, c *xwindow.Window) {
+	c.Listen(xproto.EventMaskStructureNotify | xproto.EventMaskPropertyChange | xproto.EventMaskFocusChange)
+
+	// Attach structure events
+	xevent.ConfigureNotifyFun(func(x *xgbutil.XUtil, ev xevent.ConfigureNotifyEvent) {
+		fmt.Println("Client structure event")
+	}).Connect(X, c.Id)
+
+	// Attach property events
+	xevent.PropertyNotifyFun(func(x *xgbutil.XUtil, ev xevent.PropertyNotifyEvent) {
+		aname, _ := xprop.AtomName(X, ev.Atom)
+		fmt.Println("Client property event ", aname)
+	}).Connect(X, c.Id)
+
+	// Attach focus in events
+	xevent.FocusInFun(func(x *xgbutil.XUtil, ev xevent.FocusInEvent) {
+		fmt.Println("Client focus in event")
+	}).Connect(X, c.Id)
+
+	// Attach focus out events
+	xevent.FocusOutFun(func(x *xgbutil.XUtil, ev xevent.FocusOutEvent) {
+		fmt.Println("Client focus out event")
+	}).Connect(X, c.Id)
+}
+
func StateUpdate(X *xgbutil.XUtil, e xevent.PropertyNotifyEvent) {
aname, err := xprop.AtomName(X, e.Atom)

But even with the code shown below added, the example still registers each and every workspace change correctly while at the same time cortile frequently fails to do so. The root cause must be something else ...

...just a guess in the dark, please uncomment those 4 lines and report back:
https://github.com/leukipp/cortile/blob/main/input/mousebinding.go#L50-L53

Please also try the version from the xgb-jezek branch, where github.com/BurntSushi/xgb* is replaced with the github.com/jezek/xgb* fork, which provides those features:

I've forked the XGB repository from BurntSushi's github to apply some
patches which caused panics and memory leaks upon close and tests were added,
to test multiple server close scenarios.

Much of the code has been rewritten in an effort to support thread safety and multiple extensions.

It is thread safe and gets immediate improvement from parallelism when
GOMAXPROCS > 1. (See the benchmarks in xproto/xproto_test.go for evidence.)

But even with the code shown below added, the example still registers each and every workspace change correctly while at the same time cortile frequently fails to do so. The root cause must be something else ...

...just a guess in the dark, please comment those 4 lines and report back: https://github.com/leukipp/cortile/blob/main/input/mousebinding.go#L50-L53

That's it! After commenting those lines I cannot reproduce the issue anymore.

Please also try the version from the xgb-jezek branch [...]

No difference to the main branch's behavior in terms of the issue observed.

Thanks for your feedback! A proper fix will be included in the next cortile release.

The fix is included in v2.5.0.


Add measure for gpu power draw

You want to make a PR to Talos
Thanks so much :) First, please take a moment to carefully check through
the below items:
Sanity

[ ] I'm aware of the implications of the proposed changes
[ ] Code is PEP8
[ ] I'm making the PR to master

Docs

[ ] Docs are updated
[ ] Docs version is correct (index.html and _coverpage.md)

Tests

[ ] Changes have gone through actual use testing
[ ] All local tests have passed (run ./test.sh in /talos)
[ ] Tests have been updated to reflect the changes

Hello @mikkokotila! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file talos/utils/power_draw_append.py:

Line 15:80: E501 line too long (81 > 79 characters)

In the file talos/utils/power_draw_callback.py:

Line 27:80: E501 line too long (95 > 79 characters)


⚠ Bofrost.com has degraded performance

In 3ed1c7a, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 934 ms

Resolved: Bofrost.com performance has improved in d80efb0 after 6 minutes.


[Wait for #2221][Application] YOLOv3 implementation for forwarding in torch @open sesame 06/13 14:50

Added YOLO v3 pytorch implementation for forwarding in pytorch.
Signed-off-by: Seungbaek Hong<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2222. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

We generate a report if there are dangerous coding constructs in your code. Please read http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2222-202306081541410.23918700218201-90ef88dc26a86cf5aa8ab58ef6cc7f4c4f99b631/report/pylint_result.txt.

:octocat: cibot: @baek2sm, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2222-202306081541410.23918700218201-90ef88dc26a86cf5aa8ab58ef6cc7f4c4f99b631/.

We generate a report if there are dangerous coding constructs in your code. Please read http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2222-202306131449540.014975070953369-90ef88dc26a86cf5aa8ab58ef6cc7f4c4f99b631/report/pylint_result.txt.

:octocat: cibot: @baek2sm, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2222-202306131449540.014975070953369-90ef88dc26a86cf5aa8ab58ef6cc7f4c4f99b631/.

please git rebase yolov3_dknet53_torch https://github.com/nnstreamer/nntrainer/pull/2217 , thank you.

We generate a report if there are dangerous coding constructs in your code. Please read http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2222-202306161818370.7328929901123-2a55cd4f7c5164f87ece3b1a058e169bfd24f27e/report/pylint_result.txt.

We generate a report if there are dangerous coding constructs in your code. Please read http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2222-202309131057440.64405202865601-ad3e5beedd9f5c417f58a457643d1e214947afd9/report/pylint_result.txt.

:octocat: cibot: @baek2sm, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2222-202309131057440.64405202865601-ad3e5beedd9f5c417f58a457643d1e214947afd9/.

We generate a report if there are dangerous coding constructs in your code. Please read http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2222-202309131910430.49766111373901-ab555d641e9f004a734ecb6bec8ea3aa930f6061/report/pylint_result.txt.

:octocat: cibot: @baek2sm, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2222-202309131910430.49766111373901-ab555d641e9f004a734ecb6bec8ea3aa930f6061/.

We generate a report if there are dangerous coding constructs in your code. Please read http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2222-202309141400010.33766007423401-ab555d641e9f004a734ecb6bec8ea3aa930f6061/report/pylint_result.txt.

It is already merged by #2229


Default baseline sources per chain

This PR adds default baseline sources per chain, using all supported sources.
Test Plan
Try out some commands:
$ cargo run -p solver -- --node-url https://mainnet.infura.io/v3/$INFURA_PROJECT_ID
...
2021-11-18T09:44:03.730Z  INFO solver: using baseline sources baseline_sources=[UniswapV2, SushiSwap, BalancerV2]
...
$ cargo run -p solver -- --node-url https://rpc.xdaichain.com
...
2021-11-18T09:44:35.165Z  INFO solver: using baseline sources baseline_sources=[Honeyswap, SushiSwap]
...
$ cargo run -p solver -- --node-url https://mainnet.infura.io/v3/$INFURA_PROJECT_ID --baseline-sources SushiSwap
...
2021-11-18T09:45:09.981Z  INFO solver: using baseline sources baseline_sources=[SushiSwap]
...

Codecov Report

Merging #1404 (53ac2a5) into separate-uniswap-like-protocols (b3aea6d) will decrease coverage by 0.05%.
The diff coverage is 0.00%.

@@                         Coverage Diff                         @@
##           separate-uniswap-like-protocols    #1404      +/-   ##
===================================================================
- Coverage                            66.38%   66.33%   -0.06%
===================================================================
  Files                                  150      150
  Lines                                29943    29962      +19
===================================================================
- Hits                                 19879    19876       -3
- Misses                               10064    10086      +22


Add support for a translation context

Yeah, we haven't added that, though I suspect it can follow a similar pattern to how we're doing comments.
So probably a sketch of supporting this would be:

Define another HTML comment directive to let authors specify the ctxt, similar to what we're doing here

Collect and thread that state when we're gathering groups for translation.

Finally, pass the ctxt here and call the builder method for setting the ctxt.

So I think this would be fairly straightforward extension.
Originally posted by @dyoo in https://github.com/google/comprehensive-rust/pull/1973#discussion_r1563132168

This is about adding support for the translation context.

I am planning to work on this feature, assigned to myself.


Cannot find RobotPlanarGraph

In simple_ik_examples/test_chain_2d_limits_new.py
we have:
from graphik.graphs.graph_base import RobotPlanarGraph
However graphik.graphs.graph_base does not contain a RobotPlanarGraph object or function

Thanks for pointing this out, I will take a look later this week!

It should work now.


Facebook Share Doesn't Set Title Correctly

Facebook has changed how Sharer.php works. [It no longer accepts detailed parameters](no longer accept detailed parameters?).
However, the template stills sets the title and content. This gives users the impression that the template isn't working correctly.
To resolve this, either:

Switch to Facebook's feed dialog way of sharing to Facebook. This might include the requirement to obtain an App ID from Facebook.
Remove the expectation that the template can set the title.

See also: https://developerscorner.storymaps.arcgis.com/how-to-fix-facebook-sharing-6df958944a1c

The issue described in the blog post https://developerscorner.storymaps.arcgis.com/how-to-fix-facebook-sharing-6df958944a1c has now been fixed in this repo. See release 1.4.9.
For existing deployed Shortlists that have the issue just see the blog post above for how to simply apply the fix to your Shortlist without downloading 1.4.9.


Fix bug where Pause/Break key scancode is converted to Ctrl-NumLock.

https://wiki.osdev.org/PS/2_Keyboard#Scan_Code_Set_1
https://wiki.osdev.org/PS/2_Keyboard#Scan_Code_Set_2
Scancode Set 1:

Pause/Break

0xE1 0x14 0x77 0xE1 0xF0 0x14 0xF0 0x77

LeftCtrl (Pressed)

0x14

NumLock (Pressed)

0x77

LeftCtrl (Released)

0xF0 0x14

NumLock (Released)

0xF0 0x77

LeftCtrl-NumLock (Pressed)

0x14 0x77

LeftCtrl-NumLock (Released)

0xF0 0x14 0xF0 0x77 0x14 0x77

It appears Zeal is interpreting Pause/Break as Ctrl-NumLock because of either the starting three bytes matching LeftCtrl-NumLock Pressed, or the latter four bytes matching LeftCtrl-NumLock Released. Though the specific bytes are different for Scan Code 1, both sets have matching byte values in the scancodes like this for these keys. The only distinguishing factor is that the isolated Pause/Break code starts with 0xE1 and divides the duplicates via another 0xE1. The code that processes 0xE1 bytes in the keyboard driver scan code parsing/scancode-to-keyname logic may need to be reviewed

https://github.com/Zeal-Operating-System/ZealOS/blob/master/src/Kernel/SerialDev/Keyboard.ZC
See:

ScanCode2Char
ScanCode2KeyName
KbdBuildSC
KbdPacketRead
KbdHandler

From the OSDev Wiki link above:

Note that scancodes with extended byte (E0) generates two different interrupts: the first containing the E0 byte, the second containing the scancode

The mentioned functions have different mechanisms for handling this 0xE0 "extended byte", but the odd 0xE1 of Pause/Break is likely being dropped/skipped/incorrectly matched, and the rest of its bytes matching up to the next closest scancode. An additional integration for factoring in the Pause/Break scancode similar to how 0xE0 bytes are handled may be needed to resolve this bug


Support using custom versions of templates

For PXBLUE-1920
Fixes #73

Changes proposed in this Pull Request:

Fix the expo logic to work with the latest expo version
Add --alpha and --beta template support
Add support for using local file versions of templates
Update the docs (order of steps has changed slightly also)

NOTE: This is only for Angular, React, and React Native. We will need to add this behavior when we implement the Ionic templates, since there is nothing in here for Ionic templates yet.

I've tested out these changes with --alpha tags for a react and angular project; do we have any templates that have a beta release?
Both tests ran just fine & I'm happy with the error received when a missing version was requested.

I've tested out these changes with --alpha tags for a react and angular project; do we have any templates that have a beta release?

Looks like no on the betas (I thought we had one, but I just looked at them all and didn't see one). The --alpha and --beta work exactly the same way though, so you can reasonably assume that if the code looks good, it will work. It should also crash out (maybe?) nicely if you request beta and the version does not exist like below.

Both tests ran just fine & I'm happy with the error received when a missing version was requested.
Nice! I didn't check that, so glad it works as expected.

same here seems to be good. I went through react, react native and one angular.  error is good
*Error: Command failed: set npm_config_yes=true  && npx create-react-app reactalpha --template<EMAIL_ADDRESS>npx: installed 67 in 5.961s
error Couldn't find any versions for "@pxblue/cra-template-authentication-typescript" that matches "1.0.0-alpha.5"


Feature:  Want to add a feature to go on home page when Click on Recode Hive logo

Is your feature request related to a problem? Please describe.
When user will click on the logo so the user must route to the home page

https://recodehive.com/
redirect them to here: https://recodehive.com/github-tutorials/


Update README.md

It is wrong word, It leads to a type error: limiter.hasTokensSync is not a function.

Thanks a lot!


fix(userspace): resolve some alerts generated by the Falco CodeQL job

Signed-off-by: Andrea Terzolo<EMAIL_ADDRESS>What type of PR is this?
/kind bug
/kind cleanup
Any specific area of the project related to this PR?
/area libscap
Does this PR require a change in the driver versions?
No
What this PR does / why we need it:
This PR should solve some issues highlighted by the CodeQL job in Falco:

https://github.com/falcosecurity/falco/security/code-scanning/18
https://github.com/falcosecurity/falco/security/code-scanning/19

Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/milestone 0.10.0

cc @LucaGuerra

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,LucaGuerra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: c3f5a4eb9eb43f3dc5e5b79bce91370b86bddb15

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, LucaGuerra
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,LucaGuerra]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Enhance error message descriptions

Verbose error messages are useful in tracking down bugs in production. While some try/except blocks return details, others do not. For those cases where it does not, it would be good to add logging that goes to the server logs to aid debugging. Specifically, a line like traceback.print_exc() should be added before returning HTTPExceptions. I believe these lines all need such a treatment:
https://github.com/paradimdata/project_chameleon/blob/39195b1e3869bd13cbfdf36b6568d4364ee07c43/api.py#L89
https://github.com/paradimdata/project_chameleon/blob/39195b1e3869bd13cbfdf36b6568d4364ee07c43/api.py#L365
https://github.com/paradimdata/project_chameleon/blob/39195b1e3869bd13cbfdf36b6568d4364ee07c43/api.py#L384
https://github.com/paradimdata/project_chameleon/blob/39195b1e3869bd13cbfdf36b6568d4364ee07c43/api.py#L402
https://github.com/paradimdata/project_chameleon/blob/39195b1e3869bd13cbfdf36b6568d4364ee07c43/api.py#L421
https://github.com/paradimdata/project_chameleon/blob/39195b1e3869bd13cbfdf36b6568d4364ee07c43/api.py#L440
https://github.com/paradimdata/project_chameleon/blob/39195b1e3869bd13cbfdf36b6568d4364ee07c43/api.py#L464
https://github.com/paradimdata/project_chameleon/blob/39195b1e3869bd13cbfdf36b6568d4364ee07c43/api.py#L482
https://github.com/paradimdata/project_chameleon/blob/39195b1e3869bd13cbfdf36b6568d4364ee07c43/api.py#L500
https://github.com/paradimdata/project_chameleon/blob/39195b1e3869bd13cbfdf36b6568d4364ee07c43/api.py#L519
https://github.com/paradimdata/project_chameleon/blob/39195b1e3869bd13cbfdf36b6568d4364ee07c43/api.py#L565
Thank you!

Added traceback.print_exc() to all the lines given. Also added more descriptive error messages.


Start zsh 5.0 branch

Fail loading zim if zsh version < 5.0.
Also fix git-info failing in zsh 5.0.8 as reported in #176 and #177.

@Eriner, this finishes the discussion in #184.

LGTM :+1:

Merged into 12e4ee2


Add reStructedText support and fix readme render bug

should be part of #374, see below screenshots.

Codecov Report

Merging #2564 into master will increase coverage by <.01%.
The diff coverage is 33.33%.

@@            Coverage Diff             @@
##           master    #2564      +/-   ##
==========================================
+ Coverage   27.07%   27.08%   +<.01%
==========================================
  Files          86       87       +1
  Lines       17119    17137      +18
==========================================
+ Hits         4635     4641       +6
- Misses      11809    11821      +12
  Partials      675      675

Impacted Files
Coverage Δ

modules/markup/orgmode/orgmode.go
90.9% <ø> (ø)
:arrow_up:

...odules/markup/reStructuredText/reStructuredText.go
33.33% <33.33%> (ø)

Continue to review full report at Codecov.

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

Tests added and rebased.

LGTM

@lafriks LGTM seems not to work

@Morlinest all done.

@ethantkoenig Yes, but this is the most mature library I can find. Also, if #2570 could be merged, external tool could override internal library.

@ethantkoenig I don't mind to put this PR later. If #2570 could be merged, it also resolved #374.

And maybe https://github.com/demizer/go-rst is a better choice.

@lunny go-rst is marked as ABANDONED. I think with #374 closed this could also be closed.


Exception when using the buildShortAppLinking

_AGCAppLinking.buildLongAppLinking works fine.
AGCAppLinking.buildShortAppLinking builder throws the ff. error
E/AGCAppLinkingException(27918): (PluginException) UNKNOWN: url is null

Please check your agconnect-services.json file. Make sure you have selected your storage location in the portal and redownload this file. Also, make sure it is in the right place.

Please check your agconnect-services.json file. Make sure you have selected your storage location in the portal and redownload this file. Also, make sure it is in the right place.

Solution was NOT the agconnect-services.json file.
solution was adding a whitelist url in the app gallery app linking api.


it get errors when i test

File "/home/nfs/admin0/chenguang/project/RepPoints/mmdetection/build/lib.linux-x86_64-3.7/mmdet/ops/dcn/deform_conv.py", line 55, in forward
cur_im2col_step)
RuntimeError: input image is smaller than kernel (shape_check at mmdet/ops/dcn/src/deform_conv_cuda.cpp:127)
deform_conv_cuda.cpp:127
AT_CHECK((inputHeight >= kH && inputWidth >= kW),
"input image is smaller than kernel");
Thanks for help me !!!!

I had a similar error while training for some specific images:
RuntimeError: input image is smaller than kernel (shape_check at mmdet/ops/dcn/src/deform_conv_cuda.cpp:127)

This might help you: https://github.com/open-mmlab/mmdetection/issues/1453
The explanation is given here: open-mmlab/mmdetection#1453 (comment)


Use ed25519 for SSH keys

Code: https://github.com/QPod/lab-dev/blob/main/docker_devbox/work/start--pre.sh#L5
Change to: ssh-keygen -t ed25519 -N "" -C hostname -f -f ~/.ssh/id_ed25519
ref: https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key

Fixed in https://github.com/QPod/lab-dev/pull/31


No "direct" option for InfluxDB connection in Grafana

I create using:
docker run -d --name docker-influxdb-grafana -p <IP_ADDRESS>:3003:3003 -p <IP_ADDRESS>:8083:8083 -p <IP_ADDRESS>:8086:8086 -v /home/homeassistant/influxdb:/var/lib/influxdb -v /home/homeassistant/grafana:/var/lib/grafana philhawthorne/docker-influxdb-grafana:edge

(I changed port 3004, surely makes no difference)
In Grafana's Add Source for InfluxDB, there are choices of "Server" and "Browser" no "Direct" as per docs. Neither option works, both produce an error on "Save and Test"

Looks like this has changed and you should use "Server (default)"
For the URL, enter http://localhost:8086 and that should work
On Thu, Aug 18, 2022 at 2:40 AM Niall Douglas @.***>
wrote:

I create using:
docker run -d --name docker-influxdb-grafana -p <IP_ADDRESS>:3003:3003 -p <IP_ADDRESS>:8083:8083 -p <IP_ADDRESS>:8086:8086 -v /home/homeassistant/influxdb:/var/lib/influxdb -v /home/homeassistant/grafana:/var/lib/grafana philhawthorne/docker-influxdb-grafana:edge
(I changed port 3004, surely makes no difference)
In Grafana's Add Source for InfluxDB, there are choices of "Server" and
"Browser" no "Direct" as per docs. Neither option works, both produce an
error on "Save and Test"
—
Reply to this email directly, view it on GitHub
https://github.com/philhawthorne/docker-influxdb-grafana/issues/64, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFO7J7RFSWZMTE7IS2OLXLVZUIZTANCNFSM562G3K7A
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I tried that before as well, still an error.
I found that if you go into the InfluxDB Admin page and create a new database, and then specify that database name along with root/root as the credentials to the Grafana Add Source, that works.

Hmm yes that makes sense. When I don't specify the DB name, Grafana complains that there is no database connected.
Instructions probably need to be clearer that a InfluxDB database needs to be created before you can add it to Grafana

I just got everything up and running, pretty time series graphs. I used https://github.com/Jepsson/esphome-influxdb as a custom component for esphome, the microcontroller now sends sensor readings direct to influxdb no home assistant needed. Very nice. Thanks for your work on this, it saved me a bunch of time arsing around getting docker influx and docker grafana etc etc to talk to each other and to have docker store the DB somewhere persistent. I just wanted to get it up and recording on a secure network, I didn't want to have to arse around with anything else probably much better practice in terms of security.


fix(controller): Add missing permissions to create/update configmaps for memoization

These are required to run the memoization example: https://github.com/argoproj/argo-workflows/blob/master/examples/memoize-simple.yaml
time="2021-03-18T14:11:42.810Z" level=info msg="Saving ConfigMap cache entry" key=test-5 name=my-config namespace=argo nodeId=memoized-simple-workflow-6mftb
time="2021-03-18T14:11:42.814Z" level=info msg="Create configmaps 403"
time="2021-03-18T14:11:42.814Z" level=error msg="Failed to save node outputs to cache" error="could not save to config map cache: configmaps is forbidden: User \"system:serviceaccount:argo:argo\" cannot create resource \"configmaps\" in API group \"\" in the namespace \"argo\"" namespace=argo nodeID=memoized-simple-workflow-6mftb workflow=memoized-simple-workflow-6mftb

time="2021-03-18T14:31:01.181Z" level=info msg="Update configmaps 403"
time="2021-03-18T14:31:01.182Z" level=error msg="Failed to save node outputs to cache" error="error creating cache entry: configmaps \"my-config\" is forbidden: User \"system:serviceaccount:argo:argo\" cannot update resource \"configmaps\" in API group \"\" in the namespace \"argo\"" namespace=argo nodeID=memoized-simple-workflow-bqtfb workflow=memoized-simple-workflow-bqtfb

Signed-off-by: terrytangyuan<EMAIL_ADDRESS>Checklist:

[x] My organization is added to USERS.md.

I'm not sure we want this by default. But we should:

Add them to the quick-start manifests.
Document the permissions.

Great suggestion. Updated.


Bug in time_distributed_dense when in tensorflow backend because of set_shape?

Hi,
the code below is:
#encoding=utf-8

import tensorflow as tf
import os
os.environ["KERAS_BACKEND"] = "tensorflow"
from keras import initializations
from keras.models import Model
from keras.layers.recurrent import LSTM, Recurrent, SimpleRNN, time_distributed_dense, GRU
from keras import backend as K

w_c = K.random_normal_variable((2,7), mean=0, scale=1)
x = K.random_normal_variable((1, 2, 2), mean=0, scale=1)
# q = time_distributed_dense(x, w_c, output_dim=7, input_dim=2)
q = time_distributed_dense(x, w_c)

sess = tf.Session()
gini = tf.global_variables_initializer()
sess.run(gini)

qv = sess.run(q)
print(qv.shape)

Error is:
  File "E:/project/learn_test/test.py", line 18, in <module>
    q = time_distributed_dense(x, w_c)
  File "e:\project\keras\keras\layers\recurrent.py", line 52, in time_distributed_dense
    x.set_shape([None, None, output_dim])
  File "D:\Anaconda3\lib\site-packages\tensorflow\python\framework\ops.py", line 419, in set_shape
    self._shape = self._shape.merge_with(shape)
  File "D:\Anaconda3\lib\site-packages\tensorflow\python\framework\tensor_shape.py", line 573, in merge_with
    other = as_shape(other)
  File "D:\Anaconda3\lib\site-packages\tensorflow\python\framework\tensor_shape.py", line 821, in as_shape
    return TensorShape(shape)
  File "D:\Anaconda3\lib\site-packages\tensorflow\python\framework\tensor_shape.py", line 457, in __init__
    self._dims = [as_dimension(d) for d in dims_iter]
  File "D:\Anaconda3\lib\site-packages\tensorflow\python\framework\tensor_shape.py", line 457, in <listcomp>
    self._dims = [as_dimension(d) for d in dims_iter]
  File "D:\Anaconda3\lib\site-packages\tensorflow\python\framework\tensor_shape.py", line 378, in as_dimension
    return Dimension(value)
  File "D:\Anaconda3\lib\site-packages\tensorflow\python\framework\tensor_shape.py", line 33, in __init__
    self._value = int(value)
TypeError: int() argument must be a string, a bytes-like object or a number, not 'Tensor'

But when I set  time_distributed_dense(x, w_c, output_dim=7, input_dim=2), it run ok;
So what's up here? tf.set_shape can't pass tensor or ? Thanks

If you're trying to use the functional API of Keras, you're using the wrong syntax, please refer the docs. Also note that the TimeDistributedDense layer has been deprecated in favour of the TimeDistributed wrapper which can be used to wrap the Dense layer

@abhaikollara Thanks very much
Solved it!


Stack stuck on activating

Rancher Version:
Latest
Docker Version:
1.11.2
OS and where are the hosts located? (cloud, bare metal, etc):
Ubuntu 14.04
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
HA rancher 3 nodes, external db
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Deploy our cluster and we're in activating in the stack listing
Results:
Stack has been stuck on activating for days, and it's fine nothing is wrong...
Expected:
Activated

Here is the api output for the stack:
{
"id": "1e32",
"type": "environment",
"links": {
"self": "…/v1/projects/1a5/environments/1e32",
"account": "…/v1/projects/1a5/environments/1e32/account",
"services": "…/v1/projects/1a5/environments/1e32/services",
"composeConfig": "…/v1/projects/1a5/environments/1e32/composeconfig",
},
"actions": {
"remove": "…/v1/projects/1a5/environments/1e32/?action=remove",
"error": "…/v1/projects/1a5/environments/1e32/?action=error",
"addoutputs": "…/v1/projects/1a5/environments/1e32/?action=addoutputs",
"activateservices": "…/v1/projects/1a5/environments/1e32/?action=activateservices",
"deactivateservices": "…/v1/projects/1a5/environments/1e32/?action=deactivateservices",
"exportconfig": "…/v1/projects/1a5/environments/1e32/?action=exportconfig",
},
"name": "stuff,
"state": "activating",
"accountId": "1a5",
"created": "2016-07-12T00:13:58Z",
"createdTS":<PHONE_NUMBER>000,
"description": null,
"dockerCompose": null,
"environment": null,
"externalId": null,
"healthState": "healthy",
"kind": "environment",
"outputs": null,
"previousEnvironment": null,
"previousExternalId": null,
"rancherCompose": null,
"removed": null,
"startOnCreate": null,
"transitioning": "yes",
"transitioningMessage": "In Progress",
"transitioningProgress": null,
"uuid": "64f3a03b-78a4-48fa-8825-5bff5a214531",
}

Any ideas?

Are all the services green in the stack?
How did you deploy your stack?
Since you're using HA, are there any system services in HA that are having issues?

Hi @deniseschannon , all services are green, deployed the stack using rancher-compose.   All system services look fine in the HA stack.
Sorry for the late reply, was on vacation.

Could you share your docker-compose.yml of your stack so I could try and reproduce?

Wish i could, but a lot of confidential stuff in there.   Ironically, it seems to have sorted itself out... No idea how, as we haven't changed a thing.


Ouflow Threw A Error - HarmonyLib.HarmonyException: Patching exception in method null

https://pastebin.com/uu7Z9yeS

Outflow is deprecated as per Resonite update 2<IP_ADDRESS>5, I just haven't gotten around to archiving this repo yet. Hitches in voice and streamed data when people join a session has been fixed in the main game. Outflow is not longer required.


refactor: remove not null annotations

Checklist

[x] the contributor license agreement is signed
[x] commit message follows commit guidelines
[ ] tests are included
[ ] screenshots are included showing significant UI changes
[ ] documentation is changed or added

Description of change
https://github.com/typescript-eslint/typescript-eslint/blob/master/packages/eslint-plugin/docs/rules/no-non-null-assertion.md

Thanks for the feedback @edalex-ian! :bow:
the code has been updated to ignore the lint errors in cloudcontrol/index.ts and resolve the errors elsewhere.


[Discussion] History / Solved Task Endpoint

Endpoint for already solved and completed tasks, inclusive submissions

Endpoint was introduced lately. UI integration to be defined