View Issue Details

IDProjectCategoryView StatusLast Update
0004930Talerotherpublic2019-12-20 18:12
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
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Product Versiongit (master) 
Target Version0.6Fixed in Version0.6 
Summary0004930: Render 'conflict' errors due to /track operations.
Description'backoffice' category here.

Since no frontend returns HTML anymore when doing backoffice activity,
JS is in charge of rendering /track related errors.

In particular, conflicts related to /track operations contain non trivial
data that needs to be properly rendered.

Of course, other errors like 404 (e. g. "unknown order") are to be rendered too.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

The plan

IDSummaryStatusAssigned ToEstimated effort (hours)
0005365Caching results makes testing difficult. closedMarcello Stanisci
This issue (hours)
Its children (hours)0
Together (hours)0
Nothing is missing: the plan can be finished.

Relationships

parent of 0005365 closedMarcello Stanisci Caching results makes testing difficult. 
child of 0005303 closedMarcello Stanisci Resume the back-office site. 

Activities

Marcello Stanisci

2018-03-27 09:43

reporter   ~0012898

This issue doesn't depend on the twister anymore,
as one is now usable. Deleting its "child" status.

Marcello Stanisci

2018-06-26 13:05

reporter   ~0013082

It's right that the Twister is not a blocker for this anymore, but the situation is still pending: the merchant returns cached results for /track operations and so twisting the communication between the merchant backend and the exchange helps very little (helps just on the very first request merchant->exchange).

Marcello Stanisci

2018-06-26 13:41

reporter   ~0013083

A possible solution is to generate X trackable transactions and NOT make them fall under the same aggregation. This way, manual testing can be done on those X entries. As of X, the bigger the better.

Marcello Stanisci

2018-06-29 10:01

reporter   ~0013113

Manually tested on Tripwire, thanks to 0005365 and 0005366.

Marcello Stanisci

2018-06-29 10:02

reporter   ~0013114

0005366 not related here anymore, because it's more a wishlist than a bug now.

Issue History

Date ModifiedUsernameFieldChange
2017-03-04 09:49Marcello StanisciNew Issue
2017-03-04 09:49Marcello StanisciAssigned To => Marcello Stanisci
2017-03-04 09:49Marcello StanisciStatusnew => assigned
2017-03-04 09:50Marcello StanisciDescription Updated
2017-03-05 23:24Christian GrothoffProduct Version => git (master)
2017-03-05 23:24Christian GrothoffTarget Version => 0.3
2017-04-30 11:31Marcello StanisciRelationship addedchild of 0004782
2017-04-30 11:31Marcello StanisciRelationship deletedchild of 0004782
2017-04-30 11:32Marcello StanisciRelationship addedchild of 0004781
2017-04-30 14:54Christian GrothoffTarget Version0.3 => 0.6
2018-03-27 09:43Marcello StanisciNote Added: 0012898
2018-03-27 09:43Marcello StanisciRelationship deletedchild of 0004781
2018-06-08 09:21Marcello StanisciDescription Updated
2018-06-26 13:05Marcello StanisciNote Added: 0013082
2018-06-26 13:25Marcello StanisciRelationship addedchild of 0005303
2018-06-26 13:26Marcello StanisciRelationship addedparent of 0005366
2018-06-26 13:26Marcello StanisciRelationship addedparent of 0005365
2018-06-26 13:41Marcello StanisciNote Added: 0013083
2018-06-29 10:01Marcello StanisciNote Added: 0013113
2018-06-29 10:02Marcello StanisciNote Added: 0013114
2018-06-29 10:02Marcello StanisciRelationship deletedparent of 0005366
2018-06-29 10:03Marcello StanisciStatusassigned => informing
2018-06-29 10:03Marcello StanisciResolutionopen => fixed
2018-09-15 09:06Christian GrothoffFixed in Version => 0.6
2019-12-20 18:12Christian GrothoffStatusinforming => closed