Tahoe Trac bug watches not being updated

[Zooko Wilcox-O'Hearn]

I "asked a question" about why the remote watches to the trac that I administer aren't getting updated:

https://answers.launchpad.net/launchpad/+question/187145

Deryck Hodge (deryck) said that they had reset the bug watch, and that if the problem persisted I should open a bug against launchpad itself. Well, that ticket (https://bugs.launchpad.net/pyopenssl/+bug/434411) still hasn't been updated, and I also noticed another one with the same problem: https://bugs.launchpad.net/ubuntu/+source/nevow/+bug/410098

[Deryck Hodge (deryck)]

Bug watches do not appear to be updating, though the watches themselves say they are being updated. For example, the one linked above says it was checked 22 hours ago. But the status is not updated. And in "Recent Activity" the last completed updated is listed on 2011-10-27. So it seems like the watches are being scheduled, are being updated as if run, but are not actually logged as updated.

[Zooko Wilcox-O'Hearn (zooko)]

Here are a few things that might lead to a mismatch in a database somewhere, causing events to get dropped on the floor:

1. The URL of the trac has changed -- https://answers.launchpad.net/launchpad/+question/187178
2. The name may have changed.
3. There are multiple tracs that start with the same prefix -- formerly http://allmydata.org/trac/ and now https://tahoe-lafs.org/trac/

[Robert Collins (lifeless)]

See also bug 341997 - this may be a dupe. Does the tahoe trac have the LP plugin installed?

[Zooko Wilcox-O'Hearn (zooko)]

It has:

TracXMLRPC 1.1.2

TracLaunchpad 0.1.2-2

[Zooko Wilcox-O'Hearn (zooko)]

I upgraded my trac from Trac 0.12.2 to 0.12.3. Upgraded TracXMLRPC from 1.1.2 to a new package with many changes to its source code that also calls itself 1.1.2. Upgraded TracLaunchpad from 0.1.2-2 to 0.1.2-3.

Finally, I noticed this comment on http://trac-hacks.org/wiki/XmlRpcPlugin:

"""
If you have the AccountManagerPlugin enabled and you followed their advice/example to disable the standard login module with

[components]
trac.web.auth.LoginModule = disabled

the /login/xmlrpc URL for authorized access will not work as expected. Every access will look like anonymous access. You can use the HttpAuthPlugin to correct this.
"""

I did indeed have Account ManagerPlugin and have loginmodule disabled, so that could have been part of my problem. I followed the instructions to install HttpAuthPlugin, and now have v1.1 of that installed.

So, please try again, oh launchpad, to read from and/or write to my tickets.

[Zooko Wilcox-O'Hearn (zooko)]

Unfortunately, this doesn't appear to have fixed it. For example, this launchpad ticket: https://bugs.launchpad.net/ubuntu/+source/pycryptopp/+bug/944585 links to this pycryptopp ticket: https://tahoe-lafs.org/trac/pycryptopp/ticket/82 . The pycryptopp ticket was closed as "fixed" several days ago (2012-03-02_06:30:54Z -- https://tahoe-lafs.org/trac/pycryptopp/timeline?from=2012-03-02T06%3A30%3A54Z&precision=second ), but the launchpad ticket has not been automatically updated to reflect that.

What's the next step in debugging this?

[Robert Collins (lifeless)]

you could run the sync code with a local build of LP and see if it
works; if it doesn't: drill in, if it does, that would tell us to look
at e.g. firewalls.

[Zooko Wilcox-O'Hearn (zooko)]

Ugh, that sounds intimidating, but I might manage it. What's the command or where's the documentation for running the sync code?

[Zooko Wilcox-O'Hearn (zooko)]

Well, I got as far as:

Developers: please run utilities/link-external-sourcecode.

and

$ utilities/link-external-sourcecode
Usage: link-external-sourcecode [options] [parent]

link-external-sourcecode: error: Parent branch not specified, and could not be discovered.

But I'm definitely giving up on building launchpad for now. I have some other urgent tasks to do that are more rewarding because I already know all about their build/setup/test quirks...

[Deryck Hodge (deryck)]

You say it doesn't work, but are you sure someone reset the watch to try again? I don't see anyone say they did here. I reset it now for the first bug listed in the description. Just in case it hasn't been tried yet.

[Zooko Wilcox-O'Hearn (zooko)]

The Bug Watch Updater today updated, correctly, this ticket: https://bugs.launchpad.net/ubuntu/+source/pycryptopp/+bug/931542 So I think this works now! Hooray! Thanks!

[Deryck Hodge (deryck)]

Awesome, I'll mark the bug as fixed then. Thanks for getting back to us!