Retention in days seems has no effect

Problem
I have specified retention_in_days 3 parameter for out_cloudwatch_logs. Log group within Cloudwatch was created successfully and I have bunch of logs in my streams. However, logs are not expiring (I see Never Expire in log group's metadata).
Steps to replicate
  <match **>
    @type cloudwatch_logs
    @id out_cloudwatch_logs_containers
    region "#{ENV.fetch('REGION')}"
    log_group_name "/eks/#{ENV.fetch('CLUSTER_NAME')}/containers"
    log_stream_name_key stream_name
    remove_log_stream_name_key true
    auto_create_stream true
    retention_in_days 3
    <buffer>
      flush_interval 5
      chunk_limit_size 2m
      queued_chunks_limit_size 32
      retry_forever true
    </buffer>
  </match>

Expected Behavior or What you need to ask
Log Group which being created should have retention policy with expiration in 3 days.
Using Fluentd and CloudWatchLogs plugin versions

Amazon Linux 2
Within Kubernetes (inside EKS)
Docker image fluent/fluentd-kubernetes-daemonset:v1.3.3-debian-cloudwatch-1.2

Similar - checked permissions. Currently the used role has logs:* ....
Fluentd Image: v0.12-debian-cloudwatch
Received following exception in Kubernetes cluster when log groups are created with auto_create_stream true.
2019-04-08 14:33:58 +0000 [warn]: failed to set retention policy for Log group 'Kubernetes.Cluster.kube-system' with error ["/fluentd/vendor/bundle/ruby/2.3.0/gems/aws-sdk-core-3.22.1/lib/seahorse/client/plugins/raise_response_errors.rb:15:in `call'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/aws-sdk-core-3.22.1/lib/aws-sdk-core/plugins/jsonvalue_converter.rb:20:in `call'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/aws-sdk-core-3.22.1/lib/aws-sdk-core/plugins/idempotency_token.rb:17:in `call'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/aws-sdk-core-3.22.1/lib/aws-sdk-core/plugins/param_converter.rb:24:in `call'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/aws-sdk-core-3.22.1/lib/aws-sdk-core/plugins/response_paging.rb:10:in `call'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/aws-sdk-core-3.22.1/lib/seahorse/client/plugins/response_target.rb:23:in `call'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/aws-sdk-core-3.22.1/lib/seahorse/client/request.rb:70:in `send_request'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/aws-sdk-cloudwatchlogs-1.4.0/lib/aws-sdk-cloudwatchlogs/client.rb:1490:in `put_retention_policy'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/fluent-plugin-cloudwatch-logs-0.4.5/lib/fluent/plugin/out_cloudwatch_logs.rb:381:in `put_retention_policy'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/fluent-plugin-cloudwatch-logs-0.4.5/lib/fluent/plugin/out_cloudwatch_logs.rb:371:in `create_log_group'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/fluent-plugin-cloudwatch-logs-0.4.5/lib/fluent/plugin/out_cloudwatch_logs.rb:177:in `block in write'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/fluent-plugin-cloudwatch-logs-0.4.5/lib/fluent/plugin/out_cloudwatch_logs.rb:144:in `each'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/fluent-plugin-cloudwatch-logs-0.4.5/lib/fluent/plugin/out_cloudwatch_logs.rb:144:in `write'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/fluentd-0.12.43/lib/fluent/buffer.rb:354:in `write_chunk'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/fluentd-0.12.43/lib/fluent/buffer.rb:333:in `pop'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/fluentd-0.12.43/lib/fluent/output.rb:342:in `try_flush'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/fluentd-0.12.43/lib/fluent/output.rb:149:in `run'"]

Similar - checked permissions. Currently the used role has logs:* ....
Fluentd Image: v0.12-debian-cloudwatch
Received following exception in Kubernetes cluster when log groups are created with auto_create_stream true.
2019-04-08 14:33:58 +0000 [warn]: failed to set retention policy for Log group 'Kubernetes.Cluster.kube-system' with error ["/fluentd/vendor/bundle/ruby/2.3.0/gems/aws-sdk-core-3.22.1/lib/seahorse/client/plugins/raise_response_errors.rb:15:in `call'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/aws-sdk-core-3.22.1/lib/aws-sdk-core/plugins/jsonvalue_converter.rb:20:in `call'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/aws-sdk-core-3.22.1/lib/aws-sdk-core/plugins/idempotency_token.rb:17:in `call'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/aws-sdk-core-3.22.1/lib/aws-sdk-core/plugins/param_converter.rb:24:in `call'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/aws-sdk-core-3.22.1/lib/aws-sdk-core/plugins/response_paging.rb:10:in `call'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/aws-sdk-core-3.22.1/lib/seahorse/client/plugins/response_target.rb:23:in `call'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/aws-sdk-core-3.22.1/lib/seahorse/client/request.rb:70:in `send_request'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/aws-sdk-cloudwatchlogs-1.4.0/lib/aws-sdk-cloudwatchlogs/client.rb:1490:in `put_retention_policy'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/fluent-plugin-cloudwatch-logs-0.4.5/lib/fluent/plugin/out_cloudwatch_logs.rb:381:in `put_retention_policy'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/fluent-plugin-cloudwatch-logs-0.4.5/lib/fluent/plugin/out_cloudwatch_logs.rb:371:in `create_log_group'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/fluent-plugin-cloudwatch-logs-0.4.5/lib/fluent/plugin/out_cloudwatch_logs.rb:177:in `block in write'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/fluent-plugin-cloudwatch-logs-0.4.5/lib/fluent/plugin/out_cloudwatch_logs.rb:144:in `each'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/fluent-plugin-cloudwatch-logs-0.4.5/lib/fluent/plugin/out_cloudwatch_logs.rb:144:in `write'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/fluentd-0.12.43/lib/fluent/buffer.rb:354:in `write_chunk'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/fluentd-0.12.43/lib/fluent/buffer.rb:333:in `pop'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/fluentd-0.12.43/lib/fluent/output.rb:342:in `try_flush'", "/fluentd/vendor/bundle/ruby/2.3.0/gems/fluentd-0.12.43/lib/fluent/output.rb:149:in `run'"]

If someone else every has this exception: allowed retention values....
--retention-in-days (integer)
The  number  of  days  to retain the log events in the specified log
group. Possible values are: 1, 3, 5, 7, 14, 30, 60,  90,  120,  150,
180, 365, 400, 545, 731, 1827, and 3653.

Seems it works now. I forgot to add logs:PutRetentionPolicy for my log group. I suppose that was an issue.
Tested with values 3 and 7 for retention_in_days parameter

not sure if it's related to this issue. I tried to install Fluentd as daemon set in my EKS cluster following this tutorial Set Up FluentD as a DaemonSet to Send Logs to CloudWatch Logs
You can find used fluend config via this link
It doesn't have retention_in_days field, so I added it myself.
But retention value works only upon creation, if I update config, it doesn't change retention policy for existing log group

I tried to install Fluentd as daemon set in my EKS cluster following this tutorial Set Up FluentD as a DaemonSet to Send Logs to CloudWatch Logs
You can find used fluend config via this link
It doesn't have retention_in_days field, so I added it myself.
But retention value works only upon creation. If I update config, it doesn't change retention policy for existing log group

Can you confirm this is working for you please ?

@tontondematt  I will check tonight and let you know. Previously made workaround creating log group and their retention period explicitly

@tontondematt did the update ever work for you.


Width option not working correctl

When i give my svg a width this happens:

my code:
saveSvgAsPng(document.getElementById(svgId), "Proefdruk.png", {width: '800px'});
the wanted result is more like this, but then with a width of 800px:

The width option sets the width XML attribute of the SVG node, which I believe simply crops the contents of the SVG and doesn't resize/stretch it.


Analyzer not propofates the type of members inherited from Object

This issue was originally filed by<EMAIL_ADDRESS>
=========
dynamic object; // At least it an "Object"
var string = object.toString();
=========
The "toString()" inherited from "Object" but "String" type does not propogated.
Even "bottom" type inherited from "Object".
=========
var bottom = null;
// Unnecessary type check, the result is always true
print(null is Object);
=========
This means that "toString()", which are always "Object.toString()", at least has upper bound type "String" on every type, include "dynamic".
But analyzer not take this into account.

I think this works today. DartPad seems happy anyways. It knows that toString() returns a String.


Wrong code in v5.0.0 dist

It appears the dist-modules are not up-to-date w.r.t. the lib code, compare e.g.:
https://github.com/prakhar1989/react-tags/blob/v5.0.0/lib/ReactTags.js#L62
with:
https://github.com/prakhar1989/react-tags/blob/v5.0.0/dist-modules/ReactTags.js#L136
The dist still refers to item.toLowerCase() whereas the lib refers to item.text.toLowerCase()…

@gjvoosten thanks a lot for reporting this.Its fixed now https://github.com/prakhar1989/react-tags/blob/v5.0.1/dist-modules/ReactTags.js#L136

@ad1992 Thanks for fix and the quick turn-around time!


fix: force reference to be reloaded when params have changed

When upgrading Ember to 3.28, our has-many relationships are not loaded anymore.
It seems that a little bug was introduced by this commit 4c6f15d3a4af824236801c1efc74f960f5eff0aa: we can see that in the addon/mixins/model.js file, the reloadRelationship is still called with 2 arguments, but the definition of this function has been modified by removing this 2nd argument (forceReload).
With this version of the code, our code is running smoothly.

@mdehoog if you need more information I'd be happy to help!

Duplicate of https://github.com/mdehoog/ember-data-has-many-query/pull/37


when the listview is empty or cannot fill viewpager, the header automatically scrolls down.

as title. finally resolved by adding  transparent layout to listview.

how to add transparent layout to listview? addHeadView or else method？

@wilsonssss I don't understand you meaning


k8s 1.5 support

Small change happend in the k8s 1.5 release, now it returns None in case there is nothing to return and in 1.4 it was a empty array.
I did a fast ugly patch which fix this for me:
diff -ur pykube/pykube/query.py /home/vagrant/.local/lib/python2.7/site-packages/pykube/query.py
--- pykube/pykube/query.py      2016-12-13 12:03:11.924150049 +0000
+++ /home/vagrant/.local/lib/python2.7/site-packages/pykube/query.py    2016-12-13 12:03:45.035794481 +0000
@@ -105,17 +105,21 @@
         Execute the API request and return an iterator over the objects. This
         method does not use the query cache.
         """
-        for obj in self.execute().json()["items"]:
-            yield self.api_obj_class(self.api, obj)
+        if self.execute().json()["items"] is not None:
+            for obj in self.execute().json()["items"]:
+                yield self.api_obj_class(self.api, obj)

     @property
     def query_cache(self):
         if not hasattr(self, "_query_cache"):
             cache = {"objects": []}
             cache["response"] = self.execute().json()
-            for obj in cache["response"]["items"]:
-                cache["objects"].append(self.api_obj_class(self.api, obj))
-            self._query_cache = cache
+            if cache["response"]["items"] is not None:
+                for obj in cache["response"]["items"]:
+                    cache["objects"].append(self.api_obj_class(self.api, obj))
+                self._query_cache = cache
+            else:
+                self._query_cache = {"objects": {}}
         return self._query_cache

     def __len__(self):

Pls note - it's 0.13.0 diff.

Fixed in  4c44e33.


adding kind install instructions for KIC

Description
What did you change and why?
I added a section on installing Kong for Kubernetes with Kong Enterprise for KIC on kind. I feel we have make it easy for developers to deploy Kong enterprise and be able to play around so they can use and promote the platform internally.
Testing instructions
Netlify link: /kubernetes-ingress-controller/latest/deployment/kind/
Checklist

[x] Review label added
[x] PR pointed to correct branch (main for immediate publishing, or a release branch: e.g. release/gateway-3.2, release/deck-1.17)

Hey Lena,
I think all the changes are acceptable. I think I have committed most the
suggestions. Do you need anything else from me?
On Thu, May 18, 2023 at 8:04 AM lena-larionova @.***>
wrote:

@.**** requested changes on this pull request.
In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197092198
:

@@ -0,0 +1,184 @@
+---
+title: Kong for Kubernetes with Kong Enterprise
+---

+This guide walks through setting up the {{site.kic_product_name}} with Kong
+Enterprise. This architecture is described in detail in this doc.
+
+### Set up Kind cluster
+
+The first thing we need to do is create a kind cluster to deploy {{site.kic_product_name}} to:
⬇ Suggested change
-The first thing we need to do is create a kind cluster to deploy {{site.kic_product_name}} to:
+First, create a kind cluster to deploy {{site.kic_product_name}} to:

In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197093010
:

+nodes:
+- role: control-plane

kubeadmConfigPatches:

|

kind: InitConfiguration
extraPortMappings:

containerPort: 80

hostPort: 80
protocol: TCP

containerPort: 443

hostPort: 443
protocol: TCP
+EOF
+```

+We're going create our resources in the kong namespace. Create this now:
⬇ Suggested change
-We're going create our resources in the kong namespace. Create this now:
+Next, create a kong namespace for your resources:

In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197093112
:

|

kind: InitConfiguration
extraPortMappings:

containerPort: 80

hostPort: 80
protocol: TCP

containerPort: 443

hostPort: 443
protocol: TCP
+EOF
+```

+We're going create our resources in the kong namespace. Create this now:
+
+```bash
+$ kubectl create namespace kong
⬇ Suggested change
-$ kubectl create namespace kong
+kubectl create namespace kong

In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197093244
:

protocol: TCP
+EOF
+```

+We're going create our resources in the kong namespace. Create this now:
+
+bash +$ kubectl create namespace kong +
+
+### Create a Kong Enterprise License secret (optional)
+
+If you have a Kong Enterprise license, save it to disk as license.json and create a secret:
+
+```bash
+$ kubectl create secret generic kong-enterprise-license --from-file=license=./license.json -n kong
⬇ Suggested change
-$ kubectl create secret generic kong-enterprise-license --from-file=license=./license.json -n kong
+kubectl create secret generic kong-enterprise-license --from-file=license=./license.json -n kong

In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197093475
:

+```

+### Create a Kong Enterprise License secret (optional)
+
+If you have a Kong Enterprise license, save it to disk as license.json and create a secret:
+
+bash +$ kubectl create secret generic kong-enterprise-license --from-file=license=./license.json -n kong +
+
+### Set your Kong Manager password
+
+The Kong Manager UI requires authentication. {{site.kic_product_name}} uses the kong-enterprise-superuser-password
+secret to set the default value for the default kong_admin user.
+
+Run the following, replacing cloudnative with a random password of your choice and note it down.
⬇ Suggested change
-Run the following, replacing cloudnative with a random password of your choice and note it down.
+Run the following, replacing cloudnative with a random password of your choice and note it down:

In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197093557
:

+If you have a Kong Enterprise license, save it to disk as license.json and create a secret:
+
+bash +$ kubectl create secret generic kong-enterprise-license --from-file=license=./license.json -n kong +
+
+### Set your Kong Manager password
+
+The Kong Manager UI requires authentication. {{site.kic_product_name}} uses the kong-enterprise-superuser-password
+secret to set the default value for the default kong_admin user.
+
+Run the following, replacing cloudnative with a random password of your choice and note it down.
+
+```bash
+$ kubectl create secret generic kong-enterprise-superuser-password  -n kong --from-literal=password=cloudnative
⬇ Suggested change
-$ kubectl create secret generic kong-enterprise-superuser-password  -n kong --from-literal=password=cloudnative
+kubectl create secret generic kong-enterprise-superuser-password  -n kong --from-literal=password=cloudnative

In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197093693
:

+bash +$ kubectl create secret generic kong-enterprise-license --from-file=license=./license.json -n kong +

+### Set your Kong Manager password
+
+The Kong Manager UI requires authentication. {{site.kic_product_name}} uses the kong-enterprise-superuser-password
+secret to set the default value for the default kong_admin user.
+
+Run the following, replacing cloudnative with a random password of your choice and note it down.
+
+bash +$ kubectl create secret generic kong-enterprise-superuser-password  -n kong --from-literal=password=cloudnative +
+
+Once these resources have been created, we are ready to deploy {{site.kic_product_name}}.
⬇ Suggested change
-Once these resources have been created, we are ready to deploy {{site.kic_product_name}}.
+Once these resources have been created, you're ready to deploy {{site.kic_product_name}}.

In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197093815
:

+```

+### Set your Kong Manager password
+
+The Kong Manager UI requires authentication. {{site.kic_product_name}} uses the kong-enterprise-superuser-password
+secret to set the default value for the default kong_admin user.
+
+Run the following, replacing cloudnative with a random password of your choice and note it down.
+
+bash +$ kubectl create secret generic kong-enterprise-superuser-password  -n kong --from-literal=password=cloudnative +
+
+Once these resources have been created, we are ready to deploy {{site.kic_product_name}}.
+
+## Install Kong
⬇ Suggested change
-## Install Kong
+## Install {{site.base_gateway}}

In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197094598
:

+Run the following, replacing cloudnative with a random password of your choice and note it down.
+
+bash +$ kubectl create secret generic kong-enterprise-superuser-password  -n kong --from-literal=password=cloudnative +
+
+Once these resources have been created, we are ready to deploy {{site.kic_product_name}}.
+
+## Install Kong
+
+bash +kubectl apply -f https://raw.githubusercontent.com/Kong/kubernetes-ingress-controller/v{{ page.kong_version | replace: ".x", ".0" }}/deploy/single/all-in-one-postgres-enterprise.yaml +
+
+This may take a few minutes if this is the first time you're running {{ site.base_gateway }} in Docker with a database.
⬇ Suggested change
-This may take a few minutes if this is the first time you're running {{ site.base_gateway }} in Docker with a database.
+This may take a few minutes.
not sure that you need to qualify the "few minutes". It may take a few
minutes for various reasons, right?
In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197094742
:

+```

+Once these resources have been created, we are ready to deploy {{site.kic_product_name}}.
+
+## Install Kong
+
+bash +kubectl apply -f https://raw.githubusercontent.com/Kong/kubernetes-ingress-controller/v{{ page.kong_version | replace: ".x", ".0" }}/deploy/single/all-in-one-postgres-enterprise.yaml +
+
+This may take a few minutes if this is the first time you're running {{ site.base_gateway }} in Docker with a database.
+
+Once bootstrapped, you should see the {{site.kic_product_name}} running:
+
+```bash
+$ kubectl get pods -n kong
⬇ Suggested change
-$ kubectl get pods -n kong
+kubectl get pods -n kong

In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197095000
:

+NAME                            READY   STATUS      RESTARTS   AGE
+ingress-kong-548b9cff98-n44zj   2/2     Running     0          21s
+kong-migrations-pzrzz           0/1     Completed   0          4m3s
+postgres-0                      1/1     Running     0          4m3s

Please split the result out into a separate codeblock.
In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197095125
:

+This may take a few minutes if this is the first time you're running {{ site.base_gateway }} in Docker with a database.
+
+Once bootstrapped, you should see the {{site.kic_product_name}} running:
+
+bash +$ kubectl get pods -n kong +NAME                            READY   STATUS      RESTARTS   AGE +ingress-kong-548b9cff98-n44zj   2/2     Running     0          21s +kong-migrations-pzrzz           0/1     Completed   0          4m3s +postgres-0                      1/1     Running     0          4m3s +
+
+### Configure your ingress
+
+Kong's Admin API, Kong Manager UI and the proxy will all be exposed on the same port.
⬇ Suggested change
-Kong's Admin API, Kong Manager UI and the proxy will all be exposed on the same port.
+{{site.base_gateway}}'s Admin API, Kong Manager UI, and the proxy will all be exposed on the same port.

In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197095523
:

+This may take a few minutes if this is the first time you're running {{ site.base_gateway }} in Docker with a database.

+Once bootstrapped, you should see the {{site.kic_product_name}} running:
+
+bash +$ kubectl get pods -n kong +NAME                            READY   STATUS      RESTARTS   AGE +ingress-kong-548b9cff98-n44zj   2/2     Running     0          21s +kong-migrations-pzrzz           0/1     Completed   0          4m3s +postgres-0                      1/1     Running     0          4m3s +
+
+### Configure your ingress
+
+Kong's Admin API, Kong Manager UI and the proxy will all be exposed on the same port.
+We use Kong to route to the correct internal port based on the host provided.
⬇ Suggested change
-We use Kong to route to the correct internal port based on the host provided.
+Use {{site.base_gateway}} to route to the correct internal port based on the host provided.

In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197095960
:

ingressClassName: kong

rules:

host: manager.127-0-0-1.nip.io

http:

 paths:

 - path: /

   pathType: ImplementationSpecific

   backend:

     service:

       name: kong-manager

       port:

         number: 80

+" | kubectl apply -f -
+```
+
+Finally, apply the following patch to set the KONG_ADMIN_API_URI to the hostname we set in the ingress above:
⬇ Suggested change
-Finally, apply the following patch to set the KONG_ADMIN_API_URI to the hostname we set in the ingress above:
+Apply the following patch to set the KONG_ADMIN_API_URI to the hostname you set in the ingress above:

In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197096848
:

     service:

       name: kong-manager

       port:

         number: 80

+" | kubectl apply -f -
+ + +Finally, apply the following patch to set the `KONG_ADMIN_API_URI` to the hostname we set in the ingress above: + +bash
+kubectl patch deployment -n kong ingress-kong -p "{"spec": { "template" : { "spec" : {"containers":[{"name":"proxy","env": [{ "name" : "KONG_ADMIN_API_URI", "value": "http://admin-api.127-0-0-1.nip.io" }]}]}}}}"
+```
+
+### Expose the proxy to your host machine
+
+We need to apply some kind specific patches to make our proxy accessible on our host machine:
⬇ Suggested change
-We need to apply some kind specific patches to make our proxy accessible on our host machine:
+Apply the following kind-specific patches to make the proxy accessible on the host machine:

In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197097249
:

+Finally, apply the following patch to set the KONG_ADMIN_API_URI to the hostname we set in the ingress above:

+bash +kubectl patch deployment -n kong ingress-kong -p "{\"spec\": { \"template\" : { \"spec\" : {\"containers\":[{\"name\":\"proxy\",\"env\": [{ \"name\" : \"KONG_ADMIN_API_URI\", \"value\": \"http://admin-api.127-0-0-1.nip.io\" }]}]}}}}" +
+
+### Expose the proxy to your host machine
+
+We need to apply some kind specific patches to make our proxy accessible on our host machine:
+
+bash +kubectl patch deployment -n kong ingress-kong -p '{"spec":{"template":{"spec":{"containers":[{"name":"proxy","ports":[{"containerPort":8000,"hostPort":80,"name":"proxy","protocol":"TCP"},{"containerPort":8443,"hostPort":443,"name":"proxy-ssl","protocol":"TCP"}]}]}}}}' +
+
+It will take a few minutes to roll out the updated deployment. Once the new
+ingress-kong pod is up and running, visit http://manager.127-0-0-1.nip.io/ and you should be able to log
⬇ Suggested change
-ingress-kong pod is up and running, visit http://manager.127-0-0-1.nip.io/ and you should be able to log
+ingress-kong pod is up and running, visit http://manager.127-0-0-1.nip.io and you should be able to log

In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197097584
:

+kubectl patch deployment -n kong ingress-kong -p "{"spec": { "template" : { "spec" : {"containers":[{"name":"proxy","env": [{ "name" : "KONG_ADMIN_API_URI", "value": "http://admin-api.127-0-0-1.nip.io" }]}]}}}}"
+```

+### Expose the proxy to your host machine
+
+We need to apply some kind specific patches to make our proxy accessible on our host machine:
+
+bash +kubectl patch deployment -n kong ingress-kong -p '{"spec":{"template":{"spec":{"containers":[{"name":"proxy","ports":[{"containerPort":8000,"hostPort":80,"name":"proxy","protocol":"TCP"},{"containerPort":8443,"hostPort":443,"name":"proxy-ssl","protocol":"TCP"}]}]}}}}' +
+
+It will take a few minutes to roll out the updated deployment. Once the new
+ingress-kong pod is up and running, visit http://manager.127-0-0-1.nip.io/ and you should be able to log
+in to the Kong Manager UI.
+
+As you follow along with other guides on how to use your newly deployed the {{site.kic_product_name}},
⬇ Suggested change
-As you follow along with other guides on how to use your newly deployed the {{site.kic_product_name}},
+As you follow along with other guides on how to use your newly deployed {{site.kic_product_name}},

In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197097872
:

+bash +kubectl patch deployment -n kong ingress-kong -p '{"spec":{"template":{"spec":{"containers":[{"name":"proxy","ports":[{"containerPort":8000,"hostPort":80,"name":"proxy","protocol":"TCP"},{"containerPort":8443,"hostPort":443,"name":"proxy-ssl","protocol":"TCP"}]}]}}}}' +
+
+It will take a few minutes to roll out the updated deployment. Once the new
+ingress-kong pod is up and running, visit http://manager.127-0-0-1.nip.io/ and you should be able to log
+in to the Kong Manager UI.
+
+As you follow along with other guides on how to use your newly deployed the {{site.kic_product_name}},
+you will be able to browse Kong Manager and see changes reflected in the UI as Kong's
+configuration changes.
+
+## Making a request through the proxy
+
+Finally, let's setup an environment variable to hold the IP address of kong-proxy service:
⬇ Suggested change
-Finally, let's setup an environment variable to hold the IP address of kong-proxy service:
+Let's set up an environment variable to hold the IP address of kong-proxy service:

In app/_src/kubernetes-ingress-controller/deployment/kind.md
https://github.com/Kong/docs.konghq.com/pull/5365#discussion_r1197098108
:

+## Making a request through the proxy

+Finally, let's setup an environment variable to hold the IP address of kong-proxy service:
+
+bash +export PROXY_IP="proxy.127-0-0-1.nip.io" +curl $PROXY_IP +
+
+Output:
+
+ +{"message":"no Route matched with those values"}% +
+
+This $PROXY_IP variable will be used in future guides. Please follow our
⬇ Suggested change
-This $PROXY_IP variable will be used in future guides. Please follow our
+This $PROXY_IP variable will be used in future guides. Follow our
—
Reply to this email directly, view it on GitHub
https://github.com/Kong/docs.konghq.com/pull/5365#pullrequestreview-1431725098,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A26ZL4PBHXIXVTOEBVFKNXTXGVDN5ANCNFSM6AAAAAAWMUHMRE
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Regards
https://konghq.com/ Rajeev Ramani (he/him)
APIs | Mesh | Microservices @ Kong http://konghq.com/
+61 431588242


Fix for Visual Studio multiprocess builds for CMake versions > 2.8

In case CMake version is greater than 2.8 (3.0.1 for example) the /MP option was not added to Visual Studio which increased building time

@alalek , thanks! How about now? Or it is better to remove this line at all?

Looks more better, thanks!
:+1:
BTW, CMake 2.6.3+ has CMAKE_VERSION variable (http://www.cmake.org/Bug/view.php?id=9017) so we can use this:
IF(CMAKE_VERSION VERSION_GREATER "2.8.6")

Thanks, replaced with a shorter version as you suggested. Hope all is good now :-)

I still get only single processor compilation here. I'm using the cmake-gui with cmake 3.6.3. If I understand http://www.cmake.org/Bug/view.php?id=9017 well, the correct fix would be:
if("${CMAKE_VERSION}" VERSION_GREATER 2.8.6)
According to the same note on that page:

The IF command supports VERSION_GREATER comparison as of 2.6.2, so use
cmake_minimum_required(VERSION 2.6.2)
to guarantee that it exists.


Problems to mount RF-based range sensor models on USV

Hi,
we have mounted several mbzirc_rf_long_range sensors on the USV and only the last one mounted works. We need this setup to relative localization of the drone wrt USV. This setup is typically used due to the size of USV.
We have checked with camera, lidar and radar sensors and have verified that more than one can be mounted and works.
Are we mounting it wrong or is it for another reason? We run:
ros2 launch mbzirc_ign spawn.launch.py name:=usv world:=coast model:=usv x:=-1462 y:=-16.5 z:=0.3 R:=0 P:=0 Y:=0 slot4:=mbzirc_rf_long_range slot5:=mbzirc_rf_long_range
If we spawn a drone, only sensor in slot5 works.
Thanks,
José Antonio Cobano

hi, we are only allowing one RF range sensor per vehicle. I've updated the Robot and Sensor API wiki page to mention this.


Add support for "well known" subdirectories in public and private user directories

Here's an idea I think could be fun and/or interesting: adopt the /.well-known/ (RFC 5785) convention for public and private keybase directories. Files stored within this standard, probably hidden, top-level directory (inside a kbfs folder) would have certain standard formats and provide additional functionality for users, effectively overlaying social networking capabilities on top of kbfs.
blog
This could be as simple as a directory containing a collection of Jekyll-style Markdown files with YAML front matter containing metadata, or just an Atom XML file. E.g.
/keybase/public/crimeminister/.kbfs/blog/1970-01-01-hello-world.md

microblog
Something similar to the above but with additional constraints on content length, etc. trsst is interesting here.
cv
A JSON-based format for describing CVs could do the trick here. Other XML-based formats like XMLRésumé are also of interest.
vlog
An Atom feed coupled with video files, perhaps?
With these kinds of documents stored in a kbfs folder, it would then be interesting to enable their display as part of the keybase user profile, e.g.

https://keybase.io/crimeminister/blog
https://keybase.io/crimeminister/microblog
https://keybase.io/crimeminister/cv
etc.

Keybase already naturally provides the "follow" mechanism present in sites like Twitter, Tumblr, etc. to construct a social graph, but with the added goodness of signing and (if-desired) privacy-via-encryption.

don't forget audio. +1 for podcasts in addition to vlogs


BigNumber prototype should have util.inspect.custom for NodeJS

Currently console.log(new BigNumber(42)) outputs the following in NodeJS:
BigNumber { s: 1, e: 1, c: [ 42 ] }

Ideally it should output 42. This can be solved by setting util.inspect.custom on BigNumber.prototype. Users can patch it as follows (in TypeScript):
import { BigNumber } from 'bignumber.js';

// Set a debug print function for NodeJS
import isNode = require('detect-node');
if (isNode) {
    // Dynamically load a NodeJS specific module.
    // Typescript requires all imports to be global, so we need to use
    // `const` here and disable the tslint warning.
    // tslint:disable-next-line: no-var-requires
    const util = require('util');

    // Set a custom util.inspect function
    (BigNumber.prototype as any)[util.inspect.custom] = function(): string {
        // Return the readable string representation
        // tslint:disable-next-line: no-invalid-this
        return this.toString();
    };
}

Thanks for the information.
I won't add this to the library though as I don't want to include any require calls.

Added note to README regarding util.inspect.custom, and added custom inspect function internally for users of Node.js v10.12.0+.
Thanks for your input.


Add rlike string comparison

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Implement a Spark SQL rlike, which checks for specific fast paths in order to avoid using a regex.  These types of fast paths are currently implemented for like.
Describe the solution you'd like
Implement rlike functions, similar to the like functions.  Given the existing code this should be limited to a few functions, with the remaining generated through macros.
Describe alternatives you've considered
Additional context

FWIW there is regex rewrite logic already in DataFusion that we could crib from - https://github.com/apache/arrow-datafusion/pull/4646
Tbh I'm not sure if this is better handled at the query planner level :thinking:

@tustvold Thanks for the tip!   I'll definitely take a look.


Check for presence of a config value

I'm trying to check whether a particular value exists in git config, but I don't think its possible?
It seems that there is no specific method for checking if a key exists, and all the methods that pull out values return a Result not an Option which makes it difficult to differentiate between a key not being present or an issue when getting a value for a key.
Is this something that could be supported? Or Am I missing something obvious?
Thanks for the great library by the way!

I think this may be communicated through the error type perhaps? If you inspect the error it probably has a particular code/class for "not present" vs "failed to parse"
(note that I'm just guessing though, I haven't scrutinized libgit2 for this myself)

Closing as I think this'll probably be communicated via the error.


Could not GET 'https://jcenter.bintray.com/com/facebook/react/react-native/maven-metadata.xml'. Received status code 502 from server: Bad Gateway

Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
Please provide a clear and concise description of what the bug is. Include screenshots if needed.
Please test using the latest React Native release to make sure your issue has not already been fixed: https://reactnative.dev/docs/upgrading.html
React Native version:
Run react-native info in your terminal and copy the results here.
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

npx react-native init project
2.yarn react-native run-android

Expected Results
Describe what you expected to happen.
[Could not GET 'https://jcenter.bintray.com/com/facebook/react/react-native/maven-metadata.xml'. Received status code 502 from server: Bad Gateway]
Snack, code example, screenshot, or link to a repository:
Please provide a Snack (https://snack.expo.io/), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
You may provide a screenshot of the application if you think it is relevant to your bug report.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

i checked https://stackoverflow.com/questions/49510176/android-studio-gradle-sync-failed-could-not-head-received-status-code-5 but it not working

It seems Jcenter downloads is downs, please check https://status.bintray.com

Jcenter is shutting down. Maybe they are trying to warn us to switch. See https://github.com/react-native-community/discussions-and-proposals/issues/331

Just run with offline mode. Turn off your connection, run-android and turn it on back.

Is it another way to replace Jcenter to MavenCentral manually  since jcenter getting server error now , and since jCenter is shutting down and affect Android apps globally starting May

@arwysyah i think jCenter extended their support till 1st Feb 2022

same issue here :(

@ydv0121
Ah i see ,only Rest Api and UI will be sunsetted on May
“To clarify, the JCenter repository will keep serving packages for 12 months until February 1st 2022. Only the JCenter REST API and UI will be sunsetted on May 1st 2021.”

JCenter is up now.

it worked

you can close the issue

Just run with offline mode. Turn off your connection, run-android and turn it on back.

Excellent. Thank you :) You have saved my time.

I've just started having this issue today, I checked https://status.bintray.com and it seems jcenter and bintray have already been sunset every though the date was 1 Feb 2022. What can I do to fix this issue, besides for offline mode?

@Lexical-Luke you need to update your build.gradle
Remove or disable jcenter() and change it to mavenCentral() android/build.gradle
repositories {
mavenLocal()
//  jcenter()       // <- remove it
mavenCentral()  // <- add it
maven { url "https://plugins.gradle.org/m2/" }
maven { url "https://repo.spring.io/plugins-release/" }

}

I've tried these but I still get the same issue.

Sorry bro ,currently i didnt open my Laptop ,
But here the things
maybe you should update your React Native version, currently 0.65 already replaced jcenter()
and here some references, hope can help you:

https://github.com/react-native-community/discussions-and-proposals/issues/331
https://stackoverflow.com/questions/67418153/android-studio-gradle-please-remove-usages-of-jcenter-maven-repository-from
https://stackoverflow.com/questions/50726435/difference-among-mavencentral-jcenter-and-mavenlocal

@arwysyah, I made sure to take my time and check everything, I tried all 3 of your points independently then all together, even tried some other tricks like running $ npm ls metro-config and trying to resolve those issues, I'm still left with the same issue if not more of the same.
      > Failed to list versions for com.facebook.react:react-native.
         > Unable to load Maven meta-data from https://repo.spring.io/plugins-release/com/facebook/react/react-native/maven-metadata.xml.
            > Could not get resource 'https://repo.spring.io/plugins-release/com/facebook/react/react-native/maven-metadata.xml'.
               > Could not GET 'https://repo.spring.io/plugins-release/com/facebook/react/react-native/maven-metadata.xml'. Received status code 401 from server: Unauthorized
      > Failed to list versions for com.facebook.react:react-native.
         > Unable to load Maven meta-data from https://dl.bintray.com/google/mobile-ads-adapters-android/com/facebook/react/react-native/maven-metadata.xml.
            > Could not get resource 'https://dl.bintray.com/google/mobile-ads-adapters-android/com/facebook/react/react-native/maven-metadata.xml'.
               > Could not GET 'https://dl.bintray.com/google/mobile-ads-adapters-android/com/facebook/react/react-native/maven-metadata.xml'. Received status code 502 from server: Bad Gateway
   > Could not resolve org.webkit:android-jsc:+.
     Required by:
         project :app
      > Failed to list versions for org.webkit:android-jsc.
         > Unable to load Maven meta-data from https://repo.spring.io/plugins-release/org/webkit/android-jsc/maven-metadata.xml.
            > Could not get resource 'https://repo.spring.io/plugins-release/org/webkit/android-jsc/maven-metadata.xml'.
               > Could not GET 'https://repo.spring.io/plugins-release/org/webkit/android-jsc/maven-metadata.xml'. Received status code 401 from server: Unauthorized
      > Skipped due to earlier error
      > Failed to list versions for org.webkit:android-jsc.
         > Unable to load Maven meta-data from https://google.bintray.com/flexbox-layout/org/webkit/android-jsc/maven-metadata.xml.
            > Could not get resource 'https://google.bintray.com/flexbox-layout/org/webkit/android-jsc/maven-metadata.xml'.
               > Could not GET 'https://google.bintray.com/flexbox-layout/org/webkit/android-jsc/maven-metadata.xml'. Received status code 502 from server: Bad Gateway

@Lexical-Luke Same for me. The issue persists for 2 days already and it seems like the server is down: https://isdown.app/integrations/bintray

@Lexical-Luke its looks like you already solved the problem , and i think better for you to change your credential account

@arwysyah, Definitely not solved & that is @latusdenis's creds.

Hmm okay i see,
@Lexical-Luke @latusdenis
i found an article in OneSignal website
Its sounds reasonable   that there are some libs maybe havent changed to mavenCentral() on your project .
I havent tried on my laptop
but if you want to try it
delete your modules and reinstall
And here is the complete article :
https://www.google.co.id/amp/s/onesignal.com/blog/android-migrate-jcenter-to-maven-central/amp/

I've done that literally hundreds of times, its the first thing I do before a clean install, also ./gradlew clean.

I'm using https://github.com/wgltony/react-native-braintree-dropin-ui, so should the lib move to mavenCentral()?

@Lexical-Luke 😂😂, but how if you create a new project and trying to run it ? Is it running correctly ( react native latest version)? Sometimes its possible to get and error because of gradle because of network connection when sync the gradle , but for your case i think its not . 🤔
@Lexical-Luke i think the libs already implemented mavenCentral () too . But i  never used that lib, so really sorry for that.

@arwysyah, our dev team has other apps, this is the only one affected, the others are on RN 0.64.0, this one that is having issues was on RN 0.63.4, I've since upgraded it to 0.65.0

@Lexical-Luke i just tried to look into detail your problem ,flexbox-layout releases appear to only be published to jcenter and are not present on maven central.
Remove
maven {
url "https://google.bintray.com/flexbox-layout"
}// remove this one if exist
Try  this :
dependencies {
implementation 'com.google.android.flexbox:flexbox:3.0.0'
} //add this one
For detail information:
https://github.com/google/flexbox-layout/issues/566#issuecomment-844630491
@latusdenis i dont know if you already solved the problem or not, i guess you issue also because
https://cardinalcommerceprod.jfrog.io/ ,
i found this article https://cardinaldocs.atlassian.net/wiki/spaces/CMSDK/pages/1998914459/Setting+up+CardinalMobileSDK+-+Android+-+V+2.2.5
Idont know it would help you or not, i cause i never used the lib and sdk
if bug still appear :maybe we can open the issue

@Lexical-Luke How if you change your internet connection, sometimes its also possible to happened because of your network connection didnt have a proxy 🤔

@arwysyah, unfortunately, I don't have a VPN to try out some net config, I tried connecting through my phone's wifi, and still no luck, my colleague has the same issue and we both work from home (different networks).
Here is my current build.gradle, I am currently using kotlinVersion = "1.4.32", I'm not sure if additional steps are required.
buildscript {
    ext {
        buildToolsVersion = "31.0.0"
        minSdkVersion = 21
		kotlinVersion = "1.4.32"
        supportLibVersion = "30.0.0"
	    supportVersion = "30.0.0"
        compileSdkVersion = 31
        targetSdkVersion = 31
        ndkVersion = "21.4.7075529"
        RNNKotlinVersion = kotlinVersion
    }
    repositories {
        google()
        mavenCentral()
        mavenLocal()
        // jcenter()
    }
    dependencies {
        classpath ("com.android.tools.build:gradle:4.1.2")
        classpath 'com.google.gms:google-services:4.3.3'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlinVersion"

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    repositories {
        mavenCentral()
        mavenLocal()
        // jcenter()

        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url("$rootDir/../node_modules/react-native/android")
        }
        maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }
        mavenCentral {
            // We don't want to fetch react-native from Maven Central as there are
            // older versions over there.
            content {
                excludeGroup "com.facebook.react"
            }
        }
        google()
        maven {
            // react-native-date-picker
            url "https://jitpack.io"
        }
        maven { url "https://maven.google.com" }
    }
}

Have you tried this one :
There is no flexbox on Maven Central. There is a flexbox on Google's Maven repo, but only 3.0.0. Some transitive dependency of yours is seeking 2.0.1. And, based on that dependency list, it must be io.kommunicate.sdk:kommunicateui:2.1.8 that is looking for the older flexbox.
Unfortunately, the developers of io.kommunicate.sdk:kommunicateui have not updated their library, apparently.
You can try manually adding your own dependency on com.google.android.flexbox:flexbox:3.0.0 and perhaps setting up an exclude rule on the io.kommunicate.sdk:kommunicateui:2.1.8 dependency to tell Gradle to ignore its transitive dependency on flexbox. Ideally, the developers of io.kommunicate.sdk:kommunicateui would update their library to depend on com.google.android.flexbox:flexbox:3.0.0.
To exclude the failing dependency, change:
implementation 'io.kommunicate.sdk:kommunicateui:2.1.8'
to:
implementation('io.kommunicate.sdk:kommunicateui:2.1.8') {
exclude group: "com.google.android", module: "flexbox"
}
😆😆

@arwysyah, you may be on the right track we are using kommunicate and it has been a problem child in the past 🥴
We have this in the app/build.gradle:
implementation project(':react-native-kommunicate-chat')
I changed it to your suggestion and the only thing that has changed is the build time fails twice as fast 😂 - same error.

@Lexical-Luke I saw they module/libs , its looks like they havent changed the version of flexbox ,still from jcenter, i was wondering have you tried to changed from their libs that exist on your project ? I saw also on Zendesk they have a same issue before , but i dont know 😂😂,since my suggestion always failed 😂🙏🏻.
here the pict:

@arwysyah, Interesting results..
Don't worry but things not working so far, you've been hitting all the points I also thought would work, you're a king for trying 👑
build.gradle
allprojects {
    repositories {
        mavenCentral()
        mavenLocal()
        // jcenter()
        maven {url "https://kommunicate.jfrog.io/artifactory/kommunicate-android-sdk"}
        maven {url "https://google.bintray.com/flexbox-layout"}

        maven {
            // All of React Native (JS, Obj-C sources, Android binaries) is installed from npm
            url("$rootDir/../node_modules/react-native/android")
        }
        maven {
            // Android JSC is installed from npm
            url("$rootDir/../node_modules/jsc-android/dist")
        }
        mavenCentral {
            // We don't want to fetch react-native from Maven Central as there are
            // older versions over there.
            content {
                excludeGroup "com.facebook.react"
            }
        }
        google()
        maven {
            // react-native-date-picker
            url "https://jitpack.io"
        }

        maven { url "https://maven.google.com" }

    }
}

The fancy new error:
> Task :app:mergeReleaseAssets FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:mergeReleaseAssets'.
> Could not resolve all files for configuration ':app:releaseRuntimeClasspath'.
   > Could not resolve com.google.firebase:firebase-bom:29.0.0.
     Required by:
         project :app
      > Could not resolve com.google.firebase:firebase-bom:29.0.0.
         > Could not get resource 'https://google.bintray.com/flexbox-layout/com/google/firebase/firebase-bom/29.0.0/firebase-bom-29.0.0.pom'.
            > Could not HEAD 'https://google.bintray.com/flexbox-layout/com/google/firebase/firebase-bom/29.0.0/firebase-bom-29.0.0.pom'. Received status code 502 from server: Bad Gateway
   > Could not resolve com.google.firebase:firebase-bom:29.0.0.
     Required by:
         project :app > project :react-native-firebase_analytics
         project :app > project :react-native-firebase_app
         project :app > project :react-native-firebase_auth
         project :app > project :react-native-firebase_firestore
      > Could not resolve com.google.firebase:firebase-bom:29.0.0.
         > Could not get resource 'https://google.bintray.com/flexbox-layout/com/google/firebase/firebase-bom/29.0.0/firebase-bom-29.0.0.pom'.
            > Could not HEAD 'https://google.bintray.com/flexbox-layout/com/google/firebase/firebase-bom/29.0.0/firebase-bom-29.0.0.pom'. Received status code 502 from server: Bad Gateway
   > Could not resolve com.google.firebase:firebase-auth.
     Required by:
         project :app > project :react-native-firebase_auth
      > Skipped due to earlier error
      > Skipped due to earlier error
   > Could not resolve com.google.firebase:firebase-firestore.
     Required by:
         project :app > project :react-native-firebase_firestore
      > Skipped due to earlier error
      > Skipped due to earlier error

@Lexical-Luke
did you changed the firebase version ?
How about using “com.google.gms:google-services:4.3.10” ?

@arwysyah, I'm not sure about the firebase version. I tried “com.google.gms:google-services:4.3.10”  but it didn't change the previous error.
package.json:
    "@react-native-firebase/analytics": "^12.8.0",
    "@react-native-firebase/app": "^12.8.0",
    "@react-native-firebase/auth": "^12.8.0",
    "@react-native-firebase/firestore": "^12.8.0",
    "firebase": "^7.23.0",
    "firebase-admin": "^8.12.0",

app/build.gradle:
dependencies {
    // implementation "org.webkit:android-jsc:+"
    implementation fileTree(dir: "libs", include: ["*.jar"])
    implementation platform('com.google.firebase:firebase-bom:29.0.0')
    implementation project(':react-native-gesture-handler')
    implementation project(':react-native-linear-gradient')
    // implementation project(':react-native-kommunicate-chat')
    // implementation 'io.kommunicate.sdk:kommunicateui:2.1.8'
    implementation('io.kommunicate.sdk:kommunicateui:2.1.8') {
        exclude group: "com.google.android", module: "flexbox"
    }
    implementation 'com.google.android.flexbox:flexbox:3.0.0'
    // implementation("com.github.google:flexbox-layout:2.0.1")
    implementation "com.facebook.react:react-native:+"  // From node_modules
    // implementation("com.facebook.react:react-native:0.65.0") { force = true }
    implementation 'com.google.firebase:firebase-analytics'
    implementation 'com.google.firebase:firebase-messaging:20.0.1'
    implementation 'com.google.firebase:firebase-iid:20.0.1'
    implementation project(':react-native-notifications')
    implementation 'com.google.firebase:firebase-core:16.0.0'
    implementation 'com.android.support:multidex:1.0.3'

    implementation "androidx.swiperefreshlayout:swiperefreshlayout:1.0.0"

    debugImplementation("com.facebook.flipper:flipper:${FLIPPER_VERSION}") {
        exclude group:'com.facebook.fbjni'
    }

    debugImplementation("com.facebook.flipper:flipper-network-plugin:${FLIPPER_VERSION}") {
        exclude group:'com.facebook.flipper'
        exclude group:'com.squareup.okhttp3', module:'okhttp'
    }

    debugImplementation("com.facebook.flipper:flipper-fresco-plugin:${FLIPPER_VERSION}") {
        exclude group:'com.facebook.flipper'
    }

    if (enableHermes) {
        def hermesPath = "../../node_modules/hermes-engine/android/";
        debugImplementation files(hermesPath + "hermes-debug.aar")
        releaseImplementation files(hermesPath + "hermes-release.aar")
    } else {
        implementation jscFlavor
    }
}

I think no need to remove firebase.bom version , cause this “ implementation platform('com.google.firebase:firebase-bom:29.0.0')” the correct version that exist on firebas doc ,
hmm 🤔🤔 weird , i checked the flexbox already on maven also
Here : https://maven.google.com/web/m_index.html?q=Flex#com.google.android.flexbox:flexbox:3.0.0
https://issuetracker.google.com/issues/120759347#comment106

@arwysyah, can we open up the issue again? So far I've gone full circle down that rabbit hole. I read through each of the 126 comments in issuetracker tried out a bunch of things and even tried upgrading Gradle and a few dependencies, I've not got the same issue I started with...

@Lexical-Luke yeah we can reopen this issue , and also better for you to investigate your 3rd party libs

@arwysyah, we're currently in the process, opened a ticket with kommunicate and we are checking all our packages, have to try everything to get our app to build again 😅

I am able to resolve it. Update the packages to latest version whatever package you are receiving 502.

@gopidevarapalli and this error?
> Failed to list versions for com.facebook.react:react-native.
         > Unable to load Maven meta-data from https://cardinalcommerce.bintray.com/android/com/facebook/react/react-native/maven-metadata.xml.
            > Could not get resource 'https://cardinalcommerce.bintray.com/android/com/facebook/react/react-native/maven-metadata.xml'.
               > Could not GET 'https://cardinalcommerce.bintray.com/android/com/facebook/react/react-native/maven-metadata.xml'. Received status code 502 from server: Bad Gateway

Hi Lexical,
Can you share complete error log?

Hi Lexical-Luke,
Remove maven { url('https://cardinalcommerce.bintray.com/maven') } from build.gradle and try

I am facing similar issue:

What went wrong:
Could not determine the dependencies of task ':react-native-intercom:generateReleaseRFile'.

Could not resolve all task dependencies for configuration ':react-native-intercom:releaseRuntimeClasspath'.
Could not resolve com.facebook.react:react-native:+.
Required by:
project :react-native-intercom
Failed to list versions for com.facebook.react:react-native.
Unable to load Maven meta-data from https://dl.bintray.com/intercom/intercom-maven/com/facebook/react/react-native/maven-metadata.xml.
Could not get resource 'https://dl.bintray.com/intercom/intercom-maven/com/facebook/react/react-native/maven-metadata.xml'.
Could not GET 'https://dl.bintray.com/intercom/intercom-maven/com/facebook/react/react-native/maven-metadata.xml'. Received status code 502 from server: Bad Gateway

Update on my previous issue: We were unable to fix/patch the previous issue and we decided to just start a massive cleanup, we got rid of loads of packages, even removed Intercom entirely and moved to gifted chat. Good luck.

I am facing similar issue:

What went wrong:
Could not determine the dependencies of task ':react-native-intercom:generateReleaseRFile'.

Could not resolve all task dependencies for configuration ':react-native-intercom:releaseRuntimeClasspath'.
Could not resolve com.facebook.react:react-native:+.
Required by:
project :react-native-intercom

Failed to list versions for com.facebook.react:react-native.
Unable to load Maven meta-data from https://dl.bintray.com/intercom/intercom-maven/com/facebook/react/react-native/maven-metadata.xml.
Could not get resource 'https://dl.bintray.com/intercom/intercom-maven/com/facebook/react/react-native/maven-metadata.xml'.
Could not GET 'https://dl.bintray.com/intercom/intercom-maven/com/facebook/react/react-native/maven-metadata.xml'. Received status code 502 from server: Bad Gateway

Try to remove  maven { url('https://dl.bintray.com/maven') } from build.gradle and check

I am facing similar issue:

What went wrong:
Could not determine the dependencies of task ':react-native-intercom:generateReleaseRFile'.

Could not resolve all task dependencies for configuration ':react-native-intercom:releaseRuntimeClasspath'.
Could not resolve com.facebook.react:react-native:+.
Required by:
project :react-native-intercom

Failed to list versions for com.facebook.react:react-native.
Unable to load Maven meta-data from https://dl.bintray.com/intercom/intercom-maven/com/facebook/react/react-native/maven-metadata.xml.
Could not get resource 'https://dl.bintray.com/intercom/intercom-maven/com/facebook/react/react-native/maven-metadata.xml'.
Could not GET 'https://dl.bintray.com/intercom/intercom-maven/com/facebook/react/react-native/maven-metadata.xml'. Received status code 502 from server: Bad Gateway

Try to remove maven { url('https://dl.bintray.com/maven') } from build.gradle and check

I guess mostly your problem its because you are using intercom package
Try this :
In the build.gradle file, it uses the following dependency under repositories:
maven {
url 'https://dl.bintray.com/intercom/intercom-maven'
}

UPDATE HERE!!
Yes, it worked.
As below code was in node_modules, i can't delete that directly. After checking library(https://github.com/tinycreative/react-native-intercom) for updates, it was recently fixed. Code was removed in upgraded version.
Code that was causing issue:
maven {
url 'https://dl.bintray.com/intercom/intercom-maven'
}

Yeah so, i think the problem are not about react native core, so checking the libs  that you are using inside your React Native App. Since also react native contributor keep updating and improving react native for better performance and experience.
note : currently  you can using JSI and bridge C/C++ for better performance maybe its a bit hard for now but later it will easier since JSI havent completed yet currently


python312Packages.sparsezoo: init at 1.8.1

Description of changes
Add python312Packages.sparsezoo, a neural network model repository.

python311Packages.py-machineid: init at 0.6.0
python311Packages.sparsezoo: init at 1.8.1

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 337214 run on aarch64-darwin 1

8 packages built:

python311Packages.py-machineid
python311Packages.py-machineid.dist
python311Packages.sparsezoo
python311Packages.sparsezoo.dist
python312Packages.py-machineid
python312Packages.py-machineid.dist
python312Packages.sparsezoo
python312Packages.sparsezoo.dist

Result of nixpkgs-review pr 337214 run on x86_64-darwin 1

8 packages built:

python311Packages.py-machineid
python311Packages.py-machineid.dist
python311Packages.sparsezoo
python311Packages.sparsezoo.dist
python312Packages.py-machineid
python312Packages.py-machineid.dist
python312Packages.sparsezoo
python312Packages.sparsezoo.dist

Result of nixpkgs-review pr 337214 run on x86_64-linux 1

8 packages built:

python311Packages.py-machineid
python311Packages.py-machineid.dist
python311Packages.sparsezoo
python311Packages.sparsezoo.dist
python312Packages.py-machineid
python312Packages.py-machineid.dist
python312Packages.sparsezoo
python312Packages.sparsezoo.dist

Result of nixpkgs-review pr 337214 run on aarch64-linux 1

8 packages built:

python311Packages.py-machineid
python311Packages.py-machineid.dist
python311Packages.sparsezoo
python311Packages.sparsezoo.dist
python312Packages.py-machineid
python312Packages.py-machineid.dist
python312Packages.sparsezoo
python312Packages.sparsezoo.dist

result of nixpkgs-lint --include-unfinished-lints pkgs/development/python-modules/{py-machineid,sparsezoo} 1
Advice: redundant package in nativeBuildInputs
    ╭─[pkgs/development/python-modules/sparsezoo/default.nix:44:25]
    │
 44 │   nativeBuildInputs = [ pythonRelaxDepsHook ];
    │                       ───────────┬───────────
    │                                  ╰───────────── remove this from nativeBuildInputs
    │                                  │
    │                                  ╰───────────── part of this list
────╯

result of nixpkgs-lint --include-unfinished-lints pkgs/development/python-modules/{py-machineid,sparsezoo} 1
Advice: redundant package in nativeBuildInputs
    ╭─[pkgs/development/python-modules/sparsezoo/default.nix:44:25]
    │
 44 │   nativeBuildInputs = [ pythonRelaxDepsHook ];
    │                       ───────────┬───────────
    │                                  ╰───────────── remove this from nativeBuildInputs
    │                                  │
    │                                  ╰───────────── part of this list
────╯

Oh right, I forgot about this.

LGTM

Thank you for the review !


fix typo and add pictures

typo:

add pictures:
Cyton's download pictures https://docs.citahub.com/en-US/toolchain/cyton/cyton-intro

I remembered I added the pictures in my PR, why was it removed？:thinking_face:

#88


Updates to VSCode are making my IBM i connections disappear

👉🏻 Whenever VSCode does an update the IBM i connections disappear
I setup my IBM i connections, filters, library list, etc. and everything works fine.
Then after a few days, I see this popup when starting VSCode:

Then when VSCode opens my connections are gone:

Please can you investigate.
Thanks,
Andrew

Context
Version

Code for IBM i version
2.8.0

Visual Studio Code version
1.87.0

Operating System
win32_x64

Active extensions
COBOL (cobol): 10.3.25
Code for IBM i Walkthroughs (vscode-ibmi-walkthroughs): 0.4.0
Db2 for IBM i (vscode-db2i): 0.10.0
Emmet (emmet): 1.0.0
Error Lens (errorlens): 3.16.0
Git (git): 1.0.0
Git Base (git-base): 1.0.0
GitHub (github): 0.0.1
IBM i Notebooks (vscode-ibmi-notebooks): 0.0.5
Merge Conflict (merge-conflict): 1.0.0
Node Debug Auto-attach (debug-auto-launch): 1.0.0
TODO Highlight (vscode-todo-highlight): 1.0.5
anycode (anycode): 0.0.73

Not connected 🔌

@amurphy-lp Did all your VS Code setting get changed as well? I already looked into this and I think it's a VS Code issue and not Code for IBM i.

@worksofliam How can I check this?
The 'Thunder Client' extension did not lose it's settings, but 'SSH FS' does.

Just checked the properties of the settings.json file and even though I created IBM i connections a few days ago, it shows the Date modified as:
10 March 2024, 21:54:06

Possible dupe of #1952

Hmmm, I am not sure as I still have the Code for IBM i icon on the left, it is just my connections are gone due to settings/json being replaced.

This appears to be due to a missing file from the installation. After removing and reinstalling a couple of times, it seems to be functioning correctly now.

The issue has not occurred since the reinstallation, so I am closing the ticket.


fix issue with JNI libraries for sbt 0.13, refs #36

Hi,
I had the same issue described in #36, since 0.13 sbt does forking a bit different, see
https://github.com/sbt/sbt/blob/473fc8476d25ef3fcbfe6b91b7ee57f1099bdf72/main/src/main/scala/sbt/Defaults.scala#L453
https://github.com/sbt/sbt/blob/9c442d3aed53bdc89db1ada9d5b204bf02adb339/run/src/main/scala/sbt/Run.scala#L26
You can verify this fix by launching any akka-persistence application with native leveldb journal.
Thanks,
Gleb

This works for me. I have had same problem with reactive-mongo and sbt-resolver as in #36 and those changes resolved it. Thanks @kanterov!

Same here, have been using the fork of sbt-revolver by @kanterov for a couple of weeks now to get it working.

Would you please merge this, it seems it will solve some problems


chore: fix spark_install version

Related Issues/PRs

#xxx
What changes are proposed in this pull request?
Briefly describe the changes included in this Pull Request.
How is this patch tested?

[ ] I have written tests (not required for typo or doc fix) and confirmed the proposed feature/bug-fix/change works.

Does this PR change any dependencies?

[ ] No. You can skip this section.
[ ] Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

[ ] No. You can skip this section.
[ ] Yes. Make sure you have added samples following below steps.

Find the corresponding markdown file for your new feature in website/docs/documentation folder.
Make sure you choose the correct class estimators/transformers and namespace.
Follow the pattern in markdown file and add another section for your new API, including pyspark, scala (and .NET potentially) samples.
Make sure the DocTable points to correct API link.
Navigate to website folder, and run yarn run start to make sure the website renders correctly.
Don't forget to add <!--pytest-codeblocks:cont--> before each python code blocks to enable auto-tests for python samples.
Make sure the WebsiteSamplesTests job pass in the pipeline.

/azp run

/azp run

Codecov Report

Merging #1994 (c8e123e) into master (3bd07e9) will decrease coverage by 1.06%.
The diff coverage is n/a.

:exclamation: Current head c8e123e differs from pull request most recent head bfc067e.


Accessing an array out of bound on bms_apply_dis_scp at bms_bq769x0.c:257

Hello, thanks for making this repository open-source as it is very beneficial for renewable energy enthusiasts community.
I found some issues when trying to set SCD_THRESH and other setting bits on PROTECT1, 2, 3 registers. The firmware is able to write to those registers, but upon closer look, there is a mistake in what the firmware write to those registers.
My investigation leads to something peculiar in how SCD_THRESH is chosen over SCD_threshold_setting in bq769x0_registers.h.
In bms_apply_dis_scp() at bms_bq769x0.c:
    for (int i = sizeof(SCD_threshold_setting)-1; i > 0; i--) {
        if (conf->dis_sc_limit * conf->shunt_res_mOhm >= SCD_threshold_setting[i]) {
            protect1.bits.SCD_THRESH = i;
            break;
        }
    }

In above snippet, sizeof(SCD_threshold_setting) is expected to give the array length. But in reality, sizeof() returns the array size in bytes. And because  @SCD_threshold_setting is composed of uint16_t elements, sizeof(SCD_threshold_setting) returns 2 bytes * array length.
Is this a mistake or there is actually a reason for using  sizeof(SCD_threshold_setting) instead of  sizeof(SCD_threshold_setting) / sizeof(SCD_threshold_setting[0]) ?
Of course I am not an expert in C programming as I have never taken formal education on this matter, so pardon me if I was wrong.
Reference
https://stackoverflow.com/questions/671703/array-index-out-of-bound-in-c

Oh yes, you are right. That's a mistake.
As you might have seen, I started with several updates/improvements in the code base, also to support the ISL94202 chip. The part of the code for the ISL was directly implemented together with unit tests. The older parts for BQ chips still lack unit-tests and will need a review and some more testing. Thanks for finding this bug already :)

Okay, no problem. If that's the case, I will submit pull request regarding this matter.
While reviewing the code, I also have some inquiry about how this firmware decides when to apply balancing. But I think it's better to open another thread for this.

Ok, cool.
And yes, please open another issue for the other topic.

Found this error in multiple locations and fixed all of them now.


Cannot use solution name for projects argument in DotNetCoreCLI@2 publish task

Type: Bug
Task: DotNetCoreCLI@2
Command: publish
Environment
Azure Pipelines, hosted agent
Issue Description
When executing publish command it's not possible to provide solution name as projects.
Why solution name works fine for restore and build but not for publish? I tried to find anything about it in docs but with no avail.
In my scenario I have multiple projects organized in several solutions. So in some pipeline I want to build and publish only projects within a specific solution. And it works with building but not with publishing. I tried to use **/*.csproj for projects param but of course it results in error because not all projects have been built in the build task.
I guess I can try to list all needed projects explicitly but that is just horrible.
My build and publish task definitions:
- task: DotNetCoreCLI@2
  displayName: 'Build projects'
  inputs:
    command: 'build'
    vstsFeed: $(nugetFeed)
    projects: $(solution)
    arguments: '--configuration $(buildConfiguration) --no-restore'

- task: DotNetCoreCLI@2
  displayName: 'Publish and zip'
  inputs:
    command: 'publish'
    #projects: $(solution)
    projects: '**/*.csproj'
    publishWebProjects: false
    arguments: '--no-build --configuration $(buildConfiguration) --output $(Build.ArtifactStagingDirectory)'
    zipAfterPublish: true

Task logs
log1.txt
Error logs
When trying to use solution name:
Command: C:\Program Files\dotnet\dotnet.exe" publish D:\a\1\s\HomeSafe.CI-CD.sln --no-build --configuration Release --output D:\a\1\a\s
Error: ##[error]Dotnet command failed with non-zero exit code on the following projects : [ 'D:\\a\\1\\s\\HomeSafe.CI-CD.sln' ]
When trying to use  **/*.csproj:
Command: C:\Program Files\dotnet\dotnet.exe" publish D:\a\1\s\InitNotResponseFunction.Tests\InitNotResponseFunction.Tests.csproj --no-build --configuration Release --output D:\a\1\a\InitNotResponseFunction.Tests(InitNotResponseFunction.Tests exists in repo but is not included in target solution)
Error: ##[error]Unhandled: ENOENT: no such file or directory, scandir 'D:\a\1\a\InitNotResponseFunction.Tests'

It got it working like this, It seems like there is an issue with the zipAfterPublish 👍
- task: UseDotNet@2
  inputs:
    packageType: 'sdk'
    version: '7.x'

....
....
....

- task: DotNetCoreCLI@2
  name: 'Publish'
  displayName: 'Publish'
  inputs:
    command: 'publish'
    publishWebProjects: false
    projects: '$(solution)'
    arguments: '--configuration $(BuildConfiguration) --property:PublishDir="$(Build.ArtifactStagingDirectory)" --no-restore --no-build'
    modifyOutputPath: false
    zipAfterPublish: false

- task: ArchiveFiles@2
  displayName: 'Zip Artifact'
  inputs:
    rootFolderOrFile: '$(Build.ArtifactStagingDirectory)'
    includeRootFolder: false
    archiveType: 'zip'
    archiveFile: '$(Build.ArtifactStagingDirectory)/trololo.zip'
    replaceExistingArchive: true

- task: PublishBuildArtifacts@1
  displayName: 'Publish Artifact'
  inputs:
    PathtoPublish: "$(Build.ArtifactStagingDirectory)"
    ArtifactName: 'drop_trololo'
    publishLocation: 'Container'

@ja0b Thank you for suggestion. But I believe your version will create a single zip archive for the whole solution, right? I believe it won't work with release pipeline which will need a zip file per project(in my scenatio it's one webapp and several functions).


Topics EE changes

Description
This PR satisfies the below-listed pointers:

Clicking on the topic should scroll down to the taxonomy
Background should be white
Change cursor to pointer for clickable elements(small circles)
Change the color of the infobox to lighter ones
Interactive Mode with user interaction updating EE

Remove connecting line, and time.

Don't show infobox on unvisited circles.

Relevant Technical Choices

Testing Instructions

Additional Information:

Screenshot/Screencast

Checklist

[x] I have thoroughly tested this code to the best of my abilities.
[x] I have reviewed the code myself before requesting a review.
~This code is covered by unit tests to verify that it works as intended.~
[ ] The QA of this PR is done by a member of the QA team (to be checked by QA).

Fixes #856

@mayan-000 Feel free to merge it after the QA is done by @milindmore22


Add arm support for josh-proxy

It would be nice to run it on a Mac M1/M2 without using emulation.

Hi @hgezim,
I am developing and running josh-proxy on M1 and M2 without regularly without issues, so I'm wondering what exactly you are reporting here 🤔
Are you asking for an ARM docker image? True we don't have that, but it can easily be built.

True we don't have that, but it can easily be built.

Hi, I'm struggling to build it on M1. Do you have advice on what commands to use? Here's what I've tried:
docker build git@github.com:josh-project/josh.git#master

Which results in the error:
ERROR: failed to solve: git: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed

Any help would be appreciated :)

I've also tried the command from Getting Started (https://josh-project.github.io/josh/guide/gettingstarted.html):
docker run \
--name josh-proxy \
--detach \
--publish 8000:8000 \
--env JOSH_REMOTE=https://github.com \
--volume josh-vol:/data/git \
joshproject/josh-proxy:latest >/dev/null

Which results in:
Unable to find image 'joshproject/josh-proxy:latest' locally
latest: Pulling from joshproject/josh-proxy
docker: no matching manifest for linux/arm64/v8 in the manifest list entries.
See 'docker run --help'.


Wiki Demo App Missing Argument

Scale method has named parameter and hasn't declared on what type of argument does pressed ? 0.95 : 1.0 would be.
Line 231
.scale(pressed ? 0.95 : 1.0, animate: true)

.scale(all: pressed ? 0.95 : 1.0, animate: true)

The wiki is free for anyone to edit :)


Change exisiting effect

Hi,
so i am using esp32 to light up 5 different leds in a JLed array.
i am using random function to initialize the delay to breathe function of these leds when they are declared.
Now what i want is to again change the breathing times of these leds in the void loop(). Any way to that.
Q. Is there any way i can change the running breathe effect during runtime to again call random and change its duration.
Note: Kindly also show a code that shows how to change a running effect in the FAQ.
#include <jled.h>
#define led1 27
#define led2 26
#define led3 25
#define led4 33
#define led5 32
#define freq  5000
#define ledChannel  0
#define resolution  8
int rnum [5];
int ledno[] = {led1,led2,led3,led4,led5};
JLed leds[] = {
  JLed(ledno[0]).Breathe(rnum[0]=random(2000,8000)).DelayAfter(1000).Forever(),
  JLed(ledno[1]).Breathe(rnum[1]=random(2000,8000)).DelayAfter(1000).Forever(),
  JLed(ledno[2]).Breathe(rnum[2]=random(2000,8000)).DelayAfter(1000).Forever(),
  JLed(ledno[3]).Breathe(rnum[3]=random(2000,8000)).DelayAfter(1000).Forever(),
  JLed(ledno[4]).Breathe(rnum[4]=random(2000,8000)).DelayAfter(1000).Forever()
  };
  JLedSequence sequence(JLedSequence::eMode::PARALLEL, leds);

void setup() {
  // put your setup code here, to run once:
 Serial.begin(115200);
}

void loop() {
sequence.Update();
}

Edit: Made the code easier to understand.

Hi, you could try to change the JLed effects in the leds[] with something like:
void loop() {
  if (some_somecondition) {
    leds[0].Breathe(1000);
    leds[1].FadeOn(2000);
   // etc.
  }
sequence.Update();
}

in the example you have given, can breathe have random(2000,8000) as it's parameters?.
Since i want the duration of breathe to change after previous breathe effect has finished.
To make it easier for you:

Assume that for the first led, random assigned a value of 3000 to breathe.
In the void loop, i again want random to assign another value, when the previous breathe effect (the one in point 1) had finished.
And so the process of randomly assigned values to breathe continues.

Essentially what i want is that:

The led breathes at a different rate every time the object is updated.
Minimum code is required. Hence, i am avoiding sequential commands. Which i would have to give to every led separately.
Extra Bit (You can ignore it if you want) : Even if i did do that, there would still be a sequence of breaths (lets say 2 short breath and 1 long breath) and thus not random.

Oh and kindly increase documentation:

Like showing how to change a running effect at run-time. By that i mean in void loop().
Demonstrate the working of state and misc  functions through an example code.

And by the way, this library is a life-saver, i am currently making automatic stairs lights, which will illuminate the step on which the person is standing, there will also be a music mode where the led's will act as a vu meter.


[Event Change Request] codeunit 5944 SignServContractDoc procedure SetInvoicing() event OnBeforeSetInvoicing

Please can you include the following parameters to the OnBeforeSetInvoicing event...
HideDialog
InvoiceNow
InvoiceFrom
InvoiceTo
InvoicingStartingPeriod
GoOut

The event publisher would be...
[IntegrationEvent(false, false)]
local procedure OnBeforeSetInvoicing(var ServiceContractHeader: Record "Service Contract Header"; var IsHandled: Boolean; HideDialog: Boolean; var InvoiceNow: Boolean; var InvoiceFrom: Date; var InvoiceTo: Date; var InvoicingStartingPeriod: Boolean; var GoOut: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 10907.


Fixes false positives in Link isActive checks

This is intended to fix https://github.com/rackt/react-router/issues/1441.
It's possible that you have better ideas in mind for solving this, so feel free to disregard this PR if that's the case.
I pulled the path matching code into URLUtils so that they're easier to test. Maybe it's possible to re-use some of the existing pattern matching, but I didn't see an easy way.

Doesn't seem to work. Needs to take route hierarchy into account.

@gonsfx Can you elaborate? Do you have a test case that it doesn't pass?

@gonsfx Oh I see what you mean. Rather than match based on the URL, match on the route component hierarchy.

A typical example i cross-posted into other issues would be
<Router history={new BrowserHistory}>
  <Route component={App}>
    <Route path="/" component={HomePage}>
      <Route path="nested" component={NestedPage}>
        <Route path="nested" component={NestedPage} />
      </Route>
      <Route path="nest" component={NestPage} />
    </Route>
    <Route path="some" component={SomePage} />
    <Route path="other" component={OtherPage} />
  </Route>
</Router>


Fuzz: oss-fuzz integration

What problem does this PR solve?
Issue Number: none
Problem Summary:
This is a preparation for oss-fuzz integration cf https://github.com/google/oss-fuzz/pull/5702
cc @breeswish
What is changed and how it works?
What's Changed:

bump fuzzers crates versions
use another option build to fuzz utility (to build and not run a target)

Check List
Tests

Integration test

Well, this is adding more integrations tests...
Release note

No release note

/cc @breeswish

Just did the sign-off

Friendly ping @overvenus what do I need to do now ?

Should I do something or close this ?

I can do a rebase if there is interest in this...

Closing as stale cc @breezewish
would you still want it ?


[BUG] Console.out() always enables highlighting by default

Console.out() by default enables highlighting even if it is disabled in the Console constructor.
from rich.console import Console
console = Console(highlight=False)
console.print('cd /usr/lib')  # no hightlight
console.out('cd /usr/lib')  # hightlight

It is expected that Console.out() makes less changes to the output than Console.print().
It happens because the default value of hightlight is True in Console.out() and None in Console.print(). The fix is making it None.
rich 9.3.0

Fixed in 9.5.0


Since HACS v0.13.0b0 I have a problem with the integration "Sensor.Geoip".

Since HACS v0.13.0b0 I have a problem with the integration "Sensor.Geoip". If I remove them with "uninstall", then the folder "None" under "custom_components" will be removed, but after a reboot the integration appears again in the overview with the status "Orange".
Originally posted by @bussio in https://github.com/custom-components/hacs/issues/377#issuecomment-518585402

https://github.com/custom-components/hacs/issues/377#issuecomment-518755507

@ludeeus I meant the folder, which is mentioned here in the description of the integration under HACS.
"When installed, this will be located in '/ config / custom_components / None', you still need to add it to your 'configuration.yaml' file."

@bussio sensor.geoip should not exsist in HACS.
the repository is not compliant.
Will fix that so it's removed in the next beta

https://github.com/custom-components/hacs/commit/a6eb1891d038a98f940bd5440edcaba370b4c2cf Fixed by blacklisting.
Check readded to the integration logic https://github.com/custom-components/hacs/commit/342a2c388338f636ab14f8b58fe52db01bec21ad


beforeTest() / afterTest() not run between test invocations

I'm unable to tell from the docs whether this works as designed, but I observed in kotlintest 3.3.1 that a test with invocations > 1 does not have its beforeTest() / afterTest() called in between invocations. Which in my case makes the second invocation fail as afterTest() does some required clean-up of a temporary directory which must not exist when the test starts.
Could you please clarify what the intended behavior is / whether this is a bug, and if it's not a bug / works as intended, guide my to which is the proper way to clean-up between test invocations without duplicating too much code? In particular, would the introduction of beforeInvocation() / afterInvocation() be an option?

beforeInvocation() / afterInvocation is a great name for what I've struggled to come up with a name for in the past.
However I'm undecided if invocations should move out of the test case completely and into a helper function, which could also be used for threads, retries and timeout.
test("my test") {
  invocations(3).retry(2) {
     // some test
  }
}

The upside is that it greatly simplifies the implementation.
The downside is you can't hook into a listener.

I take your answer as a "it currently works as designed" 😉 As for how to implement a beforeInvocation() / afterInvocation(), I'm undecided and will leave that to you 😁

The downside is you can't hook into a listener.

Prehaps the code invocations(3) could delegate to a part that registers every invocation to be processed by the listeners. It could be a little bit hackish, but I think it might work

Ok in the latest snapshot I have replaced invocations with replay(k, n).
eg
      replay(times = 10, threads = 3) {
      }

And they accept listeners which are just functions.
      replay(10, 3, before = {  }, after = {  }) {

      }

I actually reverted this and added beforeInvocation / afterInvocation to TestListener.


Remove the body def from {Start,Stop}Notebook

This is to avoid the following warning:
E0527 04:45:37.104443      38 template.go:978] created a body with 0 properties in the message, this might be unintended: name:"StartNotebookRequest" field:{name:"id" number:1 label:LABEL_OPTIONAL type:TYPE_STRING json_name:"id"}
I believe we don't need the body since the the request has only the "id" field, which is in the path param.

Thanks! Fixed.


doc: add hugegraph server setup guide for IDEA

The Quick Start section provides instructions on how to start and stop HugeGraphServer using scripts. However, for developers, this method may not be convenient as it is not integrated with IDE tools and can be difficult to debug.
So I add a guide to explain how to run and debug HugeGraphServer on the Linux platform using IntelliJ IDEA.
I have read the CLA Document and I hereby sign the CLA

@liuxiaocs7 @Radeity @msgui could also take a look for it (Review CN doc only)


Its a leagl state, that listenerThread is null.

Its a leagl state, that listenerThread is null.
In your sequence listener.Stop() would not be called.
It would be better to just handle the listenerThread inside the if-block.
        if (listenerThread != null) {
          listenerThread.Abort();
          listenerThread = null;
        }
        listener.Stop();

Originally posted by @vanatic in https://github.com/openhardwaremonitor/openhardwaremonitor/pull/1343#discussion_r841883012
Originally posted by @0144k in https://github.com/ipinfo/cli/issues/103

Its a leagl state, that listenerThread is null.
In your sequence listener.Stop() would not be called.
It would be better to just handle the listenerThread inside the if-block.

        if (listenerThread != null) {

          listenerThread.Abort();

          listenerThread = null;

        }

        listener.Stop();

Originally posted by @vanatic in https://github.com/openhardwaremonitor/openhardwaremonitor/pull/1343#discussion_r841883012
Originally posted by @0144k in https://github.com/ipinfo/cli/issues/103


Added acyclic coloring

Allows user to color graph using acyclic coloring algorithm.
The main difference between acyclic coloring and ordinary distance-1 coloring is that in the case of acyclic coloring, on top of the regular distance-1 coloring condition, there is an added condition that all the cycles in the graph have atleast 3 colors present.
Example to illustrate the difference:

TODO:

[x] 1. clean the code
[ ] 2. add tests
[ ] 3. replace indexing of firstTreeToVisit with either edge type or find a more efficient way to identify the specific edge object instead of iterating over all edges

#29

I want to approve this PR just for the artistic drawings, but I'll restrain myself

Those renderings, A+.

@pkj-m to be ~a pain in the~ detailed-oriented, I'd advise putting all functions and variables in snake_case, not camelCase as mergeTrees and forbiddenColors

@pkj-m some few more comments, then it looks good

@ChrisRackauckas @matbesancon can we merge this now?

Good to me yes
On Mon, Aug 26, 2019, 21:44 Pankaj Mishra<EMAIL_ADDRESS>wrote:

@ChrisRackauckas https://github.com/ChrisRackauckas @matbesancon
https://github.com/matbesancon can we merge this now?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/JuliaDiffEq/SparseDiffTools.jl/pull/60?email_source=notifications&email_token=AB2FDMXC2FVUCTF3YYTVYUDQGQXAPA5CNFSM4IJ3RQTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5FOONY#issuecomment-525002551,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB2FDMWBEJ4GIJP24PNKGB3QGQXAPANCNFSM4IJ3RQTA
.


PyPi package deprecations

It would be nice if there was a way to mark a Pip package as deprecated, or simply warn about dependencies not updated for a long time.
For example Flask-BabelEx is deprecated and should be replaced with Flask-Babel.

Dupe of https://github.com/dependabot/dependabot-core/issues/3242, and unfortunately probably not something we can do for reasons outlined in https://github.com/dependabot/dependabot-core/issues/3242#issuecomment-1211592452.