Opened 9 years ago

Last modified 9 years ago

#1398 defect closed fixed (fixed)

[newpb] implement a correct eventually(), use callLater rather than callFromThread

Reported by: glyph Owned by:
Priority: highest Milestone:
Component: Keywords:
Cc: glyph, itamarst, warner, jknight Branch:
Author: Launchpad Bug:

Description


Change History (6)

comment:1 Changed 9 years ago by glyph

Since I keep talking about this simple queue, I'm just going to fix the tests
with it.  This should fix the incorrect use of callFromThread and hopefully end
some of the discussion about what insane thing the reactor should be doing in
callLater.  I also notice that eventually is implemented twice; once in the
tests and once in the application code; I'll fix that too.

comment:2 Changed 9 years ago by glyph

I have created a branch for you called "eventually-1398".

Warner, if you could review this and see if it meets your needs for ordering
guarantees?  It does pass all the PB tests.

comment:3 Changed 9 years ago by glyph

Warner, should I merge this?

comment:4 Changed 9 years ago by warner

merged to trunk, r15512

comment:5 Changed 9 years ago by warner

hrm, I meant to mark this as resolved.. really..

comment:6 Changed 3 years ago by <automation>

  • Owner warner deleted
Note: See TracTickets for help on using tickets.