duniter issueshttps://git.duniter.org/nodes/typescript/duniter/-/issues2020-05-05T18:31:49+02:00https://git.duniter.org/nodes/typescript/duniter/-/issues/1403Add bash auto completion for duniter cli commands2020-05-05T18:31:49+02:00Vincent TexierAdd bash auto completion for duniter cli commandsFollowing this tutorial, we can add an auto-completion script for bash in the repository.
https://iridakos.com/programming/2018/03/01/bash-programmable-completion-tutorial
It will ease the duniter cli commands use.Following this tutorial, we can add an auto-completion script for bash in the repository.
https://iridakos.com/programming/2018/03/01/bash-programmable-completion-tutorial
It will ease the duniter cli commands use.1.8Vincent TexierVincent Texierhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1367Display stored public key with wizard key command2020-10-04T18:56:02+02:00MoulDisplay stored public key with wizard key command1.9https://git.duniter.org/nodes/typescript/duniter/-/issues/1258add WS2P into wizard network command2020-10-04T18:42:39+02:00Éloïsadd WS2P into wizard network command2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1404In the cli help, arguments use bracket [argument] or <argument>2020-10-04T18:30:14+02:00Vincent TexierIn the cli help, arguments use bracket [argument] or <argument>The cli --help use two different syntax to specify arguments.
`[argument]` or `<argument>`
We should use only one.
I recommend `[argument]`.The cli --help use two different syntax to specify arguments.
`[argument]` or `<argument>`
We should use only one.
I recommend `[argument]`.1.9https://git.duniter.org/nodes/typescript/duniter/-/issues/1335Have command specific options2019-01-29T12:17:41+01:00MoulHave command specific optionscf https://www.npmjs.com/package/commander#command-specific-options
This is really annoying to find which option apply to which command.
There is some specifics option only for `sync` command for instance.
They should only be accessib...cf https://www.npmjs.com/package/commander#command-specific-options
This is really annoying to find which option apply to which command.
There is some specifics option only for `sync` command for instance.
They should only be accessible via `duniter sync -h` and not via `duniter -h`.
General options which can apply to many commands should stay at the root of the help.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1312Wizard network fails if no interface in conf.json2019-04-09T22:25:06+02:00TuxicomanWizard network fails if no interface in conf.jsonI manually edited the conf.json to remove the network interfaces entries.
Then when launching the wizard to set them again I get this error :
```
$ duniter wizard network
2018-10-22T18:00:38+02:00 - debug: Plugging file system...
2018-...I manually edited the conf.json to remove the network interfaces entries.
Then when launching the wizard to set them again I get this error :
```
$ duniter wizard network
2018-10-22T18:00:38+02:00 - debug: Plugging file system...
2018-10-22T18:00:38+02:00 - debug: Loading conf...
2018-10-22T18:00:39+02:00 - error: Error: No interface to listen to.
at onLoading (/opt/duniter/app/modules/bma/index.js:157:31)
at FileDAL.server.dal.loadConfHook (/opt/duniter/index.js:286:31)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:160:7
```
1.7https://git.duniter.org/nodes/typescript/duniter/-/issues/1215Petite erreur dans l'aide du terminal Duniter2018-01-19T10:23:36+01:00Cédric MoreauPetite erreur dans l'aide du terminal Duniter*Created by: LeoBoudet*
Il y a une inversion entre les définitions de **--ws2p-host <host>** et **--ws2p-port <port>**.
(Je ne sais pas s'il est pertinent de le signaler ici particulièrement, si vous considérez qu'il y a mieux pour s...*Created by: LeoBoudet*
Il y a une inversion entre les définitions de **--ws2p-host <host>** et **--ws2p-port <port>**.
(Je ne sais pas s'il est pertinent de le signaler ici particulièrement, si vous considérez qu'il y a mieux pour signaler ces petites coquilles, je suis à l'écoute.)https://git.duniter.org/nodes/typescript/duniter/-/issues/1198Should be able to set PoW threads count in config.json2017-12-03T00:43:43+01:00nanocrykShould be able to set PoW threads count in config.json1.7ÉloïsÉloïshttps://git.duniter.org/nodes/typescript/duniter/-/issues/1162use --keyprompt in daemon mode2021-01-04T13:13:05+01:00Éloïsuse --keyprompt in daemon modeCurrently, the `--keyprompt` option works only in `direct_start` mode.Currently, the `--keyprompt` option works only in `direct_start` mode.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1074port/remoteport might be stored as a string2018-01-27T07:27:43+01:00Cédric Moreauport/remoteport might be stored as a stringWhen using `duniter config --port 10902` for example, the port is stored as a string a leads to problems if UPnP is enabled, because a string is sent to UPnP devices which refuse the request.When using `duniter config --port 10902` for example, the port is stored as a string a leads to problems if UPnP is enabled, because a string is sent to UPnP devices which refuse the request.https://git.duniter.org/nodes/typescript/duniter/-/issues/1059Add a new option for `gen-next`: `--local-submit`2018-01-27T07:27:42+01:00Cédric MoreauAdd a new option for `gen-next`: `--local-submit`Using this option, `gen-next` command:
* would not require `host` and `port` parameters
* would send the generated block to local blockchain instead of the networkUsing this option, `gen-next` command:
* would not require `host` and `port` parameters
* would send the generated block to local blockchain instead of the network1.4.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1052`gen-next` command is broken since TS migration2018-01-27T07:27:43+01:00Cédric Moreau`gen-next` command is broken since TS migration1.4.0https://git.duniter.org/nodes/typescript/duniter/-/issues/995Simulate next inclusion of newcomers2018-01-27T07:27:44+01:00Cédric MoreauSimulate next inclusion of newcomersWhen we look at https://g1-monit.elois.org/willMembers?lg=fr, we always wonder which combinations will be used by Duniter to include new members.
It would be useful to be able to simulate this, by fixing the medianTime value of curren...When we look at https://g1-monit.elois.org/willMembers?lg=fr, we always wonder which combinations will be used by Duniter to include new members.
It would be useful to be able to simulate this, by fixing the medianTime value of current block temporarily, not in the DB.
For example, with this command:
```bash
duniter gen-next --show --check --at 1495731720
```
This would simulate the next block with a simulation that our current `medianTime = 1495731720`, which is 2017/5/25 19:02:00.1.3.0https://git.duniter.org/nodes/typescript/duniter/-/issues/991Wrong loading with autoStack in a module2018-01-27T07:27:44+01:00Cédric MoreauWrong loading with autoStack in a moduleWhen we make a new module, depending on `duniter` and calling `duniter.statics.autoStack()`, the stack tries to find the modules in `node_modules/duniter/package.json` instead of local `package.json`.
This behavior could be fixed by a...When we make a new module, depending on `duniter` and calling `duniter.statics.autoStack()`, the stack tries to find the modules in `node_modules/duniter/package.json` instead of local `package.json`.
This behavior could be fixed by adding a 2nd parameter to autoStack(), giving the directory where to look at:
```js
autoStack: (priorityModules, dir) => {
const pjson = require(path.join(dir || __dirname, './package.json'));
// [...]
}
```
And on the call side:
```js
const stack = require('duniter').statics.autoStack([{
name: 'duniter-hello',
required: require('./index')
}], __dirname)
```
Or with #989:
```js
require('duniter').statics.quickRun(__dirname, './index.js')
```1.3.0https://git.duniter.org/nodes/typescript/duniter/-/issues/989Add a "quickRun" method in duniter API2018-01-27T07:27:44+01:00Cédric MoreauAdd a "quickRun" method in duniter APIWhen making a Duniter module, for testing it, we always have to create a `run.js` file with the same boring code:
```js
"use strict"
const co = require('co')
const stack = require('duniter').statics.autoStack([{
name: 'duniter...When making a Duniter module, for testing it, we always have to create a `run.js` file with the same boring code:
```js
"use strict"
const co = require('co')
const stack = require('duniter').statics.autoStack([{
name: 'duniter-prover',
required: require('./index')
}])
co(function*() {
try {
yield stack.executeStack(process.argv)
} catch(e) {
console.error(e)
}
process.exit()
})
```
We could have some shortcut of it, wrapping above code:
```js
require('duniter').statics.quickRun('./index.js')
```1.3.0https://git.duniter.org/nodes/typescript/duniter/-/issues/969Add a `--slow` option for `sync` command2018-01-27T07:27:45+01:00Cédric MoreauAdd a `--slow` option for `sync` commandOn very low connections (< 100 Kb/s), the sync will likely fail at some point.
But it could work if the number of download slots was limited to 1. I've tested it, it works.
Also, there is a bug on local storage of downloaded chunks...On very low connections (< 100 Kb/s), the sync will likely fail at some point.
But it could work if the number of download slots was limited to 1. I've tested it, it works.
Also, there is a bug on local storage of downloaded chunks: they are not stored on a brand new installation, so when the download eventually fail, we have to start the whole download again.
Diagnostic: replace `localNumber == 0` by `localNumber <= 0` in the `downloadChunk` function.1.3.0https://git.duniter.org/nodes/typescript/duniter/-/issues/951`reset all` does not remove the keyring file2018-01-27T07:27:44+01:00Cédric Moreau`reset all` does not remove the keyring file1.3.0https://git.duniter.org/nodes/typescript/duniter/-/issues/945Allow to pass level argument to logs sub-command2017-11-28T16:49:16+01:00Cédric MoreauAllow to pass level argument to logs sub-command*Created by: M5oul*
Like:
```bash
duniter logs --loglevel trace
```*Created by: M5oul*
Like:
```bash
duniter logs --loglevel trace
```Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/940Make daemonizer like a normal module2018-01-27T07:27:45+01:00Cédric MoreauMake daemonizer like a normal moduleThe daemonizing process will be removed from `duniter.sh` to be like any normal module.The daemonizing process will be removed from `duniter.sh` to be like any normal module.1.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/938Add a `--loglevel` option2018-01-27T07:27:45+01:00Cédric MoreauAdd a `--loglevel` optionWhich could change the loglevel either in configuration or at runtime.Which could change the loglevel either in configuration or at runtime.1.2.0