Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

There was a problem

You must be a member of this account.

ExecutableQueue rounds

#140

ExecutableQueue should be able to store rounds that effectively get appended when the current round expires. This will more closely emulate schema and solve some problems in Server.

Reported by bahuvrihi · January 25th, 2009 @ 06:06 PM

State: invalid
Milestone: none
Assigned to: bahuvrihi bahuvrihi

Activity

  1. bahuvrihi
    bahuvrihi

    This is also required to prevent a stop/start cycle for rounds. See http://bahuvrihi.lighthouseapp.c...

    February 11th, 2009 @ 05:06 PM

  2. bahuvrihi
    bahuvrihi
    • State changed from new to resolved
    • Assigned user set to bahuvrihi

    (from [3837fe81322fcd2222fb76c628c3604f2c3fcd32]) added rounds to ExecutableQueue and fixed stop bug [#140 ExecutableQueue rounds state:resolved responsible:bahuvrihi] [#148 Exe.run flubs stop/terminate state:resolved responsible:bahuvrihi] http://github.com/bahuvrihi/tap/...

    February 11th, 2009 @ 08:13 PM

  3. bahuvrihi
    bahuvrihi
    • State changed from resolved to open

    ExecutableQueue doesn't handle rounds cleanly. It will likely be best to introduce a RoundsQueue, or similar, to track rounds. Maybe even add this at the app level (app.rounds, providing an array of ExecutableQueues).

    February 16th, 2009 @ 10:30 AM

  4. bahuvrihi
    bahuvrihi
    • State changed from open to invalid

    ExecutableQueue no longer supports rounds.

    May 25th, 2009 @ 12:12 PM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.