"libtoolize not found" - linux dependency

have hit this error a few times :
make: Leaving directory '/home/mix/projects/SSBC/beaker/app/node_modules/sqlite3/build'

><EMAIL_ADDRESS>install /home/mix/projects/SSBC/beaker/app/node_modules/sodium-prebuilt
> prebuild --install --preinstall make

./autogen.sh: 13: ./autogen.sh: libtoolize: not found
Makefile:8: recipe for target 'configure' failed
make: *** [configure] Error 127
prebuild ERR! build Error: make  failed with exit code 2
prebuild ERR! build     at Object.exports.spawnFailed (/home/mix/projects/SSBC/beaker/app/node_modules/prebuild/error.js:31:10)
prebuild ERR! build     at ChildProcess.<anonymous> (/home/mix/projects/SSBC/beaker/app/node_modules/prebuild/util.js:113:14)
prebuild ERR! build     at emitTwo (events.js:106:13)
prebuild ERR! build     at ChildProcess.emit (events.js:191:7)
prebuild ERR! build     at Process.ChildProcess._handle.onexit (internal/child_process.js:204:12

have run  burnthemall
I think there's a dependency required : libtool in ubuntu
sorry to following is thorough and a bit tedious.

sudo apt-get install libtool
npm run burnthemall

lead to:
libtoolize:   error: One of these is required:
libtoolize:                 gm4 gnum4 m4

ran:
sudo apt-get install m4
npm run burnthemall

Got:
autogen.sh: aclocal: not found

ran:
sudo apt-get install automake
npm run burnthemall

(I thought that was already installed)
works

Thanks. I'll update the docs to mention these.

It could just be automake...
On Mon, 15 Aug 2016 07:10 Paul Frazee<EMAIL_ADDRESS>wrote:

Closed #54 https://github.com/pfrazee/beaker/issues/54.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pfrazee/beaker/issues/54#event-755109343, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACitnjgt8YoXV11-deV54i5c6YurMPh2ks5qf2gvgaJpZM4JjqDf
.


[stable/mongodb-replicaset] first pod stuck in status  Init:2/3

BUG REPORT
Version of Helm and Kubernetes:
kubernetes 1.12.1
helm 2.9.1
Which chart:
[stable/mongodb-replicaset]
What happened:
Mongo not started. First pod stuck in status Init:2/3
no logs pod/m-mongodb-replicaset-0 -c bootstrap
no file /work-dir/log.txt
NAME                         READY   STATUS     RESTARTS   AGE
pod/m-mongodb-replicaset-0   0/1     Init:2/3   0          2m13s

How to reproduce it (as minimally and precisely as possible):
values.yaml
replicas: 1

persistentVolume:
  enabled: true
  storageClass: "kube"
  accessModes:
    - ReadWriteOnce
  size: 1Gi
  annotations: {}

helm upgrade --install m stable/mongodb-replicaset --namespace mongo --values v.yml

/assign @unguiculus

i try with replicas:3 - pod steel freeze in state init:2/3

pv is ceph rbd via kube standart plugin

pod describe
Events:
  Type    Reason                  Age   From                             Message
  ----    ------                  ----  ----                             -------
  Normal  Scheduled               60s   default-scheduler                Successfully assigned mongo/m-mongodb-replicaset-0 to ingress-1
  Normal  SuccessfulAttachVolume  60s   attachdetach-controller          AttachVolume.Attach succeeded for volume "pvc-beb9840a-d2dc-11e8-a873-fa163e0a375b"
  Normal  Pulling                 43s   kubelet, ingress-1  pulling image "busybox"
  Normal  Pulled                  40s   kubelet, ingress-1  Successfully pulled image "busybox"
  Normal  Created                 40s   kubelet, ingress-1  Created container
  Normal  Started                 40s   kubelet, ingress-1  Started container
  Normal  Pulling                 40s   kubelet, ingress-1 pulling image "k8s.gcr.io/mongodb-install:0.6"
  Normal  Pulled                  38s   kubelet, ingress-1  Successfully pulled image "k8s.gcr.io/mongodb-install:0.6"
  Normal  Created                 37s   kubelet, ingress-1  Created container
  Normal  Started                 37s   kubelet, ingress-1  Started container
  Normal  Pulling                 36s   kubelet, ingress-1  pulling image "mongo:3.6"
  Normal  Pulled                  34s   kubelet, ingress-1  Successfully pulled image "mongo:3.6"
  Normal  Created                 34s   kubelet, ingress-1  Created container
  Normal  Started                 34s   kubelet, ingress-1  Started container

What chart version? 3.6.1 has a number of fixes around bootstrap container. Did 2nd init container finish? It's not clear if bootstrap container is running or install container from what you've posted.

Last chart version: 3.6.1
yes. 2nd init container finished, 3rd init - bootstraup launched and running without any logs
my cluster domain is not default cluster.local, is set to test.local

Perhaps, exec into bootstrap and cat /etc/resolv.conf. There should be a line like search default.svc.cluster.local svc.cluster.local cluster.local firescope.int and peer-finder will attempt to use svc.* to guess domain. Also, just try it with cluster.local to see if it works.

k exec -it m-mongodb-replicaset-0 -c bootstrap sh
$ cat /etc/resolv.conf
nameserver <IP_ADDRESS>
search mongo.svc.s01.local svc.s01.local s01.local
options ndots:5

i try install ANOTHER cluster with cluster domain cluster.local
and mongodb started up
NAME                         READY   STATUS    RESTARTS   AGE
pod/m-mongodb-replicaset-0   1/1     Running   0          2m46s
pod/m-mongodb-replicaset-1   1/1     Running   0          113s
pod/m-mongodb-replicaset-2   1/1     Running   0          77s

NAME                           TYPE        CLUSTER-IP   EXTERNAL-IP   PORT(S)     AGE
service/m-mongodb-replicaset   ClusterIP   None         <none>        27017/TCP   2m46s

NAME                                    DESIRED   CURRENT   AGE
statefulset.apps/m-mongodb-replicaset   3         3         2m46s

log from bootstrap container
logs pod/m-mongodb-replicaset-0 -c bootstrap
2018/10/20 10:52:03 Peer list updated
was []
now [m-mongodb-replicaset-0.m-mongodb-replicaset.mongo.svc.cluster.local]
2018/10/20 10:52:03 execing: /init/on-start.sh with stdin: m-mongodb-replicaset-0.m-mongodb-replicaset.mongo.svc.cluster.local
2018/10/20 10:52:18 [2018-10-20T10:52:03,176090718+00:00] [on-start.sh] Bootstrapping MongoDB replica set member: m-mongodb-replicaset-0
[2018-10-20T10:52:03,177645782+00:00] [on-start.sh] Reading standard input...
[2018-10-20T10:52:03,179389683+00:00] [on-start.sh] Skipping init mongod standalone script
[2018-10-20T10:52:03,180928467+00:00] [on-start.sh] Peers: m-mongodb-replicaset-0.m-mongodb-replicaset.mongo.svc.cluster.local
[2018-10-20T10:52:03,182452870+00:00] [on-start.sh] Starting a MongoDB replica
[2018-10-20T10:52:03,184631452+00:00] [on-start.sh] Waiting for MongoDB to be ready...
2018-10-20T10:52:03.223+0000 I CONTROL  [initandlisten] MongoDB starting : pid=30 port=27017 dbpath=/data/db 64-bit host=m-mongodb-replicaset-0
2018-10-20T10:52:03.223+0000 I CONTROL  [initandlisten] db version v3.6.8
2018-10-20T10:52:03.223+0000 I CONTROL  [initandlisten] git version: 6bc9ed599c3fa164703346a22bad17e33fa913e4
2018-10-20T10:52:03.223+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.1.0f  25 May 2017
2018-10-20T10:52:03.223+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2018-10-20T10:52:03.223+0000 I CONTROL  [initandlisten] modules: none
2018-10-20T10:52:03.223+0000 I CONTROL  [initandlisten] build environment:
2018-10-20T10:52:03.223+0000 I CONTROL  [initandlisten]     distmod: debian92
2018-10-20T10:52:03.223+0000 I CONTROL  [initandlisten]     distarch: x86_64
2018-10-20T10:52:03.223+0000 I CONTROL  [initandlisten]     target_arch: x86_64
2018-10-20T10:52:03.223+0000 I CONTROL  [initandlisten] options: { config: "/data/configdb/mongod.conf", net: { bindIp: "<IP_ADDRESS>", port: 27017 }, replication: { replSet: "rs0" }, storage: { dbPath: "/data/db" } }
2018-10-20T10:52:03.224+0000 I STORAGE  [initandlisten]
2018-10-20T10:52:03.224+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
2018-10-20T10:52:03.224+0000 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
2018-10-20T10:52:03.224+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=1460M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),cache_cursors=false,compatibility=(release="3.0",require_max="3.0"),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
exception: connect failed
[2018-10-20T10:52:03,301617802+00:00] [on-start.sh] Retrying db.adminCommand('ping').ok
2018-10-20T10:52:03.828+0000 I STORAGE  [initandlisten] WiredTiger message [1540032723:828471][30:0x7f99a954d580], txn-recover: Set global recovery timestamp: 0
2018-10-20T10:52:03.870+0000 I CONTROL  [initandlisten]
2018-10-20T10:52:03.870+0000 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
2018-10-20T10:52:03.870+0000 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
2018-10-20T10:52:03.870+0000 I CONTROL  [initandlisten]
2018-10-20T10:52:03.870+0000 I CONTROL  [initandlisten]
2018-10-20T10:52:03.870+0000 I CONTROL  [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/enabled is 'always'.
2018-10-20T10:52:03.870+0000 I CONTROL  [initandlisten] **        We suggest setting it to 'never'
2018-10-20T10:52:03.870+0000 I CONTROL  [initandlisten]
2018-10-20T10:52:03.871+0000 I STORAGE  [initandlisten] createCollection: local.startup_log with no UUID.
2018-10-20T10:52:03.918+0000 I FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory '/data/db/diagnostic.data'
2018-10-20T10:52:03.918+0000 I STORAGE  [initandlisten] createCollection: local.me with no UUID.
2018-10-20T10:52:04.000+0000 W REPL     [ftdc] Rollback ID is not initialized yet.
2018-10-20T10:52:04.075+0000 I STORAGE  [initandlisten] createCollection: local.replset.minvalid with no UUID.
2018-10-20T10:52:04.095+0000 I REPL     [initandlisten] Did not find local voted for document at startup.
2018-10-20T10:52:04.095+0000 I REPL     [initandlisten] Did not find local Rollback ID document at startup. Creating one.
2018-10-20T10:52:04.095+0000 I STORAGE  [initandlisten] createCollection: local.system.rollback.id with no UUID.
2018-10-20T10:52:04.113+0000 I REPL     [initandlisten] Initialized the rollback ID to 1
2018-10-20T10:52:04.113+0000 I REPL     [initandlisten] Did not find local replica set configuration document at startup;  NoMatchingDocument: Did not find replica set configuration document in local.system.replset
2018-10-20T10:52:04.113+0000 I NETWORK  [initandlisten] waiting for connections on port 27017
2018-10-20T10:52:04.113+0000 I CONTROL  [LogicalSessionCacheReap] Sessions collection is not set up; waiting until next sessions reap interval: Can not create config.system.sessions collection
2018-10-20T10:52:04.362+0000 I NETWORK  [listener] connection accepted from <IP_ADDRESS>:46100 #1 (1 connection now open)
2018-10-20T10:52:04.363+0000 I NETWORK  [conn1] received client metadata from <IP_ADDRESS>:46100 conn1: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "3.6.8" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 9 (stretch)"", architecture: "x86_64", version: "Kernel 4.18.15-1.el7.elrepo.x86_64" } }
2018-10-20T10:52:04.366+0000 I NETWORK  [conn1] end connection <IP_ADDRESS>:46100 (0 connections now open)
[2018-10-20T10:52:04,367056302+00:00] [on-start.sh] Initialized.
[2018-10-20T10:52:04,368731429+00:00] [on-start.sh] Checking if m-mongodb-replicaset-0.m-mongodb-replicaset.mongo.svc.cluster.local is primary
2018-10-20T10:52:04.409+0000 I NETWORK  [listener] connection accepted from <IP_ADDRESS>:35492 #2 (1 connection now open)
2018-10-20T10:52:04.409+0000 I NETWORK  [conn2] received client metadata from <IP_ADDRESS>:35492 conn2: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "3.6.8" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 9 (stretch)"", architecture: "x86_64", version: "Kernel 4.18.15-1.el7.elrepo.x86_64" } }
2018-10-20T10:52:04.412+0000 I NETWORK  [conn2] end connection <IP_ADDRESS>:35492 (0 connections now open)
2018-10-20T10:52:04.451+0000 I NETWORK  [listener] connection accepted from <IP_ADDRESS>:46104 #3 (1 connection now open)
2018-10-20T10:52:04.452+0000 I NETWORK  [conn3] received client metadata from <IP_ADDRESS>:46104 conn3: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "3.6.8" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 9 (stretch)"", architecture: "x86_64", version: "Kernel 4.18.15-1.el7.elrepo.x86_64" } }
        "errmsg" : "no replset config has been received",
2018-10-20T10:52:04.455+0000 I NETWORK  [conn3] end connection <IP_ADDRESS>:46104 (0 connections now open)
[2018-10-20T10:52:04,456111783+00:00] [on-start.sh] Initiating a new replica set with myself (m-mongodb-replicaset-0.m-mongodb-replicaset.mongo.svc.cluster.local)...
MongoDB shell version v3.6.8
connecting to: mongodb://<IP_ADDRESS>:27017
2018-10-20T10:52:04.503+0000 I NETWORK  [listener] connection accepted from <IP_ADDRESS>:46106 #4 (1 connection now open)
2018-10-20T10:52:04.503+0000 I NETWORK  [conn4] received client metadata from <IP_ADDRESS>:46106 conn4: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "3.6.8" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 9 (stretch)"", architecture: "x86_64", version: "Kernel 4.18.15-1.el7.elrepo.x86_64" } }
MongoDB server version: 3.6.8
2018-10-20T10:52:04.504+0000 I REPL     [conn4] replSetInitiate admin command received from client
2018-10-20T10:52:04.504+0000 I REPL     [conn4] replSetInitiate config object with 1 members parses ok
2018-10-20T10:52:04.504+0000 I REPL     [conn4] ******
2018-10-20T10:52:04.504+0000 I REPL     [conn4] creating replication oplog of size: 990MB...
2018-10-20T10:52:04.504+0000 I STORAGE  [conn4] createCollection: local.oplog.rs with no UUID.
2018-10-20T10:52:04.516+0000 I STORAGE  [conn4] Starting WiredTigerRecordStoreThread local.oplog.rs
2018-10-20T10:52:04.516+0000 I STORAGE  [conn4] The size storer reports that the oplog contains 0 records totaling to 0 bytes
2018-10-20T10:52:04.516+0000 I STORAGE  [conn4] Scanning the oplog to determine where to place markers for truncation
2018-10-20T10:52:04.560+0000 I REPL     [conn4] ******
2018-10-20T10:52:04.560+0000 I STORAGE  [conn4] createCollection: local.system.replset with no UUID.
2018-10-20T10:52:04.600+0000 I COMMAND  [conn4] Assigning UUID 30b7ba2c-04a2-4dc0-8205-2c8c8e319cc3 to collection local.system.rollback.id
2018-10-20T10:52:04.601+0000 I COMMAND  [conn4] Assigning UUID c3e78307-9841-4b4e-90b1-6e31967d2bc2 to collection local.system.replset
2018-10-20T10:52:04.601+0000 I COMMAND  [conn4] Assigning UUID 199635e2-4445-490f-a480-68408eb44b2f to collection local.me
2018-10-20T10:52:04.601+0000 I COMMAND  [conn4] Assigning UUID 1327f11a-6bf8-4d9c-92a2-152592ced459 to collection local.startup_log
2018-10-20T10:52:04.601+0000 I COMMAND  [conn4] Assigning UUID 1dbd6002-ec0d-48d6-bcbb-daf7a96a7f14 to collection local.replset.minvalid
2018-10-20T10:52:04.601+0000 I COMMAND  [conn4] Assigning UUID d3044e34-5859-4678-8471-25afb8464da2 to collection local.oplog.rs
2018-10-20T10:52:04.601+0000 I STORAGE  [conn4] createCollection: admin.system.version with provided UUID: bc902f3e-bb01-486a-a2e5-16e0ff504915
2018-10-20T10:52:04.644+0000 I COMMAND  [conn4] setting featureCompatibilityVersion to 3.6
2018-10-20T10:52:04.644+0000 I NETWORK  [conn4] Skip closing connection for connection # 4
2018-10-20T10:52:04.644+0000 I REPL     [conn4] New replica set config in use: { _id: "rs0", version: 1, protocolVersion: 1, members: [ { _id: 0, host: "m-mongodb-replicaset-0.m-mongodb-replicaset.mongo.svc.cluster.local:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 } ], settings: { chainingAllowed: true, heartbeatIntervalMillis: 2000, heartbeatTimeoutSecs: 10, electionTimeoutMillis: 10000, catchUpTimeoutMillis: -1, catchUpTakeoverDelayMillis: 30000, getLastErrorModes: {}, getLastErrorDefaults: { w: 1, wtimeout: 0 }, replicaSetId: ObjectId('5bcb08d429390fdc9287a396') } }
2018-10-20T10:52:04.644+0000 I REPL     [conn4] This node is m-mongodb-replicaset-0.m-mongodb-replicaset.mongo.svc.cluster.local:27017 in the config
2018-10-20T10:52:04.644+0000 I REPL     [conn4] transition to STARTUP2 from STARTUP
2018-10-20T10:52:04.644+0000 I REPL     [conn4] Starting replication storage threads
2018-10-20T10:52:04.645+0000 I REPL     [conn4] transition to RECOVERING from STARTUP2
2018-10-20T10:52:04.645+0000 I REPL     [conn4] Starting replication fetcher thread
2018-10-20T10:52:04.645+0000 I REPL     [conn4] Starting replication applier thread
2018-10-20T10:52:04.645+0000 I REPL     [conn4] Starting replication reporter thread
2018-10-20T10:52:04.645+0000 I COMMAND  [conn4] command local.oplog.rs appName: "MongoDB Shell" command: replSetInitiate { replSetInitiate: { _id: "rs0", members: [ { _id: 0.0, host: "m-mongodb-replicaset-0.m-mongodb-replicaset.mongo.svc.cluster.local" } ] }, $db: "admin" } numYields:0 reslen:147 locks:{ Global: { acquireCount: { r: 32, w: 20, W: 2 }, acquireWaitCount: { W: 1 }, timeAcquiringMicros: { W: 85 } }, Database: { acquireCount: { r: 4, w: 4, W: 16 } }, Collection: { acquireCount: { r: 2, w: 2 } }, oplog: { acquireCount: { r: 2, w: 3 } } } protocol:op_msg 140ms
{
        "ok" : 1,
        "operationTime" : Timestamp(1540032724, 1),
        "$clusterTime" : {
                "clusterTime" : Timestamp(1540032724, 1),
                "signature" : {
                        "hash" : BinData(0,"AAAAAAAAAAAAAAAAAAAAAAAAAAA="),
                        "keyId" : NumberLong(0)
                }
        }
}
2018-10-20T10:52:04.648+0000 I NETWORK  [conn4] end connection <IP_ADDRESS>:46106 (0 connections now open)
2018-10-20T10:52:04.649+0000 I REPL     [rsSync] transition to SECONDARY from RECOVERING
2018-10-20T10:52:04.649+0000 I REPL     [rsSync] conducting a dry run election to see if we could be elected. current term: 0
2018-10-20T10:52:04.649+0000 I REPL     [replexec-0] dry election run succeeded, running for election in term 1
2018-10-20T10:52:04.649+0000 I STORAGE  [replexec-0] createCollection: local.replset.election with generated UUID: 937c767a-10f8-4c98-85e0-a95351d05ab2
2018-10-20T10:52:04.694+0000 I REPL     [replexec-0] election succeeded, assuming primary role in term 1
2018-10-20T10:52:04.694+0000 I REPL     [replexec-0] transition to PRIMARY from SECONDARY
2018-10-20T10:52:04.694+0000 I REPL     [replexec-0] Resetting sync source to empty, which was :27017
2018-10-20T10:52:04.694+0000 I REPL     [replexec-0] Entering primary catch-up mode.
2018-10-20T10:52:04.694+0000 I REPL     [replexec-0] Exited primary catch-up mode.
2018-10-20T10:52:06.649+0000 I STORAGE  [rsSync] createCollection: config.transactions with generated UUID: fcb9176e-18a5-4077-8cde-05edacc97018
2018-10-20T10:52:06.673+0000 I REPL     [rsSync] transition to primary complete; database writes are now permitted
2018-10-20T10:52:06.673+0000 I STORAGE  [monitoring keys for HMAC] createCollection: admin.system.keys with generated UUID: 9909ef55-8a6b-4d9d-b70b-b43670b7bc03
[2018-10-20T10:52:07,649490652+00:00] [on-start.sh] Waiting for replica to reach PRIMARY state...
2018-10-20T10:52:07.690+0000 I NETWORK  [listener] connection accepted from <IP_ADDRESS>:46110 #5 (1 connection now open)
2018-10-20T10:52:07.690+0000 I NETWORK  [conn5] received client metadata from <IP_ADDRESS>:46110 conn5: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "3.6.8" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 9 (stretch)"", architecture: "x86_64", version: "Kernel 4.18.15-1.el7.elrepo.x86_64" } }
2018-10-20T10:52:07.693+0000 I NETWORK  [conn5] end connection <IP_ADDRESS>:46110 (0 connections now open)
[2018-10-20T10:52:07,694243711+00:00] [on-start.sh] ✓ Replica reached PRIMARY state.
[2018-10-20T10:52:07,695921272+00:00] [on-start.sh] MongoDB bootstrap complete
[2018-10-20T10:52:07,697672587+00:00] [on-start.sh] Shutting down MongoDB (force: true)...
MongoDB shell version v3.6.8
connecting to: mongodb://localhost:27017/admin
2018-10-20T10:52:07.737+0000 I NETWORK  [listener] connection accepted from <IP_ADDRESS>:46112 #6 (1 connection now open)
2018-10-20T10:52:07.737+0000 I NETWORK  [conn6] received client metadata from <IP_ADDRESS>:46112 conn6: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "3.6.8" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 9 (stretch)"", architecture: "x86_64", version: "Kernel 4.18.15-1.el7.elrepo.x86_64" } }
MongoDB server version: 3.6.8
2018-10-20T10:52:17.738+0000 I REPL     [conn6] transition to SECONDARY from PRIMARY
server should be down...
2018-10-20T10:52:17.738+0000 I COMMAND  [conn6] terminating, shutdown command received
2018-10-20T10:52:17.738+0000 I NETWORK  [conn6] shutdown: going to close listening sockets...
2018-10-20T10:52:17.738+0000 I NETWORK  [conn6] removing socket file: /tmp/mongodb-27017.sock
2018-10-20T10:52:17.738+0000 I REPL     [conn6] shutting down replication subsystems
2018-10-20T10:52:17.738+0000 I REPL     [conn6] Stopping replication reporter thread
2018-10-20T10:52:17.738+0000 I REPL     [conn6] Stopping replication fetcher thread
2018-10-20T10:52:17.739+0000 I REPL     [conn6] Stopping replication applier thread
2018-10-20T10:52:18.650+0000 I REPL     [conn6] Stopping replication storage threads
2018-10-20T10:52:18.651+0000 I FTDC     [conn6] Shutting down full-time diagnostic data capture
2018-10-20T10:52:18.652+0000 I STORAGE  [WTOplogJournalThread] oplog journal thread loop shutting down
2018-10-20T10:52:18.652+0000 I STORAGE  [conn6] WiredTigerKVEngine shutting down
2018-10-20T10:52:18.773+0000 I STORAGE  [conn6] shutdown: removing fs lock...
2018-10-20T10:52:18.773+0000 I CONTROL  [conn6] now exiting
2018-10-20T10:52:18.773+0000 I CONTROL  [conn6] shutting down with code:0
2018/10/20 10:52:19 Peer finder exiting

#1399

tcpdump from interface bootstrap container:
dns resolv worked. problem in
    <IP_ADDRESS>.46742 > <IP_ADDRESS>.domain: [bad udp cksum 0x17f9 -> 0x04ed!] 25179+ SRV? m-mongodb-replicaset.mongo.svc.s01.local. (58)
14:30:55.295370 IP (tos 0x0, ttl 62, id 26841, offset 0, flags [DF], proto UDP (17), length 185)
    <IP_ADDRESS>.domain > <IP_ADDRESS>.46742: [bad udp cksum 0x185c -> 0x88b1!] 25179* q: SRV? m-mongodb-replicaset.mongo.svc.s01.local. 1/0/1 m-mongodb-replicaset.mongo.svc.s01.local. [30s] SRV m-mongodb-replicaset-0.m-mongodb-replicaset.mongo.svc.s01.local.:0 10 100 ar: m-mongodb-replicaset-0.m-mongodb-replicaset.mongo.svc.s01.local. [30s] A <IP_ADDRESS> (157)

try to start
https://github.com/kubernetes/contrib/blob/4b2a8512a95611acb174bd306e501719ce70b1cf/peer-finder/peer-finder.go#L135

$ docker run --rm=true -it --entrypoint=/peer-finder gcr.io/google_containers/mongodb-install:0.6 --help
Usage of /peer-finder:
  -ns string
    	The namespace this pod is running in. If unspecified, the POD_NAMESPACE env var is used.
  -on-change string
    	Script to run on change, must accept a new line separated list of peers via stdin.
  -on-start string
    	Script to run on start, must accept a new line separated list of peers via stdin.
  -service string
    	Governing service responsible for the DNS records of the domain this pod is in.

@foxish Can we get an updated gcr.io/google_containers/mongodb-install with the latest peer-finder? The latest 0.6 is still missing -domain.

/cc @foxish @unguiculus

/assign @foxish

I updated the image as a first step in #9707. Feel free to create a follow-up PR.

This problem is still not resolved. The current mongodb-install docker image is still pointing to the old image without the -domain support . Can we please upgrade the image.

This is definitely still a problem. My cluster DNS is not cluster.local and I cannot get past 2/3 container initializing

I can't connect to my mongo cluster from other services and I see the following whenever I try to run a find on a collection:
Error: error: {
        "operationTime" : Timestamp(1552021460, 1),
        "ok" : 0,
        "errmsg" : "node is not in primary or recovering state",
        "code" : 13436,
        "codeName" : "NotMasterOrSecondary",
        "$clusterTime" : {
                "clusterTime" : Timestamp(1552021460, 1),
                "signature" : {
                        "hash" : BinData(0,"XfJCVFxzjxOx8pb/k8t6aE4CiWE="),
                        "keyId" : NumberLong("6664334391939956738")
                }
        }
}

How corect helm run string?
helm install --name mongodb-replicaset stable/mongodb-replicaset --domain cluster.local

Same issue here. When the cluster domain is not default "cluster.local" bootstrap init container is stuck. Tried a different cluster with "cluster.local", works out of the box.

Same issue here.

same issue here


Add long description and classifiers to _restclient and nwis_client setup.py

Adds long descriptions and classifiers to bring _restclient and nwis_client up to parity with other subpackages.

All tests pass and pushing it through. FYI: got a little out of scope. @aaraney
Got a deprecation warning on line 673 of iv.py because python mistook \d as a unicode character in the regex expression. The fix was to make the regex a raw string.

@jarq6c thanks for the bug fix and add the long descriptions, I'd forgotten to do that yesterday.


K8SPXC-954: Update k8s packages and cert-manager

Also in this PR: K8SPXC-940: Update cert-manager

Test name
Status

scheduled-backup
failed

big-data
failed

storage
failed

upgrade-haproxy
failed

recreate
failed

cross-site
passed

haproxy
failed

scaling
failed

upgrade-proxysql
failed

smart-update
failed

init-deploy
failed

restore-to-encrypted-cluster
failed

scaling-proxysql
failed

self-healing
passed

self-healing-chaos
failed

limits
failed

upgrade-consistency
failed

security-context
failed

demand-backup
failed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

operator-self-healing
passed

operator-self-healing-chaos
failed

monitoring-2-0
failed

pitr
failed

affinity
failed

demand-backup-encrypted-with-tls
failed

one-pod
failed

auto-tuning
failed

proxysql-sidecar-res-limits
failed

users
failed

tls-issue-self
failed

tls-issue-cert-manager
failed

tls-issue-cert-manager-ref
failed

validation-hook
failed

We run 35 out of 35

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1133/commits/93cc92bcfd0cdc57e2318a7e23a2ab626c6acdc8
image: perconalab/percona-xtradb-cluster-operator:PR-1133-93cc92bc

Test name
Status

scaling
failed

storage
failed

upgrade-haproxy
failed

recreate
failed

big-data
failed

scheduled-backup
failed

haproxy
failed

cross-site
failed

upgrade-proxysql
failed

smart-update
failed

self-healing
passed

self-healing-chaos
failed

scaling-proxysql
failed

restore-to-encrypted-cluster
failed

init-deploy
failed

self-healing-advanced
passed

self-healing-advanced-chaos
failed

limits
failed

demand-backup
failed

security-context
failed

upgrade-consistency
failed

operator-self-healing
passed

operator-self-healing-chaos
failed

pitr
failed

monitoring-2-0
failed

demand-backup-encrypted-with-tls
failed

affinity
failed

one-pod
failed

auto-tuning
failed

proxysql-sidecar-res-limits
failed

users
failed

tls-issue-self
failed

tls-issue-cert-manager
failed

tls-issue-cert-manager-ref
failed

validation-hook
failed

We run 35 out of 35

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1133/commits/9c7eb1e98993fb6e1b691e37936c2a4d6990336b
image: perconalab/percona-xtradb-cluster-operator:PR-1133-9c7eb1e9

Test name
Status

big-data
passed

scaling
passed

storage
passed

scheduled-backup
failed

haproxy
passed

cross-site
passed

upgrade-haproxy
passed

recreate
passed

scaling-proxysql
passed

self-healing
passed

self-healing-chaos
passed

init-deploy
passed

restore-to-encrypted-cluster
passed

security-context
passed

self-healing-advanced
passed

upgrade-proxysql
passed

self-healing-advanced-chaos
passed

limits
passed

demand-backup
passed

monitoring-2-0
passed

operator-self-healing
passed

operator-self-healing-chaos
passed

smart-update
passed

affinity
passed

one-pod
passed

auto-tuning
passed

pitr
passed

proxysql-sidecar-res-limits
passed

upgrade-consistency
passed

users
passed

demand-backup-encrypted-with-tls
failed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
failed

We run 34 out of 35

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1133/commits/a3fa520cab4f4f54a27bc41d829c2b282b6ccbb9
image: perconalab/percona-xtradb-cluster-operator:PR-1133-a3fa520c

Test name
Status

scheduled-backup
passed

upgrade-haproxy
passed

haproxy
passed

scaling
passed

storage
passed

cross-site
passed

recreate
passed

init-deploy
passed

scaling-proxysql
passed

big-data
passed

self-healing
passed

restore-to-encrypted-cluster
passed

limits
passed

security-context
passed

self-healing-chaos
passed

demand-backup
passed

monitoring-2-0
passed

self-healing-advanced
passed

pitr
passed

affinity
passed

self-healing-advanced-chaos
passed

demand-backup-encrypted-with-tls
passed

one-pod
passed

operator-self-healing
passed

auto-tuning
passed

operator-self-healing-chaos
passed

proxysql-sidecar-res-limits
passed

users
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

upgrade-proxysql
passed

validation-hook
passed

smart-update
passed

upgrade-consistency
passed

We run 35 out of 35

commit: https://github.com/percona/percona-xtradb-cluster-operator/pull/1133/commits/a3fa520cab4f4f54a27bc41d829c2b282b6ccbb9
image: perconalab/percona-xtradb-cluster-operator:PR-1133-a3fa520c


User edit page too long

User info edit page too long when role count is more then 5 or 10，there has no scrollbar。

BTW. I think the Tenant Names cannot be repeated.


Handle functions that never return in RET503 (#2602)

Hi,
Thanks for your relentless work on Ruff!
What do you think about this first shot, extremely rough, extremely naive and incomplete attempt to handle https://github.com/charliermarsh/ruff/issues/2602 by trying to figure out whether the last statement is a call to one of the known no-return functions? This is my first timid look into the Ruff source code, and my first ever look into rustpython-parser, too, so there will certainly be several "this is not the way" objections... assuming this is even on the right path.
And to foresee at least one of these objections: as noted in the code comments, this is naive and incomplete in that it compares the name under which the module ("os", "pytest", etc) is referenced, and not the actual name of the imported module. I would guess that Ruff already records imported modules somewhere so that there is a way for this code to obtain the actual (possibly fully qualified) name of the module that the expression refers to; if you could point me to a place in the Ruff code where something like that is done, I'd be happy to use it here. Also the same applies to unqualified names in function calls: when we see a call to abort() or xfail(...) as the last statement, it would be nice to be able to notice that this is, in this particular Python source file, actually from pytest import xfail and not complain about it.
Of course, as noted in #2602, a real solution would not only resolve called functions and methods, but also check whether they are type-annotated as NoReturn, and base the decision on that. If you say that my temporary band-aid is not worth merging since a type-checking solution may be the way to go, that would be fine, too.
Thanks again, and keep up the great work!
G'luck,
Peter

Right, so after @charliermarsh pointed me in the right direction on resolving function calls, things are a bit simpler now in https://github.com/charliermarsh/ruff/pull/2701/commits/41ee9a827b1c25e34f2ef2391224d3fecbca565e
Of course, the question remains of whether an allowlist that Somebody(tm) needs to maintain is the right path to take, but it might help things along for the present.

This is great, thanks! I'm generally a fan of pragmatic improvements like this.

Thanks for this @ppentchev! Without typing support this is the next best thing.
Also nice picking up on stuff in the standard library.


Sierpinski triangle demo is missing per-node expensive computation

Hello, just a thought about the rendering performance demo:
https://codesandbox.io/s/voby-demo-triangle-l837v0?file=/src/index.tsx:222-385
const useSeconds = (): Observable<number> => {

  const seconds = $(0);

  useInterval ( () => seconds ( ( seconds () % 9 ) + 1 ), 1000 );

  return seconds;
};

I think that useSeconds() should be "wrapped" into an intermediary observable that triggers at the same time as the seconds signal which is scheduled to reliably fire at every seconds tick. The goal of this "wrapper" observable is to introduce a computationally-taxing operation, per node of the triangular structure (just as in the original React demo).
This is specifically what makes this stress-test relevant, as remarked by Ryan Carniato:
https://github.com/ryansolid/solid-sierpinski-triangle-demo#solid-sierpinski-triangle-demo
See:
https://github.com/ryansolid/solid-sierpinski-triangle-demo/blob/889db98d7697bd39d8fe3ca0e0134fb2788b4447/src/main.jsx#L46-L51
    var e = performance.now() + 0.8;
    // Artificially long execution time.
    while (performance.now() < e) {}
};

(sorry, I don't know enough about Voby to contribute a PR)
I used the same technique in my stress-test for fine-grain reactivity / observable lib experiment (I use uHTML for DOM rendering). Otherwise, rendering at 200 FPS is way too easy :)

Done, thanks 👍 To be fair I don't really understand the point of that demo as a benchmark, an artificial delay of 0.8ms every 1000ms is just irrelevant I think. I think the demo just looks cool 😂

hello, yeah the CPU spike during each second tick didn't in fact make much difference in my stress-testing of uHTML + bring-my-own-reactive-lib ... however this triangles demo revealed a bug in my observer propagation algorithm (runaway memory leak which I didn't catch with unit tests)
And as you say, the demo "looks cool" ;)
PS: I've reached a point after several design/implementation iterations where my micro-lib is slightly faster than Solid but still slightly slower than Kairo (benchmarked in Node, Firefox, Safari and Chrome). It uses a synchronous propagation pattern, unlike CellX which defers to a microtask (rather unpredictable + skips updates as batched by default). Anyway, this is just a spare-time fun experiment, the API surface is super small (only the fundamental primitives, no sugar) so probably not that useful for any real-world DOM fine-grain reactivity use (I use it to refresh Preact components ... so strictly speaking reactivity at the VDOM component level, not direct DOM expressions). I am also playing with uHTML which does a complete DOM render diff but uses cache/memo to optimise the render pass.
The reactivity lib currently stands at just under 1KB (gzipped). Kairo is massive by comparison, super feature rich (and so damn fast!!). Solid reactivity core is great of course, and fine-tuned for its DOM use.
I haven't looked at Oby yet. I should add it to my Solid benchmark fork, not only to test performance but also consistency (propagation completeness and order).
Cheers, Dan

Thanks for your reply.
The CellX benchmark is of very limited interest due to how the "layers of reactivity" are structured ( https://github.com/Riim/cellx/blob/11ba12c4317534fce1c797dbad17006d7a72d82d/perf/perf.html#L159 ). The timing measurements become meaningful at around 3000-5000 layers, but at that point many implementations reach call stack limits, so the whole exercise becomes rather pointless :)
(plus, the call stack limitations are sometimes unpredictably alleviated in subsequent runs due to JS engine optimisations / function inlining)
That being said, just for fun I continue to run CellX's benchmark, mainly to stress-test my algorithm + implementation with this particular "layer" pattern. Note that CellX's "win" is largely due to deferring batched updates in a microtask, which causes undesirable unpredictable behaviour in real-world applications (notably DOM / frontend).
Crucially, I use Solid's own benchmark ( https://github.com/solidjs/solid/blob/main/packages/solid/bench/bench.cjs ) which more realistically represents real-world usage: isolation of creation vs. propagation, using a thoughtfully-crafted set of reactive graph "shapes" (i.e. mass-initialisation of observable units + computed derivations, and separate cost measurement for synchronous updates inside the reactive structure).
PS: there are significant discrepancies between JS runtimes: Node vs. Firefox vs. Safari vs. Chrome ... so, I always look at the results of synthetic / micro benchmarks with some scepticism ... including my own stats ;)
Kairo is particularly super-fast in Safari / JavaScriptCore, notably in the creation phase ... I don't think that other runtimes de-opt code paths, so maybe there are some unintentional JSCore-friendly micro-optimisation in Kairo! :)
By the way, I modified Solid's bench.cjs to verify / assert the order of reactive updates, and I discovered that Solid, Kairo, vuerx and rval-mod are consistent, whilst s-mod, sinuous-modandsinuous` are not.
I am also using Solid's unit-tests (specifically: https://github.com/solidjs/solid/blob/main/packages/solid/test/signals.spec.ts and https://github.com/solidjs/solid/blob/main/packages/solid/test/signals.memo.spec.ts ) to verify that my code performs in a manner that is "compatible" with fine-grain DOM reactivity (i.e. order of updates, propagation consistency, etc.). My algorithm "disagree" with some of Solid's reactive update paths, but I am taking this outcome as "my implementation is very likely incorrect, and it will break in some not-yet-tested edge-case"  ;o)
To be clear: I have an open-source playground / kitchen sink on GitHub, but I have no intention of publishing yet another NPM package. I take satisfaction in fine-tuning both the algorithm and its corresponding TS/JS code, whilst keeping the JS bundle size tiny (mostly for educational purposes, in my spare time, over food breaks).
My implementation of core reactivity primitives seem to have reached a level of memory/CPU performance close to Kairo and slightly better than Solid ... but in the real world, the perf bottleneck probably narrows-down to the DOM / VDOM / diff / updates (which is a problem space I have absolutely zero desire to explore ... I am quite happy to rely on the extensive prior art produced by devs smarter than me :)
Saving a few milliseconds of code execution in the reactivity logic is "nice to have", it's by no means a game-changing factor in anything other than very niche application domains. I quickly realised that it is a futile pursuit. Better focus on consistency / reliability / predictability. For example, frustratingly Terser minification introduces a few milliseconds of performance loss compared with raw JS code (I presume that somehow Terser's var/loop jiggling triggers de-opt in some code paths). I also observe significant jumps / variations when executing benchmark runs in V8 (not so much in other engines), so the median and mean average figures only tell a certain story. According to Chrome's profiler, garbage collection is largely responsible for random perf gaps in the flame graph, so I have been focusing on memory allocations and disposal patterns.
Please let me know if you are aware of particularly gruelling "reactive data" performance tests, like massive spreadsheet resolver benchmarks :)

Thanks for the pointers, I think I agree with everything you said.
I didn't know that cellx's performance was due to batching updates basically, that makes me feel much better about my implementation then 😂, which is indeed meant to be used in a different context, where batching everything may not be desirable.
I don't know of a better benchmark unfortunately, in fact I was kind of looking for a better one myself, I think I'll just run Solid's too and see what happens. Cellx's benchmark was useful to me though to get a sense of the numbers I should be seeing, and to find some re-executions that could have been avoided, but it's very narrow in scope and not really representative of real-world scenarios.
Testing-wise I'm running Sinuous' test suite plus about ~170 custom tests at the moment. It might be interesting to run Solid's test suite too, just to be even more sure that things are working correctly.
DOM-wise if you change your mind potentially you could just wire your implementation with dom-expressions, or you could just fork voby, delete everything that you don't need, and provide a shim for the remaining functions that are needed from oby here, it could be fun.

Thanks for sharing your thoughts.
The other day I was actually having a look at Ryan's @vue/reactivity wrapper for dom-expressions:
https://github.com/ryansolid/vuerx-jsx/blob/master/src/lib.ts
Besides providing a useful example of API shim, this integrates a "modified version of mapSample from S-array[https://github.com/adamhaile/S-array] by Adam Haile", just as in Solid itself ( https://github.com/solidjs/solid/blob/main/packages/solid/src/reactive/array.ts )
....another piece of the puzzle which was solved a while ago with good performance and reliability, so thankfully no need to "reinvent the wheel" here :)

Re. CellX microtask updates batching:
FWIW, I was quite surprised to observe that my humble synchronous algo was faster than CellX's async updates:
5000 "layers" (beforeChange: [2,4,-1,-6], afterChange: [-2,1,-4,-4])
(2020 MacBookPro Intel i5)
(CellX JS bundle from CDN<EMAIL_ADDRESS>)
Chrome:
CellX:
MIN: 9.800000000745058,
MAX: 12.300000000745058,
AVERAGE: 11.020000000111759,
MEDIAN: 10.550000000745058

Mine:
MIN: 4.799999998882413,
MAX: 15,
AVERAGE: 9.129999999701976,
MEDIAN: 7.349999998696148

Safari:
CellX:
MIN: 9,
MAX: 12,
AVERAGE: 10.100000000000183,
MEDIAN: 10

Mine:
MIN: 6.000000000003638,
MAX: 12,
AVERAGE: 7.900000000001091,
MEDIAN: 7.000000000003638

Firefox:
CellX:
MIN: 20,
MAX: 26,
AVERAGE: 23.2,
MEDIAN: 23

Mine:
MIN: 7,
MAX: 17,
AVERAGE: 13.6,
MEDIAN: 14.5

more likely, your code triggers de-opt in JS engines.
in my experience the most obvious kind of perf-killing JS is holey arrays (index beyond length-1, or Array(N) pre-alloc), as well as non-monomorphic objects (shapes with varying property order and value types) ... which both cause costly opt/de-opt cycles.
on top of that, there are many micro optimisations such as "for of" iteration vs. old-school index loops (reverse vs. increasing index makes no difference anymore in modern JS engines), resetting arrays to undefined/null vs. empty [], object.assign() vs. spread syntax, array push vs. concat allocations depending on the anticipated total capacity, usage of slice() array views followed by unforeseen/unpredicted allocation due to changes in the underlying array, object.freeze/seal or object.create(null) which seem useful on paper but in practice totally kill perf. etc. :)
PS: my original sync implem. was even faster (consistent 4ms runs) but I really wanted the consistency / predictability of updates propagation so I accepted the trade-off. In other words, I had managed to optimise extremely for Cellx's particular benchmark, but ended up breaking other important creation+propagation scenarios.

I think maybe having the code organized into classes and split into many functions may be the main issue there. Though I can't really write it differently without tradeoffs, so I think I'm happy with that.

Solid, Kairo, Cellx, etc. all use object-oriented programming style, yet they achieve good/excellent performance. So I think the performance optimisation lies elsewhere in your code. Besides the aforementioned potential de-opts, maybe your algorithm (or perhaps just its implementation) causes too many unnecessary array mutations and/or graph traversals? As you know the "difficult" part is to dynamically manage link relationships between nodes in the reactive graph (child dependencies and parent reactions of atomic observable units + computed derivations), in a memory and CPU-efficient manner. My algorithm is really quite simple (thus the small number of total lines of code for the core routines), but its implementation is a little tricky due to micro-optimisations like array re-use, index tracking, etc. (which make the code harder to read too! :)

Solid, Kairo, Cellx, etc. all use object-oriented programming style, yet they achieve good/excellent performance.

Solid is more on the functional spectrum than Voby is in my opinion. Like things are organized into classes in Voby, but I don't see a single class in Solid. Methods written like that may be harder to optimize, I'm not sure they can be inlined (or inlined as much).

So I think the performance optimisation lies elsewhere in your code.

I think using sets for deduplicating is partly responsible for this, Solid just doesn't deduplicate registrations, other than that though I really have no clue, there's basically nothing that I haven't tried optimizing already. Maybe the codebase needs a fresh pair of eyes to look at it.

maybe your algorithm (or perhaps just its implementation) causes too many unnecessary array mutations and/or graph traversals?

In cellx's benchmark those seem optimal 🤔 Well there's only one thing that I spotted that it's not optimized, if a cell in the benchmark depends on a and b, and a = 3 and b = 5, then given the particular implementation of the cell it shouldn't re-render if suddenly a = 5 and b = 3 because the result will be the same, but that's basically impossible to detect by the library, and calling the computed should be very cheap anyway and it won't cause its children to be refreshed if the output value is the same.
I think the "issue" is largely using sets, deduplicating, having the code split into classes and calling many functions for anything.

its implementation is a little tricky due to micro-optimisations like array re-use, index tracking, etc. (which make the code harder to read too! :)

I don't think I'm doing either of those, are you keeping track of indexes like Solid is doing, and also not doing any deduplication on the registration of signals with their parents? I'm not sure where I could reusing arrays 🤔

Hello, in my implementation there are no duplicate registrations (parent reactions and/or child dependencies). I use array.includes() instead of array.indexof() but performance is roughly identical. I don't use Set, notably because iterators are expensive compared with old-school looping over array indices. The array of child dependencies is re-used in order to avoid unnecessary costly allocations during the execution of a computed derivation (in other words, when signals read inside computations are the same as in the previously-executed derivation, the array remains identical so no need to reset+reallocate eagerly, might as well do it lazily, only if needed).

Hello, in my implementation there are no duplicate registrations (parent reactions and/or child dependencies). I use array.includes() instead of array.indexOf() but performance is roughly identical.

Calling indexOf/includes on an array of arbitrary length can backfire performance-wise though 🤔 with a set this check happens in constant time. Maybe in real world scenarios indexOf/includes is not a problem usually, but I'm not sure how I feel about it in general.

The array of child dependencies is re-used in order to avoid unnecessary costly allocations during the execution of a computed derivation (in other words, when signals read inside computations are the same as in the previously-executed derivation, the array remains identical so no need to reset+reallocate eagerly, might as well do it lazily, only if needed).

That's interesting, I'm doing that too, but only if the observer had only one dependency prior to being re-executed, maybe I should just do it always. I'm trying to avoid calling indexOf/includes as much as possible though, as those can get out of hand in edge cases.

@danielweck Do you have a link to your project? I'd like to take a look at it, I can't find in your github profile.

My implementation is a single TypeScript file (design + code in constant flux):
https://github.com/danielweck/preact-wmr-twind-zero/blob/main/packages/preact-things/src/observant/core/index.ts
... which is located inside my GitHub "kitchen sink" (side project, frontend performance experimentations).
Pre-compiled/transpiled Javascript is available in my Codesandbox:
Sierpinski triangle:
https://codesandbox.io/s/uhtml-obs-demo-triangle-forked-cnmehi?file=/public/obs.js
SVG clock ;)
https://codesandbox.io/s/uhtml-obs-demo-clock-forked-41if2u?file=/obs.js
CellX benchmark (Oby fork):
https://codesandbox.io/s/oby-bench-cellx-forked-1jyvch?file=/observant.js
... that being said, Codesanbox is convenient but performance metrics are somewhat impacted by the IDE integration. For more reliable / consistent measurements, and for my own regression tests I prefer to use this simple webpage (shows CellX bench median / mean average, and runs the Solid bench as well):
https://danielweck.github.io/preact-wmr-twind-zero/perf-online.html
Finally, I regularly execute the NodeJS bench for regression testing:
https://github.com/danielweck/preact-wmr-twind-zero/blob/f01b4bd3b84f9aac8629eb7aa1addfd1ecbcc753/packages/preact-things/package.json#L109-L112
https://github.com/danielweck/preact-wmr-twind-zero/blob/main/packages/preact-things/perf.cjs
(this requires a local build so you'll need to pnpm i && pnpm lint && pnpm test && cd packages/preact-things && pnpm bundle && pnpm perf :)

Thanks for the pointers! I switched to always diffing dependencies rather than only if the previous dependencies contained one item, and it seems some ~5% faster in cellx's benchmark, though I traded that performance for cleaner code elsewhere already. The main sort of bottleneck for that benchmark seems just propagating stale/ready events, possibly largely due to my use of Sets.

I might have missed an optimization, maybe if an observable is being listened only by a single observer I don't need to send stale/ready messages across the tree? It seems like that should be safe 🤔


Question: is AlpineJS automatically available?

Hey @PhiloNL,
Sorry to bother you since I have more of a question than an issue. Is AlpineJS automatically available once we include the asset?
<script src="https://unpkg.com/@wire-elements/wire-extender" data-uri="https://wire-elements.dev"></script>

I'm getting quite confused as I tried to include Alpine via
@assets
    <script
        defer
<EMAIL_ADDRESS>    ></script>
@endassets

The weird part is, that Alpine is working but I can't find it included in my <head> tag. I could understand that it is working out of the box since Livewire relies on it. But then there is a bug in Livewire, since it does not show up in the <head> tag?! 😕

Hi @maltebaer,
Alpine is part of Livewire v3 so there is no need to load Alpine manually as an asset (this will likely also result into conflicts). So livewire.js includes Alpine, that's is why it doesn't show up in the <head> tag.

Thanks for the quick reply, that makes sense.
One weird thing tough, if you include a script after @vite() it does not make it into the header. So better do
@assets
    <script
        src="https://cdn.jsdelivr.net/npm/pikaday/pikaday.js"
        defer
    ></script>
    @vite('resources/css/components/chatbot.css')
@endassets

and not the other way around. Maybe it'll help someone else.

No problem. Not sure about the @vite problem though, I've never used @assets together with @vite.


feat: Automation of the update of the NOTICE_MIGRATION.md on releases

Summary:
Automation of the update of the NOTICE_MIGRATION.md on releases
Expected behavior:
Example of a PR on release is available here.
NOTE: this workflow won't work for the next release since the generation of rules.json isn't supported for release v4.1.0. This is why in the example provided bellow the severity of the notice in the PR body isn't accurate of version 4.1.0. Going forward the update will work as expected.
Closes #1524
Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Run the unit tests with gradle test to make sure you didn't break anything
[x] Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
[x] Linked all relevant issues
[x] Include screenshot(s) showing how this pull request works and fixes the issue(s)

@emmambd  unfortunately, it won't work for the next release since the previous release didn't support the generation of rules.json. But it will work for the next ones!


HHH-12963: HANA dialect doesn't set internal configuration for use_unicode_string_types correctly

use member variable instead of local variable
fix an "unboxing" compiler warning

Applied upstream, thanks


Added kw/edu/moe

The email domain for teachers and students in the official school system in Kuwait, it matches the domain of the ministry: moe.edu.kw

@AliQ80 lib/domains/kw/edu/moe: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

sorry for that, and thank you for your comment, I have redone this.


chore(java_templates): add lint/static analysis presubmit checks for samples

This PR was generated using Autosynth. :rainbow:
Synth log will be available here:
https://source.cloud.google.com/results/invocations/107672f6-5b9d-4fec-9a44-a79dbdc67f47/targets

[ ] To automatically regenerate this PR, check this box.

Source-Link: https://github.com/googleapis/synthtool/commit/c3caf0704f25a0c365f1c315e804a30b87c62a75

@billyjacobson would you be able to take a look at the failing static analysis build?


Ansible Tower provider url verification does not display flash error with invalid credentials

Purpose or Intent
When the URL entered for an Ansible tower provider causes URI to throw an exception on parse, the flash message is not displayed in the UI

added URL validation in the angular form
strip spaces from the URL entered in the UI
handle exception in URI.parse

Links
https://bugzilla.redhat.com/show_bug.cgi?id=1366468
Steps for Testing/QA
When adding a new Ansible Tower provider, add one space to the end of the URL. Enter invalid credentials. Click on Validate - there will be no flash error message displayed without the fix.

@miq-bot add_label wip, ui, bug

@miq-bot remove_label wip

@miq-bot add_label darga/yes

@miq-bot add_label wip

@lgalis as discussed, you moved the sync_form_to_instance and update_authentication_provider methods into the begin block so the user would be aware if an exception happened during the angular transaction.  Without this, the exceptions get logged, but the user is not made aware.  I think we should move them back out of the begin block.  The other option we discussed was trimming the URL in JS, so it's always clean when it comes up.
@himdel We need some way of propagating exceptions in ruby during an angular transaction that is more generic, like we would do for normal html transactions that would display the Rails exception screen?  With the problem being fixed here, the exception was only logged, the user didn't even know anything happened.

Aaah, that's a good point, we should be able to make $http do anything we want on an error response code.. so I guess adding a flash message would make sense? Or a huge red dialog..?

@dclarizio @lgalis  Something like https://github.com/ManageIQ/manageiq/pull/10984 should address that problem, if I understand correctly..

@miq-bot remove_label wip

@miq-bot add_label euwe/yes

Euwe Backport details:
$ git log -1
commit d14fdac7e16b39ea8d87d895294d870847ee9ae7
Author: Dan Clarizio<EMAIL_ADDRESS>Date:   Fri Oct 21 11:56:57 2016 -1000

    Merge pull request #10683 from lgalis/ansible_add_provider_with_invalid_credentials

    Ansible Tower provider url verification does not display flash error with invalid credentials or when the URL contains a space
    (cherry picked from commit ec20ea90df7c53ae6dd396529b60194887889d04)

    https://bugzilla.redhat.com/show_bug.cgi?id=1366468

Darga BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1368162

Darga Backport details:
$ git log -1
commit 0c23b6985f1bf72e21c80ce38ddfbd357b2e14d0
Author: Dan Clarizio<EMAIL_ADDRESS>Date:   Fri Oct 21 11:56:57 2016 -1000

    Merge pull request #10683 from lgalis/ansible_add_provider_with_invalid_credentials

    Ansible Tower provider url verification does not display flash error with invalid credentials or when the URL contains a space
    (cherry picked from commit ec20ea90df7c53ae6dd396529b60194887889d04)

    https://bugzilla.redhat.com/show_bug.cgi?id=1368162


Does this model only work serially?

I open multiple websites of this model that I deployed myself, and submit the work separately, but they can't work in parallel, they can only be put into the queue for serial processing

--concurrency_count=4

or choose whatever you like.  However, this uses a shared model state, and not all models will handle that well due to caching in the model.  E.g. falcon has issues, so we disable caching.
For optimal concurrency best to use vLLM or TGI inference servers.  There's no real cost and relatively easy to setup.


Allow dynamic evaluation of invoice number prefix

Description
This pull request enhances the functionality of the InvoiceSequencer class by enabling dynamic evaluation of the invoice number prefix configured in the admin panel. Previously, the prefix was treated as a plain string, limiting its flexibility.
With this enhancement, users can now enter dynamic PHP expressions such as date('Ym') in the admin panel, and the system will evaluate them to include the current year in the invoice numbers.
This improvement enhances the customization options available to users, allowing for more flexible and dynamic invoice number generation in Bagisto.

Result

Additionally, this modification ensures backward compatibility by continuing to support plain string prefixes.

Result

Documentation

[X] My pull request requires an update on the documentation repository.

@ghermans
Here, some test cases are failing. Please review and make the necessary changes.

@amit-webkul it should be resolved now


Add staging environment

Feature Request | Maintenance
The developers want to push to a development branch first before merging into master.
Acceptance Criteria

This ticket is done when: a separate development branch is established

This ticket is done when: this development branch builds, runs tests etc just like the master branch

This ticket is done when: a process around merging into the master branch (on release) is established. ie. when we merge, how and who is responsible

@deepankarm  help needed to set up domains

Setup https://console-dev.jina.ai/


DEP: signal: deprecate using medfilt and order_filter with float128 and object dtypes

Reference issue

As discussed on scipy-dev list on 22 Feb 2023:
<EMAIL_ADDRESS>What does this implement/fix?

Delegate to ndimage in signal.medfilt and signal.order_filter.
The former does not handle objects (e.g. Decimals) and longdoubles, so deprecate using them here.
Additional information

The goal here is to reduce duplication between ndimage and signal, and  get rid of https://github.com/scipy/scipy/blob/main/scipy/signal/_lfilter.c.in entirely (700 LOC of fairly obscure C code). Cannot just remove them, so deprecate first.
This PR is mainly to gauge the reaction from users and experts. For one, I am not entirely sure that our test coverage is sufficient. Thoughts?

This PR is mainly to gauge the reaction from users and experts. For one, I am not entirely sure that our test coverage is sufficient. Thoughts?

Missed this, feel free to ignore my comments for the mean time

@DWesl @thouis you two have been looking at signal.order_filter  in #16468, any thoughts on the proposal?

It looks as though the deprecation only applies for two dtypes; if the functionality is overlapping, can't one of them be fully deprecated?

Rebased to retrigger CI. macOS arm64 shows a relevant failure:
scipy/ndimage/_filters.py:1378: in _rank_filter
    _nd_image.rank_filter(input, rank, footprint, output, mode, cval,
E   RuntimeError: array type not supported

OK, tests on ARM64 MacOS seem to pass now. (had to use dtype.char, ugh).

That should never be necessary AFAIK; the right thing would have been np.longdouble I suspect (float128 and float96 are aliases to that which may not exist). That said, no big deal either way, so let's get it in.

That should never be necessary AFAIK; the right thing would have been np.longdouble I suspect (float128 and float96 are aliases to that which may not exist). That said, no big deal either way, so let's get it in.

That was my first reaction too, but https://github.com/scipy/scipy/pull/18341/commits/e302668bde746604b4b0504b5695945cda738536 failed on arm64 CI (can't test locally though).

I did a quick check locally, this is plain weird:
>>> a = np.linspace(0, 1, 3, dtype=np.longdouble)
>>> a.dtype
dtype('float64')
>>> a.dtype.char
'd'
>>> a.astype(np.longdouble).dtype
dtype('float64')
>>> a.astype(np.longdouble).dtype.char
'g'

Let's forget about that and move on though, it's not worth caring about. longdouble needs to just disappear.

Thanks for verifying it's not me losing my marbles! :-)

Let's forget about that and move on though, it's not worth caring about. longdouble needs to just disappear.

+1


Impossible to generate JWT Token

Hi, I've been trying to generate the token for programmatic as stated on this guide:
https://developers.docusign.com/docs/platform/auth/jwt/jwt-get-token/#Create
But I simply have not had success, and keep gettinginvalid_request as an error response:
There are a couple of things that concern me on the guide:

You request a user account ID, in my API & Keys Pannel I have User ID & API Account ID I'm guessing is the first, but you can understand my confusion.
In the example JWT, you're passing a "name" parameter but on the body definition, you are not mentioning it. Should I pass it or not? What is the name from the user, or from the account?
The param exp, mentions it defaults to one hour but it also mentions that is required. Also, it says that cannot be set to more than one hour, but in the example JWT it is set to more than an hour.
Finally, on the sample JWT, you're declaring in the signature that a dot separates the public and private keys. Most signature packages I encountered use a colon "," instead:

RSASHA256(
  base64UrlEncode(-----BEGIN PUBLIC KEY-----
MIIBIj...IDAQAB
-----END PUBLIC KEY-----) + "." +
  base64UrlEncode(-----BEGIN RSA PRIVATE KEY-----
MIIEpQ...9ZwKY=
-----END RSA PRIVATE KEY-----),

This last issue leads me to think, that I'm possibly encountering a bug. Please help @acooper4960

I've enabled logs in security preferences but it only contains my web navigation history.
I also tried in the troubleshooting section, in the same guide. But the response I'm getting is not included, the closest there it is: "Invalid authentication request: The response type is not supported", but mentions a different issue.

I really do not understand where the error was in my previous attempts, but here is a Node script that get's the job done.
I hope it helps someone, and maybe it can be added to the docs, because using curl as the docs currently suggest do not return the error_description.
const jwt = require('jsonwebtoken');
const moment = require('moment');
const axios = require('axios');
const fs = require('fs');

const grant_type = 'urn:ietf:params:oauth:grant-type:jwt-bearer'
const privateKey = fs.readFileSync('private.key')
const clientId = "<your-application-client-id>"
const userId = "<your-user-id>"

const claims = {
  iss: clientId,
  sub: userId,
  iat: moment().unix(),
  exp: moment().add(60, 'minutes').unix(),
  aud: "account-d.docusign.com",
  scope: "signature impersonation"
}

jwt.sign(claims, privateKey, { algorithm: 'RS256' }, (err, assertion) => {
    if (err) console.log(err)

    console.log(assertion);
    const body = { grant_type, assertion };

    axios.post('https://account-d.docusign.com/oauth/token', body)
    .then(({data}) => console.log(data))
    .catch(({response}) => console.log(response.data));
});

As for my questions:

Yes, is the User Id, not the API Id.
The name is not required, the sample JWT body requires an update.
The exp claim is indeed required and needs to be valid (less than one hour of difference with the iat). However, the value is dismissed when generating the token. I suggest updating the sample (with a valid difference) and replacing the "Defaults to one hour" wording for "is set to one hour". Even better remove the claim, or use it when generating the token.
As for the last point, fortunately, no bugs to report :)

Hi @Santiago8888, I apologize for the delayed response and thank you for bringing this to our attention and for providing suggestions to improve our docs. It seems you have already found answers to your questions. Please reach out if you need further assistance.
As for documentation, I've created DEVDOCS-3429 for our docs team to address these concerns.

Indeed @annesophien, my questions were solved and using the API. Good luck, with the Docs update!
Feel free to close.

Closing this issue for now. Thanks for checkout out SDKUnitTests for docusign-node-client specific inquiries @Santiago8888, that is usually where we direct customers for questions such as this.


Update mediation policy using inline content is not implemented

Need to implement this. Adding mediation policy using inline is implemented and hence we need to support 'PUT' as well.

We will not add this functionality for the upcoming 3.1.0 release. Will consider in future 3.x releases.

Mediation policy is now change to operation policy view and please check if this align with it and re-open if needed.


Suggest FAQ about name

Based on https://discuss.commonsearch.org/t/common-search-es/15/2

Great, thanks! I'll probably remove the last paragraph which is kind of a let down ;)


XPlat fixes for WebAssembly.

A few changes to help with WebAssembly on xplat. Note that while most tests pass, there's still a couple of issues: firstly, liveness of entrypoints in the debugger.js test is incorrectly handled, and secondly, we uncovered a bug that also happens in asm.js related to floating-point arguments. Due to this, ENABLE_WASM isn't set on xplat yet, but chakracore does now build and run with that flag set.

Reviewed 1 of 4 files at r1, 12 of 13 files at r2.
Review status: all files reviewed at latest revision, 4 unresolved discussions, some commit checks failed.

lib/WasmReader/WasmSignature.cpp, line 187 at r2 (raw file):

WasmSignature::Dump()
{
    Output::Print(_u("("));

Could you wrap the content of this function with #if ENABLE_DEBUG_CONFIG_OPTIONS

test/WasmSpec/rlexe.xml, line 2 at r2 (raw file):

<?xml version="1.0" encoding="utf-8"?>
<!-- Auto Generated by convert-test-suite -->

Like the comment mentions, this file is automatically generated, thus you should also edit the source that creates this file.
Change <baseline>${getBaselinePath(specFile)}</baseline> in  test\WasmSpec\convert-test-suite\index.js to replace backward slash to forward slash

Comments from Reviewable

@dotnet test OSX osx_osx_debug_static please

Reviewed 2 of 3 files at r3, 4 of 4 files at r4.
Review status: all files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

lib/Runtime/Library/CMakeLists.txt, line 117 at r2 (raw file):
Previously, obastemur (Oguz Bastemur) wrote…
I would really appreciate if you can add these sources conditionally.
if (CC_TARGETS_AMD64)
    set(CRLIB_SOURCE_CODES ${CRLIB_SOURCE_CODES}
        WasmLibrary.cpp
        WebAssembly.cpp
        .... and others
       )
endif()

..and an xplat-todo note enable this for other arch(s) same applies to other CMake etc. changes.

@penguinwizzard Can you look at this request ?

test/WasmSpec/convert-test-suite/index.js, line 95 at r4 (raw file):

function hostFlags(specFile, {useFullpath} = {}) {
  return `-wasm -args ${
    useFullpath ? specFile : path.relative(rlRoot, specFile)

I think you should call slash here as well. our host is probably able to support backward slash in arguments, but might as well keep them conform across the file.

Comments from Reviewable

@dotnet test OSX osx_osx_debug_static please

in case the CI is just fine #2405 should take care of the random initialization failures.

(Since reviewable is crashing when I try to submit these responses there:)
I've added the slash command to the second location in the conversion script, and re-generated the rlexe file from it as appropriate.
The cmake files have additions to only include the wasm-related files if building on amd64 for xplat builds.

 on my side
@obastemur  Could you review the changes in cmakelist files.

Reviewed 6 of 6 files at r6, 1 of 1 files at r7.
Review status: all files reviewed at latest revision, 3 unresolved discussions.

Comments from Reviewable

:shipit:


Add support for resources to wit-component

This commit fully integrates resource types in the component model with
the wit-component crate, implementing features such as:

A WIT package using resource types can now be round-tripped through
its WebAssembly encoding. This enables use cases such as wit-bindgen
which embed type information in custom sections of core wasm binaries
produced by native compilers.

Core modules can be lifted into components and the component can use
resources. This provides a target for wit-bindgen and other code
generators to use when generating guest code. Resource intrinsics and
destructors are all available to the core wasm as desired.

WIT can be inferred from components using resources, where functions
are represented as resource-related functions in WIT.

The roundtrip-wit fuzzer is extended with resources support meaning
all of the above support will be fuzzed on OSS-Fuzz.

This required a number of refactorings in wit-component especially
around how type information was handled. Previous processing was a bit
fast-and-loose because where exactly a type was defined didn't really
matter since everything was nominal. With resource types, however,
definition locations are significant and this required some fixes to
previous processing. One example of this is that
https://github.com/WebAssembly/component-model/issues/208 was discovered through this work and the
fixes required were implemented previously and further handled here in
wit-component.
Overall this PR has been almost exclusively fuzz-driven in its
development. I started out with the bare bones of getting simple
components working with resources being imported and exported, then
added fuzzing support to wit-smith, then let the fuzzer go wild. Quite
a few issues were discovered which led to all of the refactorings and
processing here in this PR. I definitely won't claim that this is a
simplification at all to wit-component by any measure. Rather it's
taking a complicated codebase and making it more complicated. In my
mind though the "saving grace" is that I'm pretty confident in the
testing/fuzzing story here. It's relatively easy to isolate issues and
add test cases for the various things that can crop up and the fuzzer
has quite good coverage of all the various paths through
wit-component. All that's to say that this is surely not the "best" or
easiest to understand implementation of resources, but it's intended to
be sufficient for now.

Note: this builds on https://github.com/bytecodealliance/wasm-tools/pull/1081 and https://github.com/bytecodealliance/wasm-tools/pull/1083 in the first two commits

cc @silesmo as you're likely interested in this as well


support for controlling entities in an area based on a partial name

for example
entity name: person room ceiling lights
area: person room
sentence: turn on the ceiling lights in person room
I notice that at present, it expects a mostly exact match with the entity name or aliases, and this sentence form would be more natural in my opinion.
Not sure if this is the right place to be asking this though.

As a workaround you could define an alias "ceiling lights". I assume this should work, as long as you indeed only call the intent with the area as well.

You sure about that?
I checked https://github.com/home-assistant/intents/blob/main/sentences/en/homeassistant_HassTurnOn.yaml and it doesnt seem to support areas for generic entities.
And it definitely doesnt work.

You sure about that? I checked https://github.com/home-assistant/intents/blob/main/sentences/en/homeassistant_HassTurnOn.yaml and it doesnt seem to support areas for generic entities.
And it definitely doesnt work.

It should work, if you define an alias "alcove lights"  (or in the first example "ceiling lights") for person room ceiling lights. So no support for generic entities but you can rename entities to match your needs.

so the home assistant matching logic can match "area" "entity" as an entity name?
Well, it's good to know I guess.
But IMO,   in  should probably be suported too, if only for consistency with the other actions. And feels more natural in an english sentence to me. But that's probably out of scope of this particular issue I suppose.
And I still think having some kind of partial/fuzzy matching for entities would probably be beneficial for the user experience. Assuming it doesn't perform an action on a low-confidence match I suppose.

Partial/fuzzy matching will come later when we use the sentences from this repo to train actual machine learning models. For example: generating all possible sentences and using snips-nlu to train an English model.


WATCH transactions

Hi.
Stdnet looks like a very powerful, yet simple ORM. I read the docs and tried looking through the code for transaction support.
I have an use case almost exactly like in the Redis docs:
http://redis.io/topics/transactions -> section on optimistic locking and check-and-set
Does transactions with Stdnet support WATCH command?
My thanks.
Jussi

Jussi,
the short answer is No.
At the moment, transactions don't use WATCH and therefore there is no guarantee that keys taking part in the transaction have changed by the time we issue the EXEC command.
The good news is, once redis 2.6 is out, there will not be a need for WATCH in stdnet.
The transaction will be issued as a lua script, atomically, with WATCH part of the script.
This will be in stdnet 0.7

OK, thank you for the fast response.
I noticed that there is a redis client implementation in the stdnet. Any thoughts on using redis-py and stdnet concurrently in the same python session?
I was thinking that I could implement my data structures with stdnet, but create the CAS procedure keys directly to Redis. It looks like Redis 2.6 is not quite here yet and I'd like to get my testing underway. Thus I might use redis-py and stdnet at the same time, but with separate connections to Redis.

That should be fine. You can use stdnet to manage and retrieve your data, and use redis-py for your specific needs. You could also use the internal (redis-py) client by doing something like this:
from stdnet import getdb

rpy = getdb().redispy

or with a connection string
rpy = getdb('redis://my.host.name:6379/?db=1').redispy

Great, thank you.
It seems I can use instance_keys on model instances to get the keys I want to watch.


This isn't an issue yet - but... (StackPath)

I'm curious if anyone is looking at writing code to interface with StackPath's API.  StackPath has acquired MaxCDN and they are in the process of merging.  I had a conversation with a MaxCDN person who said it was unknown whether or not they'd continue to use the MaxCDN api or migrate to StackPath's or use both.  The cool think about StackPath is that SSL is included as part of their CDN solution where MaxCDN charges $99/month to acquire and manage the keys.  It might be something worth looking at.  Not sure how much work it'd be to add it - but it'd certainly create some additional value to folks who want to support SSL.

Sounds like it could be fun!  When doing the bug fixes for RackSpace CDN it got me intrigued by all of this.  So trying my hand with StackPath APIs would be pretty cool.
Update
I notice this recent article on StackPath where despite acquiring MaxCDN they are still advocating the use of it to communicate with their own CDN.  I have to figure when the dust settles Stackpath will likely keep both APIs.


Building the initial code base - Repo is Work In Progress until specified otherwise

We will now build the initial code base
@azulehner , after accepting the invitation I sent you, please push your code base of the simulator, and @gadial will PR in parallel his wrapper to Qiskit. @azulehner I made you admin, so you should be able to push your initial code, and later approve enhancements to it
The entire code base will be in work-in-progress until smooth integration. Hopefully we'll have the code base ready soon, remove the WIP, and can proceed to enhance it from here.

I have pushed my code base of the simulator

Here are detailed instructions for the install and test process for pip users.  We wish to verify this indeed works for Linux computers.

sudo pip uninstall qiskit-addon-jku
sudo -H pip install qiskit-addon-jku
Run sudo pip show qiskit-addon-jku and take a look at the dir given by Location:
3.1) This directory should have a subdirectory named qiskit_addon_jku (note the underline).
3.2) This subdir should have the following files: MakeCache.txt  CMakeFiles  cmake_install.cmake  init.py  jkuprovider.py  jku_simulator  Makefile  pycache  qasm_simulator_jku.py
Try running on the test files located in the examples directory of the github code.
4.1) python3 examples/jku_backend.py (might have to copy the ghz.qasm from the examples dir to the working dir)
4.2) python3 examples/jku_circuit.py
If it fails, you might need to set PYTHONPATH to point at the correct dirs: setenv PYTHONPATH <path_to_python_package_dir>/qiskit_addon_jku:<path_to_python_package_dir>/qiskit

Closing as we are done for first release and ready for public


When I start lt, it prints out a URL but then exits immediately after

Doesn't print any message about why. I'm running Docker within a traefik network for my proxied endpoint, so I'm using the --local-* flags in order to accomplish that. This was working no more than a week ago.
I tried running a basic proxy with the command lt --port 8001 and that worked as expected. So this seems to be something to do with the --local-* flags. But this was working well for me previously. I haven't changed the args either.
This is the command that isn't working now:
lt \
  --local-host domain.local \
  --local-https true \
  --local-cert ~/docker/traefik/certs/domain-cert.pem \
  --local-key ~/docker/traefik/certs/domain-key.pem \
  --local-ca ~/.local/share/mkcert/rootCA.pem \
  --port 443 \
  --print-requests

lt --version is 2.0.2. System is Void Linux. Not sure what else I need to include.

Seems the issue is with the localhttps/ca/key arguments.
This fixed the issue for me.
https://github.com/localtunnel/localtunnel/issues/472#issuecomment-1447562993

Seems the issue is with the localhttps/ca/key arguments.
This fixed the issue for me.
https://github.com/localtunnel/localtunnel/issues/472#issuecomment-1447562993

Seems the issue is with the localhttps/ca/key/cert arguments.
This fixed the issue for me.
#472 (comment)

thanks. I'll check that out.

i'm not sure why i had to do it, but by adding --allow-invalid-cert true to the args, my problem went away. will close the issue.

Just FYI for anyone that comes looking, add environment variable DEBUG=localtunnel:client to debug errors.


ensure stylelint covers all folders and fix violations

no ticket
still some sass wasnt being covered as the glob wasnt covering subfolders, this PR addresses and that fixes lint violations
caveat: i have ignored:

cookie abtest sass - once the abtest has finished only one variant will remain and hence a lot of styles will be removed and ill fix linting at that point.
process steps sass - these styles were largley written pre my time on project and at 600 lines of code i am not inclined to fix lint problems when this will disappear shortly to be replaced by @josephhull676 far more succint steps component

Review app deployed to https://teaching-vacancies-review-pr-3287.london.cloudapps.digital


Apple M3 Pro + UTM + Windows 11 ARM issues

I can't seem to get things working on my Apple M3 Pro with UTM, using a Windows 11 ARM iso.
Initial Windows setup works, but when it reboots it throws an error and won't continue.
Windows 11 ARM ISO was downloaded using CrystalFetch.
ISO was modified on Windows using AnyBurn method

This looks like a very niche case.
If the Windows without the script runs fine, I suggest stripping down the script first to only a few options, using the script maker. Then if the windows load fine, add a few more options, and continue this until you face the issue you are having at the moment.
Now you narrowed the problem to a few options, which it's easier to find the one thing that's caused the problem.
I don't have an apple device, though I would try this myself and help you.

Same issue when using VMware fusion as well, so maybe it's related to ARM

While the file does have support for ARM64, I don't have a way of actually testing it because I don't have ARM64 hardware.
I will say though, that when testing in VMware, sometimes my windows installations also fail but if I just retry the process without changing anything, it completes successfully, so I don't know why it happens, but sometimes it errors during installation.


Bug: Open in new tab is showing for files in search results

Description
(Please click the video links, I used multiple video)
Context menu shows wrong info on a file. At 0:28

If pressed "Open in new tab" it gives:
.
But this is the wrong context menu.
In the debug.log the error at 18:06 (0:31) is not logged. As is the wrong context menu not logged. It happend earlier around 17:55, but not sure if that is same error.
Again the wrong context menu plus wrong preview results happend:
At 0:33 is shows the wrong search results. At 0:38 is does not show al the results (Windows file explorer shows more, including the "238"folder). At 0:04 and 0:39 it shows the wrong context menu.
Also clicking on the parent folder botton a few times causes Files to crash.
https://github.com/files-community/Files/assets/35999180/9f7ed021-1223-4a51-97d8-05d6b19c93c6
Steps To Reproduce
Check this video1, video2, video3.
Requirements
Fix the contaxt menu, so it shows the right context so the error could never occur.
Files Version
<IP_ADDRESS>
Windows Version
10.0.22631.2715
Log File
debug.log

Thanks for the report

@lrstolk what's the file extension for that file?

@lrstolk

@lrstolk what's the file extension for that file?

It is an .FLP file

Also I see you changed the title, but that is one of the many problems, are all solved?

It's a bit hard to follow what's going on as the steps to repro the issue weren't added. Aside from the "open in new tab" showing in search results, what's the other issue?

Also I see you changed the title, but that is one of the many problems, are all solved?

It's a bit hard to follow what's going on as the steps to repro the issue weren't added. Aside from the "open in new tab" showing in search results, what's the other issue?

That is due to it maybe being in the original post https://github.com/files-community/Files/issues/14058
Problem:
If you search for an item, the second time searching it shows the wrong results, as shown in the video, the second time I search for 238, it shows different/wrong results.
I also found another weird thing. When I use the column layout and go through maps and search and press back, it forgets the previous map I was in. My directory is like map1/map2/map3, map 1 is the inital map in the column layout, I search and press back, it goes to map1 instead of map1/map2/map3.


Migrate to the new test proxy system

Follow this guide migrate to new test proxy system.
There have around handcraft 900 test cases need to be migrated.

https://microsoft-my.sharepoint.com/:x:/p/yuchaoyan/ERBFulQ0O-xCpVOw1-QuBXgB_n4l4-WVE6Tuhwoo1go2IQ?e=du4qfL


Add logout button

This ticket is blocked by: https://github.com/CDLUC3/dmsp_backend_prototype/issues/43
Once the above is complete, then add a logout button that calls that endpoint, and subsequently deletes the JWT token cookie.

Start with removing cookie rather than waiting on #43

Switched back to "In Progress" since I want to add some handling of context for authentication.


Add an array_position function

Use case:
Add the ability to search for an element in an array and retrieve back the array index.
As per the PostgreSQL documentation:

array_position ( anycompatiblearray, anycompatible [, integer ] ) → integer
Returns the subscript of the first occurrence of the second argument in the array, or NULL if it's not present. If the third argument is given, the search begins at that subscript. The array must be one-dimensional. Comparisons are done using IS NOT DISTINCT FROM semantics, so it is possible to search for NULL.
array_position(ARRAY['sun', 'mon', 'tue', 'wed', 'thu', 'fri', 'sat'], 'mon') → 2

Feature description:
several values are grouped in an array:
CREATE TABLE metrics(
    ts timestamp,
    values_sensor1 ARRAY(INTEGER),
    values_sensor2 ARRAY(INTEGER)
);

INSERT INTO metrics VALUES (NOW(), [1, 3, 7, 4], [9, 8, 0, 2]);

Possible query involving array_position:
-- find out if a value is contained in an array
SELECT array_position(values_sensor1, 10) IS NULL
FROM metrics;
-- expected output: true

-- find the position of an existing element
SELECT array_position(values_sensor1, 3)
FROM metrics;
-- expected output: 2

Especially if there is a correlation between values_sensor1 and values_sensor2 (i.e. values recorded at the same time are stored at the same index), array_position would enable queries identifying the position of a known element in the first array, and then querying the second array at the same position.

Implemented by #12249 and part of our next feature release. Thank you for reporting.


chore(package): update github-repository-provider to version 7.5.3

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Python:command 'python.setInterpreter' not found

Issue Type: Bug
I have installed Python 3.7.3 and extension in my system.
When I press 'Ctrl + Shift + P' and type 'setInterpreter', trying to set interpreter , VScode always warning 'command 'python.setInterpreter' not found'. I have no idea to solve it . (I  reinstalled Python and VS Code but didn't work.)
HELP!!!!

Extension version: 2019.4.11881
VS Code version: Code 1.33.1 (51b0b28134d51361cf996d2f0a1c698247aeabd8, 2019-04-11T08:27:14.102Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 1992)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
7.89GB (4.54GB free)

Process Argv

Screen Reader
no

VM
0%

I got this message at macbook too

same problem.
And the version 2019.3.6558 didn't see this problem in my environment. You can rollback to this version at this time as a solution way.

same problem,hoping fix soon.

same problem.
And the version 2019.3.6558 didn't see this problem in my environment. You can rollback to this version at this time as a solution way.
how to Install previous versions

Thank you! I tried. It didn't work.

I had the same problem on my Mac until I rolled back the version.
I observed the error message in the Developer Tools Console (Help -> Toggle Developer Tools) when upon the window loading:

Activating extension 'ms-python.python' failed: Unexpected token } in JSON at position 1719.

same problem.
And the version 2019.3.6558 didn't see this problem in my environment. You can rollback to this version at this time as a solution way.
how to Install previous versions

I got this message just now.And rollback to the old version worked..
I think the new version have some bugs to solve...

same problem.
And the version 2019.3.6558 didn't see this problem in my environment. You can rollback to this version at this time as a solution way.
how to Install previous versions

Thank you! I tried. It didn't work.

close the extension autoupdate first

Version 2019.4.11881 does not activate correctly in VS Code if you check the log / developer console. ( unexpected token ... ) Rolling back to the previous version worked for me.

I got this message at macbook too
I got the same problem at Ubuntu 18.04 too

same problem.
And the version 2019.3.6558 didn't see this problem in my environment. You can rollback to this version at this time as a solution way.
how to Install previous versions

same problem.
And the version 2019.3.6558 didn't see this problem in my environment. You can rollback to this version at this time as a solution way.
how to Install previous versions

thanks, the problem is solved. i think the latest version has some bugs.

I have the same problem, temporarily resolved by rolling back to the previous version, and by the way temporarily turning off extended update checking and automatic updates.

I got the same problem, fix with installing old version vscode
OS: Windows10 Pro 1809 (New install)
Python 3.6.7 64-bit (New install)

I have this problem as well. I rolled back to previous version and everything is OK.

Me too, seems that it is not wise to enable automatic update extensions.

Thanks all!! Disable automatic update extensions and roll back to the previous version is nice.

It's a duplicate of #5437. Either install the previous version of the extension or do the following:

I remove last extra comma from "C:\Users[username].vscode\extensions\ms-python.python-2019.4.11881\package.nls.[language].json."
and restart vs code.

It's a duplicate of #5437. Either install the previous version of the extension or do the following:

I remove last extra comma from "C:\Users[username].vscode\extensions\ms-python.python-2019.4.11881\package.nls.[language].json."
and restart vs code.

thank you, the best answer!!!!!!!!!!!

It's a duplicate of #5437. Either install the previous version of the extension or do the following:

I remove last extra comma from "C:\Users[username].vscode\extensions\ms-python.python-2019.4.11881\package.nls.[language].json."
and restart vs code.

the best answer!!! thank you

same problem.
And the version 2019.3.6558 didn't see this problem in my environment. You can rollback to this version at this time as a solution way.
how to Install previous versions
and you need to disable automatic update extension temporarily and waiting for the fix

I had this problem as well. I rolled back to previous version and everything now is ok, to WORK!

It's a duplicate of #5437. Either install the previous version of the extension or do the following:

I remove last extra comma from "C:\Users[username].vscode\extensions\ms-python.python-2019.4.11881\package.nls.[language].json."
and restart vs code.

The best answer !!!! thank you.
The most uninteresting error

Duplicate of #5437


Project Proposal: Due on May 5, 2024

The project proposal is not a complicated document.  It should be roughly a page in length and give an overview of what the project is about in general.  This will help your team agree on the size and scope of the project as well as provide the instructor with a chance to help ensure that the project is appropriate for the number of team members.  The proposal will also feed directly into the design document that you will produce next.
Don't get caught up in design details or any specific points for the proposal (again, that's what the design document will be). Instead, focus on the big picture of what you are hoping to accomplish with the project and why it's relevant to the networking and computing field.
Here is a general list of things the instructor will be looking for in the proposal:
• Project name
• List of all team members and their anticipated role in the project
• Overview of the project including a list of major software/hardware/networking components
• Description of the project's potential impact/market

rough draft here


⚠ Fortnite has degraded performance

In 7cbf2ae, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1559 ms

Resolved: Fortnite performance has improved in ba6d175.


fix: remove dropdown group if no children

Fix per @markmhendrickson comment
There is no sense in rendering dropdown group wrapper if there are no children.

But even with these changes, we'd still render the bottom divider, which doesn't fix the problem.
The responsibility of this component is currently to only add a style wrapper around Radix. Here that rule is broken by adding business logic. We can't be sure we always want this behaviour. React docs also suggest caution with Children. If this behaviour was so obvious, it'd be in Radix.
IMO It's a very dangerous game trying to solve problems you encounter in one instance of a UI component's use, by making changes to the UI component itself.
If you really want to use this approach, create a wrapper component of DropdownMenu.Group that has this conditional rendering Children logic.


A problem when loading model with a lambda layer

My model has a lambda layer like this:
summary = keras.layers.Lambda(sum,name='Lambda_sum')(x)
def sum(x):
    return keras.backend.sum(x[0:21],-1,keepdims=True)

I save it with checkpoint.
now I want to load it
model = load_model('./checkpoint/checkpoint-18.hdf5')

but there is an error:NameError: name 'keras' is not defined

import keras