View Issue Details

IDProjectCategoryView StatusLast Update
0004732Talerotherpublic2017-06-06 12:18
ReporterMarcello Stanisci Assigned ToMarcello Stanisci Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PriorityhighSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Versiongit (master) 
Target Version0.3Fixed in Version0.3 
Summary0004732: "conflict" case /track frontends
DescriptionBoth frontends need to handle the '409 Conflict' status returned by the backend as response for /track/transfer and /track/transaction.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Marcello Stanisci

2016-10-27 14:37

reporter   ~0011394

In 59a9320 each frontend renders the conflict error. Since the JSON returned
contains lots of information, it's still to be decided how the error page should look like.

Christian Grothoff

2016-10-30 10:38

manager   ~0011396

I think we should output the key points: which transaction and which wire transfer caused the conflict (i.e. transaction X was both supposed to be covered by wire transfer Y and also supposed to be NOT covered by wire transfer Y). The rest of the JSON is cryptographic proof and we should just have a way to "download cryptographic evidence" which allows the user to export the JSON to file. Ideally, we'd later have a command-line tool to check such 'evidence' files (in court); but such tools can wait for now IMO.

Marcello Stanisci

2016-11-02 20:08

reporter   ~0011402

Error messages rendered, export json missing.

Marcello Stanisci

2016-11-03 16:32

reporter   ~0011415

The logic to save the file has been added. Some testing is needed now!

Marcello Stanisci

2016-11-04 16:19

reporter   ~0011429

Last edited: 2016-11-04 16:19

(Local) testing is currently blocked by 0004754, as it's still not possible to
withdraw/buy/aggregate to get a workable wtid.

Marcello Stanisci

2016-11-07 15:51

reporter   ~0011444

Waiting for 0004762.

Marcello Stanisci

2016-11-16 22:02

reporter   ~0011499

Waiting for 0004781, this needs to be tested "by hand" by temporariliy patch
the merchant.

Marcello Stanisci

2016-11-28 13:50

reporter   ~0011550

This also needs the aggregator working fine (which is not quite always the case), as otherwise no tracking can happen.

Marcello Stanisci

2016-11-30 15:22

reporter   ~0011559

Do test also tutorial merchant on this.

Marcello Stanisci

2016-12-05 16:13

reporter   ~0011567

Last edited: 2016-12-05 16:39

Fixed in 85b0f7a8d (frontends) and 3b93f18 (tutorial site).

Issue History

Date ModifiedUsernameFieldChange
2016-10-15 21:35Marcello StanisciNew Issue
2016-10-15 21:35Marcello StanisciAssigned To => Marcello Stanisci
2016-10-15 21:35Marcello StanisciStatusnew => assigned
2016-10-26 20:09Marcello StanisciDescription Updated
2016-10-27 14:37Marcello StanisciNote Added: 0011394
2016-10-30 10:38Christian GrothoffNote Added: 0011396
2016-11-02 20:08Marcello StanisciNote Added: 0011402
2016-11-03 12:09Marcello StanisciPrioritynormal => high
2016-11-03 16:32Marcello StanisciNote Added: 0011415
2016-11-04 16:19Marcello StanisciNote Added: 0011429
2016-11-04 16:19Marcello StanisciNote Edited: 0011429
2016-11-07 15:51Marcello StanisciNote Added: 0011444
2016-11-15 14:54Christian GrothoffProduct Version => git (master)
2016-11-15 14:54Christian GrothoffTarget Version => 0.3
2016-11-16 22:02Marcello StanisciNote Added: 0011499
2016-11-28 13:50Marcello StanisciNote Added: 0011550
2016-11-30 15:22Marcello StanisciNote Added: 0011559
2016-12-05 16:13Marcello StanisciStatusassigned => informing
2016-12-05 16:13Marcello StanisciResolutionopen => fixed
2016-12-05 16:13Marcello StanisciNote Added: 0011567
2016-12-05 16:39Marcello StanisciNote Edited: 0011567
2017-01-16 09:19Christian GrothoffFixed in Version => 0.3
2017-06-06 12:18Christian GrothoffStatusinforming => closed