|Submitter||Diff||Changes||Open Issues||Last Updated|
|Error loading review requests:|
59 bytes, text/x-review-board-request
|Details | Review|
When looking at what we get on the web and json for searches in changelog, I noticed that the pushlog data is empty. See https://hg.mozilla.org/releases/l10n/mozilla-beta/de/changelog?rev=limit(sort(branch(default),%20-rev)) or https://hg.mozilla.org/releases/l10n/mozilla-beta/de/json-changelog?rev=limit(sort(branch(default),%20-rev)). The culprit is that for searches, webcommands uses the searchentry template. That has the right entries, but it uses webutil.commonentry as entry type, and pushlog doesn't overwrite that. Now, it can, and that makes overwriting each of changesetentry and changelistentry obsolete. I have a patch for that. no-docker tests pass with hg 4.0.1. I dug a bit into the history of commonentry, https://www.mercurial-scm.org/repo/hg/diff/5aa2afb4f81a/mercurial/hgweb/webutil.py introduced that November 2015, so we should be good in terms of mercurial versions? 3.7 was released 2016-02-01 I tried running the tests against 3.7, but they fail for hgmo being 4.0 only. Should the claim about compat in pushlog/__init__.py be lifted?
Comment on attachment 8832863 [details] bug 1336090, wrap webutil.commonentry to add push metadata, https://reviewboard.mozilla.org/r/109124/#review110310 Nice improvement. Yes, we should update testedwith. I'll do that as a follow-up.
Attachment #8832863 - Flags: review?(gps) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/hgcustom/version-control-tools/rev/3912a52b8945 wrap webutil.commonentry to add push metadata, r=gps
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
Oh, it looks like the test issue is related to the hgmo extension and not pushlog itself. I may or may not clean this up. It appears to only be a problem with the test environment, since it loads the hgmo extension.
This is now deployed. I verified from the URLs in comment #0 that it is working.
You need to log in before you can comment on or make changes to this bug.