Added Rds discovery

Addresses https://github.com/openraven/magpie/issues/2
16:38:59.472 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Discovering RDS instances in eu-north-1
16:39:00.004 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Finished Rds instances discovery in eu-north-1
16:39:00.004 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Discovering RDS instances in ap-south-1
16:39:00.751 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Finished Rds instances discovery in ap-south-1
16:39:00.752 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Discovering RDS instances in eu-west-3
16:39:01.051 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Finished Rds instances discovery in eu-west-3
16:39:01.051 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Discovering RDS instances in eu-west-2
16:39:01.372 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Finished Rds instances discovery in eu-west-2
16:39:01.372 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Discovering RDS instances in eu-west-1
16:39:01.874 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Finished Rds instances discovery in eu-west-1
16:39:01.874 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Discovering RDS instances in ap-northeast-3
16:39:03.167 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Finished Rds instances discovery in ap-northeast-3
16:39:03.167 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Discovering RDS instances in ap-northeast-2
16:39:04.602 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Finished Rds instances discovery in ap-northeast-2
16:39:04.602 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Discovering RDS instances in ap-northeast-1
16:39:06.204 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Finished Rds instances discovery in ap-northeast-1
16:39:06.204 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Discovering RDS instances in sa-east-1
16:39:07.563 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Finished Rds instances discovery in sa-east-1
16:39:07.564 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Discovering RDS instances in ca-central-1
16:39:08.305 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Finished Rds instances discovery in ca-central-1
16:39:08.306 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Discovering RDS instances in ap-southeast-1
16:39:09.538 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Finished Rds instances discovery in ap-southeast-1
16:39:09.539 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Discovering RDS instances in ap-southeast-2
16:39:10.915 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Finished Rds instances discovery in ap-southeast-2
16:39:10.915 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Discovering RDS instances in eu-central-1
16:39:11.164 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Finished Rds instances discovery in eu-central-1
16:39:11.164 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Discovering RDS instances in us-east-1
16:39:11.991 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Getting tags for null
16:39:12.189 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Getting DbClusters for arn:aws:rds:us-east-1:321859670049:db:docdb-2020-06-12-17-05-48
16:39:12.547 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Getting DBSize for arn:aws:rds:us-east-1:321859670049:db:docdb-2020-06-12-17-05-48
16:39:13.433 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Finished Rds instances discovery in us-east-1
16:39:13.433 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Discovering RDS instances in us-east-2
{
  "session" : {
    "id" : "60bf8e84-b8bf-41d5-a508-a92a56e566da",
    "createdAt" : "2021-03-23T15:38:57.266465Z"
  },
  "pluginPath" : [ "magpie.aws.discovery:Rds" ],
  "contents" : {
    "region" : "us-east-1",
    "tags" : { },
    "DbClusters" : {
      "marker" : null,
      "dbClusters" : [ {
        "allocatedStorage" : 1,
        "availabilityZones" : [ "us-east-1f", "us-east-1b", "us-east-1d" ],
        "backupRetentionPeriod" : 1,
        "characterSetName" : null,
        "databaseName" : null,
        "dbClusterIdentifier" : "docdb-2020-06-12-17-05-48",
        "dbClusterParameterGroup" : "default.docdb3.6",
        "dbSubnetGroup" : "default",
        "status" : "available",
        "percentProgress" : null,
        "earliestRestorableTime" : "2021-03-22T00:14:22.655Z",
        "endpoint" : "docdb-2020-06-12-17-05-48.cluster-cziutqdayzm4.us-east-1.docdb.amazonaws.com",
        "readerEndpoint" : "docdb-2020-06-12-17-05-48.cluster-ro-cziutqdayzm4.us-east-1.docdb.amazonaws.com",
        "customEndpoints" : null,
        "multiAZ" : false,
        "engine" : "docdb",
        "engineVersion" : "3.6.0",
        "latestRestorableTime" : "2021-03-23T15:35:26.780Z",
        "port" : 27017,
        "masterUsername" : "dbadmin",
        "dbClusterOptionGroupMemberships" : null,
        "preferredBackupWindow" : "00:00-00:30",
        "preferredMaintenanceWindow" : "tue:03:34-tue:04:04",
        "replicationSourceIdentifier" : null,
        "readReplicaIdentifiers" : [ ],
        "dbClusterMembers" : [ {
          "dbInstanceIdentifier" : "docdb-2020-06-12-17-05-48",
          "isClusterWriter" : true,
          "dbClusterParameterGroupStatus" : "in-sync",
          "promotionTier" : 1
        } ],
        "vpcSecurityGroups" : [ {
          "vpcSecurityGroupId" : "sg-706c4359",
          "status" : "active"
        } ],
        "hostedZoneId" : "ZNKXH85TT8WVW",
        "storageEncrypted" : true,
        "kmsKeyId" : "arn:aws:kms:us-east-1:321859670049:key/f8722a45-e1f2-4cb5-a566-f3a4f51457ed",
        "dbClusterResourceId" : "cluster-PYVVEHLR7KATFL77TK4TT22PZI",
        "dbClusterArn" : "arn:aws:rds:us-east-1:321859670049:cluster:docdb-2020-06-12-17-05-48",
        "associatedRoles" : [ ],
        "iamDatabaseAuthenticationEnabled" : false,
        "cloneGroupId" : null,
        "clusterCreateTime" : "2020-06-12T17:06:36.365Z",
        "earliestBacktrackTime" : null,
        "backtrackWindow" : null,
        "backtrackConsumedChangeRecords" : null,
        "enabledCloudwatchLogsExports" : null,
        "capacity" : null,
        "engineMode" : "provisioned",
        "scalingConfigurationInfo" : null,
        "deletionProtection" : false,
        "httpEndpointEnabled" : false,
        "activityStreamMode" : null,
        "activityStreamStatus" : "stopped",
        "activityStreamKmsKeyId" : null,
        "activityStreamKinesisStreamName" : null,
        "copyTagsToSnapshot" : false,
        "crossAccountClone" : false,
        "domainMemberships" : [ ],
        "tagList" : [ ],
        "globalWriteForwardingStatus" : null,
        "globalWriteForwardingRequested" : null,
        "pendingModifiedValues" : null
      } ]
    },
    "size" : {
      "VolumeBytesUsed" : 49954816
    },
    "sizeInBytes" : 49954816,
    "maxSizeInBytes" :<PHONE_NUMBER>
  },
  "contentClass" : "com.fasterxml.jackson.databind.node.ObjectNode"
}
16:39:14.147 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Finished Rds instances discovery in us-east-2
16:39:14.148 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Discovering RDS instances in us-west-1
16:39:15.054 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Finished Rds instances discovery in us-west-1
16:39:15.054 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Discovering RDS instances in us-west-2
16:39:16.142 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Getting tags for null
16:39:16.455 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Getting DbClusters for arn:aws:rds:us-west-2:321859670049:db:neptunedb-instance-1
16:39:16.765 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Getting DBSize for arn:aws:rds:us-west-2:321859670049:db:neptunedb-instance-1
16:39:17.708 [pool-1-thread-1] WARN  i.o.m.p.a.d.AWSDiscoveryPlugin - neptunedb-instance-1 RDS instance is missing size metrics
16:39:17.708 [pool-1-thread-1] INFO  i.o.m.p.a.d.AWSDiscoveryPlugin - Finished Rds instances discovery in us-west-2
{
  "session" : {
    "id" : "60bf8e84-b8bf-41d5-a508-a92a56e566da",
    "createdAt" : "2021-03-23T15:38:57.266465Z"
  },
  "pluginPath" : [ "magpie.aws.discovery:Rds" ],
  "contents" : {
    "region" : "us-west-2",
    "tags" : { },
    "DbClusters" : {
      "marker" : null,
      "dbClusters" : [ {
        "allocatedStorage" : 1,
        "availabilityZones" : [ "us-west-2c", "us-west-2b", "us-west-2d" ],
        "backupRetentionPeriod" : 1,
        "characterSetName" : null,
        "databaseName" : null,
        "dbClusterIdentifier" : "neptunedb",
        "dbClusterParameterGroup" : "default.neptune1",
        "dbSubnetGroup" : "default-vpc-08cc5635964d1f41f",
        "status" : "available",
        "percentProgress" : null,
        "earliestRestorableTime" : "2021-03-22T10:44:28.247Z",
        "endpoint" : "neptunedb.cluster-csuzxmfx5ngc.us-west-2.neptune.amazonaws.com",
        "readerEndpoint" : "neptunedb.cluster-ro-csuzxmfx5ngc.us-west-2.neptune.amazonaws.com",
        "customEndpoints" : null,
        "multiAZ" : false,
        "engine" : "neptune",
        "engineVersion" : "<IP_ADDRESS>",
        "latestRestorableTime" : "2021-03-23T15:37:33.922Z",
        "port" : 8182,
        "masterUsername" : "admin",
        "dbClusterOptionGroupMemberships" : null,
        "preferredBackupWindow" : "10:35-11:05",
        "preferredMaintenanceWindow" : "mon:07:37-mon:08:07",
        "replicationSourceIdentifier" : null,
        "readReplicaIdentifiers" : [ ],
        "dbClusterMembers" : [ {
          "dbInstanceIdentifier" : "neptunedb-instance-1",
          "isClusterWriter" : true,
          "dbClusterParameterGroupStatus" : "in-sync",
          "promotionTier" : 1
        } ],
        "vpcSecurityGroups" : [ {
          "vpcSecurityGroupId" : "sg-04ee86fc5944dd022",
          "status" : "active"
        } ],
        "hostedZoneId" : "Z22EZDAJT6W257",
        "storageEncrypted" : true,
        "kmsKeyId" : "arn:aws:kms:us-west-2:321859670049:key/7142cbed-82a1-4625-92ad-28175217dd4d",
        "dbClusterResourceId" : "cluster-U2LDD263ABRJFAOP666YEIWTVU",
        "dbClusterArn" : "arn:aws:rds:us-west-2:321859670049:cluster:neptunedb",
        "associatedRoles" : [ ],
        "iamDatabaseAuthenticationEnabled" : false,
        "cloneGroupId" : null,
        "clusterCreateTime" : "2020-11-11T01:06:02.554Z",
        "earliestBacktrackTime" : null,
        "backtrackWindow" : null,
        "backtrackConsumedChangeRecords" : null,
        "enabledCloudwatchLogsExports" : null,
        "capacity" : null,
        "engineMode" : "provisioned",
        "scalingConfigurationInfo" : null,
        "deletionProtection" : false,
        "httpEndpointEnabled" : false,
        "activityStreamMode" : null,
        "activityStreamStatus" : "stopped",
        "activityStreamKmsKeyId" : null,
        "activityStreamKinesisStreamName" : null,
        "copyTagsToSnapshot" : false,
        "crossAccountClone" : false,
        "domainMemberships" : [ ],
        "tagList" : [ ],
        "globalWriteForwardingStatus" : null,
        "globalWriteForwardingRequested" : null,
        "pendingModifiedValues" : null
      } ]
    }
  },
  "contentClass" : "com.fasterxml.jackson.databind.node.ObjectNode"
}

@kickroot
What javadocs are needed here?

@PrzemyslawTusinski In retrospect I don't see an obvious need for Javadocs here.  There's no point in javadoc as busywork.


fix: BasePathStrategy no longer breaks the strategy chain

Fixes #877

:tada: This PR is included in version 8.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


webrtc-audio-processing: enable powerpc64le

Description of changes
This commit enables powerpc64le for webrtc-audio-processing, following
the pattern established by riscv64 support in f13cf5ef4779.
It is unfortunate that upstream doesn't use tooling that can figure
out endianness by querying the compiler (e.g. autoconf, cmake, meson,
etc all know how to do this).
Things done

Built on platform(s)

[X] x86_64-linux
[X] powerpc64le-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

@ofborg eval

Bummer that this causes so much rebuild.
If you prefer I can make the patch conditional on the hostPlatform and submit a patch to staging that removes the conditional.  Or I could just send the patch to staging (when it reopens).  This is not even remotely release-critical.

Okay, let's see if I remember how to change the base branch without mass-inviting every single nixpkgs reviewer.... ::crosses fingers::

I originally wrote this patch a few days ago, and earlier today I found out that Gentoo hard written a much more complete version of it as part of their qtwebengine support.
I've updated this PR to include the Gentoo version, and credited them at the top of the patch.

Thanks.  Staging is closed until 2022-May-15 so I will mark this as draft until then to keep it off of the maintainers' to-do list.

Btw, contributing now contains a guide describing the rebase process for retargeting 👍

Staging is not closed, see https://github.com/NixOS/nixpkgs/issues/165792

Staging is not closed, see #165792. Also, this looks quite safe to me.

You're right.  Sorry about that.  The other four staging PRs I have affect stdenv, so I had been thinking of the earlier 17-Apr deadline.

No worries :). Cross-compiled for aarch64-multiplatform as well, let's get this in.


Validate topic names

Catch the common case of someone sticking an invalid char in the topic
line.
Topic: catch1-
Reviewers: brian-k

Reviews in this chain:
└https://github.com/Skydio/revup/pull/102 Validate topic names

#
head
base
diff
date
summary

0
3e08fa1e
fa4e5a9a
diff
Apr 4 2:19 AM
1 file changed, 4 insertions(+)


Fix pushing / unshifting falsey elements into Queue

Attempting to push 0, null or '' would not actually alter the Queue, as they all evaluate to false in non-strict comparison

Coverage remained the same at 100.0% when pulling ac68799e7d290863c26082ad15646dc14d35a017 on jhermsmeier:fix-push into 82fdf947bae13a8e4ec7bcc608a52bdb022474ce on Salakar:master.

Woops, cheers for this again, will publish a new version tomorrow

Cool, thanks!

Published to npm 👍


[Feature Request] Related to "int" type in "Advanced Search" - w2grid

I am using asp.net core as "back end".
In "Advanced Search", it is a problem if special expressions used in int type (for example =,<,>) are in the url.

These expressions are used in the url for different purposes. For example, the use of "=" is different. As a result, errors occur.
"=" for example;

">" for example;

Of course this can be solved in "asp.net core". But the use of these expressions did not make sense to me. I leave it to your discretion.

alternative nomenclature;
"=" : equal
">" : greaterthan
"<" : lessthan
">=" : greaterthanorequal
"<=" : lessthanorequal

I do understand that certain characters are "bad" in the url, however I do not understand how to reproduce this issue.
Take this demo: http://w2ui.com/web/demos/#/grid/3
Searching for ID=123 results in the following request, with special characters being urlencoded:
http://w2ui.com/web/demos/data/list.json?request=%7B%22limit%22%3A100%2C%22offset%22%3A0%2C%22searchLogic%22%3A%22AND%22%2C%22search%22%3A%5B%7B%22field%22%3A%22recid%22%2C%22type%22%3A%22int%22%2C%22operator%22%3A%22%3D%22%2C%22value%22%3A123%7D%5D%7D

the decoded request looks like this:
{"limit":100,"offset":0,"searchLogic":"AND","search":[{"field":"recid","type":"int","operator":"=","value":1}]}

Please provide a minimal fiddle that demonstrates the issue.

yes your comment is correct. There is no problem with the url. The problem is on the server side. It treats the equals statement as if the parameter was assigned a value. but we do not value the parameter on the "client side" side.
So what can you ask? Server side is none of my business. Yes true. but the problem is that "between" is a "string" expression along with "=,>,<" these expressions are numeric. that is, the expression "between" needs to be made numerical or it is necessary to change the expressions.

I want to point out that you can definitely know. When we examine the big data grid of the library known with extjs, you will see that the naming is like this. It made more sense to me to send it to the server side with these expressions (equal, greater, lessthan) in the url. Thank you for your interest.

Example;
"operator" :"equal" or "operator" :"lessthan".


[Bug]:  cmdk this library was updated to  ^1.0.0 version, this version is having conflicts on next

Describe the bug
when i add the comand component and try use is having that error
Unhandled Runtime Error
TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
Call Stack
Function.from

A
(app-pages-browser)/node_modules/cmdk/dist/index.mjs (1:3976)
U
(app-pages-browser)/node_modules/cmdk/dist/index.mjs (1:2996)
eval
(app-pages-browser)/node_modules/cmdk/dist/index.mjs (1:1737)
eval
(app-pages-browser)/node_modules/cmdk/dist/index.mjs (1:10359)
Map.forEach

eval
(app-pages-browser)/node_modules/cmdk/dist/index.mjs (1:10359)
commitHookEffectListMount
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21035:0)
commitHookLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21145:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21343:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21421:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21510:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21421:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
Affected component/components
Command, Combobox
How to reproduce
You just must install this library cmdk on that version ^1.0.0 and try to integrate on Combo box component
Codesandbox/StackBlitz link
No response
Logs
Unhandled Runtime Error
TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))

Call Stack
Function.from
<anonymous>
A
(app-pages-browser)/node_modules/cmdk/dist/index.mjs (1:3976)
U
(app-pages-browser)/node_modules/cmdk/dist/index.mjs (1:2996)
eval
(app-pages-browser)/node_modules/cmdk/dist/index.mjs (1:1737)
eval
(app-pages-browser)/node_modules/cmdk/dist/index.mjs (1:10359)
Map.forEach
<anonymous>
eval
(app-pages-browser)/node_modules/cmdk/dist/index.mjs (1:10359)
commitHookEffectListMount
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21035:0)
commitHookLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21145:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21343:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21421:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21510:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21421:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)
recursivelyTraverseLayoutEffects
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (22860:0)
commitLayoutEffectOnFiber
(app-pages-browser)/node_modules/next/dist/compiled/react-dom/cjs/react-dom.development.js (21340:0)

System Info
chromebook 315, linux debian x64, chrome

Before submitting

[X] I've made research efforts and searched the documentation
[X] I've searched for existing issues

Hello, see #2944 for solution,
you essentially need to wrap CommandList around your CommandItems

@jhnguyen521 that mostly fixed it but now I cannot click the items, only keyboard nav


Automatically calculate AF alleles not present in vcf

When M2 tries to get the AF from a sites-only resource vcf, it needs to know what AF to use for an allele not contained in this vcf.  In principle this should be doable automatically, without requiring an explicit argument.

Issue moved to broadinstitute/gatk #2980 via ZenHub


Achievement System

Users want to see their progress/level up.
Implement a leveling system based on time spent studying.

One way to begin would be with daily user stats over currently employed accumulative style that shows total hours studied. A daily hour count will make levelling and leaderboard features neater looking too.


Avoid space replacement.

https://github.com/Synor/synor/blob/920bc81155795047be157f2fda320f753cd44e5d/packages/database-mongodb/src/utils/get-config.ts#L40
You no longer need to do such things, if you simply upgrade connection-string to the latest, which has it since v4.0.0, see #38.

Thanks @vitaly-t 😃

Thanks @vitaly-t 😃


cmd/go: spurious linefeed + backspace (\r\u0008) characters in go test -json output on Windows

On Windows 10 I see unexpected output in one of our tests. I do not see this extra output on Linux.
Perhaps there's some obscure bug in our code but we don't have anything that obviously emits such a strange combination as \r\u0008.

What version of Go are you using (go version)?

go version go1.17.1 windows/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env

set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=D:\go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=D:\go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.17.1
set GCCGO=gccgo
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=E:\git\go-sqlcmd\go.mod
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config

What did you do?
git clone https://github.com/microsoft/go-sqlcmd
set SQLCMDSERVER=mysqlservername
go test -json ./...

What did you expect to see?
{"Time":"2022-02-15T15:16:17.355648516Z","Action":"output","Package":"github.com/microsoft/go-sqlcmd/cmd/sqlcmd","Test":"TestQueryAndExit","Output":"--- PASS: TestQueryAndExit (0.71s)\n"}

What did you see instead?
{"Time":"2022-02-15T10:03:01.7125903-05:00","Action":"output","Package":"github.com/microsoft/go-sqlcmd/cmd/sqlcmd","Test":"TestQueryAndExit","Output":"\r\u0008\r\u0008\r\u0008--- PASS: TestQueryAndExit (0.62s)\n"}

\u0008 is BACKSPACE. I
However, at first glance this looks like a variation on #26325 / #33419. Probably something else in the test is writing to the test's stdout or stderr, and because the extra output doesn't occur at a newline boundary, cmd/test2json isn't able to parse past it.

Duplicate of #26325

FWIW it's not just in the json, the backspace characters are encoded in plain text when not using -json.

That's exactly what I'm saying. The testing package (and go test) does not inject those characters in the text itself, so they must be coming from some other package linked into the test binary.
You could try compiling the test and setting a debugger breakpoint to figure out what is writing those bytes. Perhaps they're coming from a subprocess (via os/exec) that has been set to forward its own stdout and/or stderr?


Animation Switch not compatible with react-transition-group v2

This is regarding - https://github.com/ReactTraining/react-router/issues/4351
So react-transition-group is superceeding react-addons-css-tranistion-group - https://github.com/reactjs/react-transition-group
Transition API v2 expects immediate children of <TransitionGroup> to be <CSSTransition>.
React Router <Switch> expects immediate children to be of type <Route>.
Does this mean it is not possible to do this with v2 transition api? I put some details/code here - https://github.com/reactjs/react-transition-group/issues/83

This is simple usage of v2 transition api:
import React, { Component } from 'react'
import { render } from 'react-dom'
import { TransitionGroup, CSSTransition } from 'react-transition-group'

import './index.css'

class App extends Component {
    state = {
        theme: 1
    }
    upTheme = () => this.setState(({ theme }) => ({ theme:theme+1 }));
    render() {
        const { theme } = this.state;
        return (
            <TransitionGroup className="rawr">
                <CSSTransition appear timeout={{appear:1000,enter:2000,exit:1000}} classNames="pagefade" key={theme.toString()}>
                    {theme}
                </CSSTransition>
            </TransitionGroup>
        );
    }
}

CSS:
.pagefade-enter, .pagefade-appear { opacity:0; }
.pagefade-enter.pagefade-enter-active,
.pagefade-appear.pagefade-appear-active { opacity:1; transition:opacity 1000ms; }
.pagefade-enter.pagefade-enter-active { transition-delay:1000ms; }
.pagefade-exit { opacity:1; }
.pagefade-exit.pagefade-exit-active { opacity:0; transition:opacity 1000ms; }

https://hackernoon.com/animated-page-transitions-with-react-router-4-reacttransitiongroup-and-animated-1ca17bd97a1a

Thanks Tim for the fast reply. Darn is it true that the way recommended in #4351 of wrapping the switch no longer works?

You need to make sure you're assigning key props to everything. That's the trick.

Not sure whether this is what you want, but here is how I use react-transition-group v2 with react-router v4:
<TransitionGroup>
    <CSSTransition key={this.props.location.key} timeout={500} classNames="fading-animation-transition" mountOnEnter={true} unmountOnExit={true}>
        <Switch key={this.props.location.key} location={this.props.location}>
            <Route path="/" exact component={Home} />
            <Route path="/blog" component={Blog} />
            <Route path="/albumn" component={Albumn} />
        </Switch>
    </CSSTransition>
</TransitionGroup>

Thank you so so much @Horizon-Blue !! That is exactly what I was trying to do. Thanks so much!

Thank you it works well !
There is still the case when you have sub routes, the transition will be triggered on every sub routes changes.

@hlehmann Yeah, that's because location.key keeps changing every time the route gets an update. To solve this problem, you can try using this.props.location.pathname instead of this.props.location.key, and using split() to get the prefix. e.g.
<TransitionGroup>
    <CSSTransition key={this.props.location.pathname.split('/')[1]} timeout={500} classNames="fading-animation-transition" mountOnEnter={true} unmountOnExit={true}>
        <Switch key={this.props.location.pathname.split('/')[1]} location={this.props.location}>
            <Route path="/" exact component={Home} />
            <Route path="/blog" component={Blog} />
            <Route path="/albumn" component={Albumn} />
        </Switch>
    </CSSTransition>
</TransitionGroup>

Thill will trigger the animation if I switch from /blog to /albumn, but will not trigger if I switch from /blog to /blog/post

Yes that's the solution I came out. But maybe a more integrated solution like a  could avoid this trick.

@Horizon-Blue It works, but trow this error. Don't know what's wrong.
removeClass.js:4 Uncaught TypeError: Cannot read property 'classList' of null
at removeClass (removeClass.js:4)
at CSSTransition.removeClasses (CSSTransition.js:267)
at Object.CSSTransition._this.onExit (CSSTransition.js:228)
at Transition.performExit (Transition.js:250)
at Transition.updateStatus (Transition.js:195)
at Transition.componentDidUpdate (Transition.js:159)
at measureLifeCyclePerf (ReactCompositeComponent.js:75)
at eval (ReactCompositeComponent.js:729)
at CallbackQueue.notifyAll (CallbackQueue.js:76)
at ReactReconcileTransaction.close (ReactReconcileTransaction.js:80)
at ReactReconcileTransaction.closeAll (Transaction.js:206)
at ReactReconcileTransaction.perform (Transaction.js:153)
at ReactUpdatesFlushTransaction.perform (Transaction.js:140)
at ReactUpdatesFlushTransaction.perform (ReactUpdates.js:89)
at Object.flushBatchedUpdates (ReactUpdates.js:172)
at ReactDefaultBatchingStrategyTransaction.closeAll (Transaction.js:206)
at ReactDefaultBatchingStrategyTransaction.perform (Transaction.js:153)
at Object.batchedUpdates (ReactDefaultBatchingStrategy.js:62)
at Object.batchedUpdates (ReactUpdates.js:97)
at dispatchEvent (ReactEventListener.js:147)

@DGizmo Seems like the problem is that ReactDOM.findDOMNode(this) returns null when your component switch to exit state.
As in facebook/react#4651, ReactDOM.findDOMNode will return null when the component is unmounted or the ref changes. Are you unmounting or re-referencing the DOM node inside your route?
I don't know enough about your setup to give a suggestion, but in my personal experience, I always found it very helpful to wrap everything inside CSSTransition with a div. This will not only ensure that CSSTransition always have a DOM node to work on (so findDOMNode won't return null), but also allow me to separate route transition and all the other animation within the route (otherwise, the animation will be applied to the outermost DOM node inside your route, which might not be what you want)
So here is how you can wrap your routes, notice the div with class WRAPPER:
 <TransitionGroup>
    <CSSTransition key={this.props.location.pathname.split('/')[1]} timeout={500} classNames="fadeTranslate" mountOnEnter={true} unmountOnExit={true}>

            <Switch location={this.props.location}>
                <Route path="/" exact component={Home} />
                <Route path="/blog" component={Blog} />
                <Route path="/albumn" component={Albumn} />
            </Switch>

    </CSSTransition>
</TransitionGroup>

And the classNames you give CSSTransition will be applied to this div:

Give it a try :). Let me know if the issue still persists.

Now it works without errors, thank you @Horizon-Blue! But because of the additional wrapper layer I had to rework my animations. Well, now it looks complex :)

Thank you very much @Horizon-Blue for your help on this. The article linked on hackernoon in the comment above - https://github.com/ReactTraining/react-router/issues/5279#issuecomment-310946205 - is not related to react-transition-group v2 - so I really appreciate you giving this help.

This was very helpful @Horizon-Blue. Any thoughts on how one might achieve different transitions for each route?

@andrewcroce I can't think of any elegant way to approach this... though one thing you can try is to define a custom map from pathname to corresponding css transition effect, e.g.:
const transitionMap = {
    blog: { classNames: 'fade-translate', timeout: 500 },
    albumn: { classNames: 'fade-in-out', timeout: 300 },
    account: { classNames: 'fade-translate', timeout: 550 },
};

and in your route definition:
render = () => {
    const current = this.props.location.pathname.split('/')[1];
    return (
        <TransitionGroup>
            <CSSTransition
                key={current}
                classNames="default-transition"
                timeout={300}
                {...transitionMap[current]}
                mountOnEnter={true}
                unmountOnExit={true}
            >

                    <Switch location={this.props.location}>
                        <Route path="/blog" component={Blog} />
                        <Route path="/albumn" component={Albumn} />
                        <Route path="/about" component={About} />
                        <Route path="/account" component={Account} />
                    </Switch>

            </CSSTransition>
        </TransitionGroup>
    );
};

If there is no special transition defined for a route, then default-transition will be used. Otherwiese,  {...transitionMap[current]} will override previously defined transitions.
This might not be the best way to solve the problem, but it should work... :P

Thanks so much @Horizon-Blue to help us brainstorm these ideas. I also have a need in the future for varied transitions per route, I will share my brainstorm here when I get to work on that. :)

Thanks @Horizon-Blue. This is a helpful idea.

Here is a page transition example with React Router 4 and React Transition Group 2, related issue.

Thanks for your help @Horizon-Blue .Now the page sliding animation is OK.
const RouterMap = () => (
  <Router>
    <Route render={({ location }) =>
      <TransitionGroup>
        <CSSTransition key={location.pathname.split('/')[1]} timeout={500} classNames="pageSlider" mountOnEnter={true} unmountOnExit={true}>
          <Switch location={location}>
            <Route path="/" exact component={ Index } />
            <Route path="/comments" component={ Comments } />
            <Route path="/opinions" component={ Opinions } />
            <Route path="/games" component={ Games } />
          </Switch>
        </CSSTransition>
      </TransitionGroup>
    } />
  </Router>
)

And the css:
.pageSlider-enter {
  transform: translate3d(100%, 0, 0);
}

.pageSlider-enter.pageSlider-enter-active {
  transform: translate3d(0, 0, 0);
  transition: all 600ms;
}
.pageSlider-exit {
  transform: translate3d(0, 0, 0);
}

.pageSlider-exit.pageSlider-exit-active {
  transform: translate3d(-100%, 0, 0);
  transition: all 600ms;
}

The animation is as bellow:

As you see,  the  animation that index page slide to the detail page is all right. But when I click the Back icon, I hope 'index page' comes out from left to right.
I know if I change the CSS as bellow, the page will come out from left to right:
.pageSlider-enter {
  transform: translate3d(-100%, 0, 0);
}
.pageSlider-exit.pageSlider-exit-active {
  transform: translate3d(100%, 0, 0);
  transition: all 600ms;
}

But how combine the two animations together?  Generally speaking, whenever user clicks the back icon, the animation should be from left to right. Do you have any idea? Many thanks.

Hi @jasonintju , you could try something similar to the method discussed in https://github.com/ReactTraining/react-router/issues/5279#issuecomment-316877263 to specify a different class for the root page.
e.g.
const isRoot = location.pathname === '/';

and then
<CSSTransition key={location.pathname.split('/')[1]} timeout={500} classNames={isRoot ? 'left-to-right' : 'right-to-left'} mountOnEnter={true} unmountOnExit={true}>

For my purpose I recently created a module based on react-css-transtion-replace here: https://github.com/LKay/react-transition-replace to animate between routes.
Then I just created a SwitchTransition component which handles route change just like regular Switch:
const SwitchTransition = withRouter(
    ({
        children,
        classNames,
        location,
        match : matchProps,
        transition : Transition,
        ...props
    }) => {
        let match, child;

        React.Children.forEach(children, (element) => {
            if (!React.isValidElement(element)) return;

            const { path: pathProp, exact, strict, from } = element.props;
            const path = pathProp || from;

            if (!match) {
                child = element;
                match = path ? matchPath(location.pathname, { path, exact, strict }) : matchProps;
            }
        });

        return (
            <TransitionReplace
                classNames={ classNames }
                timeout={ 500 }
                overflowHidden
            >
                { match ? (
                    <Transition
                        key={ match.path }
                        mountOnEnter
                        unmountOnExit
                        { ...props }
                    >
                        { cloneElement(child, { location, computedMatch: match }) }
                    </Transition>
                ) : null }
            </TransitionReplace>
        )
    }
);

And the example use:
<SwitchTransition
    transition={ SlideTransition }
    classNames="slide"
>
    <Route path="/step1" component={ Step1 }  />
    <Route path="/step2" component={ Step2 }  />
</SwitchTransition>

@Horizon-Blue  I have a problem! I do all the the thing above and the compiler is good. when I run in chrome, this console print like this:

and the animation do not work. the "exit" means the css hook "className-exit"?
this is the code:
<Route render={({location}) => {             console.log(location);             return
                 <Route exact path="/" render={() => (                     <Redirect to="/home"/>                 )}/>                 <TransitionGroup>                     <CSSTransition                         key={location.pathname.split('/')[1]}                         className="transitionWrapper"                         timeout={400}                     >                         <Switch location={location}>                             <Route exact path="/home" component={Home}/>                             <Route path="/inspiration" render={() =>
this is page2!
}/>                             <Route path="/mood" render={() =>
this is page3 mood!
}/>                         </Switch>                     </CSSTransition>                 </TransitionGroup>
         }}/>
and my css is:
:global(.transitionWrapper-enter) {     opacity: 0.1; } :global(.transitionWrapper-enter.transitionWrapper-enter-active){     opacity: 1;     transition: all .4s ease-out; } :global(.transitionWrapper-exit) {     opacity: 1; } :global(.transitionWrapper-exit.transitionWrapper-exit-active){     opacity: 0.01;     transition: all .4s ease-out; }

Rebound off of @LKay's code for ReactCSSTransitionGroup:
import React, { cloneElement } from 'react';
import { withRouter, matchPath, Route } from 'react-router-dom';
import ReactCSSTransitionGroup from 'react-addons-css-transition-group';

class _TransitionSwitch extends React.Component {
    render() {
        const {
            children,
            classNames,
            location,
            match: matchProps,
            transitionProps,
            ...props
        } = this.props;

        let match, child;

        React.Children.forEach(children, element => {
            if (!React.isValidElement(element)) return;

            const { path: pathProp, exact, strict, from } = element.props;
            const path = pathProp || from;

            if (!match) {
                child = element;
                match = path
                    ? matchPath(location.pathname, { path, exact, strict })
                    : matchProps;
            }
        });

        return (
            <Route
                render={({ location }) =>
                    <ReactCSSTransitionGroup {...transitionProps}>
                        {cloneElement(child, {
                            key: match.path || 'default',
                            location,
                            computedMatch: match
                        })}
                    </ReactCSSTransitionGroup>}
            />
        );
    }
}

export const TransitionSwitch = withRouter(_TransitionSwitch);

can we rewrite animated-transitions?

If you have some kind of authorization to protect a route and try to access it, a redirection warning is given. It works, but it's always giving that warning, am I doing something wrong?
<TransitionGroup>
  <CSSTransition key={location.key} classNames="fade" timeout={2000}>
    <Switch location={location}>
      <Route
        exact
        path="/"
        render={props =>
          !this.state.loggedIn ? (
            <PageOne />
          ) : (

              <Redirect to="/page2" />

          )
        }
      />
      <Route
        path="/page2"
        render={props =>
          this.state.loggedIn ? (
            <PageTwo />
          ) : (

              <Redirect to="/" />

          )
        }
      />
      <Route path="/page3" component={PageThree} />
    </Switch>
  </CSSTransition>
</TransitionGroup>

Thanks for this thread it helped me a lot to understand my problem.
@andrewcroce here is the way I do to handle multiple transitions (in my case there can be multiple leaving transitions on the same page depending on the next state):
On the changing page trigger I push a new location to the history with a state:
<Button
    onClick={() => {
        history.push({
            pathname: '/next',
            state: {transition: 'fade', duration: 1000}
        })
    }
/>
    Go to next page
</Button>

Then I declared a Transition component (to understand this code you need to read this issue that was the end of my search for a solution):
import React from 'react'
import { TransitionGroup, CSSTransition } from 'react-transition-group'

const childFactoryCreator = (props) => child => React.cloneElement(child, props)

export const Transitions = ({ transition, duration, pageKey, children, ...props }) => (
  <TransitionGroup
    childFactory={childFactoryCreator({ classNames: transition, timeout: duration })}
    {...props}
  >
    <CSSTransition
      key={pageKey}
      classNames={transition}
      timeout={duration}
    >
      { children }
    </CSSTransition>
  </TransitionGroup>
)

Then on the router component:
withRouter(({ location }) => (
    // default is no transition. override if location has a state
    <Transitions pageKey={location.pathname} transition='' duration={0} {...location.state}>
        <Switch location={location}>
            <Route path='/home' component={Home} />
            <Route path='/next' component={Next} />
        </Switch>
    </Transitions>
))

Hi. I followed the advice in this thread to get my Routes animating. I am having an issue with the <Redirect> component. Redirecting works, but I still get a warning in the console:

Warning: You tried to redirect to the same route you're currently on: "/"

The warning is visible in this code sandbox when you enter a bad route. Is there another way I should use the Redirect?


SSLApp - SSL_ERROR_SYSCALL

After change my server to SSL im getting this error:
$ curl https://stream.domain.com:9001 -iv
*   Trying x.x.x.x:9001...
* Connected to stream.domain.com (x.x.x.x) port 9001 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to stream.domain.com:9001
* Closing connection 0
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to stream.domain.com:9001

I noted that SSL options is not checking file. Even if file does not exists it does not send me any error.
const app = uWS.SSLApp();

app.ws("/*", {
  /* Options */
  idleTimeout: 32,
  maxBackpressure: 1024,
  maxPayloadLength: 16 * 1024 * 1024,
  commpression: 0,

  /* SSL Options */
  key_file_name: './tls/server.key',
  cert_file_name: './tls/server.crt',
  ca_file_name: './tls/server.full-ca.bundle',
  dh_params_file_name: './tls/dhparam.pem',

What am i doing wrong?

App.listen will fail

App.listen will fail

Tks for the quickly reply @uNetworkingAB! I found the error. I was setting SSL options in app.ws insted of app.
const app = uWS.SSLApp({
  /* SSL Options */
  key_file_name: './tls/server.key',
  cert_file_name: './tls/server.crt',
  ca_file_name: './tls/server.full-ca.bundle',
  dh_params_file_name: './tls/dhparam.pem',
});

app.ws("/*", {
  /* Options */
  idleTimeout: 32,
  maxBackpressure: 1024,
  maxPayloadLength: 16 * 1024 * 1024,
  commpression: 0,

Close it


Update feeds.xml

RestorePrivacy contains privacy and security news, original research, and in-depth resources. It is added to the 🔒 Infosec | Privacy section.

Thanks @glaucusec - I didn't know this source. From your experience, is it privacy focused or rather on the generic cybersecurity (including privacy) side?

Thanks @glaucusec - I didn't know this source. From your experience, is it privacy focused or rather on the generic cybersecurity (including privacy) side?

I don't think its just privacy focused. It inlcudes news related to infosec and also privacy. Some of the latest ones are RansomHouse Cyber Gang Claims Ipca Laboratories as Latest Victim, Verified Twitter Vulnerability Exposes Data from 5.4 Million Accounts. In depth researches on certain topics and very well written how-to-guides and also certain reviews on open-source apps and services. If you are just looking for news this is the link

Then it's probably a better fit for "Infosec | Generic News"? If that looks good to you, please feel free to add a new commit to this PR and I'll happily accept it. Please, feel free to add yourself to the README under the contributors/credits :-)

Okay

A new commit will be visible now. Thanks

LGTM


Resource Deployment UX Refresh

First pass at the resource deployment UX refresh. This PR changes the card style to that of azure portal ones.
Screenshots:
Light not selected:

Light selected:

Dark not selected:

dark selected

Resource dialog light

Resource dialog dark

Pull Request Test Coverage Report for Build 249281834

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.004%) to 39.094%

Totals

Change from base Build 249236629:
0.004%

Covered Lines:
19128

Relevant Lines:
44674

💛  - Coveralls


[web][a11y]: Testing tools for flutter web

Steps to reproduce
Are there any testing tools or extensions to test accessibility for flutter web applications?
Actual results
All tools fails because no DOM is generated.
Logs

Logs

<!-- Paste your logs here -->

Flutter Doctor output

Doctor output

<!-- Paste your output here -->

@niteshsh4rma
Check the documentation and see if it helps to answer your question.

@darshankawar not helpful as such, because it creates only semantics tree which helps only for Aria label things, but there are other metrics as well like Contrast Ratio, Text Zooming etc.

For contrast ratio, you can follow-up in this issue.
For text zooming, probably this is similar.
Closing this issue. If you disagree, write in comments and I'll reopen it.


Commenting on examples 2C and 2D

Continue from #968 with further examples.

This time just example 2C was done here:
https://github.com/input-output-hk/cardano-ledger-specs/compare/michal/example-2c


Charge Sector Projection

this implements a function to project an initial product state without charge conservation into a specific charge sector in order to initialize an MPS within that sector.

@jhauschild should we merge this for v0.99?

Thanks @jhauschild for the review! I incorporated the changes, except for the last unresolved comment (returning a list of sets of tuples) yet, as I'm testing this function anyways at the moment - I noticed that the function does not seem to be directly applicable for more than one type(s) of charges, i.e. for a SpinHalfFermionSite, I'll look into this.
We have a test for conservation of 'Sz' and for 'N', unfortunately due to renaming, this is continued on the branch cs_projection (https://github.com/LudwigZw/tenpy/tree/cs_projection). It seems that I can't change the source for this PR. Should we close this and @LudwigZw open another one?

Continue discussion in #363


Add support for styled('element') syntax

Description
MUI uses styled('element') instead of styled.element, but otherwise the functionality is almost the same.
It would be great if styled('element') syntax was supported.
import { styled } from '@mui/system';

const MyComponent = styled('div')({
  color: 'darkslategray',
  backgroundColor: 'aliceblue',
  padding: 8,
  borderRadius: 4,
});

I can see the above example works if I use import styled from 'styled-components'.
So it should be just a matter of detecting import { styled } from '@mui/system', right?

Yeah. We probably need to extend the default behavior of target.defineFunctions.
https://ota-meshi.github.io/eslint-plugin-css/settings/#target-definefunctions

one comment on the above - and related to styled components that i'd like to highlight
  padding: 8,
  borderRadius: 4,

the shorthand suggested by the OP (not "8px", but 8) syntax would be nice to support across the board (not just in styled components, but inline styling as well) - adding a rule that checks for properties that don't need "px" values and be able to warn or enforce that syntax.
Other systems like MUI that use object based css properties would be great to support as well. ie: sx & makeStyles

Not to forget other possible style definitions in MUI.
Breakpoints support
sx={{ margin: { xs: 1, sm: 1.5, md: 2 } }}

CSS properties shorthand names
sx={{ m: { xs: 1, sm: 1.5, md: 2 } }}

Nested selectors
sx={{ color: '#f00', ':hover': { color: '#0f0' } }}

Named colors
sx={{ color: 'primary.main' }}

Function style definitions
sx={({ theme}) => ({ margin: theme.spacing(1, 2) })}
// or
sx={{ margin: ({ theme}) => theme.spacing(1, 2) }}

Array definitions
sx={[ { m: 1 }, isError && { color: '#f00' }, ({ theme }) => ({ p: theme.spacing(1) }) ]}

Component theming
theme = {
    MuiButton: {
        styleOverrides: {
            root: {
                // all style definitions
            },
            secondary: ({theme}) => ({
                // all style definitions
            })
        }
    }
}

etc.
I'm wondering whether this particular ESLint plugin is capable of all of these and if there is maybe some other existing plugin that gives us all of these out of the box?
It would be even better if it supported browserslist, so that CSS would be checked against CSS feature support.
I'm using eslint-plugin-compat for Typescript feature support and I'd like to add CSS-in-JS support for MUI themed components, MUI styled components and sx prop compatibility checking.


feat: enable usage of chains without pre-existing deployments in axiom-std

let me figure out what's going on with the axiom-sdk first before merging

client SDK tests passed after running locally and rerunning the CI tests


Static linking of native resources

Hi there - very nice project you have here! :-)
I'm curious if the resource-config.json file you have means that the native dependencies referenced there are dynamically linked at runtime on the users machine, if they exist, and are not statically compiled into the final executable native image? It seems that to statically link the native dependencies is another step, and so I'm curious on what your thinking is here.
Thanks!

Here's an interesting thing:
I also believe that System.loadLibrary() in a native image will still require to dynamically load a shared library from a runtime environment (unless you do a special Feature step), whether the image is statically linked (native-image --static) or not.
However, for the epoll library (not 100% sure about tcnative though), fortunately netty has its own special logic to load a native library. As said earlier, the netty JAR already embeds the shared libraries in it, and there is a reason for that. When it doesn't load a library from a system, it opens the embedded .so file (assumed to be in META-INF/native) as a resource stream, creates a temp file, writes the contents of the .so file to it, and loads that temp file. And this logic still runs and works in the AOT-compiled native image.
For example, if you pass -Dio.netty.native.deleteLibAfterLoading=false when running a native image, you will be able to verify these temp files have been created. The operations can also be observed from the strace output.
$ strace -e open,openat target/com.example.driver -Dio.netty.native.deleteLibAfterLoading=false
...
openat(AT_FDCWD, "/home/chanseok/tmp/gitrepos/native-lib-test/libio_grpc_netty_shaded_netty_transport_native_epoll_x86_64.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
...
openat(AT_FDCWD, "/tmp/libio_grpc_netty_shaded_netty_transport_native_epoll_x86_641025032029681471214.so", O_RDWR|O_CREAT|O_EXCL, 0666) = 9
openat(AT_FDCWD, "/tmp/libio_grpc_netty_shaded_netty_transport_native_epoll_x86_641025032029681471214.so", O_WRONLY|O_CREAT|O_TRUNC, 0666) = 9
openat(AT_FDCWD, "/tmp/libio_grpc_netty_shaded_netty_transport_native_epoll_x86_641025032029681471214.so", O_RDONLY|O_CLOEXEC) = 9
...
openat(AT_FDCWD, "/home/chanseok/tmp/gitrepos/native-lib-test/libio_grpc_netty_shaded_netty_transport_native_epoll.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
...
(... the same sequence repeats for libio_grpc_netty_shaded_netty_tcnative ...)
...
$ ls /tmp/*epoll*.so
/tmp/libio_grpc_netty_shaded_netty_transport_native_epoll_x86_641025032029681471214.so

But the program fails to load the library, unfortunately. I saw the following error at one point while I was debugging, and the JNI version returned as -1 makes me think that it's failing inside JNI_OnLoad in the epoll native code for some reason. The log message also confirms that the native code was executed from the temp .so file.
Exception in thread "main" java.lang.UnsatisfiedLinkError: Unsupported JNI version 0xffffffff, required by /tmp/libio_grpc_netty_shaded_netty_transport_native_epoll_x86_6410688026722735409597.so

Nice discoveries @chanseokoh.

Exception in thread "main" java.lang.UnsatisfiedLinkError: Unsupported JNI version 0xffffffff, required by /tmp/libio_grpc_netty_shaded_netty_transport_native_epoll_x86_6410688026722735409597.so

Yeah I encountered this error too. I tested this code out today and made a mini-reproducer of the code snippet @JonathanGiles provided. I also dug up the old jni-config.json that we used to have in this repo.
Not sure if the discovery is useful, but I found out that if we add the jni-config.json to the reproducer, it gets the native library to load properly.
One can try with mvn package -Pnative and then ./com.example.driver in the project to compile with GraalVM and then run to verify. Probably for macOS you will need to modify the resource-config.json so it adds the shared libs you need.
May 12, 2021 6:42:20 PM com.example.Driver main
INFO: Epoll.isAvailable(): true
May 12, 2021 6:42:20 PM com.example.Driver main
INFO: OpenSsl.isAvailable(): true
May 12, 2021 6:42:21 PM com.example.Driver main
INFO: SSL Context is io.grpc.netty.shaded.io.netty.handler.ssl.OpenSslServerContext@70cdad0d, class is class io.grpc.netty.shaded.io.netty.handler.ssl.OpenSslServerContext

But yeah, now I am kind of curious what is the relationship between the jni-config.json and this stuff being done in the Features.
I'll give the Features a try next. Yeah I see, it kind of seems silly to add the shared lib as a resource in the image for it to be later dynamically linked rather than try to just statically link at build time.

I also believe that System.loadLibrary() in a native image will still require to dynamically load a shared library from a runtime environment (unless you do the special Feature step), whether the image is statically linked (native-image --static) or not.

I was curious what this means @chanseokoh; is dynamic linking unavoidable if you use System.loadLibrary? Or if you did the prework in the feature to statically link then does it work transparently? Hm, maybe we must try to find out...

The code I ended up with (with a number of different experiments clearly showing) is below. I've not cleaned it up as it gives some indication to the paths I went down. Note the first method is something I want to remove, when the resources are statically linked.

@JonathanGiles - I see. Does your solution already work without the duringSetup step (or was that just for illustration purposes)? Or were there still blockers that you had?
Also general tip: You will be able to see at a low-level what is going on in Netty if you turn your log levels to debug. This can be done by pasting this code at the top of your main method:
    Logger root = Logger.getLogger("");
    root.setLevel(Level.FINEST);
    root.addHandler(new StreamHandler(System.out, new SimpleFormatter()));

    for (Handler handler : root.getHandlers()) {
      handler.setLevel(Level.FINEST);
    }

With that logging hint, I can see on macos I am getting the following error reported:
Epoll.isAvailable(): false
May 13, 2021 4:04:22 PM io.netty.util.internal.NativeLibraryLoader loadLibrary
FINE: Successfully loaded the library netty_tcnative_osx_x86_64
May 13, 2021 4:04:22 PM io.netty.handler.ssl.OpenSsl <clinit>
FINE: Initialize netty-tcnative using engine: 'default'
May 13, 2021 4:04:22 PM io.netty.handler.ssl.OpenSsl <clinit>
FINE: Failed to initialize netty-tcnative; OpenSslEngine will be unavailable. See https://netty.io/wiki/forked-tomcat-native.html for more information.
java.lang.UnsatisfiedLinkError: io.netty.internal.tcnative.Library.aprMajorVersion()I [symbol: Java_io_netty_internal_tcnative_Library_aprMajorVersion or Java_io_netty_internal_tcnative_Library_aprMajorVersion__]
        at com.oracle.svm.jni.access.JNINativeLinkage.getOrFindEntryPoint(JNINativeLinkage.java:153)
        at com.oracle.svm.jni.JNIGeneratedMethodSupport.nativeCallAddress(JNIGeneratedMethodSupport.java:57)
        at io.netty.internal.tcnative.Library.aprMajorVersion(Library.java)
        at io.netty.internal.tcnative.Library.initialize(Library.java:149)
        at io.netty.handler.ssl.OpenSsl.initializeTcNative(OpenSsl.java:597)
        at io.netty.handler.ssl.OpenSsl.<clinit>(OpenSsl.java:153)
        at com.oracle.svm.core.classinitialization.ClassInitializationInfo.invokeClassInitializer(ClassInitializationInfo.java:375)
        at com.oracle.svm.core.classinitialization.ClassInitializationInfo.initialize(ClassInitializationInfo.java:295)

I was curious what this means; is dynamic linking unavoidable if you use System.loadLibrary? Or if you did the prework in the feature to statically link then does it work transparently? Hm, maybe we must try to find out...

With the right Feature setup, the System.loadLibrary call will know that the library you want is statically linked, and no dynamic libs will be required.

Yeah I see, it kind of seems silly to add the shared lib as a resource in the image for it to be later dynamically linked rather than try to just statically link at build time.

Statically linking libraries at compile-time: I believe theoretically this is doable, but there are also hurdles. In the end, it all boils down to using the linker ld, so the arguments below does not only apply to JNI in Java but to any language.
Java is portable, but these native libraries are not. This is why grpc-netty-shaded embeds platform-specific libraries, for Windows, Mac, Linux, x86_64, aarch64, etc.
$ ls -l grpc-netty-shaded/META-INF/native
total 9564
-rw-r----- 1 chanseok eng 2425856 Aug 21  2020 io_grpc_netty_shaded_netty_tcnative_windows_x86_64.dll
-rw-r----- 1 chanseok eng 1933284 Aug 21  2020 libio_grpc_netty_shaded_netty_tcnative_linux_aarch64.so
-rw-r----- 1 chanseok eng 2628280 Aug 21  2020 libio_grpc_netty_shaded_netty_tcnative_linux_x86_64.so
-rw-r----- 1 chanseok eng 2714596 Aug 21  2020 libio_grpc_netty_shaded_netty_tcnative_osx_x86_64.jnilib
-rw-r----- 1 chanseok eng   83075 Sep  8  2020 libio_grpc_netty_shaded_netty_transport_native_epoll_x86_64.so

Therefore, to make the Java Netty look like it's portable like magic, it needs a special logic to determine which library file to load based on the OS and arch (e.g., here and here).
Anyways, this mechanism is dynamic loading of shared libraries.
If you want to statically link libraries, then you need to link them at build-time, of course. That means, you will also need a special logic to choose the right binary based on the platform where you build. (It's not difficult to do so though. The code just needs to be slightly more sophisticated.)
However, to do static linking, you need static libraries (i.e., .a files, not .so). Unless someone periodically pre-compiles and releases static libraries, you'll have to build them from source (e.g., from these epoll .c files) yourself on some popular platforms at least.

With the right Feature setup, the System.loadLibrary call will know that the library you want is statically linked, and no dynamic libs will be required.

I confirm this too. This matches my observation.

With that logging hint, I can see on macos I am getting the following error reported:
Epoll.isAvailable(): false
May 13, 2021 4:04:22 PM io.netty.util.internal.NativeLibraryLoader loadLibrary
FINE: Successfully loaded the library netty_tcnative_osx_x86_64
May 13, 2021 4:04:22 PM io.netty.handler.ssl.OpenSsl <clinit>
FINE: Initialize netty-tcnative using engine: 'default'
May 13, 2021 4:04:22 PM io.netty.handler.ssl.OpenSsl <clinit>
FINE: Failed to initialize netty-tcnative; OpenSslEngine will be unavailable. See https://netty.io/wiki/forked-tomcat-native.html for more information.
java.lang.UnsatisfiedLinkError: io.netty.internal.tcnative.Library.aprMajorVersion()I [symbol: Java_io_netty_internal_tcnative_Library_aprMajorVersion or Java_io_netty_internal_tcnative_Library_aprMajorVersion__]
        at com.oracle.svm.jni.access.JNINativeLinkage.getOrFindEntryPoint(JNINativeLinkage.java:153)
        at com.oracle.svm.jni.JNIGeneratedMethodSupport.nativeCallAddress(JNIGeneratedMethodSupport.java:57)
        at io.netty.internal.tcnative.Library.aprMajorVersion(Library.java)
        at io.netty.internal.tcnative.Library.initialize(Library.java:149)
        at io.netty.handler.ssl.OpenSsl.initializeTcNative(OpenSsl.java:597)
        at io.netty.handler.ssl.OpenSsl.<clinit>(OpenSsl.java:153)
        at com.oracle.svm.core.classinitialization.ClassInitializationInfo.invokeClassInitializer(ClassInitializationInfo.java:375)
        at com.oracle.svm.core.classinitialization.ClassInitializationInfo.initialize(ClassInitializationInfo.java:295)

To fix these you'll have to manually iterate and add the classes found in the UnsatisfiedLinkError (like the io.netty.internal.tcnative.Library.aprMajorVersion) to the jni-config.json. And just keep trying rebuild/update until it works.
Based on what @chanseokoh said, I'm not sure if static linking is possible then. In the past I went down the rabbit hole of trying to get the native libraries to load at image build time (this can be done by reverting the native-image.properties and setting the OpenSsl and ssl-related classes to be initialized at build-time). But I was never able to get this to work; I'd always get some sort of seg-fault error at runtime.

Probably for macOS you will need to modify the resource-config.json so it adds the shared libs you need.

In my testing, the sample works without this particular file. Seems unnecessary.

In the past I went down the rabbit hole of trying to get the native libraries to load at image build time

I'm just speculating, but this might be relevant. But to me, it doesn't make much sense that dynamic loading of shared libraries can be accomplished at build time that makes actual calls work at runtime. (Does "loading" mean somehow embedding platform-specific function code into a native image? But that's no longer dynamic loading.)

Oh, one more thing. I've never used Mac, so didn't realize this before: epoll is not available on Mac. (The Stack Overflow answer is a bit old, but I think this is still the case.) @JonathanGiles so it's likely that you'll never get true from epoll.isAvailable() on your Mac? Anyways, one of the answers also seems to suggest that Netty has kqueue support instead of epoll for Mac.

There is a tcnative-kqueue that I do use, but you are right - I never expected to see epoll as true on my mac. I'm running out of things to try to get this to work - I suspect for now we just will end up falling back to using the JDK implementations (which are drastically slower) until a better solution is found in the graalVM / netty projects.

Hey there, I will look into how to enable this correctly at least for Linux.
Regarding time, I'll try to get to this, but because this does not block the functionality of the project it is a little bit lower priority for us right now as we try to expand our coverage fully for all GCP libraries.

Unrelatedly, I'm curious how you validate that your support for graalvm is complete. In other words, what testing strategies do you use to ensure that a native app will work completely the same as a Java version of the app?

Good question. We currently maintain a set of sample applications which exercise different GCP client libraries and will build and run these in our CI. This is our form of validation in the early stages (which you can see is limited by the code paths you can cover).
In the long run, we would like to build the unit tests of all the client libraries as a native image and validate the tests by running the test images. This work is a GA blocker for us and we're looking into how we could do this.

Closing as part of clean up


Extend Unit Testing

extends unit testing to improve test coverage

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
:information_source: You can also turn on project coverage checks and project coverage reporting on Pull Request comment
Thanks for integrating Codecov - We've got you covered :open_umbrella:


fix(Combobox): Fix flushSync being called inside a lifecycle method

Resolves #1730
Updates @tanstack/react-virtual
After some experimenting, it seems like this bug comes from the library we are using.
It only happens when you scroll in the list container, close and open again.
If you scroll back to the top before closing, the error does not happen.
The only fix I found is to scroll back to the top before closing.

Tested with the virtualized example in Storybook, looks to be working fine without errors 👌


Linux: background-opacity does not change actual window opacity

On Hyprland (wayland), when setting background opacity to anything below 1.0 (e.g. 0.4), it only makes the background brighter, but is not actually becoming transparent.
Kitty with 0.85 opacity above, Ghostty 1.0 opacity below:

Kitty with 0.85 opacity above, Ghostty 0.4 opacity below:

It should be apparent that my desktop background is visible behind Kitty but not behind ghostty.
I have no special window rules set in Hyprland for kitty nor for ghostty.

Likely duplicate of https://github.com/ghostty-org/ghostty/issues/3324

yes this is a duplicate of #3324, closing


[SMALLFIX] Small cleanups

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/17861/
Test PASSed.


Pull-Request: Enumerable

Enumerable
Project is using a module inside of a class. For this a class (MyList ) was created and a module (MyEnumerable). The module implement a subset of the functionality of Enumerable.
Files added:

main.rb
my_enumerable.rb
my_list.rb

Invalid Code Review Request ❌
Hi @Zven94 ,
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
You have submitted a project, that uses Gitflow. The project requires you to use GitHub flow. Kindly implement that.
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


Add Python 3.6 to testing

Python 3.6 tests pass but this PR is blocked by #702

I'm closing this PR because this project is now deprecated. Please see the release notes for v4.1.0 for more details.


Lager does not perform any group leader redirection from error_logger messages

By default, Erlang keeps an error_logger handler running for the sole purpose of redirecting messages between nodes:
https://github.com/erlang/otp/blob/OTP-17.0/lib/kernel/src/error_logger.erl#L367-L370
You can use gen_event:which_handlers(error_logger) to see there is always an error_logger handler in there. All other erlang handlers by default ignore messages coming from other nodes as they assume a redirection will happen, for example:
https://github.com/erlang/otp/blob/OTP-17.0/lib/stdlib/src/error_logger_tty_h.erl#L54-L55
However, lager by default removes all error_logger handlers:
https://github.com/basho/lager/blob/2.0.3/src/lager_app.erl#L109-L110
And the default logger installed by lager does not do any redirection based on the node group leader:
https://github.com/basho/lager/blob/2.0.3/src/error_logger_lager_h.erl#L148
This basically means that, after lager is installed, there is no node redirection happening. The main downside of this behaviour is that when using remote shells, the log messages are no longer redirected. The same with executing processes on remote nodes, where you may expect at the least the crash to be reported in the caller.
However, lager may have good reasons to remove this behaviour, however I could not find a rationale anywhere. So is it a bug or a feature? :D

In 3.x we have group leader support. Still probably need to fix up the emulator messages though.

Closing this for now, please reopen if we missed something.


Update Arriba to v2.4

Relevant discussion https://trello.com/c/l06WbXZX/1419-debug-sort-of-arriba-dragen-interaction-issues

@skanwal is this still planned for the next release?

@alexiswl -- yes, It's WIP, I'll push to GH next week.


Organization settings: Fix tippy design and hover delay for edit/delete in custom profile fields.

This PR fixes the issue #27816.
Explanation:
In the "Organization settings" under the tab "Custom profile fields" the edit and delete buttons have a hover-text displaying "edit" respectivley "delete". Before, it looked like the GIF "old version" below but this PR has updated the design to use the new tippy design, shown in GIF "New version dark mode" and "New version lilght theme" where LONG_HOVER_DELAY is used.
Fixes: #27816

Screenshots and screen captures:
Old version - before this PR

New version dark theme

New version lilght theme

Self-review checklist

[x] [Self-reviewed](https://zulip.readthedocs.io/en/latest/contributing/code-reviewing.html#how-to review-code) the changes for clarity and maintainability (variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see [commit discipline (https://zulip.readthedocs.io/en/latest/contributing/commit-discipline.html)).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

@sayamsamal please review this one when you get a chance; not a release goal, so please prioritize 8.0 tasks first.

Hi @sayamsamal! I noticed that you're the reviewer for this PR, and I was wondering if you could let me know when you might have some time to take a look at it. I appreciate your efforts, and I wish you all the best!

The implementation LGTM, and I don't have any comments on it.
If I could nitpick on one thing, it would be the fact that we are a bit more verbose with the intent on similar tooltips such as, "Edit topic", "Edit profile", "Edit bot" and "Edit stream name and description".
So let's name the tooltip as "Edit custom profile field".

I have left a comment about some redundant code in your commit, LGTM otherwise.

@angelicaferlin I have left a comment about some redundant code in your commit, LGTM otherwise.

@sayamsamal Thanks for the review!
I have now updated my PR as you suggested and let me know if anything else needs to be sorted.

@zulipbot claim

Merged after changing "Fix tippy" to "Use tippy" -- since previously we were using the HTML title attribute, not the Tippy tooltip library that this is now using. Being really precise in all communications around open source work is important to effective communication, so please be mindful of this sort of detail in your work. Thanks @angelicaferlin!


[WIP] Update react-scripts, remove unnecessary babel packages, audit fix

Part 1 of splitting up PR #656. Here I upgraded react-scripts and gh-pages and removed some babel-related dependencies and config files that were unnecessary (they don't show up in a brand-new CRA project and it seems to run fine without them). I'm going to check to make sure the build/preview still work and resolve any conflicts.

Also added ajv version 6 since npm kept complaining about an unmet peer dependency.

I forgot to mention, it also includes significant changes in package-lock.json from running npm audit fix (i.e. upgrading packages with security issues). I believe the upgrade to gh-pages was from that as well (it must've been the only one of our top-level dependencies that required an upgrade).

Other than that question, it looks good to me! Though I definitely have no idea what side effects could happen.


Always said the file is being used via update

VSCode Version: 1.32.2 (user setup)
OS Version: Windows 10 17134

Steps to Reproduce:

Close VS Code
Waiting for the updater

Does this issue occur when all extensions are disabled?: Yes
Here are the logs:
vscode-inno-updater-1552634929.log

I have the same issue (also had it yesterday with 1.32.2) -- resolved it yesterday by downloading the full package instead of using the built-in installer.  Resolved it today by doing a hard exit (file > exit) rather than hot exit [X].
Does this issue occur when all extensions are disabled?: Yes
1 __ vscode-inno-updater-1552642674.log
2 __ vscode-inno-updater-1552643235.log
Additional: while the built-in installer waiting to install (notification message to restart VSCode) or is running (trying to install), I lose a lot of interaction with my desktop: mouse still moves but can't click every time, windows become unresponsive (titlebar message "not responding"), keyboard doesn't type or types sporadically.  Might be coincidental, might not.  Takes a minute or two for full 100% responsiveness to return.  This is also only since yesterday.

Please switch to the system install, if the user install doesn't work for you: https://code.visualstudio.com/docs/?dv=win64

Wow.  Closing this issues as a "works for me"?  That's a low response.
As you didn't clarify which post you are responding to, I'm going to focus on mine.

I am using the system installer.  Which leads me to think you didn't look at my logs -- because "C:\Program Files\Microsoft VS Code" = system installer.

If there is a feature that suddenly, as of one minor-point-revision, stops working, maybe that's an issue with the feature; I've been using for over a year now with no issue.

"ERRO Failed to mark file for deletion: Access is denied"  <- why not actually tell us in the log WHICH file was locked, anyway?  That could help us figure out why a file is locked and what might be keeping it open.

Not sure why you felt it was necessary to add the links, just in case we weren't capable of finding them on the VSCode site ourselves.  Maybe you were being nice, or maybe this is just a cut-n-paste answer...


effector-triggered immune signalling

We found the term meaning
"effector-triggered immunity /immune signalling "
GO:0009870 defense response signaling pathway, resistance gene-dependent
Rename
effector-triggered immune signaling  (this is what the process is almost universally called)
exact synonym defense response signaling pathway, resistance gene-dependent
exact synonym effector-triggered immunity (this might be broad if these terms include the signalling + response)
exact R-protein mediated resistance signaling
ETI
current definition
A series of molecular signals that depends upon R-genes and is activated during defense response. PMID:11418339
This isn't great because it doesn't define "R-genes"
Suggest
A series of molecular signals generated when a microbe effector interacts with a  "NTR: resistance gene receptor" (/see issues/18031), leading to the activation, perpetuation, or inhibition of an effector-triggered signalling involved in innate immunity.
In plants, effector- triggered immunity  is a second line of defense occuring  after microbial "effector molecules" are translocated into the host in response to host PTI signaling.
Open questions:
a) When people talks about an "immune response" are they referring to the signalling, or the responses/outcomes of the signalling? or both
For signalling pathways we generally separate the signalling from the response, so I was wondering if we should always refer to these as "immunity" which seems to be what arises from the signaling or as"immune signalling pathway"
b) One definition we found says that pathogens are alerted to the effectors by the " associated damage caused by pathogenic toxins or effectors." We need to find if this is true?

known responses to "effector-triggered immune signalling"
hypersensitive response is the main response to ETI
another  process is
"cell wall toughening"
we propose to annotate this as "positive regulation of hypersensitive response"
Some  things are readouts for the hypersensitive response (a type of programmed cell death):
Readouts we came across so far

ion flux influx of calcium and hydrogen
DNA laddering
accumulation of RoS (reactive oxygen species burst) BUT this also occurs during PTI
lesions
transcription of ETI  pathogen resistance genes

Note that we think the wikipedia article is incorrect here. This is the response to PTI.
Ros triggers deposition of lignin and callose, crosslinking of cell wall proteins (cell wall toughening)

I edited the above for clarity
Q Does anyone know of any other outputs of "ETI" than Hypersensitive response ?
(not readouts, see above)
In other words, does ETI have any other outcomes than cell death?

Note that here we  envisage that mainly receptors will be annotated. We aren't sure what constitutes the downstream signalling pathway. We will look for papers on this.

GO:0052158
Ontology | biological_process
Term name | modulation by symbiont of host resistance gene-dependent defense response
also means the same thing as
GO:0009870 defense response signaling pathway, resistance gene-dependent
found with the synonym
modulation by organism of host gene-for-gene resistance
(gene-for-gene resistance is ETI)

Actually...
The molecular basis of necrosis-induced ETS involving necrotrophic fungi is still largely unknown, but has in several cases exhibited the hallmarks of programmed cell death (PCD); DNA laddering, heterochromatin condensation, cell shrinkage, callose deposition and an oxidative burst [9,16,17].
So callose deposition is also a hallmark of necrosis  effector-induced susceptibility and therefore presumably of  ETI.
I will revise above accordingly later.

I edited the above and added more readouts

other tickets cover the valid part of this. Mainly this term needs taxon restrictions. It isn't a great term, because its just describing a signalling pathway involved in the immune response  and there are probably better terms.
I will  check the annotations and assess in a new ticket.

replaced by
GO:0009870 defense response signaling pathway, resistance gene-dependent #18312


aux_operators in VQE required to be legacy operators?

Information

Qiskit Aqua version:
{'qiskit-terra': '0.14.1', 'qiskit-aer': '0.5.1', 'qiskit-ignis': '0.3.0', 'qiskit-ibmq-provider': '0.7.1', 'qiskit-aqua': '0.7.1', 'qiskit': '0.19.2'}

Python version:
Python 3.6.0

Operating system:
macOS 10.15.3

What is the current behavior?

I am using a VQE class in qiskit.aqua.algorithms.minimum_eigen_solvers.vqe.
VQE constructor accepts aux_operators, Optional[List[Optional[Union[OperatorBase, LegacyBaseOperator]]]].
If aux_operators is a list,  aux_operators setter calls to_opflow()  on each element of the list, regardless whether an element is OperatorBase or LegacyBaseOperator.
Since OperatorBase are already in Operator Flow mode, they don't have the to_opflow() method.
So if aux_operators contains elements that are OperatorBase, an error s thrown.

Steps to reproduce the problem

Initialize VQE, passing aux_operators as a non-empty list of operators, with at least one element as non-legacy.

What is the expected behavior?

Since OperatorBase is already in the Operator Flow form, these instances are fine as is in the aux_operators setter code.

Suggested solutions

Either change the setter code or add a trivial to_opflow() method to OperatorBase.

Hi @avkhadiev! That seems right, that case is missed. Would you want to make the fix yourself? 🙂

I think the setter code would be better off checking if the conversion was needed or not - having a trivial method BaseOperator method (to convert to itself as a no-op), given the intent is to remove the legacy operators later, seems the least desirable in my mind.


A Scaler interface for push based events

This is a RFC for adding a push based scaler interface that looks like this
type PushScaler interface {
	Scaler

	Start(ctx context.Context, active chan<- struct{})
}

scaler.go
Use-Case
For event sources that support a streaming client. This allows KEDA to connect as a client to an endpoint that can stream "isActive" requests per scaledObject.
Specification

[ ] active updates from the push scaler reset the cooldownPeriod. They just skip the pollingInterval.

[ ] provide a generic GRPC implementation

service ExternalPushScaler {
    rpc StreamScaleRequests(ScaledObjectRef) returns (stream activeResponse) {}
}

this can be used in the scaled object with
...
spec:
  triggers:
    - type: external-push
      metadata:
        address: grpc-server-address:port

Few remarks:
I have been back and forth on the signature or Start().
	Start(ctx context.Context, active chan<- struct{})
// vs
	Start(ctx context.Context, active func())

it seems that a callback is simpler for this scenario, but I haven't seen a lot of go code with callbacks like that, so I'm not sure if it's something that's avoided.

Looking good! I like this idea.
As for the signature, I'd prefer to use "the standard" go way, ie. with chan. But maybe you'll find other (better) ways during the implementation.

Do I still have some time to review this or am I too late?
(out on holiday)

sure, I still need to update the docs as well. Will wait for your review

It looks good to me but we’ll need good documentation that cover the use-case as it might not be clear what to expect or when to use it.
Maybe even document an example scenario.

Merged

Reopening as we don't have docs merged for it yet https://github.com/kedacore/keda-docs/pull/193


Pact feature to emit events

Thoughts on adding an event system to Pact?

Like Ethereum events
To aid interaction with the outside (off-chain) world. E.g. something off-chain could know to perform some action because a particular event (like a balance transfer) has occurred on-chain
Workflows like the accounts example would seem to benefit from this (see https://github.com/kadena-io/pact/blob/bf927fb2b3b6b08841555f59dd36054e6f864745/examples/accounts/accounts.pact#L118), where date, amount, and data are continually overwritten, emulating an in-contract mutable length-1 log. I think ideally log events would be emitted and not stored in contract data tables

/cc @slpopejoy @emilypi @joelburget

Additionally events would make it easier to test that Pact code is doing what we expect, which seems like a telling signal as well.

As for a mental model for how this would fit in with Pact execution -- consider tx environment as sort of providing "reader" functionality, and events as "writer"

If I had e.g. some infrastructure that I wanted to integrate with Pact, my personal ideal situation would be if I could easily things up to publish on-chain events that have occurred to Kafka.

@bts what would be massively helpful here is to document exactly what and how events are implemented in Ethereum and the appropriate way to make them real in Pact.
In the linked eth event doc, the first example is simply a function return value, "which is an intended use of events": for Pact this is already handled using the poll api etc. The actual use which I assume is what you want is "asynchronous triggers with data" which receives minimal treatment, and then pushes events as a storage gas hack (storage gas being a problem we intend to address directly). Worst of all, like so many Eth "technical docs", they really just point at opaque web3 techniques and give no indication how events are actually implemented: are they simply receipts in the receipt merkle tree? Are they a separate datastore (ie the "Log" output stack)?
We do have demand for events from clients so there is much interest in crafting a solution. However, note how RDBMS's have never offered a built-in solution for this, as there is no magic bullet for scalable event propagation.
One approach we are investigating for a client involves a consumable event pubsub architecture:

Populate a subscriber table keyed on event keys to a list of subscriber identities.
Populate an event table with keys identifying event of interest, with value being a list of event data.
Offer a polling function that drains the list, returning the new values.
Publish events by appending to the event list for a given key.

In any case, would appreciate any expertise or other light you can shed about how this is accomplished in Ethereum.

This is a good resource for the main idea: https://media.consensys.net/technical-introduction-to-events-and-logs-in-ethereum-a074d65dd61e
Basically contract execution produces events that live in a log alongside transactions in the blockchain.
A given ethereum node can have listeners for events registered via the web3 api, and when a block is mined into the chain, if there are any applicable listeners registered, they will be notified. Typically a frontend web3 application will register a listener before sending a transaction into the network to minimize a chance of losing the event.
Note implications around chain races and reorgs here -- just because a tx is mined into the chain for your node doesn't mean that will necessarily be the case for the network's chain over the long term.

Closing this for now. Many of the use cases for events seem to stem from Ethereum's approach, and now we have many alternate models to choose from:

capabilities can provide IOC (inversion of control) from the Ethereum model, where a third party can now directly/safely call a protected function on-behalf-of another user.
the main thing we don't have is the ability to stream responses for some event. But given that any stream can be replaced by repeated polling, it seems less urgent.


chore(main): release 0.1.0

:robot: I have created a release beep boop
0.1.0 (2023-04-03)
Documentation

Add CONTRIBUTING and LICENSE (9f7cd39)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/philips-software/SPDXMerge/releases/tag/v0.1.0 :sunflower:


Updates for Bricks CAR

Please let us know if that didn't come through, we're just trying to update one file:
projects/2.3.2-Tools/<IP_ADDRESS>-PROTEAS-YTUNE/<IP_ADDRESS>-Bricks.tex

@drhansj: Just to be clear, 11 files were modified or added with this PR.  The changes appear to be relevant to the PROTEAS-YTUNE project, but I want to make sure they are what you intend.  Your comment about wanting to change only the Bricks.tex file is why I am asking.


add queue

all PUTs (not POST or GET) will be synchronous, preventing people from getting into bad states because of server errors
form closing/unfocus/unselect doesn't happen until stuff saves, preventing weird in-between states
you can drag+drop multiple items as API calls are queued, but they'll retain their unsaved (blue) highlight until they save (and now they're guaranteed to save in order)
when the page loads, there's now a progress bar as well as the "Loading" message
when navigating away from the page, the queue will be checked (as well as any open forms) and an confirm will pop up if there are pending API calls

Coverage increased (+1.8%) to 76.033% when pulling 250de455431b9d0764b9e49197a8440e2d3b3323 on queue into 05888bdc7499b245f9d103594134acc6d4ecfa9f on master.

Coverage increased (+0.9%) to 75.176% when pulling a8109b1323a9d643c43c1c294d153004538755b6 on queue into 05888bdc7499b245f9d103594134acc6d4ecfa9f on master.