Two DataTable in One Page - Second one initialising weird

I opened a stackoverflow question, but I copy the question here too.
I have two dataTable in my page and I have a method like below:
function ToDataTable()
{
    $(".dataTable").css("width", "100%");

    $(".dataTable").each(function ()
    {
        var $that = $(this);

        /* Start of method */
        function ToDataTableInternal()
        {
           var table = $that.DataTable({
               responsive: {
                   details: { type: "column", target: -1 },
               },
               columnDefs: [{
                       className: "control", orderable: !1, targets: -1,
                   },
                   { orderable: !1 }],
               "paging": false,
               "ordering": false,
               "info": false,
               "searching": false,
                retrieve: true
           });
        }
        /* End of method */

        if ($that.is(":visible"))
        {
            ToDataTableInternal()
        }
        else
        {
            // Observe all invisible parents or table to trigger
            // ToDataTableInternal method if made visible
            var $arr = $(this).parentsUntil(":visible").filter(function ()
            {
                return $(this).css("display") === "none";
            }).add($(this));

            var observers = [];

            $arr.each(function ()
            {
                var observer = new MutationObserver(function (mutations)
                {
                    mutations.forEach(function (mutation)
                    {
                        if ((mutation.attributeName === 'style' ||
                               mutation.attributeName === 'class') &&
                                 $that.is(":visible"))
                        {
                            ToDataTableInternal();

                            for (var i = 0; i < observers.length; i++)
                            {
                                // Disconnect observers
                                observers[i].disconnect();
                            }
                        }
                    });
                });

                observers.push(observer);
                observer.observe(this, {
                    attributes: true
                });
            });
        }
    });
}

The reason I have this method is that when table's display is none, it really lags browser(especially IE, where I cannot do anything for minimum of 5 seconds) which is the reason of that I'm changing the table to DataTable after it made visible.
But the problem with calling methods individually is the second DataTable doesn't have the same settings which I passed on. Instead, second one has filters, paging, sort elements in it too.
 What may be the problem?
After some look throughs,
It actually changes both of them to dataTable at the same time, but how? it isn't possible from the way I do things. but the problem I explained still happens.
I think the problem is that I have "dataTable" class in my table element, so it behaves this way,

My apologies if the New Issue template text and Contributing document are not clear enough. Please ask support questions in the DataTables forums with a link to a test case showing the issue so I can help to debug the problem.


Constant etcd alerts about 503 on http probe

We're constantly receiving 503 from etcd alerts in our slack channel, like so:

Sometimes multiple per hour, sometimes once a day.
This happens with our HA rancher server, and with main cluster. Both built with RKE.
Otherwise network connectivity is fine and it seems there is no packet loss.
May it be that this normal and just alert is too sensitive? How can we investigate this further?

Useful
Info

Versions
Rancher v2.0.4 UI: v2.0.53

Access
local admin

Route
global-admin.clusters.index

@aiwantaozi Everything working fine and we do not see any effects of this error on cluster workings, and it seems this is a very intermittent error, no way to catch componentstatus when it happens. Right now componentstatus is all good:
 kubectl get componentstatus
NAME                 STATUS    MESSAGE              ERROR
controller-manager   Healthy   ok
scheduler            Healthy   ok
etcd-0               Healthy   {"health": "true"}
etcd-2               Healthy   {"health": "true"}
etcd-1               Healthy   {"health": "true"}

etcd's and controlplane running on same hosts. These hosts are dedicated to them.

Ok, let me jump here ;-)
I have similar issues for the last 2 months. I'm running 3 etcd/scheduler + 2 dedicated etcd in the cluster with (2GB RAM, 1CPU). It did happen even on the empty cluster. CPU is around 10-20% max, 50% mem.
My cluster is split between 2 DC (2ms ping between them), I'e bumped etcd config a bit:
services:
  etcd:
    extra_args:
      election-timeout: "5000"
      heartbeat-interval: "500"

I believe this issue is happening, when etcd is doing snapshots. When it did happened again on dedicated etcd node, I quickly jumped on that node and get docker logs for etcd container:
2018-08-15 05:14:15.606840 I | etcdmain: etcd Version: 3.2.18
2018-08-15 05:14:15.606895 I | etcdmain: Git SHA: eddf599c6
2018-08-15 05:14:15.606899 I | etcdmain: Go Version: go1.8.7
2018-08-15 05:14:15.606902 I | etcdmain: Go OS/Arch: linux/amd64
2018-08-15 05:14:15.606906 I | etcdmain: setting maximum number of CPUs to 1, total number of available CPUs is 1
2018-08-15 05:14:15.606952 N | etcdmain: the server is already initialized as member before, starting as etcd member...
2018-08-15 05:14:15.606966 I | embed: peerTLS: cert = /etc/kubernetes/ssl/kube-etcd-THAT_NODE_IP.pem, key = /etc/kubernetes/ssl/kube-etcd-THAT_NODE_IP-key.pem, ca = , trusted-ca = /etc/kubernetes/ssl/kube-ca.pem, client-cert-auth = true
2018-08-15 05:14:15.607511 I | embed: listening for peers on https://<IP_ADDRESS>:2380
2018-08-15 05:14:15.607552 I | embed: listening for client requests on <IP_ADDRESS>:2379
2018-08-15 05:14:15.634240 I | etcdserver: recovered store from snapshot at index 100001
2018-08-15 05:14:15.635710 I | mvcc: restore compact to 105102
2018-08-15 05:14:15.819725 I | etcdserver: name = etcd-nvme-2gb-nbg1-etcd1
2018-08-15 05:14:15.819893 I | etcdserver: data dir = /var/lib/rancher/etcd/
2018-08-15 05:14:15.819938 I | etcdserver: member dir = /var/lib/rancher/etcd/member
2018-08-15 05:14:15.819994 I | etcdserver: heartbeat = 500ms
2018-08-15 05:14:15.820029 I | etcdserver: election = 5000ms
2018-08-15 05:14:15.820081 I | etcdserver: snapshot count = 100000
2018-08-15 05:14:15.820149 I | etcdserver: advertise client URLs = https://<IP_ADDRESS>:2379,https://THAT_NODE_IP:4001
2018-08-15 05:14:16.290902 I | etcdserver: restarting member 6b2dbc3be73fd6b3 in cluster 68a20fe25dffa9cd at commit index 141337
2018-08-15 05:14:16.293393 I | raft: 6b2dbc3be73fd6b3 became follower at term 4
2018-08-15 05:14:16.293416 I | raft: newRaft 6b2dbc3be73fd6b3 [peers: [6b2dbc3be73fd6b3,728a67faea27a45d,a7d57947478fb750,f2de2d6dfd577a58], term: 4, commit: 141337, applied: 100001, lastindex: 141338, lastterm: 4]
2018-08-15 05:14:16.293529 I | etcdserver/api: enabled capabilities for version 3.2
2018-08-15 05:14:16.293538 I | etcdserver/membership: added member 728a67faea27a45d [https://OTHER_NODE:2380] to cluster 68a20fe25dffa9cd from store
2018-08-15 05:14:16.293543 I | etcdserver/membership: added member a7d57947478fb750 [https://OTHER_NODE:2380] to cluster 68a20fe25dffa9cd from store
2018-08-15 05:14:16.293547 I | etcdserver/membership: added member f2de2d6dfd577a58 [https://ANOTHER_NODE:2380] to cluster 68a20fe25dffa9cd from store
2018-08-15 05:14:16.293555 I | etcdserver/membership: added member 6b2dbc3be73fd6b3 [https://THAT_NODE_IP:2380] to cluster 68a20fe25dffa9cd from store
2018-08-15 05:14:16.293560 I | etcdserver/membership: set the cluster version to 3.2 from store
2018-08-15 05:14:16.303972 I | mvcc: restore compact to 105102
2018-08-15 05:14:16.501216 W | auth: simple token is not cryptographically signed
2018-08-15 05:14:16.504787 I | rafthttp: starting peer 728a67faea27a45d...
2018-08-15 05:14:16.504954 I | rafthttp: started HTTP pipelining with peer 728a67faea27a45d
2018-08-15 05:14:16.507145 I | rafthttp: started peer 728a67faea27a45d
2018-08-15 05:14:16.507307 I | rafthttp: added peer 728a67faea27a45d
2018-08-15 05:14:16.507395 I | rafthttp: starting peer a7d57947478fb750...
2018-08-15 05:14:16.507475 I | rafthttp: started HTTP pipelining with peer a7d57947478fb750
2018-08-15 05:14:16.521297 I | rafthttp: started streaming with peer 728a67faea27a45d (writer)
2018-08-15 05:14:16.521457 I | rafthttp: started streaming with peer 728a67faea27a45d (writer)
2018-08-15 05:14:16.521558 I | rafthttp: started streaming with peer 728a67faea27a45d (stream MsgApp v2 reader)
2018-08-15 05:14:16.521872 I | rafthttp: started streaming with peer 728a67faea27a45d (stream Message reader)
2018-08-15 05:14:16.522185 I | rafthttp: started streaming with peer a7d57947478fb750 (writer)
2018-08-15 05:14:16.522758 I | rafthttp: started peer a7d57947478fb750
2018-08-15 05:14:16.522832 I | rafthttp: added peer a7d57947478fb750
2018-08-15 05:14:16.522884 I | rafthttp: starting peer f2de2d6dfd577a58...
2018-08-15 05:14:16.522934 I | rafthttp: started HTTP pipelining with peer f2de2d6dfd577a58
2018-08-15 05:14:16.523757 I | rafthttp: started peer f2de2d6dfd577a58
2018-08-15 05:14:16.523826 I | rafthttp: added peer f2de2d6dfd577a58
2018-08-15 05:14:16.523883 I | etcdserver: starting server... [version: 3.2.18, cluster version: 3.2]
2018-08-15 05:14:16.524569 I | embed: ClientTLS: cert = /etc/kubernetes/ssl/kube-etcd-THAT_NODE_IP.pem, key = /etc/kubernetes/ssl/kube-etcd-THAT_NODE_IP-key.pem, ca = , trusted-ca = /etc/kubernetes/ssl/kube-ca.pem, client-cert-auth = true
2018-08-15 05:14:16.525438 I | rafthttp: started streaming with peer a7d57947478fb750 (writer)
2018-08-15 05:14:16.525552 I | rafthttp: started streaming with peer a7d57947478fb750 (stream MsgApp v2 reader)
2018-08-15 05:14:16.526097 I | rafthttp: started streaming with peer a7d57947478fb750 (stream Message reader)
2018-08-15 05:14:16.526319 I | rafthttp: started streaming with peer f2de2d6dfd577a58 (writer)
2018-08-15 05:14:16.526381 I | rafthttp: started streaming with peer f2de2d6dfd577a58 (writer)
2018-08-15 05:14:16.526447 I | rafthttp: started streaming with peer f2de2d6dfd577a58 (stream MsgApp v2 reader)
2018-08-15 05:14:16.526604 I | rafthttp: started streaming with peer f2de2d6dfd577a58 (stream Message reader)
2018-08-15 05:14:16.542181 I | raft: raft.node: 6b2dbc3be73fd6b3 elected leader 728a67faea27a45d at term 4
2018-08-15 05:14:16.542533 I | rafthttp: started HTTP pipelining with peer fae45edff5cba178
2018-08-15 05:14:16.542593 E | rafthttp: failed to find member fae45edff5cba178 in cluster 68a20fe25dffa9cd
2018-08-15 05:14:16.542900 I | rafthttp: peer a7d57947478fb750 became active
2018-08-15 05:14:16.542965 I | rafthttp: established a TCP streaming connection with peer a7d57947478fb750 (stream MsgApp v2 writer)
2018-08-15 05:14:16.543082 E | rafthttp: failed to find member fae45edff5cba178 in cluster 68a20fe25dffa9cd
2018-08-15 05:14:16.543270 I | rafthttp: established a TCP streaming connection with peer a7d57947478fb750 (stream Message writer)
2018-08-15 05:14:16.543499 I | rafthttp: peer f2de2d6dfd577a58 became active
2018-08-15 05:14:16.543552 I | rafthttp: established a TCP streaming connection with peer f2de2d6dfd577a58 (stream MsgApp v2 writer)
2018-08-15 05:14:16.543685 I | rafthttp: established a TCP streaming connection with peer f2de2d6dfd577a58 (stream Message writer)
2018-08-15 05:14:16.543951 I | rafthttp: peer 728a67faea27a45d became active
2018-08-15 05:14:16.544007 I | rafthttp: established a TCP streaming connection with peer 728a67faea27a45d (stream Message writer)
2018-08-15 05:14:16.544192 I | rafthttp: established a TCP streaming connection with peer 728a67faea27a45d (stream MsgApp v2 writer)
2018-08-15 05:14:16.607634 I | etcdserver: 6b2dbc3be73fd6b3 initialzed peer connection; fast-forwarding 8 ticks (election ticks 10) with 3 active peer(s)
2018-08-15 05:14:16.653527 I | rafthttp: established a TCP streaming connection with peer a7d57947478fb750 (stream MsgApp v2 reader)
2018-08-15 05:14:16.653955 I | rafthttp: established a TCP streaming connection with peer f2de2d6dfd577a58 (stream MsgApp v2 reader)
2018-08-15 05:14:16.654270 I | rafthttp: established a TCP streaming connection with peer a7d57947478fb750 (stream Message reader)
2018-08-15 05:14:16.654405 I | rafthttp: established a TCP streaming connection with peer f2de2d6dfd577a58 (stream Message reader)
2018-08-15 05:14:16.654516 I | rafthttp: established a TCP streaming connection with peer 728a67faea27a45d (stream Message reader)
2018-08-15 05:14:16.654653 I | rafthttp: established a TCP streaming connection with peer 728a67faea27a45d (stream MsgApp v2 reader)
2018-08-15 05:14:16.673170 I | etcdserver/membership: added member fae45edff5cba178 [https://<IP_ADDRESS>:2380] to cluster 68a20fe25dffa9cd
2018-08-15 05:14:16.673377 I | rafthttp: starting peer fae45edff5cba178...
2018-08-15 05:14:16.673446 I | rafthttp: started HTTP pipelining with peer fae45edff5cba178
2018-08-15 05:14:16.674115 I | rafthttp: started peer fae45edff5cba178
2018-08-15 05:14:16.674188 I | rafthttp: added peer fae45edff5cba178
2018-08-15 05:14:16.678843 I | rafthttp: started streaming with peer fae45edff5cba178 (writer)
2018-08-15 05:14:16.678995 I | rafthttp: started streaming with peer fae45edff5cba178 (writer)
2018-08-15 05:14:16.679076 I | rafthttp: started streaming with peer fae45edff5cba178 (stream MsgApp v2 reader)
2018-08-15 05:14:16.679304 I | rafthttp: started streaming with peer fae45edff5cba178 (stream Message reader)
2018-08-15 05:14:16.689793 I | etcdserver: published {Name:etcd-nvme-2gb-nbg1-etcd1 ClientURLs:[https://THAT_NODE_IP:2379 https://IP:4001]} to cluster 68a20fe25dffa9cd
2018-08-15 05:14:16.690068 I | embed: ready to serve client requests
2018-08-15 05:14:16.690311 I | embed: serving client requests on [::]:2379
2018-08-15 05:14:16.767468 I | rafthttp: peer fae45edff5cba178 became active
2018-08-15 05:14:16.767633 I | rafthttp: established a TCP streaming connection with peer fae45edff5cba178 (stream MsgApp v2 writer)
2018-08-15 05:14:16.767798 I | rafthttp: established a TCP streaming connection with peer fae45edff5cba178 (stream Message writer)
2018-08-15 05:14:16.786478 I | rafthttp: established a TCP streaming connection with peer fae45edff5cba178 (stream Message reader)
2018-08-15 05:14:16.792561 I | rafthttp: established a TCP streaming connection with peer fae45edff5cba178 (stream MsgApp v2 reader)
2018-08-15 05:14:27.002697 W | rafthttp: lost the TCP streaming connection with peer 728a67faea27a45d (stream Message reader)
2018-08-15 05:14:27.002874 E | rafthttp: failed to read 728a67faea27a45d on stream Message (unexpected EOF)
2018-08-15 05:14:27.002954 I | rafthttp: peer 728a67faea27a45d became inactive
2018-08-15 05:14:27.007408 W | rafthttp: lost the TCP streaming connection with peer 728a67faea27a45d (stream MsgApp v2 reader)
2018-08-15 05:14:29.311128 W | rafthttp: lost the TCP streaming connection with peer 728a67faea27a45d (stream Message writer)
2018-08-15 05:14:30.211504 I | rafthttp: peer 728a67faea27a45d became active
2018-08-15 05:14:30.212070 I | rafthttp: established a TCP streaming connection with peer 728a67faea27a45d (stream Message reader)
2018-08-15 05:14:30.212603 I | rafthttp: established a TCP streaming connection with peer 728a67faea27a45d (stream MsgApp v2 reader)
2018-08-15 05:14:30.344572 I | rafthttp: established a TCP streaming connection with peer 728a67faea27a45d (stream Message writer)
2018-08-15 05:14:30.345132 W | rafthttp: closed an existing TCP streaming connection with peer 728a67faea27a45d (stream MsgApp v2 writer)
2018-08-15 05:14:30.345228 I | rafthttp: established a TCP streaming connection with peer 728a67faea27a45d (stream MsgApp v2 writer)
2018-08-15 05:14:33.325099 I | raft: 6b2dbc3be73fd6b3 [term: 4] received a MsgVote message with higher term from 728a67faea27a45d [term: 5]
2018-08-15 05:14:33.325360 I | raft: 6b2dbc3be73fd6b3 became follower at term 5
2018-08-15 05:14:33.325490 I | raft: 6b2dbc3be73fd6b3 [logterm: 4, index: 141421, vote: 0] cast MsgVote for 728a67faea27a45d [logterm: 4, index: 141421] at term 5
2018-08-15 05:14:33.325620 I | raft: raft.node: 6b2dbc3be73fd6b3 lost leader 728a67faea27a45d at term 5
2018-08-15 05:14:33.332096 I | raft: raft.node: 6b2dbc3be73fd6b3 elected leader 728a67faea27a45d at term 5
2018-08-15 05:14:42.223620 W | etcdserver: timed out waiting for read index response
2018-08-15 05:14:55.444886 W | etcdserver: apply entries took too long [310.61351ms for 2 entries]
2018-08-15 05:14:55.445357 W | etcdserver: avoid queries with large range/delete range!
2018-08-15 05:15:44.463208 W | etcdserver: apply entries took too long [406.223407ms for 2 entries]
2018-08-15 05:15:44.463430 W | etcdserver: avoid queries with large range/delete range!
2018-08-15 05:19:33.272577 I | wal: segmented wal file /var/lib/rancher/etcd/member/wal/0000000000000003-0000000000022e44.wal is created

We see the same issue, also for distributed etcd cluster in several different data centers. I turned of the notifications temporarily

Etcd give some suggestion when these warnings happened and deployment hardware recommendation
https://github.com/etcd-io/etcd/blob/master/Documentation/faq.md#what-does-the-etcd-warning-apply-entries-took-too-long-mean
https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/hardware.md

@miv @aiwantaozi I believe it is ok. I am not sure if you change the default repeat interval time or not but it seems like it is set around 10 min. The time for the repeat interval we recommend is 1 hour(3 hour in alert manager's default). If it is set too short, the alerts will appear very often. So I think it is not a bug though. Feel free to reopen this issue if anything doesn't make sense to you.

I think this is a false error from rancher. I have "endpoint health" check done every second on the etcd cluster and also docker logs follow on all members.
Also I'm watching the network socket in chrome for the rancher page.
The error keeps showing up in chrome socket (and also in the interface, when I'm watching it) pretty often. It takes 4-5 seconds for the error to show up and be cleared. And in my case it's always the same etcd node:
{
            "conditions":[
               {
                  "message":"HTTP probe failed with statuscode: 503",
                  "status":"False",
                  "type":"Healthy"
               }
            ],
            "name":"etcd-0",
            "type":"/v3/schemas/clusterComponentStatus"
         },

But nothing shows on my other consoles: the health check and logs.
How can I investigate how rancher does the check?

Too bad that this is a won't-fix, this is really annoying and will lead to people just disabling the check

Reopen it as some users still hit it in 2.3.2.
In 2.0.x, 2.1.x and 2.2.x, the group_wait is 3 mins and resolve_timeout is 5 mins. As resolve_timeout is longer than group_wait, alert manager will fire the alert even when ETCD health check only returns 503 once.
group_wait for this alert has been changed to 10 mins to make the alert not that sensitive in 2.3.x.

with RANCHER v2.3.5
received email  sometimes
Alert Name: Alert for etcd
Severity: critical
Cluster Name: for-testenv (ID: local)
Logs: HTTP probe failed with statuscode: 503

We also get like 3-5 Alerts per day per cluster.
We are using Rancher 2.3.5 with Digital Ocean Managed Kubernetes.

Seeing the same on Rancher 2.3.3 - etcd alerts once an hour or so

We are getting this same issue witch Rancher version 2.3.5 on an HA server.
The cluster seems fine though.

same on 2.3.2 after "hard" removing one node. Is this going to be fixed?

Issue is still present in 2.4.17.

Issue is still present after upgrading to 2.5.9. Somewhat more often than on 2.4.17.

as stiks wrote, just use this in your RKE config to have higher timeouts:
services:
  etcd:
    extra_args:
      election-timeout: "5000"
      heartbeat-interval: "1000"

It was already set to sticks's configuration:
        election-timeout: '5000'
        heartbeat-interval: '500'

I've updated the heartbeat interval to 1000, we'll see in some days if there is any improvement.
Thanks


[rdc/spid] Waive CSb to any flops @ SPI_DEV*CLK

The current env. setup in RDC does not describe the relationship between CSb and SCK or the current description (below) is not well defined:
\# chip_earlgrey_asic.env:26
\# Define SPI_DEVICE CSB as reset
create_reset -interval 10 -high -waveform SPI_DEV_CLK top_earlgrey.u_spi_device.rst_csb_buf

Due to the issue, RDC reports many (27) errors starting from io_mode, or bitcnt to a few SPI_DEV*_CLK flops. They can be waived as CSb will be de-asserted (0 -> 1) avoiding any edges of SCK.

o wow...so the tool doesn't understand that CSb is related to SCK? That seems like a bug on their end...should we file an issue to track for post M2? Maybe leave the issue number here in the comments?

 I will contact them and check.


Update AJV library to the latest one

This is the latest stabile release: https://github.com/ajv-validator/ajv/releases/tag/v7.2.1

Implemented with this PR: https://github.com/elixir-europe/bio-validator/pull/5


RAM usage question

I have one question about RAM usage.

My scrapy code is not executing anymore, but I am still able to see that RAM is being consumed by playwright.
What should I do to avoid all RAM to be consumed by paywirght even so that scraping process is not running any more?
I was having a lot of playwright timeouts during scraping. Maybe I experienced memory leaks?

A good catch, thank you for noticing.


[#128217001] Scale up the instance type of concourse

https://www.pivotaltracker.com/story/show/128217001
What
We were using c4.large: 2x CPU, 3.5GB, ~$0.105 per Hour.
But we are having trouble with concourse consuming too much memory
and eventually collapses.
m4.large 2x CPU and 8GB is $0.12 per Hour, so it is a worth it to
upgrade.
How to review
Deploy concourse as described in readme. Check VM type.
Who?
Anyone but @keymon

Indeed instance type changes to m4.large after deployment.


feat: enforce stricter typing for Component props

I noticed that Component props were being loosely typed, but Svelte has a ComponentProps type for enforcing stricter props typing.
While this could have been done like below to keep compatibility
type Component<T extends SvelteComponent = SvelteComponent> = {
    component: ComponentType<T>,
} & ComponentProps<T>

I think it makes more sense to have props in a dedicated object. This is a breaking change, but I think it has a few benefits, listed below. These benefits will also be multiplied if more non-Svelte props are added to the type of Component.

It makes it clearer which props are being used by svelte-mosaic and which are being used by the Svelte component

It allows the Svelte component to have a prop named "component" without conflicting to the non-Svelte prop by the same name

It removes the warning given by Svelte for passing the "component" prop to Svelte components which don't export such a prop

<Component> was created with unknown prop 'component'

This could also be fixed by, in Mosaic and with alpha as an example, doing
const { alphaComponent, ...alphaProps } = tree.alpha;

<svelte:component this={alphaComponent} {...alphaProps} />

Thanks! Though, I didn't intend for this package to be used after finding https://github.com/orefalo/svelte-splitpanes - I wanted dynamic component shifting with https://github.com/LeoDog896/svelte-reparent that preserved browser state, but never got to it 😅

splitpanes is what I'm currently using, but it's not nearly as flexible with where panes can be as mosaic. It could make sense to use splitpanes inside of mosaic, though?

Also, I did that that reparent branch, but I don't really understand what it accomplishes that just svelte:component doesn't; would you mind explaining?

Also, I did that that reparent branch, but I don't really understand what it accomplishes that just svelte:component doesn't; would you mind explaining?

The reparent branch is completely unfinished. What svelte-reparent specifically does is preserve any DOM state that svelte doesn't when moving around elements and stops svelte from trying to recreate the entire element. However, I don't quite like the package's API design anymore.

splitpanes is what I'm currently using (see TwoDimensionalSplitPanes), but it's not nearly as flexible, with where panes can be, as mosaic. It could make sense to use splitpanes inside of mosaic, though?

I didn't consider that at all! I do agree I should use splitpanes internally for this package 👍

Still don't quite understand reparent, sorry, and I'm wondering if it's something about Svelte I'm misunderstanding because I thought the purpose of <svelte:component> was exactly what you are describing. Because, instead of
<svelte:component this={dynamicComponent} />

You could do
<dynamicComponent />

But, at least in Svelte 4, the latter is treated statically (this was recently fixed for Svelte 5, see https://github.com/sveltejs/svelte/pull/12646, deprecating svelte:component)

Nevermind, I am misunderstanding; the difference in reactivity is if the value of dynamicComponent changes, not if the contents of the component changes


update process to 0.11

<EMAIL_ADDRESS>has a very important fix that fixes the queue being completely clogged when an error happens so can we bump it :(
@sokra

:+1:

:+1:

:ship:

:trophy:

ping @sokra

Thanks


Remove auto-assign to eerhardt column on comments

cc @jeffhandley @eerhardt
Eric comments on a lot of issues to move them along but doesn't wish to be automatically treated as the triager.  Can we remove the automation for him that automatically places issues in his column when he comments on them.  @eerhardt  would you like the same thing for PRs?

@eerhardt would you like the same thing for PRs?

If it is easy, yes.


feat: add Thing Type support for IoT thing search

Hello,
I would like to add support for searching through things while filtering by ThingType.

Hello @bblommers
I can see tests in your PRs are running fine, while tests in that PR are constantly failing for the tests and code that I did not touch.
Can you give any advice on what can I do to make the tests green here and have this PR merged?


ILI9341 (ILI9XXX) set orientation function fails to update the display area correctly

Describe the bug
The ili9xxx_set_orientation() function rotates the display but doesn't update the display width and height after rotation, if applicable.
In the ILI9XXX driver (display_ili9xxx.c), ILI9XXX configuration is held in a static const struct with display size attributes x_resolution = 240 & y_resolution = 320. The display is configured for portrait mode. Display rotation works fine for 0 (normal) & 180 degrees but not for  90 or 270 degrees. After rotation, the display area is not being adjusted to cover the whole display area in landscape.
If the board overlay is configured for landscape mode (i.e.  x_resolution = 320 & y_resolution = 240), then rotation for landscape views (90 & 270) are fine but incorrect when in portrait mode. Reason being that the display area is not being adjusted after rotation.
What have you tried to diagnose or workaround this issue?
I have used several ILI9341 displays from 2.8", 2.4" and 2" sizes.
To Reproduce
Build the Adafruit 2." TFT Touch Shield v2 examples, /zephyrproject/zephyr/samples/display/lvgl.
I adapted the sample for  Particle Xenon and BBC MicroBit v2 boards. The Particle Xenon board overlay is attached below.
Expected behavior
The ili9xxx_set_orientation() function should correctly rotate the display for all supported rotations 0, 90, 180 and 270 degrees, and adjust the display area to cover whole of the screen size.
Impact
Unable to use the whole display area for presentation of text and graphics.
Logs and console output
Display size is defined in a static const ili9xxx_config structure and therefor fixed as 240x320
ili9xxx_set_orientation() can be used to rotate the display

With x_resolution = 240, y_resolution = 320
--- normal (0 deg): display fills 240x320 area, upside down
--- 180 deg: display fills 240x320 area
--- 90 deg:  displays 240x240 to left in landscape 320x240
--- 270 deg: displays 240x240 to left in landscape 320x240

With x_resolution = 320, y_resolution = 240
--- 90 deg: display fills 320x240 area
--- 270 deg: display fills 320x240 area, upside down
--- normal:  displays 240x240 up in portrait 240x320
--- 180 deg: displays 240x240 up in portrait 240x320

Environment (please complete the following information):

Zephyr v2.5.0

Additional context
Here's the devicetree section from the Particle Xenon nRF52840 board overlay.
&spi0 {
compatible = "nordic,nrf-spi";
status = "okay";
sck-pin =  <47>;
mosi-pin = <45>;
miso-pin = <46>;
cs-gpios = <&gpio1 8 GPIO_ACTIVE_LOW>; /* D4 */
ili9340@0 {
	compatible = "ilitek,ili9340";
	label = "ILI9340";
	spi-max-frequency = <25000000>;
	reg = <0>;
	cmd-data-gpios = <&gpio1 10 GPIO_ACTIVE_LOW>;  /* D5 */
	reset-gpios = <&gpio0 31 GPIO_ACTIVE_LOW>;     /* A5 */
	pixel-format = <ILI9XXX_PIXEL_FORMAT_RGB565>;
	rotation = <0>;
            frmctr1 = [00 18];
	pwctrl1 = [23 00];
	vmctrl1 = [3e 28];
	vmctrl2 = [86];
	pgamctrl = [0f 31 2b 0c 0e 08 4e f1 37 07 10 03 0e 09 00];
	ngamctrl = [00 0e 14 03 11 07 31 c1 48 08 0f 0c 31 36 0f];
};

The current display width/height can be obtained using display_get_capabilities. As you can see in https://github.com/zephyrproject-rtos/zephyr/blob/master/drivers/display/display_ili9xxx.c#L297, the returned values will take into account the current rotation. Is that part failing?

Thank you for your response.
The ili9xxx_get_capabilities() function does return the expected display size, however ili9xxx_set_orientation() in /zephyr/drivers/display/display_ili9xxx.c does not update the display width (x_resolution) & height (y_resolution) depending on the rotation.
From my understanding, in ili9xxx_set_orientation, for example if we had display_width and display_height then for the rotations we would add the following:
   0 & 180 degrees:  display_width = ILI##t##_X_RES, display_height = ILI##t##_Y_RES
   90 & 270 degrees: display_width = ILI##t##_Y_RES, display_height = ILI##t##_X_RES

In ili9xxx_set_orientation(), the display orientation is correctly updated via  data->orientation = orientation, so that ili9xxx_get_capabilities()  returns the correct display resolution. Note that in ili9xxx_get_capabilities(), for 90 & 270 degrees, width & height get updated correctly.  However, the ILI9XXX controller still has the display size prior to rotation. Therefore, after rotation, we'll see part of the display not used (see photo 2 below) though ili9xxx_get_capabilities() will think it's working with the new resolution.
I have a patched version to work but since the x_resolution & y_resolution (and inversion ) are being held in a static const struct ili9xxx_config ili9xxx_config_##n and we appear to be using struct ili9xxx_data in display_ili9xxx.c, we may want to extend ili9xxx_data to add display_width, display_height (and display_inversion) so that rotation works correctly (and we can also add a new ili9xxx_set_inversion() function).
I assume we have the ili9xxx_data so that we leave  ili9xxx_config_##n as is.
Do you know where ILI##t##_X_RES and ILI##t##_Y_RES are defined?
Thank you for looking at this issue.
Attached show the portrait image, portrait rotated by 90 degrees, and portrait rotated by 90 degrees correctly.

@key1066 from the screenshot it looks like you are using LVGL.
Is this a correct observation?
If yes did you updated the field rotated inlv_disp_drv_t?

Thank you for your suggestion. Yes, I'm using LVGL. No, I haven't updated the field rotated in lv_disp_drv_t.  I'll take a look at your link and preview further.
From my earlier review of LVGL, my understanding from LVGL is that it doesn't rotate the output data itself, it only changes the logical screen size. The ILI9341 driver would still need to inform the ILI92431 controller of the new display area after sending the command, for example, to rotate the display from portrait to landscape 320x240.
In photo #2, LVGL won't be able to access the area outside the display screen size (non-white area), hence part of the logical 320x240 display that LVGL sees is off screen.
In the case of the Zephyr driver, ili9xxx_set_orientation changes the logical screen size from portrait to landscape so that display_get_capabilities reflects the landscape screen size but the ILI9341 controller still has the screen in portrait mode.
I have also reviewed the Adafruit ILI9341 driver source. They have a similar rotation method like ili9xxx_set_orientation but in addition to issuing the rotation command to the ILI9341 controller, their ILI9341 driver also updates the display screen size when rotating from portrait to landscape (or landscape to portrait), and the GFX basically works with the logical screen size. This is currently what I do in my patched version but like to see a proper fix.
I have the same ILI9341 displays working under the Arduino Framework using the Adafruit ILI9341 driver.  Their demo app cycles through the rotations quite fast.

I think the problem here is that LVGL configures its resolution when it is initialized (see https://github.com/zephyrproject-rtos/zephyr/blob/master/lib/gui/lvgl/lvgl.c#L99) but if you later change it via the display API you need to manually call https://docs.lvgl.io/latest/en/html/porting/display.html#_CPPv418lv_disp_drv_updateP9lv_disp_tP13lv_disp_drv_t with the new settings. @key1066 can you try?

@vanwinkeljan, @gmarull, Thank you. Much appreciated.
As per your suggestion, I've used lv_disp_drv_update() in a local function to update the display orientation at run time, as in below.
All works fine.
static void disp_update_orientation(enum display_orientation orientation) {
	lv_disp_t *lv_disp;
	const struct device *disp_dev;
	lv_disp_drv_t *lv_disp_drv;
        struct display_capabilities cap;

	lv_disp = lv_disp_get_default();
	disp_dev = lv_disp->driver.user_data;
	lv_disp_drv = &lv_disp->driver;

        display_set_orientation(disp_dev,orientation);
        display_get_capabilities(disp_dev, &cap);

	if (cap.current_orientation == DISPLAY_ORIENTATION_ROTATED_90 ||
	     cap.current_orientation == DISPLAY_ORIENTATION_ROTATED_270) {
                lv_disp_drv->rotated = 1;
	} else
		lv_disp_drv->rotated = 0;

       // update display driver
	lv_disp_drv_update(lv_disp, lv_disp_drv);
	lv_obj_invalidate(lv_scr_act());
}

I also use ST7789V displays and noticed that st7789v_set_orientation in https://github.com/zephyrproject-rtos/zephyr/blob/master/drivers/display/display_st7789v.c#L256 isn't currently implemented.
Are there plans to implement this function at some stage or is there another reason as to why it is not implemented? Thanks.

I also use ST7789V displays and noticed that st7789v_set_orientation in https://github.com/zephyrproject-rtos/zephyr/blob/master/drivers/display/display_st7789v.c#L256 isn't currently implemented.
Are there plans to implement this function at some stage or is there another reason as to why it is not implemented?

@jfischer-no is there any reason why the function is not implemented?
@key1066 I assume we can close the issue?

Regarding ST7789: A few months ago, I did open an enhancement request for ST7789 set orientation but got no response, https://github.com/zephyrproject-rtos/zephyr/issues/32286.

Shall open I open a separate bug for ST7789 set orientation in the hope it may get some attention?

FYI - @vanwinkeljan, some of ST7789 displays like from Waveshare and others with CS can use the ILI9XXX driver.


Avoid stack overflow in self_talk_nonblocking_test

Build was failing in unit tests on my machine where the stack limit is
8MB (ulimit -s 8192)
Confirmed build now works with ulimit -s 512

Not sure why Travis isn't re-running the build

Restarted https://travis-ci.org/awslabs/s2n/builds/206489798 , worst comes to worst we could close this and open a new one :)


Server 2022 GVLK Keys not visible in GUI

Hello,
the Server 2022 GVLK Keys are not visible in the GUI

This is true, as we have not added the 2022 GLVK to the database yet: https://github.com/Py-KMS-Organization/py-kms/blob/master/py-kms/KmsDataBase.xml
...but I struggle to do that for you, because I'll need some more information for that:

SkuId of the CSVLK
GroupId
MinKeyId
MaxKeyId
InvalidWinBuild (optional)

I know the keys are available at https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys, but for the rest I have no idea where to look for... Could someone help me to gather this information, please?

This is true, as we have not added the 2022 GLVK to the database yet: https://github.com/Py-KMS-Organization/py-kms/blob/master/py-kms/KmsDataBase.xml
...but I struggle to do that for you, because I'll need some more information for that:
* SkuId of the CSVLK

* GroupId

* MinKeyId

* MaxKeyId

* InvalidWinBuild (optional)

I know the keys are available at https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys, but for the rest I have no idea where to look for... Could someone help me to gather this information, please?

How were those info gathered?
I can look it up if I knew how it was found on the other versions.

@simonmicro
I hope this helps.

This is true, as we have not added the 2022 GLVK to the database yet: https://github.com/Py-KMS-Organization/py-kms/blob/master/py-kms/KmsDataBase.xml
...but I struggle to do that for you, because I'll need some more information for that:

SkuId of the CSVLK
GroupId
MinKeyId
MaxKeyId
InvalidWinBuild (optional)

I know the keys are available at https://learn.microsoft.com/en-us/windows-server/get-started/kms-client-activation-keys, but for the rest I have no idea where to look for... Could someone help me to gather this information, please?

From what's showing in the GUI, the SKU ID for "Windows Server 2022" is :
9bd77860-9b31-4b7b-96ad-2564017315bf
And from another fork of py-kms, I found this version of the database file :
https://raw.githubusercontent.com/hyperboreanwolfgirl/py-kms/master/py-kms/KmsDataBase.xml

GroupId : 206
MinKeyId : 551000000
MaxKeyId : 570999999
InvalidWinBuild : [0,1,2]

As for the WinBuilds section of the database file, an entry for Windows Server 2022 should look like that :
<WinBuilds>
        [...]
        <WinBuild BuildNumber="20348" DisplayName="Windows Server 2022" UseForEpid="true" PlatformId="3612" MayBeServer="true" UsesNDR64="true" MinDate="18/08/2021"/>
</WinBuilds>

@simonmicro  I've pulled in the changes mentioned by @BenPi-Ross into a PR at #96

@Matthew-Beckett I have tested the PR, and it doesn't resolve the issue. I have located an updated KmsDataBase.xml and have raised PR #99

Does this help? (Make sure to scroll over) Utilized pkeyconfigreader

ActConfigID
RefGroupID
EditionID
ProductDescription
ProductKeyType
IsRandomized
PartNumber
EULAType
Product Key
Product ID
Extended PID
RefGroupID

{ec868e65-fadf-4759-b23e-93fe37f2cc29}
4327
ServerRdsh
Windows Server 2019 RTM ServerRdsh Volume:GVLK
Volume:GVLK
FALSE
[RS5]X21-83765
Volume
CPWHC-NT2C7-VYW78-DHDB2-PG3GK
00432-70000-00000-AA869
XXXXX-04327-000-000000-03-1033-9200.0000-2462023
4327

{19b5e0fb-4431-46bc-bac1-2f1873e4ae73}
4469
ServerTurbine
Windows Server 2019 RTM ServerTurbine Volume:GVLK
Volume:GVLK
FALSE
[RS5]X22-30731
Volume
NTBV8-9K7Q8-V27C6-M2BTV-KHMXV
00446-90000-00000-AA458
XXXXX-04469-000-000000-03-1033-9200.0000-2462023
4469

{9bd77860-9b31-4b7b-96ad-2564017315bf}
4541
ServerStandard
Windows Server 2021 RTM ServerStandard Volume:GVLK
Volume:GVLK
FALSE
[Fe]X22-39407
Volume
VDYBN-27WPP-V4HQT-9VMD4-VMK7H
00454-10000-00001-AA343
XXXXX-04541-000-000001-03-1033-9200.0000-2462023
4541

{ef6cfc9f-8c5d-44ac-9aad-de6a2ea0ae03}
4546
ServerDatacenter
Windows Server 2021 RTM ServerDatacenter Volume:GVLK
Volume:GVLK
FALSE
[Fe]X22-39426
Volume
WX4NM-KYWYW-QJJR4-XV3QB-6VM33
00454-60000-00001-AA230
XXXXX-04546-000-000001-03-1033-9200.0000-2462023
4546

{f5e9429c-f50b-4b98-b15c-ef92eb5cff39}
4556
ServerStandardACor
Windows Server 2021 RTM ServerStandardACor Volume:GVLK
Volume:GVLK
FALSE
[Fe]X22-39464
Volume
67KN8-4FYJW-2487Q-MQ2J7-4C4RG
00455-60000-00001-AA970
XXXXX-04556-000-000001-03-1033-9200.0000-2462023
4556

{39e69c41-42b4-4a0a-abad-8e3c10a797cc}
4557
ServerDatacenterACor
Windows Server 2021 RTM ServerDatacenterACor Volume:GVLK
Volume:GVLK
FALSE
[Fe]X22-39465
Volume
QFND9-D3Y9C-J3KKY-6RPVP-2DPYV
00455-70000-00001-AA521
XXXXX-04557-000-000001-03-1033-9200.0000-2462023
4557

{8c8f0ad3-9a43-4e05-b840-93b8d1475cbc}
4562
ServerAzureCor
Windows Server 2021 RTM ServerAzureCor Volume:GVLK
Volume:GVLK
FALSE
[Fe]X22-39475
Volume
6N379-GGTMK-23C6M-XVVTC-CKFRQ
00456-20000-00001-AA869
XXXXX-04562-000-000001-03-1033-9200.0000-2462023
4562

{e4db50ea-bda1-4566-b047-0ca50abc6f07}
3895
ServerRdsh
Windows Server Next Beta ServerRdsh Volume:GVLK
Volume:GVLK
FALSE
[RS3]X21-41298
Volume
7NBT4-WGBQX-MP4H7-QXFF8-YP3KX
00389-50000-00001-AA010
XXXXX-03895-000-000001-03-1033-9200.0000-2462023
3895

Similar issue with server 2016, activation works, but it doesn't show in the logs (if enabled) and it doesn't show in the web ui

Hi,
Just thought I'd add mu 2.2 cents worth as I can see a few pull requests for this.
I've been happily using pyKMS for years, but was running it on a Linux box using systemd. Recently been moving small footprint things across to Docker containers in stead, so only been looking at this more in depth as part of that.
pyKMS has been successfully activating Windows 10/11, Office 2021, Server 2022 etc, but I also encountered the issue of Windows Server 2022 not appearing as such in the WebUI as this was the first time I actually explored the Web UI.
I tried using the updated KmsDatabse.xml from https://github.com/Py-KMS-Organization/py-kms/pull/106, and while the WebUI had the correct product name and showed as 'activated' the Windows Servers 2022 were failing saying the KMS server was unavailable.
I then tried using https://github.com/Py-KMS-Organization/py-kms/pull/96 as the basis, and the activations started working again, and the WebUI was showing the correct Windows Server 2022 name, but it didn't have the Windows 11 changes.
So, I tried grabbing the KmsDataBase.xml from the current branch, and just added in the Windows Server 2022 entries from pull request 96.
I now have all the clients still successfully activating (including Windows Server 2022), and the WebUI is listing Windows Server 2022 and Windows 10/11 Enterprise etc. Attaching incase this helps anyone else, and I can see there are a few different pull requests with different KmsDataBase.xml files. The attached is working for me.
KmsDataBase.zip

just updated and it doesn't seem to fix the server 2022 issue:
py-kms is online since 6/10/2024, 5:39:23 PM. This instance was accessed 2 times. View this softwares license here.
This instance is running version "e60cc1b7e12b19e5bd4dd7db5ff7a5d609455f04" from branch "next" of py-kms.


handle 303

I think there's a better way to handle this, but I can't think of one right now.

Hey @j4qfrost, thanks for the PR. Let me check it once.

@j4qfrost, it's working, but can you please send the same PR to my develop branch instead of master, as we follow develop as the development branch?

Done.

Hey @j4qfrost,
Thanks for the fix.
Published a release v1.1.0 with the fix. Check it out:
npm rm -g linkedin-auto-connect
npm i -g linkedin-auto-connect


job getting cancelled

Running a job getting cancelled even thought there is not cancellation of job  even thought at no place i have passed err.cancelJob or called Queue.cancelJob. It only happens inside docker container otherwise works fine.
`{
"data": {
    "ciprId": "45554" ,
    "invoiceId": "98397" ,
    "invoicePaymentId": "99159"
} ,
"dateCreated": Sat Mar 11 2017 03:55:30 GMT+00:00 ,
"dateEnable": Sat Mar 11 2017 04:00:35 GMT+00:00 ,
"dateFinished": Sat Mar 11 2017 03:55:32 GMT+00:00 ,
"dateStarted": Sat Mar 11 2017 03:55:35 GMT+00:00 ,
"id": "57f31d2a-cab9-4734-8027-0e5916067c50" ,
"log": [
    {
        "data": null ,
        "date": Sat Mar 11 2017 03:55:30 GMT+00:00 ,
        "message": "Job added to the queue" ,
        "processCount": 0 ,
        "queueId": "d5e5677cddf2:jobs:payments:1:45bf900d-82dd-4f49-9664-20ee5120ad04" ,
        "retryCount": 0 ,
        "status": "waiting" ,
        "type": "information"
    } ,
    {
        "date": Sat Mar 11 2017 03:55:35 GMT+00:00 ,
        "message": "Job retrieved and active" ,
        "processCount": 0 ,
        "queueId": "d5e5677cddf2:jobs:payments:1:45bf900d-82dd-4f49-9664-20ee5120ad04" ,
        "retryCount": 0 ,
        "status": "active" ,
        "type": "information"
    } ,
    {
        "date": Sat Mar 11 2017 03:55:32 GMT+00:00 ,
        "processCount": 1 ,
        "queueId": "d5e5677cddf2:jobs:payments:1:45bf900d-82dd-4f49-9664-20ee5120ad04" ,
        "retryCount": 0 ,
        "status": "cancelled" ,
        "type": "information"
    }
] ,
"name": null ,
"priority": 40 ,
"processCount": 1 ,
"progress": 0 ,
"queueId": "d5e5677cddf2:jobs:payments:1:45bf900d-82dd-4f49-9664-20ee5120ad04" ,
"repeat": false ,
"repeatDelay": 300000 ,
"retryCount": 0 ,
"retryDelay": 60000 ,
"retryMax": 5 ,
"status": "cancelled" ,
"timeout": 300000

}`

@crossroads77 There was a logic bug introduced recently. It is fixed in v3.0.1. Please update your local version and try again.
I suspect your job failed processing and raised an error. The bug was seeing the error as a cancel.
Thanks for reporting.

Yes upgrade to v3.0.1 fixed it.
Thanks


Ayaneo Geek (and supposedly Ayaneo 2) | Extra Buttons not working and Desktop not rotated in the right way, but also not able to be rotated via Settings, and SD card apparently not recognized

Hi there, I wanted to try out Chimera OS on my Ayaneo Geek, because I was quite frustrated with the Windows experience. After installation everything seems to work as expected except for the extra Buttons (AyaNeo, "=", LC, RC) and in the Desktop view the screen is not rotated to the same orientation as the Steam Interface, but I also can't rotate it via the gnome settings, it doesn't let me apply the changes unfortunately. And because of the not-recognized buttons I basically don't have a guide button, so I can't exit emulated games for example ^^*
Oh it also seems like the SD card is not recognized in any way, I can't add it as an additional Steam library for example and when I try to manage storage via the Web Interface I just get a blank page.
I was wondering if there might be a fix or if anything went wrong during installation. But i didn't find anything for my device online, so I hope it is ok to file this issue for it now. I can provide additional data, if needed, I'm just not sure what to provide so far other than the device ^^*
Great work though, this OS seems really great so far, love the Web Interface.
Oh and I hope it's ok to file it like this, I thought three different issues seemed a bit much to create at once ^^*

Gotta correct myself, the SD card is working, it just wasn't formatted correctly

V40 will have native support for the 2/geek controls. Ayaneo have finally sent out thier dev units so we should be getting them soon. I anticipate quick resolution once we have them in hand.

V40 will have native support for the 2/geek controls. Ayaneo have finally sent out thier dev units so we should be getting them soon. I anticipate quick resolution once we have them in hand.

Awesome, native support would of course be even better ^^
Do you have any idea on the desktop rotation problem maybe? Because that would basically then be my only real remaining problem. Can't change it in the gnome settings, it says there was an error and doesn't le me apply the rotation

V40 will have native support for the 2/geek controls. Ayaneo have finally sent out thier dev units so we should be getting them soon. I anticipate quick resolution once we have them in hand.

Awesome, native support would of course be even better ^^
Do you have any idea on the desktop rotation problem maybe? Because that would basically then be my only real remaining problem. Can't change it in the gnome settings, it says there was an error and doesn't le me apply the rotation

This may sound weird, but try switching to any other resolution that does work and then switch back to your desired resolution in the rotation you are wanting.

I already tried switching resolutions, every other resolution works. It still doesn't let me rotate the screen. I can't even click "apply" when I select anything other than "landscape"

As

V40 will have native support for the 2/geek controls. Ayaneo have finally sent out thier dev units so we should be getting them soon. I anticipate quick resolution once we have them in hand.

As a quick follow up to that, would you also be able to implement the RGB light control? Or more precisely that it turns off when you hibernate the device? I think that is the only think really "sucking" power during hibernation, and otherwise the hibernation is working nicely ^^

As

V40 will have native support for the 2/geek controls. Ayaneo have finally sent out thier dev units so we should be getting them soon. I anticipate quick resolution once we have them in hand.

As a quick follow up to that, would you also be able to implement the RGB light control? Or more precisely that it turns off when you hibernate the device? I think that is the only thing really "sucking" power during hibernation, and otherwise the hibernation is working nicely ^^

Cant be done, unfortunately. While the command registers were recently reverse engineered,  they can only be accessed when the system is on. The charging red and sleep strobe are functions that are built into the firmware. This issue also exists for windows users, Aya Space can't even disable it.

As

V40 will have native support for the 2/geek controls. Ayaneo have finally sent out thier dev units so we should be getting them soon. I anticipate quick resolution once we have them in hand.

As a quick follow up to that, would you also be able to implement the RGB light control? Or more precisely that it turns off when you hibernate the device? I think that is the only thing really "sucking" power during hibernation, and otherwise the hibernation is working nicely ^^

Cant be done, unfortunately. While the command registers were recently reverse engineered, they can only be accessed when the system is on. The charging red and sleep strobe are functions that are built into the firmware. This issue also exists for windows users, Aya Space can't even disable it.

That seems weird though, I could've sworn when I had Windows installed when I first got the device the Lights actually did totally shut down when I hibernated the device. That's why I tested the Battery percentage usage over Hibernation time. I had like 1% for around 8h of hibernation (lights where out, not "strobing" or "breathing") and when I tried it again in Chimera (which had the "breathing" in hibernation) it was around 1% battery usage per hour. So I'm pretty sure in the "Windows Configuration" of the device the Lights have actually been able to turn off during Hibernation. I think that was even a feature they announced at some point, something like a full shutdown of the gamepad while in Hibernation, as to save Battery.

I think Hibernate on Windows turning of the device (and writing memory to disk) and the default Suspend on ChimeraOS does not. So this is why the lights stay on. Would love an option to actually hibernate to disk on ChimeraOS, both for the lights to be off but also for the battery to last longer. The extra 10s to boot up should be fine.

I think Hibernate on Windows turning of the device (and writing memory to disk) and the default Suspend on ChimeraOS does not. So this is why the lights stay on. Would love an option to actually hibernate to disk on ChimeraOS, both for the lights to be off but also for the battery to last longer. The extra 10s to boot up should be fine.

I'm working on this. https://github.com/ChimeraOS/frzr/commit/d6ac08d4a9a17c4e712fced11087f81d558812f1


Switch to Markdown

coverage: 98.864%. remained the same
when pulling b5b945ee161884589631ad56ef1302c2303fe205 on improve_readme
into 8ece95a72371c1b77c2bb2b7696181933c92f430 on main.


fix(deps): upgrade gravitee-bom, gravitee-common & reporter-api

Issue
https://github.com/gravitee-io/issues/issues/XXXXX
Description
A small description of what you did in that PR.
Additional context

Gravitee.io Automatic Deployment
🚀 A prerelease version of this package has been published on Gravitee's private artifactory, you can:

use it directly by updating your project with version: 3.0.0-upgrade-deps-SNAPSHOT
download it from Artifactory here

:tada: This PR is included in version 3.0.0 :tada:
The release is available on:

3.0.0
GitHub release

Your semantic-release bot :package::rocket:


Fix broken change log rst link

Small typo left in from #395

closing and addressing as part of #404 to not pollute the changelog


chore(package): update semantic-release to version 8.2.0

Closes #75

Coverage remained the same at 100.0% when pulling 2a935c98bac7f3007828a4d185dee0e2d532e209 on greenkeeper/semantic-release-8.2.0 into 179ad21d3b13e50879139e8303c5ba483d9b3c61 on master.


Releases and Docker Images

Is your feature request related to a problem? Please describe.
It would be nice if we could have releases, pre-built binaries and docker images for pmcenter.
Describe the solution you'd like
Setting up a CI/CD pipeline would be a pretty good solution I think.
Describe alternatives you've considered
Nope
Additional context
Nope

Thanks for the feedback! Sorry for the late response but I'll soon start working on it.

I've created a docker hub repository with docker image pre-built available, and updated the README file, which you can check out right now.
Since pmcenter has its own updates system, currently I'm not going for the CI/CD pipeline solution (although it's considered pretty awesome).
Closing this issue, feel free to open it again for additional info.


Monai Application Server plugin for task runner

Closing this since we don't plan to have a MONAI App Server.


Command for the script is wrong

AzureMigrateInstaller-physical.ps1

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

ID: e280f0d6-a71b-6b97-5d3d-ef6974607581
Version Independent ID: 65621352-e710-b77b-0ca4-ec169566d7e6
Content: Set up an Azure Migrate appliance for physical servers - Azure Migrate
Content Source: articles/migrate/how-to-set-up-appliance-physical.md
Service: azure-migrate
GitHub Login: @rayne-wiselman
Microsoft Alias: raynew

@anspa Thanks for the feedback. I have created a PR (Pull Request) with the required changes. The doc will automatically get updated once the open PR is merged.

Verified and updated the document as required. Thanks.


Possible fix for get_build_via_exporttool() crashing upon attempting to index possible_versions variable

Upon using this to scan IPs, the get_build_via_exporttool() consistently crashed for me as it attempts to index a nil value in possible_versions.
attempt to index a nil value
stack traceback:
	[C]: in for iterator 'for iterator'
	ms-exchange-version.nse:74: in upvalue 'get_build_via_exporttool'
	ms-exchange-version.nse:103: in upvalue 'get_owa_build'
	ms-exchange-version.nse:215: in function <ms-exchange-version.nse:211>
	(...tail calls...)

This is solved by checking whether possible_versions is nil and returning build if this is the case. It now runs smoothly for me.

Thanks!


Add new type which represents pointer with tag value

jmem_cpointer_tag_t is newly added to represent pointer along with tag value.
This new type is first applied to scope_cp to mark initailized function properties (length, name) later
JerryScript-DCO-1.0-Signed-off-by: HyukWoo Park<EMAIL_ADDRESS>

@zherczeg Thank you for the review. I'll update it with some fix for 32bit mode.

@zherczeg
I fixed it as you commented.
But it seems that appveyor is not working now. I'll retry it later.

It looks like many prs are blocked by appveyor, we will figure out something.


Make the usage of pairings generic in ZeroMorph implementation

For now we are just using Grumpkin, but we should make our implementation generic to work over any elliptic curve that provides an appropriate bilinear pairing.

Helped by #28, but #30 is needed to convert the current hiding variant to a generic form.

This is done in https://github.com/lurk-lab/arecibo/tree/zeromorph, please reopen if there's anything left


Missing flag prints name of the first flag, not the missing flag.

consider a command foo --bar --baz
where --bar is defined, but --baz isn't.
pflag prints unknown flag: --bar even though the actual offending flag is --baz

I added a test case trying to reproduce this, but I couldn't manage it. Maybe it has something specific to do with that command line in GoogleCloudPlatform/kubernetes#4247? If you can provide a failing test case that would be great.

Thanks for looking into it, I'm using pflag via cobra commander for CLI,
maybe that's doing something screwy.  I'll try to get a repro.
Brendan
On Feb 14, 2015 7:17 PM, "Alex Ogier"<EMAIL_ADDRESS>wrote:

I added a test case trying to reproduce this, but I couldn't manage it.
Maybe it has something specific to do with that command line in
GoogleCloudPlatform/kubernetes#4247
https://github.com/GoogleCloudPlatform/kubernetes/issues/4247? If you
can provide a failing test case that would be great.
—
Reply to this email directly or view it on GitHub
https://github.com/ogier/pflag/issues/14#issuecomment-74402171.

Another case: https://github.com/GoogleCloudPlatform/kubernetes/issues/4758
cc @thockin

Ok, see https://github.com/spf13/cobra/pull/65, this looks like its an issue in the upstream user.


Added a form of authentication to the UI

I added HTTP basic authentication to the web UI
I extended the existing StaticWebRoutable class.
The password and user name can be defined in the properties file.
Since there are no existing unit tests for the  UI, I did not have to change one.
This is my first contribution Iam waiting for your feedback.
Floodlight-DCO-1.0-Signed-off-by: Jannis Ohms<EMAIL_ADDRESS>

@jaoh quick ping on this one -- could you please briefly describe the use case for the work? Your information would help us better understand your work, thanks!

@jaoh I'll close this PR for now -- if you want to revisit, feel free to re-open it. Thanks!


[BUG] Yurthub keeps crashing: "lb failed to cache req yurthub watch services"

What happened:
After adding one node using the yurtadm join command, yurthub  keeps crashing and restarting every few minutes, causing kube-flannel, kube-proxy and raven-agent to restart aswell
What you expected to happen:
For yurthub to keep running normally.
How to reproduce it (as minimally and precisely as possible):

Installed kubernetes master node on a server with kubeadm (version 1.28.5).
Installed flannel, on CIDR <IP_ADDRESS>/16
Installed OpneYURT components using helm, following this guide (https://openyurt.io/docs/installation/manually-setup)
Installed yurtadm on an edge node (raspberry pi running ubuntu), and execured the following command:
yurtadm join <IP_ADDRESS>:6443 --token=xxx --node-type=edge --discovery-token-unsafe-skip-ca-verification --cri-socket=unix:///run/containerd/containerd.sock --v=5
All components are installed, but the edge components crash after a few minutes, then restarting again, in a loop.

Anything else we need to know?:
Environment:

OpenYurt version: v1.5.0
Kubernetes version (use kubectl version):
Client Version: v1.31.3
Kustomize Version: v5.4.2
Server Version: v1.28.15
OS (e.g: cat /etc/os-release):
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.1 LTS (Noble Numbat)"
Kernel (e.g. uname -a):
Linux thesis-gilleslefranc-2 6.8.0-49-generic #49-Ubuntu SMP PREEMPT_DYNAMIC Mon Nov  4 02:06:24 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Install tools:
Others:

YurtHub logs (last 10 lines):
2024-12-15T11:48:15.291964103Z stderr F I1215 11:48:15.291262       1 cache_manager.go:386] yurthub watch nodepools: /apis/apps.openyurt.io/v1beta1/nodepools get 0 objects(add:0/update:0/del:0)
2024-12-15T11:48:15.292577203Z stderr F E1215 11:48:15.291396       1 loadbalancer.go:391] lb failed to cache req yurthub watch nodepools: https://<IP_ADDRESS>:6443/apis/apps.openyurt.io/v1beta1/nodepools?allowWatchBookmarks=true&resourceVersion=5434&timeoutSeconds=309&watch=true in local cache, EOF
2024-12-15T11:48:15.292674924Z stderr F I1215 11:48:15.291069       1 util.go:248] yurthub watch nodepools: /apis/apps.openyurt.io/v1beta1/nodepools?allowWatchBookmarks=true&resourceVersion=5434&timeoutSeconds=309&watch=true with status code 200, spent 1m15.187555851s
2024-12-15T11:48:15.292730497Z stderr F I1215 11:48:15.291838       1 util.go:248] yurthub watch services: /api/v1/services?allowWatchBookmarks=true&resourceVersion=5432&timeout=5m7s&timeoutSeconds=307&watch=true with status code 200, spent 1m15.083990561s
2024-12-15T11:48:15.292761737Z stderr F I1215 11:48:15.292107       1 secure_serving.go:311] Stopped listening on <IP_ADDRESS>:10261
2024-12-15T11:48:15.292789329Z stderr F I1215 11:48:15.287226       1 dynamic_cafile_content.go:170] "Shutting down controller" name="client-ca-bundle::/var/lib/yurthub/pki/ca.crt"
2024-12-15T11:48:15.292816385Z stderr F E1215 11:48:15.292258       1 cache_manager.go:392] yurthub /api/v1/namespaces/kube-system/configmaps watch decode ended with: EOF
2024-12-15T11:48:15.292843088Z stderr F I1215 11:48:15.287318       1 tlsconfig.go:255] "Shutting down DynamicServingCertificateController"
2024-12-15T11:48:15.292869106Z stderr F I1215 11:48:15.292326       1 cache_manager.go:386] yurthub watch configmaps: /api/v1/namespaces/kube-system/configmaps get 0 objects(add:0/update:0/del:0)
2024-12-15T11:48:15.293191137Z stderr F I1215 11:48:15.287407       1 start.go:207] hub agent exited

/kind bug

@Gillefranc It seems that Yurthub container has received SIGTERM signal from the os, this means that Yurthub process has been killed by os.

@Gillefranc you can use the following command to verify which signal cause yurthub exit.
strace -p {PID} -e trace=signal

please use the pid of yurthub process to replace the {PID}.


add new features

Background
The script addon.py already have functions for preprocessing, normalization, clustering, cell type prediction, gene list for cells/tissues, gene expression per cell types, DEG per tissue types, and UMAP plotting for cell types.
Suggested features
Addition of following features will complete the omics agent task:
1. Data import module
2. csv reader function for agent
3. Omics data QC
4. batch effects correction
5. DEG for cell types
6. plot UMAP for tissue types
7. Cell annotation and cell discovery
8. Lineage/trajectory inference analysis
9. Functional enrichment, ontology and pathway analysis
10. Gene regulatory networks
11. cell-cell communication
12. Cell compositional analysis
13. Gene perturbation modeling
14. Metabolic modeling
15. Multi-omics data integration
16. Method-specific features (e.g. TFBS from scATAC-seq, immune receptors)
Next steps
1. unit testing
2. Connect these tasks with LangChain agent

Updated data import functionality
Replace hard coded file location with e.g., cellxgene (search over metadata and download datasets by ID)

3. Omics data QC
Add filtering based on QC metrics such as mitochondrial gene counts, doublets, # of genes, etc.

4. batch effects correction and data visualization
Possible calling Seurat for batch correction and UMAP

6. plot UMAP for tissue types
Unify the plotting by cell type or by tissue type. In general, one should be able to plot a UMAP on whatever dimension they are interested in.

7a. Cell annotation
Option 1: user provides a custom gene list or Option 2: database e.g. ImmuneCellAI or CyberSort
7b. Cell discovery
Clustering and detection of clusters via a defined metric

12. Cell compositional analysis
Quantified proportions of cell types in a tissue or region of interest

14. Metabolic modeling
Integration with GRN to constrain a metabolic model with applications in cancer, immunological and inflammatory related diseases, etc.

15. Multi-omics data integration

Dual ATAC-seq and RNA-seq kits from 10x
Data fusion algorithms such as MoFA

Prerequisites

The above features should be labeled as either a "tool" or a "microagent" (e.g., cell2Sentence) and also propose what would be the function, script, class, etc that would be the "tool" or the single cell foundation model that would be the "microagent"
Map out the folder and file layout for the talk2cells agent
refactored and reorganize the current code into tools and microagents


How to load all pages at once

Attach (recommended) or Link to PDF file here:
Configuration:

Web browser and its version:Chrome 76.0.3809.132
Operating system and its version:windows 7
PDF.js version:2.2.228
Is a browser extension:

What went wrong? (add screenshot)
How to load all pages at once,Now the default load is 2 pages，Continue loading when the mouse scrolls to a page。
I want to load all pages at once.Thank you ~

Duplicate of #11179.


drivers/adc: stm32: workaround for L462xE errata 2.5.2 and stuck reads

According to the ST Errata sheet ES0389 - Rev 5, section 2.5.2, the
workaround to the issue of "Wrong ADC result if conversion done late
after calibration or previous conversion" is to perform two consecutive
ADC conversions.
We found also that the same objective is achieved enabling and disabling
it at every read. Moreover, this approach solves another issue found on
several STM32L462VE samples, where the reads were stuck, giving always
the same wrong value, that was 0 or the last calibration value.
Additional clearing of ADRDY flag has been added to avoid finding it
already set before next enabling.
Signed-off-by: Giancarlo Stasi<EMAIL_ADDRESS>

It looks like buildkite had errors on tests that don't seems to be related to this PR changes (e.g. tests/kernel/workq/work/kernel.work.api).
The "convert to draft - put in ready state" trick used in similar past cases doesn't help.

I would like other ADC users could review

@str4t0m, thanks for your suggestions. I tried to apply the changes you proposed.
I could test them with some limitation on our L462VE platform, as we're using an older branch without G0 family support, I'll try to test it more when possible. Unfortunately I don't have any G0 family board to test it.

@giansta - is this one moving forward still?

@str4t0m - can you please re-review?

@anangl - could you also please review?

@giansta , @str4t0m  - can we move this forward?

@giansta - please address comments from @str4t0m


Removed unneeded struct

closes https://github.com/Comcast/codex/issues/27

Codecov Report

Merging #37 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #37   +/-   ##
=======================================
  Coverage   59.17%   59.17%
=======================================
  Files          11       11
  Lines         627      627
=======================================
  Hits          371      371
  Misses        229      229
  Partials       27       27

Impacted Files
Coverage Δ

db/db.go
38.51% <ø> (ø)
:arrow_up:

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 49ba20f...1708c22. Read the comment docs.


Setting OPENTOK_VERSION in Makefile

Fixes https://github.com/kickstarter/ios-oss/issues/75

Thanks for the feedback! I updated the PR


Add support for subdoc xattrs and fetching document vattrs

I appear to have missed half of the mutation operations...

I appear to have missed half of the mutation operations...


[Guide] ES6: Prevent object mutation; fixes and enhancements

Remove phantom image
Remove notes for contributors
Change explanation and hints.
Links to markdown

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 🎉


Performance and markers.

I want to plot two data series: one with 10 data points with markers and one with +5000 data points and no markers.  This made my datasets (with just 500 entries) quite slow !!!
Wihtout datalabels its fast (anyway I dont know why it takes so much time to print the datalabels).


[goBack]: Go back TO rather than FROM?

I don't understand the meaning / usage of the goBack method when a key is supplied. Let's say I have the following event history:
navigation.navigate(SCREEN_KEY_A);
...
navigation.navigate(SCREEN_KEY_B);
...
navigation.navigate(SCREEN_KEY_C);
...
navigation.navigate(SCREEN_KEY_D);

I am now on Screen D and when I click some contrived button on Screen D, I expect to go all the way back to A. Not immediately back to C, but straight back to A (popping D, C, and B). My intuition says the following code should do it:
navigation.goBack(SCREEN_KEY_A)

I.e., "go back TO Screen A", but this doesn't seem to be the case. The docs say that when you supply a key to goBack, it specifies the screen to go back FROM. Does this mean in the example above, I would want:
navigation.goBack(SCREEN_KEY_B) // if I go back from B, I will land on A?

I tried the above usage (supplying a key to goBack), but nothing happens. Nothing gets popped, no errors are logged. So I've fallen back to using:
navigation.goBack(null);
navigation.goBack(null);
navigation.goBack(null);

But this is terrible for obvious reasons.
Can you clarify what you mean by "from", and how the goBack method should be used to achieve the example above? Thanks!

I believe it's a typo and we meant to, @ericvicenti ?

I also would like to go back from e.g. Home > Start > Login from the Login page straight back to the Home page.

goBack with a key does not seem to work at all on beta 7. Nothing happens + no error message.

I would also like to know how to do this. I previously used NavigationExperimental and had access to a popTo function, which would pop routes off the stack all the way to a specifc named route, but I can't see an obvious way to do this with react-navigation.

Same problem +1.

I agree that this should be available by default. Here's code I use which works (does flash up the screens in between though):
import { Navigator } from './Navigator';
import { JUMP_BACK_TO_ROUTE } from './constants';

export const reducer = (state, action) => {
  if (action.type === JUMP_BACK_TO_ROUTE) {
    const newState = {
      ...state,
      routes: [],
    };
    for (let i = 0; i < state.index; i += 1) {
      const routeCopy = { ...state.routes[i] };
      newState.routes.push(routeCopy);
      if (routeCopy.routeName === action.routeName) {
        newState.index = i;
        break;
      }
    }
    return newState;
  }
  return Navigator.router.getStateForAction(action, state) || state;
};

I expect to go all the way back to A

How do you get the key for A?
Probably the following is better:
goBack() - Go back 1 level
goBack({ to: key }) - Go back to this screen, but where do you get this key? prolly you should be able to supple a routeName and it should take you two the last screen with that name
Though I'm not sure what goBack({ from: key }) will do, or supposed to do.

can we pass Params while using goBack() function

How do you get the key for A?

Many ways. For example, passing an onDone function prop, such as this:
// in some part of the application, i..e ScreenX
<SomeComplexScreenOrStackOfScreens
  ...
  onDone={() => {
    navigation.goBack(SCREEN_KEY_X);
  }}
  ...
/>

// in another part of the application, i..e ScreenY
<SomeComplexScreenOrStackOfScreens
  ...
  onDone={() => {
    navigation.goBack(SCREEN_KEY_Y);
  }}
  ...
/>

How would you pass the onDone prop to a screen?

Oh. Imperatively, through params:
// push to SomeComplexScreenOrStackOfScreens from ScreenY, want to return to ScreenY when done
navigation.navigate(SCREEN_KEY_SOME_COMPLEX_SCREEN_OR_STACK_OF_SCREENS, {
  onDone: () => {
    navigation.goBack(SCREEN_KEY_Y);
  },
});

// push to SomeComplexScreenOrStackOfScreens from ScreenX, want to return to ScreenX when done
navigation.navigate(SCREEN_KEY_SOME_COMPLEX_SCREEN_OR_STACK_OF_SCREENS, {
  onDone: () => {
    navigation.goBack(SCREEN_KEY_X);
  },
});

The onDone param is then treated as a first class citizen in SomeComplexScreenOrStackOfScreens; it is passed around / stored / wired up accordingly so the system knows what do do when the user is "Done".

To clarify what I mean by SomeComplexScreenOrStackOfScreens, think of a slide show. It can be a screen that calls itself recursively until you reach the end of the slide show. At that point, you have no more slides to push, so you need an exit strategy. This is where onDone comes in.

@joncursi  can we pass Params while using goBack() function ???

Passing functions in params in not recommended. Though yeah, you can pass the key in the param. Doesn't seem a lot useful though since it's just the previous screen.

@satya164 it's not always the previous screen. In the slideshow example above, you could push through 20 slides, and then at the end want to pop all the way back to the screen that initiated the slide show to begin with. Know what i mean?

yeah, gotcha

What if we allowed a key to be specified to navigate, and it would "navigate back" if the key is in already in the routes.
This could also be a nice solution to the 'tap-twice push-twice' issue. When providing a key and a link is quickly tapped twice, the first navigate pushes, and the second navigate simply makes sure that the correct key is active.
More discussion in https://github.com/react-community/react-navigation/issues/135

That would be a good idea!
Op 26 apr. 2017 17:31 schreef "Eric Vicenti"<EMAIL_ADDRESS>
What if we allowed a key to be specified to navigate, and it would
"navigate back" if the key is in already in the routes.
This could also be a nice solution to the 'tap-twice push-twice' issue.
When providing a key and a link is quickly tapped twice, the first
navigate pushes, and the second navigate simply makes sure that the
correct key is active.
More discussion in #135
https://github.com/react-community/react-navigation/issues/135
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/react-community/react-navigation/issues/1213#issuecomment-297448902,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGMQRa9vyNVBcJXDuJvW0MRqoqGSGIY9ks5rz2NWgaJpZM4NGblB
.

same problem

thanks @edmofro , that suits me well for now!

My case is quite specific so to go back from say routeFive to routeTwo i passed routeTwoKey as a prop down to routeFive then used goBack(routeTwoKey);

I have routes: List -> Detail -> Update.
I want to back to the List after submitted an update. So, i did:
  // Navigate to Update with Detail key as a param.
  handleUpdatePress = (params) => {
    const { navigate, state } = this.props.navigation;
    navigate('UpdateResult', {
      ...params,
      parentKey: state.key,
    });
  };

On Update screen, i write a handle for submitted update:
  handleSubmitted = () => {
    const { goBack, state } = this.props.navigation;
    const { parentKey } = state.params;
    goBack(parentKey || null);
  };

@giautm I'm not sure how you got that to work because when I do the same thing on my end (supplying a key rather than null), nothing pops!

To be honest, the whole key/from thing doesn't make much sense to me. My absolute preference would be to maybe have an alternative mode for "goBack" (if we didn't want to break BC) which would simply keep popping until a given routeName (not key - they're too hard to create* and then pass around!) is found, and then stop at that screen. So pretty much like the OP's method but instead of using these weird keys we just use the routeName (which, actually, I think the OP is trying to do anyway). That'd also work for @joncursi's slideshow issue.

*In fact I'm not currently sure how to create them. They appear to be being generated for me on my navigate actions, but I need to read the docs as to how to create my own to use as "back from" keys temporarily.

FWIW I have written by own goBackTo saga that I am currently using. While it is based on redux-saga, the same could work for redux-thunk or anything else that can query the current state in order to determine an action that should be dispatched.
I feel like it does the most correct (with what react-navigation gives us anyway) way to solve this. In short:

Get current stack
Starting at the current index, and working backwards, find a route with the given routeName
When found, get the key for the screen that's "next" in the stack after it
Call `NavigationActions.back() using the "from key" mode and using that key

There's a little bit of extra checking in there to ensure we don't go to odd places if the screen was not found or is the screen we're on. (Not found: just go back one screen, screen we're on: do nothing.)
So far in my limited testing it works fine, but I'll update that gist if it needs refinement.

#3393 has landed, so hopefully this is addressed now! Feel free to file followup issues if it doesn't work for you
@alexrussell, the main reason is because there may be several routes with the same routeName (it really means more like route type), so they are not really identifiable that way. Keys will never be duplicated. However, you can now provide a key while navigating to something, so hopefully they key will be more accessible when navigating back to a screen.
Also, you can provide a key to the back action to tell the stack where to go back from.

I see where you're coming from, though I must say, even given the caveats of a route name not being unique (though it is unique to a 'screen', just not a screen + parameters, right?), most of the time all I want to do is actually go back in the stack until you find a route (any route) that matches the route name. Realistically I want to go back to the most recent state of a given screen, so that wouldn't matter to me as long as the semantics of going back is that it goes back only to the most recent route in the stack.
(Also, side note, I'd definitely have to go back to rather than from but again maybe that's just me misunderstanding the use-case of the current situation and trying to fit my own one into it.)
Anyway, fair enough if you don't feel comfortable with the library supporting something very slightly ambiguous (though, of course this could be specified in the docs, etc.). As mentioned earlier I managed to come up with my own utility function to do this anyway, it's just a shame it's not in the lib.

I kinda agree that it would be nice to support this general use case of going back to the screen with the route name. Actually.. we could probably fix this by using the route name as the key, until the first duplicate key arrives!
Only confusing part is that you specify the "key" inside the action and not the routeName, so people may mix up the concepts because of this.
cc @brentvatne

@ericvicenti actually that may not be as useful a fix as you think - if RN uses the route name as the key until it sees a duplicate, it means that if the stack contains two entries with the same route name, the more recent one will have the generated (unknown) key, so going back to a given 'screen' will end up going back to the first (oldest), not the most recent one. Unless I'm not understanding you correctly.

Yeah, you're right that it wouldn't be ideal in that case. If you have another suggestions, maybe you could draft up an RFC to propose it to the community?

@ericvicenti the only suggestion I have right now is the gist that I posted earlier. It would probably need a tweak to be implemented into RN: first off it wouldn't need to be a saga as it'd be built into RN and wouldn't need to generate a back-from-key action as it's already be an action, also it has its own set of heuristics that you may not like (if no route found go back one screen, if current route is the route searching for do nothing), so I dunno if it's really worth anything to you.

It seems there isn't a clear solution here, but thanks for the feedback. I'll keep the use case in mind for future improvements!

That sounds fair.

@alexrussell I agree that a function to go back to screen with routeName is necessary and it'll make my code much cleaner. At the first time, i'm so confused about the routeName and key. Hope @ericvicenti could provide an official function to solve this.

Good news! This is something we are changing in v2 within the navigate behavior:
https://github.com/react-navigation/rfcs/pull/25
Now you can 'navigate' to a routeName that is earlier in the stack, and you will go back to it.
Feel free to try this behavior out in<EMAIL_ADDRESS>Thanks go to @brentvatne for this fix!

Ooh, sounds promising. And from the looks of it you can still have multiple entries in the stack of a given route by just using the key property, right? (Because that could be an issue in some use cases.)

@alexrussell - yup, exactly. those are the two options in that case

I changed @edmofro code a bit, so you can add a parameter backTo when navigating to a page which needs to goBack to a certain page when navigating back:
if (
    action.type === NavigationActions.BACK &&
    (state.routes[state.index].params &&
      state.routes[state.index].params.backTo)
  ) {
    const backTo = state.routes[state.index].params.backTo
    const newState = {
      ...state,
      routes: []
    }
    for (let i = 0; i < state.index; i += 1) {
      const routeCopy = { ...state.routes[i] }
      newState.routes.push(routeCopy)
      if (routeCopy.routeName === backTo) {
        newState.index = i
        break
      }
    }
    return newState
  }

Now when I navigate to a screen which needs to goBack to a certain page I can use the backTo param:
navigate('UserInfo', { backTo: 'Dashboard' })

@superdopey looks good but can you please tell me where do you put this code?


Implement service unsubscribe command

Fixes issue #736

Closing as a new approach has been decided (see https://github.com/projectriff/riff/issues/771 and https://github.com/projectriff/riff/issues/772).


Channel Closure since Aug 9

As the tittle reads I closed the channel on Aug 9 and nothing.. I hear from everyone that it typically takes 2 weeks and someone mentioned it only took 2 days from them.. I don't know why it's taking so long but here's the channel ID d3e40097346c73cf02600e49eab939485d3cdfe58ce7c26dac0488769a5b02ab

Can you post your logs?

I'd be happy to @benthecarman can you tell me how I can find them ?

Settings > emergency kit > download logs
Then upload them here

I just saved it to my phone but didn't know how to upload it here so here's a link https://wormhole.app/6d7W9#5ufwZrqZTRmQl7A9-o2Kjw

Also @benthecarman quick question, cause this might solve it. A fren of mine sent the liquidity for the channel to open, would that be reverted back to his address or go to on-chain mutiny wallet that I have ?

Also @benthecarman quick question, cause this might solve it. A fren of mine sent the liquidity for the channel to open, would that be reverted back to his address or go to on-chain mutiny wallet that I have ?

No it should go to your onchain and wallet


How to stretch the tap target to fill the entire button

How can I make the tap target larger like on the second image?

Are you using latest version?

I'm using the 2.1.4 because of some other dependencies

This has been fixed at recent releases.
The workaround for earlier versions is to adjust button height instead of add contentPadding.

Which height?

@patrikbadanjak
https://pub.dev/documentation/dropdown_button2/latest/dropdown_button2/ButtonStyleData/height.html
It was called buttonHeight in earlier version.


Do not allow duplicate labels across function expression boundaries

Filed by @michaelficarra previously as issue 561.
What steps will reproduce the problem?
Attempt to parse a: !function(){ a:; }.
What is the expected output?
A parse failure.
What do you see instead?
An AST.
What version of the product are you using? On what operating system? Which browser?
esprima.org: http://esprima.org/demo/parse.html?code=a%3A !function a() { a%3A%3B }
Please provide any additional information below.
Remember that duplicate labels are allowed across function declaration boundaries, as in a: function a(){ a:; }.

I believe that program is valid. At least, browsers and Shift accept it, and per spec ContainsDuplicateLabels of ExpressionStatement is unconditionally false.
@michaelficarra, can you clarify?

@bakkot This was true during ES5. See ES5 §12.12.

An ECMAScript program is considered syntactically incorrect if it contains a LabelledStatement that is enclosed by a LabelledStatement with the same Identifier as label. This does not apply to labels appearing within the body of a FunctionDeclaration that is nested, directly or indirectly, within a labelled statement.

I think we fixed it in the ES6 timeframe, and that appears to be confirmed by the section of the spec that you linked.

Closing this as it does not apply anymore.


please provide an API to read JSON from file directly.

Describe the feature in as much detail as possible.
In most case, I have a config file with json format data in it. I want to load this config parameter directly.

Include sample usage where appropriate.
For example, I have a mysql client that will read the configuration of MySQL ip address, port,  user name and password. All these infos are provided in a json file.

This can be easily done with the public API:
json from_file(const std::string& filename)
{
    std::ifstream s(filename);
    return json::parse(s);
}

(That said, I do not think that such a function needs to be added to the library.)

thanks


"Github" code data download only

The size of pile is too big for me. I just want to download the "Github" code data. But the number of Pile train file is 30. I would like to know exactly which file contains the "Github" code data.

The data is already processed by that stage, and may not be what you want. You probably want the github.tar from the preliminary components https://the-eye.eu/public/AI/pile_preliminary_components/github.tar and process it yourself.

The data is already processed by that stage, and may not be what you want. You probably want the github.tar from the preliminary components https://the-eye.eu/public/AI/pile_preliminary_components/github.tar and process it yourself.

Hi, thank you so much for your sharing.
I download the github.tar, but I can not unzip the file by tar -xvf github.tar. My github.tar is 108,097.71MB. I'm very confused why I can not unzip it.
Best.

The link is no longer working, is there another link to obtain the data?


Add rustfmt to the tools list

r? @alexcrichton
We should probably add something for cargo-fmt too once https://github.com/rust-lang/rust/pull/46031 lands, but I'm not sure if we can just add it to the list or not, seeing as it is not its own component.

Thanks! Mind detailing a bit what happens if we land this? Does rustup auto-create shims for all these tools? Do we know what happens when rustup encounters a file that already exists?
I'm a little worried that the upgrade experience here won't be great (you update rustup and all of a sudden rustfmt stops working) but maybe because it's nightly-only it's ok?

The list is used for creating hard links - rustup creates a hard link for each name in the list to the rustup executable. The same list is also used for cleaning up the old multirust stuff and for uninstall. If a file exists where rustup wants to hardlink, then it just removes it.
I guess that is pretty sucky for people who have cargo installed rustfmt, but the fix is pretty easy. However, this would also affect people using the Syntex version of rustfmt, so isn't limited to nightly users.
I'll have a think about if we can improve this...

Oh so I don't think it's critical we think too hard about this, but rather we can just be clear about the messaging. For a "true lossless experience" we'd have to wait for rustfmt-preview to hit the stable channel I think (right now I think it's only beta/nightly?). That is, for all beta/nightly users there's a "better method" of installing the rls which we'll manage from now on if they follow a few simple steps (albeit not automatic steps, but hey rustfmt is pre-1.0).
I'd personally be ok doing that but if you think we should be more cautious I'm ok with that as well!

I think we can't land as is - everyone who has rustfmt installed will have it broken when the rustup update with no messaging about the issue or how to fix it. I'm not too worried about stable users, there are probably a few left, but that version of rustfmt is really old.
I don't think we can do this only when the user adds the rustfmt component without some major re-jigging of rustup. Two ideas:

add a temporary, opt-in flag, e.g., rustup update --rustfmt which adds the shims, by default don't add rustfmt
detect existing rustfmt and display a warning and continue y/n prompt (do people run rustup update on CI or other automated environments? Could this cause problems there? I suppose we could just issue a warning and do it anyway without a prompt).

Actually yeah a warning sounds great to me! Something like "that binary already exists, please remove it and then add the rustup component". Presumably rustup would just automatically create the binary if it doesn't exist on each invocation?

Bear in mind that the component may well not exist for many of the toolchains the user has installed, assuming it has only just been added. Am I right in thinking rustfmt doesn't support stable rust yet? So at least you won't have to wait for the component to land on stable, but you may still want to leave some time between adding the component, and enabling the warning and proxy in rustup.

but you may still want to leave some time between adding the component, and enabling the warning and proxy in rustup.

It's already been a few weeks since we added the component and it is available on beta.

@alexcrichton ok, this is a version with a warning. It was a bit more complicated than I thought because how do we distinguish rustfmt that was installed by the user from rustfmt installed as a shim by rustup? So I added some token files to hack around the issue. It is not clear to me how tool shims actually get deleted, but it looks like rustup nukes the Cargo directory, which makes the rustfmt thing a non-issue. I've not done anything with the Windows installer because I figured the number of stable Rustfmt users on Windows will be very small.

@nrc oh these are all hard links I think, so I believe same-file should do the trick? (the crate)

Would it be possible to add a test for this as well to ensure the UI looks right and the file isn't clobbered?

I'm not clear on the details here, but it seems like rustup may make hard links or soft links, depending on the platform, would the same-file trick still work? And what could we compare the file to using same-file?

Oh if it's symlinks then it wouldn't work yeah, and I was thinking we'd compare to rustup itself. Perhaps in the meantime we could just compare file sizes? (seems unlikely they'd be byte-for-byte the same size)

This version compares the size of the possible links to try and work out if they are rustup shims or real files.

@bors: r+
Looks great!

:pushpin: Commit 93a5569 has been approved by alexcrichton

:hourglass: Testing commit 93a5569c5e1117a407f8eb017294c0cd2e49ca76 with merge 4c23be5fe674b5f321e8095287271288dd6459dc...

:boom: Test timed out

@bors: retry

:hourglass: Testing commit 93a5569c5e1117a407f8eb017294c0cd2e49ca76 with merge 9f013e816a2ffc00b328c0d604aa52fa0ca89b1b...

is bors stuck? It shouldn't take 10 hours, right?

:boom: Test timed out

urgh well it passed anyway

So, with this released, how should one install rustfmt on a clean environment? Pass --force to cargo install?
I hope this is the right place to ask this kind of questions.
$ docker run -it --rm ubuntu:xenial-20171201
# apt-get update
# apt-get install build-essential curl
# curl https://sh.rustup.rs -sSf | bash -s -- --default-toolchain nightly -y
# rustc -V
rustc 1.24.0-nightly (169929308 2017-12-23)
# rustfmt
error: toolchain 'nightly-x86_64-unknown-linux-gnu' does not have the binary `rustfmt`
# cargo install rustfmt-nightly
    Updating registry `https://github.com/rust-lang/crates.io-index`
 Downloading rustfmt-nightly v0.3.4
  Installing rustfmt-nightly v0.3.4
error: binary `cargo-fmt` already exists in destination
binary `rustfmt` already exists in destination
Add --force to overwrite

@mcheshkov eventually, the right way will be to rustup component add rustfmt-preview, but I think there is still a bug or two to deal with. In the meantime, cargo install rustfmt-nightly --force should work.


updated .csproj file to point to the same directory for the packages folder

The solution was not building otherwise as the .csproj file was looking for the packages folder one level above it.

Thanks @vman ! I am not maintaining this for a long time but thank you for the PR :)


How do I use this package with jest?

Currently installed Laravel version:
6.6.*
Currently installed Ziggy version
0.8.1
Hello, I'm in the course of testing my vue components, but I'm stuck on Vue components that use this package. For some reason I am not able to import the route helper. In the hopes of figuring this out I'm launching a long shot here, maybe someone has had a similar issue.
These are my imports atop of my .spec.js file
import route from '../../../vendor/tightenco/ziggy/src/js/route.js';
import { Ziggy } from '../../../resources/js/ziggy.js';

And an example piece of code from the components  <script> tags
   mounted() {
        axios.get(route('clock_group.user.followings')).then(res => {
            this.followings = res.data;
        });
        axios.get(route('clock_group.members', this.clockGroupId)).then(res => {
            this.members = res.data;
        });
    },

But I keep getting the following error ReferenceError: route is not defined.
EDIT:
If this is out of scope, feel free to close the issue without a solution.

@aFluxx one option is to map it in your package.json file:
{  "jest": {      "moduleNameMapper": {          "^ziggy$": "<rootDir>/vendor/tightenco/ziggy/dist/js/route.js"      }  } }
Another option it to mock this file in jest (https://jestjs.io/docs/ru/manual-mocks). Just create a ziggy.js in mocks folder and export a function that will mock ziggy's one.

Gonna close this issue, but if anyone has more info feel free to reply again.


Update framer to 92

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

The latest version is 9285 https://updates.devmate.com/com.motif.framer.xml


Island Perimeter

Coverage remained the same at 100.0% when pulling 182dacfb876b0e46ec9aa178cf89b99a6f2985ac on island-perimeter into cc9186bdd0888ea1d37f202edc3172a960f2ee11 on master.


[Docker] Fix nginx disable ssl if no certs provided

This PR fixes the following issue:
https://github.com/Netflix/security_monkey/issues/637
When there is no ssl certs, the sed was failing because you can't change the inode of a mounted file. This is referenced in Docker's doc:

Note: Many tools used to edit files including vi and sed --in-place may result in an inode change. Since Docker v1.1.0, this will produce an error such as “sed: cannot rename ./sedKdJ9Dy: Device or resource busy”. In the case where you want to edit the mounted file, it is often easiest to instead mount the parent directory.

https://docs.docker.com/engine/tutorials/dockervolumes/#volume-labels

Coverage remained the same at 61.507% when pulling f028839239cc287b176316fd679f268fd758265c on jeyglk:fix/nginx-disable-https into 9a6c849d0472df293118ab2b90a8553979fb08d3 on Netflix:develop.

This allows the nginx container to start properly with HTTP - however the login fails due to the Docker env SESSION_COOKIE_SECURE=True, which can only work with HTTPS.

Oh hey very cool.

Coverage remained the same at 61.507% when pulling 958dd7289ca5dcc98d1ea52d10f8042eea2daff6 on jeyglk:fix/nginx-disable-https into 9a6c849d0472df293118ab2b90a8553979fb08d3 on Netflix:develop.

Fixed in #657


minor structure updates

[x] The alignment needs to be fixed when there are two segments
[ ] All tests needs to pass for ios9 , ios10

Codecov Report

Merging #3 into develop will increase coverage by 0.03%.
The diff coverage is 93.93%.

@@             Coverage Diff             @@
##           develop       #3      +/-   ##
===========================================
+ Coverage    81.31%   81.34%   +0.03%
===========================================
  Files            4        4
  Lines          396      402       +6
===========================================
+ Hits           322      327       +5
- Misses          74       75       +1

Impacted Files
Coverage Δ

Tests/HLSegmentedControlTests.swift
96.33% <100%> (ø)
:white_check_mark:

Source/HelperExtensions.swift
88.09% <100%> (-11.91%)
:x:

Source/HLSegmentedControl.swift
78.38% <92.85%> (+2.3%)
:white_check_mark:

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 ffc06c8...de039ea. Read the comment docs.