Hello,
I open a new thread for the same, because other one is very big and not easy to understand (and quite old also)
I have tried to build by myself sakia on my mac, wiki instructions were accurate, but if I try to launch sakia.app nothing happens.
I have tried to download on some previous releases the sakia for macos build and it is the same, it just opens and closes immediately.
Finally, I tried to run sakia without building, but then it automatically plugs on g1.duniter.org:443 and I don’t know if it is from my side or from this site but if I activate debug, I see
DEBUG:node:connect_current_block:[Errno 1] Cannot connect to host g1.duniter.org:443 ssl:True [Can not connect to g1.duniter.org:443 [[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:645)]] : 4aCqw
And then I can not connect since the identity can’t be checked.
Would someone have some clues on what to do? I don’t see any option to start connecting to an other node and in the graphical interface, it seems there is not the option either.
So Inso, with your help, I have found how to fix first step of failing travis build.
But it continues to fail, and here possibly more complex to find why, since there are no precise errors I can see but a SIGABRT sent :
tests/functional/test_certification_dialog.py Server started on http://127.0.0.1:62855
.E
tests/functional/test_connection_cfg_dialog.py Server started on http://127.0.0.1:62879
Traceback (most recent call last):
File "/Users/florck/Documents/Perso/Duniter/sakia.git/src/sakia/gui/widgets/dialogs.py", line 7, in <lambda>
dialog.finished.connect(lambda r: future.set_result(r))
File "/Users/florck/.pyenv/versions/3.5.1/Python.framework/Versions/3.5/lib/python3.5/asyncio/futures.py", line 329, in set_result
raise InvalidStateError('{}: {!r}'.format(self._state, self))
asyncio.futures.InvalidStateError: FINISHED: <Future finished result=16384>
ci/travis/test.sh: line 26: 23051 Abort trap: 6 py.test -s
I have tried to play with breakpoints, without great success. If you have time for debugging with me later, I will try to find you on the chat !
Je penche pour un problème de temps de synchro car le soucis est aléatoire (sur 5 exécutions, 3 plantées) et du coup ça plante dans l’une ou l’autre des fonctions de test_connection_cfg_dialog suivant les moments…
Et il semblerait que ce soit ma modification qui introduit la régression car il cherche à cliquer yes dans la fenetre où y a que “ok” !
Comme je te disais sur le chat, mais tu étais pu connecté, c’est surtout le fait de cliquer sur un “yes” qui existe pas vraiment qui fait une sorte de faute de segmentation et suicide le python…
Je cherche une astuce pour savoir dans quelle messageBox je suis !
Pas le choix, y a que @Nartagnan qui accepte de me nourrir en échange de Ğ1. (3 pour la soirée jeux d’hier)
Pour info, j’utilise sakia sans aucun de problème sous mac, même si je n’ai pas retesté l’installation depuis les packages. Je le lance direct en python ! #pratique