Unable to build according to the documented guides

Following the instructions in https://github.com/vmware-tanzu/octant/blob/master/HACKING.md yields an error from the go run build.go ci-quick command:
npm ERR! errno 130
npm ERR<EMAIL_ADDRESS>postinstall: `node ./bin/postinstall/script.js`
npm ERR! Exit status 130
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-01-17T19_52_39_751Z-debug.log
2020/01/17 19:52:39 web-deps: exit status 130
exit status 1

A quick look at the logs reveals this:
8560 verbose linkBins [ { ng: './bin/ng' },
8560 verbose linkBins   '/root/octant/web/node_modules/.bin',
8560 verbose linkBins   false ]
8561 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8562 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8563 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle false
8564 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/root/octant/web/node_modules/@angular/cli/node_
modules/.bin:/root/octant/web/node_modules/.bin:/root/go/bin:/usr/lib/go-1.13/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:
:/bin
8565 verbose lifecycle<EMAIL_ADDRESS>CWD: /root/octant/web/node_modules/@angular/cli
8566 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'node ./bin/postinstall/script.js' ]
8567 silly lifecycle<EMAIL_ADDRESS>Returned: code: 130  signal: null
8568 info lifecycle<EMAIL_ADDRESS>Failed to exec postinstall script
8569 verbose teardown shutting down workers.
8570 info teardown Done in 0.001s
8571 verbose stack Error<EMAIL_ADDRESS>postinstall: `node ./bin/postinstall/script.js`
8571 verbose stack Exit status 130
8571 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
8571 verbose stack     at EventEmitter.emit (events.js:189:13)
8571 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
8571 verbose stack     at ChildProcess.emit (events.js:189:13)
8571 verbose stack     at maybeClose (internal/child_process.js:970:16)
8571 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
8572 verbose pkgid<EMAIL_ADDRESS>8573 verbose cwd /root/octant/web
8574 verbose Linux 4.15.0-74-generic
8575 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "ci"
8576 verbose node v10.15.3
8577 verbose npm  v6.4.1
8578 error code ELIFECYCLE
8579 error errno 130
8580 error<EMAIL_ADDRESS>postinstall: `node ./bin/postinstall/script.js`
8580 error Exit status 130
8581 error Failed at the<EMAIL_ADDRESS>postinstall script.
8581 error This is probably not a problem with npm. There is likely additional logging output above.
8582 verbose exit [ 130, true ]

This is on ubunut 18.04 running node 10.15.3 and npm 6.4.1
I was able to work around this by following these steps suggested by @GarySmith :
cd web
npm install
npm run build
cd ..
go generate ./web
go run build.go build
Also the https://github.com/vmware-tanzu/octant/blob/master/web/README.md has build instructions that include using a make from the top level dir, I don't believe a makefile exists at this level.

I'm also seeing an error similar when setting up a new development environment:
? Would you like to share anonymous usage data with the Angular Team at Google u
nder
Google’s Privacy Policy at https://policies.google.com/privacy? For more details
 and
how to change this setting, see http://angular.io/analytics. (y/N) npm ERR! code ELIFECYCLE
npm ERR! errno 130
npm ERR<EMAIL_ADDRESS>postinstall: `node ./bin/postinstall/script.js`
npm ERR! Exit status 130
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/jordan/.npm/_logs/2020-03-24T19_00_24_973Z-debug.log
2020/03/24 12:00:25 web-deps: exit status 130
exit status 1

Log info:
12661 verbose lifecycle<EMAIL_ADDRESS>PATH: /home/jordan/.nvm/versions/node/v13.11.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/jordan/go/src/github.com/vmware-tanzu/octant/web/node_modules/@angular/cli/node_modules/.bin:/home/jordan/go/src/github.com/vmware-tanzu/octant/web/node_modules/.bin:/home/jordan/.nvm/versions/node/v13.11.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/go/bin
12662 verbose lifecycle<EMAIL_ADDRESS>CWD: /home/jordan/go/src/github.com/vmware-tanzu/octant/web/node_modules/@angular/cli
12663 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'node ./bin/postinstall/script.js' ]
12664 silly lifecycle<EMAIL_ADDRESS>Returned: code: 130  signal: null
12665 info lifecycle<EMAIL_ADDRESS>Failed to exec postinstall script
12666 verbose teardown shutting down workers.
12667 info teardown Done in 0s
12667 info teardown Done in 0s
12668 verbose stack Error<EMAIL_ADDRESS>postinstall: `node ./bin/postinstall/script.js`
12668 verbose stack Exit status 130
12668 verbose stack     at EventEmitter.<anonymous> (/home/jordan/.nvm/versions/node/v13.11.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
12668 verbose stack     at EventEmitter.emit (events.js:315:20)
12668 verbose stack     at ChildProcess.<anonymous> (/home/jordan/.nvm/versions/node/v13.11.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
12668 verbose stack     at ChildProcess.emit (events.js:315:20)
12668 verbose stack     at maybeClose (internal/child_process.js:1026:16)
12668 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
12669 verbose pkgid<EMAIL_ADDRESS>12670 verbose cwd /home/jordan/go/src/github.com/vmware-tanzu/octant/web
12671 verbose Linux 5.3.0-7642-generic
12672 verbose argv "/home/jordan/.nvm/versions/node/v13.11.0/bin/node" "/home/jordan/.nvm/versions/node/v13.11.0/bin/npm" "ci"
12673 verbose node v13.11.0
12674 verbose npm  v6.13.7
12675 error code ELIFECYCLE
12676 error errno 130
12677 error<EMAIL_ADDRESS>postinstall: `node ./bin/postinstall/script.js`
12677 error Exit status 130
12678 error Failed at the<EMAIL_ADDRESS>postinstall script.
12678 error This is probably not a problem with npm. There is likely additional logging output above.
12679 verbose exit [ 130, true ]

After some digging I was able to see this was failing on npm ci right after angular/cli asks about anonymous usage data. I was able to find a work around by doing export NG_CLI_ANALYTICS=false to keep angular/cli from asking. That made the HACKING instructions work for me.
You can also do export NG_CLI_ANALYTICS=ci if you don't mind sending that usage data.
More information can be found here: https://github.com/angular/angular-cli/blob/master/docs/design/analytics.md

Want to pop that up as a PR? I'll gladly merge that.

Ya. I'll get one up.


[stable/mongodb-replicaset] Auth not enabled or required when auth.enabled=true

Is this a request for help?:
yes
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT

Version of Helm and Kubernetes:
minikube version: v0.24.1
kubectl version: Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.4",  GitCommit:"9befc2b8928a9426501d3bf62f72849d5cbcd5a3", GitTreeState:"clean", BuildDate:"2017-11-20T19:12:24Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"darwin/amd64"}
helm version: Client: &version.Version{SemVer:"v2.7.2", GitCommit:"8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState:"clean"}
Which chart:
stable/mongodb-replicaset
EDIT: stable/mongodb-replicaset-2.1.3
What happened:
Authentication is not actually enabled in MongoDB when auth.enabled=true
Clients on the mongo node and in other pods can connect to the replicaset and read-write data without authenticating.
What you expected to happen:
Authentication is required to connect to mongodb replicaset
How to reproduce it (as minimally and precisely as possible):
Step 1: Install helm chart with authentication enabled
helm install --set auth.enabled=true,auth.adminUser=test,auth.adminPassword=test,auth.key=test stable/mongodb-replicaset
Step 2: Shell in primary node and read/write without authenticating
a) Initiate bash session on primary pod
kubectl exec -it <name-of-primary-pod> /bin/bash
b) Connect to mongo without auth
mongo
c) Write + Read Data
rs0:PRIMARY> use test
switched to db test
rs0:PRIMARY> db.testCollection.insertOne({"foo":"bar"})
{
	"acknowledged" : true,
	"insertedId" : ObjectId("5a2adf6a77d04d87d7c118a9")
}
rs0:PRIMARY> db.testCollection.findOne()
{ "_id" : ObjectId("5a2adf6a77d04d87d7c118a9"), "foo" : "bar" }
rs0:PRIMARY>

Step 3: Confirm Auth is not enabled for MongoDB Replicaset
a) Find mongod start command and configuration file
ps aux | grep mongo
Output:
root         1  1.0  3.0 1456484 62840 ?       Ssl  18:45   0:06 mongod --config=/config/mongod.conf

Yo can see --auth flag is not set in command
b) Read config file applied to mongod process
cat /config/mongod.conf
Output:
net:
  port: 27017
replication:
  replSetName: rs0
storage:
  dbPath: /data/db

You can see that no authentication setting is present. Therefore the replicaset will not require authentication for connecting clients.
Either the command line flag --auth must be set or security.authorization section must be specified in the config for authentication to be enabled. source
Anything else we need to know:
I also created a bash session into a python3 container and used pymongo client to read+write data to the replicaset without authentication.
Unless I've made some kind of mistake, this could be a serious issue if users believe that auth.enabled will result in the database being protected with mandatory authentication. It seems that in reality only an admin user is created but clients can side step this by connecting without specifying a user. Therefore, if the service is exposed externally, or a node or pod in the kubernetes cluster is compromised, the database is compromised as well.
I hope I've missed something, and I'm wrong in identifying this issue!

An update on this; just setting auth: enabled: true doesn't take any effect. You have to manually restore the commented out configmap-settings at the bottom of the file as well.
I think the configmap-setting shouldn't be managed manually - if auth is enabled, the mongo authorization-configuration should automatically be created through the template to avoid issues such as these.
Aside from that, I am also running into the problem where the two settings above properly enabled auth in the replicaset, but my admin user is never created and thus, I can't access the database to create my service users.
I am pretty much opposite you - I have experience with Kubernetes and Helm, but not very much with Mongo.
I noticed that the actual effect of providing the secret is that the environment variables ADMIN_USER and ADMIN_PASSWORD are set in the containers through the mongodb-statefulset template. Does this mean anything to you?

@dimhoLt
Thanks for the information!
However, I'm still getting inconsistent results with enabling auth. I took your advice and did the following:
Case 1: Install using --set (failed)
Action
helm install --set auth.enabled=true,auth.adminUser=test,auth.adminPassword=test,auth.key=testcontent,security.authorization=enabled,security.keyfile=/keydir/key.txt stable/mongodb-replicaset
Contrary to my initial report, I added the parameters security.authoriztion=enabled and security.keyfile=/keydir/key.txt
Result

PASS: Cluster started successfully.
PASS: Admin user was created
FAIL: Authentication is NOT required to read/write to DB

Comments
Perhaps I've made an error in setting the values? Can somebody check my inputs here?
Case 2: Install using file -f (passed)
Action
I updated the parameters in the values.yml to the following:
auth:
  enabled: true
  adminUser: test
  adminPassword: test
  key: keycontent
...
configmap:
  ...
  security:
    authorization: enabled
    keyFile: /keydir/key.txt

Installed with the following command
helm install -f values.yml stable/mongodb-relplicaset
Result

PASS: Cluster created successfully
PASS: Admin user created
PASS: Authentication is required to read/write to DB

Disscussion

I think the configmap-setting shouldn't be managed manually - if auth is enabled, the mongo authorization-configuration should automatically be created through the template to avoid issues such as these.

I agree 100%. Also, the documentation's "Authentication" section makes no mention of updating the ConfigMap. So the README definitely needs to be updated

Aside from that, I am also running into the problem where the two settings above properly enabled auth in the replicaset, but my admin user is never created and thus, I can't access the database to create my service users.

Yes, I've encountered the same problem. I'm the one that opened #2965
At the end of the day, I'm still of the opinion this is some dangerous stuff, because really the cluster initialization is failing silently. Users may think that authentication is enabled when truly it's not.
Change Requests
Should I open another ticket for this?
1: Update README with ConfigMap instructions
Update the README with proper instructions for current chart version 2.1.3
Perhaps even put a warning at the top alerting users to this issue, so they double check auth is properly enabled. Users might be unaware that they are victims of this issue.
2: Auto-Update ConfigMap when auth.enabled=true
This way an operator only has to enable user authentication in one place.
3: Cluster Initialization should fail if authentication is not properly enabled and enforced
I don't think you can trust all users will be prudent enough (especially if they're not well-versed in mongo) to verify auth is properly enabled. Therefore, cluster initialization should fail if an automated authentication check fails on cluster creation.

Just wanted to toss my 👍  to all this. I ran into this issue as well and realized that DBs were not actually locked down as I thought they were...

Even with auth enabled I'm still not able to authenticate to the cluster. By enabling everything like @dimhoLt suggests I am able to actually sure on authentication (because the --auth flag is being set). However, I'm not able to actually authenticate now. I think that this repo might actually be using bad ENV vars for the admin username and password.
Been digging a bit further and it looks like there might be some issues upstream with the MongoDB Docker image. https://github.com/docker-library/mongo/issues/211.

I managed to get auth working by changing the following env vars in the helm charts:

ADMIN_USER -> MONGO_INITDB_ROOT_USERNAME
ADMIN_PASSWORD -> MONGO_INITDB_ROOT_PASSWORD

I've been trying to figure this out for almost a day now. It creates replicaset perfectly fine with AUTH disabled. The moment I try to enable auth - it gets stuck ini Init state forever.
I tried using existingSecret* keys and pre-created the keys, or let helm create it's own secrets with keys, both to the same result of deployment never succeeding:
auth:
  enabled: true
    adminUser: admin
    adminPassword: pass1
    key: some-key-name

...

# Entries for the MongoDB config file
configmap:
  storage:
    dbPath: /data/db
    directoryPerDB: true
  net:
    port: 27017
    # For Mongo 3.6 we also need to bind to outside world
    bindIpAll: true
    # Uncomment for TLS support
    # ssl:
    #   mode: requireSSL
    #   CAFile: /ca/tls.crt
    #   PEMKeyFile: /work-dir/mongo.pem
  replication:
     replSetName: rs0
  # Uncomment for TLS support or keyfile access control without TLS
  security:
     authorization: enabled
     keyFile: /keydir/key.txt
  setParameter:
    enableLocalhostAuthBypass: true

Alternatively, when using existing key, i'd use something like this, and it didn't work either:
TMPFILE=$(mktemp)
/usr/bin/openssl rand -base64 741 > $TMPFILE
kubectl create secret generic mongodb-replicaset-prod-keyfile --from-file=key.txt=$TMPFILE

and
kubectl create secret generic mongodb-replicaset-prod-admin --from-literal=user=admin --from-literal=password=test1

I'm wondering what you had to do to get it up and running in your case?
Thank you

Same as @virtuman here, the minute I enable auth (key, keyfile, admin user/pass, auth) the pod initialization hangs.
Working as expected otherwise

Just noticed this issue. Sorry for being late to the party. I'll try and come up with a fix.

/assign

@unguiculus
I believe I have a patch that works regarding the use of an existing secret. I implemented @ekryski recommendations. Mind if I issue a PR within the next day or so?

Sure, PRs are welcome.

FWIW, things work correctly if you follow case 2 in https://github.com/kubernetes/charts/issues/2976#issuecomment-351163614. Don't know why case 1 doesn't work. Seems to be a Helm thing. I'd try and use separate --set flags per value.
I admit that documentation could be better, but the comment in the values.yaml  mentions what you have to uncomment.
https://github.com/kubernetes/charts/blob/master/stable/mongodb-replicaset/values.yaml#L89-L92

I added a fix into my existing PR: #3728. Feel free to test and review.

Thanks @unguiculus , my problem seems to be related to the actual value of those secrets, if you use chars like *{}) then the rs init hangs. I'm assuming perhaps due to some vars not being escaped?

For reference: Following PR #3728, which is intended to fix this issue, I can't install the chart. I've opened another issue #4706

I think this is related. I'm trying to set up auth with:
auth:
  enabled: true
  adminUser: admin
  adminPassword: xxxxx
  key: xxxxxxx

I see the env vars set properly in the bootstrap container:
      POD_NAMESPACE:   monty-mongo (v1:metadata.namespace)
      REPLICA_SET:     rsp
      AUTH:            true
      ADMIN_USER:      <set to the key 'user' in secret 'mongo-pii-rs-mongodb-replicaset-admin'>      Optional: false
      ADMIN_PASSWORD:  <set to the key 'password' in secret 'mongo-pii-rs-mongodb-replicaset-admin'>  Optional: false

However that container clearly fails on the init script, the output of that container is:
[jovyan@6e7959e0e3f0 monty-mongo (⎈ |k8s-dev5.lark.com:monty-mongo)]$ k logs mongo-pii-rs-mongodb-replicaset-0 -c bootstrap
2018/05/22 20:39:22 Peer list updated
was []
now [mongo-pii-rs-mongodb-replicaset-0.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local]
2018/05/22 20:39:22 execing: /init/on-start.sh with stdin: mongo-pii-rs-mongodb-replicaset-0.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local
2018/05/22 20:39:24 MongoDB shell version v3.6.4
connecting to: mongodb://<IP_ADDRESS>:27017
2018-05-22T20:39:22.459+0000 W NETWORK  [thread1] Failed to connect to <IP_ADDRESS>:27017, in(checking socket for error after poll), reason: Connection refused
2018-05-22T20:39:22.459+0000 E QUERY    [thread1] Error: couldn't connect to server <IP_ADDRESS>:27017, connection attempt failed :
connect@src/mongo/shell/mongo.js:251:13
@(connect):1:6
exception: connect failed
MongoDB shell version v3.6.4
connecting to: mongodb://<IP_ADDRESS>:27017
MongoDB server version: 3.6.4
{
	"ok" : 1,
	"operationTime" : Timestamp(1527020793, 1),
	"$clusterTime" : {
		"clusterTime" : Timestamp(1527020793, 1),
		"signature" : {
			"hash" : BinData(0,"Fwr8jRrgFqSi6IVMVEEh6xgbvns="),
			"keyId" : NumberLong("6558444137920593921")
		}
	}
}
MongoDB shell version v3.6.4
connecting to: mongodb://<IP_ADDRESS>:27017/admin
MongoDB server version: 3.6.4
2018-05-22T20:39:24.637+0000 E QUERY    [thread1] Error: Authentication failed. :
DB.prototype._authOrThrow@src/mongo/shell/db.js:1608:20
@(auth):6:1
@(auth):1:2
exception: login failed
2018/05/22 20:39:25 Peer finder exiting

My best guess is that the script is not waiting properly for mongodb to start up which is why mongo is getting Connection refused.
Here is /work-dir/log.txt:
mongodb@mongo-pii-rs-mongodb-replicaset-0:/work-dir$ cat log.txt
[2018-05-22T20:39:22,342783094+0000] [on-start.sh] Bootstrapping MongoDB replica set member: mongo-pii-rs-mongodb-replicaset-0
[2018-05-22T20:39:22,344383092+0000] [on-start.sh] Reading standard input...
[2018-05-22T20:39:22,345944674+0000] [on-start.sh] Peers:
[2018-05-22T20:39:22,346993638+0000] [on-start.sh] Starting a MongoDB instance...
[2018-05-22T20:39:22,348356467+0000] [on-start.sh] Waiting for MongoDB to be ready...
2018-05-22T20:39:22.422+0000 I CONTROL  [initandlisten] MongoDB starting : pid=17 port=27017 dbpath=/data/db 64-bit host=mongo-pii-rs-mongodb-replicaset-0
2018-05-22T20:39:22.422+0000 I CONTROL  [initandlisten] db version v3.6.4
2018-05-22T20:39:22.422+0000 I CONTROL  [initandlisten] git version: d0181a711f7e7f39e60b5aeb1dc7097bf6ae5856
2018-05-22T20:39:22.422+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.1t  3 May 2016
2018-05-22T20:39:22.422+0000 I CONTROL  [initandlisten] allocator: tcmalloc
2018-05-22T20:39:22.422+0000 I CONTROL  [initandlisten] modules: none
2018-05-22T20:39:22.422+0000 I CONTROL  [initandlisten] build environment:
2018-05-22T20:39:22.422+0000 I CONTROL  [initandlisten]     distmod: debian81
2018-05-22T20:39:22.422+0000 I CONTROL  [initandlisten]     distarch: x86_64
2018-05-22T20:39:22.422+0000 I CONTROL  [initandlisten]     target_arch: x86_64
2018-05-22T20:39:22.422+0000 I CONTROL  [initandlisten] options: { config: "/data/configdb/mongod.conf", net: { bindIpAll: true, port: 27017 }, replication: { replSet: "rsp" }, security: { authorization: "enabled", keyFile: "/data/configdb/key.txt" }, storage: { dbPath: "/data/db" } }
2018-05-22T20:39:22.424+0000 I -        [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
2018-05-22T20:39:22.424+0000 I STORAGE  [initandlisten]
2018-05-22T20:39:22.424+0000 I STORAGE  [initandlisten] ** WARNING: Using the XFS filesystem is strongly recommended with the WiredTiger storage engine
2018-05-22T20:39:22.424+0000 I STORAGE  [initandlisten] **          See http://dochub.mongodb.org/core/prodnotes-filesystem
2018-05-22T20:39:22.424+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=7135M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),cache_cursors=false,log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
[2018-05-22T20:39:22,472382497+0000] [on-start.sh] Retrying...
2018-05-22T20:39:23.325+0000 I STORAGE  [initandlisten] WiredTiger message [1527021563:325901][17:0x7f0988d4ca00], txn-recover: Main recovery loop: starting at 3/778240
2018-05-22T20:39:23.435+0000 I STORAGE  [initandlisten] WiredTiger message [1527021563:435181][17:0x7f0988d4ca00], txn-recover: Recovering log 3 through 4
2018-05-22T20:39:23.495+0000 I STORAGE  [initandlisten] WiredTiger message [1527021563:495703][17:0x7f0988d4ca00], txn-recover: Recovering log 4 through 4
2018-05-22T20:39:23.549+0000 I STORAGE  [initandlisten] WiredTiger message [1527021563:549172][17:0x7f0988d4ca00], txn-recover: Set global recovery timestamp: 0
2018-05-22T20:39:23.575+0000 I STORAGE  [initandlisten] Starting WiredTigerRecordStoreThread local.oplog.rs
2018-05-22T20:39:23.575+0000 I STORAGE  [initandlisten] The size storer reports that the oplog contains 1407 records totaling to 158468 bytes
2018-05-22T20:39:23.575+0000 I STORAGE  [initandlisten] Scanning the oplog to determine where to place markers for truncation
2018-05-22T20:39:23.586+0000 I CONTROL  [initandlisten]
2018-05-22T20:39:23.586+0000 I CONTROL  [initandlisten] ** WARNING: /sys/kernel/mm/transparent_hugepage/defrag is 'always'.
2018-05-22T20:39:23.586+0000 I CONTROL  [initandlisten] **        We suggest setting it to 'never'
2018-05-22T20:39:23.586+0000 I CONTROL  [initandlisten]
2018-05-22T20:39:23.632+0000 I FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory '/data/db/diagnostic.data'
2018-05-22T20:39:23.633+0000 I REPL     [initandlisten] Rollback ID is 1
2018-05-22T20:39:23.634+0000 I REPL     [initandlisten] No oplog entries to apply for recovery. appliedThrough and checkpointTimestamp are both null.
2018-05-22T20:39:23.635+0000 I NETWORK  [initandlisten] waiting for connections on port 27017
2018-05-22T20:39:23.642+0000 W NETWORK  [replexec-0] getaddrinfo("mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local") failed: Name or service not known
2018-05-22T20:39:23.646+0000 I NETWORK  [replexec-0] getaddrinfo("mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local") failed: Name or service not known
2018-05-22T20:39:23.651+0000 W NETWORK  [replexec-0] getaddrinfo("mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local") failed: Name or service not known
2018-05-22T20:39:23.654+0000 I NETWORK  [replexec-0] getaddrinfo("mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local") failed: Name or service not known
2018-05-22T20:39:23.654+0000 I REPL     [replexec-0] New replica set config in use: { _id: "rsp", version: 3, protocolVersion: 1, members: [ { _id: 0, host: "mongo-pii-rs-mongodb-replicaset-0.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 1, host: "mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 }, { _id: 2, host: "mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-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('5b044631e0a44ed90fb6efc2') } }
2018-05-22T20:39:23.654+0000 I REPL     [replexec-0] This node is mongo-pii-rs-mongodb-replicaset-0.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 in the config
2018-05-22T20:39:23.654+0000 I REPL     [replexec-0] transition to STARTUP2 from STARTUP
2018-05-22T20:39:23.655+0000 I REPL     [replexec-0] Starting replication storage threads
2018-05-22T20:39:23.655+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:23.655+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:23.655+0000 I REPL     [replexec-0] transition to RECOVERING from STARTUP2
2018-05-22T20:39:23.655+0000 I REPL     [replexec-0] Starting replication fetcher thread
2018-05-22T20:39:23.655+0000 I REPL     [replexec-0] Starting replication applier thread
2018-05-22T20:39:23.655+0000 I REPL     [replexec-0] Starting replication reporter thread
2018-05-22T20:39:23.656+0000 I REPL     [rsSync] transition to SECONDARY from RECOVERING
2018-05-22T20:39:23.661+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:23.661+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:23.661+0000 I REPL_HB  [replexec-1] Error in heartbeat (requestId: 1) to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:23.661+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:23.665+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:23.665+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:23.665+0000 I REPL_HB  [replexec-0] Error in heartbeat (requestId: 3) to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:23.665+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:23.669+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:23.669+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:23.669+0000 I REPL_HB  [replexec-2] Error in heartbeat (requestId: 5) to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:23.669+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:23.674+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:23.674+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:23.674+0000 I REPL_HB  [replexec-1] Error in heartbeat (requestId: 7) to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:23.674+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:23.678+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:23.678+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:23.678+0000 I REPL_HB  [replexec-0] Error in heartbeat (requestId: 9) to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:23.678+0000 I REPL     [replexec-0] Member mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 is now in state RS_DOWN
2018-05-22T20:39:23.682+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:23.682+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:23.682+0000 I REPL_HB  [replexec-1] Error in heartbeat (requestId: 11) to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:23.682+0000 I REPL     [replexec-1] Member mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 is now in state RS_DOWN
2018-05-22T20:39:24.178+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:24.182+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:24.184+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:24.184+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:24.184+0000 I REPL_HB  [replexec-1] Error in heartbeat (requestId: 13) to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:24.184+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:24.189+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:24.189+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:24.189+0000 I REPL_HB  [replexec-0] Error in heartbeat (requestId: 15) to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:24.189+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:24.195+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:24.195+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:24.195+0000 I REPL_HB  [replexec-2] Error in heartbeat (requestId: 17) to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:24.195+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:24.203+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:24.203+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:24.203+0000 I REPL_HB  [replexec-1] Error in heartbeat (requestId: 19) to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:24.203+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:24.209+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:24.209+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:24.209+0000 I REPL_HB  [replexec-0] Error in heartbeat (requestId: 21) to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:24.214+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:24.214+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:24.214+0000 I REPL_HB  [replexec-1] Error in heartbeat (requestId: 23) to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:24.528+0000 I NETWORK  [listener] connection accepted from <IP_ADDRESS>:45064 #1 (1 connection now open)
2018-05-22T20:39:24.528+0000 I NETWORK  [conn1] received client metadata from <IP_ADDRESS>:45064 conn1: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "3.6.4" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 8 (jessie)"", architecture: "x86_64", version: "Kernel 4.4.115-k8s" } }
2018-05-22T20:39:24.531+0000 I NETWORK  [conn1] end connection <IP_ADDRESS>:45064 (0 connections now open)
[2018-05-22T20:39:24,534698841+0000] [on-start.sh] Initialized.
2018-05-22T20:39:24.580+0000 I NETWORK  [listener] connection accepted from <IP_ADDRESS>:45066 #2 (1 connection now open)
2018-05-22T20:39:24.580+0000 I NETWORK  [conn2] received client metadata from <IP_ADDRESS>:45066 conn2: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "3.6.4" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 8 (jessie)"", architecture: "x86_64", version: "Kernel 4.4.115-k8s" } }
2018-05-22T20:39:24.581+0000 I ACCESS   [conn2] Unauthorized: not authorized on admin to execute command { replSetGetStatus: 1.0, $clusterTime: { clusterTime: Timestamp(1527020793, 1), signature: { hash: BinData(0, 170AFC8D1AE016A4A2E8854C544121EB181BBE7B), keyId:<PHONE_NUMBER>920593921 } }, $db: "admin" }
2018-05-22T20:39:24.583+0000 I NETWORK  [conn2] end connection <IP_ADDRESS>:45066 (0 connections now open)
[2018-05-22T20:39:24,586679389+0000] [on-start.sh] Shutting down MongoDB (force: true)...
2018-05-22T20:39:24.633+0000 I NETWORK  [listener] connection accepted from <IP_ADDRESS>:45068 #3 (1 connection now open)
2018-05-22T20:39:24.633+0000 I NETWORK  [conn3] received client metadata from <IP_ADDRESS>:45068 conn3: { application: { name: "MongoDB Shell" }, driver: { name: "MongoDB Internal Client", version: "3.6.4" }, os: { type: "Linux", name: "PRETTY_NAME="Debian GNU/Linux 8 (jessie)"", architecture: "x86_64", version: "Kernel 4.4.115-k8s" } }
2018-05-22T20:39:24.637+0000 I ACCESS   [conn3] SCRAM-SHA-1 authentication failed for admin on admin from client <IP_ADDRESS>:45068 ; UserNotFound: Could not find user admin@admin
2018-05-22T20:39:24.638+0000 I NETWORK  [conn3] end connection <IP_ADDRESS>:45068 (0 connections now open)
[2018-05-22T20:39:24,641443309+0000] [on-start.sh] Good bye.
2018-05-22T20:39:24.709+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:24.714+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:24.714+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:24.714+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:24.714+0000 I REPL_HB  [replexec-1] Error in heartbeat (requestId: 25) to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:24.714+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:24.718+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:24.718+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:24.718+0000 I REPL_HB  [replexec-0] Error in heartbeat (requestId: 27) to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:24.718+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:24.723+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:24.723+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:24.723+0000 I REPL_HB  [replexec-2] Error in heartbeat (requestId: 29) to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:24.723+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:24.728+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:24.728+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:24.728+0000 I REPL_HB  [replexec-1] Error in heartbeat (requestId: 31) to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:24.728+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:24.732+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:24.732+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:24.732+0000 I REPL_HB  [replexec-0] Error in heartbeat (requestId: 33) to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:24.736+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:24.736+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:24.736+0000 I REPL_HB  [replexec-1] Error in heartbeat (requestId: 35) to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:25.232+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:25.236+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:25.237+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:25.237+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:25.237+0000 I REPL_HB  [replexec-1] Error in heartbeat (requestId: 37) to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:25.237+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:25.240+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:25.240+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:25.241+0000 I REPL_HB  [replexec-0] Error in heartbeat (requestId: 39) to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:25.241+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:25.245+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:25.245+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:25.245+0000 I REPL_HB  [replexec-2] Error in heartbeat (requestId: 41) to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:25.245+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:25.249+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:25.249+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:25.249+0000 I REPL_HB  [replexec-0] Error in heartbeat (requestId: 43) to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:25.249+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Connecting to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017
2018-05-22T20:39:25.254+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:25.254+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:25.254+0000 I REPL_HB  [replexec-2] Error in heartbeat (requestId: 45) to mongo-pii-rs-mongodb-replicaset-1.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable
2018-05-22T20:39:25.259+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Failed to connect to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 - HostUnreachable: HostUnreachable
2018-05-22T20:39:25.259+0000 I ASIO     [NetworkInterfaceASIO-Replication-0] Dropping all pooled connections to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017 due to failed operation on a connection
2018-05-22T20:39:25.259+0000 I REPL_HB  [replexec-1] Error in heartbeat (requestId: 47) to mongo-pii-rs-mongodb-replicaset-2.mongo-pii-rs-mongodb-replicaset.monty-mongo.svc.cluster.local:27017, response status: HostUnreachable: HostUnreachable

I had similar issue due to bad ssl key format and by looking at
kubectl describe pod mongodb-mongodb-replicaset-0
I could Identify that bootstrap container was still running and by looking at this container log there was noting special
kubectl logs mongodb-mongodb-replicaset-0 -c bootstrap

inside this container there is a script that log to /work-dir/log.txt
you can always see content of this file and it will mostly show you what is the problem with your deployment I hope
kubectl exec mongodb-mongodb-replicaset-0 -c bootstrap --  cat /work-dir/log.txt

this still is an issue. from what i see. When outputting the log files from all pods, it looks like the admin user never really gets created:
kubectl exec -it -npersistance mongo-mongodb-replicaset-0 cat /work-dir/log.txt | grep on-start
[2018-09-14T11:13:52,547058086+00:00] [on-start.sh] Bootstrapping MongoDB replica set member: mongo-mongodb-replicaset-0
[2018-09-14T11:13:52,548852694+00:00] [on-start.sh] Reading standard input...
[2018-09-14T11:13:52,552271422+00:00] [on-start.sh] Peers:
[2018-09-14T11:13:52,555081755+00:00] [on-start.sh] Starting a MongoDB instance...
[2018-09-14T11:13:52,561126593+00:00] [on-start.sh] Waiting for MongoDB to be ready...
[2018-09-14T11:13:52,718525633+00:00] [on-start.sh] Retrying...
[2018-09-14T11:13:55,112375192+00:00] [on-start.sh] Retrying...
[2018-09-14T11:13:57,219216969+00:00] [on-start.sh] Initialized.
[2018-09-14T11:13:57,403700763+00:00] [on-start.sh] Shutting down MongoDB (force: true)...
[2018-09-14T11:13:57,529441037+00:00] [on-start.sh] Good bye.
kubectl exec -it -npersistance mongo-mongodb-replicaset-1 cat /work-dir/log.txt | grep on-start
[2018-09-14T11:14:22,360964257+00:00] [on-start.sh] Bootstrapping MongoDB replica set member: mongo-mongodb-replicaset-1
[2018-09-14T11:14:22,365043898+00:00] [on-start.sh] Reading standard input...
[2018-09-14T11:14:22,366598137+00:00] [on-start.sh] Peers: mongo-mongodb-replicaset-0.mongo-mongodb-replicaset.persistance.svc.cluster.local
[2018-09-14T11:14:22,367727513+00:00] [on-start.sh] Starting a MongoDB instance...
[2018-09-14T11:14:22,369081610+00:00] [on-start.sh] Waiting for MongoDB to be ready...
[2018-09-14T11:14:22,565054595+00:00] [on-start.sh] Retrying...
[2018-09-14T11:14:24,846129453+00:00] [on-start.sh] Retrying...
[2018-09-14T11:14:27,052446061+00:00] [on-start.sh] Initialized.
[2018-09-14T11:14:27,281634303+00:00] [on-start.sh] Shutting down MongoDB (force: true)...
[2018-09-14T11:14:27,469303484+00:00] [on-start.sh] Good bye.
kubectl exec -it -npersistance mongo-mongodb-replicaset-2 cat /work-dir/log.txt | grep on-start
[2018-09-14T11:15:00,715371444+00:00] [on-start.sh] Bootstrapping MongoDB replica set member: mongo-mongodb-replicaset-2
[2018-09-14T11:15:00,716656220+00:00] [on-start.sh] Reading standard input...
[2018-09-14T11:15:00,718388186+00:00] [on-start.sh] Peers: mongo-mongodb-replicaset-0.mongo-mongodb-replicaset.persistance.svc.cluster.local mongo-mongodb-replicaset-1.mongo-mongodb-replicaset.persistance.svc.cluster.local
[2018-09-14T11:15:00,719503601+00:00] [on-start.sh] Starting a MongoDB instance...
[2018-09-14T11:15:00,720716847+00:00] [on-start.sh] Waiting for MongoDB to be ready...
[2018-09-14T11:15:00,940319792+00:00] [on-start.sh] Retrying...
[2018-09-14T11:15:03,259400144+00:00] [on-start.sh] Retrying...
[2018-09-14T11:15:05,452164994+00:00] [on-start.sh] Retrying...
[2018-09-14T11:15:07,566998122+00:00] [on-start.sh] Initialized.
[2018-09-14T11:15:08,049282145+00:00] [on-start.sh] Shutting down MongoDB (force: true)...
[2018-09-14T11:15:08,180132011+00:00] [on-start.sh] Good bye.

the required line in https://github.com/helm/charts/blob/master/stable/mongodb-replicaset/init/on-start.sh#L162 never gets executed. somehow all pods think they are in replica mode on startup.
are we sure no replset config has been received is the right string to grep for ?

ah, sorry, this is not true.  I was banging my head till I found this issue.

Hello guys,
I feel alone but for me it is really not working
using
helm install -f values.yaml stable/mongodb-replicaset
With those values.yaml
auth:
  enabled: true
  adminUser: gwapit
  adminPassword: password
  metricsUser: gwapit-metrics
  metricsPassword: password
  key: keycontent

configmap:
  security:
    authorization: enabled
    keyFile: /data/configdb/key.txt

But I am still able to connect directly
mongo xx.xx.xx.xx:27017/admin without any user / password
and of course, user and password does not work : getting crazy on that.
I did not test https://github.com/helm/charts/issues/2976#issuecomment-352493149
but I feel it strange to use that as there is a shell script for that ?


fix newer kernel usb detection

It appears newer Linux kernels have moved /proc/bus/usb/devices to /sys/kernel/debug/usb/devices. This small update makes the driver check both paths.

Hi Max - Thanks for the contribution! As you may have noticed, I've mostly abandoned this project, but it's interesting to see that it might still have a chance of being useful to someone.
I have some minor review notes on your change (see diff comments), but probably nothing that should stop it from getting merged.


2023a and 2023b tz code and data release

The 2023b release of the tz code and data is available. It follows so closely on the 2023a release because Lebanon's government announced that Lebanon's spring-forward transition previously scheduled for the end of this week has been delayed until April 20.
https://data.iana.org/time-zones/releases/

Workin on it. ;)

This has been completed (see release 2023b).
Any further drama around Lebanon's time change should not be affected unless a new zone gets created to keep track of whether some people observed the change and others didn't. If a new zone is created as described, there may be a need to create two overlapping areas for Lebanon to represent each zone.


How should we format the pdf preview?

Is the way we have it set up right now ok?

FROM COURT LEADERSHIP: Joe says that our current setup is fine.


Add test for CreateLanguage_CreatesLanguage

Motivation
Related to #69
Test out the new approach of Unit tests that are not dependent on real Kontent Project.
Checklist

[ ] Code follows coding conventions held in this repo
[ ] Automated tests have been added
[ ] Tests are passing
[ ] Docs have been updated (if applicable)
[ ] Temporary settings (e.g. variables used during development and testing) have been reverted to defaults

How to test
If manual testing is required, what are the steps?

I would use the same HTTP bodies we have in our swagger examples:
MAPI Swagger definition


AzureError has "response" while it shouldn't

It shouldn't have response because it's a generic error class. ServiceResponseError could be the one to have a response. An example is EventHubError will extend AzureError and EventHubError doesn't have response.
class AzureError(Exception):
    """Base exception for all errors."""

    def __init__(self, message, *args, **kwargs):
        self.inner_exception = kwargs.get('error')
        self.response = kwargs.get('response')
        self.exc_type, self.exc_value, self.exc_traceback = sys.exc_info()
        self.exc_type = self.exc_type.__name__ if self.exc_type else type(self.inner_exception)
        self.exc_msg = "{}, {}: {}".format(message, self.exc_type, self.exc_value)  # type: ignore
        self.message = str(message)
        super(AzureError, self).__init__(self.message, *args)

merged


SB-930 orientDb cascade updates does not work [idle TODO]

implemented in https://github.com/strongbox/strongbox/pull/620


serverDependenciesToBundle fails in v1.5.1 with RegExps

What version of Remix are you using?
1.5.1
Steps to Reproduce
Do something similar to https://remix.run/docs/en/v1/api/conventions#serverdependenciestobundle
module.exports = {
  appDirectory: "app",
  assetsBuildDirectory: "public/build",
  publicPath: "/build/",
  serverBuildDirectory: "build",
  ignoredRouteFiles: ["**/.*"],
  serverDependenciesToBundle: [
    /^rehype.*/,
    /^remark.*/,
    /^unified.*/,
    "@sindresorhus/slugify",
  ],
};

Expected Behavior
Remix to accept RegExps for ESM exclusion.
Actual Behavior
TypeError [ERR_INVALID_ARG_TYPE]: The "request" argument must be of type string. Received an instance of RegExp
   at Object.readConfig (/home/docker/code/app/node_modules/@remix-run/dev/config.js:67:11)
   at Object.build (/home/docker/code/app/node_modules/@remix-run/dev/cli/commands.js:146:31)
   at Object.run (/home/docker/code/app/node_modules/@remix-run/dev/cli/run.js:468:22)
   at Object.<anonymous> (/home/docker/code/app/node_modules/@remix-run/dev/cli.js:16:11)
   at Module._compile (node:internal/modules/cjs/loader:1103:14)
   at Object.Module._extensions..js (node:internal/modules/cjs/loader:1155:10)
   at Module.load (node:internal/modules/cjs/loader:981:32)
   at Function.Module._load (node:internal/modules/cjs/loader:822:12)
   at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:77:12)
   at node:internal/main/run_main_module:17:47

@ZipBrandon just upgraded my app that use RegExps for serverDependenciesToBundle and it's working as expected.
Could you setup a minimal reproduce case on a public repository so that we can see what's going on?

Following up on this, this was my error. I had the old API of
const { getDependenciesToBundle } = require(`@remix-run/dev`);
...

  serverDependenciesToBundle: [
    ...getDependenciesToBundle(
      /rehype.*/,
      /remark.*/,
      /unified.*/,
      /micromark.*/,
      /mdast.*/,
      /react-querybuilder.*/,
      /react-day-picker.*/,
      /react-dnd-html5-backend.*/,
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>      `@sindresorhus/slugify`,
      `react-markdown`,
      `micromark-util-symbol`,
      `zwitch`,
      `fault`,
      `ccount`,
      `react-dnd`,
      `parse-entities`,
      `stringify-entities`,
      `hastscript`,
      `ts-invariant`,
      `unist-util-map`,
      `markdown-table`,
      `longest-streak`,
      `vfile`,
      `vfile-message`,
      `@apollo/client`,
      `@sindresorhus/transliterate`,
    ),
  ],


Remove unnecessary clone on Span

Hi!
I started using pest-ast and I was running into the following lint:
warning: using `clone` on type `Span<'_>` which implements the `Copy` trait
   --> src/ast.rs:102:38
    |
102 | ...t_ast(outer(with(span_into_string)))] String);
    |          ^^^^^ help: try removing the `clone` call: `outer`
    |
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#clone_on_copy

Personally I think it is desirable to have it on, so I checked out pest-ast's code and noticed that the first element in the ConversionStrategy::Outer tuple is always a Span, which is Copy and thus shouldn't ever need clone.
I have not delved super deep in the code, though, so I'm not 100% confident on this statement: have I overlooked something?
I also changed the example slightly, removing the need for allowing lints altogether. Hth!

When will this be released?


 27. Feb. 2020 um
21:16:

WANT TO SEE HOT PICS WITH ME? 💋 💋 💋
👇 👇 👇
https://is.gd/ms4xm3
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fffaraz/awesome-cpp/issues/957?email_source=notifications&email_token=ADJAZL5YTKCDNART74CJ2WLRFANQNA5CNFSM4K5COIR2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IQ5CS3A,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJAZL6R27M6UMUY6WYCDUDRFANQNANCNFSM4K5COIRQ
.


allow use string file name for array elements

Hello.
I would like to use ActiveRecord models as Array values. But when class name puts into string, class name includes all model fields and I get something strange errors with missing constants.

Coverage increased (+0.006%) to 99.254% when pulling d6264d41a2fd4f6c3f0ac8f085f9bcb60d85f832 on pandamako:feature/use_ar_class_names into 309cf952ca33cb72d5956da6d6b724b9430e7026 on davydovanton:master.

Coverage increased (+0.006%) to 99.254% when pulling d6264d41a2fd4f6c3f0ac8f085f9bcb60d85f832 on pandamako:feature/use_ar_class_names into 309cf952ca33cb72d5956da6d6b724b9430e7026 on davydovanton:master.

Coverage increased (+0.006%) to 99.254% when pulling d6264d41a2fd4f6c3f0ac8f085f9bcb60d85f832 on pandamako:feature/use_ar_class_names into 309cf952ca33cb72d5956da6d6b724b9430e7026 on davydovanton:master.

Coverage increased (+0.006%) to 99.254% when pulling d6264d41a2fd4f6c3f0ac8f085f9bcb60d85f832 on pandamako:feature/use_ar_class_names into 309cf952ca33cb72d5956da6d6b724b9430e7026 on davydovanton:master.

Coverage increased (+0.006%) to 99.254% when pulling d6264d41a2fd4f6c3f0ac8f085f9bcb60d85f832 on pandamako:feature/use_ar_class_names into 309cf952ca33cb72d5956da6d6b724b9430e7026 on davydovanton:master.

Coverage increased (+0.006%) to 99.254% when pulling d6264d41a2fd4f6c3f0ac8f085f9bcb60d85f832 on pandamako:feature/use_ar_class_names into 309cf952ca33cb72d5956da6d6b724b9430e7026 on davydovanton:master.

Coverage increased (+0.006%) to 99.254% when pulling d6264d41a2fd4f6c3f0ac8f085f9bcb60d85f832 on pandamako:feature/use_ar_class_names into 309cf952ca33cb72d5956da6d6b724b9430e7026 on davydovanton:master.


Philosophical Questions

WE CAN attempt to answer the question of why we exist in a literal sense: by tracing our human story back through the whorls and rifts of evolution, through the contested origins of life on Earth and the collapsing cloud of dust and gas that became our home planet 4.5 billion years ago, back to the birth of our universe some 13.8 billion years ago – and perhaps further still.
Yet none of this story of happenstance helps us in finding the kind of meaning we crave: meaning in significance. “Now we know that the cosmos contains at least a million billion galaxies, each containing hundreds of billions of stars, most of which have planets around them. In one of these zillions of planets, as probably in many others, chemistry became complex and evolved in all sorts of critters, one of which, not particularly good in surviving, is humankind,” says physicist Carlo Rovelli at Aix-Marseille University in France. “It is clear that any ambition of this humankind to be particularly significant in the grand scheme of things looks silly.”
Read more: https://www.newscientist.com/article/0-why-do-we-exist-the-meaning-of-life-isnt-to-be-found-in-the-stars/#ixzz7MEBgqcz8

You don't lock bro!


Multi-monitor option

Hi!
I implemented an option to remove the top bar only on the main monitor. I made it optional since a lot of people want both behaviors.
This is the reason the pull looks big: I had to add a few files:

Settings.ui
prefs.js
utils.js (I kept it separate from util.js)
and the schema

Question about the "About" tab I included: I cite the license a being GPL2 (as this is required when uploading extensions to e.g.o), but on your github the license is MIT. We can change this to whatever you like.
I'll add two screenshots soon.

Is there a reason to introduce settings for this ? I mean we never ever want to have this triggering on another monitor.

If you look at https://github.com/deadalnix/pixel-saver/issues/80#issuecomment-240309667 some people want it to be an option as they're happy with how it works currently.   Adding in the settings page obviously adds a bit of code, but you're going to ruffle some feathers if it isn't configurable.

@deadalnix Exactly, when I was working on this I noticed the same comment that @MannyC referenced, but I also received other comments (@antmak) asking me to make it configurable.
It's ultimately up to you. If you don't want to make it configurable, you can cherry-pick the first commit in this PR!

I can confirm that this works like a charm and is highly useful. This makes the extension usable on my 3-monitor setup.
I think this should be enabled by default, and I see the toggle option purely as a bonus for people who want to switch it off (but why would you?).

@kmhofmann

I think this should be enabled by default,

No, wrong way. I use pixel-saver on several 2-monitor configurations under Fedora and CentOS. This option is harmful for me, and I wanna simple sane default: save my pixels. Window titles are evil. Hide this option somewhere deeper.

I think @antmak demonstrates the wish/need to make this optional.  Personally I vote for the enabled by default option as currently pixel-saver does not act sanely for me on multiple monitors.

Disclaimer: I don't have strong feelings, as I don't use this extension. I implemented this as I thought it would be something cool to have, nothing more.
The default for the option is false, but it can obviously be changed very easily. Also, the fact that it's an option should make everyone happy (I hope?), as no one is forced to use the extension in a given way.
@deadalnix is there anything else you'd like to see discussed/added?

@antmak It is far from obvious for the common user (or first-time Gnome user, as I was) how to un-maximize an already maximized window on a secondary monitor when the top bar isn't there. Heck, I used xkill until I looked up better alternatives. :)
The option should be enabled by default, purely from a "good UX for everyone" perspective.
It's not a problem for anyone who wants to save a few more pixels to switch this off.

@kmhofmann pixel-saver is not default plugin in gnome.
Let's return a window title to the main monitor, dont be shy... Oh, just turn off pixel-saver :)

I put some thought into this. It's clear to me that the default behavior should be to disable pixel saver on the secondary monitor. The expected behavior is that the activity bar merged with the title bar when a window is maximized and there is no activity bar on the secondary monitor.
I'm ok with having an option to keep it enabled anyway as it seems there is a fair amount of demand for it, but that shouldn't be the default behavior.
Is it possible to get a PR with exclusively the disabling of pixel saver on the second monitor ? This would make thing clearer if separate things are separated.

I just rebased against the current master branch.
I set the default to show the titlebars on secondary monitors, and I fixed the typo @zapashcanon found (thanks!).

Is it possible to get a PR with exclusively the disabling of pixel saver on the second monitor ? This would make thing clearer if separate things are separated.

The first commit does exactly this, if I understand correctly your question.

[988c5f0cdc02596e9dbda463bb45e5064bb442e3] show titlebars on secondary monitos
[98bd88be1842c08387a8bad74637887e280c5157] add a settings framework
[37c01cb83ebf37752fd43d2d12dc17db77f5ead0] make use of the setting

Unless I misunderstood the question.

Ok I'm goin to cherry ick the first commit and then review more thoroughly the rest. The note will need to be updated to reflect that there is now configuration in pixel saver. I wish to provide out of the box what a regular user will expect, but it seems clear that there is demand from power users (who I assume know the keyboard shortcuts to maximize/unmaximize) to save more pixel, so let's add a config.

That sounds fine to me!
I do understand that's quite a bit of code that I'm proposing. The whole settings thing requires the xml code, the schemas and a handler. What I want to mention about these things is that I didn't just "come up" with all the code. I based this on the code used by dash-to-dock (that I also then used on other extensions I maintain).
Let me know if you have more questions about it. Here is a quick summary of the new files:

Settings.ui: Contains the structure of the settings window
prefs.js: Builds the settings window (allowing translations if we add locales) and connects the true or false status of the option key
schema: presents the options (booleans, strings, whatever is necessary) to the extension system
utils.js: initializes a settings instance, so that they are available to the extension code

I've just tested this and while the titlebar won't get removed on the secondary monitor, the close buttons are still shown in the top panel even if there's only a maximized window on the secondary monitor.

@jhasse Thanks for spotting that. I included a fix in the latest commit. [562108603d0f4486dc041e921995a6d7c587655b].
@deadalnix since now we have a settings framework, we can easily make the buttons optional and fix #75.

@jhasse Thanks for spotting that. I included a fix in the latest commit. [5621086].

Thanks :) One minor thing left: The window title is still shown on the top bar if a window is maximized on a secondary monitor.

Thanks :) One minor thing left: The window title is still shown on the top bar if a window is maximized on a secondary monitor.

For some reason I missed this comment... I just saw it!
I noticed this, but I left it in as I thought it wouldn't bother. In what case is it bad? If an app is on the secondary monitor (without having pixel saver), the app menu shows up anyway.
Is it in case we have two windows of the same app each on a different monitor?

Ok can someone with multiple monitor can attest what's the state of this PR ? It's a bit difficult on my side for now because I do not have a multi monitor set up to test this.

I noticed this, but I left it in as I thought it wouldn't bother. In what case is it bad? If an app is on the secondary monitor (without having pixel saver), the app menu shows up anyway.

But if you have two windows of the same app maximized on both monitors (on the primary monitor first), the one on the secondary is displayed two times (in Gtk's top panel and in the top bar) and the title of the window on the primary monitor is not displayed.
Hope you get what I mean :D Maybe it isn't worth fixing.

Ok can someone with multiple monitor can attest what's the state of this PR ? It's a bit difficult on my side for now because I do not have a multi monitor set up to test this.

I'm using it and it works fine :) Also there's the option to turn it off.

@jhasse I included a fix for the title issue in [45d878fc8b3b0c11c91e554824a0986732dcaac6].
I also added [072d09c8172cee769dc356aa7c70742ae033e85b] to better refresh the appMenu and the buttons! Let me know how it goes...

I use this to fullscreen kodi on a 3rd monitor - if you use fullscreen in kodi it always picks the primary monitor. If you maximise it has a titlebar. This extension helps.
I would like to see settings introduced as a per application basis.

@gazhay  I'd love to add more settings, but first we need to introduce a settings framework, which this PR does.

Love to see action on this - If I may make a suggestion, I believe if we forgot about primary monitor, and instead make this option be for enabling only whether the monitor has a panel or not it would make this more versatile.
Think of using this extension along with the Multiple Monitor Panels extension, both together would work lovely if we focused on the existence of a panel on the current monitor =)

Exactly what I needed.

:+1: as default behavior.
Integrates well with for example "Dash to panel" as per screenshot.

Since removing the extension does not restore default behavior, logging out is required to test, after that it worked as expected for me.

It'd be great to see some progress in some of the PRs, not just this one.
At this point I'm considering uploading my own fork to e.g.o, which is only a shame, as I certainly don't want to maintain another extension, nor duplicate efforts.
Unfortunately, given the current status quo, many features are being held back.

@franglais125 I've already created a fork here: https://github.com/jhasse/gnome-shell-extension-pixel-saver-ng
This is because of a bug in Mutter which was fixed in GNOME 3.24, so my fork only works with 3.24 or newer. I could merge your changes there and then upload it to e.g.o if you want.

Thanks for the offer! I'll take look at your changes tomorrow. I just happened to upload to e.g.o! Since I had to push the changes to master on my github, I closed this PR. If not I'd be spamming everyone with every single commit I push.
It's still in review obviously. https://extensions.gnome.org/review/7144


Update label selectors caution about OR operator

Fixes #17391

Preview: https://deploy-preview-17477--kubernetes-io-master-staging.netlify.com/docs/concepts/overview/working-with-objects/labels/#label-selectors

/lgtm
/approve


How to implement Mosaic or MixUp Augmentation to the Supervised and Strong Pipeline ?

I try to implement the mosaic and mixup augmentation in your code, but I confused because the dataset is wrapped around the SemiDataset wrapper and the mosaic or mixup augmentation need the dataset to wrap on the MultiImageMixDataset type. Do you have any idea how to implement this kind of work ?

Is it possible to implement it like this?https://github.com/open-mmlab/mmclassification/blob/188aa6ed5dae184024818a6c3a72e5b0c733888d/mmcls/models/classifiers/image.py#L103


Feature request: Add italic support

Please add support for Italics, for reference, I got this hello_world.rs screenshots where tomasr/molokai theme has support for italics (e.g: rust uses them in macro! invocations).
Attaching screenshots to see a diff on the println! call difference, see line 13 as an example.  (I really like this theme btw, thanks!)
tomasr/molokai with italic support:

tanvirtin/monokai.nvim

Thanks again for your time and your effort on the project!

Hi there, glad you are enjoying the colorscheme! I have updated support for italics on some keywords such as:

Macro function calls
Function declaration keyword
Comments

If things look good to you feel free to close this issue, thank you!


Bug - conditionally rendered styles via the css helper function return incorrect property values

Environment
System:

OS: Linux 5.8 Ubuntu 20.04.2 LTS (Focal Fossa)
CPU: (20) x64 Intel(R) Core(TM) i9-10900KF CPU @ 3.70GHz
Memory: 20.23 GB / 31.23 GB
Container: Yes
Shell: 5.8 - /usr/bin/zsh

Binaries:

Node: 15.14.0 - /usr/bin/node
Yarn: 2.4.1 - /usr/bin/yarn
npm: 7.7.6 - /usr/bin/npm

styled-components version: 5.2.3
Reproduction
https://codesandbox.io/s/musing-fermi-s0d9z?file=/src/App.js
Steps to reproduce
Open developer tools and observe the styles present on the Text element. Notice that the color property is incorrectly outputted as:
color: ,green,;
Expected Behavior
If

The user conditionally renders styles using the css helper function
and
Returns a CSS property via a function  (ex. const getColor = () => 'green')

Then:
The property should be the same as what we returned. It should not be wrapped in commas. (ex. the css generated should be green not ,green,).
Actual Behavior
It seems that:
If

We conditionally render styles that are generated via the css helper function
and
A property value is returned from a function (ex. const getColor = () => 'green')

Then
The property returned from the function will be wrapped with commas and therefore will not be rendered by the browser as it's an incorrect property value.

You've used a regular template literal to embed a css tagged template literal. You can embed a template literal directly, but if you embed a css tag you basically can't stringify it and expect the correct output. It'll have an intermediate representation that isn't a plain string

Ok well, this would be very useful assuming there isn't a better way to mix in code other than using the css helper. For example, I often have a bunch of styles that I want to share between components and sometimes these shared styles have template literals in them (to control what get's rendered via props). I want to be able to render these styled anywhere and sometimes I want to only render them conditionally in other components. It would be awesome if that was possible. If there's some better way to do this, could you please share it?

Ok, maybe I wasn't clear on this 😅 You can share css annotated CSS, i.e. tagged template literals. But if you interpolate the return value of css into a regular template string then you'll get invalid output, i.e.:
css`${css``}` // this works
`${css``}` // this does not work

Ok thanks I'll try that out.


ImageReader using jpgd under GPL 3.0 license

Hello,
the class ImageReader is using jpgd which is released under the GPL 3.0 License. This means you cannot release this library under the Apache 2.0 due to the conditions in the GPL License. Can you please change the used jpg decoder?

Errr, which source files or linked libraries do you think are under GPL?
I believe the jpgd files in this repository came from Rich Geldreich's jpeg-compressor which have clearly been contributed to the public domain. This is indicated both in the repository I've just referenced, and also clearly written at the top of source files themselves:
https://github.com/glassechidna/zxing-cpp/blob/0db7f855135222becff193671faae79c083424b6/cli/src/jpgd.cpp

Oh sorry. You are totally right. I've thought you got this source-file from this project: https://github.com/kornelski/jpeg-compressor.


Auto Commenting On New Issue Creation

it ensures that comments on issues follow a consistent format or structure. This helps teams maintain a standardized approach to handling issues, reducing confusion and misunderstandings.
Users don’t need to manually add repetitive information or instructions. The automatic comment can include standard guidelines, troubleshooting steps, or links to documentation.

it ensures that comments on issues follow a consistent format or structure. This helps teams maintain a standardized approach to handling issues, reducing confusion and misunderstandings. Users don’t need to manually add repetitive information or instructions. The automatic comment can include standard guidelines, troubleshooting steps, or links to documentation.

please go for it!
please put a short video or ss before pr

@iamparas0 oK sir and thank you for the opportunity

@iamparas0  Sir  I can't show the  ss or video ,once the pr is merged the feature will start working


Support a copying read from Unalign<T> where T: !Copy but is FromBytes + IntoBytes

When working with generic code where we don't want to require Copy for large structs but is still constructed from unaligned bytes, the Ref::read method comes in handy. However, this doesn't work when you have a Ref<&[u8], [Unalign<T>]>, since there's no builtin way to index a Ref<_, [T]>.
It'd be very nice if I could take some &Unalign<T> and copy out a T where T: FromBytes + IntoBytes. This would be infallible shorthand for T::read_from_bytes(unaligned_val.as_bytes()).unwrap(). I'm not aware of an infallible way to copy out of an Unalign<T> where T: !Copy.

I'm going to make this a child of #1316 - the full solution to this is to support generic types in transmute!, which in turn requires being able to express generic size equality.


Create a getDefaultTerm() function for termData

Currently, the expression termData[defaultTerm] is used to access the default term, which is not the most concise.
Create a function getDefaultTerm() in termData which returns that expression, and make sure all usages of the expression are replaced with this function call. Optionally, also make sure defaultTerm is no longer accessible from outside of termData.

I'll claim this one.


Mark the vault certificates to be renewed 30 days before expiry

Mark vault TLS certificate to be renewed 30 days before expiry

/assign @simonswine

/lgtm


How to test Maestro cards

Hi,
i've got a problem testing Maestro Cards. For example when i use the data from the test payment page:
N°:<PHONE_NUMBER>000000
Expiry: Any date in the future
CSC: not required
I always got the following error:
Uncaught TypeError: Cannot read property 'length' of undefined
Stacke Trace:
mangoPay._validation._cvvValidator._validate	@	mangopay-kit.js:268
mangoPay.cardRegistration._validateCardData	@	mangopay-kit.js:90
mangoPay.cardRegistration.registerCard	@	mangopay-kit.js:57
registerCard	@	mangopay.js:28
.mixin..(anonymous function)	@	underscore.js:1178
(anonymous function)	@	confirm.js:231
This happens when I dont use a CSC (as described in the documentation). When i use a CSC like e.g. 123 then i got the following result:
{
ResultCode: "105204",
ResultMessage: "CVV_FORMAT_ERROR"
}
Does anybody has same problems?

Hey @crebuh, sorry to hear you're having troubles. Are you definitly using the latest version of the kit? I'm pretty sure https://github.com/Mangopay/cardregistration-js-kit/commit/789999ab98be6a7bda1749269bd5c4464a13cdc2 fixed this problem.

Also, you are definitely updateing the CardType to MAESTRO in this line: https://github.com/Mangopay/cardregistration-js-kit/blob/master/demo/index.php#L31

@hobailey
thx for the response. I updated to the latest version now the validator error message is gone.
Regarding the type of card I'm using this plugin (https://github.com/christemple/detect-card-js) to detect the card type in the background.
It is weird for the example number from Mangopay:<PHONE_NUMBER>000000 it always tells me that it is a Diners-Card?
When i use another example number for Maestro like:<PHONE_NUMBER>438453
it works ;)

@crebuh yep, our PSP doesn't use the right BINs with their test cards unfortunately - it's on our list to sort out :-)

FYI, we've seen the same issue with another library https://github.com/braintree/credit-card-type/issues/20

Hi @rik, I confirm this is an issue with the test payment cards we use as the BINs are indeed inaccurate.


Faster binary encoding/decoding

/cc @let-def

I've removed the confusing headers option and added an explicit Unboxed sub-module for unboxed binary operations. I'll merge once the CI is green.

I can review on Monday, if needed

I've tried to take all your comments into account (but the 2 about the len which can be addressed later -- as I am not sure how to address these properly)

CI restarted...


add config to allow people using proxy when downloading

Nice, i'll look into implementing it.
Would this let people use their local VPN services to access websites?
I've had some users in china having issues accessing locked websites due to the mod not using their VPN settings and i'd like to fix it.

i use clash proxy and it works. vpn should also works if you know the vpn proxy address and port.

Currently added in my personal dev repo for 3.0 release, reworked the code a bit to integrate it with config settings but it's almost the same.


Render tracking options correctly as xml

The rendering of Tracking options and category didn't correspond with the structure expected by the Xero API and mentioned in the documentation. See the example XML on https://developer.xero.com/documentation/api/invoices
This is the XML generated before the change:
<Invoice>
        <Type>ACCREC</Type>
        <Contact>
            <Name>Peninsula</Name>
        </Contact>
        <LineItems>
            <LineItem>
                <Description>Night 02/11/2017</Description>
                <Quantity>1</Quantity>
                <UnitAmount>91.67</UnitAmount>
                <TaxType>OUTPUT2</TaxType>
                <TaxAmount>18.33</TaxAmount>
                <Tracking>
                    <Name>General</Name>
                </Tracking>
            </LineItem>
        </LineItems>
        <Date>2017-11-03T12:32:14+01:00</Date>
        <LineAmountTypes>Exclusive</LineAmountTypes>
        <Reference>15</Reference>
        <Status>DRAFT</Status>
    </Invoice>

This is the changed version of the output XML:
      <Invoice>
          <Type>ACCREC</Type>
          <Contact>
              <Name>Peninsula</Name>
          </Contact>
          <LineItems>
              <LineItem>
                  <Description>Night 02/11/2017</Description>
                  <Quantity>1</Quantity>
                  <UnitAmount>91.67</UnitAmount>
                  <TaxType>OUTPUT2</TaxType>
                  <TaxAmount>18.33</TaxAmount>
                  <Tracking>
                      <TrackingCategory>
                          <Name>General</Name>
                          <Option>PMS Interface</Option>
                      </TrackingCategory>
                  </Tracking>
              </LineItem>
          </LineItems>
          <Date>2017-11-03T12:32:14+01:00</Date>
          <LineAmountTypes>Exclusive</LineAmountTypes>
          <Reference>15</Reference>
          <Status>DRAFT</Status>
      </Invoice>

I would like to have written a test for it, but there are no tests at the moment regarding marshalling/unmarshalling XML.

Thanks for the time you've taken to explain the pull request - it makes a huge difference!  Follow us on twitter @XeroAPI and flick us a DM with your address and we'll get some swag out to you.  :-)

Hi @TheRegan, seems that I can't send you guys a DM on Twitter unless you follow back. My twitterhandle is @pieterbaecke. Cheers!

Followed :-)  Flick us a DM when you get a chance


Android: will not work if using applicationIdSuffix or applicationId.

Throws exception if using applicationIdSuffix or applicationId is different than the application source package name.
Example:
You have com.android.sample as package name in your source code, and you have 2 flavors free and pro with applicationId com.android.sample.free andcom.android.sample.pro respectively. ReactNativeConfigModule throws exception: ReactConfig: Could not find BuildConfig class

My bad, missed Advanced Android Setup section in Read Me. Closing the issue.


Clippy warning: attempt to mutate range bound within loop

Just wanted to check this isn't intended to change the range over which the for loop iterates, as it won't. If the code is correct as-is, you can suppress the lint by adding #[allow(clippy::mut_range_bound)] above the for loop. Otherwise, this may be something to fix?
warning: attempt to mutate range bound within loop
   --> src\lib.rs:270:41
    |
270 | ...                   cur_line_x += 1;
    |                       ^^^^^^^^^^
    |
    = note: `#[warn(clippy::mut_range_bound)]` on by default
    = note: the range of the loop is unchanged
    = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#mut_range_bound

Thanks for pointing this out. No I wasn't trying to edit the bounds of that loop, Just mutate a variable outside of it, that happened to be part of defining that loop's range. I have updated the code so there is less confusion and this lint goes away.


New CEL convenience function: random()

Title: New CEL convenience function: random()
Description:

When called, use Random::RandomGenerator to generate a random uint64
Useful in Access Logger Filter to introduce sampling
Although this is possible with the Runtime filter, this would be useful for end users

Questions:

Should this convenience function be available everywhere? E.g. the access log formatter?
On the flip note, should this function, and others in the future, be explicitly requested by the user? E.g. a list of extensions provided with a cel expression under a new type:

message CelActivationSettings {
  repeated google.protobuf.Any typed_functions = 1;
}

message CelRandomFunction {
}

...

@wtzhang23
Is this issue for sampling in access log OR for general random purpose? This is ongoing effort https://github.com/envoyproxy/envoy/pull/34611 for former.
Also, that will be great to introduce random feature in general rather than limiting to accessLog

Intended specifically for only using the CEL access log filter. I know it is possible to compose multiple access log filters together but I'd like to use CEL by itself for convenience sake. Especially should the expression change frequently.

If you are adding a CEL convenience function, it seems that it should not only be tied with access log, even if it is not available everywhere
Limiting the scope to CEL SGTM

cced @kyessenov  as well

Will try to add it everywhere I can once I open a PR

Seems like x-request-id is already present so it may be better to simply use that? As in, in addition to the request.id attribute, another attribute that converts it into a uint that can be used for randomness (e.g. use the request id extension's getInteger function)?
Anyways, I'm almost done with the function; just need to write unit tests.


Add cross editor c++ linting config

.clang_complete is understood by various editors. It provides information that
linters and other tools can use.

What exactly does this do?

Thought you fixed this?

Though so too.

What exactly does this do?

It lets me and potentially use clang as an in-editor linter.


mock a pending component for the time to resolve beforeEach hook

Version
4.0.5
Vue Suspense component dont return fallback when vue-router is locked by a promise in beforeEach hook.
Maybe the router could provide a mock pending component the time to be able to return a route?
<router-view v-slot="{component}">
        <Suspense>
            <template #default>

                    <component :is="component" />

            </template>
            <template #fallback>
                Loading...
            </template>
        </Suspense>
    </router-view>

You likely need a :timeout="0" in your suspense component
Proper integration with suspense is yet to come.

Thank you for timeout, but that doesn't help in this case, I had already tested
Disappointed that it is closed so quickly.
Is duplicate with other issue?  Is there any discussion to track?

Proper integration with suspense is yet to come.

@posva Any news on this ?

It was closed because it didn't follow the guidelines. Other than that, this has been discussed multiple times in other issues over at vue-next and they also usually appear linked here. Looking for suspense fallback in issues yields the issues with different explanations.
That being said, Suspense is still experimental, and a few necessary changes are still needed in core for it to become stable and get a better integration with vue-router (which has also been said in other issues already)


fix: 修复apigw请求鉴权问题 --story=119092682

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.cheynechen seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Otherwise fails when a full url is passed (like from pagination)

@jacwright - fixes issue where routes won't match if a full URL is being passed in routeHandler. This was discovered due to pagination generating full URLs - click them caused the page to reload.

:+1:


Chore: add mongodb example

Checklist

[x] run make test
[x] PR title must follow conventional-commit-standard
[ ] tests and/or benchmarks are included
[x] documentation is changed or added
[x] commit message and code follows the Code of conduct

Hi @konoikon thank you for creating a PR :100:


ADDON BINDER: Cannot resolve assembly

Startup loading error before main menu:
[ERR 23:09:41.374] ADDON BINDER: Cannot resolve assembly: ContractsWindow.Unity, Culture=neutral, PublicKeyToken=null
[ERR 23:09:41.420] ADDON BINDER: Cannot resolve assembly: ContractsWindow.Unity, Culture=neutral, PublicKeyToken=null
v9.4 on KSP 1.10.1. Log attached.
Similar issue: https://github.com/CYBUTEK/KerbalEngineer/issues/156
KSP.log

reference back to original with recommended solution:
https://github.com/jrbudda/KerbalEngineer/issues/52


Fix issues with Pending Survey status

add new menu link for managers
allow users to edit report and report survey
display reports with Pending Survey status on separate page

 Pending Survey status: 2 issues

 Remove "e.g. Chris Chambers<EMAIL_ADDRESS>from opposed reviewers example


glXSwapIntervalSGI broken in some implementations

glXSwapIntervalSGI might not function in some implementations as described here. The "workaround" is to prioritize EXT and MESA before SGI.

Has been fixed through #779


Project title

Project title
(Write project title over here)
Project Description
(Describe the project over here)
Stack:
[ ] Html
[ ] CSS
[ ] JavaScript

Blog app code is not working


Fix theming in the audio bus editor

master version of https://github.com/godotengine/godot/pull/51113. Reverts https://github.com/godotengine/godot/pull/50593 and reimplements a new fix for https://github.com/godotengine/godot/issues/50583.
Now, in master tooltips look a bit off because they are windows now and it seem to introduce rendering inconsistencies (they seem to be bigger than the panel requires) and bugs (they don't seen to support alpha opacity). But these issues are beyond the matters of this PR.
https://user-images.githubusercontent.com/11782833/127750297-fa7266a5-c3d9-4fd4-89b9-52f62fed3fe7.mp4

Thanks!


bug(parser): debezium json parser incorrectly parses datetime value from mysql

Describe the bug
The connector node uses the debezium config time.precision.mode=adaptive_time_microseconds(default), which converts the datetime value type to i64 unix epoch time with a precision of milliseconds.
However, the json parser assumes the precision using the number of digits:
https://github.com/risingwavelabs/risingwave/blob/55d143839266b2bed178be74398746f2f5282cc7/src/expr/src/vector_op/cast.rs#L163-L185
The result is that dates outside of the range [1973-03-03 09:46:40, 5138-11-16 09:46:40) could be parsed incorrectly without a warning...
To Reproduce

insert a datetime 9999-12-31T23:59:59 into mysql
obtain the cdc json from debezium (9999-12-31T23:59:59 converted to<PHONE_NUMBER>99000, which has 15 digits)
the risingwave parser returns 1978-01-11T21:31:40.799 without a warning or error (since the parser uses a precision of microseconds with 15 digits)

Expected behavior
No response
Additional context
No response

@wangrunji0408

cc @xiangjinwu Any ideas?

The connector node uses the debezium config time.precision.mode=adaptive_time_microseconds(default), which converts the datetime value type to i64 unix epoch time with a precision of milliseconds.

As the issue itself shows, it is very easy to get microseconds vs milliseconds wrong.
We could document our timestamptz type as only supporting values in [1973-03-03 09:46:40, 5138-11-16 09:46:40). Anyways we are already not supporting the full range as PostgreSQL's 4713 BC - 294276 AD.
If we do want to be more compatible here, we should keep i64_to_timestamptz untouched. When the parser can make sure the input is microseconds in a specific context, call something like us_to_timestamptz rather than i64_to_timestamptz.

It is not possible for the parser to detect such an error, since the parser does not know the precision of the value (milli/micro)...
For example, 9999-12-31T23:59:59 is converted to microseconds by debezium, and the parser receives the value<PHONE_NUMBER>99000, which has 15 digits. The parser than assumes that it is in milliseconds, and returns 1978-01-11T21:31:40.799, and the parser has no trivial way of knowing thether this is correct or not!
Therefore I suggest that we document this issue, and ask the user to avoid timestamp/datetime values outside of our supported range [1973-03-03 09:46:40, 5138-11-16 09:46:40) in their source tables :)
@neverchanje

I have opened an issue here: https://github.com/risingwavelabs/risingwave-docs/issues/957 :)