#581 closed defect (invalid)

time-out of results appears to happen before it is supposed to

Reported by: zooko Owned by:
Priority: major Milestone: 1.7.0
Component: code-frontend-web Version: 1.2.0
Keywords: usability wui Cc:
Launchpad Bug:

Description

I keep getting "unknown/expired handle 'xejkkdqay2ygimef2huncyxyci'". It is supposed to keep that around for 10 minutes once the job has completed. Perhaps it is expiring 10 minutes after it started instead of 10 minutes after it completed?

Change History (4)

comment:1 Changed at 2009-01-12T20:39:44Z by zooko

See related ticket #577 in which I request that we stop using timeouts entirely and remember each result until the user explictly tells us to forget that result, or the node is restarted.

comment:2 Changed at 2010-02-11T04:27:12Z by davidsarah

  • Component changed from code-frontend to code-frontend-web
  • Keywords usability wui added
  • Milestone changed from undecided to eventually

comment:3 Changed at 2010-02-27T08:52:31Z by davidsarah

  • Milestone changed from eventually to 1.7.0

Can this still be reproduced? #577 greatly increased the timeouts, and there are tests for ophandle expiry that look good to me.

comment:4 Changed at 2010-02-27T15:09:31Z by zooko

  • Resolution set to invalid
  • Status changed from new to closed

Closing this as invalid since I didn't write down enough detail to be persuasive to my future (now) self that I wasn't hallucinating.

Note: See TracTickets for help on using tickets.