Unknown exception encountered with possibly-broken third-party extension "configwizard"
Categories
(Firefox Build System :: Bootstrap Configuration, defect)
Tracking
(Not tracked)
People
(Reporter: cmartin, Unassigned)
Details
Attachments
(1 file)
|
500 bytes,
application/octet-stream
|
Details |
I newly-updated mozilla-build, purged everything, and typed ./mach bootstrap. Received this when asked to setup Mercurial:
** Unknown exception encountered with possibly-broken third-party extension "configwizard" (version N/A)
** which supports versions 5.3 of Mercurial.
** Please disable "configwizard" and try your action again.
** If that fixes the bug please report it to https://bugzilla.mozilla.org/enter_bug.cgi?product=Developer%20Services&component=Mercurial%3A%20configwizard
** Python 3.9.10 (tags/v3.9.10:f2f3f53, Jan 17 2022, 15:14:21) [MSC v.1929 64 bit (AMD64)]
** Mercurial Distributed SCM (version 6.2.3)
** Extensions loaded: blackbox, configwizard, extdiff, fsmonitor, strip
Traceback (most recent call last):
File "C:\moz\mozilla-build\python3\Scripts\hg", line 59, in <module>
dispatch.run()
File "C:\moz\mozilla-build\python3\lib\site-packages\mercurial\dispatch.py", line 143, in run
status = dispatch(req)
File "C:\moz\mozilla-build\python3\lib\site-packages\mercurial\dispatch.py", line 232, in dispatch
status = _rundispatch(req)
File "C:\moz\mozilla-build\python3\lib\site-packages\mercurial\dispatch.py", line 276, in _rundispatch
ret = _runcatch(req) or 0
File "C:\moz\mozilla-build\python3\lib\site-packages\mercurial\dispatch.py", line 451, in _runcatch
return _callcatch(ui, _runcatchfunc)
File "C:\moz\mozilla-build\python3\lib\site-packages\mercurial\dispatch.py", line 461, in _callcatch
return scmutil.callcatch(ui, func)
File "C:\moz\mozilla-build\python3\lib\site-packages\mercurial\scmutil.py", line 153, in callcatch
return func()
File "C:\moz\mozilla-build\python3\lib\site-packages\mercurial\dispatch.py", line 441, in _runcatchfunc
return _dispatch(req)
File "C:\moz\mozilla-build\python3\lib\site-packages\mercurial\dispatch.py", line 1254, in _dispatch
return runcommand(
File "C:\moz\mozilla-build\python3\lib\site-packages\mercurial\dispatch.py", line 899, in runcommand
ret = _runcommand(ui, options, cmd, d)
File "C:\moz\mozilla-build\python3\lib\site-packages\mercurial\dispatch.py", line 1266, in _runcommand
return cmdfunc()
File "C:\moz\mozilla-build\python3\lib\site-packages\mercurial\dispatch.py", line 1252, in <lambda>
d = lambda: util.checksignature(func)(ui, *args, **strcmdopt)
File "C:\moz\mozilla-build\python3\lib\site-packages\mercurial\util.py", line 1880, in check
return func(*args, **kwargs)
File "C:/Users/cmartin/.mozbuild/version-control-tools/hgext\configwizard\__init__.py", line 492, in configwizard
cw = configobjwrapper(path)
File "C:/Users/cmartin/.mozbuild/version-control-tools/hgext\configwizard\__init__.py", line 1318, in __init__
self.c = ConfigObj(infile=lines, encoding='utf-8',
File "C:\Users\cmartin\.mozbuild\version-control-tools\pylib\configobj\configobj.py", line 1207, in __init__
self._load(infile, configspec)
File "C:\Users\cmartin\.mozbuild\version-control-tools\pylib\configobj\configobj.py", line 1304, in _load
raise error
configobj.ParseError: Parse error in value at line 4.
Comment 1•3 years ago
|
||
I'm not able to reproduce. Could you try renaming your .mozbuild directory in %USERPROFILE% and then re-running ./mach bootstrap? Then, if it fails, pasting the full log here?
Comment 2•3 years ago
|
||
(In reply to Chris Martin [:cmartin] from comment #0)
File "C:\Users\cmartin.mozbuild\version-control-tools\pylib\configobj\configobj.py", line 1304, in _load
raise error
configobj.ParseError: Parse error in value at line 4.
Can you share your .hgrc file (line 4 in particular)? I imagine this is a similar problem to bug 1751287, problems with encoding differences between configobj and Mercurial.
| Reporter | ||
Comment 3•3 years ago
|
||
I have attached my mercurial.ini file. I tried renaming <userdir>/.mozbuild and bootstrapping again, but the same error happened.
Comment 4•3 years ago
|
||
This is the same problem as bug 1739613. There is a workaround in bug 1739613 comment 10.
Description
•