Ho creato una FAQ nel readme

In risposta alla confusione indotta dal fatto che a quanto pare il DEVEL.md è troppo lungo e/o non si trova, ho aggiunto al README.md in home page una FAQ delle procededure.

Mi verificate che si capisce e che è corretta?

Ho fatto una PR per proporre alcune modifiche alla documentazione, alcuni punti, secondo me, potevano essere confusi e ho provato a renderli più chiari (forse anche troppo :slight_smile:, ma meglio abbondare) e ho spostato le istruzioni di installazione dei vari SO in un file separato perché forse il DEVEL.md era poco letto perché la parte di Windows occupava metà del file :slight_smile: e dopo la prima installazione diventava inutile

Ecco un caso di esempio:
l’ultima volta ho sviluppato i test, ho fatto la PR e quindi stava funzionando tutto. Successivamente mi volevo mettere a lavorare sui test, ho fatto ripartire l’ambiente, ho avuto problemi, ho cancellato i container, ma non ho sbloccato la situazione (ho fatto un casino e non mi ricordo come :slight_smile: ). In ogni caso ora mi trovo in questa situazione:

  • se lancio qualsiasi comando iosdk ovviamente mi dice command not found
  • se lancio docker ps non ho nessun container
  • se lancio docker images ho questa risposta:
REPOSITORY                    TAG                 IMAGE ID            CREATED             SIZE
pagopa/iosdk-theia            master              bc40218670fc        4 days ago          1.94GB
pagopa/iosdk-openwhisk        master              074b93265721        4 days ago          1.38GB
openwhisk/action-nodejs-v10   nightly             d1ab9a3d1eae        5 days ago          974MB
redis                         5                   aa27923130e6        3 weeks ago         98.4MB
pagopa/action-python-v3.7     2020-11-16          a09642f6b94f        3 weeks ago         1.08GB
pagopa/openwhisk-standalone   2020-10-21          8f027180ffc1        7 weeks ago         1.37GB
pagopa/theia                  2020.06.08          51e0bae4f405        6 months ago        1.94GB

A questo punto provo a rifare l’installazione da capo:

  1. lancio bash setup e ottengo questa risposta:
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?
  1. quindi accedo come root e rieseguo il comando, sembra andar tutto ok ma ricevo questo errore:
WARNING: You are using pip version 19.2.3, however version 20.3.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
npm ERR! prepareGitDep 1> 
npm ERR! prepareGitDep > core-js@2.6.12 postinstall /root/.npm/_cacache/tmp/git-clone-04f098ca/node_modules/core-js
npm ERR! prepareGitDep > node -e "try{require('./postinstall')}catch(e){}"
npm ERR! prepareGitDep 
npm ERR! prepareGitDep 
npm ERR! prepareGitDep > @adobe/aio-lib-core-config@1.2.8 postinstall /root/.npm/_cacache/tmp/git-clone-04f098ca/node_modules/@adobe/aio-lib-core-config
npm ERR! prepareGitDep > patch-package
npm ERR! prepareGitDep 
npm ERR! prepareGitDep 
npm ERR! prepareGitDep 2> npm WARN install Usage of the `--dev` option is deprecated. Use `--only=dev` instead.
npm ERR! prepareGitDep npm WARN deprecated core-js@2.6.12: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm ERR! prepareGitDep npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm ERR! prepareGitDep npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm ERR! prepareGitDep npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm ERR! prepareGitDep npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
npm ERR! prepareGitDep npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm ERR! prepareGitDep npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm ERR! prepareGitDep npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm ERR! prepareGitDep sh: 1: patch-package: Permission denied
npm ERR! prepareGitDep npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/jest-haste-map/node_modules/fsevents):
npm ERR! prepareGitDep npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! prepareGitDep npm WARN eslint-config-xo-space@0.20.0 requires a peer of eslint@^5.3.0 but none is installed. You must install peer dependencies yourself.
npm ERR! prepareGitDep npm WARN tsutils@3.17.1 requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
npm ERR! prepareGitDep 
npm ERR! prepareGitDep npm ERR! code ELIFECYCLE
npm ERR! prepareGitDep npm ERR! syscall spawn
npm ERR! prepareGitDep npm ERR! file sh
npm ERR! prepareGitDep npm ERR! errno ENOENT
npm ERR! prepareGitDep npm ERR! @adobe/aio-lib-core-config@1.2.8 postinstall: `patch-package`
npm ERR! prepareGitDep npm ERR! spawn ENOENT
npm ERR! prepareGitDep npm ERR! 
npm ERR! prepareGitDep npm ERR! Failed at the @adobe/aio-lib-core-config@1.2.8 postinstall script.
npm ERR! prepareGitDep npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! prepareGitDep 
npm ERR! prepareGitDep npm ERR! A complete log of this run can be found in:
npm ERR! prepareGitDep npm ERR!     /root/.npm/_logs/2020-12-13T17_50_51_569Z-debug.log
npm ERR! prepareGitDep 
npm ERR! prepareGitDep 1> 
npm ERR! prepareGitDep > husky@4.2.3 install /root/.npm/_cacache/tmp/git-clone-51e74e8f/node_modules/husky
npm ERR! prepareGitDep > node husky install
npm ERR! prepareGitDep 
npm ERR! prepareGitDep 
npm ERR! prepareGitDep 2> npm WARN install Usage of the `--dev` option is deprecated. Use `--only=dev` instead.
npm ERR! prepareGitDep npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm ERR! prepareGitDep npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm ERR! prepareGitDep internal/modules/cjs/loader.js:883
npm ERR! prepareGitDep   throw err;
npm ERR! prepareGitDep   ^
npm ERR! prepareGitDep 
npm ERR! prepareGitDep Error: Cannot find module '/root/.npm/_cacache/tmp/git-clone-51e74e8f/node_modules/husky/husky'
npm ERR! prepareGitDep     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
npm ERR! prepareGitDep     at Function.Module._load (internal/modules/cjs/loader.js:725:27)
npm ERR! prepareGitDep     at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
npm ERR! prepareGitDep     at internal/main/run_main_module.js:17:47 {
npm ERR! prepareGitDep   code: 'MODULE_NOT_FOUND',
npm ERR! prepareGitDep   requireStack: []
npm ERR! prepareGitDep }
npm ERR! prepareGitDep npm ERR! code ELIFECYCLE
npm ERR! prepareGitDep npm ERR! errno 1
npm ERR! prepareGitDep npm ERR! husky@4.2.3 install: `node husky install`
npm ERR! prepareGitDep npm ERR! Exit status 1
npm ERR! prepareGitDep npm ERR! 
npm ERR! prepareGitDep npm ERR! Failed at the husky@4.2.3 install script.
npm ERR! prepareGitDep npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! prepareGitDep 
npm ERR! prepareGitDep npm ERR! A complete log of this run can be found in:
npm ERR! prepareGitDep npm ERR!     /root/.npm/_logs/2020-12-13T17_50_53_029Z-debug.log
npm ERR! prepareGitDep 
npm ERR! premature close

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2020-12-13T17_50_53_065Z-debug.log

quindi non è una buona idea lanciarlo da root…

  1. se lancio source source-me-first ottengo questa risposta che mi sembra corretta
Client: Docker Engine - Community
 Version:           19.03.14
 API version:       1.40
 Go version:        go1.13.15
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.14
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.13.15
  Experimental:     false
 containerd:
  Version:          1.3.9
 runc:
  Version:          1.0.0-rc10
 docker-init:
  Version:          0.18.0
Node v12.18.0
Python 3.7.7
go version go1.13.12 linux/amd64

Ora, al di là che non mi ricordo come sono arrivato a questa situazione di casino :slight_smile: (e probabilmente sarebbe stata utile per trovare una soluzione), ma come me probabilmente altri si troveranno in una situazione simile… come se ne viene fuori?

Ho provato a cancellare il file con i permessi di root e a rilanciare il comando, ma il risultato è lo stesso.
Il file /var/lib/dpkg/lock-frontend viene creato dal setup di iosdk?

Hai un processo (penso l’updater) che blocca apt e quindi il setup (che fa delle installazioni) non riesce a fare il suo lavoro.

GLi errori che ottieni vengono dal fatto che mancano dipendenze essenziali come il gcc che non hai potuto completare

Vedi qui

Stoppa l’updater e completa il setup…

grazie per il link, ma purtroppo non è quello il problema.

Il processo non è bloccato, ma non ho i permessi, così faccio “sudo su” gli do i permessi e procede, ma completa con errori.

Ho reinstallato Ubuntu 20.04.1 LTS così da avere una situazione pulita, ma già da subito ho lo stesso problema di permesso e concedendo i permessi di root ho l’errore simile al precedende, ma cambia alcuni dettagli, riporto la parte saliente:

WARNING: You are using pip version 19.2.3, however version 20.3.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
npm ERR! prepareGitDep 1> 
npm ERR! prepareGitDep > husky@4.2.3 install /root/.npm/_cacache/tmp/git-clone-b5bbc20c/node_modules/husky
npm ERR! prepareGitDep > node husky install
npm ERR! prepareGitDep 
npm ERR! prepareGitDep 
npm ERR! prepareGitDep 2> npm WARN install Usage of the `--dev` option is deprecated. Use `--only=dev` instead.
npm ERR! prepareGitDep npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm ERR! prepareGitDep npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm ERR! prepareGitDep sh: 1: node: Permission denied
npm ERR! prepareGitDep npm ERR! code ELIFECYCLE
npm ERR! prepareGitDep npm ERR! syscall spawn
npm ERR! prepareGitDep npm ERR! file sh
npm ERR! prepareGitDep npm ERR! errno ENOENT
npm ERR! prepareGitDep npm ERR! husky@4.2.3 install: `node husky install`
npm ERR! prepareGitDep npm ERR! spawn ENOENT
npm ERR! prepareGitDep npm ERR! 
npm ERR! prepareGitDep npm ERR! Failed at the husky@4.2.3 install script.
npm ERR! prepareGitDep npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! prepareGitDep 
npm ERR! prepareGitDep npm ERR! A complete log of this run can be found in:
npm ERR! prepareGitDep npm ERR!     /root/.npm/_logs/2020-12-20T08_48_21_326Z-debug.log
npm ERR! prepareGitDep 
npm ERR! prepareGitDep 1> 
npm ERR! prepareGitDep > core-js@2.6.12 postinstall /root/.npm/_cacache/tmp/git-clone-d429609d/node_modules/core-js
npm ERR! prepareGitDep > node -e "try{require('./postinstall')}catch(e){}"
npm ERR! prepareGitDep 
npm ERR! prepareGitDep 
npm ERR! prepareGitDep 2> npm WARN install Usage of the `--dev` option is deprecated. Use `--only=dev` instead.
npm ERR! prepareGitDep npm WARN deprecated core-js@2.6.12: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm ERR! prepareGitDep npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm ERR! prepareGitDep npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm ERR! prepareGitDep npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm ERR! prepareGitDep npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart()
npm ERR! prepareGitDep npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm ERR! prepareGitDep npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm ERR! prepareGitDep npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm ERR! prepareGitDep sh: 1: node: Permission denied
npm ERR! prepareGitDep npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/jest-haste-map/node_modules/fsevents):
npm ERR! prepareGitDep npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! prepareGitDep npm WARN eslint-config-xo-space@0.20.0 requires a peer of eslint@^5.3.0 but none is installed. You must install peer dependencies yourself.
npm ERR! prepareGitDep npm WARN tsutils@3.17.1 requires a peer of typescript@>=2.8.0 || >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
npm ERR! prepareGitDep 
npm ERR! prepareGitDep npm ERR! code ELIFECYCLE
npm ERR! prepareGitDep npm ERR! syscall spawn
npm ERR! prepareGitDep npm ERR! file sh
npm ERR! prepareGitDep npm ERR! errno ENOENT
npm ERR! prepareGitDep npm ERR! core-js@2.6.12 postinstall: `node -e "try{require('./postinstall')}catch(e){}"`
npm ERR! prepareGitDep npm ERR! spawn ENOENT
npm ERR! prepareGitDep npm ERR! 
npm ERR! prepareGitDep npm ERR! Failed at the core-js@2.6.12 postinstall script.
npm ERR! prepareGitDep npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! prepareGitDep 
npm ERR! prepareGitDep npm ERR! A complete log of this run can be found in:
npm ERR! prepareGitDep npm ERR!     /root/.npm/_logs/2020-12-20T08_48_22_768Z-debug.log
npm ERR! prepareGitDep 
npm ERR! premature close

I processi non sono bloccati e questa volta mi richiede di lanciare setup.sh perché non è mai stato eseguito completamente, a differenza dalla precedente volta

simone@SIMPORT:~/Dev/magicianred/io-sdk$ source source-me-first
You need to run 'bash setup.sh' first
simone@SIMPORT:~/Dev/magicianred/io-sdk$ bash setup.sh
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?
simone@SIMPORT:~/Dev/magicianred/io-sdk$ sudo lsof /var/lib/dpkg/lock-frontend
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/125/gvfs
      Output information may be incomplete.
lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs
      Output information may be incomplete.
lsof: WARNING: can't stat() fuse file system /run/user/1000/doc
      Output information may be incomplete.
simone@SIMPORT:~/Dev/magicianred/io-sdk$ sudo killall apt apt-get
apt: no process found
apt-get: no process found

Provo ad installare la versione 18 di Ubuntu e cerco almeno di completare il lavoro dei test

Simone, confermo quanto riporti (si blocca durante npm su “husky”, uscito fuori in una delle ultime commit)

premetto che il problema mi sembra chiaramente che nin riesci ad esegure apt-get

fai bash -x setup.sh e posta illog

questo l’output senza permessi di root

simone@SIMPORT:~/Dev/magicianred/io-sdk$ bash -x setup.sh
+ set -e
+ export NODENV_VERSION=12.18.0
+ NODENV_VERSION=12.18.0
+ export PYENV_VERSION=3.7.7
+ PYENV_VERSION=3.7.7
+ export GOENV_VERSION=1.13.12
+ GOENV_VERSION=1.13.12
+ export LOCAL=/home/simone/.local
+ LOCAL=/home/simone/.local
+ export BIN=/home/simone/.local/bin
+ BIN=/home/simone/.local/bin
+ mkdir -p /home/simone/.local/bin
+ case "$(uname)" in
++ uname
+ test -e /etc/os-release
+ source /etc/os-release
++ NAME=Ubuntu
++ VERSION='20.04.1 LTS (Focal Fossa)'
++ ID=ubuntu
++ ID_LIKE=debian
++ PRETTY_NAME='Ubuntu 20.04.1 LTS'
++ VERSION_ID=20.04
++ HOME_URL=https://www.ubuntu.com/
++ SUPPORT_URL=https://help.ubuntu.com/
++ BUG_REPORT_URL=https://bugs.launchpad.net/ubuntu/
++ PRIVACY_POLICY_URL=https://www.ubuntu.com/legal/terms-and-policies/privacy-policy
++ VERSION_CODENAME=focal
++ UBUNTU_CODENAME=focal
+ case "$VERSION_CODENAME" in
+ echo -e '8\n41\n'
+ apt-get install -y libicu-dev libvpx-dev
E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?

Cavolo! HO capito.

Confermo tutto! Avete ragione.

Qui:

                (bionic) sudo apt-get install -y libicu60 libvpx5 ;;
                 (focal) echo -e "8\n41\n" | apt-get install -y libicu-dev libvp

manca sudo di fronte a apt-get, solo per ubuntu 20

Inoltre ho riprodotto il problema di npm.

Il sudo è colpa mia, l’npm devo capirlo.

provo a correggere.

2 Mi Piace

grazie :slight_smile:

Dovrei aver “sistemato” e mergiato le pull requests. E aggiunto una faq sulla relativa instabilità del master.

Fatemi sapere.

il comando bash setup.sh sembra andar bene ora, termina in questo modo:

WARNING: You are using pip version 19.2.3, however version 20.3.3 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   926  100   926    0     0   2095      0 --:--:-- --:--:-- --:--:--  2090
Downloading the standalone nim distribution for Linux from https://apigcp.nimbella.io/downloads/nim/nim-v1.10.2/nim-v1.10.2-linux-x64.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 39.2M  100 39.2M    0     0  3282k      0  0:00:12  0:00:12 --:--:-- 3270k
Removing old installation, if any, and swapping in the new
Removing old symlink, if any, from /usr/local/bin and establishing the new
Installation complete

il comando source source-me-first:

>     Client: Docker Engine - Community
>      Version:           20.10.1
>      API version:       1.41
>      Go version:        go1.13.15
>     Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.24/version: dial unix /var/run/docker.sock: connect: permission denied
>      Context:           default
>      Experimental:      true
>     Node v12.18.0
>     Python 3.7.7
>     go version go1.13.12 linux/amd64

il make invece:

make build 
make[1]: Entering directory '/home/simone/Dev/pagopa/io-sdk'
echo "checking required versions"
checking required versions
node -v | grep v12
v12.18.0
python3 -V | grep 3.7
Python 3.7.7
go version | grep go1.13
go version go1.13.12 linux/amd64
make -C admin
make[2]: Entering directory '/home/simone/Dev/pagopa/io-sdk/admin'
echo "Checking you did not forget to do source ../source-me-first"
Checking you did not forget to do source ../source-me-first
node -v | grep v12

v12.18.0
cd web && npm install && npm run build
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

added 786 packages from 383 contributors and audited 787 packages in 8.025s

31 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities


> svelte-app@1.0.0 build /home/simone/Dev/pagopa/io-sdk/admin/web
> rollup -c


src/main.js → public/app/build/bundle.js...
  1365 |     		try {
  1366 |     			const response = await ioSDKService.getCustomConnectors();
> 1367 |     			customConnectors.update(connectors => response?.details?.connectors || []);
       |     			                                              ^ Unexpected token: punc (.)
  1368 |     		} catch(e) {
  1369 |     			console.log(e);
  1370 |     		}
[!] (plugin terser) SyntaxError: Unexpected token: punc (.)
SyntaxError: Unexpected token: punc (.)
    at ee (/home/simone/Dev/pagopa/io-sdk/admin/web/node_modules/terser/dist/bundle.min.js:1:19541)
    at c (/home/simone/Dev/pagopa/io-sdk/admin/web/node_modules/terser/dist/bundle.min.js:1:28244)
    at l (/home/simone/Dev/pagopa/io-sdk/admin/web/node_modules/terser/dist/bundle.min.js:1:28335)
    at f (/home/simone/Dev/pagopa/io-sdk/admin/web/node_modules/terser/dist/bundle.min.js:1:28388)
    at G (/home/simone/Dev/pagopa/io-sdk/admin/web/node_modules/terser/dist/bundle.min.js:1:42202)
    at ge (/home/simone/Dev/pagopa/io-sdk/admin/web/node_modules/terser/dist/bundle.min.js:1:48272)
    at /home/simone/Dev/pagopa/io-sdk/admin/web/node_modules/terser/dist/bundle.min.js:1:49152
    at be (/home/simone/Dev/pagopa/io-sdk/admin/web/node_modules/terser/dist/bundle.min.js:1:49167)
    at ze (/home/simone/Dev/pagopa/io-sdk/admin/web/node_modules/terser/dist/bundle.min.js:1:50421)
    at qe (/home/simone/Dev/pagopa/io-sdk/admin/web/node_modules/terser/dist/bundle.min.js:1:50653)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! svelte-app@1.0.0 build: `rollup -c`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the svelte-app@1.0.0 build 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/simone/.npm/_logs/2020-12-20T14_20_46_997Z-debug.log
make[2]: *** [Makefile:40: web/public/build/bundle.js] Error 1
make[2]: Leaving directory '/home/simone/Dev/pagopa/io-sdk/admin'
make[1]: *** [Makefile:9: build] Error 2
make[1]: Leaving directory '/home/simone/Dev/pagopa/io-sdk'
make: *** [Makefile:5: branch] Error 2

sembrerebbe che la sintassi col ? interrogativo del javascript non gli piaccia, l’ho sostituita con

customConnectors.update( connectors => response && response.details && response.details.connectors ? response.details.connectors : [] );

è presente nei file:

  • admin/web/src/Connectors.svelte
  • admin/web/src/Menu.svelte

Cambiata quella sintassi (ma non l’ho provata) sembra che compili, ma ho questo errore

docker build -t pagopa/iosdk-openwhisk:master .
Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Post http://%2Fvar%2Frun%2Fdocker.sock/v1.24/build?buildargs=%7B%7D&cachefrom=%5B%5D&cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile&labels=%7B%7D&memory=0&memswap=0&networkmode=default&rm=1&shmsize=0&t=pagopa%2Fiosdk-openwhisk%3Amaster&target=&ulimits=null&version=1: dial unix /var/run/docker.sock: connect: permission denied
make[2]: *** [Makefile:6: build] Error 1
make[2]: Leaving directory '/home/simone/Dev/pagopa/io-sdk/admin'
make[1]: *** [Makefile:9: build] Error 2
make[1]: Leaving directory '/home/simone/Dev/pagopa/io-sdk'
make: *** [Makefile:5: branch] Error 2

Dovrebbe essere relativo anche a questo warning del source-me-first

Got permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get http://%2Fvar%2Frun%2Fdocker.sock/v1.24/version: dial unix /var/run/docker.sock: connect: permission denied

ho provato a seguire le istruzioni di questa pagina ma il gruppo per docker esiste già (mi ricordo che una delle precedenti volte avevo fatto questi passaggi ed era andato)

Ho mergiato delle modifiche di @Sf3ris e come ho scritto nella FAQ ora il master potrebbe essere instabile ma le mergio appunto per consentire il test. Alla fine abbiamo le release per le versioni stabili.

Ho tentato di creare un branch devel ma ha fatto più confusione che beneficio e quindi ora accetto il master potenzialmente instabile come in molti progetti.

@Sf3ris che ne dici?

Sono d accordo con la scelta di tenere il master come upstream e le release come versione stable.
Ci da un bel vantaggio in ambito CI e testing, e rimane piu chiaro secondo me.

Avete qualche feedback per la patch dei connettori?

se parli di quello che ho segnalato io, mettendo l’operatore ternario il problema di compilazione si è risolto

Mi mandi la PR per io-gateway-connectors così cominciamo a creare anche il repositori dei connettori