winterstein / sogive-app

The SoGive user app - See your impact
Other
2 stars 5 forks source link

Dashboard seems to have a delay (?) #170

Open SanjayRedScarf opened 6 years ago

SanjayRedScarf commented 6 years ago

User a_joshiuk@yahoo.co.uk (who happens to be my Dad) tried to allocate his £10 of credit at Sightsavers at around 8am this morning (26th Dec 2017). He in fact succeeded, however when he went to the dashboard, his donation history was blank. However he later logged out and logged in again and it was populated.

He was surprised and confused about it being blank, and wanted reassurance that the transaction had gone ahead correctly.

Surely we would expect it to be populated immediately?

winterstein commented 6 years ago

At a guess, the dashboard caches the list of donations the first time you visit it. And the new-donation code doesn't invalidate that list. So you get stuck seeing the old version.

Old CS joke: There are only two hard problems in computer science: Naming things, cache invalidation problems, and off-by-one errors.

On 26 December 2017 at 10:42, SanjayLikesCharities <notifications@github.com

wrote:

User a_joshiuk@yahoo.co.uk (who happens to be my Dad) tried to allocate his £10 of credit at Sightsavers at around 8am this morning (26th Dec 2017). He in fact succeeded, however when he went to the dashboard, his donation history was blank. However he later logged out and logged in again and it was populated.

He was surprised and confused about it being blank, and wanted reassurance that the transaction had gone ahead correctly.

Surely we would expect it to be populated immediately?

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/winterstein/sogive-app/issues/170, or mute the thread https://github.com/notifications/unsubscribe-auth/AAPmsM57iB0Fi0AwU-j-0vnFvM17rKonks5tEM2wgaJpZM4RMros .

--

Dr Daniel Winterstein Director Edinburgh +44 (0)772 5172 612 http://sodash.com http://sogrow.co.uk

winterstein commented 6 years ago

NB: I'll fix this, but meanwhile, reloading the page should fix it.