Unable to create wildcard certificates

Is this a BUG REPORT or FEATURE REQUEST?:  BUG REPORT

Uncomment only one, leave it on its own line:

/kind bug

/kind feature

What happened: I tried creating wildcard certificates using image canary. Cert-manager panics while creating an order for the wildcard certificate. However, I got the certificate generated for another ingress which request for the same domain mydomain.ooo (no wildcard).
What you expected to happen: Order gets completed and new wildcard certificate is created.
How to reproduce it (as minimally and precisely as possible):  I installed cert-manager with static deployment files from : here. I am using quay.io/jetstack/cert-manager-controller:v0.3.1 cert-manager image. Then I created ingress using the following config:
{
  "kind": "Ingress",
  "apiVersion": "extensions/v1beta1",
  "metadata": {
    "name": "sub-es",
    "namespace": "development",
    "annotations": {
      "certmanager.k8s.io/acme-challenge-type": "dns01",
      "certmanager.k8s.io/acme-dns01-provider": "cloudflare",
      "certmanager.k8s.io/issuer": "letsencrypt-staging",
      "kubernetes.io/ingress.class": "nginx",
      "kubernetes.io/tls-acme": "true"
    }
  },
  "spec": {
    "tls": [
      {
        "hosts": [
          "*.mydomain.ooo"
        ],
        "secretName": "es-cert"
      }
    ],
    "rules": [
      {
        "host": "es.mydomain.ooo",
        "http": {
          "paths": [
            {
              "path": "/",
              "backend": {
                "serviceName": "myservice",
                "servicePort": 9200
              }
            }
          ]
        }
      }
    ]
  }
}

Anything else we need to know?: Following are the logs from cert-manager pod:
I0705 05:39:05.888329       1 sync.go:126] Certificate "es-cert" for ingress "sub-es" is up to date
I0705 05:39:05.888346       1 controller.go:166] ingress-shim controller: Finished processing work item "development/sub-es"
I0705 05:39:05.894032       1 controller.go:136] issuers controller: syncing item 'cert-manager/letsencrypt-staging'
I0705 05:39:05.894081       1 acme.go:159] getting private key (letsencrypt-staging->tls.key) for acme issuer cert-manager/letsencrypt-staging
I0705 05:39:05.894446       1 logger.go:67] Calling GetAccount
I0705 05:39:05.894797       1 controller.go:136] issuers controller: syncing item 'development/letsencrypt-staging'
I0705 05:39:05.894825       1 acme.go:159] getting private key (letsencrypt-staging->tls.key) for acme issuer development/letsencrypt-staging
I0705 05:39:05.895176       1 logger.go:67] Calling GetAccount
I0705 05:39:06.529674       1 setup.go:73] letsencrypt-staging: verified existing registration with ACME server
I0705 05:39:06.529731       1 controller.go:150] issuers controller: Finished processing work item "development/letsencrypt-staging"
I0705 05:39:06.555893       1 setup.go:73] letsencrypt-staging: verified existing registration with ACME server
I0705 05:39:06.555926       1 controller.go:150] issuers controller: Finished processing work item "cert-manager/letsencrypt-staging"
I0705 05:39:07.824772       1 controller.go:177] certificates controller: syncing item 'development/my-wildcard-cert'
I0705 05:39:07.824787       1 controller.go:177] certificates controller: syncing item 'development/es-cert'
I0705 05:39:07.824866       1 sync.go:239] Preparing certificate development/es-cert with issuer
I0705 05:39:07.824875       1 acme.go:159] getting private key (letsencrypt-staging->tls.key) for acme issuer development/letsencrypt-staging
I0705 05:39:07.825116       1 sync.go:177] Certificate development/my-wildcard-cert scheduled for renewal in 1438 hours
I0705 05:39:07.825136       1 controller.go:191] certificates controller: Finished processing work item "development/my-wildcard-cert"
I0705 05:39:07.825282       1 prepare.go:247] Cleaning up previous order for certificate development/es-cert
I0705 05:39:07.825299       1 prepare.go:263] Cleaning up old/expired challenges for Certificate development/es-cert
I0705 05:39:07.825308       1 logger.go:22] Calling CreateOrder
I0705 05:39:08.267472       1 acme.go:193] Created order for domains: [{dns *.mydomain.ooo}]
I0705 05:39:08.267513       1 logger.go:52] Calling GetAuthorization
I0705 05:39:08.362536       1 logger.go:77] Calling DNS01ChallengeRecord
I0705 05:39:08.362568       1 prepare.go:263] Cleaning up old/expired challenges for Certificate development/es-cert
I0705 05:39:08.362576       1 logger.go:47] Calling GetChallenge
I0705 05:39:08.466710       1 dns.go:78] Checking DNS propagation for "mydomain.ooo" using name servers: [<IP_ADDRESS>:53]
I0705 05:39:08.686376       1 dns.go:85] DNS record for "mydomain.ooo" not yet propagated
E0705 05:39:08.686546       1 sync.go:168] [development/es-cert] Error getting certificate 'es-cert': secret "es-cert" not found
E0705 05:39:08.686932       1 runtime.go:66] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:72
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:65
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:51
/usr/local/go/src/runtime/asm_amd64.s:509
/usr/local/go/src/runtime/panic.go:491
/usr/local/go/src/runtime/panic.go:63
/usr/local/go/src/runtime/signal_unix.go:367
/go/src/github.com/jetstack/cert-manager/pkg/apis/certmanager/v1alpha1/helpers.go:20
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/dns/dns.go:136
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/dns/dns.go:67
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:236
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:173
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:146
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:94
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/sync.go:240
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/sync.go:108
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:215
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:69
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:178
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:183
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:147
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88
/usr/local/go/src/runtime/asm_amd64.s:2337
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
	panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xece4c1]
 goroutine 195 [running]:
github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0)
	/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:58 +0x111
panic(0x13c8d00, 0x1f699d0)
	/usr/local/go/src/runtime/panic.go:491 +0x283
github.com/jetstack/cert-manager/pkg/apis/certmanager/v1alpha1.(*ACMEIssuerDNS01Config).Provider(0x0, 0xc42057c470, 0xa, 0x1f6a550, 0x0, 0x1f7c7b0)
	/go/src/github.com/jetstack/cert-manager/pkg/apis/certmanager/v1alpha1/helpers.go:20 +0x51
github.com/jetstack/cert-manager/pkg/issuer/acme/dns.(*Solver).solverForIssuerProvider(0xc4205f2930, 0xc42057c470, 0xa, 0x134d380, 0xc42005cef0, 0xc4204ad0e0, 0x1f145a0)
	/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/dns/dns.go:136 +0x7a
github.com/jetstack/cert-manager/pkg/issuer/acme/dns.(*Solver).Present(0xc4205f2930, 0x1f145a0, 0xc420afab00, 0xc4202e0680, 0xc42058ae70, 0x6a, 0xc4209be600, 0x5b, 0xc42053fbb0, 0x6, ...)
	/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/dns/dns.go:67 +0x5a
github.com/jetstack/cert-manager/pkg/issuer/acme.(*Acme).presentChallenge(0xc42005f080, 0x1f145a0, 0xc420afab00, 0x1f1c300, 0xc4209aa970, 0xc4202e0680, 0xc42058ae70, 0x6a, 0xc4209be600, 0x5b, ...)
	/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:236 +0x3a1
github.com/jetstack/cert-manager/pkg/issuer/acme.(*Acme).processChallenge(0xc42005f080, 0x1f145a0, 0xc420afab00, 0x1f1c300, 0xc4209aa970, 0xc4202e0680, 0xc42058ae70, 0x6a, 0xc4209be600, 0x5b, ...)
	/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:173 +0xb6
github.com/jetstack/cert-manager/pkg/issuer/acme.(*Acme).presentOrder(0xc42005f080, 0x1f145a0, 0xc420afab00, 0x1f1c300, 0xc4209aa970, 0xc4202e0680, 0xc420476d20, 0x159b3c8, 0x30)
	/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:146 +0x928
github.com/jetstack/cert-manager/pkg/issuer/acme.(*Acme).Prepare(0xc42005f080, 0x1f145a0, 0xc420afab00, 0xc4202e0680, 0x2, 0xc420467998)
	/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:94 +0x3df
github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).issue(0xc4203ee000, 0x1f145a0, 0xc420afab00, 0x1f14860, 0xc42005f080, 0xc4202e0680, 0x0, 0x1ef7920)
	/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/sync.go:240 +0x163
github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).Sync(0xc4203ee000, 0x1f145a0, 0xc420afab00, 0xc4200d2488, 0x1ef7920, 0xc42030e990)
	/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/sync.go:108 +0x385
github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).processNextWorkItem(0xc4203ee000, 0x1f145a0, 0xc420afab00, 0xc4200170a0, 0x13, 0x2, 0x2)
	/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:215 +0x2b5
github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).(github.com/jetstack/cert-manager/pkg/controller/certificates.processNextWorkItem)-fm(0x1f145a0, 0xc420afab00, 0xc4200170a0, 0x13, 0x2, 0x134d380)
	/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:69 +0x52
github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).worker.func1(0xc4203ee000, 0xc420554da8, 0xc4203021e0, 0x134d380, 0xc42052a1c0, 0x0, 0x0)
	/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:178 +0x24f
github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).worker(0xc4203ee000, 0xc4203021e0)
	/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:183 +0x166
github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).Run.func1()
	/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:147 +0x33
github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1(0xc4205e7820)
	/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133 +0x5e
github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc4205e7820, 0x3b9aca00, 0x0, 0x1, 0xc4203021e0)
	/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134 +0xbd
github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait.Until(0xc4205e7820, 0x3b9aca00, 0xc4203021e0)
	/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88 +0x4d
created by github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).Run
	/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:147 +0x182

Environment: I am using AKS

Kubernetes version (use kubectl version): 1.9.6
Cloud provider or hardware configuration**: Azure
Install tools:
Others: using nginx-ingress: quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.13.0

Thanks for the report. Can you share your Certificate and Issuer resources
as well? This should help isolate the issue 😄
On Thu, 5 Jul 2018 at 06:53, Prince Raj<EMAIL_ADDRESS>wrote:

Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT
Uncomment only one, leave it on its own line:
/kind bug
/kind feature
What happened: I tried creating wildcard certificates using image canary.
Cert-manager panics while creating an order for the wildcard certificate.
However, I got the certificate generated for another ingress which request
for the same domain mydomain.ooo (no wildcard).
What you expected to happen: Order gets completed and new wildcard
certificate is created.
How to reproduce it (as minimally and precisely as possible): I
installed cert-manager with static deployment files from : here
https://github.com/jetstack/cert-manager/blob/master/contrib/manifests/cert-manager/without-rbac.yaml.
I am using quay.io/jetstack/cert-manager-controller:v0.3.1 cert-manager
image. Then I created ingress using the following config:
{
"kind": "Ingress",
"apiVersion": "extensions/v1beta1",
"metadata": {
"name": "sub-es",
"namespace": "development",
"annotations": {
"certmanager.k8s.io/acme-challenge-type": "dns01",
"certmanager.k8s.io/acme-dns01-provider": "cloudflare",
"certmanager.k8s.io/issuer": "letsencrypt-staging",
"kubernetes.io/ingress.class": "nginx",
"kubernetes.io/tls-acme": "true"
}
},
"spec": {
"tls": [
{
"hosts": [
"*.mydomain.ooo"
],
"secretName": "es-cert"
}
],
"rules": [
{
"host": "es.mydomain.ooo",
"http": {
"paths": [
{
"path": "/",
"backend": {
"serviceName": "myservice",
"servicePort": 9200
}
}
]
}
}
]
}
}
Anything else we need to know?: Following are the logs from
cert-manager pod:
I0705 05:39:05.888329       1 sync.go:126] Certificate "es-cert" for ingress "sub-es" is up to date
I0705 05:39:05.888346       1 controller.go:166] ingress-shim controller: Finished processing work item "development/sub-es"
I0705 05:39:05.894032       1 controller.go:136] issuers controller: syncing item 'cert-manager/letsencrypt-staging'
I0705 05:39:05.894081       1 acme.go:159] getting private key (letsencrypt-staging->tls.key) for acme issuer cert-manager/letsencrypt-staging
I0705 05:39:05.894446       1 logger.go:67] Calling GetAccount
I0705 05:39:05.894797       1 controller.go:136] issuers controller: syncing item 'development/letsencrypt-staging'
I0705 05:39:05.894825       1 acme.go:159] getting private key (letsencrypt-staging->tls.key) for acme issuer development/letsencrypt-staging
I0705 05:39:05.895176       1 logger.go:67] Calling GetAccount
I0705 05:39:06.529674       1 setup.go:73] letsencrypt-staging: verified existing registration with ACME server
I0705 05:39:06.529731       1 controller.go:150] issuers controller: Finished processing work item "development/letsencrypt-staging"
I0705 05:39:06.555893       1 setup.go:73] letsencrypt-staging: verified existing registration with ACME server
I0705 05:39:06.555926       1 controller.go:150] issuers controller: Finished processing work item "cert-manager/letsencrypt-staging"
I0705 05:39:07.824772       1 controller.go:177] certificates controller: syncing item 'development/my-wildcard-cert'
I0705 05:39:07.824787       1 controller.go:177] certificates controller: syncing item 'development/es-cert'
I0705 05:39:07.824866       1 sync.go:239] Preparing certificate development/es-cert with issuer
I0705 05:39:07.824875       1 acme.go:159] getting private key (letsencrypt-staging->tls.key) for acme issuer development/letsencrypt-staging
I0705 05:39:07.825116       1 sync.go:177] Certificate development/my-wildcard-cert scheduled for renewal in 1438 hours
I0705 05:39:07.825136       1 controller.go:191] certificates controller: Finished processing work item "development/my-wildcard-cert"
I0705 05:39:07.825282       1 prepare.go:247] Cleaning up previous order for certificate development/es-cert
I0705 05:39:07.825299       1 prepare.go:263] Cleaning up old/expired challenges for Certificate development/es-cert
I0705 05:39:07.825308       1 logger.go:22] Calling CreateOrder
I0705 05:39:08.267472       1 acme.go:193] Created order for domains: [{dns *.mydomain.ooo}]
I0705 05:39:08.267513       1 logger.go:52] Calling GetAuthorization
I0705 05:39:08.362536       1 logger.go:77] Calling DNS01ChallengeRecord
I0705 05:39:08.362568       1 prepare.go:263] Cleaning up old/expired challenges for Certificate development/es-cert
I0705 05:39:08.362576       1 logger.go:47] Calling GetChallenge
I0705 05:39:08.466710       1 dns.go:78] Checking DNS propagation for "mydomain.ooo" using name servers: [<IP_ADDRESS>:53]
I0705 05:39:08.686376       1 dns.go:85] DNS record for "mydomain.ooo" not yet propagated
E0705 05:39:08.686546       1 sync.go:168] [development/es-cert] Error getting certificate 'es-cert': secret "es-cert" not found
E0705 05:39:08.686932       1 runtime.go:66] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:72
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:65
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:51
/usr/local/go/src/runtime/asm_amd64.s:509
/usr/local/go/src/runtime/panic.go:491
/usr/local/go/src/runtime/panic.go:63
/usr/local/go/src/runtime/signal_unix.go:367
/go/src/github.com/jetstack/cert-manager/pkg/apis/certmanager/v1alpha1/helpers.go:20
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/dns/dns.go:136
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/dns/dns.go:67
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:236
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:173
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:146
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:94
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/sync.go:240
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/sync.go:108
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:215
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:69
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:178
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:183
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:147
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88
/usr/local/go/src/runtime/asm_amd64.s:2337 http://github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:72/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:65/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:51/usr/local/go/src/runtime/asm_amd64.s:509/usr/local/go/src/runtime/panic.go:491/usr/local/go/src/runtime/panic.go:63/usr/local/go/src/runtime/signal_unix.go:367/go/src/github.com/jetstack/cert-manager/pkg/apis/certmanager/v1alpha1/helpers.go:20/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/dns/dns.go:136/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/dns/dns.go:67/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:236/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:173/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:146/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:94/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/sync.go:240/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/sync.go:108/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:215/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:69/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:178/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:183/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:147/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88/usr/local/go/src/runtime/asm_amd64.s:2337
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xece4c1]
goroutine 195 [running]:github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/runtime.HandleCrash(0x0, 0x0, 0x0)
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/runtime/runtime.go:58 +0x111
panic(0x13c8d00, 0x1f699d0)
/usr/local/go/src/runtime/panic.go:491 +0x283github.com/jetstack/cert-manager/pkg/apis/certmanager/v1alpha1.(*ACMEIssuerDNS01Config).Provider(0x0, 0xc42057c470, 0xa, 0x1f6a550, 0x0, 0x1f7c7b0)
/go/src/github.com/jetstack/cert-manager/pkg/apis/certmanager/v1alpha1/helpers.go:20 +0x51github.com/jetstack/cert-manager/pkg/issuer/acme/dns.(*Solver).solverForIssuerProvider(0xc4205f2930, 0xc42057c470, 0xa, 0x134d380, 0xc42005cef0, 0xc4204ad0e0, 0x1f145a0)
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/dns/dns.go:136 +0x7agithub.com/jetstack/cert-manager/pkg/issuer/acme/dns.(*Solver).Present(0xc4205f2930, 0x1f145a0, 0xc420afab00, 0xc4202e0680, 0xc42058ae70, 0x6a, 0xc4209be600, 0x5b, 0xc42053fbb0, 0x6, ...)
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/dns/dns.go:67 +0x5agithub.com/jetstack/cert-manager/pkg/issuer/acme.(*Acme).presentChallenge(0xc42005f080, 0x1f145a0, 0xc420afab00, 0x1f1c300, 0xc4209aa970, 0xc4202e0680, 0xc42058ae70, 0x6a, 0xc4209be600, 0x5b, ...)
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:236 +0x3a1github.com/jetstack/cert-manager/pkg/issuer/acme.(*Acme).processChallenge(0xc42005f080, 0x1f145a0, 0xc420afab00, 0x1f1c300, 0xc4209aa970, 0xc4202e0680, 0xc42058ae70, 0x6a, 0xc4209be600, 0x5b, ...)
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:173 +0xb6github.com/jetstack/cert-manager/pkg/issuer/acme.(*Acme).presentOrder(0xc42005f080, 0x1f145a0, 0xc420afab00, 0x1f1c300, 0xc4209aa970, 0xc4202e0680, 0xc420476d20, 0x159b3c8, 0x30)
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:146 +0x928github.com/jetstack/cert-manager/pkg/issuer/acme.(*Acme).Prepare(0xc42005f080, 0x1f145a0, 0xc420afab00, 0xc4202e0680, 0x2, 0xc420467998)
/go/src/github.com/jetstack/cert-manager/pkg/issuer/acme/prepare.go:94 +0x3dfgithub.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).issue(0xc4203ee000, 0x1f145a0, 0xc420afab00, 0x1f14860, 0xc42005f080, 0xc4202e0680, 0x0, 0x1ef7920)
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/sync.go:240 +0x163github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).Sync(0xc4203ee000, 0x1f145a0, 0xc420afab00, 0xc4200d2488, 0x1ef7920, 0xc42030e990)
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/sync.go:108 +0x385github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).processNextWorkItem(0xc4203ee000, 0x1f145a0, 0xc420afab00, 0xc4200170a0, 0x13, 0x2, 0x2)
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:215 +0x2b5github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).(github.com/jetstack/cert-manager/pkg/controller/certificates.processNextWorkItem)-fm(0x1f145a0, 0xc420afab00, 0xc4200170a0, 0x13, 0x2, 0x134d380)
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:69 +0x52github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).worker.func1(0xc4203ee000, 0xc420554da8, 0xc4203021e0, 0x134d380, 0xc42052a1c0, 0x0, 0x0)
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:178 +0x24fgithub.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).worker(0xc4203ee000, 0xc4203021e0)
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:183 +0x166github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).Run.func1()
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:147 +0x33github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1(0xc4205e7820)
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:133 +0x5egithub.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait.JitterUntil(0xc4205e7820, 0x3b9aca00, 0x0, 0x1, 0xc4203021e0)
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:134 +0xbdgithub.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait.Until(0xc4205e7820, 0x3b9aca00, 0xc4203021e0)
/go/src/github.com/jetstack/cert-manager/vendor/k8s.io/apimachinery/pkg/util/wait/wait.go:88 +0x4d
created by github.com/jetstack/cert-manager/pkg/controller/certificates.(*Controller).Run
/go/src/github.com/jetstack/cert-manager/pkg/controller/certificates/controller.go:147 +0x182
Environment: I am using AKS

Kubernetes version (use kubectl version): 1.9.6
Cloud provider or hardware configuration**: Azure
Install tools:
Others: using nginx-ingress:
quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.13.0

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jetstack/cert-manager/issues/706, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMbP7EXM-3hNcfhSSF9BshK7RiBUTG-ks5uDanFgaJpZM4VDSPG
.

Thanks for the quick response @munnerz . Here are the resources you asked:
certificate:
Name:         es-cert
Namespace:    development
Labels:       <none>
Annotations:  <none>
API Version:  certmanager.k8s.io/v1alpha1
Kind:         Certificate
Metadata:
  Cluster Name:
  Creation Timestamp:  2018-07-05T05:32:55Z
  Owner References:
    API Version:           extensions/v1beta1
    Block Owner Deletion:  true
    Controller:            true
    Kind:                  Ingress
    Name:                  sub-es
    UID:                   baacdffa-8014-11e8-adbb-2271ac5a1ff1
  Resource Version:        4407799
  Self Link:               /apis/certmanager.k8s.io/v1alpha1/namespaces/development/certificates/es-cert
  UID:                     de856370-8014-11e8-adbb-2271ac5a1ff1
Spec:
  Acme:
    Config:
      Dns 01:
        Provider:  cloudflare
      Domains:
        *.mydomain.ooo
  Common Name:
  Dns Names:
    *.csfunda.ooo
  Issuer Ref:
    Kind:       Issuer
    Name:       letsencrypt-staging
  Secret Name:  es-cert
Status:
Events:
  Type    Reason       Age   From          Message
  ----    ------       ----  ----          -------
  Normal  CreateOrder  37m   cert-manager  Created new ACME order, attempting validation...
  Normal  CreateOrder  37m   cert-manager  Created new ACME order, attempting validation...
  Normal  CreateOrder  36m   cert-manager  Created new ACME order, attempting validation...
  Normal  CreateOrder  36m   cert-manager  Created new ACME order, attempting validation...
  Normal  CreateOrder  35m   cert-manager  Created new ACME order, attempting validation...
  Normal  CreateOrder  35m   cert-manager  Created new ACME order, attempting validation...
  Normal  CreateOrder  35m   cert-manager  Created new ACME order, attempting validation...
  Normal  CreateOrder  34m   cert-manager  Created new ACME order, attempting validation...
  Normal  CreateOrder  33m   cert-manager  Created new ACME order, attempting validation...
  Normal  CreateOrder  31m   cert-manager  Created new ACME order, attempting validation...
  Normal  CreateOrder  29m   cert-manager  Created new ACME order, attempting validation...
  Normal  CreateOrder  23m   cert-manager  Created new ACME order, attempting validation...
  Normal  CreateOrder  18m   cert-manager  Created new ACME order, attempting validation...
  Normal  CreateOrder  13m   cert-manager  Created new ACME order, attempting validation...
  Normal  CreateOrder  8m    cert-manager  Created new ACME order, attempting validation...
  Normal  CreateOrder  3m    cert-manager  Created new ACME order, attempting validation...

issuer:
Name:         letsencrypt-staging
Namespace:    cert-manager
Labels:       <none>
Annotations:  <none>
API Version:  certmanager.k8s.io/v1alpha1
Kind:         Issuer
Metadata:
  Cluster Name:
  Creation Timestamp:  2018-07-03T16:24:55Z
  Generation:          0
  Resource Version:    4161556
  Self Link:           /apis/certmanager.k8s.io/v1alpha1/namespaces/cert-manager/issuers/letsencrypt-staging
  UID:                 9f0d52b2-7edd-11e8-adbb-2271ac5a1ff1
Spec:
  Acme:
    Email<EMAIL_ADDRESS>    Http 01:
    Private Key Secret Ref:
      Key:
      Name:  letsencrypt-staging
    Server:  https://acme-v02.api.letsencrypt.org/directory
Status:
  Acme:
    Uri:  https://acme-v02.api.letsencrypt.org/acme/acct/37710139
  Conditions:
    Last Transition Time:  2018-07-03T16:25:56Z
    Message:               The ACME account was registered with the ACME server
    Reason:                ACMEAccountRegistered
    Status:                True
    Type:                  Ready
Events:                    <none>

It looks like you have not specified any DNS01 configuration on your Issuer resource for the Cloudflare provider.
Take a look at the docs here: http://cert-manager.readthedocs.io/en/latest/tutorials/acme/dns-validation.html for how to do so (specifically, take a look at the example of an Issuer used for DNS01 validations below):
apiVersion: certmanager.k8s.io/v1alpha1
kind: Issuer
metadata:
  name: letsencrypt-staging
  namespace: default
spec:
  acme:
    server: https://acme-staging-v02.api.letsencrypt.org/directory
    email<EMAIL_ADDRESS>
    # Name of a secret used to store the ACME account private key
    privateKeySecretRef:
      name: letsencrypt-staging

    # ACME DNS-01 provider configurations
    dns01:

      # Here we define a list of DNS-01 providers that can solve DNS challenges
      providers:

        - name: prod-dns
          clouddns:
            # A secretKeyRef to a google cloud json service account
            serviceAccountSecretRef:
              name: clouddns-service-account
              key: service-account.json
            # The project in which to update the DNS zone
            project: gcloud-prod-project

        - name: cf-dns
          cloudflare:
            email<EMAIL_ADDRESS>            # A secretKeyRef to a cloudflare api key
            apiKeySecretRef:
              name: cloudflare-api-key
              key: api-key.txt

I have also opened #708 and #709 which will stop this causing a panic in future.
Going to close this issue now as it's a configuration issue, and we have a PR in place to prevent the panic 😄

Hi @munnerz
As pointed by you I am able to generate wildcard certificates. But somehow, the wildcard certificate is not getting used by the ingress. I am not able to access the ingress over https. Let me know what things you need to debug this issue.
Thanks


test

Type: Incorrect
Summary:
test
Details:
test
Resolution:
test
Affected definitions:

toml_edit 0.13.4

You can review the change introduced to the full definition at ClearlyDefined.


feat: Implemented Schema Fetch for MSSQL Plugin (#16014)

Description
Implemented Get Structure for MSSQL Plugin.
Refactored the existing code for MSSQL Plugin. Added the following

MssqlDatasourceUtils - contains the utilities for getting connection, logging Hikari CP Status and getting DB schema structure and templates
MssqlExecuteUtils - contains utilities for populating rows  and columns, and closing connection  after query execution
MssqlTestDBContainerManager - Test helper to create container, datasource configuration and run queries for MSSQL unit tests

PR fixes following issue(s)
Fixes #16014
Media

Type of change

New feature (non-breaking change which adds functionality)
This change requires a documentation update

Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.

[x] Manual
[x] JUnit

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test

/build-deploy-preview

@prapullac @btsgh We'll only be focusing on the schemas for MSSQL here. For Generate CRUD Page, there's a separate issue and will be fixed in that.

Hey @sanveer-osahan
Trying to create a query from the entity explorer does not show an example query.
https://www.loom.com/share/7c5d40b343f84c39af515dc095d823e5

/build-deploy-preview

/ok-to-test


Fix deopt caused by slicing arguments object

Gotta go fast

Awesome, thank you for pointing this out, TIL. :smile:
By the way, I used IRHydra2 to look up the intermediate representations of your proposed change and the following (which omits the length cache):
var values = Array(arguments.length - 1);
for (var i = 1; i < arguments.length; i++) {
  values[i - 1] = arguments[i];
}

Your suggestion and the above were identical, which seems to confirm what is discussed in this post: http://mrale.ph/blog/2014/12/24/array-length-caching.html
All else being equal, I think would prefer omitting the length cache, if you wouldn't mind updating your PR.
Regardless, I'd like to start benchmarking (https://github.com/rtsao/csjs/issues/12) and hopefully identify further optimizations.

Glad you're thinking about that. I was too. I found an old thread from about 2013 saying that preallocating the array doesn't affect performance, but in my testing and many others', it clearly does. It appears that the length access is indeed properly cached in an optimized function. V8 is a fickle yet powerful beast.
I've amended the commit.

By the way, thanks for pointing out IRHydra2. That is seriously, seriously awesome. Been looking for something like this to validate some of my assumptions/guesses.


i18n/add german translation

I find these translation a bit more awkward than #207. However some translations are better in this one so these two translations should probably be compared to improve the final German translation.

Hi @bitgroestl, I merged the other PR for the German translation, but thanks for the PR. Don't hesitate to make a new one if you think translation can be improved :)


Adding $on.hover to Box throws confusing AssertionError

Package version
1.2.0
Flutter version
$ flutter --version
Flutter 3.23.0-13.0.pre.102 • channel master • git@github.com:flutter/flutter.git
Framework • revision cd8e84f465 (5 weeks ago) • 2024-06-05 08:02:53 -0700
Engine • revision 11a32d43e3
Tools • Dart 3.5.0 (build 3.5.0-222.0.dev) • DevTools 2.36.0
Steps to reproduce

Take sample code (using a Box widget) from fluttermix.com
Add $on.hover() declaration to its Style
Run app (app crashes)
Replace Box with PressableBox
Run app again (now it works)

Expected results
The app should render and use the hover effect.
If hover's incompatibility with Box is known and intended, there should be a more helpful error message.
Actual results
══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
The following assertion was thrown building Box(dirty):
Unable to find an instance of PressableState...
'package:mix/src/widgets/widget_state/widget_state.dart':
Failed assertion: line 55 pos 12: 'result != null'

The relevant error-causing widget was:
  Box Box:file:///Users/craiglabenz/Dev/fdr/mix_sample/lib/main.dart:77:12

When the exception was thrown, this was the stack:
#2      WidgetStateModel.of (package:mix/src/widgets/widget_state/widget_state.dart:55:12)
#3      WidgetStateModel.hoverOf (package:mix/src/widgets/widget_state/widget_state.dart:86:12)
#4      OnHoverVariant.when (package:mix/src/widgets/widget_state/widget_state_variant.dart:39:55)
#5      _applyVariants (package:mix/src/core/factory/mix_data.dart:157:35)
#6      applyContextToVisualAttributes (package:mix/src/core/factory/mix_data.dart:142:13)
#7      new MixData.create (package:mix/src/core/factory/mix_data.dart:37:27)
#8      Style.of (package:mix/src/core/factory/style_mix.dart:176:47)
#9      StyledWidget.withMix (package:mix/src/core/styled_widget.dart:52:23)
#10     Box.build (package:mix/src/specs/box/box_widget.dart:53:12)
#11     StatelessElement.build (package:flutter/src/widgets/framework.dart:5690:49)
#12     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:5620:15)
#13     Element.rebuild (package:flutter/src/widgets/framework.dart:5336:7)
#14     ComponentElement._firstBuild (package:flutter/src/widgets/framework.dart:5602:5)
#15     ComponentElement.mount (package:flutter/src/widgets/framework.dart:5596:5)
...     Normal element mounting (7 frames)
#22     Element.inflateWidget (package:flutter/src/widgets/framework.dart:4471:16)
#23     MultiChildRenderObjectElement.inflateWidget (package:flutter/src/widgets/framework.dart:7038:36)
#24     MultiChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:7050:32)
...     Normal element mounting (28 frames)
#52     Element.inflateWidget (package:flutter/src/widgets/framework.dart:4471:16)
#53     MultiChildRenderObjectElement.inflateWidget (package:flutter/src/widgets/framework.dart:7038:36)
#54     MultiChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:7050:32)
...     Normal element mounting (128 frames)
#182    Element.inflateWidget (package:flutter/src/widgets/framework.dart:4471:16)
#183    MultiChildRenderObjectElement.inflateWidget (package:flutter/src/widgets/framework.dart:7038:36)
#184    MultiChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:7050:32)
...     Normal element mounting (188 frames)
#372    Element.inflateWidget (package:flutter/src/widgets/framework.dart:4471:16)
#373    MultiChildRenderObjectElement.inflateWidget (package:flutter/src/widgets/framework.dart:7038:36)
#374    MultiChildRenderObjectElement.mount (package:flutter/src/widgets/framework.dart:7050:32)
...     Normal element mounting (552 frames)
#926    Element.inflateWidget (package:flutter/src/widgets/framework.dart:4471:16)
#927    Element.updateChild (package:flutter/src/widgets/framework.dart:3966:18)
#928    _RawViewElement._updateChild (package:flutter/src/widgets/view.dart:441:16)
#929    _RawViewElement.mount (package:flutter/src/widgets/view.dart:464:5)
...     Normal element mounting (15 frames)
#944    Element.inflateWidget (package:flutter/src/widgets/framework.dart:4471:16)
#945    Element.updateChild (package:flutter/src/widgets/framework.dart:3966:18)
#946    RootElement._rebuild (package:flutter/src/widgets/binding.dart:1605:16)
#947    RootElement.mount (package:flutter/src/widgets/binding.dart:1574:5)
#948    RootWidget.attach.<anonymous closure> (package:flutter/src/widgets/binding.dart:1527:18)
#949    BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:3038:19)
#950    RootWidget.attach (package:flutter/src/widgets/binding.dart:1526:13)
#951    WidgetsBinding.attachToBuildOwner (package:flutter/src/widgets/binding.dart:1265:27)
#952    WidgetsBinding.attachRootWidget (package:flutter/src/widgets/binding.dart:1247:5)
#953    WidgetsBinding.scheduleAttachRootWidget.<anonymous closure> (package:flutter/src/widgets/binding.dart:1233:7)
#957    _RawReceivePort._handleMessage (dart:isolate-patch/isolate_patch.dart:184:12)
(elided 5 frames from class _AssertionError, class _Timer, and dart:async-patch)

Code sample
Code sample
class MixWidget extends StatelessWidget {

  @override
  Widget build(BuildContext context) {
    final style = Style(
      $box.height(100),
      $box.width(300),
      $box.margin(10, 20),
      $box.color.blue(),
      $box.borderRadius(10),
      $box.padding(10),
      $box.border(
        color: Colors.black,
        width: 1,
        style: BorderStyle.solid,
      ),
      $on.hover(
        $box.color.red(),
      ),
    );

    return Box(
      style: style,
      child: const Text('Hello'),
    );
  }
}

Replacing Box with PressableBox helps the app run successfully again, but this currently requires active investigation from a developer to figure out. Also, I'm not actually sure whether that is the correct solution!

@craiglabenz This makes sense. We are looking into ways to apply some of the widget states automatically to the box and merge them. In the meantime, we will definitely improve the error message.


[bug] swc_core / @swc/core version incompatibility

Describe the bug
The SWC plugin fails. I assume the WASM interface changed and somehow the correct versions are not enforced. What is the correction version of the @swc/xxx packages? Could not find a mention of @swc/core in the repo anywhere.
I get<EMAIL_ADDRESS>in our pnpm-lock.yaml.
Caused by:
    0: failed to invoke `/workspaces/product-ui-next/node_modules/.pnpm/@onlook+nextjs<EMAIL_ADDRESS>as js transform plugin at /workspaces/product-ui-next/node_modules/.pnpm/@onlook+nextjs<EMAIL_ADDRESS>    1: failed to run Wasm plugin transform. Please ensure the version of `swc_core` used by the plugin is compatible with the host runtime. See https://swc.rs/docs/plugin/selecting-swc-core for compatibility information. If you are an author of the plugin, please update `swc_core` to the compatible version.

@smndtrl , what version of next are you running? Does it go away if you update next to latest (if possible)?
This seems to happen for versions lower than 14.1 as they seldom break the swc plugin ecosystem

I just discovered that for some reason (probably react compiler) we moved onto the 15 RC branch. My bad! I'll have to wait and see than until onlook can support that because a quick switch of next to 14.2.12 did not resolve it.
Feel free to close


Security vulnerability in 2.6.2 and 2.7.0 Client

Using 2.6.2 client Bouncy castle jar file, an inner jar of pulsar client has some internal transitive dependencies with 1.6.0 version of bouncy castle which is causing the HIGH vulnerabilities.
Using 2.7.0 High vulnerability is removed but it has 1 CRITICAL vulnerability with the new transitive dependency jar (bcprov-ext-jdk15on-1.66.jar

The issue had no activity for 30 days, mark with Stale label.

Closed as stale. Feel free to open a new issue if it's still relevant for maintained versions.
IIRC 2.6.x is end of life and 2.7.5 is the last release of 2.7.x. You can try 2.7.5 to see if it's still an issue.


feat: gRPC and OpenAPI Integration

fixes: #1201

@ssddOnTop This still has an extremely long way to go. So for now, just to minimize PR noise, I will close the PR, but please re-open when you are ready for someone to take a look. Thank you!


chore: OCR page: missing case fixed + file splited

Hi everyone!
Here are some improvements suggested by @monsieurtanuki in #5384.
For part/part of, I prefer this approach, which keeps classes private

Codecov Report
Attention: Patch coverage is 0% with 61 lines in your changes missing coverage. Please review.

Project coverage is 7.26%. Comparing base (4d9c7fc) to head (80c47c9).
Report is 200 commits behind head on develop.

Files
Patch %
Lines

...b/pages/product/edit_ocr/edit_ocr_main_action.dart
0.00%
59 Missing :warning:

..._app/lib/pages/product/edit_ocr/edit_ocr_page.dart
0.00%
2 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           develop   #5395      +/-   ##
==========================================
- Coverage     9.54%   7.26%   -2.28%
==========================================
  Files          325     392      +67
  Lines        16411   20030    +3619
==========================================
- Hits          1567    1456     -111
- Misses       14844   18574    +3730

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


18 03 2021 - Commodities Payout Terms Meeting Minutes

Date
Thursday, 18 03 2021 - 11am ET / 4pm GMT
Untracked attendees

Fullname, Affiliation, GitHub username

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Convene & roll call (5mins)
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
[ ] Approve past meeting minutes
[ ] ISDA ARC Feedback on Frequency & Rounding Proposals - Revisions Needed
[ ] PricingDates Discussion Continued

Decisions Made

[ ] Decision 1
[ ] Decision 2
[ ] ...

Action Items

[ ] Action 1
[ ] Action 2
[ ] ...

WebEx info

Meeting link: https://finos.webex.com/finos/j.php?MTID=m67d73e1fc1592e699f3cf95d4627de8d
Meeting number:<PHONE_NUMBER>
Password: JMrsuEmY376
Call-in:

Join by video system: Dial<EMAIL_ADDRESS>You can also dial <IP_ADDRESS> and enter your meeting number.
Join by phone: +1-415-655-0003 US Toll | +44-20319-88141 UK Toll | Access code:<PHONE_NUMBER>

hi @astonGS, my colleague James will be representing FINOS on today's call. Thank you @mcleo-d !

Hi everyone 👋

hi

hi

Minutes approved.


Document similarity worflow

Pipeline should work as follows:
Process each incoming document: create sentence vectors indices
Store the indices so that it can be re created if the process dies
For each query: compute vector, find k nearest matches irrespective of any threshold and return the ranked result which is   a list of document ids with similarity scores
Fetch the documents from ES and return to DIG UI
If the user chooses a facet, add filter to the list of documents for a query, re rank the results and return to DIG UI. So, if originally we had k documents, adding a facet will always return <= k documents. The facets act as a filter

Updated Pipeline

The followings tasks are done:

Vectorize each sentence using tensorflow
Index the vectors in FAISS index, and store the link in hbase
Able to query  a string and return k similar docs back


Support VS 2017 Net Standard / Net Core Project Types

Currently the Net Standard 1.5 project type is the old json based project type. Is there a roadmap to update to the standard xml .csproj type that Microsoft added in VS 2017?
Are there any plans to transition from packages.config and move to PackageReference?

I have no plans to make this change, but you're more than welcome to propose a pull request. I need to make sure that it remains buildable using the build.bat script.


Rich Text Editor should not destroy markdown

This issue was reported on the Joplin repository but it's not something that we can fix since the change needs to be done on the plugin:
https://github.com/laurent22/joplin/issues/9929

A complete fix for this depends on laurent22/joplin#10315.  The current fix works as long as the typogram does not have leading whitespace.  As a workaround, any non-whitespace character can be added at the beginning of the typogram.

That's great, thanks @cwesson! We'll look at fixing this whitespace issue

Fixed in v1.0.1 with Joplin v3.0.13.


Mediaelement.js only shows "download file"

mediaelement.js is my Player for Stream Live, this work good on: Chrome, IE, Mozilla, but don't work on mobiles.
I would like to get the Flash fallback for mediaelement.js to work, but it only shows a black area saying "download file" in the upper left.
What is mistake on my script or what I need to implement ?
This is my source code:
<head>
	<link rel="stylesheet" href="http://example.com/player/build/mediaelementplayer.css" />
	<link rel="stylesheet" href="http://example.com/player/build/mediaelementplayer.min.css" />
	<script src="http://example.com/player/build/jquery.js"></script>
	<script src="http://example.com/player/build/mediaelement-and-player.js"></script>

	<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.7.1/jquery.min.js"></script>
	<script type="text/javascript" src="http://example.com/player/build/mediaelement-and-player.min.js"></script>
</head>
<body>
<video width="500" height="400" id="player1" src="<?php echo $_GET['v'];?>" type="video/rtmp" controls="controls">
		    <!-- MP4 for Safari, IE9, iPhone, iPad, Android, and Windows Phone 7 -->
            <source type="video/mp4" src="http://mediaelementjs.com/media/echo-hereweare.mp4" />
            <!-- WebM/VP8 for Firefox4, Opera, and Chrome -->
            <source type="video/webm" src="http://mediaelementjs.com/media/echo-hereweare.webm" />
            <!-- Ogg/Vorbis for older Firefox and Opera versions -->
            <source type="video/ogg" src="http://mediaelementjs.com/media/echo-hereweare.ogv" />
        </video>

        <script>$('video').mediaelementplayer({flashStreamer:"rtmp://example.com:1935/live",
		plugins: ['flash', 'silverlight'],
            alwaysShowControls: false,
            success: function (mediaElement, domObject) {
                if (mediaElement.pluginType == 'flash') {
                    mediaElement.play();
                }
            },
    });
</script>
</body>

Thanks in advance for any help!

@floriano12 When you talk about mobile, you mean iOS? Because in order to play RTMP you need Flash and iOS doesn't support it

Thanks, @ron666
tell me please, how can build a player for iOS ?
you can modify my player ?
Thanks in advance !!

@floriano12 There's nothing to do with iOS; you have to switch to HLS in order to support them.

@ron666 and for HLS, you can show me a player... how can build a player for hls ?

@floriano12 Check demo/mediaelementplayer-hls.html. Right now MediaElement can stream HLS. The trick here is how to generate the m3u8 file. My preference is always to use AWS services to do that. Check https://aws.amazon.com/elastictranscoder/ for more information.


Update cbindgen to a version that uses Clap v4+.

Currently cbindgen requires Clap version 3, and this causes cargo deny to throw the following error.
  ┌─ checks/bindings/c/Cargo.lock:2:1
  │
2 │ atty 0.2.14 registry+https://github.com/rust-lang/crates.io-index
  │ ----------------------------------------------------------------- unsound advisory detected
  │
  = ID: RUSTSEC-2021-0145
  = Advisory: https://rustsec.org/advisories/RUSTSEC-2021-0145
  = On windows, `atty` dereferences a potentially unaligned pointer.

    In practice however, the pointer won't be unaligned unless a custom global allocator is used.

    In particular, the `System` allocator on windows uses `HeapAlloc`, which guarantees a large enough alignment.

    # atty is Unmaintained

    A Pull Request with a fix has been provided over a year ago but the maintainer seems to be unreachable.

    Last release of `atty` was almost 3 years ago.

    ## Possible Alternative(s)

    The below list has not been vetted in any way and may or may not contain alternatives;

     - [std::io::IsTerminal](https://doc.rust-lang.org/stable/std/io/trait.IsTerminal.html) - Stable since Rust 1.70.0
     - [is-terminal](https://crates.io/crates/is-terminal) - Standalone crate supporting Rust older than 1.70.0
  = Announcement: https://github.com/softprops/atty/issues/50
  = Solution: No safe upgrade is available!
  = atty v0.2.14
    └── clap v3.2.25
        └── cbindgen v0.26.0
            └── (build) cchecks v0.1.0

Blocked on https://github.com/mozilla/cbindgen/issues/880

Updated cbindgen with new clap version.


Remove delete_recursively

Looks like this was copied from Lwt at some point. It is not used within obuilder currently, nor have I found it used in any of our other projects. And it has since been exposed in Lwt. See https://github.com/ocsigen/lwt/blob/48abed72467ca7479e95f1be06d02f40c7c434bd/CHANGES#L25

I confirm that all these functions can be removed now that they've been exposed from Lwt.

Thank you for the reviews (and for spotting the extra dead code, @punchagan)!

The CI errors are spurious, and recorded in issues.


soc: riscv: Add ability for SOC to use custom sys_io functions

Add Kconfig SOC_HAS_CUSTOM_SYS_IO symbol that an SoC can set to specify that it has a custom implementation for sys_io functions.

we usually prefer to have some kind of z_soc_* overriding functions

Thanks for the hint, I'll try to get this done properly

@ycsin You could check out how LiteX VexRiscv handles it, as it has custom sys_io-style functions implementations: https://github.com/zephyrproject-rtos/zephyr/blob/main/soc/riscv/litex-vexriscv/soc.h

@ycsin You could check out how LiteX VexRiscv handles it, as it has custom sys_io-style functions implementations: https://github.com/zephyrproject-rtos/zephyr/blob/main/soc/riscv/litex-vexriscv/soc.h

yeah no, please don't. Introducing some kind of SoC-specific IO helpers is making all the drivers basically un-portable on any different platform. Better sticking to sys_io functions and override those when needed.

@ycsin You could check out how LiteX VexRiscv handles it, as it has custom sys_io-style functions implementations: https://github.com/zephyrproject-rtos/zephyr/blob/main/soc/riscv/litex-vexriscv/soc.h

I'd say this model should be avoided. If we have SoCs that require custom sys_io functions, we should modify sys_io so that it allows for both, arch-specific and/or soc-specific implementations. sys_io.h header chain is a bit broken, so it may require some prep-work.

I've updated the PR to look something like https://github.com/zephyrproject-rtos/zephyr/commit/43a61329cc454ab318eefffc35f78487ff680be2

we should modify sys_io so that it allows for both, arch-specific and/or soc-specific implementations. sys_io.h header chain is a bit broken, so it may require some prep-work.

you mean we will probably first need some code reorg so that sys_write8 calls arch_sys_write8 which then calls soc_sys_write8 in the end, and allow arch/soc -specific custom implementation to provide _z_soc_sys_* & _z_arch_sys_*?

What about 64-bit operations?

Thanks for the reminder, just added & rebased


Command "ard" is not defined

Describe the bug
When running the drush archive-dump default UI task, the task appears as Succeeded but the info message indicates otherwise: Command "ard" is not defined.
This happens on Drupal 9 projects with drush 10 as the command is no longer available for that version of drush.
To Reproduce
Steps to reproduce the behavior:

Go to any project with drush 10 and any environment, then choose the Tasks tab
Click on Generate database and files backup (Drush 8 only) [drush archive-dump]
Wait and see the task as succeeded
See error message and no link to the archive dump

Expected behavior
As it is a default command from the UI, it should either work as expected or not be there if the project has drush 10.

It seems that there is no archive-dump for Drush 9+
https://github.com/drush-ops/drush/issues/1779
But this comment sounds interesting, maybe it can be ported to Lagoon instead of waiting for Drush to have this feature added back?

Looks like ard isn't coming back anytime soon - we're rewriting tasks to support these situations

and with the benefit of hindsight, maybe it is coming back sometime soon - https://github.com/drush-ops/drush/pull/5148
ard and arr are in Drush 11.1.1 - h/t to @AlexSkrypnyk for the pointer


SPM --parallel test / GH action interaction demo

This PR demonstrates how using swift test --parallel in a GH action can fail.  As you can see, the previous commit in the chain passed CI, but this one, which only adds the --parallel option, fails on both Linux and MacOS.  I believe there's some nondeterminism involved here.

Never intended to be merged


No .jar file in the folder

There is no .jar file that means i cant open the program. Please fix this please.

Check releases.


Unexpected String issue when importing the slider in React (Gatsby)

I'm importing the slider in a statically generated site using default GatsbyJS installation, it's built using React and I'm getting the following error:
Uncaught SyntaxError: Unexpected string - commons.js:54025
It's referring to the following section:
/***/ "./node_modules/ventura-slider/src/tiny-slider.module.js":
/***/ (function(module, exports) {
	// Format: ES MODULE
	// Version: 2.5.2
	// helper functions
	import './helpers/keys';
	import './helpers/childNode.remove';

Any ideas?

Did it say which string is unexpected?

@ganlanyuan I just did a clean install and added the following to the class:
import { tns } from 'tiny-slider/src/tiny-slider.module.js'

The error I get:
Uncaught SyntaxError: Unexpected token {

which refers to:
import { raf } from './helpers/raf.js';

I have no idea what's wrong with "GatsbyJS" or "react", since this is the basic import method in ES6.

Same happens with NextJS7.0.2

A workaround is to use require it inside componentDidMount which isn't that elegant but it works.

Using require brakes tests (with Jest).

Any update on this issue? Next to @a-barbieri temporary solution.

I'm experiencing this issue as well. Maybe the message in the following screenshot helps

I'm experiencing this issue as well. Maybe the message in the following screenshot helps

Same here. Any suggestions how to fix it?

I'm experiencing this issue as well. Maybe the message in the following screenshot helps

Same here.

Yep, same here, be great if we can get a fix for this

The line causing the issue has been removed with this recent commit by the author @ganlanyuan.
@Kevinio04, @Andreew4x4 or @quintmouthaan
Can any of you try the master version?
Just replace the current package.json entry with the master version:
  "dependencies": {
    "tiny-slider": "ganlanyuan/tiny-slider#master"
    // ...
  }

A better option would be to use the current commit so we can better target the problem:
  "dependencies": {
    "tiny-slider": "ganlanyuan/tiny-slider#f6cbe5d"
    // ...
  }

Does it solve the issue? Or does it return something different?

I have the same problem. I update dependency but it didn't solve it. I think this problem more from jest side end rather than react/gatsby or next.js. Maybe there is some issue in executing environment because of jest use jsdom.

It's clear that the error is thrown by the first import hit by the parser. I bet is Node not being able to understand import and Babel not being there to rescue.
I've found serveral articles talking about esm. This might be a quick fix for the server side rendering, but I'm not sure about Jest.
@DranPy Can you try it?
See also this article: How To Enable ECMAScript 6 Imports in Node.JS

Regarding Jest I just found:

https://github.com/facebook/jest/issues/4842
https://github.com/standard-things/esm/issues/706

Where they basically say that import is still somehow problematic in 2019.
This will be solved sometime in the future, but if any feels like trying we could actually make a PR where we replace all those import with require and make sure nothing brakes within the code (I'm referring to any possible ES6 syntax).

@a-barbieri
I'm not sure if I did this in the right way,  but here is what I have. I try to use ESM and info from this https://stackoverflow.com/questions/53095199/node-using-jest-with-esm-package article.
I create two files NewOrder.test.js  and  Exec.test.js with fallow code:
// Exec.test.js const esmImport = require('esm')(module) esmImport('./NewOrder.test.js')
`
// NewOrder.test.js
import React from 'react'
import renderer from 'react-test-renderer'
import { NewOrder } from '../'
describe('', () => {
const wrapper = renderer.create(

)
test('render', () => {
expect(wrapper).toMatchSnapshot()
})
})
Next thing I try to executeExec.test.jstest which in turn have to execute andmockES6 import inComponent.test.jstest file. yarn test Exec.test.jsornpx jest Exec.test.jsornpx test Exec.test.js --env=node`
In every case I get error

Before diving into your code I'd rather know if the example in the link you shared worked also on your machine. Can you replicate it exactly as it is? Then, when we know that it works we can debug your example and see if esm helps.

I heaved that error too Uncaught SyntaxError: Unexpected string  after restart the server the error is gone. But in mi case I implemented in Angular as one Directive:

import { Directive, ElementRef, Input, Output, EventEmitter, OnInit, OnDestroy } from '@angular/core';
import { TinySliderSettings, TinySliderInstance } from 'tiny-slider';
import { tns } from 'tiny-slider/src/tiny-slider';

@Directive({
  selector: '[appTinySlider]'
})
export class TinySliderDirective implements OnInit, OnDestroy {

  __tinySliderInstance: TinySliderInstance;

  @Input() tinySliderSettings: TinySliderSettings = {};

  @Output() tinySliderInstance = new EventEmitter<TinySliderInstance>();

  public constructor(
    private element: ElementRef,
  ) { }

  ngOnInit() {
    this.__tinySliderInstance = this.initSlider(this.tinySliderSettings, this.element);
    this.tinySliderInstance.emit(this.__tinySliderInstance);
  }

  ngOnDestroy() {
    this.__tinySliderInstance.destroy();
  }

  initSlider(settings: TinySliderSettings, elementRef: ElementRef): TinySliderInstance {
    const extendConfig: TinySliderSettings = Object.assign({
      container: elementRef.nativeElement
    },
      settings
    );
    return tns(extendConfig);
  }

}

a

b

c

            "styles": [
              "src/styles.scss",
              "node_modules/tiny-slider/src/tiny-slider.scss"
            ],

Any news about this? I'm having the same issue : (

I have the same issue.
There is a workaround, require tns inside useEffect hook.
const ClientFeedback = () => {   useEffect(() => {     require('tiny-slider/src/tiny-slider').tns({       container: '.client-feedback-slider',       items: 2,       autoplay: true     });   }, []);

I have the same issue.
There is a workaround, require tns inside useEffect hook.
  useEffect(() => {
    require('tiny-slider/src/tiny-slider').tns({
      container: '.client-feedback-slider',
      items: 2,
      autoplay: true
    });
  }, []);

Thanks @bkstorm you are correct this solves the issue when using shallow rendering in enzyme. The error "Cannot use import statement outside a module" is still reported when using mount however -

I was able to solve the issue with import by letting babel transform the module (so I'm assuming you are using babel). From the Jest documentation:
Since all files inside node_modules are not transformed by default, Jest will not understand the code in these modules, resulting in syntax errors.

Jest has the transformIgnorePatterns and this section of the documentation goes in further detail. You have to add the following line to your jest.config.js:
transformIgnorePatterns: ['node_modules/(?!tiny-slider/)'],

Note the regex pattern here: we are letting Jest know that we want to ignore tiny-slider from being ignored (so we are telling Jest: please let babel transform this file for us). If you already ignoring other modules you can just add the module name using a regex or e.g.:
transformIgnorePatterns: ['node_modules/(?!(tiny-slider|my-other-module-to-transform)/)'],

A full example of a jest.config.js file:
module.exports = {
  moduleNameMapper: {
    '\\.scss$': '<rootDir>/test/mocks/styleMock.js',
  },
  coverageThreshold: {
    global: {
      branches: 100,
      functions: 96.67,
      lines: 98.94,
      statements: 99.03,
    },
  },
  transformIgnorePatterns: ['node_modules/(?!tiny-slider/)'],
};

This should make Jest happy again.


[atip][XWALK-3539] Update tizen.py to get user id dynamically

Tizen user can be given by param of lite dynamically.
The default tizen user is app.

LGTM, @cicili please help double check. :)

@Honry @cicili can this pull request be landed? It affects the multi-user tasks.

@chenxix @Honry please add the UT result

Verified on latest testkit-lite(v3.1.13) build, the userID can be achieved sucessfully.

thanks, and LGTM


MissingPluginException : No implementation found

Suddenly, this error appears and happens on android devices only! :
MissingPluginException (No implementation found for method getCurrentPosition on channel flutter.baseflow.com/geolocator).
geo locator version: 8.0.5
what should I do?
I'm trying to clean flutter and get pub then, but the error still appears!

Hi @SalsabeelaHasan,
Are you by any change calling the getCurrentPosition method from an isolate or in the background?

i got same error too, 1 month ago no error appeared, since i opened my project I got exactly like this error. any solution?

Hi @DaffRazan,
Can you answer my question above? Are you calling getCurrentPosition from the background or an separate isolate?

I also got this error while calling the getCurrentPosition inside WorkManager and isolate. If you are required to fetch the location in the background or isolate, you should register the event in the android library or use the background location fetch package.

Please have a look at this comment in issue #1041. This describes the solution for this problem when calling from the background or isolate.


Context: Wayland display

Use wl_shell as of now intstead of xdg client protocol. Due to the wl_shell, physical display geometry cannot be obtained. The geometry is fixed value as of now.

Merge Wayland display


[Monitor Ingestion] Improve input validation/docs

Add another check to see if the user is passing in a string
Include an example in the README about uploading JSON files/strings
Also bumped min python version

Closes: https://github.com/Azure/azure-sdk-for-python/issues/33814

API change check
API changes are not detected in this pull request.


Code actions not making any changes to documents when selected

Thanks very much for an extremely useful product. I have a bit of an exploratory question. I am using Omnisharp on Windows with Emacs:

Operative System: Windows 10
LSP server: Omnisharp 1.39
Emacs: 29.1
Programming language: C# (csharp-mode)

Omnisharp works great except for the code actions. I get a list of code actions but when I select them, nothing happens. I am investigating the issue here: https://github.com/joaotavora/eglot/discussions/1322
What I'd like to know is, are the files modified by Omnisharp or by Emacs on a code action request? I tried debugging, and it seems like the editor is requesting the server for the changes. If that is the case, is there a log in Omnisharp I could consult to see why the files are not changing?
Many thanks for your time,

I created a discussion in reddit to see if I can gather more information on this matter. [1]
[1] https://www.reddit.com/r/emacs/comments/1bawgko/eglot_code_actions_do_not_change_the_buffer/

After a fair bit of debugging with the eglot developer [1], we finally understand the problem a bit better. It seems that Omnisharp is not sending either edit or command in the code actions message. Here is an example message as we see it in Emacs:
(:title "Generate variable 'xConnssole' -> Generate field 'xConnssole'" :kind "quickfix" :diagnostics
               []
               :data
               (:Uri "file:///home/user/dotnet/Program.cs" :Identifier "Generate field 'xConnssole'" :Name "Generate variable 'xConnssole' -> Generate field 'xConnssole'" :Range
                     (:Start
                       (:Line 12 :Character 12)
                       :End
                       (:Line 12 :Character 22))
                     :$$__handler_id__$$ "2e314f16-b735-46d8-ab39-2c20ee0d8960"))

Is there any reason why Omnisharp would do that? I have been reading through the code action spec [2] but unfortunately it isn't obvious if these parameters are mandatory or not.
[1] https://github.com/joaotavora/eglot/discussions/1322#discussioncomment-8833688
[2] https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_codeAction

Same issue for me.
I just mention that with the same OmniSharp the vscode works well...


integrate more features

this plugin:
https://github.com/andrewstuart/vim-kubernetes
is super useful for me, I can apply manifests from unnamed buffers, apply directories

also kubectl diff capability would be nice

option to change namespace

option to change context

option to sort by: creationTimestamp, name, number of containers, status (maybe option to display only failing pod

I haven't looked at the code yet but I believe that if the API is easy to use, I can start submitting PRs to help

Thank you for the suggestions! If you want to help out I'd love that! Unfortunately I'm not super happy with some parts of the code, some is good but others need to be refactored. I'll try to write some docs on the overall structure and try to refactor a bit soon.

this plugin:
https://github.com/andrewstuart/vim-kubernetes
is super useful for me, I can apply manifests from unnamed buffers, apply directories

I'll take a look at that, shouldn't be  too difficult to create an edit and/or apply from a buffer although I'd really like some security measures before that, a confirmation and maybe a kubectl diff (like you suggest in the next bulletpoint) to really make sure we don't ruin anyone's production env 😓

also kubectl diff capability would be nice

This should be pretty straightforward, how do you suggest we do the diff? Current opened buffer using a :Kubectl diff command?

option to change namespace

I started doing that, which wasn't too hard, when I finished, I kind of figured a global filter would add more value, I have a PR up that I'm finishing up soon that allows you to press ctrl-f to filter similar to grep. You can filter on anything here including namespace. Either way, I'll add namespace scope to the TODO list since I guess that's a pretty fundamental feature, just not super high prio when the filter pr gets merged

option to change context

I like that, adding it to the TODO list, what shortcut should we use?

option to sort by: creationTimestamp, name, number of containers, status (maybe option to display only failing pod

I'll add sorting to the TODO list! Would you think that filtering is enough for the failing pods?

I haven't looked at the code yet but I believe that if the API is easy to use, I can start submitting PRs to help

I'd love the help and if you are okay with the code as is then feel free! I would maybe wait for the docs and a bit of refactoring If was you though 😅

Refactoring is sort of done! ofc, can always be improved but I feel that it's pretty nice now.
I'll have to think about what to do with the diff and experiment a bit, I have a cli tool that is called kubediff that sort of does this pretty good but I'm hesitant to add further dependencies, will see how hard it's to do without any additional deps first.

Not sure I'd use a keymap, maybe an ex-command like :Kubectx?

That's a good point, a simple ex-command is probably better!

You could start with that, k9s does it great. More filters could be added in the future

Did a simple sorting by pressing s on a header column, it was easier implementation wise than doing it similar to k9s, not sure if it's better though, what do you think? Good enough?

for the completion, I need to get the kubectl api-resources so I can offer the entire list of resources available, what's the best interface to use to get the api-resources and parse them?
Thanks.

There is two ways you can do it with the current api, first is calling the commands.exec_shell_command(cmd, args) directly or using the resourcebuilders fetch method.
I think for this case, calling it directly is easiest.

[x] this plugin:
https://github.com/andrewstuart/vim-kubernetes
is super useful for me, I can apply manifests from unnamed buffers, apply directories

This is sort of done, apply directories is still tbd but will create a new issue for it!

[x] also kubectl diff capability would be nice
[x] option to change namespace
[x] option to change context
[x] option to sort by: creationTimestamp, name, number of containers, status (maybe option to display only failing pod


bugfix  - typescript code completion doesn't recognize property modifiers when more than one exists

This PR fixes microsoft/TypeScript#37117 (this issue also contains an example of the bug)
This is a simple fix to a simple problem. According to the typescript language service API, the property kindModifiers is comma-separated. Here is the relevant interface:
https://github.com/microsoft/TypeScript/blob/9c4cbd64fb020970f47b4b068f4007810e388a81/src/services/types.ts#L1051-L1054
the problem occurs when more than one modifier exists, and then no modifier is recognized.

Thanks! This is scheduled for VS code 1.45 and will be in the first 1.45 insiders build


RFE: Add plugin to generate snaps

See original issue on GitLab
In GitLab by [Gitlab user @jjardon] on Sep 12, 2018, 15:41
Background
https://snapcraft.io/
Buildstream is able to generate flatpaks at the moment, it would be interesting to be able to also generate snaps with the same metadata
Task description

[ ] Create plugin to deploy snaps

Acceptance Criteria

[ ] It's possible to deploy snaps and flatpaks with the same metadata

In GitLab by [Gitlab user @tristanvb] on Nov 4, 2020, 10:24
This is not the right venue.


schemaStorage(ticdc): remove schemaVersion in schemaStorage

What problem does this PR solve?

Issue Number: close #11868
What is changed and how it works?
This PR removes the SchemaVersion field and its associated logic from the schemaStorage component in TiCDC. The change is part of an effort to remove schema change checking and reduce redundant logic.
Related to #11733.
Check List
Tests

Unit test
Integration test

Questions
Will it cause performance regression or break compatibility?
No.
Do you need to update user documentation, design documentation or monitoring documentation?
No.
Release note
None

/retest

No need to retest. There is indeed an issue here. I will address it after I finish organizing the details of TiCDC and TiDB DDL.


require_paths attribute does not work

https://github.com/bazelruby/rules_ruby/blob/b738b9885f3fba30cbbb6fc05f23ae7a78a4ca84/ruby/private/gemspec/def.bzl#L101 hard codes it to lib.

Yes, it's a known limitation — thank you for taking on the enhancement and let me know if you want any help.
We can remote pair on this if you like.


npc-lib-bukkit + Paper 1.21.1

When importing the API in my project, Intellij Ultimate is screaming a lot.
Every spigot line I get things like this

When compiling, I get a lot of those things:

I'm using those dependencies:
<dependency>
     <groupId>io.papermc.paper</groupId>
     <artifactId>paper-api</artifactId>
     <version>1.21-R0.1-SNAPSHOT</version>
     <scope>provided</scope>
</dependency>
<dependency>
     <groupId>io.github.juliarn</groupId>
     <artifactId>npc-lib-bukkit</artifactId>
     <version>3.0.0-beta8</version>
     <scope>compile</scope>
</dependency>

I don't have those errors when I only have paper.

I just tried to reproduce your setup with the attached gradle build file (I don't use maven anymore) & building and importing works fine for me. Maybe this is just an IJ issue or you're using an incompatible java version for compiling?
plugins {
    id 'java'
}

group = 'dev.derklaro'
version = '1.0-SNAPSHOT'

repositories {
    mavenCentral()
    maven {
        name = "papermc-repo"
        url = "https://repo.papermc.io/repository/maven-public/"
    }
}

dependencies {
    compileOnly("io.papermc.paper:paper-api:1.21-R0.1-SNAPSHOT")
    implementation("io.github.juliarn:npc-lib-bukkit:3.0.0-beta8")
}

java {
    sourceCompatibility = JavaVersion.VERSION_21
    targetCompatibility = JavaVersion.VERSION_21
}

tasks.withType(JavaCompile).configureEach {
    options.encoding = 'UTF-8'
    options.release.set(21)
}

I'm using Java 21

After some tests, if I change the scope to provided, I no longer have errors. But this isn't a solution because the lib in not a plugin on the server.

When adding to exclusions, I no longer get some of the errors:

After some troubles, here is my new dependency in my pom.xml
<dependency>
            <groupId>io.github.juliarn</groupId>
            <artifactId>npc-lib-bukkit</artifactId>
            <version>3.0.0-beta8</version>
            <scope>compile</scope>
            <exclusions>
                <exclusion>
                    <groupId>net.kyori</groupId>
                    <artifactId>adventure-api</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>net.kyori</groupId>
                    <artifactId>examination-api</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>net.kyori</groupId>
                    <artifactId>examination-string</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>org.jetbrains</groupId>
                    <artifactId>annotations</artifactId>
                </exclusion>
            </exclusions>
        </dependency>

Weird. I assume this issue is because the other version is pulled transitevly from a lib in this lib and is marked as a runtime dependency, but I'm confused how maven handles the dependency resolution in that case...

Yeah


Field 'checkoutBrandingUpsert' doesn't exist on type 'Mutation'

Issue summary
Getting  Field 'checkoutBrandingUpsert' doesn't exist on type 'Mutation' when trying to Mutate checkoutBrandingUpsert. using "@shopify/shopify-app-express": "^2.0.0" and "@shopify/shopify-app-session-storage-sqlite": "^1.2.1" packages.
it appears the recent Shopify Checkout updates are not included in the packages I have installed, The mutation works just fine within GraphQL admin API app using 'API Unstable Version' screenshot (https://ibb.co/p0jkw90)
Here is the script using to update Shopify Checkout Branding (colors, fonts.....)
import { GraphqlQueryError } from "@shopify/shopify-api";
import shopify from "./shopify.js";

const CHECKOUT_BRANDING_MUTATION = `
  mutation checkoutBrandingUpsert($checkoutBrandingInput: CheckoutBrandingInput!, $checkoutProfileId: ID!) {
    checkoutBrandingUpsert(checkoutBrandingInput: $checkoutBrandingInput, checkoutProfileId: $checkoutProfileId) {
      checkoutBranding {
        customizations {
          checkbox {
            cornerRadius
          }
        }
      }
    }
  }
`;

export default async function checkoutUpdator(session, data) {
  const client = new shopify.api.clients.Graphql({ session });
  try {
    await client.query({
      data: {
        query: CHECKOUT_BRANDING_MUTATION,
        variables: {
          checkoutProfileId: "gid://shopify/CheckoutProfile/XXXXXXXX",
          checkoutBrandingInput: {
            customizations: {
              checkbox: {
                cornerRadius: "LARGE"
              }
            }
          },
        },
      },
    });
  } catch (error) {
    if (error instanceof GraphqlQueryError) {
      throw new Error(
        `${error.message}\n${JSON.stringify(error.response, null, 2)}`
      );
    } else {
      throw error;
    }
  }
}

/web/package.json
{
  "name": "shopify-app-template-node",
  "version": "1.0.0",
  "private": true,
  "license": "UNLICENSED",
  "scripts": {
    "debug": "node --inspect-brk index.js",
    "dev": "cross-env NODE_ENV=development nodemon index.js --ignore ./frontend",
    "serve": "cross-env NODE_ENV=production node index.js"
  },
  "type": "module",
  "engines": {
    "node": ">=14.13.1"
  },
  "dependencies": {
    "@shopify/shopify-app-express": "^2.0.0",
    "@shopify/shopify-app-session-storage-sqlite": "^1.2.1",
    "compression": "^1.7.4",
    "cross-env": "^7.0.3",
    "serve-static": "^1.14.1"
  },
  "devDependencies": {
    "nodemon": "^2.0.15",
    "prettier": "^2.6.2",
    "pretty-quick": "^3.1.3"
  }
}

/web/frontend/package.json
{
  "name": "shopify-frontend-template-react",
  "version": "1.0.0",
  "private": true,
  "license": "UNLICENSED",
  "scripts": {
    "build": "vite build",
    "dev": "vite",
    "coverage": "vitest run --coverage"
  },
  "type": "module",
  "engines": {
    "node": ">= 12.16"
  },
  "stylelint": {
    "extends": "@shopify/stylelint-polaris"
  },
  "dependencies": {
    "@shopify/app-bridge": "^3.1.0",
    "@shopify/app-bridge-react": "^3.1.0",
    "@shopify/app-bridge-utils": "^3.1.0",
    "@shopify/polaris": "^10.42.0",
    "@shopify/stylelint-polaris": "^9.0.2",
    "@vitejs/plugin-react": "1.2.0",
    "react": "^17.0.2",
    "react-dom": "^17.0.2",
    "react-query": "^3.34.19",
    "react-router-dom": "^6.3.0",
    "vite": "^2.8.6"
  },
  "devDependencies": {
    "history": "^5.3.0",
    "jsdom": "^19.0.0",
    "prettier": "^2.6.0",
    "vi-fetch": "^0.6.1"
  }
}

Error Receiving:
{
  "success":false,
  "error":"GraphQL query returned errors",
  "errors":[
    {
      "message":"CheckoutBrandingInput isn't a defined input type (on $checkoutBrandingInput)",
      "locations":[
        {
          "line":2,
          "column":35
        }
      ],
      "path":[
        "mutation checkoutBrandingUpsert"
      ],
      "extensions":{
        "code":"variableRequiresValidType",
        "typeName":"CheckoutBrandingInput",
        "variableName":"checkoutBrandingInput"
      }
    },
    {
      "message":"Field 'checkoutBrandingUpsert' doesn't exist on type 'Mutation'",
      "locations":[
        {
          "line":3,
          "column":5
        }
      ],
      "path":[
        "mutation checkoutBrandingUpsert",
        "checkoutBrandingUpsert"
      ],
      "extensions":{
        "code":"undefinedField",
        "typeName":"Mutation",
        "fieldName":"checkoutBrandingUpsert"
      }
    },
    {
      "message":"Variable $checkoutBrandingInput is declared by checkoutBrandingUpsert but not used",
      "locations":[
        {
          "line":2,
          "column":3
        }
      ],
      "path":[
        "mutation checkoutBrandingUpsert"
      ],
      "extensions":{
        "code":"variableNotUsed",
        "variableName":"checkoutBrandingInput"
      }
    },
    {
      "message":"Variable $checkoutProfileId is declared by checkoutBrandingUpsert but not used",
      "locations":[
        {
          "line":2,
          "column":3
        }
      ],
      "path":[
        "mutation checkoutBrandingUpsert"
      ],
      "extensions":{
        "code":"variableNotUsed",
        "variableName":"checkoutProfileId"
      }
    }
  ]
}

I wonder if there is a beta package i can use/test the checkoutBrandingUpsert, or any thing else to make it work. We are trying to build the Shopify Checkout Branding App to be able to update the checkout page look and feel that will be potentially used on many clients store to replace the current solution before our changes get deprecated by Aug 2024.
Any help and assistance would be highly appreciated.
Thanks

@ohstable The @shopify/shopify-api package only supports stable API releases, so the checkoutBrandingUpsert is not available via the api.clients.Graphql class.

@mkevinosullivan Thanks for confirmation, any idea when it will be available (included part of stable API)? Thanks


Enhanced version of Help command

Builds on @leighbb's very handy PR #60
My enhancements to it are to change how help is generated.  This is mostly about splitting out arguments and aliases from the help text itself.
There's also one or two minor typos fixed in help text, and some minor modifications in some of the help text messaging.

There's a bug if you use it in BBC BASIC - get gibberish at end of error message if an unknown command is found. Think I know what it is - will fix. Will also add help text for the new SET CONSOLE command for Quark.

cool cool.
I have this merged into the Console8 codebase a little while ago, so it's been getting a bit of use...  there's a bug that @lennart-benschop spotted there with HELP with no argument not working - it reports an error, possibly the same problem you've observed. AgonConsole8/agon-mos#25
I did try to have a look to understand why that bug was happening, but I couldn't work out why - the code looked fine to me. 🤷    Hopefully you'll have more luck @breakintoprogram :grin:

I have this merged into the Console8 codebase a little while ago, so it's been getting a bit of use... there's a bug that @lennart-benschop spotted there with HELP with no argument not working - it reports an error, possibly the same problem you've observed. AgonConsole8/agon-mos#25
I did try to have a look to understand why that bug was happening, but I couldn't work out why - the code looked fine to me. 🤷 Hopefully you'll have more luck @breakintoprogram 😁

Yes, it was returning -1 if it failed, an invalid error code. I've set this to 20 which is (in mos_errors) Invalid Command. It'll output the error automatically. I'll add some belts and braces into the error output code so that doesn't happen.
int mos_cmdHELP(char *ptr) {
	int i;
	int found = 0;
	char *cmd;

	mos_parseString(NULL, &cmd);
	if (cmd != NULL && strcasecmp(cmd, "all") == 0)
		cmd = NULL;

	for (i = 0; i < sizeof(mosCommands) / sizeof(mosCommands[0]); ++i) {
		if (cmd == NULL)
			printCommandInfo(&mosCommands[i]);
		else
			if (strcasecmp(cmd, mosCommands[i].name) == 0) {
				printCommandInfo(&mosCommands[i]);
				found = 1;
			}
	}

	if (cmd != NULL && !found) {
		return 20;
	}
	return 0;


Removing duplicate ->getSettings call

Noticed this was being called twice in the case of a final match.
Doesn’t affect performance much since it’s only called 1 extra time per
lookup (just on the final match).

Thanks. I think this can affect performance a bit in some cases, because not only the settings for the given pattern are searched, but also for all parent levels. Also it's called twice for every wrong match in step one.


knapsack example for python

Description of the change
Contains a simple example of the knapsack problem in python.

Hello @alex-cornejo!
First of all, thank you for taking the time to provide this PR, and my apologies for responding with such delay.
Unfortunately, I cannot accept your PR as is - the knapsack problem is an academic one, and we only provide Quickstarts for problems applied to a particular domain, with domain-specific constraints. (Much like we don't give a TSP Quickstart and instead provide a VRP with time windows.) Also, since Java is the primary language of Timefold Solver, we would also ask you to provide a Java equivalent of the Quickstart.
One way of going forward would be for you to adapt the Quickstart to any of the domains where the knapsack problem is typically used. Use terminology from that domain, use constraints that would reasonably be expected in that domain. And finally supply a Java version as well.
Understanding that this may take more time than you can offer, there is also another option. Take this Quickstart and publish it on your own, perhaps write a social media post about it. We will be happy to share your content on our socials as well, and give you some credit that way.
Do let me know what you've decided to do if anything, and have a good day!

Closing the PR as explained.


Badly need SignalR support in Flutter

I've been working for a few months on a mobile app that requires chat messaging. The backend was developed in Asp.Net Core and utilizes SingalR transport. I tried a few packages on pub.dev and found that signalr_client 0.1.6 works the best of any other available there but still far from good. I had to include the package code into my app project in order to fix a few bugs but still, this is not the right solution.
Due to this situation, my company started to consider the option of abandoning the whole project regardless they like my solution and everything else I've done like scheduling with appointment reminders, progress notes stored in a local, encrypted SQLite database, etc. They don't really care how I make SingalR work 100% reliable, they just want it done. You already have a package to work with a WebSocket server, you have this signalr_client package and I believe it should be a big deal for you to make something good and reliable.

@misici234
a 1st party porting a .net specific library to flutter IMO isn't a realistic expectation
As there are at least two 3rd party plugins available, namely
signalr_core [github] and signalr_client [github]
I recommend to address possible bug or missing feature in the respective github repo
alternatively you might want to take a look to this stackoverflow answer

If flutter plugins are not available for Signalr, you can always use native libraries available for signalr and use flutter's platform channels to use those native features in your flutter code.
Here are some helpful resource that might help
How to use signalr in Android?
https://github.com/Gurgen/SignalR-.net-core-android-client

@misici234
a 1st party porting a .net specific library to flutter IMO isn't a realistic expectation
As there are at least two 3rd party plugins available, namely
signalr_core [github] and signalr_client [github]
I recommend to address possible bug or missing feature in the respective github repo
alternatively you might want to take a look to this stackoverflow answer

If flutter plugins are not available for Signalr, you can always use native libraries available for signalr and use flutter's platform channels to use those native features in your flutter code.
Here are some helpful resource that might help
How to use signalr in Android?
https://github.com/Gurgen/SignalR-.net-core-android-client

@iapicca
I tried all SignalR 3rd party plugins and none of them was reliable enough or didn't work at all. Specifically, the signalr_client is abandoned plugin and signalr_core didn't work for me at all.
To develop native libraries available for SignalR and use Flutter's platform channels is not the point of Flutter development. We don't want to write the same code twice. This can be a temporary solution until the Flutter team produce a permanent solution. There is a growing popularity for SignalR communication and it's high time Flutter provides official support for it.

@iapicca
I tried all SignalR 3rd party plugins and none of them was reliable enough or didn't work at all. Specifically, the signalr_client is abandoned plugin and signalr_core didn't work for me at all.
To develop native libraries available for SignalR and use Flutter's platform channels is not the point of Flutter development. We don't want to write the same code twice. This can be a temporary solution until the Flutter team produce a permanent solution. There is a growing popularity for SignalR communication and it's high time Flutter provides official support for it.

Hi @misici234
I don't think this is something the Flutter team want to address. Flutter team is already maintaining lots of plugins/packages and since the team is small in numbers it is difficult to maintain all those packages/plugins and Flutter itself. I would suggest you to open issues in the mentioned plugin repositories or fork them and make your own version of it.

Hi @misici234
I don't think this is something the Flutter team want to address. Flutter team is already maintaining lots of plugins/packages and since the team is small in numbers it is difficult to maintain all those packages/plugins and Flutter itself. I would suggest you to open issues in the mentioned plugin repositories or fork them and make your own version of it.

Hi @pedromassangocode
I don't agree with you. When I search flutter.dev by word SignalR I get the following Work with WebSockets. Considering the growing popularity of SignalR it makes a lot of sense to add official support for it by the Flutter team. You mentioned that your team is small but I can tell you that I'm the only one developing in Flutter in my mid-size company where all other developers are C#, ASP.NET, in other words Microsoft technology. I managed to introduce Flutter and they were no so happy about it because their preference was Xamarin. Now, I'm in trouble. I told them I can do their mobile app in Flutter but it turned out that I can't because of SignalR. Please, reconsider your priorities and add SignalR in your recent TODO list.

Hi @pedromassangocode
I don't agree with you. When I search flutter.dev by word SignalR I get the following Work with WebSockets. Considering the growing popularity of SignalR it makes a lot of sense to add official support for it by the Flutter team. You mentioned that your team is small but I can tell you that I'm the only one developing in Flutter in my mid-size company where all other developers are C#, ASP.NET, in other words Microsoft technology. I managed to introduce Flutter and they were no so happy about it because their preference was Xamarin. Now, I'm in trouble. I told them I can do their mobile app in Flutter but it turned out that I can't because of SignalR. Please, reconsider your priorities and add SignalR in your recent TODO list.

@misici234
since signalr_client is seamingly abbandoned
what about opeing an issue on signalr_core's [github] and ask to implement the features you are expecting?

@misici234
since signalr_client is seamingly abbandoned
what about opeing an issue on signalr_core's [github] and ask to implement the features you are expecting?

@iapicca
I tested all of them on pub.dev and I couldn't even start a connection using the signalr_core plug-in. This is not about missing features but this is the issue about basic functionality that doesn't work and the plug-in is useless for me. Why don't Flitter team take over any of these plugins and just make them work reliably? This should not take too much time.

@iapicca
I tested all of them on pub.dev and I couldn't even start a connection using the signalr_core plug-in. This is not about missing features but this is the issue about basic functionality that doesn't work and the plug-in is useless for me. Why don't Flitter team take over any of these plugins and just make them work reliably? This should not take too much time.

@misici234

[...] Why don't Flitter team take over any of these plugins and just make them work reliably? This should not take too much time.

the team has a lot on its plate right now, personally I don't see why this should be a priority
it's like asking aspnet team team to officially support a flutter plugin...
probably not their top priority
if you don't want anything to do with the current plugins, not even open an issue in their repo,
as mentioned here, you can create a flutter plugin as follow

implementing the signalR android client and/or swift client (please not that even those plugins aren't 1st party!)
connect the native client to flutter with platform channel

@misici234

[...] Why don't Flitter team take over any of these plugins and just make them work reliably? This should not take too much time.

the team has a lot on its plate right now, personally I don't see why this should be a priority
it's like asking aspnet team team to officially support a flutter plugin...
probably not their top priority
if you don't want anything to do with the current plugins, not even open an issue in their repo,
as mentioned here, you can create a flutter plugin as follow

implementing the signalR android client and/or swift client (please not that even those plugins aren't 1st party!)
connect the native client to flutter with platform channel

@iapicca
In that case, why does the Flutter team support WebSockets? (see Work with WebSockets). As you know, SignalrR supports 3 modes of transport: WS, SSE and LP. What has more value WS or WS, SSE and LP together?
I don't expect the team to provide a solution tomorrow but expect they do it in near future.

@iapicca
In that case, why does the Flutter team support WebSockets? (see Work with WebSockets). As you know, SignalrR supports 3 modes of transport: WS, SSE and LP. What has more value WS or WS, SSE and LP together?
I don't expect the team to provide a solution tomorrow but expect they do it in near future.

Hi,
If you are looking for 100% Reliable messaging, then please check this video, here Brady says that do not use this SignalR when you need 100% reliability.
Hope it clears some thoughts.

Hi,
If you are looking for 100% Reliable messaging, then please check this video, https://youtu.be/YwezzKWrFuo here Brady says that do not use this SignalR when you need 100% reliability.
Hope it clears some thoughts.


Remove dependency on acsoo

manifestoo does everything we need.

This was done in https://github.com/OCA/oca-ci/pull/44