View Issue Details

IDProjectCategoryView StatusLast Update
0005303Talerotherpublic2019-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
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status closedResolutionfixed 
Product Version0.5 
Target Version0.6Fixed in Version0.6 
Summary0005303: Resume the back-office site.
DescriptionThe back-office can be re-deployed. There is a _slight_ dependency on 0004930,
but nothing that prevents it from being put on-line again. Various landing pages,
home pages should also restore their links to the back-office site.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

The plan

IDSummaryStatusAssigned ToEstimated effort (hours)
0004930Render 'conflict' errors due to /track operations. closedMarcello Stanisci
This issue (hours)
Its children (hours)0
Together (hours)0
Nothing is missing: the plan can be finished.

Relationships

parent of 0004930 closedMarcello Stanisci Render 'conflict' errors due to /track operations. 

Activities

Marcello Stanisci

2018-06-05 16:21

reporter   ~0012981

Last edited: 2018-06-05 16:23

When pressing the Esc button from the /track/transfer
page, the logic should (make the popup disappear AND)
stop the ongoing operation.

Marcello Stanisci

2018-06-06 09:50

reporter   ~0012982

Dropping the suggestion from the last note: it complicates things quite
unnecessarily.

Marcello Stanisci

2018-06-08 17:35

reporter   ~0013033

Deployed, but manual testing is needed before linking it in the other sites.

Marcello Stanisci

2018-06-14 13:13

reporter   ~0013040

Did manual tests under normal circumstances, but now need to conduct "twisty" tests before closing this issue. Note, twisting between the merchant and the exchange during /track operations is very bad now: the merchant uses to store
into the database the result of a track operation, and so it uses the cached
result for any future request on the same input.

There should be some way of forcing the merchant to query the exchange _every_
time, or some other tecnique that makes it easier to produce twister-based corner cases (like 424 Failed dependency)

Marcello Stanisci

2018-06-29 10:53

reporter   ~0013116

Resumed at commit 26ac0148dec4b1b5906.. (landing.git),
and from all the other sites having the left-side pane
with all Taler sites links.

Issue History

Date ModifiedUsernameFieldChange
2018-03-27 09:59Marcello StanisciNew Issue
2018-03-27 15:27Christian GrothoffAssigned To => Marcello Stanisci
2018-03-27 15:27Christian GrothoffSeverityminor => feature
2018-03-27 15:27Christian GrothoffStatusnew => assigned
2018-06-05 16:21Marcello StanisciNote Added: 0012981
2018-06-05 16:23Marcello StanisciNote Edited: 0012981
2018-06-06 09:50Marcello StanisciNote Added: 0012982
2018-06-08 17:35Marcello StanisciNote Added: 0013033
2018-06-14 13:13Marcello StanisciNote Added: 0013040
2018-06-26 13:25Marcello StanisciRelationship addedparent of 0004930
2018-06-29 10:53Marcello StanisciStatusassigned => informing
2018-06-29 10:53Marcello StanisciResolutionopen => fixed
2018-06-29 10:53Marcello StanisciNote Added: 0013116
2018-09-15 09:06Christian GrothoffFixed in Version => 0.6
2019-12-20 18:12Christian GrothoffStatusinforming => closed