[CT-1445] "Encountered an error: expected dict, got "

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Hi all! Upgraded to 1.3.0, using Homebrew. When running dbt compile to test if all is ok, I get the following - really weird - error:
Encountered an error:
expected dict, got

Yes, with the last sentence unfinished. Check the screenshot in this message as well.
Relevant brew commands:
brew update
brew upgrade dbt-bigquery

Output from dbt debug (sans possibly sensitive information denoted by XXX):
16:23:37  Running with dbt=1.3.0
dbt version: 1.3.0
python version: 3.9.15
python path: /usr/local/Cellar/dbt-bigquery/1.3.0/libexec/bin/python
os info: macOS-12.6-x86_64-i386-64bit
Using profiles.yml file at /Users/kostas/.dbt/profiles.yml
Using dbt_project.yml file at /Users/kostas/repos/bi-roi-dbt/dbt_project.yml

Configuration:
  profiles.yml file [OK found and valid]
  dbt_project.yml file [OK found and valid]

Required dependencies:
 - git [OK found]

Connection:
  method: oauth
  database: XXX-bi-dm-dev
  schema: roi
  location: US
  priority: interactive
  timeout_seconds: 300
  maximum_bytes_billed: None
  execution_project: XXX-bi-dm-dev
  job_retry_deadline_seconds: None
  job_retries: 1
  job_creation_timeout_seconds: None
  job_execution_timeout_seconds: 300
  gcs_bucket: None
  Connection test: [OK connection ok]

Expected Behavior
I was expecting dbt compile in 1.3.0 (dbt-bigquery) to compile a model, as was the case with 1.2.0 I tried just before upgrading.
Steps To Reproduce

Upgrade to 1.3.0 using brew
Run dbt compile

Relevant log output
No response
Environment
- OS: MacOsX
- Python: >3.9
- dbt: 1.3.0

Which database adapter are you using with dbt?
bigquery
Additional Context
No response

community slack thread: https://getdbt.slack.com/archives/CBSQTAPLG/p1666974608072329

@kostasgaridis Could you include the contents of the debug-level logs (either from logs/dbt.log, or by rerunning dbt --debug compile)? That might give us a hint into which file dbt is trying to read when it encounters this error.

@kostasgaridis Could you include the contents of the debug-level logs (either from logs/dbt.log, or by rerunning dbt --debug compile)? That might give us a hint into which file dbt is trying to read when it encounters this error.

Here's the log output. It's rather long and it seems that the whole query I have shows up in there for some reason as unformatted text. This is not the case when I run the same model with dbt core 1.2.2.
dbt-log.txt

Ok! Based on the logs you sent over, it seems like dbt encounters this error while:

parsing through models
without first logging that static parser failed

15:58:22.251155 [debug] [MainThread]: 1699: static parser successfully parsed roi_extra/p0_v3_backup.sql
15:58:22.253442 [debug] [MainThread]: 1603: static parser failed on roi_extra/curve_data_1.sql
15:58:22.260794 [debug] [MainThread]: 1602: parser fallback to jinja rendering on roi_extra/curve_data_1.sql
15:58:22.261860 [debug] [MainThread]: 1699: static parser successfully parsed roi_extra/p1_v3_backup.sql
15:58:22.263946 [debug] [MainThread]: 1699: static parser successfully parsed roi_extra/p2_v3_backup.sql
15:58:22.266120 [debug] [MainThread]: 1699: static parser successfully parsed roi_extra/p0_v2_backup.sql
15:58:22.268366 [debug] [MainThread]: 1699: static parser successfully parsed roi_extra/p2_v4_backup.sql
15:58:22.270811 [debug] [MainThread]: 1699: static parser successfully parsed roi_extra/p3_v2_backup.sql
15:58:22.272938 [debug] [MainThread]: 1699: static parser successfully parsed roi_extra/p1_v4_backup.sql
15:58:22.274529 [debug] [MainThread]: Sending event: {'category': 'dbt', 'action': 'invocation', 'label': 'end', 'context': [<snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x10fe200d0>, <snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x1100ec580>, <snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x1100ec550>]}
15:58:22.274747 [debug] [MainThread]: Flushing usage events
15:58:22.854055 [error] [MainThread]: Encountered an error:
expected dict, got

I'm guessing here, but I think it might mean that py_extract_from_source is failing to return a dictionary here. (That method comes from dbt-extractor, a.k.a. our static parser/analyzer for dbt-Jinja written in Rust.)
https://github.com/dbt-labs/dbt-core/blob/39c5c42215b4d6751e9644324040a1c716742224/core/dbt/parser/models.py#L379-L383
Specifically, that _shift_sources method expects to receive a dictionary, rather than... None?
https://github.com/dbt-labs/dbt-core/blob/39c5c42215b4d6751e9644324040a1c716742224/core/dbt/parser/models.py#L475
Again, I'm guessing here, not totally positive. You might be able to confirm that the static parser is the culprit by disabling it (docs), e.g.
dbt --no-static-parser parse

That would still leave us to figure out exactly which file is tripping up the static parser, and then fixing the logic within dbt-extractor. To do that, we might need you to run an interactive debugger (or access to your project files, so one of us can try).


Certificate Challenges failing with Istio + Istio Gateway when installed via Helm

Bug Description
I have installed Istio on Azure AKS via Helm and Flux. (base, istiod, gateway)
I am currently trying to migrate to Istio Gateway for exposes our applications to the outside world. Currently we do this via Nginx Ingress Controller (and works fine), but when using Istio Gateway we are getting problems when trying to create Certificates for our sub domains.
My scenario is that I'm currently trying to create a Certificate for the a Concourse url e.g. concourse-istio1.tooling.domain.com. (-istio1 is just to test a cert gets created and I can access the URL, I will be switching to a more better named domain when I know this all works)
Without getting into the details of creating Istio Gateways I am following this guide and by the time I even get to the Gateway part, I can see that the Challenge created doesn't work due to error.
Waiting for HTTP-01 challenge propagation: failed to perform self check GET request 'http://concourse-istio1.tooling.domain.com/.well-known/acme-challenge/gW6Ky1oqRmLvAzUw....

Now, I've read a tonne on people having these problems, and they recommended putting general gateways in front of it, which I've done via this
apiVersion: networking.istio.io/v1beta1
kind: Gateway
metadata:
  name: general-gateway
  namespace: istio-system
  labels:
    app: gateway
spec:
  selector:
    istio: gateway
  servers:
    - port:
        number: 80
        protocol: HTTP
        name: http
      hosts:
        - "*"

And got to a point where the error I got was waiting for http-01 challenge propagation: wrong status code '404', expected '200'
I then read more and people described that I had to add a VirtualService that took that challenge verification and directed it to the acme-solver-xxxx like so:
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: http-redirect
  namespace: istio-system
spec:
  gateways:
  - general-gateway
  hosts:
  - '*'
  http:
    - match:
        - uri:
            prefix: /.well-known/acme-challenge/
      route:
        - destination:
            port:
              number: 8089
            host: cm-acme-http-solver-nvcvc.istio-system.svc.cluster.local

Which is a terrible solution for automation as we're expected to know the pod name ahead of time meaning manual intervention (and we want all of this to be done automatically). But the error I get from this is waiting for http-01 challenge propagation: wrong status code 503 expected '200 which I'm assuming is down to some mTLS setting. But again, I don't understand how and why I'm expected to do all of this routing? Especially when the Istio Guide on Cert-manager doesn't include any of the above. I've also read many many examples of multiple people doing multiple things and I've tried many combinations and just cannot get it to work. Many of which are examples on old versions of Istio where stuff like global.k8sIngress.enabled aren't even options anymore as I'm using the newer istio/gateway Helm chart.
Issuer yaml for brevity alongside the certificate.
Certificate
---
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: concourse-ingress-cert
  namespace: istio-system
spec:
  secretName: concourse-ingress-cert
  dnsNames:
  - concourse-istio1.domain.com
  issuerRef:
    name: letsencrypt-prod
    kind: Issuer
    group: cert-manager.io

Issuer
apiVersion: cert-manager.io/v1
kind: Issuer
metadata:
  name: letsencrypt-prod
  namespace: istio-system
spec:
  acme:
    # The ACME server URL
    server: https://acme-v02.api.letsencrypt.org/directory
    # Email address used for ACME registration
    email: blah.com
    # Name of a secret used to store the ACME account private key
    privateKeySecretRef:
      name: letsencrypt-prod
    solvers:
      # An empty 'selector' means that this solver matches all domains
      - selector: {}
        http01:
          ingress:
            class: istio

And IngressClass because apparently I read somewhere I needed it as the old ingress.class annotation is being deprecated.
IngressClass
---
apiVersion: networking.k8s.io/v1beta1
kind: IngressClass
metadata:
  name: istio
  namespace: istio-system
spec:
  controller: istio.io/ingress-controller

Cert-manager HelmRelease
---
apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: HelmRepository
metadata:
  name: jetstack
  namespace: cert-manager
spec:
  interval: 1m
  url: https://charts.jetstack.io
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: cert-manager
  namespace: cert-manager
spec:
  chart:
    spec:
      chart: cert-manager
      sourceRef:
        kind: HelmRepository
        name: jetstack
  interval: 1m
  values:
    version: v1.7.1
    installCRDs: true

Not sure why all of this is getting superfluous, I'm hoping it's a simple thing to do, but at the moment, it seems that there's a lack of documentation on this, (something I'm happy to add - but I need to get it working first) especially in an area that seems to attract so many issues.
EDIT:
I will add the Flux config for how I'm installing Istio, in case there is a config variable I am missing.
HelmRelease for IstioBase and IstioD
---
apiVersion: source.toolkit.fluxcd.io/v1beta1
kind: HelmRepository
metadata:
  name: istio-system
  namespace: istio-system
spec:
  interval: 1m
  timeout: 2m0s
  url: https://istio-release.storage.googleapis.com/charts
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: istio-base
  namespace: istio-system
spec:
  chart:
    spec:
      chart: base
      version: 1.12.2
      sourceRef:
        kind: HelmRepository
        name: istio-system
  interval: 1m
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: istiod
  namespace: istio-system
spec:
  chart:
    spec:
      chart: istiod
      version: 1.12.2
      sourceRef:
        kind: HelmRepository
        name: istio-system
  interval: 1m

HelmRelease for Istio Gateway (Ingress)
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: istio-gateway
  namespace: istio-system
spec:
  chart:
    spec:
      chart: gateway
      version: 1.12.2
      sourceRef:
        kind: HelmRepository
        name: istio-system
  interval: 1m
  values:
    service:
      loadBalancerIP: [our Azure AKS LB Public IP]

Version
> istioctl version
client version: 1.12.2
control plane version: 1.12.2
data plane version: 1.12.2 (32 proxies)

> kubectl version --short
Client Version: v1.21.4
Server Version: v1.21.9

Additional Information
No response

Are you on the latest cert-manager patch release? My understand is this was broken and they reverted the change that made it break.
On the flip side, if Istio implemented https://github.com/istio/istio/issues/36971 this would also just work, even with the "broken" cert-manager versions

Hi Howard, thanks for the quick response.
I've added my HelmRelease for the cert-manager installation. As of yesterday I am using 1.7.1

When its initial failing, do you have any other virtual services or Gateways?
They should not be required - but its possible you have created one that conflicts with what cert-manager is doing.

Nope, no additional Gateways - removed them all. I have also just tried this which I saw you add on #20589 and I get the same 404 error on the challenge that I pasted in the issue description.
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: http-redirect
  namespace: concourse
spec:
  gateways:
  - https-redirect
  hosts:
  - 'concourse-istio1.domain.com'
  http:
  - redirect:
      scheme: https
      redirectCode: 302
---
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: https-redirect
  namespace: istio-system
spec:
  selector:
    istio: gateway
  servers:
  - port:
      number: 80
      name: http
      protocol: HTTP
    hosts:
    - "concourse-istio1.domain.com"
---
apiVersion: networking.istio.io/v1alpha3
kind: Gateway
metadata:
  name: https
  namespace: istio-system
spec:
  selector:
    istio: gateway
  servers:
  - port:
      number: 443
      name: https
      protocol: HTTPS
    hosts:
    - "concourse-istio1.domain.com"
    tls:
      credentialName: concourse-ingress-cert
      mode: SIMPLE
---
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: concourse-virtualservice
  namespace: concourse
spec:
  hosts:
  - "concourse-istio1.domain.com"
  gateways:
  - https
  http:
  - route:
    - destination:
        host: concourse-web
        port:
          number: 80

if you can do istioctl pc all INGRESS_POD_NAME -oyaml and attach it, during the challenge (when Ingress is still there), it could help figure out why we get 404s. I would remove all the extra VS/GWs before doing this to keep things simply.
The workaround above should only be needed if you had httpsRedirect: true on a gateway

sorry run it on the istio-ingressgateway pod, not the solver

Also, is it expected to have a istio sidecar injected to the solver pod? I've seen that in a few other threads and just wanted to double check if that was also something that was supposed to be happening? As the solver pod is in the istio-system namespace I would assume that would be a no

Basically I would expect that from your Issuer, cert-manager creates an Ingress with class: istio. Istio reads that, configures the GW, and everything is happy. No other config needed

Not sure if it's related, but in v1.7 cert-manager is again using the kubernetes.io/ingress.class annotation not the ingressClassName field (see cert-manager#4537).
So the Ingress that cert-manager creates to forward traffic to the solver pod will have the annotation and not the field.
I am not very familiar with Istio ingress controller implementation and the associated custom resources, but tried to create an Issuer and Certificate like in the issue description (without a Gateway). With cert-manager v1.7 and Istio v1.12.2 I observed that Istio ingress controller does pick up the cert-manager's created Ingress (saw Ingresse's status being updated by pilot-discovery and the cert got issued as expected). Also tried with an IngressClass resource being deployed (I believe that's no longer needed when we now use the annotation?), that too seemed to work.

Especially when the Istio Guide on Cert-manager doesn't include any of the above

Could be useful to create a more detailed tutorial on how to use cert-manager with Istio

@irbekrm  Are you using Nginx ingress controller or the Istio Gateway?
I've also noticed that the solver pod itself doesn't have the annotation kubernetes.io/ingress.class: istio, but the solver ingress service does.

@irbekrm Are you using Nginx ingress controller or the Istio Gateway?

istio ingress-gateway controller with a Gateway

I've also noticed that the solver pod itself doesn't have the annotation kubernetes.io/ingress.class: istio, but the solver ingress service does.

Yes, it should the Ingress that should have the annotation, not the pod as you already noticed. I typed the previous comment too quickly :)

Yep, so it seems we both have the same setup. My Istio Gateway is being configured with the public IP of the LB that is assignment to my AKS cluster (the same setup that we had with the Nginx Ingress Controller).
So just sitrep then:

my Istio Gateway is installed created and assigned public IP
cert-manager is installed (successfully as far as I can see) at v1.7.1
no Gateway is created yet here are the route config dumps.

virtualHosts:

domains:

'*'
name: backend
routes:
match:
prefix: /healthz/ready
route:
cluster: agent

virtualHosts:

domains:

'*'
name: backend
routes:
match:
prefix: /stats/prometheus
route:
cluster: prometheus_stats

- I add the issuer in the issue description
- I add the certificate in the issue description
- I see a `certificate`, `certificaterequest`, `order` and `challenge` is created
- the solver ingress service and solver pod are created (svc being annotated with istio ingress class)
- expecting all to be golden but get the `Waiting for HTTP-01 challenge propagation: failed to perform self check GET request ...` error as mentioned in the issue description.

Have edited issue to include how we are installing Istio incase there are some missing configuration options I am not using that I should be

Ok, so I think I may have got somewhere. I realised that I didn't annotate the cert-manager namespace with istio-injection: enabled, so when it was trying to make requests to the solver, it didn't understand where to do. With the cert-manager pods all being stood up with a istio-proxy sidecar, I now get a different error which is Waiting for HTTP-01 challenge propagation: wrong status code '503', expected '200'. I got it above also, but I've currently not got any Gateway resources defined.
Is this correct? Am I now missing something else?

Yep, so it seems we both have the same setup. My Istio Gateway is being configured with the public IP of the LB that is assignment to my AKS cluster (the same setup that we had with the Nginx Ingress Controller). It's worth mentioning that we only have the one public IP, I'm assuming this won't be a problem?

I have the same setup, but on GKE and haven't enabled sidecar injection on any of the namespaces.
I don't think there should be a need to enable sidecar injection for cert-manager to solve the challenge, but might be wrong.
In case of self-check the flow of requests could be something like cert-manager-controller-pod -> your-load-balancer -> cert-manager-created-ingress -> cert-manager-created-solver-service -> cert-manager-created-solver-pod (someone who knows Istio ingress better could correct me if the middle part is not correct).
You could check if you can access the challenge URL from outside the cluster?
Also whether the cert-manager created Ingress has been picked up by Istio ingressgateway, in my case I see
status:
  loadBalancer:
    ingress:
    - ip: <my-load-balancer-ip>

on the ingress.

I can't access the challenge URL from outside the cluster which kind of makes sense as my cert-manager solver ingress has an empty status with no loadBalancer config. So the Ingress isn't being assigned the public lb IP.

Out of curiosity @irbekrm how did you install Istio onto your cluster? Did you do it via Helm or the istioctl? I'm wondering if the helm charts aren't doing something right. I've just removed Istio from cluster completely and started again and I still have issues

Out of curiosity @irbekrm https://github.com/irbekrm how did you
install Istio onto your cluster? Did you do it via Helm or the istioctl?
I'm wondering if the helm charts aren't doing something right. I've just
removed Istio from cluster completely and started again and I still have
issues

I just ran istioctl install (with istioctl version 1.12.2)
On Wed, 16 Feb 2022 at 18:38, Chris Burns @.***> wrote:

Out of curiosity @irbekrm https://github.com/irbekrm how did you
install Istio onto your cluster? Did you do it via Helm or the istioctl?
I'm wondering if the helm charts aren't doing something right. I've just
removed Istio from cluster completely and started again and I still have
issues
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/37329#issuecomment-1042006262, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AF52AT6JWFZ6TKXJ4ICA6RDU3PVKBANCNFSM5OMKC5QA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

I'll try installing with istioctl and see if it makes a difference,

Ok, so, for test purposes, I've completely stripped down the cluster to nothing so that only flux is left.
I've installed Istio with istioctl via istioctl install --set profile=default instead of using the Flux HelmReleases described above and I can confirm that when adding the cert-manager HelmRelease, the Issuer resource and the Certificate that are in the issue description, it all works and the certificate is created successfully. I did see a brief propagation error in the challenge, but that quickly disappeared - which I'm assuming was when Istio picked up the ingress.
I'm going to remove all of the above and go back to barebones cluster again with just Flux. I am then going to attempt it all again, but this time installing via Helm (without flux) and using a different domain in the cert as this one has already been created to see if that works. If it doesn't work then I can safely assume there is either something wrong with the helm chart installation, or there is a configuration option I am not including that the istioctl does with the default profile. If it does work, then I can only conclude that Flux is the problem.

So it seems that there is a problem with the Istio installation with Helm.
When following the Istio Guides on installing Istio and Gateway with Helm
I do the following:

kubectl create namespace istio-system
 helm install istio-base istio/base -n istio-system
helm install istiod istio/istiod -n istio-system --wait
helm install istio-ingress istio/gateway -n istio-system --wait --set service.loadBalancerIP=[OUR PUBLIC LB IP]

I wait for all to be installed.
I then install cert-manager the same way as I did in the previous step (through the cert-manager HelmRelease), I also add the Issuer the same way, as well as the Certificate under a new domain (just bumped up the istio1 -> istio2 like so: concourse-istio2.tooling.domain.com, and I am back to the challenge error as before (Waiting for HTTP-01 challenge propagation: failed to perform self check GET request ...).
@howardjohn  What's your thoughts on this? Do you identify something I am not doing correctly with regards to the Helm installation of Istio in comparison to what the istioctl does? Or is the above enough for a deeper look at what the Helm installation is doing wrong (or not doing in this case)?

Ahhh I think I know what is going on.. thanks for digging into this so much.
Basically for Ingress there is just one class ("Istio"). But there may be
multiple deployments of gateway service/deployment in the cluster, so Istio
needs to know which one should serve Ingress traffic. cert-manager uses
Ingress (although they are working on more native support).
How that is configured is
https://istio.io/latest/docs/reference/config/istio.mesh.v1alpha1/#MeshConfig
ingressService
and ingressSelector. The default istioctl gateway install aligns with the
mesh config default settings, but not when installing through helm that way.
On Wed, Feb 16, 2022 at 12:49 PM Chris Burns @.***>
wrote:

So it seems that there is a problem with the Istio installation with Helm.
When following the Istio Guides
https://istio.io/latest/docs/setup/install/helm/ on installing Istio
and Gateway with Helm
I do the following:

kubectl create namespace istio-system
helm install istio-base istio/base -n istio-system
helm install istiod istio/istiod -n istio-system --wait
helm install istio-ingress istio/gateway -n istio-system --wait
--set service.loadBalancerIP=[OUR PUBLIC LB IP]

I wait for all to be installed.
I then install cert-manager the same way as I did in the previous step
(through the cert-manager HelmRelease), I also add the Issuer the same
way, as well as the Certificate under a new domain (just bumped up the
istio1 -> istio2 like so: concourse-istio2.tooling.domain.com, and I am
back to the challenge error as before (Waiting for HTTP-01 challenge
propagation: failed to perform self check GET request ...).
@howardjohn https://github.com/howardjohn What's your thoughts on this?
Do you identify something I am not doing correctly with regards to the Helm
installation of Istio in comparison to what the istioctl does? Or is the
above enough for a deeper look at what the Helm installation is doing wrong
(or not doing in this case)?
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/37329#issuecomment-1042297378, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXIN6J36OG4BJ7JLNDTU3QEULANCNFSM5OMKC5QA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks for that @howardjohn, with regards to the Helm install, is there a meshConfig value I need to add when doing a Helm install? And would it be on the base, istiod or gateway installation?

Can confirm have got it to work with Helm by adding the following meshConfig settings in the istiod Helm installation:
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: istiod
  namespace: istio-system
spec:
  chart:
    spec:
      chart: istiod
      version: 1.12.2
      sourceRef:
        kind: HelmRepository
        name: istio-system
  interval: 1m
  values:
    meshConfig:
      ingressService: istio-gateway
      ingressSelector: gateway

A bit confusing as when I did a helm show values on the istiod chart, I couldn't see those values at all available. I had to find https://github.com/istio/istio/issues/36444 in order to know how to update the meshConfig.
I will try and connect it up to a running concourse service and will report back if I can access via Chrome.

Awesome! Got it to work.

My only other question is now, when we provision a new cluster and the certificates will be created, if we specify any Gateways for ports 80, 443 etc, will these interfere with those Certificate requests? If so, I can ensure that the certificate requests get created by the Gateways - just want to double check.

No that should be fine. The only issue is if you use httpsRedirect as noted
in one of the issues you linked earlier
On Wed, Feb 16, 2022 at 2:05 PM Chris Burns @.***>
wrote:

Awesome! Got it to work.
[image: image]
https://user-images.githubusercontent.com/29541485/154364989-2be7cfde-03f8-41f2-8de1-059c9004f558.png
My only other question is now, when we provision a new cluster and the
certificates will be created, if we specify any Gateways for ports 80, 443
etc, will these interfere with those Certificate requests? If so, I can
ensure that the certificate requests get created by the Gateways - just
want to double check.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/37329#issuecomment-1042355650, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXIVJPQSUYKKZBNEOY3U3QNRBANCNFSM5OMKC5QA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Awesome. Thanks for your help @howardjohn  do you want me to update any documentation on this? I guess the missing link is the difference between the Helm and istioctl installation. Possibly a note just to say "If you have installed via Helm, you will need to ensure that the meshConfig is configured as expected" ?

It's definitely should be mentioned in documentation, spent 2 days, to figure it out.

Possibly a note just to say "If you have installed via Helm, you will need to ensure that the meshConfig is configured as expected" ?

Having just started with Istio yesterday, and having run into this issue, simply stating in the docs 'ensure that the meshConfig is configured as expected' would not have helped me. I would assume that if I install everything following the docs (using helm), other chapters in the docs (like this) would work out of the box.
Thanks @ChrisJBurns for documenting which settings fixed your problem, as it's still not clear to me what exactly is going wrong.
I needed to translate this into terraform scripts, since that's how we roll. Leaving this here for other users who are using terraform:
resource "helm_release" "istiod" {
  name              = "istiod"
  repository        = "https://istio-release.storage.googleapis.com/charts"
  chart             = "istiod"
  version           = "v1.13.0"
  namespace         = kubernetes_namespace.istio_system.metadata.0.name
  dependency_update = true

  # The following 2 parameters are a fix/workaround for this issue: https://github.com/istio/istio/issues/37329#issuecomment-1042305227
  set {
    name  = "meshConfig.ingressService"
    value = "istio-ingress"
  }
  set {
    name  = "meshConfig.ingressSelector"
    value = "ingress"
  }
}

@howardjohn  Will look to get a PR up when I've got some time and will reference on this issue, otherwise am happy if others want to be me to it :)

this issue helped. thank you for your investigation.
i have a custom deployed ingress gateway and this was not configured in the istio-operator. After reading this issue I've added following entries into the IstioOperator Config:
meshConfig:
ingressClass: istio
ingressControllerMode: DEFAULT
ingressSelector: custom-ingress-gateway-management
ingressService: custom-ingress-gateway-management
It works

Can confirm have got it to work with Helm by adding the following meshConfig settings in the istiod Helm installation:
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: istiod
  namespace: istio-system
spec:
  chart:
    spec:
      chart: istiod
      version: 1.12.2
      sourceRef:
        kind: HelmRepository
        name: istio-system
  interval: 1m
  values:
    meshConfig:
      ingressService: istio-gateway
      ingressSelector: gateway

A bit confusing as when I did a helm show values on the istiod chart, I couldn't see those values at all available. I had to find #36444 in order to know how to update the meshConfig.
I will try and connect it up to a running concourse service and will report back if I can access via Chrome.

What is best practice with multiple ingress gateways?

Does each ingress gateway need to be named the same with same selector but differentiated by namespace?
Do we create separate istiod deployments for each ingress gateway?

See https://istio.io/latest/docs/setup/additional-setup/gateway/. You can either create in same namespace but different selector, or different namespaces. The majority of time you want 1 Istiod : many gateways

See https://istio.io/latest/docs/setup/additional-setup/gateway/. You can either create in same namespace but different selector, or different namespaces. The majority of time you want 1 Istiod : many gateways

In the context of cert manager multiple ingress selectors won't work if the istiod meshConfig.ingressSelector only accepts one value.
I've tried namespace per istio ingress with same selector and that doesn't appear to work with cert manager via http-01 solver, the resulting Ingress resource just never binds to an IP.  I'm sure I'm doing something wrong but I can't find a working example of this scenario anywhere.

Uhhh life-saver. Just pay attention that by default helm (1.16) comes with
ingressSelector:  ingress

Not sure if there's something that's changed, but this solution did not work for me, and unless I'm mistaken information hasn't been added to the docs regarding this (as suggested above), and one needs to sort through multiple possible issues in this thread to come to the same conclusion.
Are we required to have the global gateway, as in the original post, or no? How might I be able to create a minimum reproducible setup of this working? Is this pattern on a whole not advised? As the configuration for this has already caused quite a headache for me.
Thanks for the detail in this thread, by the way, it's nice to see the issue explored as thorough as it was, but for a new user like me who just wants to have a cert-manager setup work the same way as other ingress controllers, this is a lot to deal with.

Confirming the findings of @afreemanio, these steps no longer work.


Java applet for File upload

http://www.java2s.com/Code/Java/Database-SQL-JDBC/InsertpicturetoMySQL.htm
We just need to apply our DB structure and modify class.


Binder Error: Table "iceberg_scan_deletes" does not have a column named "file_path"

I am using flink to write data into iceberg table, here's table definition and testing data
CREATE TABLE test (
id INT,
name STRING,
PRIMARY KEY(`id`) NOT ENFORCED
) WITH (
'connector' = 'iceberg',
'catalog-name'='hadoop_catalog',
'catalog-type'='hadoop',
'warehouse'='s3a://umbrella/hadoop/warehouse',
'table-name' = 'test',
'format-version'='2',
'write.upsert.enabled'='true'
);

INSERT INTO test VALUES (1, 'A'), (2, 'B'), (3, 'C');

In duckdb side, It could successfully read iceberg data from s3
D select * FROM iceberg_scan('s3://umbrella/hadoop/warehouse/default_database/test');
┌───────┬─────────┐
│  id   │  name   │
│ int32 │ varchar │
├───────┼─────────┤
│     1 │ A       │
│     2 │ B       │
│     3 │ C       │
└───────┴─────────┘

Then update record whose id = 3 by using upsert in flink
INSERT INTO test /*+ OPTIONS('upsert-enabled'='true') */ VALUES (3, 'C-C')

But I got ' Binder Error: Table "iceberg_scan_deletes" does not have a column named "file_path" ' when querying it again in duckdb
D select * FROM iceberg_scan('s3://umbrella/hadoop/warehouse/default_database/test');
Binder Error: Table "iceberg_scan_deletes" does not have a column named "file_path"

I am using flink-1.18.1 + iceberg-1.5.2 + duckdb-1.0.0, I suppose this is caused by version compatibility ? What's the recommanded iceberg version in duckdb-1.0.0 ? Thanks!

I am using AWS Firehose to write to Iceberg tables. It uses Iceberg V2. I get the same error when I read the table with DuckDB


Implement sortKeyDesc method

This pull request implements #21 with the following syntax:
$table->integer('price')->sortKeyDesc();

$table->sortKeyDesc('column');

$table->sortKeyDesc(['column1', 'column2']);

Also, thank you so much for sending in this PR! I really appreciate it. I am planning on spending some time with the Laravel connector next week to finalize this and other open issues. Will make sure to get this in asap.

@carlsverre Updated! I'm not really a fan of adding it as an argument since the second argument is the index name. If I want to set the index and the direction without changing the name, I will always need to use named arguments or skip the second one:
$table->sortKey(columns: 'name', direction: 'desc');

// OR

$table->sortKey('name', null, 'desc');

@carlsverre After I saw the code again, I noticed the fluent API was not working correctly, and the index name parameter was not being used. So I removed the index name parameter for the shard & sort key and fixed the fluent API to support the 'desc' parameter:
$table->sortKey('price', 'desc');

$table->integer('price')->sortKey('desc');


📕 How to install latest version and ControlNet to Google Drive

Please select drive from switch branches/tags

https://www.youtube.com/watch?v=njW64feGMzI

🚨 Important for 15G Free Google Drive Users:
If you want to use more models, you can download your model into Colab, which has an empty 50GB space.
Download models into /content and add --ckpt-dir /content at the end of the launch.py line

thanks to twitter@muadoyoki ❤

You can disable extension updates by adding the # character in front of the git -C pull line, like this:

This means you will not receive extension updates and the startup time will be faster.

hello，why it runs without launch.py
Status Legend:
(OK):download completed.
sed: can't read /content/drive/MyDrive/stable-diffusion-webui-colab/stable-diffusion-webui/launch.py: No such file or directory
sed: can't read /content/drive/MyDrive/stable-diffusion-webui-colab/stable-diffusion-webui/launch.py: No such file or directory
/content/drive/MyDrive/stable-diffusion-webui-colab/stable-diffusion-webui
python3: can't open file '/content/drive/MyDrive/stable-diffusion-webui-colab/stable-diffusion-webui/launch.py': [Errno 2] No such file or directory Installed


Allow setting ConnectDial on context

Allows the OnRequest handlers to hijack the ConnectDial function to dynamically set a destination, similar to the functionality available for hijacking the RoundTripper for non-CONNECT requests.

Looks good.
Will the go 1.14 prevent older go versions from using goproxy?

@elazarl
Hi,can you continue to merge this? This is a good feature for setting different proxy for CONNET method :)

@elazarl I have tested it with go 1.17.9(go version go1.17.9 linux/amd64), it works fine.
Please  review or think about this PR again? This is a key feature for case when making goproxy as a proxy gateway(forward to different upstream proxy) :)

@xzycn thanks. Can you check why the CI failed?

@elazarl Ther eare three tests failed when build in my fork. But the build status is "success".

@elazarl These tests have the same result in current master. So I think this PR is OK.

@elazarl Meanwhile,I build with go 1.17,and get the same result ("success"),afterall, this PR dosen't use any new breaking grammar :)

Is this feature still required or the configurable function ConnectDialWithReq satisfies the purpose of this one? It can do different stuff based on the passed request


sesman does not add groups when using ldap

My configuration is as follows:

Ubuntu 14.04.2
OpenLDAP Client

I'm authenticating using a server in the local network and defined some groups to add to the ones provided by ldap by modifying /etc/security/group.conf.
Then I added auth     required      pam_group.so use_first_pass to /etc/pam.d/common-auth (using pam-auth-update and the right config file in /usr/share/pam-configs).
Loggin in locally or remotely with ssh results in groups being added but using xrdp no group is added. Here is my xrdp-sesman:
#%PAM-1.0
@include common-auth
@include common-account
@include common-session
@include common-password

IIRC, pam_group is bugged with policykit
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1281700

Thank you, I had indeed some problem with policykit and now I know why. Have also found some workaround to a couple (but not all) of my problems. Still, what is happening with sesman is a little bit different. Even if policykit is bugged and ldap users were not considered, when ssh-ing into my machine calling id would show the groups, even id username is working fine. With sesman groups are not added at all. Probably this is related to policykit, I do't know, and in such case there is nothing you can do about it. Still I wanted to stress this since sesman is the only pam module that "seems" to ignore the pam_group directive (even though in my case it doesn's do any good because of that bug...). Anyway thanks for your help.

Not a xrdp issue, closing.


Merge #2669 (swayfmt replacement PR) with master including newline formatting fixes

This is a second attempt at #2695 now that #2697 has landed.

OK! cc @eureka-cpu @kayagokalp I think this should be ready to merge into #2669 and should resolve those conflicts.


Feline breakage with 'dev' branch merge

Feline integration still looking for catppuccin/core/color_palette.lua after the dev merge which changes that code.

#133 should fix it.

Raised #137 instead. cc @Pocco81

Not anymore! :tada:


Snapping mechanism notebook

Don't merge yet -- I'll update further after core and core-python PRs go through

@ctcovington What is the state of this notebook? Happy to handle Smartnoise renaming ports or any other necessary lifting.

I think it's ready to go if you think it is. It's a bit sparse, but I can't think of anything else I'd add.

Notebook work moved to an OpenDP library issue: https://github.com/opendp/opendp/issues/389


Remove "x" button is big

Remove "x" button is big. I think it would be good if it's smaller and placed at the right. But I'm still not familiar with Blender panel layout so I'm happy if Blender addon masters help me.

icon="               x" :D


Parts of package manager UI not localized

Tested with French language.
Available, Installed, Loaded
Licensing warning + Do not show this again checkbox
Labels in the details page

No repro in latest build:


KeyboardAvoidingView does not work

When adding a KeyboardAvoidingView it does nothing because the onLayout that sets the frame-ref is never called.

This is fixed in the new bindings currently being worked on (bs-react-native-next / #344).


Stateful Behaviour: Scenarios Wrong Documentation example

Hello @tomakehurst,
I'm trying to use the Stateful Behaviour feature using json setup, and trying to follow the example from the documentation, but was not working as expected:

First of all putting the mappings in the same file would return always the same request - the first mapping;
if in different files the first step is skipped when doing playback - made it work if  first step had a newScenarioState set, and second step/state is linked to the first one - not to Started state: guess is pretty trivial if you are thinking to a state machine, but many might get stuck trying the example as is; these changes made the example work:

mapping_1.json file
{
    "scenarioName": "To do list",
    "requiredScenarioState": "Started",
    **"newScenarioState": "Missing link",**
    "request": {
        "method": "GET",
        "url": "/todo/items"
    },
    "response": {
        "status": 200,
        "body" : "<items><item>Buy milk</item></items>"
    }
}

mapping_2.json file
{
    "scenarioName": "To do list",
    **"requiredScenarioState": "Missing link",**
    "newScenarioState": "Cancel newspaper item added",
    "request": {
        "method": "POST",
        "url": "/todo/items",
        "bodyPatterns": [
            { "contains": "Cancel newspaper subscription" }
         ]
    },
    "response": {
        "status": 201
    }
}

mapping_3.json file
{
    "scenarioName": "To do list",
    "requiredScenarioState": "Cancel newspaper item added",
    "request": {
        "method": "GET",
        "url": "/todo/items"
    },
    "response": {
        "status": 200,
        "body" : "<items><item>Buy milk</item><item>Cancel newspaper subscription</item></items>"
    }
}

Thanks for provinding to the world this awsome tool 👍

Hmm, now I get it, we have a more linear approach, put in the scenario only the requests with the exactly same body, the requests that are altering the resources state are different, as request body, anyway; so we wanted to solve only the order of these same requests problem - the POSTs are not in the scenario.
Thanks!


Switching channels not working

After installing Flutter via the tap flutter channel dev isn't working to switch to dev channel. Seems like Flutter requires to have these channel branches checked out in the cloned repository.

brew untap MiderWong/flutter
brew tap MiderWong/flutter
brew install --devel flutter


Localization verbiage issue with RegisterWithoutUsername View

I noticed when displaying the "return View("RegisterWithoutUsername")" view, localization was not being applied correctly.
I believe this is due to the "RegisterWithoutUsername.en" file missing?
When I added that to the project it fixed the language translation issue on that page.
Just wanted to add this incase anyone else experience similar issues.
Thanks

Great catch! 👍🏼
You can copy all resx files called Register.cshtml and rename then to RegisterWithoutUsername.
Can you send a PR for this?
Thanks

Fixed in master. Thanks👍🏼


ENS name support

Is your feature request related to a problem? Please describe.
It will be clear and user-friendly to show the ENS domain name in the place of the wallet address.
Describe the solution you'd like
using ethers we can resolve domain names from addresses.

#823


m.emote message does not parse links

Sending the message:
/me wants to go to [the park](https://thepark.com) today

has a hyperlink on Riot web but not in Riot android, even though formatted_body contains a <a> tag.

Done

Actually emote message wasn't able to display any formatted element (bold, italic, link, etc.) due to this bug

You will be able to go to the park fix the fix :)

Hooray, thanks Benoit!


leftNav menu broken between 14.0-rc2 and 14.0 release

I was working with a private build of 14.0-rc2, and after today's update, the left nav menu in my app has broken. I get the change/toggle event but I can't seem to make the menu visible.
I noticed menuItems has been deprecated in some places, but I'm not using that method afaik.
I did notice a few warnings that

Required prop index was not specified in MenuItem.

so I added these. however, this is for a LeftNav, where the menu "items" are basically buttons which don't have indexes afaik in the sense of menu items in a dropdown.
I'm also not clear about the best way to pass events from the new MenuItems. I was creating a subcomponent for each MenuItem so it can have its own props, but this is very verbose.
I'm looking at the code for the docs site, and this seems to use
  onItemTouchTap={(e, child) => this.history.push(child.props.value)}
for the menu itself. Is this also supported for LeftNav menus?
The params I get to the function are empty (when using 14.0-rc2 so I can see the menu)
AppLeftNav = React.createClass({

  navItems: [
    { route: '/', text: 'Home' },
    { route: '/players', text: 'Players' },
    { route: '/interchat', text: 'InterChat' },
    { route: '/topiclist', text: 'Topiclist' },
    { route: '/logtable?topic=greeting', text: 'Logtable' },

    { route: '/lessons', text: 'Lessons' },
    { route: '/kbase', text: 'KBase' },
    // { route: '/logreview', text: 'LogReview (old)' },
    { route: '/admin', text: 'Admin' }
  ],

  getInitialState: function() {
    return {
      open: false
    };
  },

  closeMenu() {
    this.setState({open: false});
  },

  // this has no visible effect but I see the log
  handleToggle() {
    this.setState({open: !this.state.open});
    Logger.log('LeftNav.handleToggle > ', this.state.open);
  },

  // all the params are null
  handleTap(evt, p1, p2) {
    console.log('click item > ', evt, p1, p2, this.value, this.props );
  },

  navigate(evt, p1, p2) {
    console.log('navigate', evt, p1, p2);
  },

  getNavButtons() {
    let that = this;
    return this.navItems.map( item => {
      // return <NavButton text={item.text} route={item.route} key={item.text} menuContainer={that} />;
      return (
        <MenuItem primaryText={item.text} value={item} key={item.text} index={1} />
      );
    });
  },

  render() {
    return (
      <LeftNav
        open={this.state.open}
        docked={false}
        onRequestChange={open => this.setState({open})}
        onItemTouchTap={this.handleTap}
      >
        {this.getNavButtons()}
      </LeftNav>
    );
  }

});

and MainLayout

MainLayout = React.createClass({

  //....

  showLeftMenu() {
    Logger.log('show left', this.refs.leftNav);
    this.refs.leftNav.handleToggle();
  },

  render() {
    return (

        <AppLeftNav
          ref='leftNav'
        />

        <AppBar
          title={AppConfig.pageName}
          onTouchTap={this.showLeftMenu}
        />

          {this.props.content}

    );
  },

});

@dcsan I have just tried the source code you are providing to reproduce the issue.
Here is my result:

Looks like it's working fine.

sorry for troubling you and thanks for checking. it turns out I had to update the package within a meteor package...


keybase on windows not working for some users

Found that deleting line that says keybase_binary = "keybase" on windows allows mwc713 to start listening.

Under "wallet config" I had to enter a valid path into the "keybase console client path" field.  Because the default keybase install puts the files under \AppData\keybase, and AppData is hidden by default, I had to go in through file explorer and "unhide" the directory, then add it into the "keybase console client path" using the "select" button.  Adding the path manually through cut and paste didn't seem to work.

Thanks for the details Jim.

I believe it's fixed here: https://ftp.mwc.mw/nightly_builds/11-12-2019/
Jim is confirming.

Jim confirmed it was fixed in nightlys.

Issue sounds like closed


Option to suppress colourized output

By default unimport will emit ascii colour codes in output, it'd be nice to have a way to suppress this.  I realize there's a check to see if the terminal supports colourized output, but there are also times when you want to explicitly suppress the colourization so that (as an example) you can locally redirect the output to a file and process that file via another script.

Yes good point, I will work on that.

Hi, can you try the version of 0.9.4?
check it out -> https://unimport.hakancelik.dev/#color

Works perfectly, thanks very much!


Plugin not showing up

Forgive me if i'm dumb, but is there any gimp version requirement ?
I'm on Ubuntu 22.10 gimp 2.10.32 plugin is in ~/.config/GIMP/2.20/plug-ins but i got no menu entry at all.

Do you have GIMP with python support? (You should see Filters>Python-fu>Console in the menu)
Does the plugin file stable-gimpfusion.py have executable flag? (chmod +x ~/.config/GIMP/2.20/plug-ins/stable-gimpfusion.py)
Is the plugin folder that you are using (~/.config/GIMP/2.20/plug-ins) listed in the GIMP's plug-ins folders? (Edit>Preferences>Folders>Plug-Ins)

Do you have GIMP with python support? (You should see Filters>Python-fu>Console in the menu)

I was todays days old to learn Ubuntu dropped python2 support so i have to use the flatpack version.

Yep, MacOS Gimp still has python2 bundled

It should now work in OSX.
Can you please update the plugin and check? @kav


Add ability to export presets

I've recently reinstalled the VS and must manually reconfig my CoCo presets. As the theme options grow, there should be a way to export and import preset files.

must manually reconfig my CoCo presets

After updating CoCo automatically upgrade your settings to a new version if it has a something changes, so you actually do not need to change your existing presets, because they must work as is.
Do you mean that you want extend existing presets with a new custom settings for a new added classifications? If so, you can apply existing preset, set options for a new classifications and save the current state as preset.
Currently CoCo doesn't have a way to export|import settings from UI, but settings are stored in the %localappdata%\CoCo\CoCo.config and you can copy|insert presets from it

This is exactly what I want, just this! No need for a UI function

I got it.

You should put this in the readme

I will add it into the readme for the next release, or maybe earlier


[DOC] update doc for 2408 release [skip CI]

This PR updates download docs for 24.08.0 release.

build

@jlowe @sameerz can you please help review?

build


Particle systems have issues when moved, also wrong order with map tiles

Map tiles are being displayed in an incorrect order.  The rows are reversed.
See https://playcanv.as/p/d48QShHE/
And here for more info ( https://forum.playcanvas.com/t/particle-system-change/9582/4?u=mal_duffin )
Also, when moving the particle system, there are lots of glitches ( parts of the particle system are in the wrong place ).
See https://playcanv.as/p/d48QShHE/
And here for more info ( https://forum.playcanvas.com/t/particle-system-change/9582/5?u=mal_duffin )

Hi @e-strokov, I can confirm that your pull request fixes the order of the rendering ( I checked out the branch, and ran it using the local engine option ) - nice one!.
It doesn't however fix the glitches when moving particle systems.  Click on the Add button when running the example project to see this second issue ( your pull request mentioned that it'll close this issue, when the second issue is still there )

Just a heads up that the moving bug hasn't been fixed, so the issue hasn't been resolved yet.
Here's a video showing the issue ( I tried with a number of branches, including the latest master and the new particle-emitter-space branch ).
https://drive.google.com/file/d/1YdLjVFPnL8rRcu1VpRSPsnnSFA5Jc7e_/view
In the video you're seeing two explosions on-screen at the one time ( one is like a ghost ).
You should only be seeing one explosion.

What're your thoughts on this, @e-strokov?

I've noticed two issues here...
Press Add a few times, and keep an eye on the added number system.  Rather than starting at 1 and ending at 64, it starts at 57 and ends at 56. ( 57... 64, 1.. 57 ).
Also, it's still not placing the particles in the right place.  The actual locations of the particle systems seems to be worse now than before! ( I've placed 4 red dots to indicate the position the particle systems will be randomly added to, when you press the ADD button ).

Hi @malDuffin, I submitted a fix to Particles System yesterday. It's appeared that the bug is platform specific. Could you take a look if any of problems you mentioned are resolved? Unfortunately, I can't reproduce them.
Thanks.

Hi @e-strokov,
I tried the example project, and the issue with moving still isn't fixed.
I've looked into the example, and have tried to narrow down the issue.
If you load the new project and run it, then press the button in the top corner, you should notice that there are two particle systems that get spawned ( a yellow one, and a white one ).
https://playcanvas.com/editor/scene/733096
These two particle systems are identical (cone was duplicated from the other ), other than one has a yellow tint, and is slightly scaled up.
The other difference is the lifetime.  Yellow has a lifetime of 5, and the white as a lifetime of 1.
When you press the button, you'll notice that the Yellow one appears correctly at one of the 4 red dots.
The white doesn't appear in the correct slot.  However, if you set the lifetime to 5 on white, it does appear at the right location most of the time!
Somehow, the lifetime value is causing an issue ( there may be other issues ).
If white disappears, and doesn't re-appear after clicking for ages, just refresh the page and try again.  It seems to randomly appear and disappear sometimes.
Hopefully showing this quirk will help identify the moving issue.
Note that the particle index starting at the lower row ( in this case row 7: tile 57, instead of row 0: tile 0) is also visible here, but that's a separate issue.

Hi @malDuffin,
So far I could only reproduce last issue (animation frame). But this might be platform specific (I'm testing on Mac). So, may I ask you to switch Sort mode to Camera Distance? Please let me know if this resolves other problems. Thank you.

Hi @e-strokov, with the Sort mode set to any of the three options other than None, the positioning of the particle system seems fixed.
On Mac, it might be worth you running Bootcamp to be able to debug the problems on Windows also.

Hi @malDuffin, there is yet another branch with particles changes
https://github.com/playcanvas/engine/tree/particle-refactor
could you take a look if any of your issues being resolved?
Thanks.
Evgeny

Nice one @e-strokov - that seems to have solved the issues!

Fantastic! 🎉


k8s: Add Helm chart for Vitess

@thompsonja
This is mostly a direct translation of examples/kubernetes,
which I expect can be replaced by this after some more tweaks
and doc updates.
In particular, this still does not use new features like Deployment,
and tablets are not protected by any controllers. I plan to start
incorporating these new features, potentially as options so this chart
can still work on clusters that don't have k8s Alpha features enabled.

@viglesiasce This is a first pass at something we'd like to submit to kubernetes/charts when it's ready. We'd appreciate any comments you have.

No Orchestrator?

@thompsonja Ah I forgot about that. I'll add it in.

@thompsonja PTAL

As a general comment, how does this work? I'm unfamiliar with Helm. Is this essentially templating, so that users can take the Chart and the values YAML file and generate the appropriate configs, or do users use this directly to bring up instances?

@thompsonja A Helm chart is a group of Kubernetes configs, generated by templates, with the ability to embed sub-charts (we're not using that feature yet) to model dependency relationships.
The overall goal of this chart for Vitess is that most users shouldn't need to write their own k8s configs. We should allow them to just customize/override values.yaml to get what they need.

@thompsonja Sorry, I missed the other half of your question. Users would directly use helm install to bring up this chart, after having used helm init to launch the server side of Helm into the Kubernetes cluster. The server side provides some benefits over a simple client-side template rendering system, such as versioning and rollback of chart instantiations (called "releases").

LGTM in general, my plan is to have end to end tests describe a test setup and then generate a site-values.yaml file on the fly, that should work well with this. I'll let you know how well it works out and then we can deprecate the various yaml files.

Hey @enisoc! Sorry for the delay in taking a look. I have been at Kubecon this week, so will try to get to this in the next 2 days.

@viglesiasce Thanks for offering to look. I'm going to go ahead and merge what I have so far, but I'll be watching this PR for any comments once you have time. The plan is to iterate on this in the Vitess repo before we try to submit to kubernetes/charts.


Docs: Update  developer guide to include make dev troubleshoot notice

While following the developer guide, I noticed make dev outputs a bad file descriptor error. I did some troubleshooting and noticed it was a result of a UNIX settings under the hood.
So basically, OS (mac included) have settings that limit the number of files and processes that are allowed to be open. On mac, it’s set too low which automatically leads to errors such as bad file descriptor or too many files open.
To fix the issue, I used the ulimit shell command to increase the number of files/processes allowed on my machine.

For mac, the limit is 256 which seems too little.
But regardless, great point! @eh-am
Maybe doubling the initial number might be the best case here?

Looks great! Minor tweak to wording but after that we can merge unless @petethepig has any objections


Add code skeleton, setup config and do some cleanup

Pull Request Test Coverage Report for Build 37

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

Totals

Change from base Build 36:
0.0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls

@EdDev please review

@EdDev You can squash them before merging (click on dropdown button on "Merge").

@phoracek We use "rebase" in this project, please do not create PR/s with multiple commits. The only way to squash the two commits is to do it manually.

@EdDev done


Enable the Accessors implementations for global attributes.

Problem
https://github.com/project-chip/connectedhomeip/pull/12808 added declarations but not definitions.
Change overview
Add definitions.
Testing
Code inspection.

fast track: missing delta from previous change.


Allow running cli commands without db connection

Creating the app context requires connecting to the db (if a db feature is enabled). If no db is running, the cli will not run. We have a couple options:

Can we create the db connection pool (sql, redis, etc) without needing for it to be able to actually connect to the db?
If (1) is not possible, we can add a method to the RunCommand trait that runs right after the app config is parsed (and tracing is initialized) and before the app context is created.

This can also impact commands implemented by services, eg, the openapi command. It would be good if the openapi command could be run without needing to start the db

Can we create the db connection pool (sql, redis, etc) without needing for it to be able to actually connect to the db?

I don't think this is currently possible with seaorm, but I think it is with sqlx, so we may be able to submit a PR to seaorm to enable this behavior.

Opened a PR on SEA ORM: https://github.com/SeaQL/sea-orm/pull/2268

We'll need to do the same thing for https://github.com/film42/sidekiq-rs, if possible

For redis/sidekiq, we need to move the "stale cleanup" behavior out of the "build" method so it runs after the service is built and after the "handle cli" method is run against the services.

This should be a quick fix once https://github.com/SeaQL/sea-orm/pull/2268 is merged.

The seaorm team is taking a while to look at the proposed pr above.
An alternative could be to use a OnceLock to lazy init the db connection?

Hmm, the problem with OnceLock is the db connection creation can return an error, so we would need to add a layer of checks everywhere the db connection is requested.


.NET Core + Mono Side-by-Side: 'Microsoft.NET.Sdk' specified could not be found.

I'm running into the common The SDK 'Microsoft.NET.Sdk' specified could not be found error on Arch Linux (Manjaro) - the same error apparently as #3287, #3160, #2356, #2937, and others.
I suspect my case is different. I worked on a .NET Core game for a while, then installed godot-mono, which includes Mono; when I came back to .NET Core, I get this error.
I suspect that VS Code finds the Mono runtime/SDK first, and then says "whelp there's no .NET Core SDK installed for that" and fails hard. I hesitate to uninstall Godot and verify that this works, because I really do need both working side-by-side.
Is this an impossible/unsupported configuration?
OmniSharp log
OmniSharp server started with Mono 6.0.0.
    Path: /home/nightblade/.vscode/extensions/ms-vscode.csharp-1.21.3/.omnisharp/1.34.3/omnisharp/OmniSharp.exe
    PID: 8134

[info]: OmniSharp.Stdio.Host
        Starting OmniSharp on manjaro 0.0 (x64)
[info]: OmniSharp.Services.DotNetCliService
        DotNetPath set to dotnet
[warn]: OmniSharp.MSBuild.Discovery.Providers.MonoInstanceProvider
        It looks like you have Mono 5.2.0 or greater installed but MSBuild could not be found.
Try installing MSBuild into Mono (e.g. 'sudo apt-get install msbuild') to enable better MSBuild support.
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 1 MSBuild instance(s)
            1: StandAlone 16.0 - "/home/nightblade/.vscode/extensions/ms-vscode.csharp-1.21.3/.omnisharp/1.34.3/omnisharp/.msbuild/Current/Bin"
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        MSBUILD_EXE_PATH environment variable set to '/home/nightblade/.vscode/extensions/ms-vscode.csharp-1.21.3/.omnisharp/1.34.3/omnisharp/.msbuild/Current/Bin/MSBuild.dll'
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: StandAlone 16.0 - "/home/nightblade/.vscode/extensions/ms-vscode.csharp-1.21.3/.omnisharp/1.34.3/omnisharp/.msbuild/Current/Bin"
            CscToolExe = csc.exe
            TargetFrameworkRootPath = /usr/lib/mono/xbuild-frameworks
            MSBuildToolsPath = /home/nightblade/.vscode/extensions/ms-vscode.csharp-1.21.3/.omnisharp/1.34.3/omnisharp/.msbuild/Current/Bin
            CscToolPath = /home/nightblade/.vscode/extensions/ms-vscode.csharp-1.21.3/.omnisharp/1.34.3/omnisharp/.msbuild/Current/Bin/Roslyn
            BypassFrameworkInstallChecks = true
            MSBuildExtensionsPath = /usr/lib/mono/xbuild
[info]: OmniSharp.Cake.CakeProjectSystem
        Detecting Cake files in '/home/nightblade/code/ali-the-android'.
[info]: OmniSharp.Cake.CakeProjectSystem
        Could not find any Cake files
[info]: OmniSharp.MSBuild.ProjectSystem
        Detecting projects in '/home/nightblade/code/ali-the-android/AliTheAndroid.sln'.
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/home/nightblade/code/ali-the-android/AliTheAndroid/AliTheAndroid.csproj'
[info]: OmniSharp.MSBuild.ProjectManager
        Queue project update for '/home/nightblade/code/ali-the-android/AliTheAndroid.Tests/AliTheAndroid.Tests.csproj'
[info]: OmniSharp.Script.ScriptProjectSystem
        Detecting CSX files in '/home/nightblade/code/ali-the-android'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Could not find any CSX files
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0
[info]: OmniSharp.MSBuild.ProjectManager
        Loading project: /home/nightblade/code/ali-the-android/AliTheAndroid/AliTheAndroid.csproj
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.RenameWorkspaceOptionsProvider, Order: 100
[info]: OmniSharp.WorkspaceInitializer
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.EditorConfigWorkspaceOptionsProvider, Order: 200
[info]: OmniSharp.WorkspaceInitializer
        Configuration finished.
[info]: OmniSharp.Stdio.Host
        Omnisharp server running using Stdio at location '/home/nightblade/code/ali-the-android' on host 8000.
[warn]: OmniSharp.MSBuild.ProjectManager
        Failed to load project file '/home/nightblade/code/ali-the-android/AliTheAndroid/AliTheAndroid.csproj'.
/home/nightblade/code/ali-the-android/AliTheAndroid/AliTheAndroid.csproj(1,1)
Microsoft.Build.Exceptions.InvalidProjectFileException: The SDK 'Microsoft.NET.Sdk' specified could not be found.  /home/nightblade/code/ali-the-android/AliTheAndroid/AliTheAndroid.csproj

Environment information
VSCode version: 1.38.1
C# Extension: 1.21.3
Mono Information
        OmniSharp using global mono :6.0.0
Dotnet Information
.NET Core SDK (reflecting any global.json):
 Version:   2.2.108
 Commit:    33ed5b90ce
Runtime Environment:
OS Name:     manjaro
OS Version:
OS Platform: Linux
RID:         arch-x64
Base Path:   /opt/dotnet/sdk/2.2.108/
Host (useful for support):
Version: 2.2.6
Commit:  7dac9b1b51
.NET Core SDKs installed:
2.2.108 [/opt/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.NETCore.App 2.2.6 [/opt/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

csharp
ms-vscode
1.21.3

godot-tools
geequlim
0.3.7

mono-debug
ms-vscode
0.15.8

python
ms-python
2019.9.34911

vscode-nxunit-test-adapter
wghats
0.1.2

vscode-test-explorer
hbenl
2.14.6

I've run into this issue with Manjaro Linux fully updated (Arch based).
I've MonoDevelop installed, working fine with Mono.
I wanted to try dotnet core, so I downloaded & installed it created the expected symbols in .bashrc. These are the last two lines.
export DOTNET_ROOT=$HOME/bin/dotnet
export PATH=$PATH:$HOME/bin/dotnet

...which seem to work fine:
$ echo $DOTNET_ROOT
/home/baltasarq/bin/dotnet
$ echo $PATH
/home/baltasarq/bin/google-cloud-sdk/bin:/home/baltasarq/.local/bin:/home/baltasarq/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/bin:/home/baltasarq/.local/share/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/baltasarq/.local/share/flatpak/exports/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/baltasarq/bin/node/bin:/home/baltasarq/bin/dotnet:/home/baltasarq/bin/node/bin:/home/baltasarq/bin/dotnet

$ dotnet --info
.NET Core SDK (reflecting any global.json):
 Version:   3.0.100
 Commit:    04339c3a26

Runtime Environment:
 OS Name:     manjaro
 OS Version:
 OS Platform: Linux
 RID:         linux-x64
 Base Path:   /home/baltasarq/bin/dotnet/sdk/3.0.100/

Host (useful for support):
  Version: 3.0.0
  Commit:  7d57652f33

.NET Core SDKs installed:
  3.0.100 [/home/baltasarq/bin/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.App 3.0.0 [/home/baltasarq/bin/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 3.0.0 [/home/baltasarq/bin/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

I can create a hello world dotnet application with:
$ dotnet new console --name HelloApp
$ cd HelloApp
$ dotnet run
Hello World!

Since I wanted to try Visual Studio Code and .NET Core, I installed Visual Studio Code:
$ yay -S visual-studio-code-bin
... which worked flawlessly.
The problem is when I try to open the folder of the app HelloApp created before, then OmniSharp steps in and fails.
OmniSharp server started with Mono 6.0.0.
    Path: /home/baltasarq/.vscode/extensions/ms-vscode.csharp-1.21.3/.omnisharp/1.34.3/omnisharp/OmniSharp.exe
    PID: 26562

[warn]: OmniSharp.MSBuild.Discovery.Providers.MonoInstanceProvider
        It looks like you have Mono 5.2.0 or greater installed but MSBuild could not be found.
Try installing MSBuild into Mono (e.g. 'sudo apt-get install msbuild') to enable better MSBuild support.
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Located 1 MSBuild instance(s)
            1: StandAlone 16.0 - "/home/baltasarq/.vscode/extensions/ms-vscode.csharp-1.21.3/.omnisharp/1.34.3/omnisharp/.msbuild/Current/Bin"
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        Registered MSBuild instance: StandAlone 16.0 - "/home/baltasarq/.vscode/extensions/ms-vscode.csharp-1.21.3/.omnisharp/1.34.3/omnisharp/.msbuild/Current/Bin"
            CscToolExe = csc.exe
            TargetFrameworkRootPath = /usr/lib/mono/xbuild-frameworks
            MSBuildToolsPath = /home/baltasarq/.vscode/extensions/ms-vscode.csharp-1.21.3/.omnisharp/1.34.3/omnisharp/.msbuild/Current/Bin
            CscToolPath = /home/baltasarq/.vscode/extensions/ms-vscode.csharp-1.21.3/.omnisharp/1.34.3/omnisharp/.msbuild/Current/Bin/Roslyn
            BypassFrameworkInstallChecks = true
            MSBuildExtensionsPath = /usr/lib/mono/xbuild
Microsoft.Build.Exceptions.InvalidProjectFileException: The SDK 'Microsoft.NET.Sdk' specified could not be found.  /home/baltasarq/tmp/HelloApp/HelloApp.csproj
[fail]: OmniSharp.MSBuild.ProjectManager
        Attempted to update project that is not loaded: /home/baltasarq/tmp/HelloApp/HelloApp.csproj

I've looked for a solution in the form of a framework selector or "PATH to dotnet" or similar configuration, unfortunately to no avail.
Since OmniSharp's output suggest to install msbuild for Linux, I also tried that, uninstalled the extension and installed it back again. Unofrtunately, that did not solve anything.

Microsoft.Build.Exceptions.InvalidProjectFileException: The SDK 'Microsoft.NET.Sdk' specified could not be found.  /home/nightblade/code/ali-the-android/AliTheAndroid/AliTheAndroid.csproj
PLS ADD THE FILE:
omnisharp.json  :
{
"MSBuild": {
"UseLegacySdkResolver": true
}
}
https://github.com/OmniSharp/omnisharp-vscode/issues/3287#issuecomment-536180721

PLS ADD THE FILE:
omnisharp.json :

Whoa, this actually worked for me. Thanks for the suggestion!
Just to be clear: I add this file to all my .NET Core projects, because by default, VSCode will find my Mono SDK, correct? (Or, another way to say this: don't add it for Mono projects.)

Okay, it seems it is not clear that I'm a newbie with Visual Studio Code. Where do I have to put that file?

@Baltasarq I just created a new file in the root of my project (the folder that you pick in VSCode when you pick "Open Folder" - in my case, it's the project root, and the one with a .git subdirectory).

Well, that's why I tried for starters, anyway.
I am afraid it does not work for me:
[~/tmp/HelloApp] $ ls
bin  HelloApp.csproj  obj  omnisharp.json  Program.cs
[~/tmp/HelloApp] $ cat omnisharp.json
{
    "MSBuild": {
        "UseLegacySdkResolver": true
    }
}

My "project" is so simple that it only has one folder. The one I obtained by calling dotnet new console --name HelloApp, which is the very same folder that I opened with Visual Studio Code.
No luck.

@Baltasarq this might be a long shot, but can you clone this repo, open the root folder, and tell me if it works for you or not? I tried it on two installs (one with Mono, one without) and Omnisharp loads fine in both.
https://github.com/deengames/ali-the-android

Thanks nightblade9!
Yep, I cloned your repo, but unfortunately the problem still exists, nothing new.

@Baltasarq it might be something environmental in your case. By comparing your logs to mine, I can see that my logs report this:
[info]: OmniSharp.MSBuild.Discovery.MSBuildLocator
        MSBUILD_EXE_PATH environment variable set to '/home/nightblade/.vscode/extensions/ms-vscode.csharp-1.21.3/.omnisharp/1.34.3/omnisharp/.msbuild/Current/Bin/MSBuild.dll'

You may want to try setting that environment variable to see if that fixes the problem.

Yep, I have a similar line in O#'s output.

Yep, I have a similar line in O#'s output.

pls reference to
https://github.com/OmniSharp/omnisharp-vscode/issues/3290#
direct to answer:
As a workaround, you can:
Linux/MacOS #3289 (comment) (install Mono 6.0.0 or newer)
Windows #3289 (comment) (install VS 2019) or #3289 (comment) (instal MsBuild Tools 2019)
edit:
For Windows there is also a new OmniSharp build with a fix.
To try it, add the following to your VS Code settings and restart VS Code:
"omnisharp.path": "1.34.4-beta.7"

This will download the latest prerelease OmniSharp to your VS Code and hopefully help. Thanks.
see https://github.com/OmniSharp/omnisharp-vscode/issues/3290#issuecomment-534537270
Same issue, I know that it can be fixed by installing visual studio 2019, but if you don't want install full VS2019, you can just install standalone build tools from VS2019, for me it resolved issue:
see https://github.com/OmniSharp/omnisharp-vscode/issues/3290#issuecomment-534539294
maybe helpful for you.

Can you upgrade to 1.34.4 and see if that helps?

I'm afraid nothing changed.
VSCode reports:
Version: 1.38.1
Commit: b37e54c98e1a74ba89e03073e5a3761284e3ffb0
Date: 2019-09-11T13:30:08.229Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Linux x64 4.19.69-1-MANJARO

Omnisharp reports:
Name: C#
Id: ms-vscode.csharp
Description: C# for Visual Studio Code (powered by OmniSharp).
Version: 1.21.4
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-vscode.csharp

Again, the project compiles and run with "dotnet run", even from the terminal embedded inside Visual Studio Code.
[~/tmp/HelloApp] $ cat Program.cs
using System;

namespace HelloApp
{
    class Program
    {
        static void Main(string[] args)
        {
            Console.WriteLine("Hello World!");
        }
    }
}
[~/tmp/HelloApp] $ dotnet run
Hello World!

Okay, this is new.
Just to remember the configuration of the (default) console project.
[~/tmp/HelloApp] $ cat HelloApp.csproj
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp3.0</TargetFramework>
  </PropertyGroup>

</Project>

I browsed the configuration and found a combo box for when to use mono or not. Set it to "never", hoping that it would make Omnisharp use only the dotnet installation. Unfortunately, this did not work out as expected. Also, it would be great to be able to make it work with mono.
Omnisharp started with promising results:```
Starting OmniSharp server at 10/8/2019, 9:30:15 AM
Target: /home/baltasarq/tmp/HelloApp
OmniSharp server started.
Path: /home/baltasarq/.vscode/extensions/ms-vscode.csharp-1.21.4/.omnisharp/1.34.4/run
PID: 18058
    Starting OmniSharp on manjaro 0.0 (x64)

    DotNetPath set to dotnet

    Located 1 MSBuild instance(s)
        1: StandAlone 16.0 - "/home/baltasarq/.vscode/extensions/ms-vscode.csharp-1.21.4/.omnisharp/1.34.4/omnisharp/.msbuild/Current/Bin"

    MSBUILD_EXE_PATH environment variable set to '/home/baltasarq/.vscode/extensions/ms-vscode.csharp-1.21.4/.omnisharp/1.34.4/omnisharp/.msbuild/Current/Bin/MSBuild.dll'

    Registered MSBuild instance: StandAlone 16.0 - "/home/baltasarq/.vscode/extensions/ms-vscode.csharp-1.21.4/.omnisharp/1.34.4/omnisharp/.msbuild/Current/Bin"
        MSBuildExtensionsPath = /usr/lib/mono/xbuild
        BypassFrameworkInstallChecks = true
        CscToolPath = /home/baltasarq/.vscode/extensions/ms-vscode.csharp-1.21.4/.omnisharp/1.34.4/omnisharp/.msbuild/Current/Bin/Roslyn
        CscToolExe = csc.exe
        MSBuildToolsPath = /home/baltasarq/.vscode/extensions/ms-vscode.csharp-1.21.4/.omnisharp/1.34.4/omnisharp/.msbuild/Current/Bin
        TargetFrameworkRootPath = /usr/lib/mono/xbuild-frameworks

So, it apparently uses an existing MSBuild inside Omnisharp (instead of the one in the dotnet installation), and then goes back to mono and its `xbuild` in order to find extensions and frameworks...

After some more initializations, the first warning appears, and then fails immediately:

    Failed to load project file '/home/baltasarq/tmp/HelloApp/HelloApp.csproj'.

/home/baltasarq/tmp/HelloApp/HelloApp.csproj(1,1)
Microsoft.Build.Exceptions.InvalidProjectFileException: The imported project "/usr/lib/mono/xbuild/15.0/Microsoft.Common.props" was not found. Confirm that the path in the  declaration is correct, and that the file exists on disk.  /home/baltasarq/bin/dotnet/sdk/3.0.100/Sdks/Microsoft.NET.Sdk/Sdk/Sdk.props
at Microsoft.Build.Shared.ProjectErrorUtilities.ThrowInvalidProject (System.String errorSubCategoryResourceName, Microsoft.Build.Shared.IElementLocation elementLocation, System.String resourceName, System.Object[] args) [0x00040] in :0
at Microsoft.Build.Shared.ProjectErrorUtilities.VerifyThrowInvalidProject[T1] (System.Boolean condition, System.String errorSubCategoryResourceName, Microsoft.Build.Shared.IElementLocation elementLocation, System.String resourceName, T1 arg0) [0x00003] in :0
at Microsoft.Build.Shared.ProjectErrorUtilities.ThrowInvalidProject[T1] (Microsoft.Build.Shared.IElementLocation elementLocation, System.String resourceName, T1 arg0) [0x00000] in :0
at Microsoft.Build.Evaluation.Evaluator4[P,I,M,D].ExpandAndLoadImportsFromUnescapedImportExpression (System.String directoryOfImportingFile, Microsoft.Build.Construction.ProjectImportElement importElement, System.String unescapedExpression, System.Boolean throwOnFileNotExistsError, System.Collections.Generic.List1[Microsoft.Build.Construction.ProjectRootElement]& imports) [0x0060f] in :0
at Microsoft.Build.Evaluation.Evaluator4[P,I,M,D].ExpandAndLoadImportsFromUnescapedImportExpressionConditioned (System.String directoryOfImportingFile, Microsoft.Build.Construction.ProjectImportElement importElement, System.Collections.Generic.List1[Microsoft.Build.Construction.ProjectRootElement]& projects, Microsoft.Build.BackEnd.SdkResolution.SdkResult& sdkResult, System.Boolean throwOnFileNotExistsError) [0x00268] in :0
at Microsoft.Build.Evaluation.Evaluator4[P,I,M,D].ExpandAndLoadImports (System.String directoryOfImportingFile, Microsoft.Build.Construction.ProjectImportElement importElement, Microsoft.Build.BackEnd.SdkResolution.SdkResult& sdkResult) [0x00027] in <b695b16788dd418cbe8b4d98f7a92ff3>:0    at Microsoft.Build.Evaluation.Evaluator4[P,I,M,D].EvaluateImportElement (System.String directoryOfImportingFile, Microsoft.Build.Construction.ProjectImportElement importElement) [0x0000d] in :0
at Microsoft.Build.Evaluation.Evaluator4[P,I,M,D].PerformDepthFirstPass (Microsoft.Build.Construction.ProjectRootElement currentProjectOrImport) [0x00209] in <b695b16788dd418cbe8b4d98f7a92ff3>:0    at Microsoft.Build.Evaluation.Evaluator4[P,I,M,D].EvaluateImportElement (System.String directoryOfImportingFile, Microsoft.Build.Construction.ProjectImportElement importElement) [0x00040] in :0
at Microsoft.Build.Evaluation.Evaluator4[P,I,M,D].PerformDepthFirstPass (Microsoft.Build.Construction.ProjectRootElement currentProjectOrImport) [0x000e6] in <b695b16788dd418cbe8b4d98f7a92ff3>:0    at Microsoft.Build.Evaluation.Evaluator4[P,I,M,D].Evaluate (Microsoft.Build.BackEnd.Logging.ILoggingService loggingService, Microsoft.Build.Framework.BuildEventContext buildEventContext) [0x0011c] in :0
at Microsoft.Build.Evaluation.Evaluator4[P,I,M,D].Evaluate (Microsoft.Build.Evaluation.IEvaluatorData4[P,I,M,D] data, Microsoft.Build.Construction.ProjectRootElement root, Microsoft.Build.Evaluation.ProjectLoadSettings loadSettings, System.Int32 maxNodeCount, Microsoft.Build.Collections.PropertyDictionary1[T] environmentProperties, Microsoft.Build.BackEnd.Logging.ILoggingService loggingService, Microsoft.Build.Evaluation.IItemFactory2[S,T] itemFactory, Microsoft.Build.Evaluation.IToolsetProvider toolsetProvider, Microsoft.Build.Evaluation.ProjectRootElementCache projectRootElementCache, Microsoft.Build.Framework.BuildEventContext buildEventContext, Microsoft.Build.BackEnd.SdkResolution.ISdkResolverService sdkResolverService, System.Int32 submissionId, Microsoft.Build.Evaluation.Context.EvaluationContext evaluationContext, System.Boolean interactive) [0x0002f] in :0
at Microsoft.Build.Evaluation.Project.Reevaluate (Microsoft.Build.BackEnd.Logging.ILoggingService loggingServiceForEvaluation, Microsoft.Build.Evaluation.ProjectLoadSettings loadSettings, Microsoft.Build.Evaluation.Context.EvaluationContext evaluationContext) [0x0005e] in :0
at Microsoft.Build.Evaluation.Project.ReevaluateIfNecessary (Microsoft.Build.BackEnd.Logging.ILoggingService loggingServiceForEvaluation, Microsoft.Build.Evaluation.ProjectLoadSettings loadSettings, Microsoft.Build.Evaluation.Context.EvaluationContext evaluationContext) [0x00035] in :0
at Microsoft.Build.Evaluation.Project.ReevaluateIfNecessary (Microsoft.Build.BackEnd.Logging.ILoggingService loggingServiceForEvaluation, Microsoft.Build.Evaluation.Context.EvaluationContext evaluationContext) [0x00000] in :0
at Microsoft.Build.Evaluation.Project.ReevaluateIfNecessary (Microsoft.Build.Evaluation.Context.EvaluationContext evaluationContext) [0x00007] in :0
at Microsoft.Build.Evaluation.Project.Initialize (System.Collections.Generic.IDictionary2[TKey,TValue] globalProperties, System.String toolsVersion, System.String subToolsetVersion, Microsoft.Build.Evaluation.ProjectLoadSettings loadSettings, Microsoft.Build.Evaluation.Context.EvaluationContext evaluationContext) [0x00126] in <b695b16788dd418cbe8b4d98f7a92ff3>:0    at Microsoft.Build.Evaluation.Project..ctor (System.String projectFile, System.Collections.Generic.IDictionary2[TKey,TValue] globalProperties, System.String toolsVersion, System.String subToolsetVersion, Microsoft.Build.Evaluation.ProjectCollection projectCollection, Microsoft.Build.Evaluation.ProjectLoadSettings loadSettings, Microsoft.Build.Evaluation.Context.EvaluationContext evaluationContext) [0x00093] in :0
at Microsoft.Build.Evaluation.Project..ctor (System.String projectFile, System.Collections.Generic.IDictionary2[TKey,TValue] globalProperties, System.String toolsVersion, System.String subToolsetVersion, Microsoft.Build.Evaluation.ProjectCollection projectCollection, Microsoft.Build.Evaluation.ProjectLoadSettings loadSettings) [0x00000] in <b695b16788dd418cbe8b4d98f7a92ff3>:0    at Microsoft.Build.Evaluation.Project..ctor (System.String projectFile, System.Collections.Generic.IDictionary2[TKey,TValue] globalProperties, System.String toolsVersion, Microsoft.Build.Evaluation.ProjectCollection projectCollection, Microsoft.Build.Evaluation.ProjectLoadSettings loadSettings) [0x00000] in :0
at Microsoft.Build.Evaluation.Project..ctor (System.String projectFile, System.Collections.Generic.IDictionary2[TKey,TValue] globalProperties, System.String toolsVersion, Microsoft.Build.Evaluation.ProjectCollection projectCollection) [0x00000] in <b695b16788dd418cbe8b4d98f7a92ff3>:0    at Microsoft.Build.Evaluation.ProjectCollection.LoadProject (System.String fileName, System.Collections.Generic.IDictionary2[TKey,TValue] globalProperties, System.String toolsVersion) [0x000f7] in :0
at Microsoft.Build.Evaluation.ProjectCollection.LoadProject (System.String fileName, System.String toolsVersion) [0x00000] in :0
at OmniSharp.MSBuild.ProjectLoader.EvaluateProjectFileCore (System.String filePath) [0x0003f] in <4d39b1cf1ca84cccbd4059b400c1cde5>:0
at OmniSharp.MSBuild.ProjectLoader.BuildProject (System.String filePath) [0x0000d] in <4d39b1cf1ca84cccbd4059b400c1cde5>:0
at OmniSharp.MSBuild.ProjectFile.ProjectFileInfo.Load (System.String filePath, OmniSharp.MSBuild.ProjectIdInfo projectIdInfo, OmniSharp.MSBuild.ProjectLoader loader) [0x00015] in <4d39b1cf1ca84cccbd4059b400c1cde5>:0
at OmniSharp.MSBuild.ProjectManager+<>c__DisplayClass29_0.b__0 () [0x00000] in <4d39b1cf1ca84cccbd4059b400c1cde5>:0
at (wrapper delegate-invoke) System.Func1[System.ValueTuple3[OmniSharp.MSBuild.ProjectFile.ProjectFileInfo,System.Collections.Immutable.ImmutableArray1[OmniSharp.MSBuild.Logging.MSBuildDiagnostic],OmniSharp.MSBuild.Notification.ProjectLoadedEventArgs]].invoke_TResult()   at OmniSharp.MSBuild.ProjectManager.LoadOrReloadProject (System.String projectFilePath, System.Func1[TResult] loader) [0x0001b] in <4d39b1cf1ca84cccbd4059b400c1cde5>:0
    Attempted to update project that is not loaded: /home/baltasarq/tmp/HelloApp/HelloApp.csproj

I've found a fix but the Props file need to be updated manually so make sure to do a backup before.
For the following error: Microsoft.Build.Exceptions.InvalidProjectFileException: The imported project "/usr/lib/mono/xbuild/15.0/Microsoft.Common.props" was not found. Confirm that the path in the  declaration is correct, and that the file exists on disk.  /opt/dotnet/sdk/3.0.100/Sdks/Microsoft.NET.Sdk/Sdk/Sdk.props

Grab your output of the error: me it's /opt/dotnet/sdk/3.0.100/Sdks/Microsoft.NET.Sdk/Sdk/Sdk.props

2, Edit the props file from your output and at the following line:

Replace the Project="" by your output path: here's mine

Hope it helps.

A lot has changed with sdk resolution since this issue was opened. If you are still running into this problem, please open a new issue.


Unresolved merge conflict in javadoc of Kernel.EXECUTION_MODE

Looks like an unresolved merge conflict snuck into the javadoc of Kernel.EXECUTION_MODE:
https://github.com/Syncleus/aparapi/blob/master/src/main/java/com/aparapi/Kernel.java#L376
Since it's all in a block comment this doesn't affect compilation, obviously. However, it still messes up the generated javadoc documentation.

Thanks for catching that, I'll fix it shortly.

@raner just an FYI I'll be fixing this this weekend. Sorry for the delay we just now secured funding to start getting some time looking at this project in more detail (and offering bounties).


Do NOT pass MAKEFLAGS to sub-makes

Passing MAKEFLAGS is not necessary because "most" flags are propagated
already see:
https://www.gnu.org/software/make/manual/html_node/Options_002fRecursion.html#Options_002fRecursion .
This doesn't cause a problem when Makefile-lib-llvm is invoked directly
from the command line because MAKELEVEL=0 and  MAKEFLAGS did not have a
"w" in it. But when Makefile-lib-llvm is invoked from .package/deb/rules
it is not the root, MAKELEVEL > 0, so MAKEFLAGS has a "w". Thus, when
passing $(MAKEFLAGS) on the command line to Makefile-ponyc the "w" ends up
to be a Goal and Makefile-ponyc fails.

This can be merged once CI passes. If you see this with CI passed and it's not merged, please do so.


Algorithm Definitions via README files.

I thought that algorithms should be defined in a README file located at the root of the algorithm directory. This will allow for the problem to be defined globally regardless of the language used to solve it.
A Templates folder was added and I placed a README-template inside for standardized README files for each algorithm.
This will eliminate the need to defined the algorithm in each solution file.

The repo README may be amended in order to reflect this standard of defining algorithms in the repo structure - should this PR be accepted and merged.

I like this structure. I think having a README on each algorithm provides a bit more necessary background of the problem at hand. Good improvement here! We will continue to implement this style with the creation of the new algorithms.


feat: Add search FAB inside SearchFragment

fixes #164

@dreadpool2 @nikit19 please review

@simarsingh24 The arrow that you are using doesn't look nice
Try this one https://material.io/tools/icons/?search=arrow&icon=arrow_forward&style=baseline
This one looks better IMO I guess Eventbrite is using it too

Updated 👍

PR updated

PR updated

@iamareebjamal please merge this

Build is failing


Adding pyi files for better docs

Closes #1187
Seems to be adding useful infomation

@kannon92 any suggestions as to why why machine messed with the lockfile so much in this commit?

@kannon92 any suggestions as to why why machine messed with the lockfile so much in this commit?

None. @jayofdoom and I are going to switch to setup tools so this will probably go away.
I think w/e commit you have is fine.

Okay, I'll do that within the next 2 hours
On Mon, 11 Jul 2022, 17:41 Kevin Hannon, @.***> wrote:

@.**** requested changes on this pull request.
In scripts/build-python-client.sh
https://github.com/G-Research/armada/pull/1196#discussion_r918144330:

@@ -6,10 +6,11 @@ mkdir -p proto/armada
cp pkg/api/event.proto pkg/api/queue.proto pkg/api/submit.proto pkg/api/usage.proto proto/armada
sed -i 's/([^/])pkg/api/\1armada/g' proto/armada/*.proto

+pip3 install mypy-protobuf
Probably should add this in the pyproject.toml file rather than installing
it here.
—
Reply to this email directly, view it on GitHub
https://github.com/G-Research/armada/pull/1196#pullrequestreview-1034639737,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALCTWHVENMWYUNRKWTL7MULVTRFFNANCNFSM53HTIRFQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Fix typo about License

Thanks for sharing great works!

Thanks for your correction, we will merge this PR later


chore: bdd-gh-1587819099 to 0.0.1

chore: Promote bdd-gh-1587819099 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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


Not working for me

Hi,
I've tried to run the code posted, like this:
  var ghtmlSrc = require('gulp-html-src');
  gulp.src('www/index.html')
      .pipe(ghtmlSrc())
      .pipe(gulp.dest('./wwwtest/'));

And this isn't working. Part of my html looks like this:
    ...
    <!-- build:js scripts/vendor.js -->
    <!-- bower:js -->
    <script src="bower_components/angular/angular.js"></script>
    <script src="bower_components/angular-animate/angular-animate.js"></script>
    <script src="bower_components/angular-sanitize/angular-sanitize.js"></script>
    <script src="bower_components/angular-ui-router/release/angular-ui-router.js"></script>
    <script src="bower_components/ionic/release/js/ionic.js"></script>
    <script src="bower_components/ionic/release/js/ionic-angular.js"></script>
    <script src="bower_components/ngCordova/dist/ng-cordova.js"></script>
    <script src="bower_components/angular-dynamic-locale/src/tmhDynamicLocale.js"></script>
    <script src="bower_components/angular-translate/angular-translate.js"></script>
    <script src="bower_components/angular-translate-loader-static-files/angular-translate-loader-static-files.js"></script>
    <script src="bower_components/localforage/dist/localforage.js"></script>
    ...

So, what am I actually doing wrong?

It sounds like it can't find the files.  I'm guessing it can't find www/bower_components/angular/...., or maybe it's forgetting the www/ and your bower_components directory is in the www directory.
I'll try and check later how it deals with this - in the meantime, can you post where your bower_components is in relation to the www?

Hi and thank you for replying @bruderstein. You're right. Everything is packed in www directory. So the bower_components/ is subdirectory of www/, which means: www/bower_components/ is where our js libraries are.

Ok, I've tried this exact layout out, and it works fine for me.
+ --- gulpfile.js
+---  www
      +--- index.html
      +--- bower_components
             +---- angular
                     +---- angular.js
                     +---- ... etc

Can you try adding a gulp-debug line before and after the ghtmlSrc(), and paste the output here.
e.g.
var debug = require('gulp-debug');
var ghtmlSrc = require('gulp-html-src');

 gulp.task('default', function () {
    return gulp.src('www/index.html')
        .pipe(debug({ title: 'before'}))
        .pipe(ghtmlSrc())
        .pipe(debug({ title: 'after' }))
        .pipe(gulp.dest('dist'));
});

For my little page, I get the following output:
[20:18:37] Using gulpfile ~/gulp-html-src-test/gulpfile.js
[20:18:37] Starting 'default'...
[20:18:37] before www/index.html
[20:18:37] before 1 items
[20:18:38] after www/js/test1/test.js
[20:18:38] after www/js/test2/test.js
[20:18:38] after 2 items
[20:18:38] Finished 'default' after 44 ms

Hi. Thank you for replying. Can you also post the index.html code if possible? Thank you.

Nothing to it, but all based under the www directory:
<body>
<script src="js/test1/test.js"></script>
<script src="js/test2/test.js"></script>
</body>

I'm getting a similar issue.  Set up a very simple test structure.
gulpfile.js
`
var gulp = require('gulp');
var ghtmlSrc = require('gulp-html-src');
gulp.task('abc', function () {
return gulp.src('src/*.html')
.pipe(debug({ title: 'before'}))
.pipe(ghtmlSrc())
.pipe(debug({ title: 'after' }))
`
src/test.html
`

`
My output is as follows:
[08:25:13] Using gulpfile /var/www/html/gulpfile.js [08:25:13] Starting 'abc'... [08:25:13] before src/test.html [08:25:14] before 1 items
Then nothing.
I ran the tests in the gulp-html-src directory, by doing an 'npm test' and got two errors:
`  15 passing (815ms)
2 failing

gulp-html-src for streams emits single script stream from html:
Uncaught TypeError: Cannot read property 'length' of null
at Function.Buffer.concat (buffer.js:219:24)
at PassThrough. (test/test.js:447:29)
at endReadableNT (_stream_readable.js:913:12)

gulp-html-src for streams emits multiple script streams from html:
Uncaught TypeError: Cannot read property 'length' of null
at Function.Buffer.concat (buffer.js:219:24)
at PassThrough. (test/test.js:447:29)
at endReadableNT (_stream_readable.js:913:12)
`

Node version v4.4.4, NPM version 2.15.1, Gulp 3.9.1.  Running this on CentOS 7.   Happy to provide any further information for debugging... hoping I've just done something stupid here?

Also now hitting this - similar simple setup
Node 4.4.4, npm 2.15.1, gulp 3.9.1 - on MacOS and Ubuntu 14.04 LTS

This should be pretty easy to fix - I'm away for a few days though - I'll take a look next week.

Same issue around here.

If you go to line 121 from the index.js file and replace this:
callback();

For this:
setTimeout(function () {callback();}, 0);

It passes all the testes, but still does not work.


Add cache for 5.2.3 binary urls

We're up to 5.2.4 now.
Anything stoping this from being merged?

These cache are no longer used in the default branch. swiftenv install --list will now fetch these: https://github.com/kylef/swiftenv/blob/master/CHANGELOG.md


Submit Button of Volunteer Page

Is your feature request related to a problem? Please describe.
The submit button in the volunteer html page is of indigo color which is not matching to the theme of the website I would like to update the button.
Describe the solution you'd like

So the color of the button should be matching to the bg color of navbar, I will update the button similar to the navbar background color.
Additional context
Please assign me this issue under hacktoberfest label @akshitagupta15june

I would like to work on this issue @ayan-joshi . Please assign me this issue

please assign me this issue under hacktoberfest label @akshitagupta15june

Hey @Susmita-Dey please assign this issue to me.

please assign this issue to me


Offer secret selection on edit command

This commit adds the secret selection wizard to
the edit command as well. This is triggered in
case no exact match was found. If the user aborts
the wizard then this is handled as if a new secret
was to be created.
Fixes #927

I think the behavior of selecting a secret as implemented here is much better. Not sure if creating a new one in the abort case is understood. Maybe one can initialize the secret with a comment or so? Alternatively abort means abort and the command is terminated. Edit implies to me that the secret exists already.

Ok, good idea. We originally implemented this as pass did, but I agree. It's confusing. Maybe we should add a switch to edit if you want to (possibly) create a new secret and otherwise fail if it doesn't exist already.