View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004448 | Taler | exchange | public | 2016-04-19 14:11 | 2016-04-28 20:14 |
| Reporter | Florian Dold | Assigned To | Florian Dold | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | low | Severity | tweak | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 0.0 | ||||
| Target Version | 0.0 | Fixed in Version | 0.0 | ||
| Summary | 0004448: wire configuration is redundant | ||||
| Description | If I understand correctly, the wire configuration has overlapping informatin in the GNUnet-style configuration and in the JSON configuration. Could we just generate one from each other? | ||||
| Tags | No tags attached. | ||||
| related to | 0004460 | closed | Marcello Stanisci | simplify taler installation process |
| We should have some helper script that looks over the configuration and calls the necessary programs. We also need to have directory where all those wire files are put, just because stuff like test.json in the data directory root of taler looks confusing. | |
| I don't know what you think is redundant, AFAIK there is not anything redundant anymore at this point. Please clarify. | |
| Oh, I thought we needed the exchange-wire-incoming data both in the *.json file and the configuration. But it turns out I was wrong, and we read exchange-wire-incoming *only* from .json, and the exchange-wire-outgoing *only* from the GNUnet-style config. I'll update it on the server then. By the way, since last week the configuration for the deployments on taler.net is in deployment.git:config/, please consider updating it yourself when you make major changes again in the future. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2016-04-19 14:11 | Florian Dold | New Issue | |
| 2016-04-19 14:11 | Florian Dold | Status | new => assigned |
| 2016-04-19 14:11 | Florian Dold | Assigned To | => Christian Grothoff |
| 2016-04-19 14:11 | Florian Dold | Summary | wire configuration is redundent => wire configuration is redundant |
| 2016-04-22 15:18 | Florian Dold | Relationship added | related to 0004460 |
| 2016-04-22 16:02 | Florian Dold | Note Added: 0010543 | |
| 2016-04-24 21:50 | Christian Grothoff | Note Added: 0010555 | |
| 2016-04-24 21:50 | Christian Grothoff | Assigned To | Christian Grothoff => Florian Dold |
| 2016-04-24 21:50 | Christian Grothoff | Status | assigned => feedback |
| 2016-04-24 21:50 | Christian Grothoff | Priority | normal => low |
| 2016-04-24 21:50 | Christian Grothoff | Severity | minor => tweak |
| 2016-04-24 21:50 | Christian Grothoff | Product Version | => 0.0 |
| 2016-04-24 21:59 | Florian Dold | Note Added: 0010558 | |
| 2016-04-24 21:59 | Florian Dold | Status | feedback => assigned |
| 2016-04-24 22:09 | Florian Dold | Status | assigned => informing |
| 2016-04-24 22:09 | Florian Dold | Resolution | open => fixed |
| 2016-04-28 20:14 | Christian Grothoff | Status | informing => closed |
| 2016-04-28 20:14 | Christian Grothoff | Fixed in Version | => 0.0 |
| 2016-04-28 20:14 | Christian Grothoff | Target Version | => 0.0 |