zeroconf/mq/serve interraction question

Boggess, Rod rboggess at tenovacore.com
Thu Oct 18 16:08:24 UTC 2012


I'm on Win7x64 with TortoiseHg 2.5, hg 2.3.1. I have zeroconf and mq
extensions enabled.

 

I setup an hgweb.conf file and created a dos cmd file (hg serve
--webdir-conf hgweb.conf). Initially, I shared ALL of my repositories
individually with individual listings under [paths]. Then I discovered
that I can't quite make the patches sub-repo automatically clone (well,
I could, but it's a lot more manual effort when the reference to it
isn't relative). So, I tried to go to the common directory of my repos,
and used the /trunk = "C:\**".  (Root directory modified from original,
here and in crash dump.)

 

With the recursive specification, I get a crash from zeroconf

 

C:\Users\rboggess\Desktop>hg serve --webdir-conf "C:\hgweb.conf"

** unknown exception encountered, please report by visiting

** http://mercurial.selenic.com/wiki/BugTracker

** Python 2.7.3 (default, Apr 10 2012, 23:24:47) [MSC v.1500 64 bit
(AMD64)]

** Mercurial Distributed SCM (version 2.3.1)

** Extensions loaded: convert, color, mq, churn, fetch, rebase, record,
relink,

win32mbcs, zeroconf

Traceback (most recent call last):

  File "hg", line 42, in <module>

  File "mercurial\dispatch.pyo", line 28, in run

  File "mercurial\dispatch.pyo", line 65, in dispatch

  File "mercurial\dispatch.pyo", line 88, in _runcatch

  File "mercurial\dispatch.pyo", line 740, in _dispatch

  File "mercurial\dispatch.pyo", line 514, in runcommand

  File "mercurial\extensions.pyo", line 189, in wrap

  File "hgext\color.pyo", line 364, in colorcmd

  File "mercurial\extensions.pyo", line 189, in wrap

  File "hgext\zeroconf\__init__.pyo", line 174, in cleanupafterdispatch

  File "mercurial\dispatch.pyo", line 830, in _runcommand

  File "mercurial\dispatch.pyo", line 801, in checkargs

  File "mercurial\dispatch.pyo", line 737, in <lambda>

  File "mercurial\util.pyo", line 471, in check

  File "mercurial\extensions.pyo", line 144, in wrap

  File "mercurial\util.pyo", line 471, in check

  File "hgext\mq.pyo", line 3528, in mqcommand

  File "mercurial\util.pyo", line 471, in check

  File "mercurial\commands.pyo", line 5190, in serve

  File "mercurial\hgweb\__init__.pyo", line 26, in hgweb

  File "hgext\zeroconf\__init__.pyo", line 125, in __init__

  File "hgext\zeroconf\__init__.pyo", line 93, in publish

  File "hgext\zeroconf\Zeroconf.pyo", line 1341, in registerService

  File "hgext\zeroconf\Zeroconf.pyo", line 1428, in checkService

hgext.zeroconf.Zeroconf.NonUniqueNameException

 

So, then I specified each repo-containing-directory in a separate line,
comment them all out, and uncomment them one at a time. Now, the only
sub-repos I have in the individual projects are the patches sub-repo. I
have one patches-containing project that works, but uncommenting any of
the others causes the same crash. 

 

Any insights into what is causing this non-unique conflict? I've tried
comparing the one that works with the others, and I can't see what's
different.

 

One project in particular contains two primary projects, each with its
own patches sub-repo. In this one case, I reference the parental
sub-dir, allowing hg serve to recurse. If I remove either of the
.hg/patches/.hg folder, the remaining three repos are served without
incident, but put it back, and it crashes. If I disable zeroconf
extension, they're served just fine. So, zeroconf is complaining about
something in the configuration of the patches sub-repository
configuration. I just can't see what.

 

"Patches, I'm dependin' on ya' son.

To pull the family through.

My son, it's all left up to you."

  -Clarence Carter

 

Rod Boggess

Software Engineer

Tenova Core

Cherrington Corporate Center

100 Corporate Center Drive

Coraopolis, PA 15108

Phone:  412-262-2240 x2467

Email:  rboggess at tenovacore.com

Website:  www.tenovacore.com

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20121018/4001b59e/attachment-0002.html>


More information about the Mercurial mailing list