Traefik v3 getting SSL handshake errors

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
I was trying to reach any of my ingress routes (or just localhost).
What did you see instead?
When I try to access any of my ingress routes (or just localhost) I get an SSL error like this;
$ curl https://localhost
curl: (35) OpenSSL/3.0.13: error:0A000438:SSL routines::tlsv1 alert internal error

Using the http works fine. I use cert-manager to manage the certificate, and it worked fine before.
What version of Traefik are you using?
Traefik version 3.1.2, Helm chart 30.1.0
What is your environment & configuration?
Traefik app;
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: traefik
  namespace: argocd
spec:
  destination:
    namespace: traefik
    server: 'https://kubernetes.default.svc'
  source:
    repoURL: 'https://traefik.github.io/charts'
    targetRevision: 30.*
    chart: traefik
    helm:
      values: |
        additionalArguments:
          - --providers.kubernetescrd.allowCrossNamespace=true
          - --entrypoints.name.http3
          #- --entryPoints.web.forwardedHeaders.insecure
          #- --log.level=DEBUG
          #- --serverstransport.insecureskipverify=true
        ports:
          web:
            redirectTo:
                port: websecure
        tlsStore:
          default:
            defaultCertificate:
              secretName: wildcard-kreato.dev-tls
  sources: []
  project: default
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
    syncOptions:
      - CreateNamespace=true

Traefik Ingress resource;
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: mirror-ingress
  namespace: nginx
  annotations:
    #traefik.ingress.kubernetes.io/router.entrypoints: web
    #traefik.ingress.kubernetes.io/router.tls: "true"
    cert-manager.io/cluster-issuer: mainissuer

spec:
  rules:
  - host: bin.kreato.dev
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: webserver
            port:
              number: 80
  tls:
    - secretName: wildcard-kreato.dev-tls
      hosts:
        - bin.kreato.dev

If applicable, please paste the log output in DEBUG level
{"level":"error","error":"kubernetesingress cannot be a standalone element (type *cli.ingress)","time":"2024-08-22T05:02:42Z","message":"deprecated static options analysis failed"}                                            2024-08-22T05:02:42Z INF github.com/traefik/traefik/v3/cmd/traefik/traefik.go:101 > Traefik version 3.1.2 built on 2024-08-06T13:37:51Z version=3.1.2
2024-08-22T05:02:42Z DBG github.com/traefik/traefik/v3/cmd/traefik/traefik.go:108 > Static configuration loaded [json] staticConfiguration={"api":{"dashboard":true},"entryPoints":{"metrics":{"address":":9100/tcp","forwardedHeaders":{},"http":{},"http2":{"maxConcurrentStreams":250},"transport":{"lifeCycle":{"graceTimeOut":"10s"},"respondingTimeouts":{"idleTimeout":"3m0s","readTimeout":"1m0s"}},"udp":{"timeout":"3s"}},"name":{"forwardedHeaders":{},"http":{},"http2":{"maxConcurrentStreams":250},"http3":{},"transport":{"lifeCycle":{"graceTimeOut":"10s"},"respondingTimeouts":{"idleTimeout":"3m0s","readTimeout":"1m0s"}},"udp":{"timeout":"3s"}},"traefik":{"address":":9000/tcp","forwardedHeaders":{},"http":{},"http2":{"maxConcurrentStreams":250},"transport":{"lifeCycle":{"graceTimeOut":"10s"},"respondingTimeouts":{"idleTimeout":"3m0s","readTimeout":"1m0s"}},"udp":{"timeout":"3s"}},"web":{"address":":8000/tcp","forwardedHeaders":{},"http":{"redirections":{"entryPoint":{"permanent":true,"priority":9223372036854775806,"scheme":"https","to":":443"}}},"http2":{"maxConcurrentStreams":250},"transport":{"lifeCycle":{"graceTimeOut":"10s"},"respondingTimeouts":{"idleTimeout":"3m0s","readTimeout":"1m0s"}},"udp":{"timeout":"3s"}},"websecure":{"address":":8443/tcp","forwardedHeaders":{},"http":{"tls":{}},"http2":{"maxConcurrentStreams":250},"transport":{"lifeCycle":{"graceTimeOut":"10s"},"respondingTimeouts":{"idleTimeout":"3m0s","readTimeout":"1m0s"}},"udp":{"timeout":"3s"}}},"global":{"checkNewVersion":true,"sendAnonymousUsage":true},"log":{"format":"common","level":"DEBUG"},"metrics":{"prometheus":{"addEntryPointsLabels":true,"addServicesLabels":true,"buckets":[0.1,0.3,1.2,5],"entryPoint":"metrics"}},"ping":{"entryPoint":"traefik","terminatingStatusCode":503},"providers":{"kubernetesCRD":{"allowCrossNamespace":true},"kubernetesIngress":{},"providersThrottleDuration":"2s"},"serversTransport":{"maxIdleConnsPerHost":200},"tcpServersTransport":{"dialKeepAlive":"15s","dialTimeout":"30s"}}
2024-08-22T05:02:42Z INF github.com/traefik/traefik/v3/cmd/traefik/traefik.go:611 > Stats collection is enabled.
2024-08-22T05:02:42Z INF github.com/traefik/traefik/v3/cmd/traefik/traefik.go:612 > Many thanks for contributing to Traefik's improvement by allowing us to receive anonymous information from your configuration.
2024-08-22T05:02:42Z INF github.com/traefik/traefik/v3/cmd/traefik/traefik.go:613 > Help us improve Traefik by leaving this feature on :)
2024-08-22T05:02:42Z INF github.com/traefik/traefik/v3/cmd/traefik/traefik.go:614 > More details on: https://doc.traefik.io/traefik/contributing/data-collection/
2024-08-22T05:02:42Z DBG github.com/traefik/traefik/v3/cmd/traefik/traefik.go:502 > Configured Prometheus metrics metricsProviderName=prometheus
2024-08-22T05:02:42Z INF github.com/traefik/traefik/v3/pkg/server/configurationwatcher.go:73 > Starting provider aggregator aggregator.ProviderAggregator
2024-08-22T05:02:42Z DBG github.com/traefik/traefik/v3/pkg/server/server_entrypoint_tcp.go:228 > Starting TCP Server entryPointName=metrics
2024-08-22T05:02:42Z DBG github.com/traefik/traefik/v3/pkg/server/server_entrypoint_tcp.go:228 > Starting TCP Server entryPointName=name
2024-08-22T05:02:42Z DBG github.com/traefik/traefik/v3/pkg/server/server_entrypoint_tcp.go:228 > Starting TCP Server entryPointName=traefik
2024-08-22T05:02:42Z DBG github.com/traefik/traefik/v3/pkg/server/server_entrypoint_tcp.go:228 > Starting TCP Server entryPointName=websecure
2024-08-22T05:02:42Z DBG github.com/traefik/traefik/v3/pkg/server/server_entrypoint_tcp.go:228 > Starting TCP Server entryPointName=web
2024-08-22T05:02:42Z DBG log/log.go:245 > 2024/08/22 05:02:42 sys_conn.go:36: failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 7168 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details.
2024-08-22T05:02:42Z INF github.com/traefik/traefik/v3/pkg/provider/aggregator/aggregator.go:202 > Starting provider *crd.Provider
2024-08-22T05:02:42Z INF github.com/traefik/traefik/v3/pkg/provider/aggregator/aggregator.go:202 > Starting provider *traefik.Provider
2024-08-22T05:02:42Z DBG github.com/traefik/traefik/v3/pkg/provider/aggregator/aggregator.go:203 > *crd.Provider provider configuration config={"allowCrossNamespace":true}
2024-08-22T05:02:42Z DBG github.com/traefik/traefik/v3/pkg/provider/aggregator/aggregator.go:203 > *traefik.Provider provider configuration config={}
2024-08-22T05:02:42Z INF github.com/traefik/traefik/v3/pkg/provider/kubernetes/crd/kubernetes.go:91 > label selector is: "" providerName=kubernetescrd
2024-08-22T05:02:42Z INF github.com/traefik/traefik/v3/pkg/provider/kubernetes/crd/kubernetes.go:101 > Creating in-cluster Provider client providerName=kubernetescrd
2024-08-22T05:02:42Z INF github.com/traefik/traefik/v3/pkg/provider/aggregator/aggregator.go:202 > Starting provider *ingress.Provider
2024-08-22T05:02:42Z DBG github.com/traefik/traefik/v3/pkg/provider/aggregator/aggregator.go:203 > *ingress.Provider provider configuration config={}
2024-08-22T05:02:42Z INF github.com/traefik/traefik/v3/pkg/provider/kubernetes/ingress/kubernetes.go:94 > ingress label selector is: "" providerName=kubernetes
2024-08-22T05:02:42Z INF github.com/traefik/traefik/v3/pkg/provider/aggregator/aggregator.go:202 > Starting provider *acme.ChallengeTLSALPN
2024-08-22T05:02:42Z INF github.com/traefik/traefik/v3/pkg/provider/kubernetes/ingress/kubernetes.go:104 > Creating in-cluster Provider client providerName=kubernetes
2024-08-22T05:02:42Z DBG github.com/traefik/traefik/v3/pkg/provider/aggregator/aggregator.go:203 > *acme.ChallengeTLSALPN provider configuration config={}
2024-08-22T05:02:42Z DBG github.com/traefik/traefik/v3/pkg/server/configurationwatcher.go:227 > Configuration received config={"http":{"middlewares":{"redirect-web-to-443":{"redirectScheme":{"permanent":true,"port":"443","scheme":"https"}}},"models":{"websecure":{"tls":{}}},"routers":{"ping":{"entryPoints":["traefik"],"priority":9223372036854775807,"rule":"PathPrefix(`/ping`)","ruleSyntax":"v3","service":"ping@internal"},"prometheus":{"entryPoints":["metrics"],"priority":9223372036854775807,"rule":"PathPrefix(`/metrics`)","ruleSyntax":"v3","service":"prometheus@internal"},"web-to-443":{"entryPoints":["web"],"middlewares":["redirect-web-to-443"],"priority":9223372036854775806,"rule":"HostRegexp(`^.+$`)","ruleSyntax":"v3","service":"noop@internal"}},"serversTransports":{"default":{"maxIdleConnsPerHost":200}},"services":{"api":{},"dashboard":{},"noop":{},"ping":{},"prometheus":{}}},"tcp":{"serversTransports":{"default":{"dialKeepAlive":"15s","dialTimeout":"30s"}}},"tls":{},"udp":{}} providerName=internal
2024-08-22T05:02:42Z WRN github.com/traefik/traefik/v3/pkg/provider/kubernetes/crd/kubernetes.go:137 > Cross-namespace reference between IngressRoutes and resources is enabled, please ensure that this is expected (see AllowCrossNamespace option) providerName=kubernetescrd
2024-08-22T05:02:42Z DBG github.com/traefik/traefik/v3/pkg/server/configurationwatcher.go:227 > Configuration received config={"http":{"routers":{"kube-system-traefik-dashboard-d012b7f875133eeab4e5":{"entryPoints":["traefik"],"rule":"PathPrefix(`/dashboard`) || PathPrefix(`/api`)","service":"api@internal"}}},"tcp":{},"tls":{"options":{"default":{"alpnProtocols":["h2","http/1.1","acme-tls/1"],"cipherSuites":["TLS_AES_128_GCM_SHA256","TLS_AES_256_GCM_SHA384","TLS_CHACHA20_POLY1305_SHA256","TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA","TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA","TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA","TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA","TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256","TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384","TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256","TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384","TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256","TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256"],"clientAuth":{},"sniStrict":true}},"stores":{"default":{}}},"udp":{}} providerName=kubernetescrd
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/server/configurationwatcher.go:227 > Configuration received config={"http":{"routers":{"nextcloud-nextcloud-ingress-cloud-kreato-dev":{"rule":"Host(`cloud.kreato.dev`) \u0026\u0026 PathPrefix(`/`)","service":"nextcloud-nextcloud-8080"},"nginx-mirror-ingress-bin-kreato-dev":{"rule":"Host(`bin.kreato.dev`) \u0026\u0026 PathPrefix(`/`)","service":"nginx-webserver-80"},"shrimpkey-shrimpkey-ingress-social-kreato-dev":{"rule":"Host(`social.kreato.dev`) \u0026\u0026 PathPrefix(`/`)","service":"shrimpkey-shrimpkey-3000"}},"services":{"nextcloud-nextcloud-8080":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"http://<IP_ADDRESS>:80"}]}},"nginx-webserver-80":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"http://<IP_ADDRESS>:80"}]}},"shrimpkey-shrimpkey-3000":{"loadBalancer":{"passHostHeader":true,"responseForwarding":{"flushInterval":"100ms"},"servers":[{"url":"http://<IP_ADDRESS>:3000"}]}}}},"tcp":{},"tls":{},"udp":{}} providerName=kubernetes
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/tls/tlsmanager.go:321 > No default certificate, fallback to the internal generated certificate tlsStoreName=default
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=metrics middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=metrics middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/recovery/recovery.go:22 > Creating middleware entryPointName=metrics middlewareName=traefik-internal-recovery middlewareType=Recovery
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=web middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=web middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/redirect/redirect_scheme.go:29 > Creating middleware entryPointName=web middlewareName=redirect-web-to-443@internal middlewareType=RedirectScheme routerName=web-to-443@internal
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/redirect/redirect_scheme.go:30 > Setting up redirection to https 443 entryPointName=web middlewareName=redirect-web-to-443@internal middlewareType=RedirectScheme routerName=web-to-443@internal
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/recovery/recovery.go:22 > Creating middleware entryPointName=web middlewareName=traefik-internal-recovery middlewareType=Recovery
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=traefik middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=traefik middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/recovery/recovery.go:22 > Creating middleware entryPointName=traefik middlewareName=traefik-internal-recovery middlewareType=Recovery
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=websecure middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=websecure middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=name middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=name middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=web middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=web middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=websecure middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=websecure middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=name middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=name middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=metrics middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=metrics middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=traefik middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=traefik middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/server/aggregator.go:51 > No entryPoint defined for this router, using the default one(s) instead entryPointName=["metrics","name","web","websecure"] routerName=nextcloud-nextcloud-ingress-cloud-kreato-dev
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/server/aggregator.go:51 > No entryPoint defined for this router, using the default one(s) instead entryPointName=["metrics","name","web","websecure"] routerName=nginx-mirror-ingress-bin-kreato-dev
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/server/aggregator.go:51 > No entryPoint defined for this router, using the default one(s) instead entryPointName=["metrics","name","web","websecure"] routerName=shrimpkey-shrimpkey-ingress-social-kreato-dev
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/tls/tlsmanager.go:97 > No store is defined to add the certificate MIIE8DCCA9igAwIBAgISA9wiaiKPqmXQNMdMTV/XLnRDMA0GCS, it will be added to the default store
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/tls/certificate.go:131 > Adding certificate for domain(s) cloud.kreato.dev
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/tls/tlsmanager.go:97 > No store is defined to add the certificate MIIE7TCCA9WgAwIBAgISBB6auWuw4ilWJzF6VJX1WPBsMA0GCS, it will be added to the default store
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/tls/certificate.go:131 > Adding certificate for domain(s) bin.kreato.dev
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/tls/tlsmanager.go:97 > No store is defined to add the certificate MIIE8jCCA9qgAwIBAgISAyNug7yX4VBGXwVnA5lcMoo+MA0GCS, it will be added to the default store
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/tls/certificate.go:131 > Adding certificate for domain(s) social.kreato.dev
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=metrics middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=metrics middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/server/service/service.go:267 > Creating load-balancer entryPointName=metrics routerName=shrimpkey-shrimpkey-ingress-social-kreato-dev@kubernetes serviceName=shrimpkey-shrimpkey-3000@kubernetes
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/server/service/service.go:309 > Creating server entryPointName=metrics routerName=shrimpkey-shrimpkey-ingress-social-kreato-dev@kubernetes serverName=441eff19226de85e serviceName=shrimpkey-shrimpkey-3000@kubernetes target=http://<IP_ADDRESS>:3000
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:82 > Creating middleware entryPointName=metrics middlewareName=metrics-service middlewareType=Metrics routerName=shrimpkey-shrimpkey-ingress-social-kreato-dev@kubernetes serviceName=shrimpkey-shrimpkey-3000@kubernetes
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/middleware.go:33 > Adding tracing to middleware entryPointName=metrics middlewareName=metrics-service routerName=shrimpkey-shrimpkey-ingress-social-kreato-dev@kubernetes serviceName=shrimpkey-shrimpkey-3000@kubernetes
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=metrics middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=metrics middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/server/service/service.go:267 > Creating load-balancer entryPointName=metrics routerName=nextcloud-nextcloud-ingress-cloud-kreato-dev@kubernetes serviceName=nextcloud-nextcloud-8080@kubernetes
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/server/service/service.go:309 > Creating server entryPointName=metrics routerName=nextcloud-nextcloud-ingress-cloud-kreato-dev@kubernetes serverName=a176d79b77beb31a serviceName=nextcloud-nextcloud-8080@kubernetes target=http://<IP_ADDRESS>:80
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:82 > Creating middleware entryPointName=metrics middlewareName=metrics-service middlewareType=Metrics routerName=nextcloud-nextcloud-ingress-cloud-kreato-dev@kubernetes serviceName=nextcloud-nextcloud-8080@kubernetes
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/middleware.go:33 > Adding tracing to middleware entryPointName=metrics middlewareName=metrics-service routerName=nextcloud-nextcloud-ingress-cloud-kreato-dev@kubernetes serviceName=nextcloud-nextcloud-8080@kubernetes
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=metrics middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=metrics middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/server/service/service.go:267 > Creating load-balancer entryPointName=metrics routerName=nginx-mirror-ingress-bin-kreato-dev@kubernetes serviceName=nginx-webserver-80@kubernetes
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/server/service/service.go:309 > Creating server entryPointName=metrics routerName=nginx-mirror-ingress-bin-kreato-dev@kubernetes serverName=eacfcb9283451c19 serviceName=nginx-webserver-80@kubernetes target=http://<IP_ADDRESS>:80
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:82 > Creating middleware entryPointName=metrics middlewareName=metrics-service middlewareType=Metrics routerName=nginx-mirror-ingress-bin-kreato-dev@kubernetes serviceName=nginx-webserver-80@kubernetes
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/middleware.go:33 > Adding tracing to middleware entryPointName=metrics middlewareName=metrics-service routerName=nginx-mirror-ingress-bin-kreato-dev@kubernetes serviceName=nginx-webserver-80@kubernetes
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=metrics middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=metrics middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/recovery/recovery.go:22 > Creating middleware entryPointName=metrics middlewareName=traefik-internal-recovery middlewareType=Recovery
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=name middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=name middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=name middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=name middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=name middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=name middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=name middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=name middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/recovery/recovery.go:22 > Creating middleware entryPointName=name middlewareName=traefik-internal-recovery middlewareType=Recovery
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=web middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=web middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=web middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=web middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/redirect/redirect_scheme.go:29 > Creating middleware entryPointName=web middlewareName=redirect-web-to-443@internal middlewareType=RedirectScheme routerName=web-to-443@internal
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/redirect/redirect_scheme.go:30 > Setting up redirection to https 443 entryPointName=web middlewareName=redirect-web-to-443@internal middlewareType=RedirectScheme routerName=web-to-443@internal
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=web middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=web middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=web middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=web middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/recovery/recovery.go:22 > Creating middleware entryPointName=web middlewareName=traefik-internal-recovery middlewareType=Recovery
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=traefik middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=traefik middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/recovery/recovery.go:22 > Creating middleware entryPointName=traefik middlewareName=traefik-internal-recovery middlewareType=Recovery
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=websecure middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=websecure middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=websecure middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=websecure middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=websecure middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=websecure middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=websecure middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=websecure middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=websecure middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=websecure middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/recovery/recovery.go:22 > Creating middleware entryPointName=websecure middlewareName=traefik-internal-recovery middlewareType=Recovery
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=web middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=web middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=name middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=name middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=metrics middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=metrics middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/metrics/metrics.go:50 > Creating middleware entryPointName=traefik middlewareName=metrics-entrypoint middlewareType=Metrics
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/middlewares/observability/entrypoint.go:47 > Creating middleware entryPointName=traefik middlewareName=tracing middlewareType=TracingEntryPoint
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/server/router/tcp/manager.go:237 > Adding route for social.kreato.dev with TLS options default entryPointName=websecure
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/server/router/tcp/manager.go:237 > Adding route for cloud.kreato.dev with TLS options default entryPointName=websecure
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/server/router/tcp/manager.go:237 > Adding route for bin.kreato.dev with TLS options default entryPointName=websecure
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/provider/kubernetes/ingress/kubernetes.go:181 > Skipping Kubernetes event kind *v1.EndpointSlice providerName=kubernetes
2024-08-22T05:02:43Z DBG github.com/traefik/traefik/v3/pkg/provider/kubernetes/crd/kubernetes.go:179 > Skipping Kubernetes event kind *v1.EndpointSlice providerName=kubernetescrd
2024-08-22T05:02:44Z DBG github.com/traefik/traefik/v3/pkg/provider/kubernetes/ingress/kubernetes.go:181 > Skipping Kubernetes event kind *v1.EndpointSlice providerName=kubernetes
2024-08-22T05:02:44Z DBG github.com/traefik/traefik/v3/pkg/provider/kubernetes/crd/kubernetes.go:179 > Skipping Kubernetes event kind *v1.EndpointSlice providerName=kubernetescrd
2024-08-22T05:02:44Z DBG github.com/traefik/traefik/v3/pkg/provider/kubernetes/crd/kubernetes.go:179 > Skipping Kubernetes event kind *v1.EndpointSlice providerName=kubernetescrd
2024-08-22T05:02:44Z DBG github.com/traefik/traefik/v3/pkg/provider/kubernetes/ingress/kubernetes.go:181 > Skipping Kubernetes event kind *v1.EndpointSlice providerName=kubernetes
2024-08-22T05:02:44Z DBG github.com/traefik/traefik/v3/pkg/provider/kubernetes/crd/kubernetes.go:179 > Skipping Kubernetes event kind *v1.EndpointSlice providerName=kubernetescrd
2024-08-22T05:02:44Z DBG github.com/traefik/traefik/v3/pkg/provider/kubernetes/ingress/kubernetes.go:181 > Skipping Kubernetes event kind *v1.EndpointSlice providerName=kubernetes
2024-08-22T05:03:39Z DBG github.com/traefik/traefik/v3/pkg/provider/kubernetes/ingress/kubernetes.go:181 > Skipping Kubernetes event kind *v1.Node providerName=kubernetes
2024-08-22T05:03:39Z DBG github.com/traefik/traefik/v3/pkg/provider/kubernetes/crd/kubernetes.go:179 > Skipping Kubernetes event kind *v1.Node providerName=kubernetescrd

Hey @kreatoo,
Thanks for reaching out!
To keep the repository focused, we ask that all questions be asked in the community forum. It is pretty active, so you might find that your question has already been answered there.  If not, you can ask and get help from other community members pretty quickly.

Hey @kreatoo,
Thanks for reaching out!
To keep the repository focused, we ask that all questions be asked in the community forum. It is pretty active, so you might find that your question has already been answered there.  If not, you can ask and get help from other community members pretty quickly.

Hey,
I opened a thread but I don't get how this is a question, this looks more like a bug to me.
If it was a config issue it should at least warn/error out, yet there are no logs whatsoever related to the issue, even in debug mode.


Issue with Python Django Support

Running Django versions from 3.2.x to 5.x (Same issue)
Steps to reproduce the behavior (Required)
Below is an example config that I tried
DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.mysql',
        'NAME': 'django',
        'PASSWORD':'',
        'HOST':'<IP_ADDRESS>',
        'PORT':'3306',
        'USER':'',
        'OPTIONS': {
            "init_command": "SET storage_engine=olap",
             #"init_command": "SET @default_storage_engine=olap",
        },
    }
}

Expected behavior (Required)
Should Connect without errors
Real behavior (Required)
(1064, "Getting analyzing error. Detail message: Unknown system variable 'default_storage_engine', the most similar variables are {'default_rowset_type', 'default_table_compression', 'enable_sort_aggregate'}.")

StarRocks version (Required)
3.2.2
Seems like there is no system variable in Starrocks for default_storage_engine which is needed by the mssqlclient for Django
Note:
default_storage_engine was introduced in MySQL 5.5.3.
storage_engine was removed in MySQL 5.7.5.
Starrocks seem to be show up as 5.1.0
MySQL 8.0.11 or later is required (found 5.1.0)

Please advise.
Thanks!

You can change the mysql_server_version in the fe.conf. The default is 5.1.0

Thanks @chaoyli. Will update it
How about the 1st part of the problem...i.e. Django is hardcoded to look for system variable default_storage_engine
default_storage_engine was introduced in MySQL 5.5.3 and above and storage_engine variable used in starrocks is deprecated
so applications like Django are hardcoded to look for default_storage_engine  variable and cannot connect to starrocks

@chaoyli  if we change mysql_server_version to any 8.x.x version then DDL statements like create throw error like below
setting mysql_server_version as 8.0.0
SQL Error [1064] [42000]: Getting analyzing error. Detail message: Unknown system variable 'tx_read_only', the most similar variables are {'innodb_read_only', 'trace_log_mode', 'default_rowset_type'}.

setting mysql_server_version > 8.0.0
SQL Error [1064] [42000]: Getting analyzing error. Detail message: Unknown system variable 'transaction_read_only', the most similar variables are {'innodb_read_only', 'trace_log_mode', 'default_rowset_type'}.


Update data_portal.py

refactoring code with var unpack which is more pythonic, concise, readable and efficient; how do think this change which has practical value？

@.***邮箱联系我，谢谢！


I am having a problem trying to send camera stream to srt server (vMix)

I am trying to send my device camera stream to a srt server I have on my laptop. The code I am using is the following:
Srt srt = new Srt();
srt.startUp();

// create SRT socket to send stream
Socket clientSocket = new Socket();
clientSocket.setSockFlag(SockOpt.TRANSTYPE, Transtype.LIVE);
// connect socket to srt server (vMix running on my laptop)
clientSocket.connect("<IP_ADDRESS>", 11001);

// create udp listening on <IP_ADDRESS>:7800
new Thread(new Runnable() {
	@Override
	public void run() {
		byte[] data;
		try{
			byte[] buffer = new byte[1316];
			DatagramSocket socketUDP = new DatagramSocket(7800);
			while(true){
				DatagramPacket udpPacket = new DatagramPacket(buffer, buffer.length);
				socketUDP.receive(udpPacket);
				data = udpPacket.getData();
				// send received data to srt server
				clientSocket.send(data);
			}
		}catch (Exception ex){}
	}
}).start();

// I use ffmpeg to capture android camera, and stream it to socketUDP
int rc = FFmpeg.execute("-f android_camera -video_size 320x240 -input_queue_size 60 -i 0:0 -r 30 -f h264 udp://<IP_ADDRESS>:7800");

As you can see, the code is pretty simple. I do not know why it doesn't work. I think that the problem is on the srt socket settings.
If I send the android camera directly by udp to my laptop, and use ffplay on my laptop to see it, it works fine. So I think the ffmpeg command is ok.
Another interesting thing is that if I stream my android camera using the app Larix Broadcaster, it works fine (I can see the camera on my laptop using vMix)
Last but not less important, when I run the code above, It doesn't crash, and despite I can't see the camera on vMix, if I open on vMix the statistics dialog, I can see that the vMix is receiving data from my device.

Hi,
Do you have anything in logcat? By the way, can you log the exception?

Dear ThibaultBee, thanks for your answer. Yesterday I solved the problem. The problem was the ffmpeg command I was using. I repleace the command with a new one, and now it works perfectly. This is the new ffmpeg command I am using:
-f android_camera -video_size 320x240 -input_queue_size 60 -i 0:0 -pix_fmt yuv420p -c:v libx264 -b:v 1000k -g 30 -keyint_min 120 -profile:v baseline -preset veryfast -f mpegts "udp://<IP_ADDRESS>:7800?pkt_size=1316"
Thanks again! This project is great!
It really is a big help. I had a lot of troubles trying to build haivision/srt for Android
Best regards, and merry christmas!

Glad to hear that !
By the way, you can use:
socket.getSockFlag(SockOpt.PAYLOADSIZE)
to get the payload size
Also, you can use OutputStream instead of send() which is the Java/Android way to send network packet.
Best regards and best wishes!


Code works on 1080ti but not 2080ti.

System information

Have I written custom code (as opposed to using example directory): used pre written code from here: https://github.com/MathiasGruber/PConv-Keras
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  Linux Ubuntu 19.04
TensorFlow backend (yes / no):  yes
TensorFlow version: 1.14.0
Keras version: 2.2.4
Python version:  3.6.8
CUDA/cuDNN version:9 (edit)(thought i had it at 10 but it was not this code)
GPU model and memory: MB has quad RTX2080TI (11GB) but i'm only using one of them for this

You can obtain the TensorFlow version with:
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
You can obtain the Keras version with:
python -c 'import keras as k; print(k.version)'
Describe the current behavior
Title says it all. I have a code which I trained on my 1080ti which was slow so i moved it to a 2080ti with the same everything. The code now uses the CPU rather than the GPU, i've tried reinstalling tensorflow/keras, even created a brand new env. and nothing worked. I made sure i had CUDA10 since from what i heard the new 2080ti can have a hard time with cuda9.
Describe the expected behavior
Should work on the gpu
Code to reproduce the issue
https://github.com/MathiasGruber/PConv-Keras
Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
Sorry if i did something wrong in the formatting and such.

If anyone finds this post,hello but here is how i fixed it.
I created a brand new env. and installed all my packages as i did BUT rather than doing conda install tensorflow, i did conda install tensorflow-gpu which somehow fixed everything. I might of done something different that I did not do before but this is now solved.


DigitalOcean deployment fails in v2

Hi!
I've been using your app for a project and it's been brilliant :D. However, when I come to deploy onto DigitalOcean I receive the following error message:
Error while creating app from Git template
Could not create app from Git template.
Getting owner: getting team data: rpc error: code = NotFound desc = team not found.
This only occurs on the main / v2 branches. I briefly tried to look into what might be causing the issue but I haven't been able to figure it out.

Hi @MrMannoe, sorry for the late reply and thanks for reporting this. Seems like there is be something wrong on DigitalOcean's end (maybe they made some changes and we have to update accordingly).
I'm gonna reach out to them and provide some feedback on #58 which is about the same topic.
Thank you!

Update: https://github.com/hashlips-lab/safe-nft-metadata-provider/issues/58#issuecomment-1396193453


IEN-498, IEN-500 | assign roles

user details page
assign roles
revoke access

Sorry for a too big pull request.
It's because role and acl affects almost every codes.


Update scoping_document.md

fixed an important typo in scoping_document.md: Line 77 only wrote "publish pseudonymized warn ID" but has to be "publish pseudonymized warn ID's" as each user will have generated more than one ID during the use of the app, as also stated later in line 156 correctly.

fixed with latest commit


Advance Worksheet structure and initial query

Description
This adds a structure representing the fields needed to automatically generate an Advance Worksheet. Also included is a draft query, not currently used anywhere due to how we're trying to not make massive three-to-infinity-point tasks. I'd suggest testing this by running the SQL itself against your own local db to ensure it returns what you would expect.
Reviewer Notes
A few things:

The original task included an instruction to make an advanceworksheet package, so I tucked the query there; eventually, it'll be surrounded with much more functionality. Knowing that, does it make sense to have it over there? Or should the query be in the model file, as we more often do, even though expansion is imminent? What would make more sense to you should you need to refer to this stuff at this point?
Whether fields were pointers or not was determined by how they're represented in the model structs that originally included them, with some influence from which fields are required or not while advancing in the service member signup flow. Does the end product make sense to you?
The current test mostly exists to ensure the structure saves and is accessible as a variable, but it isn't committed to a db. In this interim version of this work, do you feel this is acceptable?

Code Review Verification Steps

[ ] All tests pass.
[ ] Code follows the guidelines for Logging
[ ] The requirements listed in
Querying the Database Safely
have been satisfied.
[ ] Any migrations/schema changes also update the diagram in docs/schema/dp3.sqs
[ ] There are no aXe warnings for UI.
[ ] This works in IE.
Any new client dependencies (Google Analytics, hosted libraries, CDNs, etc) have been:

[ ] Communicated to @willowbl00
[ ] Added to the list of network dependencies

[ ] Request review from a member of a different team.
[ ] (TRIAL) Have the Pivotal acceptance criteria been met for this change?

References

Pivotal story for this change
The Advance Worksheet form in question is here. Not all fields are currently represented in our existing data; this PR just collects from what already exists without expanding our current data model.

@breanneboland I'm going to adopt this and try to push it toward completion.

Re: the column name, both adavance_id and advance_worksheet_id exist on the PPM table.


Add package.json

Adds package.json

install bats via npm instead of git-clone
install bats-assert via npm instead git-submodule
switch travis config to use standard node test setup

defaults to npm-install instead of install in travis.yml
defaults to npm-test instead of script in travis.yml

nodenv---version pulls version from package.json instead of hardcoded
grab release script (for preversion/postversion hooks) from node-build (ensures proper git state before bumping version; triggers brew-publish after bump)
grab brew-publish script from node-build to submit PR to homebrew after each version bump/release

Benefits:

npm install will give us the necessary test dependencies (bats and bats-assert)
npm run will list available scripts
npm test to test
npm version <bump> to do releases
simpler travis configuration

dropped the release script. Instead pulled in brew-publish script via npm/github.


Embedding EasyHook in a C# Class Library

Hey guys!
I'm only planning to use EasyHook for Local Hooking (using EasyHook locally after manual injection of my class library / .dll). Is it possible to embed only the necessary libraries / dll into my own class library? I'd just prefer to have it packaged into one .DLL.
I'm fairly inexperienced. Something similar to static linking in C / C++. I've used Costura Fody and ILMerge before but I'm not sure if they work in this case.
Thanks!

For the managed code, yes. But you would still need the native .dll(s)


Fixed Mayhem Integration Again

@xansec, I made a few minor changes to get mayhem integration working again:

Rust toolchain version (in rust-toolchain) now matches tikv/tikv master. It was also necessary, since some of the newly added code relies on the newer version.
For the futures crate in components/tikv_util/Cargo.toml, the thread-pool feature is necessary for tikv to build successfully. This seems to be an issue with the tikv/tikv master branch.

This github action run on my fork of the repo shows it working.

@rizaziz Can you explain what happened/

I know force pushing is not ideal, but the history of the mayhemheroes/tikv:master branch seems to be really screwed up (@rizaziz seems to have put my commits from 3 weeks ago onto a branch called old_history, them manually redid them on master). I have just pulled from tikv/tikv:master, made the changes again, and force pushed.

@xansec on commit 62db5db I already merged tikv/tikv:master into my gediminas19/tikv:mayhem branch. There have been 3 more commits to master since then, which I just merged in as well.
And yes, ad080eb contains the only actual changes I made.

For whatever reason this PR still has a lot of changes although it should be sync'd with upstream. I'm not entirely sure what's going on here, but I pushed your changes to the master branch myself and it seems to be successful:
https://github.com/mayhemheroes/tikv/runs/7054504699?check_suite_focus=true
Anyways, this is a result of processes on our end and shouldn't be your responsibility. The integration is successful. I'll close this PR for now.


Support calibration benches on apple silicon macs

This adds support for running the budget calibration benchmark code on M1 / apple silicon macs.
(It might also work on intel macs, I will give it a try tomorrow morning, but this should be enough to unblock @jayz22 on calibration)

Thank you so much @graydon !


secretory vesicle

What do you think of secretory vesicle as synonym of
term: Golgi-associated vesicle
goid: GO:0005798
or of
term: secretory granule
goid: GO:0030141
secretory vesicle:
(Science: cell biology) Membrane bounded vesicle
derived from the Golgi apparatus and containing
material that is to be released from the cell. The
contents may be densely packed, often in an inactive
precursor form (zymogen).
http://www.biology-online.org/dictionary/secretory\_vesicle
Reported by: brendamg
Original Ticket: "geneontology/ontology-requests/3305":https://sourceforge.net/p/geneontology/ontology-requests/3305

thanks www.movied.org


🔥 [UI-8] Badge page added

Added badge page
Modified font size settings for tailwind (added xxs)
Added size property forwarding to the Badge component

Already done


fix(frontend): if you disallow cookies the page just shows errors

🍰 Pullrequest

Issues

fixes #1737
None

Todo

[X] None

On chromium I'm not even able to disallow all cookies for any site. @trinity2701 How did you test it out?

Yes you can do this.
To test this, login, disallow cookies from app.... and delete existing cookie. This simulales the behaviour


Updating with GRIBI backup NHG

Adding new subtest and Updating with GRIBI NHG with backup NHG

Pull Request Functional Test Report for #3400 / 3bbb04f9abfb8f3a9d231ca7f6a38f81496cb47f
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

RT-5.7: Aggregate Not Viable All
418ad383
Log

Cisco 8000E

RT-5.7: Aggregate Not Viable All
307e5d0b
Log

Cisco XRd

RT-5.7: Aggregate Not Viable All
e4aa8ed6
Log

Juniper ncPTX

RT-5.7: Aggregate Not Viable All
9ac80c1d
Log

Nokia SR Linux

RT-5.7: Aggregate Not Viable All
eee6546a
Log

Openconfig Lemming

RT-5.7: Aggregate Not Viable All
41e9c66e
Log

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

RT-5.7: Aggregate Not Viable All

Cisco 8808

RT-5.7: Aggregate Not Viable All

Juniper PTX10008

RT-5.7: Aggregate Not Viable All

Nokia 7250 IXR-10e

RT-5.7: Aggregate Not Viable All

Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>3
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.252%

Totals

Change from base Build<PHONE_NUMBER>6:
0.0%

Covered Lines:
1983

Relevant Lines:
3589

💛  - Coveralls


Move to the latest version of concourse for community cpi/stemcell

Need to setup and connect to a credhub server to get our work more secured

Track this work in internal repo


Support google gemini

This change allows one to use langchain-google-genai and simply
generator = TestsetGenerator.with_google(...)

just like one would with with_openai() and get on with life.
Initial tests show no errors in embedding and testset generation. Prompt adaptations work on condition of #676 being merged first.

CI/CD check fail: langchain-google-genai requires Python >=3.9, <4.0

I actually think #670 could be a better way of dealing with different vendors.
However, one thing that still needs to be fixed is temperature arg being a bit of a mess (having and arg but not actually using it). When passed into the Langchain LLM it sometimes causes errors if the Langchain LLM isn't expecting it as an arg such as in #656

hey @joy13975 I agree that #670 is turning out to be the better implementation, so we'll merge that in.
as for #656 yeah that needs work and will try to get it sorted


Create from stackscript Review Feedback

Purpose
Knock out some changes that were brought up during M3 Review on June 15th, 2018
Addressed issues:

M3-779
M3-778
M3-774
M3-780

Notes

Last Revision date in StackScript Selection now is now in ISO-8601 format
Header on UDF panel now reads "StackScript Name Options"
Each UDF label has an "(Optional)" text if that UDF has a default value
Username has been added to StackScript name, similar to GitHub repo conventions (username is also greyed out)
Changed "Active Deploy" to "Active Deploys"

Coverage decreased (-0.01%) to 29.057% when pulling<PHONE_NUMBER>9bda27af501db793aa03e28c06cc6a on martinmckenna:create-from-stackscript-feedback into e196ee8317c6f9e4f43eadb284da1d601fbabd25 on linode:develop.

@asauber @alioso ready for re-review
@rjstires I also abstracted the formatDate() stuff with an showTimeStamp param if we want to display the UTF time.


Log displays player user name in headless

Based on persona_name from the gettoken file. Works with all 3 methods of adding token (gettoken.json, -t and -tj).
For issue #140

PR #142 & #143, look to address the same thing...

@callmenemo491 They do, however #142 doesn't work. At least for me. gPlayerName is not defined anywhere in the pull request, returning undefined.


Loops through stack to determine the token for request.

Previously, it was a bunch of if statements. This is simply a refactor (does the same thing, but in less code).

Also adds getToken method to Request instances. Getting the token from the request (query, body, and headers) is universal and may very well be needed elsewhere (not just the TokenGuard instance). It would be good if this was available (and didn't depend on the 'token' guard being set) but if not, developers could just add it as a macro.


Wont Work

i try to use your program and wont clean the .dll

This Writing Like this clean the file but when i try to decompile him still the Confused Code

this is because it doesnt remove the control flow
so yes everything else has been removed (near enough)

What should i do to fix it

Can you show me your error or send me some file for see it?

Try this : http://www.filedropper.com/vaultplugin


add version command for ent

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡

The current ent command line tool cannot view the version
Motivation 🔦

I'm using ent's bin file, although I always use it.
But after a while I still forgot its version.
I hope to add a command to view the version in the ent command.

Hey @godcong and thanks for proposing this. This was proposed a few times and was rejected because the current Go tool chain already solves this issue. See my answer at https://github.com/ent/ent/issues/368#issuecomment-591912949:

What's wrong with go version -m <binary>?
I also prefer users to use go generate and not ent directly, for the reason mentioned here. Especially now, when modules support is ready for production use (since Go 1.14).

In short, users should not deal with ent CLI directly. Instead, they use go run entgo.io/ent/cmd/ent. When using go run from a Go module project, Go executes the ent binary with the version mentioned in the go.mod file. This way, you're making sure the Ent version (used at runtime) is identical to the version that was used to generate the assets (with go generate).
Please, let me know if I can close the issue. Thanks

ok.
I will say if I find any problems.


Start9 wrapper

Understanding very much that there is limited time for FOSS to begin with, it would be awesome to see this bundled for Start9 (https://docs.start9.com/0.3.5.x/developer-docs/packaging)

Hi !
It's planned and ideally, someone more familiar with StartOS (which I only know by name), could do the wrapper
But first, in order to do that, I need to make the parser be able to parse the chain without having to shut down the node (which would be very annoying for people relying on it running)

@drgarlic give me a ping when shutting down bitcoin core is not needed anymore. I created several StartOS wrappers and can probably help with this.
As you said, stopping the node is a show-stopper for now.

@remcoros Will do !

@remcoros Just pushed an update ! Satonomics now requires bitcoind to run
Though is suspect there might be more things to change to be able to be ran on StartOS but it's huge milestone nonetheless

That's awesome!
Would it be possible for you to add Dockerfile(s) / docker-compose, to make building/running this locally without installing the dev dependencies on a local machine?
That would make it much easier for me to transform it to a startos package most likely.

I'm not really familiar with Docker but I'll try and will come back to you once I have something working 👍


Response object does not set url correctly

Summary
First of all, thanks for this package; being able to create unit tests for Cloudflare workers is super helpful!
Problem
I have a worker.js script that includes a call to Response.redirect():
// worker.js
async function handleRequest(request) {
  return new Promise(resolve => {
     // ... some logic to figure out the `newUrl` value

     return resolve(
       Response.redirect(newUrl, 301)
     );
  });
}

With a test:
// cloudworker set up not included in this snippet

new Promise(async (resolve, reject) => {
  const req = new Request(new URL(requestUrl));
  const res = await handleRequest(req);

  try {
    // We don't want to lock in our tests to specific redirects
    // we just want to test that the redirect logic works.
    assert.isAbove(res.status, 300);
    assert.isBelow(res.status, 400);
    assert.include(
      res.url,
      NEW_ORIGIN, // defined above...
      `The origin should change if the redirect part of the migrated pages, req=${requestUrl}`,
    );
  } catch (err) {
    return reject(err);
  }

  return resolve();
}),

Expected Behaviour
The test passes or fails, depending on the implementation of the worker.js code.
Actual Behaviour
The test always fails as res.url is undefined.
Info
@dollarshaveclub/cloudworker: 0.0.11
@dollarshaveclub/node-fetch: 3.2.0
Notes
I've had a look and it looks like the problem comes from the way the ShimResponse calls the constructor, and how it matches with the prototype of Response constructor of @dollarshaveclub/node-fetch.
The ShimResponse sets the url in the Location header, and the Response object (node-fetch) expects it to be supplied as an option.
See:
https://github.com/dollarshaveclub/cloudworker/blob/master/lib/runtime/fetch.js#L42
and
https://github.com/dollarshaveclub/node-fetch/blob/master/src/response.js#L32
If you like, I am happy to raise a PR to resolve this?
Workaround
In the meantime, I've got round my testing issue by replacing
    assert.include(
      res.url,
      NEW_ORIGIN, // defined above...
      `The origin should change if the redirect part of the migrated pages, req=${requestUrl}`,
    );

with
    assert.include(
      res.headers.get('Location'),,
      NEW_ORIGIN, // defined above...
      `The origin should change if the redirect part of the migrated pages, req=${requestUrl}`,
    );

thanks!

Hi @tgallacher. From some experimentation, I found that cloudworker's behavior is mostly correct in this scenario when compared against Cloudflare Workers. Here's an example of how Cloudflare Workers behave. Note in the console that the redirect response URL is empty. I'd be open to a PR fixing cloudworker to match that behavior (empty string instead of undefined) but not for it to be the redirect url.
All that being said, definitely correct me if I'm misinterpreting this issue. Thanks!


Fix chan double close on message disposition

if a handler calls 2 message dispositions in a close loop (which is almost certainly a bug in the code), the code will panic.
ensure we don't panic by only ever closing the channel once.
even bad code from the user should not cause a panic.

/azp run

Can you run the e2e test and finish the review? @jhendrixMSFT

Superseded by https://github.com/Azure/go-amqp/pull/69


Older version in the library manager

Just a heads up, when you download the current Arduino version and add restfully via the library manager, it will download an older version and either of the two examples given here on github will not work.
Not sure how much you can influence what the library manager contains.
Thanks for the great library in any case, makes things a lot easier 👍

Thanks! I will take a look. I can push an update but I will need to review the code first.

Thanks! I will take a look. I can push an update but I will need to review the code first.

FYI  There is actually a new version in branch feature/KISS that needs to be released. The current interface is easy...until you have an error then it spews a bunch of GCC template errors. The code in-behind the API is very complex and in the end I found it inflexible even for my needs. The KISS version changes the interface up a bit. It's maybe not quite as simple as the current API using method chaining but it is far simpler code in-behind and doesn't generate unreadable errors. Even still KISS is 10x simpler to use after you experience even 1 template error. lol.
I don't have the docs updated but the main difference is it overloads the / operator to provide URL path parsing. Think similar to C++ << streams. So an example would be something like:
int user_id;
if(request / "api" / "users" / &user_id / "details") {
     // return user details with user ID in user_id variable
     // ...
}

The return value of any / operator is a URL parser state object which can be casted to bool (true if URL matches). Instead of just using if(...)  to test for URL match you can also store the result at any point in the URL path in a variable and branch out to match different URL paths. So parsing is efficient! But this also means you can do any custom code at any point in your matching...such as resolving the user object before the final endpoint handler runs. You can also match to an endpoint, fail out, and have it recover at some earlier point and attempt another branch.

FYI  There is actually a new version in branch feature/KISS that needs to be released. The current interface is easy...until you have an error then it spews a bunch of GCC template errors. The code in-behind the API is very complex and in the end I found it inflexible even for my needs. The KISS version changes the interface up a bit. It's maybe not quite as simple as the current API using method chaining but it is far simpler code in-behind and doesn't generate unreadable errors. Even still KISS is 10x simpler to use after you experience even 1 template error. lol.
I don't have the docs updated but the main difference is it overloads the / operator to provide URL path parsing. Think similar to C++ << streams. So an example would be something like:
int user_id;
if(request / "api" / "users" / &user_id / "details") {
     // return user details with user ID in user_id variable
     // ...
}

The return value of any / operator is a URL parser state object which can be casted to bool (true if URL matches). Instead of just using if(...)  to test for URL match you can also store the result at any point in the URL path in a variable and branch out to match different URL paths. So parsing is efficient! But this also means you can do any custom code at any point in your matching...such as resolving the user object before the final endpoint handler runs. You can also match to an endpoint, fail out, and have it recover at some earlier point and attempt another branch.

Any updates on this?
Please let us know if you are continuiing the maintenance or not, otherwise we can find an adeguate replacement.
Thanks


Add hooks after completion of Migrate Value

[ ] Do only one thing
[x] Non breaking API changes
[x] Tested

What did this pull request do?
Increase the dialect of the driver, add hooks after completion of Migrate Value
User Case Description
for example in the column comment of postgresql
func (m Migrator) After(value interface{}) error {
	return m.RunWithValue(value, func(stmt *gorm.Statement) error {
		for _, field := range stmt.Schema.FieldsByDBName {
			if field.Comment != "" {
				if err := m.DB.Exec(
					"COMMENT ON COLUMN " + stmt.Table + "." + field.DBName + " is " + field.Comment,
				).Error; err != nil {
					return err
				}
			}
		}
		return nil
	})
}

Hello @kainonly
Thank you for your PR, but I don't think this is a good implementation, I would suggest you create a pull request for the postgres driver and reimplement the CreateTable method to support it.
BTW, when implementing the method, you could just call the current one by using m.Migrator.CreateTable() and create comments after the method
Thank you for your PR.


Wandb Sweep with mmdetection

Hi everyone,
Does anyone know that how to use Wandb Sweep with mmdetection? Is there any tutorial or examples?
Thanks :)

Hi @ytzhao, a member of W&B here.
Running sweeps for mmdetection scripts should pretty much be the same as any other example. the structure I usually prefer for sweeps is:

A function that takes sweep config as a parameter and initializes the hyperparams using those values
Use wandb callback to report the metrics while training using sweep configs( mmdetection already has a wandb metric logger)
Launch the sweep on the above function with desired hyperparameter search space


[flutter_localizations] Add compatibility with latest intl 0.19.0

Change intl version, 0.18.1 -> 0.19.0
Fix issue: https://github.com/flutter/flutter/issues/139861
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@FullstackWEB-developer Curious why you closed this?

Because jiffy >=6.2.2 depends on intl ^0.19.0 and every version of flutter_localizations from sdk depends on intl 0.18.1, jiffy >=6.2.2 is incompatible with flutter_localizations from sdk.
So, because kuanneng_mobile depends on both flutter_localizations from sdk and jiffy ^6.2.2, version solving failed.

@FullstackWEB-developer Curious why you closed this?

No problem, I just hope the Flutter team resolves this issue quickly.


How to edit code in gogs

Hello I just set up gogs container image , and I have migrated a few repos  from github but
I can't find the button to edit my code.
And secondly seems like gigs don't have a way to add new script or directory.
Please can someone guide me please

Hi there,
Please follow on https://github.com/gogits/gogs/issues/1071 in the future. :speech_balloon:


convert some service classes to static fields, run [GitHubLernaJson GithubLicense GithubManifest GithubMilestoneDetail GithubMilestone GithubPackageJson]

Warnings

:warning:
This PR modified service code for github but not its test code. That's okay so long as it's refactoring existing code.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @calebcartwright!

  Generated by :no_entry_sign: dangerJS against 47233945e9e3688a15e6996577f88866ce786f9e


WFLY-13387 Implemented Jaeger client metrics

Implementation for https://issues.redhat.com/browse/WFLY-13387

@ehsavoie Please have a look.
We need to be sure that any metrics we add will continue to be available as long as we provide this subsystem.
Also this should probably require a 'statistics-enabled' config attribute to turn on.

@ehsavoie Please have a look.
We need to be sure that any metrics we add will continue to be available as long as we provide this subsystem.
Also this should probably require a 'statistics-enabled' config attribute to turn on.

As far as I can see the last time the metrics changed was Feb. 2018. But I am not involved in the jaeger project and cannot say if/when the will change next.
Would statistics-enabled be an attribute in org.wildfly.extension.microprofile.opentracing.SubsystemDefinition or org.wildfly.extension.microprofile.opentracing.TracingDeploymentDefinition?

@tobiasstadler I'll defer to @ehsavoie on the attribute placement as he knows the subsystem better. Generally those are at the top level because finer-grained configuration isn't particularly useful.

@tobiasstadlerI think it is better to define this at the subsystem level, having tracers with metrics and tracers without could lead to misunderstanding and JaegerEnvTracerConfiguration wouldn't be easily configurable that way.

@tobiasstadler are you able to follow up on the comments from @ehsavoie ?  Also it looks like there is presently a merge conflict.

@darranl Sorry, I din't have time so far.

@jasondlee Are you able to comment on how relevent this is considering other changes in this area?

@darranl I'm not sure I see any overlap, necessarily, between this and the other changes, other than the possibility that the version change my break this, but I would expect, given the age of this PR, that it is already using the version we're investigating. That aside, I'm not sure i understand what's going on here to have much of substance to add.

Hello, tobiasstadler. I'm waiting for one of the admins to verify this patch with /ok-to-test in a comment.

MicroProfile OpenTracing has been removed from WildFly, so this request is no longer valid.


@conda-forge-admin, rerender

Issue:

Environment (conda list):

$ conda list

Details about  conda and system ( conda info ):

$ conda info

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I rerendered the recipe in conda-forge/jmol-feedstock#14.


Allow emoji to be optional

Emoji icon in release sections would be nice if it was optional in case people wanted a cleaner look and feel for their release notes (like myself).
I've ran ./mvnw verify and previously signed the CLA

Just so I understand, you're advocating removal of the emoji config option and consolidating it into a single title that the user provides, correct? The default section title output would stay the same.
I can do this, I just didn't want to break Spring's tooling or a third party (like release-notes-generator-action) that depends upon the current configuration format and has customized the emoji or title.

When doing so, we should document that the emoji of a Section is optional rather than silently ignoring it later as you suggest here.

With the approach you recommend, it's more appropriate to say that the title accepts, but doesn't require, an emoji in markdown format anywhere in the string, right?

Just so I understand, you're advocating removal of the emoji config option and consolidating it into a single title that the user provides, correct?

Actually I wasn't but that's a good idea. It would give you the flexibility to format titles any way you like. I am not aware of us using the emoji + title configuration option. Our usage is based on the  ReleaseNotesSections that define default sections statically.

it's more appropriate to say that the title accepts, but doesn't require, an emoji in markdown format anywhere in the string, right?

Good idea. We could generalize by saying that the title is in markdown format and that emoji are supported.

Thanks, I've modified the PR to remove emoji in favor of title containing all necessary information.

File Update

Any update on this?

Thanks for the PR @steven-sheehy. This is now merged into master.


Add class label to kubernetes ingress discovery

Ref https://github.com/prometheus/prometheus/issues/8914

Thanks @brancz
Are you happy with _ingress_class for the label name? I was torn between that and _ingress_class_name which has more parity with the field name it's derived from (ingressClassName) but felt needlessly verbose

Ah thanks for pointing it out! I agree with the verbosity, but it has happened before in Kubernetes that collisions could have happened (eg. serviceAccount and serviceAccountName) so let's use _ingress_class_name. People won't have to type this all the time, so the verbosity doesn't hurt I think.

lgtm


Couldn't load any language!

Hey,
I've trained my custom-language with the given script and it worked out-of-the-box like a charm! :-)
Anyway I face a crucial problem:
I got my .traineddata file as an output from training. I copied (just) this file into my tessdata folder.
When I hit the command tesseract --list-lang it prints all languages, including my custom lang.traineddata file.
But when I try to use my custom trained language as in tesseract img.jpg -l lang stdout it fails and says: couldn't load any language!
All other languages, like eng, deu etc. work fine! It's just my custom trained language.
The Tesseract version I'm using is 4.0.0-beta1 - should I may update my Tesseract?
What am I doing wrong? :-(
I would love any answers, suggestions and ideas, since I'm pretty new (24h in) to Tesseract and don't find any working answers on the internet.
Thank you so much and have a great day!
Michael

Please update tesseract and try.

tesseract img.jpg -l lang stdout

That's the wrong order. Please try tesseract img.jpg  stdout -l lang.

Hey guys, thanks for the fast replies!!
I was busy the whole day updating tesseract. Originally I used sudo apt-get install tesseract-ocr which results in version 4.0.0-beta1 - and there seems no way to update it?
--> So i cloned the github repository and installed it with the given make files.
Result:
I now use tesseract 4.1.1 and the correct syntax tesseract img.jpg stdout -l lang.
tesseract --version --> 4.1.1
tesseract --list-langs --> eng, custom
It still doesn't work - but I get a new error:
tesseract (legacy) engine requested but components are not present
Failed loading language 'custom'
Tesseract couldn't load any languages!
Could not initialize tesseract.

Do you guys have any idea what's going on and why?
Thanks a lot and have a good day!!

Please use the Tesseract user forum for further questions.


New version: PrismLauncher.PrismLauncher version 7.0

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/109239&drop=dogfoodAlpha

This package appears to also require a JRE:

This package appears to also require a JRE:

While that's true. Users are free to choose any JRE so we don't really want to force them to install some specific JRE using winget.

@wingetbot waivers Add Validation-Executable-Error


[Feature Request] Instant group chat

You may add a second tab for instant chat, this would be better than putting in the code useless and temporary comments or use something else in another window like discord, especially for the possible amount of files who would have their own chat.

Thanks for taking the time to share this idea! :bow: We agree that collaborating in Teletype is most effective when paired with a way to talk about the code you're writing together. From the Teletype announcement post:

For now, Teletype only transmits text, so it’s a good idea to combine it with an application for voice communication. Traditional screen sharing can also be helpful for sharing the state of applications outside of Atom. Ultimately, we want to incorporate these kinds of features directly into the package along with a long list of other improvements.

For us, we've found voice communication to be our preferred medium, but I can see where chat could potentially be useful.
As we prioritize future work, we'll be looking at feature requests like this one to determine where we can deliver the most benefit with the available engineering resources (i.e., full-time Atom engineers, community maintainers, and new contributors). In the meantime, if integrated chat is a feature that would benefit your workflow on a regular basis, adding a :+1: emoji reaction to the issue body is a great way to let us know.

it will be great and extremely useful to incorporate audio chat within teletype since it already uses webRTC.
Usually I chat with participants by typing and erasing, for example two members are in the same line and they need to discuss about something they will put some extra lines and start typing, for example:
"we should do this, we should do that" than erase and wait for the other user to answer.
With a built-in audio chat you can simply talk without having to use another chat service (teamspeak, hangouts, whatever) and without exit the atom window.

Integration with Google Hangout in the Teletype for the Voice or Video chat would be great.

Hello! Has chat feature been integrated in Teletype?


Honor graceful shutdown in deleteMachine integration test

add test validation for machine terminating state
add test validation for vm graceful shutdown
add test validation for vm destroy after graceful shutdown period

Fixes #175 (partially)

@Rohit-0505 i didn't see any comment for first use case from issue here. Pls don't forget create follow up issue for it

@Rohit-0505 i didn't see any comment for first use case from issue here. Pls don't forget create follow up issue for it

I discussed that with @afritzler , If we really want to cover the scenario of direct destroy machine by starting a new libvirt app run with gracefulShutdownTimeout=0 other than one in server_suite_test already present. He had different opinion about this and wanted to clarify over here.
@afritzler can you please give your thoughts here?


refactor: clean up StateFetcher::next_peer

The &mut Peer is unused, so we do not need to return it

Codecov Report

Merging #738 (f805456) into main (6cf5427) will decrease coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #738      +/-   ##
==========================================
- Coverage   72.67%   72.63%   -0.04%
==========================================
  Files         268      268
  Lines       27604    27604
==========================================
- Hits        20061    20050      -11
- Misses       7543     7554      +11

Flag
Coverage Δ

unit-tests
72.63% <100.00%> (-0.04%)
:arrow_down:

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

Impacted Files
Coverage Δ

crates/net/network/src/fetch/mod.rs
83.63% <100.00%> (ø)

crates/stages/src/stages/bodies.rs
91.40% <0.00%> (-1.76%)
:arrow_down:

crates/net/network/src/peers/manager.rs
81.70% <0.00%> (-0.20%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Upgrade guide for v4

Since v4 had some API changes and renaming, I was looked for an upgrade guide.
Only thing I found was the changelog. That could be a little bit clearer.
Are you interested in a Upgrading Documentation PR? Especially from 3.x.x to 4.x x?
If yes, I could send a PR in the hacktoberfest spirit.

Thank you very much, @kriswep.
Documentation is always welcome, I'm looking forward to receiving a PR.
❤#hacktoberfest


fix: use unique sbom identifier for the uri field

Description of the PR
HasSBOM has a uri field that is currently set to the source information. Both SPDX and CyclonDX provide an unique uri that can be used to identify the SBOM document. By storing this information in HasSBOM we are making it easier for folks to find "sbom-uri"->"top-level-package" relation.
PR Checklist

[x] All commits have a Developer Certificate of Origin (DCO) -- they are generated using -s flag to git commit.
[ ] All new changes are covered by tests
[ ] If GraphQL schema is changed, make generate has been run
[ ] If collectsub protobuf has been changed, make proto has been run
[ ] All CI checks are passing (tests and formatting)
[ ] All dependent PRs have already been merged

e2e flakiness will be fixed once: https://github.com/guacsec/guac/pull/1367 merges. Will rerun the test for now


Enhanced lateral control

This is a large set of enhancements for lateral control, which has been tested with positive results on many makes and models.  The enhancements are in the following areas:

MPC interpolation
Projection of future state
Steer rate and acceleration control
Steering torque calculation (modeled as a resonant circuit)
Longitudinal offset of EON camera

Overall benefit:

Steering response is improved, and made consistent across all vehicle speed ranges
Dependency and sensitivity to PID "tuning" is reduced
Feed forward error due to suspension alignment, wind, and crowning is reduced
Sample error from low resolution sensor data is reduced
Steering mechanism is more direct / intentional, and has a more fluid sweep.

The proposed logic generally works well with standard PIF parameters.  However, some vehicles, like the Honda Civic require some customization of SteerKpV and SteerKiV for smooth straight-line driving.  To simplify the tuning process, I created another branch of the proposed logic, which captures high-resolution steering data to a CSV file for offline analysis.  This would likely be done by community members with tuning expertise (via email).
The proposed tuning method uses a staged approach.  The first stage will induce a sinusoidal adjustment of all 3 resonant steering parameters (resistance, reactance, and inductance) at different frequencies.  The goal for this stage is to capture a high-level view of steering response from a broad set of combined values.  This can be completed with only 10 minutes worth of data recorded at a steady speed on a well-groomed highway during favorable weather. If the steering response is not acceptable at any point in the 10 minute log, then SteerKpV and SteerKiV should be reduced by ~20% (or more) before repeating Stage 1.  Otherwise, new values for all 3 resonant parameters will be chosen for the next tuning stage.

Here is a snapshot from stage 1.  Note that the snapshot is interactive (after following the link).  You can zoom in or out using the buttons at the top, or with mouse / keyboard shortcuts.  Also note that the "Sway" value is a periodic agitation of the steering system, which helps with the tuning process.
The second tuning stage will use a fixed value for resistance, which should be the lowest acceptable value from stage 1 (ideally 0.5).  However, the values for reactance and inductance will have a sinusoidal adjustment similar to stage 1, except with a smaller amplitude and frequency.  The goal for this stage is to validate the adjustments from stage 1 while further refining values for reactance and inductance.  This requires another 10 minute CSV data log similar to stage 1.
The third tuning stage will use fixed values for resistance and reactance.  However, the inductance value will have a sinusoidal adjustment with a smaller amplitude and frequency than stage 2.  The goal for this stage is to validate the adjustments from stage 2 while further refining inductance.  This requires another 10 minute CSV data log similar to stage 2.
The fourth and fifth stages are optional, but allow the resistance or reactance value to be further refined with a sinusoidal adjustment while the other 2 parameters remain fixed.  Stages 3-5 can be repeated again and again, if desired, until steering response is perfected (or "resonant", "impedence matched").

This has been work in progress since Nov of last year after 100s of tests can say these changes has been tested on almost every car as possible with help of other devs involved. This is a game changer as far as lateral control goes where @Gernby  has put almost day and night to work on this awesome project in the end it was all worth it thanks @Gernby for your hard work bro:)

FYI, I have added more content above.

Gernby's work has made Toyota cars feel actually safe to drive with openpilot. Before I was getting severe jerking on the 2018 Rav4 Hybrid, but with a version of his steering I was able to tune and get smooth feeling turning - best a Toyota has ever felt! It also made my Civic perform better on roads with high crowns by staying dead center. Cars will need re-tuning, but I think it is worth it in the long run.

I've driven for the last month on a fork of 0.5.8 w/ Gernby steering and I recently returned to stock for 0.5.9.  There is a significant reduction in steering quality, especially in gradual turns where Gernby steering felt much smoother and more intentional.

Agree with @rdm128 Gernby's FF steering made my car feel like it was on a "track".  perfectly centered at all times with a high degree of certainty that it would make turns very consistently.

Thanks for the comments above!
I have done a successful merge of my code with 0.5.9, but still need to clean it up.  Thankfully, it seems that 0.5.9 compliments the enhancements in this PR.

FYI, I just finished testing a 0.5.9 version of my latcontrol, and will update the PR branch after I get more feedback from the community.

Do you happen to know of a link that explains to a novice how to install it? I am worried it’s going to need SSH...
Sent from my iPhone

On Mar 4, 2019, at 1:46 PM, Gernby<EMAIL_ADDRESS>wrote:
FYI, I just finished testing a 0.5.9 version of my latcontrol, and will update the PR branch after I get more feedback from the community.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

geo2112 take a look at the workbench application on opc.ai will help you
connect and install other forks ect.
On Mon, Mar 4, 2019 at 4:52 PM geo2112<EMAIL_ADDRESS>wrote:

Do you happen to know of a link that explains to a novice how to install
it? I am worried it’s going to need SSH...
Sent from my iPhone

On Mar 4, 2019, at 1:46 PM, Gernby<EMAIL_ADDRESS>wrote:
FYI, I just finished testing a 0.5.9 version of my latcontrol, and will
update the PR branch after I get more feedback from the community.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/commaai/openpilot/pull/529#issuecomment-469475269,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ao9IrSzLNkMxlfxzWagwmhcdGv8DR3vLks5vTbG4gaJpZM4a8xJi
.

--
Thank You,
Chas Setchell
<EMAIL_ADDRESS>

After careful review of this combined set of enhancements, I believe some of the enhancements were unnecessary and / or problematic.  I spent a considerable amount of time refining the remaining enhancements and will submit a new PR after feedback from the community.


API: Handle CORS

Is your feature request related to a problem? Please describe.
API requests to Epinio from a browser suffer from CORS errors (see https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS - resources requested from a domain different from that serving the frontend JS).
Up till now we've only worked in a 'dev' environment where the origin is rewritten to match that of epinio. In product however this proxy does not exist.
There are two other methods to proxy API requests in Rancher

Via the Rancher instance / Steve API. This won't work as only whitelisted domains are accepted (it's best not to ad-hoc add/remove these)
Via the Kube API proxy. This won't work as it strips the auth header

Describe the solution you'd like
Best solution from a UI perspective, but less secure, is adding the header Access-Control-Allow-Origin: * to inform the browser the API is ok accepted these type of requests. This means the UI avoids any type of proxy either in dev world or production.
Describe alternatives you've considered
Alternatively the auth could support a fall back header, something like x-epinio-auth-header which will be checked with the Authorization header is missing. This would allow the UI to use the Kube API proxy. This adds a layer of complexity though and wouldn't solve the CORS issue for the standalone use case.
Additional context
See slack thread

We can have a configuration option on the Epinio server with a list of domains to allow for CORS. It could be an environment variable so that a re-installation is not needed if the Web UI domain changes. Would that work for you @richard-cox ?

@jimmykarily On one hand that's a good compromise and should work fine, on the other that's additional configuration. I think the former would work but as you said, would be good to edit at run time

Adding to Beta2 (assuming that the UI release for Beta2 would need this)

Reminder ticket to automate QA: #971


Examples still use md prefixes

#7241 removed all md prefixes, however the documentation examples still have them:
e.g https://material.angular.io/components/button/examples

Same for the Getting started page https://material.angular.io/guide/getting-started

The documentation site has not yet been updated with the latest guides and examples. The repo's md files have already been changed so the next push should resolve this.


Add Schedule Permutation

~Contingent on #13 being merged, as sectionsOverlap() (line 126, Scheduler.java) relies heavily on the Section.overlaps() method~
13 has been merged, this is now ready to merge pending review

There's a lot of commits showing up here that have already been merged into master (eg. I can see the google API additions in the pom.xml and those are already in master). Can you either rebase this beanch onto master or merge master into this branch to clean up overlapping code changes?

By the by, this is a prime example of the sort of pull request where you would want to use the "squash and merge" strategy once it gets reviewed.

There's a lot of commits showing up here that have already been merged into master (eg. I can see the google API additions in the pom.xml and those are already in master). Can you either rebase this beanch onto master or merge master into this branch to clean up overlapping code changes?

I meant to ask this - those commits that are showing up happened specifically after I rebased this branch onto master. What would be the best way to fix that (how would I merge master into this branch for example) and how can I avoid that going forward?

For reviewing purposes, here's a diff of this branch with master: https://github.com/googleinterns/step78-2020/compare/master...Permutation

Update: going to just squash and merge when approved, not going to deal w rebasing because it's too much of a headache (though will definitely be a lot more cognizant in the future wrt rebasing vs merging)


Unexplained Error

When I call createCustomerProfileFromTransaction($transactionId) I get E00059 The authentication type is not allowed for this method call. Does anyone know the cause of this? I'm sending to the SANDBOX server.

If you do a getTransactionDetails on the same transId, what is the transaction type & status?
Sent from my iPhone

On Nov 16, 2016, at 6:43 AM, GregCatalano<EMAIL_ADDRESS>wrote:
When I call createCustomerProfileFromTransaction($transactionId) I get E00059 The authentication type is not allowed for this method call. Does anyone know the cause of this? I'm sending to the SANDBOX server.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks for the response. It gave me the same thing and I realized I had the password wrong. Now I'm on to a new error... Progress :+1:


Explore using foreign fetch to allow event resend even when off site

https://developers.google.com/web/updates/2016/09/foreign-fetch

Imagine, for instance, that you’re an analytics provider. By deploying a foreign fetch service worker, you can ensure that all requests to your service that fail while a user is offline are queued and replayed once connectivity returns. While it’s been possible for a service’s clients to implement similar behavior via first-party service workers, requiring each and every client to write bespoke logic for your service is not as scalable as relying on a shared foreign fetch service worker that you deploy.

Foreign fetch is no longer available for testing in Chrome, and has been removed from the service worker specification.


Issues with triggers in last encounter of The Vault

Description
The last encounter of The Vault against Ser Charibert has numerous issues with the fight-specific triggers.
Additional information
The Evade marching knights trigger fired as soon as the last trash pack before the boss was killed, before we even left that tower room. At least one other fight-specific trigger fired at the wrong time though I didn't manage to catch what the text was.
The generic AoE and tankbuster triggers seemed to be fine.
The actual fight timeline also seemed to be fine.

That's one of my older submissions, yes. It shouldn't be too hard to fix the knight evasion trigger, just make it conditioned on seeing Charibert use an ability, probably Holy Chains. I'll get that taken care of tonight.
The only other thing I can think of that would have failed is if your party pushed him to the intermission within 5 seconds of the next use of Altar Candle. Because it's an instant-cast, the only way to warn against it is with a timeline trigger,