Sync fails due to (plain) metrics discovery error

Hi I'm getting started with flux and following the guide on the repository. I'm running K8s cluster with AWS EKS v1.12 and worker nodes in EC2 instances.
After deploy flux to my cluster I'm getting this errors:
ts=2019-05-23T17:56:42.830342392Z caller=main.go:210 type="internal kubernetes error" kubernetes_caller=vendor/k8s.io/client-go/discovery/cached/memory/memcache.go:199 err="couldn't get resource list for metrics/v1alpha1: the server could not find the requested resource"
ts=2019-05-23T18:01:42.855450572Z caller=loop.go:90 component=sync-loop err="collating resources in cluster for sync: unable to retrieve the complete list of server APIs: metrics/v1alpha1: the server could not find the requested resource"

Then the state of metrics that I installed following the AWS doc metrics
kubectl get --raw /apis/metrics.k8s.io/v1beta1
{"kind":"APIResourceList","apiVersion":"v1","groupVersion":"metrics.k8s.io/v1beta1","resources":[{"name":"nodes","singularName":"","namespaced":false,"kind":"NodeMetrics","verbs":["get","list"]},{"name":"pods","singularName":"","namespaced":true,"kind":"PodMetrics","verbs":["get","list"]}]}

Doing a flux sync the output is:
HEAD of master is 1d0b9e1
Waiting for 1d0b9e1 to be applied ...
== Error ==

Error: fatal: bad revision 'flux-sync..1d0b9e1', full output:
 fatal: bad revision 'flux-sync..1d0b9e1'

We don't have a specific help message for the error above.
It would help us remedy this if you log an issue at

https://github.com/weaveworks/flux/issues

saying what you were doing when you saw this, and quoting the message
at the top.

I made a change to my cloned repository to master but never get it synchronized on the cluster.
Flux version is 1.12.3
Any help would be appreciated.

I almost forget, metrics version is v0.3.3.

It seems like is trying to get data from metrics API 1alpha1 but I'm using 1beta1..

metrics/v1alpha1 seems odd, I think it should be metrics.k8s.io/v1alpha1  (whose error would had been ignored correctly by #2009 )
I am not a metrics user, but let's try to pinpoint where metrics/v1alpha1 is coming from. Can you please paste some further information?

The full logs of Flux (thanks for the excerpt BTW)
The output of kubectl get --raw /apis/
The output of kubectl get --raw /apis/metrics/v1alpha1
The output of kubectl get --raw /apis/metrics.k8s.io/v1alpha1

Hello @2opremio , thanks for the fast response. Here are the logs and outputs you requested:
1-
ts=2019-05-24T17:37:29.153985791Z caller=main.go:193 version=1.12.3 ts=2019-05-24T17:37:29.194787785Z caller=main.go:350 component=cluster identity=/etc/fluxd/ssh/identity ts=2019-05-24T17:37:29.194832968Z caller=main.go:351 component=cluster identity.pub="ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDXRSqUOxmnkJDVmhYd0H8Dzv80slqOycENSs28MtA2ynpYAXrZ92FgetNJUnUfoEruXHC9aRYMr9O/5RBmQGkVasIJq3boAI+5oj5nGPYYzXjnUJty5ZOcbPM2HFZw8Q3DAH/q8MGtv25pz7UXZMhKHkqabsLiRXNzANTFQ41yHV+FYKuYquLoqDKIla3h337nkgxABQmtm5KPErmLvMaORQZiKdTzevT9eyXGf8H8Od8K2YK6bb79oqXg3I8/kubAXI/qZpHJSN0pOyyq8LUm3/pL50itItHpv67LQ7YxVhpeGyvS0JDBLYzDoR+XVF1D57LvXMu6hBkRSMK7VJtX" ts=2019-05-24T17:37:29.194858103Z caller=main.go:352 component=cluster host=https://<IP_ADDRESS>:443 version=kubernetes-v1.12.6-eks-d69f1b ts=2019-05-24T17:37:29.194905157Z caller=main.go:364 component=cluster kubectl=/usr/local/bin/kubectl ts=2019-05-24T17:37:29.197765233Z caller=main.go:375 component=cluster ping=true ts=2019-05-24T17:37:29.201955341Z caller=main.go:508 url=git@github.com:marcossv9/flux-get-started user="Weave Flux"<EMAIL_ADDRESS>signing-key= sync-tag=flux-sync notes-ref=flux set-author=false ts=2019-05-24T17:37:29.20219346Z caller=main.go:565 upstream="no upstream URL given" ts=2019-05-24T17:37:29.202303724Z caller=main.go:594 metrics-addr=:3031 ts=2019-05-24T17:37:29.211677433Z caller=images.go:18 component=sync-loop msg="polling images" ts=2019-05-24T17:37:29.213655932Z caller=images.go:28 component=sync-loop msg="no automated workloads" ts=2019-05-24T17:37:29.21391641Z caller=loop.go:90 component=sync-loop err="git repo not ready: git repo has not been cloned yet" ts=2019-05-24T17:37:29.228989507Z caller=main.go:586 addr=:3030 ts=2019-05-24T17:37:29.367830101Z caller=aws.go:137 component=aws info="detected cluster region" source="EC2 metadata service" region=us-east-1 ts=2019-05-24T17:37:29.36797113Z caller=aws.go:104 component=aws info="restricting ECR registry scans" regions=[us-east-1] include-ids=[] exclude-ids=[602401143452] ts=2019-05-24T17:37:30.327198176Z caller=checkpoint.go:24 component=checkpoint msg="up to date" latest=1.12.3 ts=2019-05-24T17:37:30.434601096Z caller=memcached.go:112 component=memcached err="Fetching tag from memcache: memcache: connect timeout to <IP_ADDRESS>:11211" ts=2019-05-24T17:37:30.434670793Z caller=warming.go:162 component=warmer canonical_name=index.docker.io/weaveworks/flux auth={map[]} err="fetching previous result from cache: memcache: connect timeout to <IP_ADDRESS>:11211" ts=2019-05-24T17:37:31.434907559Z caller=memcached.go:112 component=memcached err="Fetching tag from memcache: memcache: connect timeout to <IP_ADDRESS>:11211" ts=2019-05-24T17:37:31.434973497Z caller=warming.go:162 component=warmer canonical_name=index.docker.io/library/memcached auth={map[]} err="fetching previous result from cache: memcache: connect timeout to <IP_ADDRESS>:11211" ts=2019-05-24T17:37:31.515785019Z caller=warming.go:198 component=warmer info="refreshing image" image=docker.io/amazon/aws-alb-ingress-controller tag_count=4 to_update=4 of_which_refresh=0 of_which_missing=4 ts=2019-05-24T17:37:31.706408025Z caller=warming.go:206 component=warmer updated=docker.io/amazon/aws-alb-ingress-controller successful=4 attempted=4 ts=2019-05-24T17:37:31.706616953Z caller=images.go:18 component=sync-loop msg="polling images" ts=2019-05-24T17:37:31.706637351Z caller=images.go:28 component=sync-loop msg="no automated workloads" ts=2019-05-24T17:38:29.382191464Z caller=warming.go:198 component=warmer info="refreshing image" image=docker.io/weaveworks/flux tag_count=31 to_update=31 of_which_refresh=0 of_which_missing=31 ts=2019-05-24T17:38:31.090721139Z caller=warming.go:206 component=warmer updated=docker.io/weaveworks/flux successful=31 attempted=31 ts=2019-05-24T17:38:31.091264947Z caller=images.go:18 component=sync-loop msg="polling images" ts=2019-05-24T17:38:31.091286631Z caller=images.go:28 component=sync-loop msg="no automated workloads" ts=2019-05-24T17:38:31.156726929Z caller=warming.go:198 component=warmer info="refreshing image" image=memcached tag_count=70 to_update=70 of_which_refresh=0 of_which_missing=70 ts=2019-05-24T17:38:35.81443173Z caller=warming.go:206 component=warmer updated=memcached successful=70 attempted=70 ts=2019-05-24T17:38:35.814546064Z caller=images.go:18 component=sync-loop msg="polling images" ts=2019-05-24T17:38:35.814570519Z caller=images.go:28 component=sync-loop msg="no automated workloads" ts=2019-05-24T17:38:45.28335996Z caller=loop.go:103 component=sync-loop event=refreshed url=git@github.com:marcossv9/flux-get-started branch=master HEAD=2c506713e0128b050feb3086df044646a42e0e30 ts=2019-05-24T17:38:45.326982872Z caller=main.go:210 type="internal kubernetes error" kubernetes_caller=vendor/k8s.io/client-go/discovery/cached/memory/memcache.go:199 err="couldn't get resource list for metrics/v1alpha1: the server could not find the requested resource" ts=2019-05-24T17:38:45.331883668Z caller=loop.go:90 component=sync-loop err="collating resources in cluster for sync: unable to retrieve the complete list of server APIs: metrics/v1alpha1: the server could not find the requested resource" ts=2019-05-24T17:39:15.513402813Z caller=loop.go:103 component=sync-loop event=refreshed url=git@github.com:marcossv9/flux-get-started branch=master HEAD=2c506713e0128b050feb3086df044646a42e0e30 ts=2019-05-24T17:39:45.746853739Z caller=loop.go:103 component=sync-loop event=refreshed url=git@github.com:marcossv9/flux-get-started branch=master HEAD=2c506713e0128b050feb3086df044646a42e0e30 ts=2019-05-24T17:40:15.964621885Z caller=loop.go:103 component=sync-loop event=refreshed url=git@github.com:marcossv9/flux-get-started branch=master HEAD=2c506713e0128b050feb3086df044646a42e0e30 ts=2019-05-24T17:40:46.181612072Z caller=loop.go:103 component=sync-loop event=refreshed url=git@github.com:marcossv9/flux-get-started branch=master HEAD=2c506713e0128b050feb3086df044646a42e0e30 ts=2019-05-24T17:41:16.474890173Z caller=loop.go:103 component=sync-loop event=refreshed url=git@github.com:marcossv9/flux-get-started branch=master HEAD=2c506713e0128b050feb3086df044646a42e0e30 ts=2019-05-24T17:41:29.602534796Z caller=warming.go:198 component=warmer info="refreshing image" image=alpine tag_count=22 to_update=22 of_which_refresh=0 of_which_missing=22 ts=2019-05-24T17:41:31.055689361Z caller=warming.go:206 component=warmer updated=alpine successful=22 attempted=22 ts=2019-05-24T17:41:31.055891166Z caller=images.go:18 component=sync-loop msg="polling images" ts=2019-05-24T17:41:31.088149416Z caller=images.go:112 component=sync-loop workload=demo:deployment/podinfo container=init repo=alpine pattern=regexp:^3.* current=alpine:3.5 info="added update to automation run" new=alpine:3.9 reason="latest 3.9 (2019-05-11 00:07:03.510395965 +0000 UTC) > current 3.5 (2019-01-30 22:20:40.179652676 +0000 UTC)" ts=2019-05-24T17:41:31.088231991Z caller=loop.go:111 component=sync-loop jobID=08055556-afdc-5697-a554-da6339d8c8a1 state=in-progress ts=2019-05-24T17:41:31.11443791Z caller=releaser.go:58 component=sync-loop jobID=08055556-afdc-5697-a554-da6339d8c8a1 type=release updates=1 ts=2019-05-24T17:41:31.138035993Z caller=warming.go:198 component=warmer info="refreshing image" image=stefanprodan/podinfo tag_count=144 to_update=144 of_which_refresh=0 of_which_missing=144 ts=2019-05-24T17:41:33.570118477Z caller=daemon.go:276 component=sync-loop jobID=08055556-afdc-5697-a554-da6339d8c8a1 revision=d9e5aeb5127c97830666da2a281688b3a0c5419a ts=2019-05-24T17:41:33.570161494Z caller=daemon.go:624 component=daemon event="Commit: d9e5aeb, demo:deployment/podinfo" logupstream=false ts=2019-05-24T17:41:33.570224863Z caller=loop.go:123 component=sync-loop jobID=08055556-afdc-5697-a554-da6339d8c8a1 state=done success=true ts=2019-05-24T17:41:33.821970587Z caller=loop.go:103 component=sync-loop event=refreshed url=git@github.com:marcossv9/flux-get-started branch=master HEAD=d9e5aeb5127c97830666da2a281688b3a0c5419a ts=2019-05-24T17:41:33.845089699Z caller=loop.go:90 component=sync-loop err="collating resources in cluster for sync: unable to retrieve the complete list of server APIs: metrics/v1alpha1: the server could not find the requested resource" ts=2019-05-24T17:41:40.336537551Z caller=warming.go:206 component=warmer updated=stefanprodan/podinfo successful=144 attempted=144 ts=2019-05-24T17:41:40.338566869Z caller=images.go:18 component=sync-loop msg="polling images" ts=2019-05-24T17:41:40.398206899Z caller=images.go:112 component=sync-loop workload=demo:deployment/podinfo container=init repo=alpine pattern=regexp:^3.* current=alpine:3.5 info="added update to automation run" new=alpine:3.9 reason="latest 3.9 (2019-05-11 00:07:03.510395965 +0000 UTC) > current 3.5 (2019-01-30 22:20:40.179652676 +0000 UTC)" ts=2019-05-24T17:41:40.398308848Z caller=loop.go:111 component=sync-loop jobID=a65a37f6-05b6-04c5-e2bf-aeeed0a08847 state=in-progress ts=2019-05-24T17:41:40.427179923Z caller=releaser.go:58 component=sync-loop jobID=a65a37f6-05b6-04c5-e2bf-aeeed0a08847 type=release updates=0 ts=2019-05-24T17:41:40.427210764Z caller=releaser.go:60 component=sync-loop jobID=a65a37f6-05b6-04c5-e2bf-aeeed0a08847 type=release exit="no images to update for services given" ts=2019-05-24T17:41:40.434902072Z caller=loop.go:121 component=sync-loop jobID=a65a37f6-05b6-04c5-e2bf-aeeed0a08847 state=done success=false err="no changes made in repo" ts=2019-05-24T17:41:40.666596764Z caller=loop.go:103 component=sync-loop event=refreshed url=git@github.com:marcossv9/flux-get-started branch=master HEAD=d9e5aeb5127c97830666da2a281688b3a0c5419a ts=2019-05-24T17:42:10.980940896Z caller=loop.go:103 component=sync-loop event=refreshed url=git@github.com:marcossv9/flux-get-started branch=master HEAD=6781af8a02da2d6d8555034ba644a6d4ea599b3b ts=2019-05-24T17:42:11.019880417Z caller=loop.go:90 component=sync-loop err="collating resources in cluster for sync: unable to retrieve the complete list of server APIs: metrics/v1alpha1: the server could not find the requested resource" ts=2019-05-24T17:42:41.195698779Z caller=loop.go:103 component=sync-loop event=refreshed url=git@github.com:marcossv9/flux-get-started branch=master HEAD=6781af8a02da2d6d8555034ba644a6d4ea599b3b ts=2019-05-24T17:43:11.684093976Z caller=loop.go:103 component=sync-loop event=refreshed url=git@github.com:marcossv9/flux-get-started branch=master HEAD=6781af8a02da2d6d8555034ba644a6d4ea599b3b ts=2019-05-24T17:43:41.916043894Z caller=loop.go:103 component=sync-loop event=refreshed url=git@github.com:marcossv9/flux-get-started branch=master HEAD=6781af8a02da2d6d8555034ba644a6d4ea599b3b
2-
{"kind":"APIGroupList","apiVersion":"v1","groups":[{"name":"apiregistration.k8s.io","versions":[{"groupVersion":"apiregistration.k8s.io/v1","version":"v1"},Error from server (NotFound): the server could not find the requested resource{"groupVersion":"apiregistration.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"apiregistration.k8s.io/v1","version":"v1"}},{"name":"extensions","versions":[{"groupVersion":"extensions/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"extensions/v1beta1","version":"v1beta1"}},{"name":"apps","versions":[{"groupVersion":"apps/v1","version":"v1"},{"groupVersion":"apps/v1beta2","version":"v1beta2"},{"groupVersion":"apps/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"apps/v1","version":"v1"}},{"name":"events.k8s.io","versions":[{"groupVersion":"events.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"events.k8s.io/v1beta1","version":"v1beta1"}},{"name":"authentication.k8s.io","versions":[{"groupVersion":"authentication.k8s.io/v1","version":"v1"},{"groupVersion":"authentication.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"authentication.k8s.io/v1","version":"v1"}},{"name":"authorization.k8s.io","versions":[{"groupVersion":"authorization.k8s.io/v1","version":"v1"},{"groupVersion":"authorization.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"authorization.k8s.io/v1","version":"v1"}},{"name":"autoscaling","versions":[{"groupVersion":"autoscaling/v1","version":"v1"},{"groupVersion":"autoscaling/v2beta1","version":"v2beta1"},{"groupVersion":"autoscaling/v2beta2","version":"v2beta2"}],"preferredVersion":{"groupVersion":"autoscaling/v1","version":"v1"}},{"name":"batch","versions":[{"groupVersion":"batch/v1","version":"v1"},{"groupVersion":"batch/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"batch/v1","version":"v1"}},{"name":"certificates.k8s.io","versions":[{"groupVersion":"certificates.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"certificates.k8s.io/v1beta1","version":"v1beta1"}},{"name":"networking.k8s.io","versions":[{"groupVersion":"networking.k8s.io/v1","version":"v1"}],"preferredVersion":{"groupVersion":"networking.k8s.io/v1","version":"v1"}},{"name":"policy","versions":[{"groupVersion":"policy/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"policy/v1beta1","version":"v1beta1"}},{"name":"rbac.authorization.k8s.io","versions":[{"groupVersion":"rbac.authorization.k8s.io/v1","version":"v1"},{"groupVersion":"rbac.authorization.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"rbac.authorization.k8s.io/v1","version":"v1"}},{"name":"storage.k8s.io","versions":[{"groupVersion":"storage.k8s.io/v1","version":"v1"},{"groupVersion":"storage.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"storage.k8s.io/v1","version":"v1"}},{"name":"admissionregistration.k8s.io","versions":[{"groupVersion":"admissionregistration.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"admissionregistration.k8s.io/v1beta1","version":"v1beta1"}},{"name":"apiextensions.k8s.io","versions":[{"groupVersion":"apiextensions.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"apiextensions.k8s.io/v1beta1","version":"v1beta1"}},{"name":"scheduling.k8s.io","versions":[{"groupVersion":"scheduling.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"scheduling.k8s.io/v1beta1","version":"v1beta1"}},{"name":"coordination.k8s.io","versions":[{"groupVersion":"coordination.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"coordination.k8s.io/v1beta1","version":"v1beta1"}},{"name":"crd.k8s.amazonaws.com","versions":[{"groupVersion":"crd.k8s.amazonaws.com/v1alpha1","version":"v1alpha1"}],"preferredVersion":{"groupVersion":"crd.k8s.amazonaws.com/v1alpha1","version":"v1alpha1"}},{"name":"metrics","versions":[{"groupVersion":"metrics/v1alpha1","version":"v1alpha1"}],"preferredVersion":{"groupVersion":"metrics/v1alpha1","version":"v1alpha1"}},{"name":"metrics.k8s.io","versions":[{"groupVersion":"metrics.k8s.io/v1beta1","version":"v1beta1"}],"preferredVersion":{"groupVersion":"metrics.k8s.io/v1beta1","version":"v1beta1"}}]}
3-
Error from server (NotFound): the server could not find the requested resource
4-
Error from server (NotFound): the server could not find the requested resource
Please let me know if you need something else.

Adding some more info, I think memcache for flux is asking for metrics API for old kubernetes 1.7 version. (metrics/v1alpha1). But I'm using the metrics API for kubernetes 1.8+ version (metrics.k8s.io/v1beta1)...

memecache doesn't cache resources/groupversions , just container image metadata.

To be more precise, there is an in-memory cache for the resource definitions but it gets invalidated every 5 minutes

Here's the problem (from kubectl get --raw /apis/):
    {
      "name": "metrics",
      "versions": [
        {
          "groupVersion": "metrics/v1alpha1",
          "version": "v1alpha1"
        }
      ],
      "preferredVersion": {
        "groupVersion": "metrics/v1alpha1",
        "version": "v1alpha1"
      }
    },
    {
      "name": "metrics.k8s.io",
      "versions": [
        {
          "groupVersion": "metrics.k8s.io/v1beta1",
          "version": "v1beta1"
        }
      ],
      "preferredVersion": {
        "groupVersion": "metrics.k8s.io/v1beta1",
        "version": "v1beta1"
      }
    }

We do ignore errors in metrics.k8s.io (see #2009 ) but not on plain metrics (which I didn't know was a thing) and seems to be misconfigured in your cluster (since kubectl get --raw /apis/metrics/v1alpha1 fails)

So, this is another incarnation of https://github.com/weaveworks/flux/issues/1991 , sigh

Thanks @2opremio I will look into that on next Monday!

@2opremio this quick fix will be available on next release?

Yep!

Yep!

Awesome! Thanks!


Powdr2

This PR introduces:

new syntax for multi machine
pilgen for single machines, with as output a tree of machines with directed links
new linker crate to link the tree, currently by inlining all machines into the same PIL and turning links into lookups

Missing:

some syntax is still a bit awkward, for external instructions and instructions in machines which don't have a pc or assignment registers
the instruction latch (to select which rows an instruction can be accessed on) is unimplemented

Breaking:

~witgen for the memory state machine (at least) as it relies on the namespace being Assembly but now the namespace is the path in the machine tree~ fixed
~riscv compiler~

Fixes https://github.com/powdr-org/powdr/issues/348
Ref https://github.com/powdr-org/powdr/issues/36 https://github.com/powdr-org/powdr/issues/235

closing this in favor of #377 and other smaller prs to come


Update user guide error scenarios

Codecov Report
Base: 72.15% // Head: 72.15% // No change to project coverage :thumbsup:

Coverage data is based on head (c22a75d) compared to base (7ee9c65).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master      #53   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


CI job is choking on new NumPy memory allocator warnings

Example: https://github.com/scipy/scipy/runs/4005856905?check_suite_focus=true
There's lots of this:
scipy/interpolate/tests/test_rbf.py ..........                           [ 17%]
Exception ignored in: 'array_dealloc'
Traceback (most recent call last):
  File "/home/runner/.local/lib/python3.10/site-packages/_pytest/unraisableexception.py", line 59, in __exit__
    del self.unraisable
RuntimeWarning: Trying to dealloc data, but a memory policy is not set. If you take ownership of the data, you must also set a memory policy.

This looks like it's in Pythran code, but nothing changed there - it seems to be due to the new memory allocator in NumPy main. @mattip can you have a look at this?

@mattip, @seberg this is still failing (example from the last hour: link), and I verified that the latest NumPy nightly includes https://github.com/numpy/numpy/pull/20200. The failure mode is slightly different:
/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/_pytest/unraisableexception.py:78: in unraisable_exception_runtest_hook
    warnings.warn(pytest.PytestUnraisableExceptionWarning(msg))
E   pytest.PytestUnraisableExceptionWarning: Exception ignored in: 'array_dealloc'
E
E   Traceback (most recent call last):
E     File "/opt/hostedtoolcache/Python/3.8.12/x64/lib/python3.8/site-packages/matplotlib/_pylab_helpers.py", line 68, in destroy
E       gc.collect(1)
E   RuntimeWarning: Trying to dealloc data, but a memory policy is not set. If you take ownership of the data, you must set a base owning the data (e.g. a PyCapsule).
        cm         = <_pytest.unraisableexception.catch_unraisable_exception object at 0x7efb8ba85700>
        err_msg    = 'Exception ignored in'
        msg        = 'Exception ignored in: \'array_dealloc\'\n\nTraceback (most recent call last):\n  File "/opt/hostedtoolcache/Python/3....memory policy is not set. If you take ownership of the data, you must set a base owning the data (e.g. a PyCapsule).\n'

Seems to still be failing even after the fixup PR https://github.com/numpy/numpy/pull/20238. Example CI log from a few minutes ago: link

Seems to me that the nightly-wheel used here was just build exactly one commit before the fix was merged.

Hmm odd. Yes you are right, thanks @seberg. It looks like the NumPy nightlies arrive inconsistently, the last 3 uploads were 2, 4 and 9 days ago: https://anaconda.org/scipy-wheels-nightly/numpy/files

I believe the cron jobs don't run if a build was run in the previous 24 hours, which can be the result of a merge or a deliberate trigger.


zed: very ancient version of nwjs

zed uses the binary release of nwjs 0.9 (at this time still called node_webkit), while the newest version is 0.29.
As this is basically a Chromium binary that can execute arbitrary Javascript and deliberately breaks all sandboxing features, we should at least keep it on a current version.
cc @Ma27
I’m pushing an update of nwjs to 0.26 at the moment, but the zed package can’t handle it, so I’m pinning to 0.9 for the time being.
https://github.com/NixOS/nixpkgs/pull/27882

Hi @Profpatsch!
Thanks a lot for working on this. It's been a while ago since I worked on this part of nixpkgs, but I slightly remember that I had to deal with several outdated versions when dealing with zed.
I'll definitely have a look into this in the next days, hopefully there's a patch by some contributors (or it's easy to file one to fix this).
However the project isn't too active, so at least when we suffer from more further breaks or security issues because of severely outdated dependencies, we shouldn't hesitate to mark this package as broken or even drop it entirely (unless there are folks heavily relying on this).

I’d be in favor of a drop; people will complain if they still use it, if that happens we can restore & update, or the package is pulled outside of nixpkgs until someone can push and maintain a recent update.

I’d be in favor of a drop; people will complain if they still use it, if that happens we can restore & update, or the package is pulled outside of nixpkgs until someone can push and maintain a recent update.

In fact I agree with you, I've observed this "restore & update" pattern with some bigger applications (especially web-services) and I think that this is unneeded extra-work for the nixpkgs maintainers and release managers before each release.
Before I file a patch to either {drop it,mark it as broken} or fix the dependency issue, I'd like to check two things before:

is there any active fork? I'd like to ensure that the project is actually dead/unresponsive or does it have a working/maintained fork?
check in the IRC if there are active zed users (I don't use it, I just fixed the derivation to help @svanderburg to get rid of npm2nix). If there are any, we should ask them to take over maintenance (or ask them to create their own overlay)

I'll try to have a deeper look into it tonight, when I know more and have an actual opinion on how to proceed, I'll leave a comment here.

As far as I know, the author is no longer actively developing Zed anymore:
https://zef.me/how-to-abandon-open-source-d5ebbc6e45e5
I happen to know him personally, but as far as I know he has no interests
in doing any major additional developments any time soon. Of course, I can
always ask but I think I already know the answer. :)
For me it's fine if it gets removed.
On Mon, Mar 19, 2018 at 3:38 PM Maximilian Bosch<EMAIL_ADDRESS>wrote:

I’d be in favor of a drop; people will complain if they still use it, if
that happens we can restore & update, or the package is pulled outside of
nixpkgs until someone can push and maintain a recent update.
In fact I agree with you, I've observed this "restore & update" pattern
with some bigger applications (especially web-services) and I think that
this is unneeded extra-work for the nixpkgs maintainers and release
managers before each release.
Before I file a patch to either {drop it,mark it as broken} or fix the
dependency issue, I'd like to check two things before:

is there any active fork? I'd like to ensure that the project is
actually dead/unresponsive or does it have a working/maintained fork?
check in the IRC if there are active zed users (I don't use it, I
just fixed the derivation to help @svanderburg
https://github.com/svanderburg to get rid of npm2nix). If there are
any, we should ask them to take over maintenance (or ask them to create
their own overlay)

I'll try to have a deeper look into it tonight, when I know more and have
an actual opinion on how to proceed, I'll leave a comment here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/issues/37361#issuecomment-374234623,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABGY96uSvYuHr5WTCrtYoWOTgDWQ8zVPks5tf8LMgaJpZM4Svsfb
.

ok I suspected something like this as the last commit was from 2015. In this case I'm also :+1: for dropping it...

just submitted a PR for now, I asked in the IRC if there are any folks using zed, if I don't get a response, I'd just vote for merging it to master and do a backport to 18.03


Use-after-free

NOTE: not even compile tested. btw, if you don't store a ref to shared ptr in lambda, p2 may be destroyed after when_all_succeed() defers. note that seastar projects like scylladb use do_with() to handle this, or just store a ref to shared ptr in lambda like done by this fix.

Oh... I think I make that same error in a bunch of places.


Function 'is_categorical' is passed instead of the value of 'categorical'

In Line 457 of dowhy\gcm\model_evaluation.py, there is the following line of code
                conditional_expectations = _estimate_conditional_expectations(                     tmp_causal_mechanism, parent_data[test_indices], is_categorical, 50                 )
Based on the context, it looks that the value of 'categorical' should be passed. However, the function 'is_categorical' is passed instead. Is this a bug?
Version information:

DoWhy version 0.11.1

This issue has been fixed in a PR


More text customisation options

We should have more customisation options like line-height, font-family, ex.

Hi @Codemaine, thanks for the feature request! Are you currently running into any issues applying a font-family to the component via applying styles in the parent component that is leveraging the <AnimatedCounter>? If you take a peak at the example codesandbox in the docs, you can see an example of a custom font being applied (in this case Comfortaa). Please let me know if you have any questions :)

Yea, maybe can add some opportunities to change text: convert to localeString or something like that. What do you think about this idea?

Hi @Codemaine, thanks for the feature request! Are you currently running into any issues applying a font-family to the component via applying styles in the parent component that is leveraging the <AnimatedCounter>? If you take a peek at the example codesandbox in the docs, you can see an example of a custom font being applied (in this case Comfortaa). Please let me know if you have any questions :)

The spacing between the characters is a lot, and I haven't found a way to decrease it

I definitely love the idea/am in favor of spending some time adding more customization options for folks. In terms of the localeString use-case, can you provide me with an example of what you would like to accomplish and/or more detail about the pain-point you are running into? @fordelord
In terms of the spacing between characters, what font family are you using while running into this issue so I can better replicate the issue? @Codemaine
Looking forward to adding these features for y'all and hope you're both having a happy new year

I would love it if you could offer the option for a className for the text, and the font I'm using is Gellix. Happy new year to you too :)

@TuckerMassad Yea, I have the component which show the estimated yearnings of the user and this number looks really big. To make number more readable I add the LocaleString to add coma between 3 number like: 123,456.78 ; 12,231.00; 12,231; 492,392,342.48. This style make number more readable and understandable from this 123456.00 to this -> 123,456.00. Can you add this feature to your library? I think this feature will make this library more customizable and comfortable.

Hey folks @Codemaine @fordelord. I've added some modifications to ensure uniformity of spacing of each individual integer as well as a new optional formatLocale boolean prop that applies Number.toLocaleString() if it is set to true (this adds commas for en-US users for example). If you bump your package version up to 1.7.5 you can give it a whirl. Below is a demo codesandbox link as well if you want to give it a whirl. Let me know if y'all have any additional requests and/or suggestions!

https://codesandbox.io/p/sandbox/floral-glitter-h6wzpp?file=%2Fsrc%2FApp.js

@TuckerMassad Thank you for your work, but it doesn't work properly, I have tested it and you can see the bug in the demo: https://www.loom.com/share/85c565a92ab74912a022b9d6d8c56a1b

Can you tell me pls when you can fix this?

I appreciate the bug demo! @fordelord  It seems that non en-US locales are running into formats that you aren't particularly looking for. If you bump your package version to 1.7.6 and replace the formatLocale boolean with includeCommas you should see your problem fixed. Ex.
<AnimatedCounter
  value={counterValue}
  color="white"
  fontSize="60px"
  includeCommas={true}
/>

Another codesandbox for you to give it a try: https://codesandbox.io/p/sandbox/dank-night-x4syjs?file=%2Fsrc%2FApp.js%3A25%2C41

Closing this one out as I haven't seen additional activity here + added requested functionality via the includeCommas prop. Please feel free to open additional feature requests in the future and i'll be sure to take a look at em 😄


Card: Add fullHeight styles

Card: Add fullHeight styles
This update adds a new prop to the Card component allowing it to have
full height styles (height: 100%). This is useful for when the Card
is contained within a flex-based element, and you require the Card
to expand the entire height of the parent element.

Changes Unknown when pulling efa4be29972cc2f71e9a9606baf54d17d1ee7641 on Card/fullHeight into ** on master**.

Changes Unknown when pulling 52231283fa65f29a95550cf24e366aa26fc9238c on Card/fullHeight into ** on master**.


#62: Secure access through LAN

@ojousima could you please check the translation into Finnish in auth.html and index.html?

hi @ojousima , is translation ok now?

@ojousima could you please check translation from my recent commit:
Deny access from the local network
Estä pääsy paikallisverkosta

Access denied.
Pääsy evätty.

Translation is ok


Selfie command not showing up in Gmail

Selfie command doesn't show up on drop down in gmail:
https://www.dropbox.com/s/7hg61md3l0pl19x/Screenshot 2016-02-22 11.08.23.png?dl=0
the

This issue magically disappeared.


Login(email) overflows out of tooltip

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:
Break down in numbered steps

Create a new chat
Enter very long email
In LHN, hover over profile picture

Expected Result:
Describe what you think should've happened
Email is adjusted in tooltip
Actual Result:
Describe what actually happened
Email overflows out of tooltip
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
None
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number:
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @chiragxarora
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1686835382299919
View all open jobs on GitHub

Should be fixed by https://github.com/Expensify/App/pull/20818

Proposal
Please re-state the problem that we are trying to solve in this issue.
Login(email) overflows out of tooltip
What is the root cause of that problem?
There is no Ellipsis effect on text.
What changes do you think we should make in order to solve the problem?
Add prop numberOfLines={1}  here
https://github.com/Expensify/App/blob/9727956e9395f08aac72237891f8db9c280c85c6/src/components/UserDetailsTooltip/index.js#L26
What alternative solutions did you explore? (Optional)

Reassigning, team change

Tracking https://github.com/Expensify/App/pull/20818 for fix

I could not reproduce this in staging nor production.

Same, i think it might be some style caching issue. Can anyone reproduce after clearing cache?

Hi @chiragxarora sorry, can you clarify, are you saying this issue isn't related to https://github.com/Expensify/App/pull/20818?

Hey @chiragxarora, just a tiny suggestion, when writing test steps share the test values to make it a bit easier 🙂
okay so it looks like you used<EMAIL_ADDRESS>I tried setting that as my first name and it looked fine for me locally and on staging,

If possible can you share proper test steps with values for email and name. Without values I'm unsure if you meant for the email to be long or display name.

Sorry, I'm a little lost about where we are with this issue.

Sounds like this isn't related to https://github.com/Expensify/App/issues/20822#issuecomment-1593180839 (which is closed now)
It sounds like we're waiting on an update to the OP to reproduce the issue?
Then we need a proposal to fix this as it's own issue, correct?

I don't understand @chiragxarora the steps here https://github.com/Expensify/App/issues/20839#issuecomment-1615095858 are completely different than the steps in the OP.
Are you reporting a different issue? I feel like this https://github.com/Expensify/App/issues/20839#issuecomment-1615095858 needs to be a different Bug report as what is in the original OP is now fixed.

Thanks for providing those steps @chiragxarora - It looks like this GH is still in a needs reproduction state so a C+/engineer hasn't been assigned.
@chiragsalian was providing feedback based only because they are working on the other GH.
Trying to reproduce this by following these steps:

sign in with an email address of length 50-60 characters
Set your display name as "AB"
hover over your tooltip from LHN/main chat/ header etc

I tried to create an Expensify account for email<EMAIL_ADDRESS>and I'm getting this error "Given Email is not valid".

Can you confirm what email you tested on so I can try and reproduce it?

I've a question, when you use emails like this by adding +111111111, are you able to receive magic code in order to complete sign in?
Yes, I'll get a magic code to my @expensifail.com inbox when I use this email<EMAIL_ADDRESS>

Awesome! I can reproduce following these steps:

sign in with an email address of length 50-60 characters (ex<EMAIL_ADDRESS>Click Settings > Profile
Set your display First name as "AB"
Send a chat to someone
Hover over your name in the chat

Notice the full email overflows

Does this look right @chiragxarora? If yes, I think this is a different bug than what was originally reported in this GH. I think this should be a different GH so you get credit as the reporter. I would report this in #expensify-Bug-source. Let me know if I'm missing a reason to keep it related to this GH.

Okay sounds good, I updated the OP to the steps reproduced here https://github.com/Expensify/App/issues/20839#issuecomment-1619002720
Added external label

nudge to @mananjadhav - thanks!

related? https://github.com/Expensify/App/issues/21100

Hi Team,
Apologies for the delay here. I couldn't update the comments on OOO. @Christinadobrzyn do we for sure know the expected output? I can see both the proposals with correct RCA, but not sure of the expected output. Based on what I see so far, I think @chiragxarora's proposal here looks good, as we don't trim any content. I am also tagging an internal engineer here to second the opinion.
@shawnborton In this case do we want to trim the tooltip content with ellipses? or do we want the content to spillover multiple lines?
🎀 👀 🎀 C+ reviewed.

Reading through the thread that @chiragxarora posted, it does in fact seem like we just want spillover to be broken, so their proposal looks good to me!

Thanks

I'm going to be ooo until August 31st so going to unassign and assign a new teammate.
At this time, we're reviewing the PR and waiting for payment.
@mananjadhav do we need a regression test on this?

Not sure why added an Overdue label, this is deployed to production. Waiting for the regression period.

We first added the styling and actual login to the Tooltip in this PR. I've posted about a comment on the PR here.
I think cases for these are very rare. I had earlier thought about adding an item in the checklist for preWrap check for using Text component. But I am not sure if it is something we want do frequently? @stitesExpensify do you have any thoughts on this?
Also I don't think we need a regression test here.

Thanks @mananjadhav! I will process the other payment in Upwork now.
All set.

Approved 1500 based on https://github.com/Expensify/App/issues/20839#issuecomment-1644135006 and Isa agreeing above.


Fix accidental breakage in test makefile

https://github.com/istio/istio/pull/20668/files accidentally deleted this making the tests break

/cherrypick release-1.5

@howardjohn: new pull request created: #21002

In response to this:

/cherrypick release-1.5

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Gemfile is not a Keybase user

When accessing a folder for the first time in /keybase/private or /keybase/public (or maybe in already visited folders also, but not all the time ...)
my log id: 70e703b87a047b73bf147f1c

Problem found: it is RVM doing some magic and trying to access some files / folders.

Arg. Not sure what the right thing to do is here.  We can whitelist that name so that you don't get error notifications about it, but then if someone legitimately tries to lookup /keybase/public/Gemfile they won't get a very useful error.  Hmmm.
@malgorithms: any suggestions?
FYI, I just reserved the "Gemfile" username so no one can claim it and confuse whatever fix we decide on.

Ok, confirmed RVM, it was just still hiding somewhere else in ZSH configuration.

@strib - yeah, I would say the simplest thing is errors involving Gemfile as a TLF username assertion shouldn't be piped through to the UI. I think that makes sense. Good call on the reservation.


Support for bash scripts using Shellcheck

https://github.com/koalaman/shellcheck can find lot's of issues in shell/bash scripts, it would be awesome if Hound could check for those.
If this is something that's wanted, I'd be happy to look into building a linter for it.

I think it would be great to add support for this. We already have an issue open for this in houndci/hound (https://github.com/houndci/hound/issues/1008), so I'm going to close this one in favor of it.


Automate deployment

Currently, the deployment is rather tedious (archive the project in xcode, sign it, upload a release in github, update the brew tap). This should be automated using github actions.

Introduced in 2f2c6f9124f1dd20d5355f1f772ca797e9c65c72


Make locations recursive

Location groups and locations should become locations with a parent location, and a allow_filter Field.


Fix on some translations

There was some mistyping messages. I fixed them today.

I also added Portuguese translation. There are little changes between Brazilian Portuguese and Portuguese, so I changed the file and created a new one.

Can you please rebase your branch on master? There are conflicts right now.

Merged manually to get this into the 0.5 release.


[source] implement relational database source

Hello folks !
First I want to say thank you for your work on dlt. The idea of a "dbt for EL" + an integration with dbt is just what Data Engineering needed 🙏🏽
Description
A lot of companies don't have an API layer on top of their applications databases. They rely on SQL queries to extract transactional data from applications databases before loading it to the datawarehouse. Maybe there is such a feature but I don't understand how to use it with dlt.
Who will this benefit?
Anyone having relational databases as data sources & relying on "SQLAlchemy-like" connection & SQL to extract data.
Thank you !

we have a simple query/table source that works with any sqlalchemy connection string (it's using pandas internally). the code is in the examples here:

https://github.com/dlt-hub/dlt/blob/2f1e056c61b4913dc8a9f8bd03d01142a2116d95/docs/examples/sources/sql_query.py - the source itself
https://github.com/dlt-hub/dlt/blob/2f1e056c61b4913dc8a9f8bd03d01142a2116d95/docs/examples/read_table.py - usage example

as you can see the source implementation is "almost" one liner :) the performance could be improved by batching and maybe direct sqlalchemy implementation. Unfortunately those examples are not distributed with the library so you may just copy the first file. We really need to think where to put built-in sources and start to distribute them...
are you planning do build something with dlt? the example above can get you started but we are very keen on improving our sources when people do something interesting with them

Hey @rudolfix thank you for the examples, I will try it as soon as I can.
Yes I am actively looking for a way to perform Extract-Load (let's say the Transform is covered with dbt) workloads in a serverless fashion (Cloud Functions/Cloud Run on GCP, Lambda on AWS, etc...) so my ELT workflows don't require expensive SQL databases and Kubernetes Clusters 🤯.
We were planning to develop something similar to dlt in order to standardize our data extraction workflows. The notable differences are :

only 1 loader since my colleagues & I mainly load data as .parquet files in (Google Cloud Storage) buckets & use external tables on top of them to stage them in our data warehouse (BigQuery).
use YAML to define our data sources and then run boilerplates code according to the source type, parameters, etc...

then you may be interested in the duckdb destination that was released today and the dbt support that is built in with dlt. with duckdb you can generate parquet trivially just by using COPY TO sql statements - and this is a feature (a parquet destination) that we plan to release in 1-2 weeks.

https://dlthub.com/docs/destinations#destination-configuration
https://github.com/dlt-hub/dlt/blob/devel/docs/examples/dbt_run_jaffle.py

this will work in lambda function. duckdb is just 1MB c++ code (if you do not know it yet) and I know that people run it on AWS lambda so GCP counterpart will work as well.
catalogue registration (ie. AWS Glue or GCP) is also something that we look at but we didn't figure out if there's interest for it

Cool ! I'm a big fan of duckdb, I already use it as an in-memory Analytical database (for light local project) but I should explore using it in our Cloud ELT Workflows.

I'm going to close this issue since dlt supports relational database sources. Thank you @rudolfix

we have a simple query/table source that works with any sqlalchemy connection string (it's using pandas internally). the code is in the examples here:

https://github.com/dlt-hub/dlt/blob/2f1e056c61b4913dc8a9f8bd03d01142a2116d95/docs/examples/sources/sql_query.py - the source itself
https://github.com/dlt-hub/dlt/blob/2f1e056c61b4913dc8a9f8bd03d01142a2116d95/docs/examples/read_table.py - usage example

as you can see the source implementation is "almost" one liner :) the performance could be improved by batching and maybe direct sqlalchemy implementation. Unfortunately those examples are not distributed with the library so you may just copy the first file. We really need to think where to put built-in sources and start to distribute them...


Add event handlers to DnD

Codecov Report

Merging #142 (e4c7142) into master (3f790ec) will decrease coverage by 0.17%.
The diff coverage is 61.53%.

@@            Coverage Diff             @@
##           master     #142      +/-   ##
==========================================
- Coverage   60.04%   59.86%   -0.18%
==========================================
  Files          17       17
  Lines         443      451       +8
  Branches       79       83       +4
==========================================
+ Hits          266      270       +4
- Misses        147      149       +2
- Partials       30       32       +2

Impacted Files
Coverage Δ

packages/dnd/src/Droppable/Droppable.js
0.00% <0.00%> (ø)

packages/dnd/src/DnDStore/DnDStoreImp.js
81.81% <75.00%> (-18.19%)
:arrow_down:

packages/store/src/Store.js
96.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Wonky css when combined with Bootstrap

Just tried to use this with Bootstrap and what was nicely highlighted code with hightlightjs became a weirdly spaced mess.
Please check css to make compatible with Bootstrap v4

Hi @SumNeuron thank you for feedback!
I tried to use default version of plugin and bootstrap, works fine.
Note: This plugin styles full customizable, and you can change each property.
Could you please provide me with an example of messed view?

@wcoder I think @SumNeuron means

@xiaozi0lei thank you for the detailed answer!
I will close this issue, if anyone has the same problem, please write here.


New env push fails

Describe the bug
I created a new environment called prod. When I run amplify status I can see all the categories are set to create in the new env. I run amplify push and I get an error that the s3 bucket already exists. I delete in the console even though I believe the push created it and it still fails.
To Reproduce
Steps to reproduce the behavior:

create new environment in an existing project with another environment
push new env
See error

Expected behavior
A new environment is created
Desktop (please complete the following information):

OS: [macOS
Browser N/A
Version 1.1.7

Additional context
Logs:
CREATE_IN_PROGRESS functionsetUsersGroup    AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:31 GMT-0400 (Eastern Daylight Time)
UPDATE_IN_PROGRESS modernapp-20190321144926 AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:26 GMT-0400 (Eastern Daylight Time) User Initiated
⠏ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS functionsendEmail       AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:32 GMT-0400 (Eastern Daylight Time)
CREATE_IN_PROGRESS authcognito5cc85e6d     AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:31 GMT-0400 (Eastern Daylight Time)
CREATE_IN_PROGRESS storagemodernAppStorage AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:31 GMT-0400 (Eastern Daylight Time)
⠴ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS functionsendEmail       AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:32 GMT-0400 (Eastern Daylight Time) Resource creation Initiated
CREATE_IN_PROGRESS authcognito5cc85e6d     AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:32 GMT-0400 (Eastern Daylight Time) Resource creation Initiated
CREATE_IN_PROGRESS storagemodernAppStorage AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:32 GMT-0400 (Eastern Daylight Time) Resource creation Initiated
CREATE_IN_PROGRESS functionsetUsersGroup   AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:32 GMT-0400 (Eastern Daylight Time) Resource creation Initiated
⠇ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS modernapp-20190321144926-functionsendEmail-1CWKLBT6TOQVH AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:32 GMT-0400 (Eastern Daylight Time) User Initiated
⠋ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS modernapp-20190321144926-authcognito5cc85e6d-AEJGT6D7A4YV AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:32 GMT-0400 (Eastern Daylight Time) User Initiated
⠙ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS S3Bucket                                                       AWS::S3::Bucket            Thu Mar 21 2019 22:16:37 GMT-0400 (Eastern Daylight Time)
CREATE_IN_PROGRESS modernapp-20190321144926-storagemodernAppStorage-199QQQ58AHE7X AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:32 GMT-0400 (Eastern Daylight Time) User Initiated
⠹ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS LambdaExecutionRole                                         AWS::IAM::Role             Thu Mar 21 2019 22:16:37 GMT-0400 (Eastern Daylight Time) Resource creation Initiated
CREATE_IN_PROGRESS LambdaExecutionRole                                         AWS::IAM::Role             Thu Mar 21 2019 22:16:36 GMT-0400 (Eastern Daylight Time)
CREATE_IN_PROGRESS modernapp-20190321144926-functionsetUsersGroup-OTZ6I6YYWE7Z AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:32 GMT-0400 (Eastern Daylight Time) User Initiated
⠏ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS LambdaExecutionRole AWS::IAM::Role Thu Mar 21 2019 22:16:37 GMT-0400 (Eastern Daylight Time)
⠹ Updating resources in the cloud. This may take a few minutes...

CREATE_FAILED S3Bucket AWS::S3::Bucket Thu Mar 21 2019 22:16:37 GMT-0400 (Eastern Daylight Time) modern-app-storage-prod already exists
⠴ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS LambdaExecutionRole AWS::IAM::Role Thu Mar 21 2019 22:16:38 GMT-0400 (Eastern Daylight Time) Resource creation Initiated
⠦ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS SNSRole AWS::IAM::Role Thu Mar 21 2019 22:16:40 GMT-0400 (Eastern Daylight Time) Resource creation Initiated
CREATE_IN_PROGRESS SNSRole AWS::IAM::Role Thu Mar 21 2019 22:16:39 GMT-0400 (Eastern Daylight Time)
⠧ Updating resources in the cloud. This may take a few minutes...

CREATE_FAILED modernapp-20190321144926-storagemodernAppStorage-199QQQ58AHE7X AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:39 GMT-0400 (Eastern Daylight Time) The following resource(s) failed to create: [S3Bucket].
⠸ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_IN_PROGRESS modernapp-20190321144926 AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:44 GMT-0400 (Eastern Daylight Time) The following resource(s) failed to create: [storagemodernAppStorage, functionsetUsersGroup, authcognito5cc85e6d, functionsendEmail].
CREATE_FAILED               functionsendEmail        AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:43 GMT-0400 (Eastern Daylight Time) Resource creation cancelled
CREATE_FAILED               functionsetUsersGroup    AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:43 GMT-0400 (Eastern Daylight Time) Resource creation cancelled
CREATE_FAILED               authcognito5cc85e6d      AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:43 GMT-0400 (Eastern Daylight Time) Resource creation cancelled
CREATE_FAILED               storagemodernAppStorage  AWS::CloudFormation::Stack Thu Mar 21 2019 22:16:43 GMT-0400 (Eastern Daylight Time) Embedded stack arn:aws:cloudformation:us-east-1:473356752602:stack/modernapp-20190321144926-storagemodernAppStorage-199QQQ58AHE7X/8290ba30-4c48-11e9-ad6b-12c395c1242e was not successfully created: The following resource(s) failed to create: [S3Bucket].
⠴ Updating resources in the cloud. This may take a few minutes...

CREATE_COMPLETE LambdaExecutionRole AWS::IAM::Role Thu Mar 21 2019 22:16:52 GMT-0400 (Eastern Daylight Time)
⠧ Updating resources in the cloud. This may take a few minutes...

CREATE_COMPLETE LambdaExecutionRole AWS::IAM::Role Thu Mar 21 2019 22:16:50 GMT-0400 (Eastern Daylight Time)
⠏ Updating resources in the cloud. This may take a few minutes...

CREATE_COMPLETE    LambdaFunction AWS::Lambda::Function Thu Mar 21 2019 22:16:56 GMT-0400 (Eastern Daylight Time)
CREATE_IN_PROGRESS LambdaFunction AWS::Lambda::Function Thu Mar 21 2019 22:16:56 GMT-0400 (Eastern Daylight Time) Resource creation Initiated
CREATE_IN_PROGRESS LambdaFunction AWS::Lambda::Function Thu Mar 21 2019 22:16:55 GMT-0400 (Eastern Daylight Time)
⠹ Updating resources in the cloud. This may take a few minutes...

CREATE_COMPLETE SNSRole AWS::IAM::Role Thu Mar 21 2019 22:16:54 GMT-0400 (Eastern Daylight Time)
⠸ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS lambdaexecutionpolicy AWS::IAM::Policy Thu Mar 21 2019 22:17:00 GMT-0400 (Eastern Daylight Time) Resource creation Initiated
CREATE_IN_PROGRESS lambdaexecutionpolicy AWS::IAM::Policy Thu Mar 21 2019 22:16:59 GMT-0400 (Eastern Daylight Time)
⠴ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS LambdaFunction AWS::Lambda::Function Thu Mar 21 2019 22:17:02 GMT-0400 (Eastern Daylight Time) Resource creation Initiated
CREATE_IN_PROGRESS LambdaFunction AWS::Lambda::Function Thu Mar 21 2019 22:17:01 GMT-0400 (Eastern Daylight Time)
⠦ Updating resources in the cloud. This may take a few minutes...

CREATE_COMPLETE    UserPool AWS::Cognito::UserPool Thu Mar 21 2019 22:17:01 GMT-0400 (Eastern Daylight Time)
CREATE_IN_PROGRESS UserPool AWS::Cognito::UserPool Thu Mar 21 2019 22:17:01 GMT-0400 (Eastern Daylight Time) Resource creation Initiated
CREATE_IN_PROGRESS UserPool AWS::Cognito::UserPool Thu Mar 21 2019 22:16:58 GMT-0400 (Eastern Daylight Time)
⠦ Updating resources in the cloud. This may take a few minutes...

CREATE_COMPLETE LambdaFunction AWS::Lambda::Function Thu Mar 21 2019 22:17:02 GMT-0400 (Eastern Daylight Time)
⠏ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE_CLEANUP_IN_PROGRESS modernapp-20190321144926 AWS::CloudFormation::Stack Thu Mar 21 2019 22:17:05 GMT-0400 (Eastern Daylight Time)
⠼ Updating resources in the cloud. This may take a few minutes...

CREATE_COMPLETE lambdaexecutionpolicy AWS::IAM::Policy Thu Mar 21 2019 22:17:06 GMT-0400 (Eastern Daylight Time)
⠴ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS lambdaexecutionpolicy AWS::IAM::Policy Thu Mar 21 2019 22:17:06 GMT-0400 (Eastern Daylight Time) Resource creation Initiated
CREATE_IN_PROGRESS lambdaexecutionpolicy AWS::IAM::Policy Thu Mar 21 2019 22:17:05 GMT-0400 (Eastern Daylight Time)
⠦ Updating resources in the cloud. This may take a few minutes...

CREATE_IN_PROGRESS UserPoolClient    AWS::Cognito::UserPoolClient Thu Mar 21 2019 22:17:06 GMT-0400 (Eastern Daylight Time)
CREATE_IN_PROGRESS UserPoolClientWeb AWS::Cognito::UserPoolClient Thu Mar 21 2019 22:17:06 GMT-0400 (Eastern Daylight Time)
⠙ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS modernapp-20190321144926-functionsendEmail-1CWKLBT6TOQVH AWS::CloudFormation::Stack Thu Mar 21 2019 22:17:07 GMT-0400 (Eastern Daylight Time) User Initiated
⠼ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS modernapp-20190321144926-authcognito5cc85e6d-AEJGT6D7A4YV AWS::CloudFormation::Stack Thu Mar 21 2019 22:17:08 GMT-0400 (Eastern Daylight Time) User Initiated
⠴ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS modernapp-20190321144926-functionsetUsersGroup-OTZ6I6YYWE7Z AWS::CloudFormation::Stack Thu Mar 21 2019 22:17:08 GMT-0400 (Eastern Daylight Time) User Initiated

DELETE_IN_PROGRESS modernapp-20190321144926-storagemodernAppStorage-199QQQ58AHE7X AWS::CloudFormation::Stack Thu Mar 21 2019 22:17:08 GMT-0400 (Eastern Daylight Time) User Initiated
⠏ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS authcognito5cc85e6d     AWS::CloudFormation::Stack Thu Mar 21 2019 22:17:07 GMT-0400 (Eastern Daylight Time)
DELETE_IN_PROGRESS storagemodernAppStorage AWS::CloudFormation::Stack Thu Mar 21 2019 22:17:07 GMT-0400 (Eastern Daylight Time)
DELETE_IN_PROGRESS functionsetUsersGroup   AWS::CloudFormation::Stack Thu Mar 21 2019 22:17:07 GMT-0400 (Eastern Daylight Time)
DELETE_IN_PROGRESS functionsendEmail       AWS::CloudFormation::Stack Thu Mar 21 2019 22:17:07 GMT-0400 (Eastern Daylight Time)
⠸ Updating resources in the cloud. This may take a few minutes...

CREATE_FAILED UserPoolClient    AWS::Cognito::UserPoolClient Thu Mar 21 2019 22:17:09 GMT-0400 (Eastern Daylight Time) Resource creation cancelled
CREATE_FAILED UserPoolClientWeb AWS::Cognito::UserPoolClient Thu Mar 21 2019 22:17:08 GMT-0400 (Eastern Daylight Time) Resource creation cancelled
⠼ Updating resources in the cloud. This may take a few minutes...

CREATE_FAILED lambdaexecutionpolicy AWS::IAM::Policy Thu Mar 21 2019 22:17:08 GMT-0400 (Eastern Daylight Time) Resource creation cancelled
⠼ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE modernapp-20190321144926-storagemodernAppStorage-199QQQ58AHE7X AWS::CloudFormation::Stack Thu Mar 21 2019 22:17:10 GMT-0400 (Eastern Daylight Time)
DELETE_SKIPPED  S3Bucket                                                       AWS::S3::Bucket            Thu Mar 21 2019 22:17:09 GMT-0400 (Eastern Daylight Time)
⠙ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE storagemodernAppStorage AWS::CloudFormation::Stack Thu Mar 21 2019 22:17:18 GMT-0400 (Eastern Daylight Time)
⠴ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE    UserPoolClient    AWS::Cognito::UserPoolClient Thu Mar 21 2019 22:17:36 GMT-0400 (Eastern Daylight Time)
DELETE_COMPLETE    UserPoolClientWeb AWS::Cognito::UserPoolClient Thu Mar 21 2019 22:17:36 GMT-0400 (Eastern Daylight Time)
DELETE_IN_PROGRESS UserPoolClient    AWS::Cognito::UserPoolClient Thu Mar 21 2019 22:17:34 GMT-0400 (Eastern Daylight Time)
DELETE_IN_PROGRESS UserPoolClientWeb AWS::Cognito::UserPoolClient Thu Mar 21 2019 22:17:34 GMT-0400 (Eastern Daylight Time)

DELETE_IN_PROGRESS LambdaFunction        AWS::Lambda::Function Thu Mar 21 2019 22:17:36 GMT-0400 (Eastern Daylight Time)
DELETE_COMPLETE    lambdaexecutionpolicy AWS::IAM::Policy      Thu Mar 21 2019 22:17:35 GMT-0400 (Eastern Daylight Time)
DELETE_IN_PROGRESS lambdaexecutionpolicy AWS::IAM::Policy      Thu Mar 21 2019 22:17:34 GMT-0400 (Eastern Daylight Time)
⠧ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS LambdaFunction        AWS::Lambda::Function Thu Mar 21 2019 22:17:37 GMT-0400 (Eastern Daylight Time)
DELETE_COMPLETE    lambdaexecutionpolicy AWS::IAM::Policy      Thu Mar 21 2019 22:17:35 GMT-0400 (Eastern Daylight Time)
DELETE_IN_PROGRESS lambdaexecutionpolicy AWS::IAM::Policy      Thu Mar 21 2019 22:17:34 GMT-0400 (Eastern Daylight Time)
⠧ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS UserPool AWS::Cognito::UserPool Thu Mar 21 2019 22:17:37 GMT-0400 (Eastern Daylight Time)
⠏ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE LambdaFunction AWS::Lambda::Function Thu Mar 21 2019 22:17:37 GMT-0400 (Eastern Daylight Time)

DELETE_COMPLETE LambdaFunction AWS::Lambda::Function Thu Mar 21 2019 22:17:37 GMT-0400 (Eastern Daylight Time)
⠧ Updating resources in the cloud. This may take a few minutes...

DELETE_IN_PROGRESS SNSRole  AWS::IAM::Role         Thu Mar 21 2019 22:17:40 GMT-0400 (Eastern Daylight Time)
DELETE_COMPLETE    UserPool AWS::Cognito::UserPool Thu Mar 21 2019 22:17:39 GMT-0400 (Eastern Daylight Time)
⠇ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE    modernapp-20190321144926-functionsetUsersGroup-OTZ6I6YYWE7Z AWS::CloudFormation::Stack Thu Mar 21 2019 22:17:40 GMT-0400 (Eastern Daylight Time)
DELETE_COMPLETE    LambdaExecutionRole                                         AWS::IAM::Role             Thu Mar 21 2019 22:17:39 GMT-0400 (Eastern Daylight Time)
DELETE_IN_PROGRESS LambdaExecutionRole                                         AWS::IAM::Role             Thu Mar 21 2019 22:17:38 GMT-0400 (Eastern Daylight Time)
⠏ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE    modernapp-20190321144926-functionsendEmail-1CWKLBT6TOQVH AWS::CloudFormation::Stack Thu Mar 21 2019 22:17:40 GMT-0400 (Eastern Daylight Time)
DELETE_COMPLETE    LambdaExecutionRole                                      AWS::IAM::Role             Thu Mar 21 2019 22:17:39 GMT-0400 (Eastern Daylight Time)
DELETE_IN_PROGRESS LambdaExecutionRole                                      AWS::IAM::Role             Thu Mar 21 2019 22:17:38 GMT-0400 (Eastern Daylight Time)
⠹ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE functionsetUsersGroup AWS::CloudFormation::Stack Thu Mar 21 2019 22:17:42 GMT-0400 (Eastern Daylight Time)
DELETE_COMPLETE functionsendEmail     AWS::CloudFormation::Stack Thu Mar 21 2019 22:17:41 GMT-0400 (Eastern Daylight Time)
⠦ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE SNSRole AWS::IAM::Role Thu Mar 21 2019 22:17:42 GMT-0400 (Eastern Daylight Time)
⠇ Updating resources in the cloud. This may take a few minutes...

DELETE_COMPLETE modernapp-20190321144926-authcognito5cc85e6d-AEJGT6D7A4YV AWS::CloudFormation::Stack Thu Mar 21 2019 22:17:43 GMT-0400 (Eastern Daylight Time)
⠙ Updating resources in the cloud. This may take a few minutes...

UPDATE_ROLLBACK_COMPLETE modernapp-20190321144926 AWS::CloudFormation::Stack Thu Mar 21 2019 22:17:55 GMT-0400 (Eastern Daylight Time)
DELETE_COMPLETE          authcognito5cc85e6d      AWS::CloudFormation::Stack Thu Mar 21 2019 22:17:55 GMT-0400 (Eastern Daylight Time)
⠋ Updating resources in the cloud. This may take a few minutes...Error updating cloudformation stack
⠋ Updating resources in the cloud. This may take a few minutes...

Following resources failed

Resource Name: S3Bucket (AWS::S3::Bucket)
Event Type: create
Reason: modern-app-storage-prod already exists

Resource Name: 4fea4ab1nnv17hc2hs3jnisqsd (AWS::Cognito::UserPoolClient)
Event Type: create
Reason: Resource creation cancelled

Resource Name: 91p9mpfvbfi3dgajihvstm5bc (AWS::Cognito::UserPoolClient)
Event Type: create
Reason: Resource creation cancelled

Resource Name: moder-lamb-7VR0EJQ4BJKW (AWS::IAM::Policy)
Event Type: create
Reason: Resource creation cancelled

✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete

@aireater Could you please delete the "modern-app-storage-prod" bucket from your S3 console and try the push again? Looks like there is a hanging S3 bucket which has the same name.

@kaustavghosh06  that's what I thought too but it was not there before the push. I deleted it and pushed again and got the following error:
Resource Name: SendEmailLambdaDataSourceRole (AWS::IAM::Role)
Event Type: create
Reason: SendEmailLambdaDataSourceRole already exists in stack arn:aws:cloudformation:us-east-1:473356752602:stack/modernapp-20190222141121-apiModernApp-3R4D1S7100E6-CustomResourcesjson-ZJE9TDBJBZM6/1dacae50-36d9-11e9-a64f-0a30b495b19a

There is only one SendEmailLambdaDataSourceRole and i believe this is the one that was created in the dev environment I already have created.

SendEmailLambdaDataSourceRole is created in my CustomResources.json file following the documentation.
Do i need to put the ${env} variable in the name as well to create the resource in multi environments?

Yes, you’re right. You would’ve to add an env prefix or postfix since IAM role names are global and need to be unique in an AWS account.


Unable to find gradlew..

I tried flutter run.but still the error exists.. gradlew.bat is not downloading.. but while running it shows downloading gradle wrapper

Hi @muthu-gokul
can you please provide your flutter doctor -v
and flutter run --verbose?

Target file verbose not found

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore going to close it.
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v'  please.


“Editor is not responding” dialog should not be blocking

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
→ This issue cannot be reproduced reliably in Safe Mode, presumably because less packages are loaded then or some offending packages are not loaded. However, as in normal mode there are always an increasing number of packages to be loaded, some of which might have loading issues, as users grow to use Atom for an increasing number of purposes, this appears to be a general problem and should be solved in a general way.
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
→ general usability issue
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
→ After I reproduced the issue several times in normal, and checked in Safe Mode, I ran atom --clear-window-state without significant improvement.
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
→ search for responding AFAICS yields similar issues, but no suitable matches for the general problem with the current approach (CMIIW)
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages
→ not a case of missing functionality

Description
The “Editor is not responding” dialog is blocking Atom when it appears. The user is forced to make a choice between “Force Close” and “Keep Waiting” to continue, even if the problem was only temporary.
Steps to Reproduce

Start Atom, optionally when automatically restoring a session that has several windows with several tabs open (the test case had 5 windows, each with 5 to 10 editor/PDF viewer tabs open – maybe I am the Atom “power user” that nobody imagined :)).
Optionally, do something in Atom that takes a long time to complete.
Optionally, exit such an Atom session.

Expected behavior: When the editor is responding again, close the dialog automatically and continue as if nothing happened, as I have observed in the Chromium (57.0.2987.98) Web browser. [For QA, a non-modal message could still be displayed later, perhaps indicating which package(s) caused the delay and/or offer to submit a bug report.]
Actual behavior: Atom does not continue in any window of a session until the user makes the choice for the affected window. Especially, if the first window of a session to be restored is blocked by the dialog, all other windows remain blank until the choice for the first window is made. Then the choice for the second window might need to be made, and so on.
In effect, if the user does not want to compromise their session by “Force Close”, they are forced, sometimes for each window and sometimes even repeatedly for one window, to select “Keep Waiting” in up to all windows of a session to get Atom working (again) or to terminate it cleanly.
Reproduces how often: Always, especially with many installed or with few or many slow loading/working packages, or many windows or many restored editor tabs per window.
Versions
$ atom --version
Atom    : 1.23.1
Electron: 1.6.15
Chrome  : 56.0.2924.87
Node    : 7.4.0

$ apm --version
apm  1.18.11
npm  3.10.10
node 6.9.5 x64
atom 1.23.1
python 2.7.12+
git 2.11.0

OS: Debian/Devuan GNU+Linux jessie/stretch/sid
But: This has probably been an issue since the first versions of Atom (which I used). With an increasing number of (useful) packages installed, and parallel work (in several windows) to be done, it just has now reached a point where the situation has become unbearable. Hence this bug report.

Thanks for taking the time to contribute!  I think this is basically a duplicate of https://github.com/atom/atom/issues/11551 so you can subscribe there for updates if you'd like.
If I mis-understood anything, please let me know.

Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


Svc classfier accuracy is very poor on 300 people dataset

I have trained a SVC classifier on 300 people dataset. 40 images/ person
But accuracy is very very poor, less than 0.5

Any updates


Follow up on #26

This is a follow up PR for #26

[x] Fix a bug found during review
[x] Modify the constrcutor to make it backward compatible
[x] Other minor formatting and messages

This is the commit containing the changes.
@Aeon512 (if you agree we can close #26 in favor of this one. I've kept your commits authoring BTW).
@reviewbybees

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.

🐝

This is great! When will the next release be which would include this?

1.11 - already released, should be in your update center now.


test-branch/execute-job/quoted-authorization/ce83f566-3582-4e5a-8f8a-6c6eeb2c1e8f

PR for testing 87568af3588f227b3ceb3a7b3cd8f829e58c3f79

/canonical/self-hosted-runners/run-workflows 87568af3588f227b3ceb3a7b3cd8f829e58c3f79


Add getVersion

#336 Add get release version from RPC

The comment should be like this: // The comments
Would you please add a test case at tests/interfaces/rpc folder?

@Kayryu will do it later.


MNT: Re-rendered with conda-smithy 1.7.0

python 3.6

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

There should be one empty line at the end of the file.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge/ase Ready for review/merge!

Some of the files have executable permissions here too. 😕 Could you please try re-rendering again?

I have added @CJ-Wright to maintainers and re-rendered the package again. Merged in other PR (https://github.com/conda-forge/ase-feedstock/pull/3). Closing this one as redundant. You can re-open it if there is something extra I have missed.

I'd really curious to know what happened in the re-rendering, @CJ-Wright . If you please could open an issue at conda-smithy documenting your steps and environment information, that would be very helpful for determining what the underlying issue is.

@jochym Thank you!
@jakirkham I will open an issue.


--adminUrl param doesn't work [develop branch]

Hi, I've found out the --adminUrl param doesn't work in develop branch. You would surely find it soon.
Problem is there src/Commands/Common/NewCommand.php#L155-L156, as you are using admin_name in defaults.

--adminUrl is the right one. Thanks for submitting. I've fixed it.


Bad link in the page

MSDN Link in the "The developer content for earlier versions of Microsoft Dynamics 365 Customer Engagement continue to be available on MSDN." returns user back to same documentation. No documentations for older content available in the link.

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a98ac9c0-258b-308b-5756-0ab5fd5da9e5
Version Independent ID: f873193b-bb93-8064-6fb4-7a4a8b9ae6f1
Content: Release history (Developer Guide for Dynamics 365 Customer Engagement)
Content Source: ce/developer/release-history.md
Service: crm-online
GitHub Login: @JimDaly
Microsoft Alias: jdaly

This is a known issue and the doc team is working to resolve.

This issue is resolved now. Thanks for reporting.


umap crashes max with a specific sound

this patch with this soundfile crash max when at point 2.5 (umap) -there must be something in the points that triggers an exception. Both in Test home compile and in Release CI compile.
Archive.zip

bug report in Test mode:
Process: Max [1475]
Path: /Applications/Max.app/Contents/MacOS/Max
Identifier: com.cycling74.Max
Version: 8.2.1 [2f7eaf31afd] (8.2.1)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Max [1475]
User ID: 501
Date/Time: 2022-07-10 14:20:03.533 +0200
OS Version: macOS 11.2.1 (20D74)
Report Version: 12
Anonymous UUID: 1CEE2877-ACA1-AF56-6B62-4814F29E546A
Time Awake Since Boot: 720 seconds
System Integrity Protection: enabled
Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Application Specific Information:
Assertion failed: (impl::checkBounds(mDesc, args...) && "Arguments out of bounds"), function operator(), file /Users/pa/Documents/documents@hudd/research/projects/fluid corpus navigation/research/fluid_decomposition/include/clients/nrt/../common/../../data/FluidTensor.hpp, line 568.
Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff2047a462 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff204a8610 pthread_kill + 263
2 libsystem_c.dylib 0x00007fff203fb720 abort + 120
3 libsystem_c.dylib 0x00007fff203fa9d6 __assert_rtn + 314
4 org.flucoma.fluid.libmanipulation	0x0000000134592c92 fluid::algorithm::UMAP::makeGraph(fluid::FluidDataSet<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >, double, 1l> const&, long, Eigen::SparseMatrix<double, 0, int>&, Eigen::Ref<Eigen::Array<double, -1, -1, 0, -1, -1>, 0, Eigen::OuterStride<-1> >, bool) const + 946
5 org.flucoma.fluid.libmanipulation	0x00000001345907bd fluid::algorithm::UMAP::train(fluid::FluidDataSet<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >, double, 1l>&, long, long, double, long, double) + 1277
6 org.flucoma.fluid.libmanipulation	0x000000013458c58f fluid::client::umap::UMAPClient::fitTransform(fluid::client::SharedClientRef<fluid::client::dataset::DataSetClient const>, fluid::client::SharedClientReffluid::client::dataset::DataSetClient) + 1039

Think this is a duplicate of #104

In makeGraph we can see that the code assumes it can rely on there being at least numNeighbours + 1 data points if discardFirst is true.
@g-roma  I'm assuming the thing to do here, as with #104, is to add a check into UMAPClient that we actually have enough data points to proceed, and maybe also an assertion here in makeGraph ?
https://github.com/flucoma/flucoma-core/blob/804a3b39260087223f304787bcba4acce445c68b/include/algorithms/public/UMAP.hpp#L265-L283


Repo missing basic description

The README and repo description are self-referential and depend on the external website to provide a basic description of what the project does.  I would suggest copying at least a brief one or two sentences to supplement the information to newcomers that find the repo before the main site such as QPDF is a command-line program that does structural, content-preserving transformations on PDF files.

Yes, you are correct. It's been a while since I've actually read the README carefully. I will definitely fix this. Thanks for bring it to my attention.

Looking at this reminds me of how it feels when someone tells you you have a big glop of food spilled on your shirt...you simultaneously appreciate that they told you and wonder how long you've been walking around like that and who has noticed. :-) I'm guessing I probably wrote this README originally for display once you'd navigated down into the files area on sourceforge, and when I moved stuff to github, I probably didn't think about adjusting it for its new context. Oh well. Now that I know about it, I can definitely make it a better first thing for someone to see.

It is an understandable oversight as the project moved from sourceforge to GitHub.  No reason to be embarrassed about it.
Improving it would help newcomers to the project and potentially boost the project's popularity overtime by lowering the barrier to entry.

Looking at this reminds me of how it feels when someone tells you you have a big glop of food spilled on your shirt..
you simultaneously appreciate that they told you and wonder how long you've been walking around like that and
who has noticed.

Updating documentation is quite annoying. I struggle with that in regards to my own projects. I am trying to treat
documentation "equal" to code but it's less fun to write high-quality documentation compared to code that does
things on its own. Perhaps one day true A.I. could write high-quality documentation automatically.
More on topic, I think the main README can serve as an entry point to other articles or links just fine. Perhaps you
can also have contributors help, e. g. write a summary in the issue description by contributors, then attach it to the
wiki and/or some internal area in doc/ or wherever qpdf is storing descriptions. And perhaps even have more people
contribute to the docs easily - I remember in ruby-gtk3 I was able to modify the files via the browser directly. This
actually helps a LOT, in particular when people aren't super-knowledgable about git on the commandline.


Allow rich 13.x

Based on the changelog, the only relevant breaking change is that support for Python 3.6 is removed:
https://github.com/Textualize/rich/blob/v13.0.0/CHANGELOG.md#1300---2022-12-30
This is OK even though we support Python 3.6 in typer, because we do still allow older versions of rich that are compatible with Python 3.6.

I am very much looking forward to this change as currently there is no easy way to use the latest versions of textualize along with the typer since:
Because no versions of textual match >0.10.1,<0.11.0
 and textual (0.10.1) depends on rich (>12.6.0), textual (>=0.10.1,<0.11.0) requires rich (>12.6.0).
Because typer (0.7.0) depends on rich (>=10.11.0,<13.0.0)
 and no versions of rich match >12.6.0,<13.0.0, typer (0.7.0) requires rich (>=10.11.0,<=12.6.0).
Thus, textual (>=0.10.1,<0.11.0) is incompatible with typer (0.7.0).
So, because my_app depends on both typer (0.7.0) and textual (^0.10.1), version solving failed.

Can any actions help offload the review responsibilities from tialango or other maintainers? I understand he's busy across multiple projects and his day job, but happy to help if there is a way to get this merged

100% support this (and generally not capping dependencies, even more so for a less-actively maintained project; see a lot of great arguments in https://iscinumpy.dev/post/bound-version-constraints/).
That being said, rich is an extra, so an easy workaround is to just depend on the additional dependencies:
- typer[all]
+ typer
+ colorama >=0.4.3,<0.5.0
+ shellingham >=1.3.0,<2.0.0
+ rich >=10.11.0,<14.0.0

Not perfect, but it gets the job done for a consuming library blocked by this.

@musicinmybrain Can you merge this ?

@musicinmybrain Can you merge this ?

I’m afraid not. I’m not a maintainer of this project, and I have no permissions on the repository.

My bad, I falsely assumed your PR was reviewed by maintainers.

Thanks @musicinmybrain! :rocket:
And thanks @atmartinez for you review with a comment explaining what you did to test it, that helps a lot! :bow:
This will be available in Typer 0.8.0 released in the next few hours.


S3 Artifact multi-namespace security vulnerability

Is this a BUG REPORT or FEATURE REQUEST?:
Both
What happened:
Context:
We want to run workflows in multiple namespaces.
We want to use s3 for storing artifacts.
Storing and retrieving artifacts is handled by the argoexec sidecar pod.
For s3 this pod directly connects to s3.
To connect to s3 the sidecar needs s3 credentials. These credentials need to be present in each namespace that we want to run workflows.
Having these credentials in each namespace opens up the s3 bucket to all namespaces. Having artifacts from one namespace available to other namespaces.
Proper namespace isolation cannot be done in this way.
What you expected to happen:
Storing and retrieving artifacts is proxied by the controller which handles the connection to s3. The controller first checks if the workflow is authorized to obtain the artifact.
This way direct access to the storage location is shielded and the artifact storage can be used for all namespaces.
Running a controller in each namespace or having a s3 bucket per namespace (currently not possible) are not feasible scaling solutions.
How to reproduce it (as minimally and precisely as possible):
Run workflows in seperate namespaces
Anything else we need to know?:
Environment:

Argo version: 2.2.1
Kubernetes version : 1.12.4

Just ran across this issue since I'm considering how to secure argo in my own cluster.
As an alternative, couldn't you modify the keyFormat in the argo cm to include the workflow namespace as the first part of the path:
https://github.com/argoproj/argo/blob/9ab1bc88f58c551208ce5e76eea0c6fb83359710/docs/workflow-controller-configmap.yaml#L62
keyFormat: {{workflow.namespace}}/{{workflow.name}}/{{pod.name}}
Then for each namespace that you could provision a user (or get credentials in another way like IRSA/kiam) that has privs only to the path that corresponds to your namespace.
This wouldn't work for minio since I don't see a way to restrict access to paths and I'm not familiar enough with GCS to determine if it's feasible there, but it should work for S3 directly at least.

i don't want create a new secret, minio have already auto create one , i want use secret in minio namespace, is it possible?
root@ubuntu:~# kubectl -n minio get secrets minio -o yaml
apiVersion: v1
data:
  rootPassword: bWluaW8xMjM=
  rootUser: YWRtaW4=
kind: Secret
metadata:
  annotations:
    meta.helm.sh/release-name: minio
    meta.helm.sh/release-namespace: minio
  creationTimestamp: "2023-08-23T08:05:56Z"
  labels:
    app: minio
    app.kubernetes.io/managed-by: Helm
    chart: minio-5.0.13
    heritage: Helm
    release: minio
  name: minio
  namespace: minio
  resourceVersion: "7979291"
  uid: 52146e18-d5ef-4a3e-bc6f-f60b7ee22b97
type: Opaque


chore(main): release 1.1.4

:robot: I have created a release beep boop
1.1.4 (2023-08-18)
Bug Fixes

修改 auto merge action 配置 (acbaa75)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/lwsgh/release-please-example/releases/tag/v1.1.4 :sunflower:


Info needed: TriggerActionFlow for Scheduled Actions

Expected Behavior
We should be able to process the records at the scheduled time. Just like the Scheduled Path in Record Triggered Flows.
Actual Behavior
Steps to Reproduce the Problem

Specifications

Version:
Platform:

Hello,
Unfortunately the Trigger Actions Framework uses autolaunched flows which cannot support scheduled actions.

Can we work on a logic which schedules a call for the scheduled trigger flow and then call another autolaunch flow or same flow on the scheduled run?

Unfortunately, time based actions are not really part of the framework. The framework is meant to partition, order, and control bypassing for synchronous trigger logic.
Feel free to try to create on your own and raise a pull request; I will close this issue for now though.


Support for local CoPilot

Hey, I'd like to do something similar to https://github.com/danielgross/localpilot, which sets github.copilot.advanced.debug.{testOverrideProxyUrl,overrideProxyUrl} to a different URL in settings.json in order to avoid having to access GitHub.
I was unable to find any way to set settings.json variables in the ELisp code. I was also unsuccessful in hardcoding the appropriate values in agent.js.
What pieces are missing to avoid the proprietary remote APIs? Or would maybe just adding a way to pass settings into the JavaScript code be enough? If the functionality for passing settings already exists, I'd be super happy if you could point me to it.

Including debug messages I added, I get the following output messages upon M-x copilot-diagnose:
Copilot agent started.
copilot--request args: ('initialize '(:capabilities (:workspace (:workspaceFolders t))))
copilot--async-request args: nil
copilot--async-request args: (:success-fn (lambda (_) (message Copilot OK.)) :error-fn (lambda (err) (message Copilot error: %S err)) :timeout-fn (lambda nil (message Copilot agent timeout.)))
Copilot error: (:code 1000 :message "Not authenticated: NotSignedIn")

The proxy I tried to hardcode in agent.js does not seem to be hit at all.

I suppose https://github.com/danielgross/localpilot/issues/12 may be the answer to the errors I'm facing. Even overriding the proxies, I get walled off by (as of yet) unavoidable authentification.

@janEbert This plugin is built on copilot.vim. If the local copilot works with copilot.vim but not with copilot.el, I can look into it.

I believe it to be an issue with the JavaScript until further notice. :)
Thanks!


compute_note_hash_and_nullifier errors and other note processing errors come up as warnings

Example:
WARN Could not process note because of "Error: The note being processed has 27 fields, while "compute_note_hash_and_nullifier" can only handle a maximum of 20 fields. Please consider increasing the allowed field size to accommodate all notes generated from the contract.". Discarding note...

Actual error comes from here
Gets caught as a warning in the note processor here
These should be warnings

I'm not following here. IS this not the same as #5670 or what is the real diff here?

5670 -> can we have a compile time error for max note lem
this one -> in general all errors in note processor now are shown up as warnings!


dbeaver/pro#1245 Detach result tabs

You can't detach the SQL terminal.

Do SQL Terminal still get updates when you detached tab and press Refresh?

No. The detached tab behaves like it was disposed, so the terminal is no longer listening for its updates.

Why?

For me it looks like the functionality of fetching results by SQL Terminal becomes broken after tab detaching.

I think we should detach results to the bottom placeholder, not in editors tab. Thus it should be a view, not an editor.

Views can't be dirty, and we must manually close them upon exiting the application. Not sure if it's a good trade-off.

Verified


Modified rcu script to support both SOA and FMWInfra Domain

Updated the sample rcu creation scripts to work for both FMW and SOA Infra domain.
Following modification were made to the scripts create-rcu-schema.sh/drop-rcu-schema.sh
in the directory kubernetes/samples/scripts/create-rcu-schema
No change to the script interface. Based on the image String, the script will add the extra components and variables while creating the rcu for  FMW and SOA Infra  using the following logic
======= create-rcu-schema.sh ====
[[ $fmwimage =~ .soasuite. ]] && rcuType=soa
[[ $fmwimage =~ .fmw-infr. ]] && rcuType=fmw
Starting of oracle DB Service remains same using the script start(stop)-db-service.sh
I run QUICK test on my branch to see any Regression on sample
http://wls-jenkins.us.oracle.com/job/weblogic-kubernetes-operator-javatest/2784/console
All Tests Clean

HI Vivek,
I have added a PR https://github.com/oracle/weblogic-kubernetes-operator/pull/1298
for the suggested change


Disambiguate Pod Phase from kubectl status

This PR extends https://github.com/kubernetes/website/pull/46299, which disambiguates pod "Phase" from the "Status" field that occurs in certain  kubectl commands.

Alesandra thanks! Make sure get the Eula paperwork done . Then the commit will go thru .

Alesandra thanks! Make sure get the Eula paperwork done . Then the commit will go thru .

Paperwork complete :)

Helps with #7092


 ****

Fixed in "Update" pull


Cache Tag Helper -inside Partial View-

Steps:

Cache tag helper inside of a partial view.  Pass data into the body of the cached section via Model data.  Something like...

<cache>     <span<EMAIL_ADDRESS>       @Model.Content      </cache>

Render partial view multiple times on same page, but with different content (via model)

Cached areas are all rendered the same as the very first instance of the partial renderings.

I assume this is because the cache tag helper code resolves the cache key to the same thing since it comes out of the same partial, i.e. it looks to the cache tag helper like it is actually the same content.
I can overcome this issue by creating a more complex vary-by parameter for each partial call, but I'm wondering if this is intended behavior or if it's something that you'd want to fix?

Assuming the code looks like this:
@Html.Partial("_CachePartial", content1)
@Html.Partial("_CachePartial", content2)

what would the uniquely identifying parameter be? Varying by the model wouldn't be correct in the general case.

Maybe I'm thinking about it wrong, but how is that different from something like this?
(Assuming this is in the same view)
<cache>
content 1
 </cache>

<cache>
content 2
 </cache>

Doesn't the caching engine recognize that as two different entries?

Razor generates a unique id per instance of <cache> when parsing it - so those two entries have different identifiers (which get added as keys). In your case, it's the same "instance" so they get the same id. Varying by the page path wouldn't help either since that's going to be the same.

Gotcha, so it is as I suspected - Razor resolves it as the same instance because it "physically" is the same one.
In the specific case of rendering a cached item from a partial, however, I think that re-use is implied (by convention).  Intuitively I expected the cache key generated to be different for each instance rendered by a call to @HtmlPartial.
It sounds like modifying the vary-by parameter manually for each instance rendered is probably the clearest way to more explicitly define the behavior.

Correct, you need to explicitly specify what you want to vary-by.