sakia issueshttps://git.duniter.org/clients/python/sakia/-/issues2020-04-05T20:45:10+02:00https://git.duniter.org/clients/python/sakia/-/issues/158Add an help window to explain and present formula of the referentials2020-04-05T20:45:10+02:00insoAdd an help window to explain and present formula of the referentials*Created by: vtexier*
In the help menu, we should add an entry for a popup window explaining referentials.
The window could contain an help text and all the formula.
*Created by: vtexier*
In the help menu, we should add an entry for a popup window explaining referentials.
The window could contain an help text and all the formula.
futurehttps://git.duniter.org/clients/python/sakia/-/issues/569Make Sakia multi-currencies2020-03-23T11:26:34+01:00Cédric MoreauMake Sakia multi-currenciesI know, you may feel like this is a troll, but it's not.
I see that we can launch Sakia using a `--currency` parameter, and this tells me we are very close to have Sakia being able to switch between a currency and another.
Yet, the...I know, you may feel like this is a troll, but it's not.
I see that we can launch Sakia using a `--currency` parameter, and this tells me we are very close to have Sakia being able to switch between a currency and another.
Yet, there is no hurry. But this would be a huge improvement for final users :smile: futurehttps://git.duniter.org/clients/python/sakia/-/issues/797Support ScuttleButt keypair as credentials (duplicate #796)2020-03-23T11:23:24+01:00Vincent TexierSupport ScuttleButt keypair as credentials (duplicate #796)[ScuttleButt is a p2p social network of a new kind](https://scuttlebutt.nz/).
The ScuttleButt keypair created in $HOME/.ssb folder use the same elliptic algorithm than Duniter Ğ1.
So it is easy to handle an account using the ssb keypai...[ScuttleButt is a p2p social network of a new kind](https://scuttlebutt.nz/).
The ScuttleButt keypair created in $HOME/.ssb folder use the same elliptic algorithm than Duniter Ğ1.
So it is easy to handle an account using the ssb keypair as credentials.
For a start, just add a "Add account from scuttlebut account" button.futureVincent TexierVincent Texierhttps://git.duniter.org/clients/python/sakia/-/issues/757Translation to french doesn't work dark theme neither2020-03-01T11:56:52+01:00insoTranslation to french doesn't work dark theme neither*Created by: mcl12345*
In settings
Translation to french doesn't work
and dark theme neither
under Windows 7*Created by: mcl12345*
In settings
Translation to french doesn't work
and dark theme neither
under Windows 7futurehttps://git.duniter.org/clients/python/sakia/-/issues/703Bug with NULL membership data2018-03-12T17:18:03+01:00insoBug with NULL membership dataWith bad network connection, the "membership_written_on" can get NULL in the databaseWith bad network connection, the "membership_written_on" can get NULL in the databasefuturehttps://git.duniter.org/clients/python/sakia/-/issues/712Sakia 0.32 rc5 crush2018-03-12T17:17:05+01:00insoSakia 0.32 rc5 crush*Created by: JordanGuiz*
Ca plante dès la création du compte, à la sauvegarde du document de révocation.
Je suis sous XUbuntu.*Created by: JordanGuiz*
Ca plante dès la création du compte, à la sauvegarde du document de révocation.
Je suis sous XUbuntu.futurehttps://git.duniter.org/clients/python/sakia/-/issues/632Sakia 0.30.11 warnings2017-07-06T20:55:59+02:00insoSakia 0.30.11 warnings*Created by: galuel*
Lots of warnings when launching from a terminal (it was the same since many versions, it is not crucial to run it, but there might not appear if all dependencies were in !?) :
Ubuntu 16.10 / 64 bits :
```bash
...*Created by: galuel*
Lots of warnings when launching from a terminal (it was the same since many versions, it is not crucial to run it, but there might not appear if all dependencies were in !?) :
Ubuntu 16.10 / 64 bits :
```bash
$ sakia --currency g1
PyInstaller Bootloader 3.x
LOADER: executable is /opt/sakia/sakia.bin
LOADER: homepath is /opt/sakia
LOADER: _MEIPASS2 is NULL
LOADER: archivename is /opt/sakia/sakia.bin
LOADER: Extracting binaries
LOADER: Executing self as child
LOADER: set _MEIPASS2 to /opt/sakia
LOADER: LD_LIBRARY_PATH=/opt/sakia
PyInstaller Bootloader 3.x
LOADER: executable is /opt/sakia/sakia.bin
LOADER: homepath is /opt/sakia
LOADER: _MEIPASS2 is /opt/sakia
LOADER: archivename is /opt/sakia/sakia.bin
LOADER: Already in the child - running user's code.
LOADER: Python library: /opt/sakia/libpython3.5m.so.1.0
LOADER: Loaded functions from Python library.
LOADER: Manipulating environment (sys.path, sys.prefix)
LOADER: Pre-init sys.path is /opt/sakia/base_library.zip:/opt/sakia
LOADER: sys.prefix is /opt/sakia
LOADER: Setting runtime options
LOADER: Initializing python
LOADER: Overriding Python's sys.path
LOADER: Post-init sys.path is /opt/sakia/base_library.zip:/opt/sakia
LOADER: Setting sys.argv
LOADER: setting sys._MEIPASS
LOADER: importing modules from CArchive
LOADER: extracted struct
LOADER: callfunction returned...
LOADER: extracted pyimod01_os_path
LOADER: callfunction returned...
LOADER: extracted pyimod02_archive
LOADER: callfunction returned...
LOADER: extracted pyimod03_importers
LOADER: callfunction returned...
LOADER: Installing PYZ archive with Python modules.
LOADER: PYZ archive: out00-PYZ.pyz
LOADER: Running pyiboot01_bootstrap.py
LOADER: Running pyi_rth_qt5.py
LOADER: Running pyi_rth_qt5plugins.py
LOADER: Running pyi_rth_pkgres.py
LOADER: Running main.py
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:88:7: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:93:7: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:98:11: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:105:11: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:112:7: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:117:11: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:124:7: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:129:7: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:134:11: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:140:11: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:146:7: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:151:20: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:296:7: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:301:7: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:306:11: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:313:11: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:320:7: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:326:20: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:332:7: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:337:7: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:342:11: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:348:11: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:354:7: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:359:20: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:448:30: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:458:30: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:468:30: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:478:30: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:498:22: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:503:22: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:508:22: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets-assets.css:513:22: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:155:8: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:163:8: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:189:8: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:199:8: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:703:13: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:776:19: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:796:16: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1256:36: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1260:36: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1264:29: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1465:28: No property named '-gtk-icon-transform'
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1525:18: 'outline-radius' is not a valid property name
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1686:45: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1704:45: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1747:25: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1755:25: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1776:25: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1784:25: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1800:25: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1818:25: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:2027:19: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:2045:19: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:2164:2: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: unity.css:126:28: No property named '-gtk-icon-transform'
(sakia:8014): Gtk-WARNING **: Theme parsing error: nautilus.css:40:16: 'outline-radius' is not a valid property name
(sakia:8014): Gtk-WARNING **: Theme parsing error: gnome-panel.css:92:20: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gnome-panel.css:98:20: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gnome-panel.css:104:20: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: gnome-terminal.css:10:41: Missing name of pseudo-class
(sakia:8014): Gtk-WARNING **: Theme parsing error: unity-greeter.css:72:28: No property named '-gtk-icon-transform'
(sakia:8014): Gtk-WARNING **: Theme parsing error: calendar.css:9:18: 'outline-radius' is not a valid property name
```futurehttps://git.duniter.org/clients/python/sakia/-/issues/711Infinite critical error loop2017-07-06T20:54:51+02:00insoInfinite critical error loop*Created by: RavanH*
After fresh install and fist launch of Sakia, I get the first connexion screen. I fill out my account details and try to connect. Then it turns out that the dialog was about creating a new account, not connecting to...*Created by: RavanH*
After fresh install and fist launch of Sakia, I get the first connexion screen. I fill out my account details and try to connect. Then it turns out that the dialog was about creating a new account, not connecting to an existing one (which is not clear at all) because I get a message about the account credentials already existing on the network.
After that, I get a critical error dialog with these details:
Creating a client session outside of coroutine
client_session: <aiohttp.client.ClientSession object at 0x7f4d2870ec88>
Problem is that when closing the error dialog with OK, a new one just opens... I cannot get out of this error loop.
futurehttps://git.duniter.org/clients/python/sakia/-/issues/610Error bug report2017-04-29T12:30:38+02:00MoulError bug reportWith 0.30.7:
```bash
DEBUG:node:connect_peers:Received a peer : J78bP
ERROR:root:Task exception was never retrieved
future: <Task finished coro=<NetworkService.discovery_loop() done, defined at sakia/services/network.py:203> exceptio...With 0.30.7:
```bash
DEBUG:node:connect_peers:Received a peer : J78bP
ERROR:root:Task exception was never retrieved
future: <Task finished coro=<NetworkService.discovery_loop() done, defined at sakia/services/network.py:203> exception=RuntimeError('coroutine raised StopIteration',)>
Traceback (most recent call last):
File "sakia/services/network.py", line 226, in discovery_loop
StopIteration
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "asyncio/tasks.py", line 239, in _step
RuntimeError: coroutine raised StopIteration
DEBUG:node:connect_peers:Received a peer : BmDso
```futurehttps://git.duniter.org/clients/python/sakia/-/issues/347Search Tab : Own identity2017-04-08T14:19:30+02:00insoSearch Tab : Own identity*Created by: galuel*
By default when we open Sakia 0.11.14, in the search tab, it seems that we have :
- Members who signed own identity
- Members own identity has signed
- Some not-member pubkey (I can see in blue a "cgeek" not member...*Created by: galuel*
By default when we open Sakia 0.11.14, in the search tab, it seems that we have :
- Members who signed own identity
- Members own identity has signed
- Some not-member pubkey (I can see in blue a "cgeek" not member, and another "cgeek" member)
We lack own identity with a special color to identify it. It seems usefull to have own identity in order to control own information and ability to copy/paste own pubkey.
And also it lacks a field with the distance in this tab (said in another issue).
futureinsoinsohttps://git.duniter.org/clients/python/sakia/-/issues/486Link not clickable on Critical error window2017-04-08T14:04:14+02:00MoulLink not clickable on Critical error windowFurthermore, I can't close the window with the cross :smile:
With `Ok`, it close.
Furthermore, I can't close the window with the cross :smile:
With `Ok`, it close.
futurehttps://git.duniter.org/clients/python/sakia/-/issues/495Monetary Mass (UD) is not correct2017-04-08T13:48:52+02:00Cédric MoreauMonetary Mass (UD) is not correctGiven the fact we have 119 members, and c = 10%, we can't have more than 1190 UD as monetary mass.
![image](https://cloud.githubusercontent.com/assets/969136/17462467/5e41668e-5cae-11e6-8978-0d3693b26e28.png)
Given the fact we have 119 members, and c = 10%, we can't have more than 1190 UD as monetary mass.
![image](https://cloud.githubusercontent.com/assets/969136/17462467/5e41668e-5cae-11e6-8978-0d3693b26e28.png)
futurehttps://git.duniter.org/clients/python/sakia/-/issues/212Transactions: it is hard to differenciate the order of units2017-04-08T13:47:01+02:00Cédric MoreauTransactions: it is hard to differenciate the order of unitsI can see in my transactions list some units of order (a power of 10), for example `UD`, `cUD`, `pUD`, etc. I like the idea, but I feel it hard to read:
![image](https://cloud.githubusercontent.com/assets/969136/9957922/c39f8244-5e04-11...I can see in my transactions list some units of order (a power of 10), for example `UD`, `cUD`, `pUD`, etc. I like the idea, but I feel it hard to read:
![image](https://cloud.githubusercontent.com/assets/969136/9957922/c39f8244-5e04-11e5-9a1c-0635010f55a9.png)
Wouldn't it be good to also have colors to signify the order? Like for Euros: we know that yellow coins means `[0,10 ; 0,50]` and bronze means `[0,01 ; 0,05]`.
The colors could always be the same, and shift when another power of 10 is reached by the UD.
What do you think?
futurehttps://git.duniter.org/clients/python/sakia/-/issues/45Include duniter node in sakia2017-04-08T13:44:52+02:00insoInclude duniter node in sakia*Created by: galuel*
I suggest uCoin server can be managed from Cutecoin, since qbottorrent as a P2P client is also the P2P server, P2P architecture suppose any client can be also server.
*Created by: galuel*
I suggest uCoin server can be managed from Cutecoin, since qbottorrent as a P2P client is also the P2P server, P2P architecture suppose any client can be also server.
futurehttps://git.duniter.org/clients/python/sakia/-/issues/529A transaction in compact format cannot measure more than 100 lines2017-04-08T13:44:15+02:00Cédric MoreauA transaction in compact format cannot measure more than 100 linesThis is a V3 rule: https://github.com/duniter/duniter/blob/master/doc/Protocol.md#transactions
I am not sure Sakia respects this rule, but from Duniter 0.30.13 this kind of transaction will be refused.
This is a V3 rule: https://github.com/duniter/duniter/blob/master/doc/Protocol.md#transactions
I am not sure Sakia respects this rule, but from Duniter 0.30.13 this kind of transaction will be refused.
futurehttps://git.duniter.org/clients/python/sakia/-/issues/427Time precision on transaction tab2017-04-08T13:42:45+02:00insoTime precision on transaction tab*Created by: galuel*
While trying to send my second transaction, (I saw no problem for the first, bu I cannot be sure). I succeeded to make a screen capture of the error message notification :
![sakia020dev9](https://cloud.githubuserc...*Created by: galuel*
While trying to send my second transaction, (I saw no problem for the first, bu I cannot be sure). I succeeded to make a screen capture of the error message notification :
![sakia020dev9](https://cloud.githubusercontent.com/assets/5245398/15245388/708d11d0-1906-11e6-914e-37ffaf6acf70.png)
End the transaction is good in the transaction tab, so while seeing error message I made a "send" again, same error message, but then the same transaction was made two times...
![sakia020dev9_2](https://cloud.githubusercontent.com/assets/5245398/15245414/9c771818-1906-11e6-9e1b-aa488c93c4ab.png)
- missing hour in the transaction tab, could be helpfull to have it...
futurehttps://git.duniter.org/clients/python/sakia/-/issues/432Salt = "secret key" = "clé secrète" + password2017-04-08T13:40:23+02:00insoSalt = "secret key" = "clé secrète" + password*Created by: galuel*
Le "salt" n'est pas le"ID" mais pourtant lui-seul permet de se connecter associé au password. Donc le ID est inefficient techniquement autant que pratiquement, ce n'est qu'une information générale, tout comme le cha...*Created by: galuel*
Le "salt" n'est pas le"ID" mais pourtant lui-seul permet de se connecter associé au password. Donc le ID est inefficient techniquement autant que pratiquement, ce n'est qu'une information générale, tout comme le champ commentaire des transactions.
Mais il doit rester secret, il est alors aussi secret que le password, c'est une seconde couche de password, un "password secret" (alors que le password est déjà censé être secret !).
Donc pourquoi ne pas gérer un seul password, ou bien différencier deux niveaux de password ? Conceptuellement pour l'utilisateur ce serait plus clair, alors que tel que présentés, les concepts s'embrouillent et sont difficiles à comprendre pour une première utilisation.
Dans ce cas, il faut l'appeler du genre "phrase secrète" ou "clé secrète" un truc plus clair.
La connexion se fait alors par : "clé secrète" + password, puisque le tout suffit à se connecter. L'UID n'est qu'une information conceptuelle, sans intérêt technique (pas plus que le champ commentaire des transactions in-fine). L'UID peut-être utilisé à d'autres fins (notamment de consultation), mais c'est autre chose. Il vaut donc mieux orienter les utilisateurs vers les données nécessaires et pas les données secondaires (UID) en terme d'usage.
futureinsoinsohttps://git.duniter.org/clients/python/sakia/-/issues/614Nodes are not same color as they have same hash2017-04-08T13:39:42+02:00MoulNodes are not same color as they have same hashfuturehttps://git.duniter.org/clients/python/sakia/-/issues/265Display each endpoint as a different peer under Network tab2017-01-14T16:59:09+01:00MoulDisplay each endpoint as a different peer under Network tabSakia keep one node with the same uid. Other are not displayed.
Sakia keep one node with the same uid. Other are not displayed.
futurehttps://git.duniter.org/clients/python/sakia/-/issues/3133D WoT visualisation2017-01-14T16:57:51+01:00inso3D WoT visualisationIt would be great if we could visualize users like in 3D, with the oldest users being on the bottom :
http://trm.creationmonetaire.info/_images/probleme_des_trois_producteurs_2.png
It would be great if we could visualize users like in 3D, with the oldest users being on the bottom :
http://trm.creationmonetaire.info/_images/probleme_des_trois_producteurs_2.png
future