Hi Juan,
juan perin wrote, On 07/06/2010 01:37 PM:
I can't find any issues in the code, and have tried various file types as well. I'm at a stand still with galaxy right now, and am simply working on figuring out this problem until its resolved. Thanks for any other ideas you might have.
If you're sure you didn't change anything, AND it positively worked before your last pull/upgrade, AND you have some time to spare, you can try "hg bisect" to pin-point the exact changeset that broke it for you (assuming it is a changeset the causes the problem, and not some local configuration issue).
Start with a fresh clone, then run:
$ hg bisect --reset $ hg bisect --good XXXX (where XXXX is an old revision number which you're sure worked) $ hg bisect --bad tip (marking the current version as NOT working)
and then mercurial/hg which automatically pull/update old revisions for you. Every time mercurial changes a revision, run your tests (that's the "time to spare" part...), and check whether you can upload the libraries as needed.
If the tests worked, run: $ hg bisect --good
if the tests failed, run: $ hg bisect --bad
Mercurial will automatically change to another revision, then you test it again (and mark it again as "--good" or "--bad"), until the exact revision that introduced the problem is found.
More information about "bisect" is here: http://hgbook.red-bean.com/read/finding-and-fixing-mistakes.html#x_6c6
Alternatively, you can just use "hg update -C -r XXX" and switch to older revisions by yourself, but "bisect" will probably be more efficient.
-gordon