Soichi Hayashi

Same issue here. ``` $ aws glacier list-vaults --account-id - [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:765) ``` I am not sure which hosts it's having a problem with, but I...

I tried installing `npm install vue-router@4` but that didn't cure it.. Installing vue-router@4 leads to another issue ``` node_modules/vue-gtag-next/vue-gtag-next.d.ts:2:25 - error TS2307: Cannot find module 'vue-router/types/router' or its corresponding type...

I've updated various packages and things and this issue disappeared. I am using the following set. ``` "dependencies": { "element-plus": "^1.1.0-beta.20", "numeral": "^2.0.6", "unplugin-vue-components": "^0.15.6", "vue": "^3.2.16", "vue-gtag-next": "^1.14.0", "vue-mapbox-ts":...

Sadly, the current implementation of forge.ssh.publicKeyToOpenSSH (and privateKeyToOpenSSH) only works with RSA key.

I think this happens on `multiple` also. Or.. it should clear the text on blur to let user know that he/she forgot to push enter and value wasn't entered. Leaving...

@TheChymera We just need a mechanism to know when to avoid upgrading our bids-specification that could break our services due to any format changes. It's been a while since I...

> The invalidation of a dataset by validator updates is due to increased coverage of the spec, This depends on the use-case, but for me, this means that the spec...

I am having a problem passing bids-validator with dataset with -desc.. like this. ``` └── sub-9002 └── ses-1 ├── anat │   ├── sub-9002_ses-1_desc-4_T2w.json │   ├── sub-9002_ses-1_desc-4_T2w.nii.gz │   ├── sub-9002_ses-1_T1w.json │  ...

humm.. ok. I was thinking something like multiple dwi with different PED.. but I guess I should set dir- entity in that case.

I just realized I could do this instead ``` OAuth2Strategy.prototype.authorizationParams = function(options) { return { selected_idp: options.idp } } router.get('/signin', function(req, res, next) { passport.authenticate('oauth2', { //this will be used...