AppImage 64bits de Sakia 0.52.0

Je viens de créer une AppImage 64bits de Sakia 0.52.0.

https://git.duniter.org/clients/python/sakia/-/releases/0.52.0

Elle doit se lancer sur tous les Linux x86_64 (pas les ARMs) !

Attention : il faut ajouter les droits d’exécution !

Soit par l’interface graphique de votre système :

  • Bouton droit sur l’icône, dans propriétés, cocher « exécuter comme un programme ».

Ou en ligne de commande :

   chmod u+x Sakia-x86_64.AppImage

Puis exécuter le fichier en double cliquant dessus ou en tapant ./Sakia-x86_64.AppImage.

Si cela fonctionne bien, j’ajouterai la fabrication au CD et l’AppImage sera disponible dans les releases.

Merci de me faire des retours.

1 Like

Tu peux cliquer sur Attach a file pour ajouter un fichier.

1 Like

Sur Debian 10, j’ai des soucis, je ne lance pas l’AppImage. Je suis le tuto de debian-facile

~/Téléchargements$ ls | grep Sakia
-rwxrwxrwx 1 root root  134787112 sept. 20 12:46 Sakia-x86_64.AppImage
~/Téléchargements$ sudo chmod +x Sakia-x86_64.AppImage 
[sudo] Mot de passe de bob : 
~/Téléchargements$ ./Sakia-x86_64.AppImage 
execv error: No such file or directory
~/Téléchargements$ Sakia-x86_64.AppImage 
bash: Sakia-x86_64.AppImage : commande introuvable

et en changeant le propriétaire :

~/Téléchargements$ sudo chown bob:bob Sakia-x86_64.AppImage 
~/Téléchargements$ ./Sakia-x86_64.AppImage 
execv error: No such file or directory

Par défaut il n’a pas le droit d’exécution : chmod 744 Sakia-x86_64.AppImage

Même comme ça j’ai l’erreur execv error: No such file or directory

Il faut installer un truc pour faire marcher ça ?

Non, juste ajouter les droits en exécution… Je vais le préciser dans le billet.

J’ai compilé et testé sur une Ubuntu 18.04, mais je vais regarder ce qui plante.

Pff, c’est censé marché partout sans efforts… sauf pour le dev ! :sweat_smile:

[EDIT]
J’ai trouvé ! Pff, des outils qui créent automatiquement des scripts… bogués, à déboguer à la main !
Ça va pas être facile de faire un job gitlab CD…

J’ai corrigé le fichier (même lien) en utilisant un autre outil qui me permettra d’intégrer ce type de package dans la CD Gitlab.

Pourra servir pour Silkaj si ça marche !

Merci de tester à nouveau chez vous.

1 Like

Là ça marche ! :slight_smile:

Par contre la liste des transactions semble rester « Loading… » à l’infini. Les nœuds sont rouges ou oranges, mais parfois quelques uns sont verts, je ne sais pas comment en ajouter un à la main.

1 Like

Normalement, si tu laisses tourner, quand le dernier mois de la blockchain sera chargé, cela devrait se calmer.

On ne peut pas pour l’instant. Ça me démange aussi. Je dois ajouter plein de fonctionnalités sur la page réseau, mais l’année prochaine seulement faute de temps.

1 Like

Ping @Attilax, @Paulart, @kimamila, @elois, @cgeek, @Galuel, @Inso : Sakia est disponible en exécutable binaire pour tous les Linux x86_64 !

Rien à installer ! Juste télécharger le fichier Sakia-x86_64.AppImage dans les releases :

3 Likes

Cool ! Je viens de lancer, sous Ubuntu 18.04.5

sudo chmod a+x *.AppImage
sudo ./Sakia-x86_64.AppImage --currency=g1

Mais j’ai tout le temps l’erreur :
image

Comment peut on préciser le nœud que l’on souhaite interroger ? (Typiquement mon noeud local)

Et les logs debug associé :

DEBUG:meta:prepare:Initializing meta database
DEBUG:meta:upgrade_database:Begin upgrade of database...
DEBUG:meta:upgrade_database:End upgrade of database...
DEBUG:network:add_connector:D9D2z connected
DEBUG:network:add_connector:38MEA connected
DEBUG:network:add_connector:5cnvo connected
DEBUG:network:add_connector:8iVdp connected
DEBUG:network:add_connector:5cnvo connected
DEBUG:network:add_connector:38MEA connected
DEBUG:node:connect_peers:[D9D2z] ClientConnectorError:Cannot connect to host g1-monit.elois.org:10901 ssl:default [Nom ou service inconnu]
DEBUG:node:safe_request:[D9D2z] ClientConnectorError:Cannot connect to host g1-monit.elois.org:10901 ssl:default [Nom ou service inconnu]
DEBUG:node:request_peers:[D9D2z] Could not connect to any BMA endpoint
DEBUG:node:connect_current_block:[D9D2z] Cannot connect to host g1-monit.elois.org:10901 ssl:default [Nom ou service inconnu]: D9D2z
DEBUG:blockchain:initialize_blockchain:Requesting blockchain parameters
DEBUG:bma:verified_get:Requesting parameters on endpoint BASIC_MERKLED_API g1.duniter.fr 10901
DEBUG:bma:verified_get:Requesting parameters on endpoint BMAS g1.duniter.inso.ovh 443
DEBUG:bma:verified_get:Requesting parameters on endpoint BASIC_MERKLED_API g1.duniter.org 10901
DEBUG:bma:verified_get:Requesting parameters on endpoint BASIC_MERKLED_API g1-monit.elois.org 10901
DEBUG:bma:_verified_request:<class 'aiohttp.client_exceptions.ClientConnectorError'>
DEBUG:bma:_verified_request:<class 'aiohttp.client_exceptions.ClientConnectorError'>
DEBUG:node:connect_current_block:[38MEA] Connected successfully to block ws
DEBUG:node:request_peers:[38MEA] Error in peers reply: Error code 2012 - Peer not found
DEBUG:node:connect_current_block:[38MEA] Received a block
DEBUG:node:connect_peers:[38MEA] Connected successfully to peer ws
DEBUG:node:safe_request:[38MEA] ClientConnectorError:Cannot connect to host g1.duniter.fr:10901 ssl:default [Connect call failed ('192.168.0.4', 10901)]
DEBUG:node:request_peers:[38MEA] Could not connect to any BMA endpoint
DEBUG:bma:_verified_request:<class 'aiohttp.client_exceptions.ContentTypeError'>
DEBUG:node:connect_current_block:[5cnvo] Websocket block WSServerHandshakeError: 200, message='Invalid response status', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL3dzL2Jsb2Nr')
DEBUG:node:connect_peers:[5cnvo] Websocket peer WSServerHandshakeError: 200, message='Invalid response status', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL3dzL3BlZXI=')
DEBUG:node:safe_request:[5cnvo] ContentTypeError:0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL25ldHdvcmsvcGVlcmluZy9wZWVycz9sZWFmPQ==')
DEBUG:node:safe_request:[5cnvo] ContentTypeError:0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL25ldHdvcmsvcGVlcmluZy9wZWVycz9sZWFmPQ==')
DEBUG:node:connect_current_block:[5cnvo] Websocket block WSServerHandshakeError: 200, message='Invalid response status', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL3dzL2Jsb2Nr')
DEBUG:node:safe_request:[5cnvo] ContentTypeError:0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL25ldHdvcmsvcGVlcmluZy9wZWVycz9sZWFmPQ==')
DEBUG:node:request_peers:[5cnvo] Could not connect to any BMA endpoint
DEBUG:node:safe_request:[5cnvo] ContentTypeError:0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL25ldHdvcmsvcGVlcmluZy9wZWVycz9sZWFmPQ==')
DEBUG:node:request_peers:[5cnvo] Could not connect to any BMA endpoint
DEBUG:node:connect_current_block:[8iVdp] Connected successfully to block ws
DEBUG:node:connect_current_block:[8iVdp] Received a block
DEBUG:node:connect_peers:[8iVdp] Connected successfully to peer ws
DEBUG:node:connect_peers:[5cnvo] Websocket peer WSServerHandshakeError: 200, message='Invalid response status', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL3dzL3BlZXI=')
DEBUG:node:safe_request:[5cnvo] ContentTypeError:0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL25ldHdvcmsvcGVlcmluZy9wZWVycz9sZWFmPQ==')
DEBUG:node:safe_request:[5cnvo] ContentTypeError:0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL25ldHdvcmsvcGVlcmluZy9wZWVycz9sZWFmPQ==')
DEBUG:node:request_peers:[5cnvo] Could not connect to any BMA endpoint
DEBUG:node:connect_current_block:[5cnvo] Websocket block WSServerHandshakeError: 200, message='Invalid response status', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL3dzL2Jsb2Nr')
DEBUG:node:connect_peers:[5cnvo] Websocket peer WSServerHandshakeError: 200, message='Invalid response status', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL3dzL3BlZXI=')
DEBUG:node:safe_request:[5cnvo] ContentTypeError:0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL25ldHdvcmsvcGVlcmluZy9wZWVycz9sZWFmPQ==')
DEBUG:node:safe_request:[5cnvo] ContentTypeError:0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL25ldHdvcmsvcGVlcmluZy9wZWVycz9sZWFmPQ==')
DEBUG:node:safe_request:[5cnvo] ContentTypeError:0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL25ldHdvcmsvcGVlcmluZy9wZWVycz9sZWFmPQ==')
DEBUG:node:request_peers:[5cnvo] Could not connect to any BMA endpoint
DEBUG:node:connect_current_block:[5cnvo] Websocket block WSServerHandshakeError: 200, message='Invalid response status', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL3dzL2Jsb2Nr')
DEBUG:node:safe_request:[5cnvo] ContentTypeError:0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL25ldHdvcmsvcGVlcmluZy9wZWVycz9sZWFmPQ==')
DEBUG:node:request_peers:[5cnvo] Could not connect to any BMA endpoint
DEBUG:node:connect_peers:[38MEA] Connected successfully to peer ws
DEBUG:node:connect_current_block:[38MEA] Connected successfully to block ws
DEBUG:node:request_peers:[38MEA] Error in peers reply: Error code 2012 - Peer not found
DEBUG:node:connect_current_block:[38MEA] Received a block
DEBUG:node:safe_request:[38MEA] ClientConnectorError:Cannot connect to host g1.duniter.fr:10901 ssl:default [Connect call failed ('192.168.0.4', 10901)]
DEBUG:node:request_peers:[38MEA] Could not connect to any BMA endpoint
DEBUG:node:connect_peers:[5cnvo] Websocket peer WSServerHandshakeError: 200, message='Invalid response status', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL3dzL3BlZXI=')
DEBUG:node:safe_request:[5cnvo] ContentTypeError:0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL25ldHdvcmsvcGVlcmluZy9wZWVycz9sZWFmPQ==')
DEBUG:node:safe_request:[5cnvo] ContentTypeError:0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL25ldHdvcmsvcGVlcmluZy9wZWVycz9sZWFmPQ==')
DEBUG:node:request_peers:[5cnvo] Could not connect to any BMA endpoint
DEBUG:node:safe_request:[D9D2z] ClientConnectorError:Cannot connect to host g1-monit.elois.org:10901 ssl:default [Nom ou service inconnu]
DEBUG:node:request_ws2p_heads:[D9D2z] Could not connect to any BMA endpoint
DEBUG:node:request_ws2p_heads:[8iVdp] Connection to BMA succeeded (g1.duniter.org,443,BMAS)
DEBUG:node:request_ws2p_heads:[38MEA] Connection to BMA succeeded (g1.duniter.fr,443,BMAS)
DEBUG:node:request_ws2p_heads:[38MEA] Connection to BMA succeeded (g1.duniter.fr,443,BMAS)
DEBUG:node:safe_request:[5cnvo] ContentTypeError:0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL25ldHdvcmsvd3MycC9oZWFkcw==')
DEBUG:node:safe_request:[5cnvo] ContentTypeError:0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL25ldHdvcmsvd3MycC9oZWFkcw==')
DEBUG:node:safe_request:[5cnvo] ContentTypeError:0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL25ldHdvcmsvd3MycC9oZWFkcw==')
DEBUG:node:request_ws2p_heads:[5cnvo] Could not connect to any BMA endpoint
DEBUG:node:safe_request:[5cnvo] ContentTypeError:0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL25ldHdvcmsvd3MycC9oZWFkcw==')
DEBUG:node:request_ws2p_heads:[5cnvo] Could not connect to any BMA endpoint
DEBUG:network:check_ws2p_heads:E3B0C44298 -> 0000001279
DEBUG:network:check_ws2p_heads:Latest block changed: 358754
DEBUG:network:check_ws2p_heads:Start refresh
DEBUG:bma:_verified_request:<class 'concurrent.futures._base.TimeoutError'>
DEBUG:bma:verified_get:Exception in responses: Cannot connect to host g1.duniter.fr:10901 ssl:default [Connect call failed ('192.168.0.4', 10901)]
DEBUG:bma:verified_get:Exception in responses: 0, message='Attempt to decode JSON with unexpected mimetype: text/html', url=URL('https://yuno.inso.ovh/yunohost/sso/?r=aHR0cHM6Ly9nMS5kdW5pdGVyLmluc28ub3ZoL2Jsb2NrY2hhaW4vcGFyYW1ldGVycw==')
DEBUG:bma:verified_get:Exception in responses: <class 'concurrent.futures._base.TimeoutError'>
DEBUG:bma:verified_get:Exception in responses: Cannot connect to host g1-monit.elois.org:10901 ssl:default [Nom ou service inconnu]
DEBUG:node:connect_peers:[38MEA] Received a peer
DEBUG:node:connect_peers:[38MEA] Received a peer
DEBUG:network:handle_new_node:Stacking new peer document: 92VdBcvvCWVBc79kNHpqLceiyPuCxrCwNx1zLacsVy2L
DEBUG:network:handle_new_node:Stacking new peer document: 92VdBcvvCWVBc79kNHpqLceiyPuCxrCwNx1zLacsVy2L
DEBUG:node:connect_peers:[8iVdp] Received a peer
DEBUG:network:handle_new_node:Stacking new peer document: 92VdBcvvCWVBc79kNHpqLceiyPuCxrCwNx1zLacsVy2L
DEBUG:network:discovery_loop:New node found: 92VdB
DEBUG:node:from_peer:Node from peer: Node(currency='g1', pubkey='92VdBcvvCWVBc79kNHpqLceiyPuCxrCwNx1zLacsVy2L', endpoints=[<duniterpy.api.endpoint.WS2PEndpoint object at 0x7f9fdc159fd0>, <duniterpy.api.endpoint.WS2PEndpoint object at 0x7f9fdc159828>], peer_blockstamp=<duniterpy.documents.block_uid.BlockUID object at 0x7f9fdc159c50>, uid='', current_buid=<duniterpy.documents.block_uid.BlockUID object at 0x7f9fdc159c50>, current_ts=0, previous_buid=<duniterpy.documents.block_uid.BlockUID object at 0x7f9fdc159d30>, state=0, software='', version='', merkle_peers_root='01ba4719c80b6fe911b091a7c05124b64eeece964e09c058ef8f9805daca546b', merkle_peers_leaves=(), root=False, member=False, last_state_change=1600781488)

Bravo en tous cas !

1 Like

Pourras tu remplacer “g1.duniter.fr” par “g1.e-is.pro:443” ?
De même g1.duniter.org:10901 par g1.duniter.org:443 ?

Un conseil, ne jamais lancer en sudo !

La monnaie par défaut est déjà la g1, mais tu peux utiliser l’option pour g1-test.

Comment peut on préciser le nœud que l’on souhaite interroger ? (Typiquement mon noeud local)

C’est pour l’instant en dur dans un yaml packagé dans le binaire. :cry:

La liste est là :

Je vais faire les changements que tu demandes et livrer une 0.52.1.

Et faire un ticket pour pouvoir modifier les serveurs dans un fichier de config.

Merci pour tes retours !

1 Like

Au lancement j’ai l’erreur suivante :

image

Et aussi :

Résumé
An unhandled exception occured

----
Traceback (most recent call last):

File “/tmp/.mount_Sakia-6AhIuF/usr/python/lib/python3.6/site-packages/sakia/main.py”, line 217, in
main()

File “/tmp/.mount_Sakia-6AhIuF/usr/python/lib/python3.6/site-packages/sakia/main.py”, line 203, in main
window = MainWindowController.startup(app)

File “/tmp/.mount_Sakia-6AhIuF/usr/python/lib/python3.6/site-packages/sakia/gui/main_window/controller.py”, line 73, in startup
navigation = NavigationController.create(None, app)

File “/tmp/.mount_Sakia-6AhIuF/usr/python/lib/python3.6/site-packages/sakia/gui/navigation/controller.py”, line 69, in create
navigation.init_navigation()

File “/tmp/.mount_Sakia-6AhIuF/usr/python/lib/python3.6/site-packages/sakia/gui/navigation/controller.py”, line 116, in init_navigation
self.model.init_navigation_data()

File “/tmp/.mount_Sakia-6AhIuF/usr/python/lib/python3.6/site-packages/sakia/gui/navigation/model.py”, line 79, in init_navigation_data
self.navigation[3][“children”].append(self.create_node(connection))

File “/tmp/.mount_Sakia-6AhIuF/usr/python/lib/python3.6/site-packages/sakia/gui/navigation/model.py”, line 96, in create_node
“icon”: self.identity_icon(connection),

File “/tmp/.mount_Sakia-6AhIuF/usr/python/lib/python3.6/site-packages/sakia/gui/navigation/model.py”, line 141, in identity_icon
if self.identity_is_member(connection):

File “/tmp/.mount_Sakia-6AhIuF/usr/python/lib/python3.6/site-packages/sakia/gui/navigation/model.py”, line 207, in identity_is_member
connection.pubkey, connection.uid

File “/tmp/.mount_Sakia-6AhIuF/usr/python/lib/python3.6/site-packages/sakia/services/identities.py”, line 455, in get_identity
return self._identities_processor.get_identity(self.currency, pubkey, uid)

File “/tmp/.mount_Sakia-6AhIuF/usr/python/lib/python3.6/site-packages/sakia/data/processors/identities.py”, line 137, in get_identity
identities = self._identities_repo.get_all(currency=currency, pubkey=pubkey)

File “/tmp/.mount_Sakia-6AhIuF/usr/python/lib/python3.6/site-packages/sakia/data/repositories/identities.py”, line 118, in get_all
return [Identity(*data) for data in datas]

File “/tmp/.mount_Sakia-6AhIuF/usr/python/lib/python3.6/site-packages/sakia/data/repositories/identities.py”, line 118, in
return [Identity(*data) for data in datas]

File “”, line 14, in init
self.membership_written_on = __attr_converter_membership_written_on(membership_written_on)

ValueError: invalid literal for int() with base 10: ‘IN’

Bonjour,
moi ça marche bien sauf le bouton « explorer » qui me retourne une page blanche. J’ai testé un transfert qui a fonctionné.
ça a repris la configuration que j’avais déjà et donc il m’a directement affiché les informations sur mon compte

Tu as encore une ancienne config avec une format obsolete dans ton dossier $HOME/.config/sakia.

Tu dois supprimer le dossier $HOME/.config/sakia et redéclarer tes comptes dans Sakia.

C’est un problème que j’ai eu aussi et ai corriger comme ça.

1 Like

Oui, bien vu !

Tant que tu n’as pas utilisé le menu « Voir dans la TdC » sur un compte, la fenêtre est blanche.
C’est un petit bug pénible que je connais et dois corriger.