Mark Sapiro wrote: >Elizabeth Schwartz wrote: >> >>Having cleaned that out, it sounds like I then proceeded to trash >>an afternoon's worth of messages by trying to flush the queue incorrectly. > > >I'm afraid so.
In case anyone is interested in the details, what actually happened when you ran bin/unshunt against qfiles/out is unshunt processed each queue entry as follows: It looked for the "original queue". This is placed in the message metadata by the shunting process to tell unshunt to which queue to restore the entry. Since the message was never shunted, there was no "original queue" so unshunt put it in the default 'in' queue. There it was picked up by IncomingRunner. Now the issue is that the message metadata in the queue entry has a 'pipeline' attribute which happens to be the empty list because when it was previously passed to the ToOutgoing handler, that was the last entry that was popped off the list leaving the list empty. Then, IncomingRunner proceeded to pass the message through the empty pipeline and was immediately finished without doing anything. Thus, the messages were all moved from the 'out' queue to the 'in' queue where IncomingRunner effectively recognized that it had already completely processed the message so this time it discarded the queue entry without doing anything. The moral is "don't unshunt anything which wasn't shunted to begin with". -- Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp
