Produire Cesium Desktop

MickaelLarose · 7 November 2017 21:50

Ça ne marche toujours pas

Mickaël@LAPTOP-BTQ6SATM MINGW64 ~/cesium-desktop (master)
$ ./release.sh 0.19.3
nvm (Node version manager) not found (directory NVM_DIR not defined). Please install nvm, and retry
Checking that 0.19.3 has been pushed to 'origin'...
Remote tag: v0.19.3
Creating the pre-release if it does not exist...
Release v0.19.3 already exists. Skips creation.
Missing asset: cesium-desktop-v0.19.3-windows-x64.exe
Starting Windows build...
>> Copying Cesium Desktop sources...
>> Starting Vagrant Windows VM...
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'unknown' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.
>> Something went wrong. Stopping build.
==> default: Attempting graceful shutdown of VM...
    default: Guest communication could not be established! This is usually because
    default: SSH is not running, the authentication information was changed,
    default: or some other networking issue. Vagrant will force halt, if
    default: capable.
==> default: Forcing shutdown of VM...
>> VM closed.
Release: v0.19.3
Uploading asset cesium-desktop-v0.19.3-windows-x64.exe...
{ Error: ENOENT: no such file or directory, stat 'C:\Users\Suzena\cesium-desktop\arch\windows\cesium-desktop-v0.19.3-windows-x64.exe'
    at Object.fs.statSync (fs.js:948:11)
    at C:\Users\Suzena\cesium-desktop\scripts\upload-release.js:48:22
    at Generator.next (<anonymous>)
    at onFulfilled (C:\Users\Suzena\cesium-desktop\node_modules\co\index.js:65:19)
    at C:\Users\Suzena\cesium-desktop\node_modules\co\index.js:54:5
    at new Promise (<anonymous>)
    at co (C:\Users\Suzena\cesium-desktop\node_modules\co\index.js:50:10)
    at githubUpload (C:\Users\Suzena\cesium-desktop\scripts\upload-release.js:47:10)
    at C:\Users\Suzena\cesium-desktop\scripts\upload-release.js:24:11
    at Generator.next (<anonymous>)
    at onFulfilled (C:\Users\Suzena\cesium-desktop\node_modules\co\index.js:65:19)
    at <anonymous>
  errno: -4058,
  code: 'ENOENT',
  syscall: 'stat',
  path: 'C:\\Users\\Suzena\\cesium-desktop\\arch\\windows\\cesium-desktop-v0.19.3-windows-x64.exe' }
All the binaries have been uploaded.

jytou · 7 November 2017 21:56

Si tu ouvres directement le programme virtualbox, est-ce que tu as une machine virtuelle installée? Dans quel état est-elle? Peux-tu la désinstaller et relancer la procédure pour voir? Combien as-tu de place disque disponible à l’endroit où le disque de la VM est stocké (probablement sur C: par défaut) ?

@cgeek ce message n’indique-t-il pas que nvm n’est pas présent sur le système (ce qui évidemment peut être un problème…)?

MickaelLarose · 7 November 2017 22:03

Oui j’ai une machine virtuelle installée mais je ne serais pas te dire dans quel état elle se trouve ^^
Tu es sûr ? Je ne peux pas modifier quelque chose et ré-essayer avant de le supprimer et de relancer ?
272 Go de libre ^^

jytou · 7 November 2017 22:12

Essaye de supprimer et de relancer. Ça ne va pas tout retélécharger, pas d’inquiétude là-dessus, il va juste recréer la VM proprement à partir de l’image que tu as téléchargée.
Si dans ton terminal tu tapes juste nvm ça te donne quoi?

MickaelLarose · 7 November 2017 22:14

Ok, je vais essayer

Ça me donne ça :

$ nvm

Running version 1.1.6.

Usage:

  nvm arch                     : Show if node is running in 32 or 64 bit mode.
  nvm install <version> [arch] : The version can be a node.js version or "latest                                                                                                                " for the latest stable version.
                                 Optionally specify whether to install the 32 or                                                                                                                 64 bit version (defaults to system arch).
                                 Set [arch] to "all" to install 32 AND 64 bit ve                                                                                                                rsions.
                                 Add --insecure to the end of this command to by                                                                                                                pass SSL validation of the remote download server.
  nvm list [available]         : List the node.js installations. Type "available                                                                                                                " at the end to see what can be installed. Aliased as ls.
  nvm on                       : Enable node.js version management.
  nvm off                      : Disable node.js version management.
  nvm proxy [url]              : Set a proxy to use for downloads. Leave [url] b                                                                                                                lank to see the current proxy.
                                 Set [url] to "none" to remove the proxy.
  nvm node_mirror [url]        : Set the node mirror. Defaults to https://nodejs                                                                                                                .org/dist/. Leave [url] blank to use default url.
  nvm npm_mirror [url]         : Set the npm mirror. Defaults to https://github.                                                                                                                com/npm/npm/archive/. Leave [url] blank to default url.
  nvm uninstall <version>      : The version must be a specific version.
  nvm use [version] [arch]     : Switch to use the specified version. Optionally                                                                                                                 specify 32/64bit architecture.
                                 nvm use <arch> will continue using the selected                                                                                                                 version, but switch to 32/64 bit mode.
  nvm root [path]              : Set the directory where nvm should store differ                                                                                                                ent versions of node.js.
                                 If <path> is not set, the current root will be                                                                                                                 displayed.
  nvm version                  : Displays the current running version of nvm for                                                                                                                 Windows. Aliased as v.

jytou · 7 November 2017 22:16

Ok, du coup je ne comprends pas le message d’erreur

Mais bon, réessaie, on va bien voir.

MickaelLarose · 7 November 2017 22:48

Voilà le résultat :

Mickaël@LAPTOP-BTQ6SATM MINGW64 ~/cesium-desktop (master)
$ ./release.sh 0.19.3
nvm (Node version manager) not found (directory NVM_DIR not defined). Please install nvm, and retry
Checking that 0.19.3 has been pushed to 'origin'...
Remote tag: v0.19.3
Creating the pre-release if it does not exist...
Release v0.19.3 already exists. Skips creation.
Missing asset: cesium-desktop-v0.19.3-windows-x64.exe
Starting Windows build...
>> Copying Cesium Desktop sources...
>> Starting Vagrant Windows VM...
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'https://s3.eu-central-1.amazonaws.com/duniter/vagrant/duniter_win7.box'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: windows_default_1510094379491_63050
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: The guest additions on this VM do not match the installed version of
    default: VirtualBox! In most cases this is fine, but in rare cases it can
    default: prevent things such as shared folders from working properly. If you see
    default: shared folder errors, please make sure the guest additions within the
    default: virtual machine match the version of VirtualBox you have installed on
    default: your host and reload your VM.
    default:
    default: Guest Additions Version: 5.0.32
    default: VirtualBox Version: 5.1
==> default: Mounting shared folders...
    default: /vagrant => C:/Users/Suzena/cesium-desktop/arch/windows
An error occurred in the underlying SSH library that Vagrant uses.
The error message is shown below. In many cases, errors from this
library are caused by ssh-agent issues. Try disabling your SSH
agent or removing some keys and try again.

If the problem persists, please report a bug to the net-ssh project.

timeout during server version negotiating
>> Something went wrong. Stopping build.
==> default: Attempting graceful shutdown of VM...
    default: Guest communication could not be established! This is usually because
    default: SSH is not running, the authentication information was changed,
    default: or some other networking issue. Vagrant will force halt, if
    default: capable.
==> default: Forcing shutdown of VM...
>> VM closed.
Release: v0.19.3
Uploading asset cesium-desktop-v0.19.3-windows-x64.exe...
{ Error: ENOENT: no such file or directory, stat 'C:\Users\Suzena\cesium-desktop\arch\windows\cesium-desktop-v0.19.3-windows-x64.exe'
    at Object.fs.statSync (fs.js:948:11)
    at C:\Users\Suzena\cesium-desktop\scripts\upload-release.js:48:22
    at Generator.next (<anonymous>)
    at onFulfilled (C:\Users\Suzena\cesium-desktop\node_modules\co\index.js:65:19)
    at C:\Users\Suzena\cesium-desktop\node_modules\co\index.js:54:5
    at new Promise (<anonymous>)
    at co (C:\Users\Suzena\cesium-desktop\node_modules\co\index.js:50:10)
    at githubUpload (C:\Users\Suzena\cesium-desktop\scripts\upload-release.js:47:10)
    at C:\Users\Suzena\cesium-desktop\scripts\upload-release.js:24:11
    at Generator.next (<anonymous>)
    at onFulfilled (C:\Users\Suzena\cesium-desktop\node_modules\co\index.js:65:19)
    at <anonymous>
  errno: -4058,
  code: 'ENOENT',
  syscall: 'stat',
  path: 'C:\\Users\\Suzena\\cesium-desktop\\arch\\windows\\cesium-desktop-v0.19.3-windows-x64.exe' }
All the binaries have been uploaded.

jytou · 7 November 2017 23:11

Pas mieux, donc. J’avoue que là je ne vois pas.
Il y a le message d’erreur nvm qui est bizarre. Et puis ça

Je n’ai pas eu ce message de mon côté. Il y a vraisemblablement un micmac avec tes clés ssh, mais quoi…

cgeek · 8 November 2017 13:21

Oui mais c’est une illusion (comme Mickaël est sur Windows, il n’a pas la variable d’export de NVM qui est demandée par le script). Mais peu importe vu que le sens de cette vérification c’est d’avoir NodeJS 6.

Tu es sûr ? Car justement c’est un trousseau volontairement “non sécurisé”, proposé spécifiquement par Vagrant. C’est tout à fait normal.

À mon avis le problème est là :

Or où est-ce que ça plante ?

Je viens de vérifier, et effectivement sur ma machine j’ai Virtualbox 5.0.40_Ubuntu. Alors @MickaelLarose, je te conseille de désinstaller ton VirtualBox actuel et d’installer cette version à la place :

http://download.virtualbox.org/virtualbox/5.0.40/VirtualBox-5.0.40-115130-Win.exe

jytou · 8 November 2017 13:45

De mon côté j’ai un virtualbox ubuntu 5.1.30r118389. Et je n’ai pas eu de problème particulier.

cgeek · 8 November 2017 13:46

Oui, mais tu as un Ubuntu … la librairie SSH n’est peut-être pas la même, et alors le conflit peut apparaître. Je ne sais pas !

jytou · 8 November 2017 14:16

C’est là qu’on se rend compte que l’informatique est quantique. On nous vend que c’est des 0 et des 1 alors que ce sont déjà des qbits.

MickaelLarose · 8 November 2017 19:51

Ok, je vais essayer

MickaelLarose · 8 November 2017 20:40

Nouvel échec

Mickaël@LAPTOP-BTQ6SATM MINGW64 ~/cesium-desktop (master)
$ ./release.sh 0.19.3
nvm (Node version manager) not found (directory NVM_DIR not defined). Please install nvm, and retry
Checking that 0.19.3 has been pushed to 'origin'...
Remote tag: v0.19.3
Creating the pre-release if it does not exist...
Release v0.19.3 already exists. Skips creation.
Missing asset: cesium-desktop-v0.19.3-windows-x64.exe
Starting Windows build...
>> Copying Cesium Desktop sources...
>> Starting Vagrant Windows VM...
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'https://s3.eu-central-1.amazonaws.com/duniter/vagrant/duniter_win7.box'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: windows_default_1510173190667_63036
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'paused' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.
>> Something went wrong. Stopping build.
==> default: Unpausing the VM...
==> default: Attempting graceful shutdown of VM...
    default: Guest communication could not be established! This is usually because
    default: SSH is not running, the authentication information was changed,
    default: or some other networking issue. Vagrant will force halt, if
    default: capable.
==> default: Forcing shutdown of VM...
>> VM closed.
Release: v0.19.3
Uploading asset cesium-desktop-v0.19.3-windows-x64.exe...
{ Error: ENOENT: no such file or directory, stat 'C:\Users\Suzena\cesium-desktop\arch\windows\cesium-desktop-v0.19.3-windows-x64.exe'
    at Object.fs.statSync (fs.js:948:11)
    at C:\Users\Suzena\cesium-desktop\scripts\upload-release.js:48:22
    at Generator.next (<anonymous>)
    at onFulfilled (C:\Users\Suzena\cesium-desktop\node_modules\co\index.js:65:19)
    at C:\Users\Suzena\cesium-desktop\node_modules\co\index.js:54:5
    at new Promise (<anonymous>)
    at co (C:\Users\Suzena\cesium-desktop\node_modules\co\index.js:50:10)
    at githubUpload (C:\Users\Suzena\cesium-desktop\scripts\upload-release.js:47:10)
    at C:\Users\Suzena\cesium-desktop\scripts\upload-release.js:24:11
    at Generator.next (<anonymous>)
    at onFulfilled (C:\Users\Suzena\cesium-desktop\node_modules\co\index.js:65:19)
    at <anonymous>
  errno: -4058,
  code: 'ENOENT',
  syscall: 'stat',
  path: 'C:\\Users\\Suzena\\cesium-desktop\\arch\\windows\\cesium-desktop-v0.19.3-windows-x64.exe' }
All the binaries have been uploaded.

MickaelLarose · 11 November 2017 19:31

Salut !

J’ai un petit problème avec cesium desktop pour windows depuis que j’ai installé les différents logiciels pour la compilation. Lorsque je lance cesium, il ne s’affiche pas à l’écran. Dans la barre des tâches, je peux visualisé dans la mini-fenêtre de visualisation la page Cesium mais quand je clique, rien n’apparaît à l’écran
Une solution à me proposer ?

jytou · 11 November 2017 21:35

Tu dois avoir probablement des erreurs dans les logs pour comprendre d’où vient le problème.