Comment 3 for bug 94289

30 seconds? I just waited five minutes to see http://bazaar.launchpad.net/~kfogel/bzr/306394-status-tolerate-nonexistent/revision/3910 show up at the top of the list of revisions on https://code.edge.launchpad.net/~kfogel/bzr/306394-status-tolerate-nonexistent :-).

Had this conversation in IRC right afterwards, in which salgado explained what's going on:

<kfogel> So on
           https://code.edge.launchpad.net/~kfogel/bzr/306394-status-tolerate-nonexistent,
           the topmost change there (3910) took a while to show up.
           Is this normal?

<kfogel> I pushed it, and the push succeeded, and I could visit
           http://bazaar.launchpad.net/~kfogel/bzr/306394-status-tolerate-nonexistent/revision/3910
           manually and see the change.

<kfogel> But it did not show up in the list of changes at
           https://code.edge.launchpad.net/~kfogel/bzr/306394-status-tolerate-nonexistent
           for five or ten minutes; instead, 3909 stayed on top.

<salgado> kfogel, yes, that's normal. there's a script which scans
           branches for new revisions, which runs every few minutes,
           so it may take some time for revisions to show up on the
           web UI

<salgado> the web UI only reads that from the DB and the DB is
           populated by the branch scanner

<kfogel> salgado: ah. thanks. There's no other way to do this than
           by polling? I think (not sure yet, just suspecting) that
           it may be a typical use case to push a change and then want
           to point someone to it.

<salgado> kfogel, I guess it should be possible to tweak our bzr
           server to notify LP about the new revision when it's
           pushed, but I don't know how complicated that'd be

<salgado> kfogel, also, note that the revision doesn't show up in the
           UI, but if you pull/merge from the branch you'll see it

<salgado> you may have noticed that already

<salgado> abentley, would be the right man to talk about that. and
           even better, he seems to be today's help contact. :)

<kfogel> salgado: yup, it was there right away -- I was even able to
           see it via the web interface (if I manually guessed the
           URL).

<abentley> kfogel: There have been proposals to implement a messaging
           system. That would allow us to kick these processes off in
           a more event-driven manner. We also may eliminate the
           mirroring phase.