[Bug 6467] New: purge remove files following directory junctions, included destinations outside the repository (security risk)
https://bz.mercurial-scm.org/show_bug.cgi?id=6467 Bug ID: 6467 Summary: purge remove files following directory junctions, included destinations outside the repository (security risk) Product: Mercurial Version: 5.6.1 Hardware: PC OS: Windows Status: UNCONFIRMED Severity: bug Priority: wish Component: purge Assignee: bugzi...@mercurial-scm.org Reporter: danielebenegi...@fastwebnet.it CC: mercurial-devel@mercurial-scm.org Python Version: --- Created attachment 2097 --> https://bz.mercurial-scm.org/attachment.cgi?id=2097=edit Windows BAT file that reproduce the reported problems. Please run it from an empty directory. Hi, if a working directory contains Directory Junctions (under Windows of course), "hg purge" will delete the content *pointed by* the link (instead of the directory junction only). This causes two big issues: - it's a dangerous security problem, because if the link points outside the repository (e.g. to system directories or to the the user's home directory), the purge command wipes out unexpected files. Note that - for example - package managers like NPM (NodeJS) could run install scripts out of the control of the user, and also an innocent link could make "hg purge" to delete content in the user PC. - it can delete tracked files in the repository, resulting in missing files and (if a tracked file was modified) lost changes. Adding the known Directory Junctions to the ".hgignore" file doesn't solve the problem (and of course can't be done for unknown junctions created by package managers). In attachment you can find a simple BAT file that creates both the above scenarios, calling "hg purge --print" to show the problem. If you remove the "--print" option you can see the effects. Please run the script in an empty directory (it expects "hg" to be in the PATH). The same setup using Unix "symlinks" under macOS works as expected instead: the symlink is removed but no content pointed by the symlink is processed by "hg purge". I think the same behavior is expected using the Directory Junctions under Windows. We often work with special build tools, and so we are forced - under Windows - to rely on Directory Junctions in the working copy to accomodate files and directories as expected by such build tools. This is more often needed when working with sub-repositories. I hope you can fix this, considering the implications. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6468] New: test-sqlitestore.t is flaky
https://bz.mercurial-scm.org/show_bug.cgi?id=6468 Bug ID: 6468 Summary: test-sqlitestore.t is flaky Product: Mercurial Version: unspecified Hardware: PC OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: pierre-yves.da...@ens-lyon.org CC: mercurial-devel@mercurial-scm.org Python Version: --- (unsurprisingly) the sqlite database can ended up locked when we try to access it: here is examples of failed run: https://foss.heptapod.net/octobus/mercurial-devel/-/jobs/153279 https://foss.heptapod.net/octobus/mercurial-devel/-/jobs/153172 https://foss.heptapod.net/octobus/mercurial-devel/-/jobs/153078 -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6471] New: After strip moved to core: AttributeError: module 'hgext.strip' has no attribute 'cmdtable'
https://bz.mercurial-scm.org/show_bug.cgi?id=6471 Bug ID: 6471 Summary: After strip moved to core: AttributeError: module 'hgext.strip' has no attribute 'cmdtable' Product: Mercurial Version: 5.7rc0 Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: normal Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: z...@zash.se CC: mercurial-devel@mercurial-scm.org Python Version: 3.7 # Command hg$ make local hg$ ./hg version # Error Traceback (most recent call last): File "/home/zash/src/hg/mercurial/extensions.py", line 264, in _runextsetup extsetup(ui) File "/usr/lib/python3/dist-packages/hgext3rd/evolve/exthelper.py", line 182, in finalextsetup knownexts[ext] = e.cmdtable AttributeError: module 'hgext.strip' has no attribute 'cmdtable' *** failed to set up extension evolve: module 'hgext.strip' has no attribute 'cmdtable' *** failed to set up extension evolve: module 'hgext.strip' has no attribute 'cmdtable' Mercurial Distributed SCM (version 5.6+98-d7a508a75d72) (see https://mercurial-scm.org for more information) Copyright (C) 2005-2020 Matt Mackall and others This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. # Bisect The first bad revision is: changeset: 46029:d7a508a75d72 user:Valentin Gatien-Baron date:Sun Nov 08 16:23:35 2020 -0500 summary: strip: move into core -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6469] New: gendoc error while building 5.7rc0
https://bz.mercurial-scm.org/show_bug.cgi?id=6469 Bug ID: 6469 Summary: gendoc error while building 5.7rc0 Product: Mercurial Version: stable branch Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: 7895pul...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- signing 46335:d9d97a6ef284 hgrc.5.gendoc.txt:1953: (ERROR/3) Unexpected indentation. Exiting due to level-3 (ERROR) system message. make[1]: *** [hgrc.5] Error 1 make: *** [doc] Error 2 make -C doc make[1]: Entering directory '/home/pulkit/repo/release-repo/release-build-5.7rc0/doc' python runrst hgmanpage --halt warning \ --strip-elements-with-class htmlonly hgrc.5.txt hgrc.5 hgrc.5.gendoc.txt:1953: (ERROR/3) Unexpected indentation. Exiting due to level-3 (ERROR) system message. Makefile:26: recipe for target 'hgrc.5' failed make[1]: *** [hgrc.5] Error 1 make[1]: Leaving directory '/home/pulkit/repo/release-repo/release-build-5.7rc0/doc' Makefile:75: recipe for target 'doc' failed make: *** [doc] Error 2 tar (child): dist/mercurial-5.7rc0.tar.gz: Cannot open: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now ../release-scripts/make-release: line 32: cd: mercurial-5.7rc0: No such file or directory Mercurial Distributed SCM (version 5.7rc0) cp: cannot stat 'dist/mercurial-5.7rc0.tar.gz': No such file or directory -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6466] New: '@:: - @' fails unexpectedly
https://bz.mercurial-scm.org/show_bug.cgi?id=6466 Bug ID: 6466 Summary: '@:: - @' fails unexpectedly Product: Mercurial Version: 5.6.1 Hardware: All OS: All Status: UNCONFIRMED Severity: bug Priority: wish Component: revset Assignee: bugzi...@mercurial-scm.org Reporter: matt_harbi...@yahoo.com CC: mercurial-devel@mercurial-scm.org Python Version: --- $ ../hg.exe log -r '@:: - @' abort: unknown revision '-@' Funny enough, it seems related to the open ended `::` operator and the `-` operator: $ ../hg.exe log -r '@::. - @' (log output omitted) $ ../hg.exe log -r '@:: and not @' (log output omitted) Quoting the last '@' doesn't help. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6473] New: __index__.py is generated with str instead of bytes
https://bz.mercurial-scm.org/show_bug.cgi?id=6473
Bug ID: 6473
Summary: __index__.py is generated with str instead of bytes
Product: Mercurial
Version: 5.7rc0
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: bug
Priority: wish
Component: Mercurial
Assignee: bugzi...@mercurial-scm.org
Reporter: matt_harbi...@yahoo.com
CC: martinv...@gmail.com,
mercurial-devel@mercurial-scm.org
Python Version: ---
After building the py2 WiX packaging, `test-check-help.t` fails on py3 trying
to interpolate `str` into `bytes`. The reason being that the generated
`__index__.py` file is left around, which the extension code looks at first if
it exists to get a list of disabled extensions. The content of the file is
something like:
```
docs = {'absorb': 'apply working directory changes to changesets
(EXPERIMENTAL)',
...
}
```
It doesn't matter too much if it's only used for py2exe, but I thought there
was some work to use it for PyOxidizer binaries. I was able to fix it by
converting inside the extensions module where it is used, but it seems to me
that it should be generated with the right content. However, I wasn't able to
get the installer build to work when converting to have b'' prefixes.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6474] New: narrow extention loose it`s page
https://bz.mercurial-scm.org/show_bug.cgi?id=6474 Bug ID: 6474 Summary: narrow extention loose it`s page Product: Mercurial Version: 5.6.1 Hardware: All OS: All Status: UNCONFIRMED Severity: feature Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: alexraynepe...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- Hallow! walk there https://www.mercurial-scm.org/wiki/UsingExtensions and try to poss to `narrowhg` - it jumps to bitbucket droped repo. where can i see how to use narrow extention? -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6475] New: sparse ext fails on getdirstate even if repo not use it
https://bz.mercurial-scm.org/show_bug.cgi?id=6475 Bug ID: 6475 Summary: sparse ext fails on getdirstate even if repo not use it Product: Mercurial Version: 5.5.1 Hardware: PC OS: Windows Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: alexraynepe...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- hallow! use hg 5.5.1 installed on win8.1 py3.8 enabled sparse extention, and after it refreshing directry state always fail: ``` #!python ** Mercurial version (5.5.1). TortoiseHg version (5.6.1+31-84d8dee08b86) ** Command: --nofork ** CWD: D:\projects\hg\thg\thg.work ** Encoding: cp1251 ** Extensions loaded: convert, strip, mq, rebase, record, transplant, highlight, show, commitextras, fix, share, hggit, censor, histedit, narrow, closehead, remotenames, schemes, eol, extdiff, patchbomb, amend, evolve, topic, absorb, split, uncommit, sparse, tortoisehg.util.configitems ** Python version: 3.8.3 (tags/v3.8.3:6f8c832, May 13 2020, 22:37:02) [MSC v.1924 64 bit (AMD64)] ** Windows version: sys.getwindowsversion(major=6, minor=3, build=9600, platform=2, service_pack='') ** Processor architecture: x64 ** Qt-5.13.2 PyQt-5.13.2 QScintilla-2.10.8 Traceback (most recent call last): File "D:/projects/hg/hg-git\hggit\gitdirstate.py", line 77, in gignore ignorefunc = matchmod.match(root, b'', [], allpats) File "D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\match.py", line 276, in match kindpats = normalize(include, b'glob', root, cwd, auditor, warn) File "D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\match.py", line 329, in _donormalize pat = pathutil.canonpath(root, cwd, pat, auditor=auditor) File "D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\pathutil.py", line 263, in canonpath raise error.Abort( mercurial.error.Abort: \.directory not under root 'D:\projects\askon\spodes\DLMS.meterkit\cosemlib' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "D:/projects/hg/hg-git\hggit\gitdirstate.py", line 83, in gignore matchmod.match(root, b'', [], extrapatterns) File "D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\match.py", line 276, in match kindpats = normalize(include, b'glob', root, cwd, auditor, warn) File "D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\match.py", line 329, in _donormalize pat = pathutil.canonpath(root, cwd, pat, auditor=auditor) File "D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\pathutil.py", line 263, in canonpath raise error.Abort( mercurial.error.Abort: \.directory not under root 'D:\projects\askon\spodes\DLMS.meterkit\cosemlib' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "D:\projects\hg\thg\thg.work\tortoisehg\hgqt\status.py", line 760, in run status = self.repo.status(**stopts) File "D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\localrepo.py", line 3324, in status return self[node1].status( File "D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\context.py", line 427, in status r = ctx2._buildstatus( File "D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\context.py", line 1961, in _buildstatus s = self._dirstatestatus(match, listignored, listclean, listunknown) File "D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\context.py", line 1870, in _dirstatestatus cmp, s = self._repo.dirstate.status( File "D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\dirstate.py", line 1247, in status self.walk(match, subrepos, listunknown, listignored, full=full) File "D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\extensions.py", line 509, in closure return func(*(args + a), **kw) File "D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\hgext\sparse.py", line 234, in walk return orig(self, match, subrepos, unknown, ignored, full) File "D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\dirstate.py", line 925, in walk ignore = self._ignore File "D:\projects\hg\thg\thg.work\venv.py38\lib\site-packages\mercurial\scmutil.py", line 1622, in __get__ entry.obj = self.func(obj) File "D:/projects/hg/hg-git\hggit\gitdirstate.py", line 113, in _ignore return gignore(self._root, files, self._ui.warn, File "D:/projects/hg/hg-git\hggit\gitdirstate.py", line 85, in gignore
[Bug 6465] New: Provide option to not use largefiles usercache
https://bz.mercurial-scm.org/show_bug.cgi?id=6465 Bug ID: 6465 Summary: Provide option to not use largefiles usercache Product: Mercurial Version: unspecified Hardware: PC OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: largefiles Assignee: bugzi...@mercurial-scm.org Reporter: djer...@cfa.harvard.edu CC: mercurial-devel@mercurial-scm.org, nato...@gmail.com Python Version: --- I work on a network where most disks (including /home) are remotely mounted via NFS (NetApp). Largefiles will copy files to the usercache if it cannot link them, which causes significant network i/o if the usercache is on an NFS mount. I have repositories on multiple remote disks, so to efficiently use Largefiles I'd have to specify a different, disk-specific largefiles.usercache value for each repo. This is, as you can imagine, painful, and leads to some frustration. It would be very useful if I could simply turn the usercache functionality off. If I find a need to use it for a particular repository, I can simply turn it on there. Thanks! -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6478] New: IndexError in hg log when given one existing and one non-existing filename
https://bz.mercurial-scm.org/show_bug.cgi?id=6478 Bug ID: 6478 Summary: IndexError in hg log when given one existing and one non-existing filename Product: Mercurial Version: default branch Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: z...@zash.se CC: mercurial-devel@mercurial-scm.org Python Version: 3.7 Some space characters accidentally escaped my revset and got me a traceback, here reproduced in the current default branch with default config: hg$ HGPLAIN= HOME=/tmp ./hg log -r tip % . obsolete feature not enabled but 242956 markers found! ** unknown exception encountered, please report by visiting ** https://mercurial-scm.org/wiki/BugTracker ** Python 3.7.3 (default, Jul 25 2020, 13:03:44) [GCC 8.3.0] ** Mercurial Distributed SCM (version 5.7rc0+79-16c18d5e5dc8) ** Extensions loaded: Traceback (most recent call last): File "./hg", line 59, in dispatch.run() File "/home/zash/src/hg/mercurial/dispatch.py", line 143, in run status = dispatch(req) File "/home/zash/src/hg/mercurial/dispatch.py", line 245, in dispatch status = _rundispatch(req) File "/home/zash/src/hg/mercurial/dispatch.py", line 289, in _rundispatch ret = _runcatch(req) or 0 File "/home/zash/src/hg/mercurial/dispatch.py", line 465, in _runcatch return _callcatch(ui, _runcatchfunc) File "/home/zash/src/hg/mercurial/dispatch.py", line 475, in _callcatch return scmutil.callcatch(ui, func) File "/home/zash/src/hg/mercurial/scmutil.py", line 155, in callcatch return func() File "/home/zash/src/hg/mercurial/dispatch.py", line 455, in _runcatchfunc return _dispatch(req) File "/home/zash/src/hg/mercurial/dispatch.py", line 1259, in _dispatch lui, repo, cmd, fullargs, ui, options, d, cmdpats, cmdoptions File "/home/zash/src/hg/mercurial/dispatch.py", line 913, in runcommand ret = _runcommand(ui, options, cmd, d) File "/home/zash/src/hg/mercurial/dispatch.py", line 1270, in _runcommand return cmdfunc() File "/home/zash/src/hg/mercurial/dispatch.py", line 1256, in d = lambda: util.checksignature(func)(ui, *args, **strcmdopt) File "/home/zash/src/hg/mercurial/util.py", line 1867, in check return func(*args, **kwargs) File "/home/zash/src/hg/mercurial/commands.py", line 4653, in log revs, differ = logcmdutil.getrevs(repo, walk_opts) File "/home/zash/src/hg/mercurial/logcmdutil.py", line 1028, in getrevs revs, filematcher = makewalker(repo, wopts) File "/home/zash/src/hg/mercurial/logcmdutil.py", line 982, in makewalker match, pats, slowpath = _makematcher(repo, revs, wopts) File "/home/zash/src/hg/mercurial/logcmdutil.py", line 836, in _makematcher filelog = repo.file(f) File "/home/zash/src/hg/mercurial/localrepo.py", line 1138, in file if path[0] == b'/': IndexError: index out of range It seems to happen when two arguments are given, one existing path and one non-existing. E.g. `hg log existingfile nonexistantfile`. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6479] New: GUI diff tools fail to launch under wayland
https://bz.mercurial-scm.org/show_bug.cgi?id=6479 Bug ID: 6479 Summary: GUI diff tools fail to launch under wayland Product: Mercurial Version: 5.6.1 Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: scoopta@scoopta.email CC: mercurial-devel@mercurial-scm.org Python Version: --- I have meld configured as my diff tool in my hgrc. When running hg resolve on my system I get this error and the resolve fails tool meld requires a GUI I did some testing and this goes away if I run DISPLAY=:0 hg resolve. It appears mercurial checks for the presence of $DISPLAY. meld is a fully wayland native application and even though I have no X server running at all just setting $DISPLAY fixes the issue. Mercurial should either not make this check or check for either $DISPLAY and $WAYLAND_DISPLAY. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6476] New: "bytes length not a multiple of item size" during `hg in`
https://bz.mercurial-scm.org/show_bug.cgi?id=6476 Bug ID: 6476 Summary: "bytes length not a multiple of item size" during `hg in` Product: Mercurial Version: 5.6.1 Hardware: PC OS: Windows Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: r...@perspexis.com CC: mercurial-devel@mercurial-scm.org Python Version: --- I'm running Ubuntu in WSL on Windows 10, with mercurial run from source. When doing a simple `hg pull` in one of my repos I got the following traceback: ``` $ hg pull pulling from ssh:// searching for changes no changes found ** unknown exception encountered, please report by visiting ** https://mercurial-scm.org/wiki/BugTracker ** Python 3.9.1 (default, Jan 25 2021, 17:58:41) [GCC 9.3.0] ** Mercurial Distributed SCM (version 5.6.1) ** Extensions loaded: histedit, extdiff, pager, fetch, graphlog, record, rebase, strip, evolve, convert Traceback (most recent call last): File "/home/russ/bin/venv_for_python_apps/bin/hg", line 43, in dispatch.run() File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/dispatch.py", line 113, in run status = dispatch(req) File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/dispatch.py", line 303, in dispatch ret = _runcatch(req) or 0 File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/dispatch.py", line 479, in _runcatch return _callcatch(ui, _runcatchfunc) File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/dispatch.py", line 488, in _callcatch return scmutil.callcatch(ui, func) File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/scmutil.py", line 153, in callcatch return func() File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/dispatch.py", line 469, in _runcatchfunc return _dispatch(req) File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/dispatch.py", line 1232, in _dispatch return runcommand( File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/dispatch.py", line 917, in runcommand ret = _runcommand(ui, options, cmd, d) File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/hgext/pager.py", line 76, in pagecmd return orig(ui, options, cmd, cmdfunc) File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/dispatch.py", line 1244, in _runcommand return cmdfunc() File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/dispatch.py", line 1230, in d = lambda: util.checksignature(func)(ui, *args, **strcmdopt) File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/util.py", line 1867, in check return func(*args, **kwargs) File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/util.py", line 1867, in check return func(*args, **kwargs) File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/hgext3rd/evolve/__init__.py", line 708, in wrapmayobsoletewc res = origfn(ui, repo, *args, **opts) File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/util.py", line 1867, in check return func(*args, **kwargs) File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/util.py", line 1867, in check return func(*args, **kwargs) File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/hgext/rebase.py", line 2159, in pullrebase ret = orig(ui, repo, *args, **opts) File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/util.py", line 1867, in check return func(*args, **kwargs) File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/commands.py", line 5330, in pull modheads = exchange.pull( File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/exchange.py", line 1827, in pull _fullpullbundle2(repo, pullop) File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/exchange.py", line 1693, in _fullpullbundle2 _pullbundle2(pullop) File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/mercurial/exchange.py", line 2018, in _pullbundle2 _pullbundle2extraprepare(pullop, kwargs) File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/hgext3rd/evolve/obsexchange.py", line 71, in _addobscommontob2pull boundaries = obsdiscovery.buildpullobsmarkersboundaries(pullop) File "/home/russ/bin/venv_for_python_apps/lib/python3.9/site-packages/hgext3rd/evolve/obsdiscovery.py", line 859, in buildpullobsmarkersboundaries missing = findmissingrange(repo.ui, repo, pullop.remote, revs) File
[Bug 6477] New: Tracking down the status of `HGMERGE=internal:local hg evolve`
https://bz.mercurial-scm.org/show_bug.cgi?id=6477 Bug ID: 6477 Summary: Tracking down the status of `HGMERGE=internal:local hg evolve` Product: Mercurial Version: unspecified Hardware: PC OS: Mac OS Status: UNCONFIRMED Severity: feature Priority: wish Component: evolution Assignee: bugzi...@mercurial-scm.org Reporter: jw...@jwatt.org CC: mercurial-devel@mercurial-scm.org, pierre-yves.da...@ens-lyon.org Python Version: --- The document: https://www.mercurial-scm.org/doc/evolution/sharing.html#bug links to: https://bitbucket.org/marmoute/mutable-history/issues/48 which appears to be long gone. Would anyone still remember what that issue is about? Is it still an issue? If so, would someone be able to file a bug here and update the documentation to link to it? -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6528] New: hg serve causes files to be marked as modified after clone
https://bz.mercurial-scm.org/show_bug.cgi?id=6528 Bug ID: 6528 Summary: hg serve causes files to be marked as modified after clone Product: Mercurial Version: 5.8 Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: g...@reaperworld.com CC: mercurial-devel@mercurial-scm.org Python Version: --- There was a lot of discussion on this in #mercurial on freenode but I'll do my best to summarize it. I don't expect this issue to be widespread as based on the commit I bisected too, it sounds like the patch just wasn't ready for some of the crazy stuff that has happened in the pidgin repository as it went from cvs -> svn -> mtn -> hg with some manual patching in between some of those steps as well. I was bootstrapping a Google Summer of Code student today and noticed that there were more modified files in the repository than there should have been. 26 files in fact that are very old and haven't been touched in a long time. I had created the repo from them using `hg init ssh://keep.imfreedom.org/prateek/pidgin` and then pushed a fresh clone of https://keep.imfreedom.org/pidgin/pidgin into it. keep.imfreedom.org is running my hgkeeper servering solution for mercurial. While I did all of this, keep was running hg 5.8. Anyways, I just did a commit by specifying the files we changed and then started debugging where these files came from. (This is important for later). I started trying to clone from other machines thinking it was something local at first. Interestingly enough, our mac build agent running hg 5.3.2 with python 2.7.17 never reproduced the issue, but a linux machine running hg 4.8.2 with python 2.7.18 did. I had a few others try with various combinations and all of them reproduced the issue as well, 26 modified files after a clone. However, Zash in #mercurial only saw 25 modified files. I ended up creating a tarball of the main pidgin repo which is currently available at https://data.imfreedom.org/pidgin/pidgin-raw.tar.xz. Using the raw repo I did a local directory clone `hg clone pidgin-raw pidgin-local` and verified the issue was not present. I then served the repo with `hg --cwd pidgin-raw serve` and cloned it with `hg clone http://localhost:8000 pidgin-local` and verified the issue was present. With that data point in hand I downgraded my local hg to 5.7.1 and performed the same test. This time, both clone did not express the issue. I then downgraded hg on keep to 5.7.1 and have been unable to reproduce for any non-poisoned repo there. I say non-poisoned because the repo I created for the GSoC student still shows the modified files on a fresh clone even with 5.7.1. That repo is https://keep.imfreedom.org/prateek/pidgin. I then bisected starting with tag:5.7.1 marked as good and tag:5.8 marked as bad. During each step, I ran `pip install -U --user .` in the hg source directory. After installation, I served a clean repo with `hg serve` and clone it with `hg clone http://localhost:8000 local` until bisect identified revision https://www.mercurial-scm.org/repo/hg/rev/49fd21f32695. The description seems like a likely candidated, but mharbison in #mercurial hasn't been able to reproduce on that revision. So as of right now, I have hg 5.7.1 running on keep.imfreedom.org to stop the spread of the poison repos. The poisoning isn't horrible, but it's not great either. So a remote init and push from a poisoned repo results in a poisoned repo. That is `hg init ssh://foo; hg push ssh://foo`. However, a local init and push does not poison. That is `hg init ../foo; hg push ../foo`. And as you may expect, a local clone of a poisoned repo poisons the new repo. That is `hg clone . ../foo`. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6529] New: Restrictions on allowable names for topics should be documented
https://bz.mercurial-scm.org/show_bug.cgi?id=6529 Bug ID: 6529 Summary: Restrictions on allowable names for topics should be documented Product: Mercurial Version: 5.6.1 Hardware: PC OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: evolution Assignee: bugzi...@mercurial-scm.org Reporter: fah...@faheem.info CC: mercurial-devel@mercurial-scm.org, pierre-yves.da...@ens-lyon.org Python Version: --- I'm running Evolve 10.3.2-1 along with Mercurial 5.6.1 on Debian stable 10.9. The title says it all. I've checked available documentation, but restrictions on topic names do not appear to be documented. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6530] New: Ijazah A Course
https://bz.mercurial-scm.org/show_bug.cgi?id=6530 Bug ID: 6530 Summary: Ijazah A Course Product: Mercurial project Version: unspecified Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: website Assignee: bugzi...@mercurial-scm.org Reporter: mubeenjazlaa...@gmail.com CC: mercurial-devel@mercurial-scm.org We are Global Online Quran Teachers, an educational organization that is located in Egypt and was set up in pursuit of spreading the Quran. We aim to teach the Best way to learn Quran Online with the Best Online Quran Teachers. https://www.onlinequranteachers.com/course/ijazah-certification/ -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6520] New: threading.currentThread has been deprecated in favour of threading.current_thread in Python 3.10
https://bz.mercurial-scm.org/show_bug.cgi?id=6520 Bug ID: 6520 Summary: threading.currentThread has been deprecated in favour of threading.current_thread in Python 3.10 Product: Mercurial Version: default branch Hardware: PC OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: tir.kar...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- This is causing issues while running tests since deprecation warnings are also recorded. I would like to contribute a patch for this. --- /root/hg-committed/tests/test-shelve3.t +++ /root/hg-committed/tests/test-shelve3.t.err @@ -11,10 +11,27 @@ $ hg commit -Aqm b $ echo test > sample.txt $ hg shelve -n test + /root/hg-committed/mercurial/vfs.py:310: DeprecationWarning: currentThread() is deprecated, use current_thread() instead +threading.currentThread(), + /root/hg-committed/mercurial/vfs.py:486: DeprecationWarning: currentThread() is deprecated, use current_thread() instead +threading.currentThread(), -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6518] New: out of date BitBucket references on 'Downloads' page.
https://bz.mercurial-scm.org/show_bug.cgi?id=6518 Bug ID: 6518 Summary: out of date BitBucket references on 'Downloads' page. Product: Mercurial project Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: bug Priority: wish Component: website Assignee: bugzi...@mercurial-scm.org Reporter: r8yo1...@sneakemail.com CC: mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/guide has some out of date references to BitBucket. Maybe update that to heptapod.net (and/or sourcehut, or others)? Maybe a pointer to the MercurialHosting wiki page. Side question: where is the repo for the mercurial web site? -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6521] New: dirstate not tracks sparse changes
https://bz.mercurial-scm.org/show_bug.cgi?id=6521 Bug ID: 6521 Summary: dirstate not tracks sparse changes Product: Mercurial Version: 5.7.1 Hardware: PC OS: Windows Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: alexraynepe...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- Hallow! use hg5.7.1 on win8.1 py3 work on sparsed repo. after update to any revision, dirstate conforms to currents configured sparse-config, and it not tracks that config changes. update, update -C - not hepls. only update to another revision and commit, rebuilds valid dirstate with new sparse-config steps to reproduce: 1) setup sparce conf A 2) update to rev A 3) change sparse conf B - add some exclude 4) hg stat reports as for confA. - expected that it reports for new confB 5) hg up -C 6) hg stat keep same 7) hg up -r A-1; hg up -r A 8) now hg stat shows files that was excluded in confB this bug was spoted by bug #4297 (https://bz.mercurial-scm.org/show_bug.cgi?id=4297) and accidentaly classifyed as destructive commit -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6523] New: test-persistent-nodemap: "dd status" not portable
https://bz.mercurial-scm.org/show_bug.cgi?id=6523 Bug ID: 6523 Summary: test-persistent-nodemap: "dd status" not portable Product: Mercurial Version: 5.8rc0 Hardware: All OS: NetBSD Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: t...@giga.or.at CC: mercurial-devel@mercurial-scm.org Python Version: --- In 5.8, test-persistent-nodemap.t uses "dd status=none". dd(1) on NetBSD does not support this, leading to --- /scratch/devel/py-mercurial/work/mercurial-5.8/tests/test-persistent-nodemap.t +++ /scratch/devel/py-mercurial/work/mercurial-5.8/tests/test-persistent-nodemap.t.err @@ -793,9 +793,13 @@ $ f -s $datafilepath corruption-test-repo/.hg/store/00changelog-*.nd: size=121088 (glob) $ dd if=$datafilepath bs=1000 count=10 of=$datafilepath-tmp status=none + dd: unknown operand status + [1] $ mv $datafilepath-tmp $datafilepath + mv: rename corruption-test-repo/.hg/store/00changelog-2dd95ded3cce65da.nd-tmp to corruption-test-repo/.hg/store/00changelog-2dd95ded3cce65da.nd: $ENOENT$ + [1] $ f -s $datafilepath - corruption-test-repo/.hg/store/00changelog-*.nd: size=1 (glob) + corruption-test-repo/.hg/store/00changelog-2dd95ded3cce65da.nd: size=121088 Check that Mercurial reaction to this event ERROR: test-persistent-nodemap.t output changed -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6524] New: test-hooklib-reject_new_heads failure
https://bz.mercurial-scm.org/show_bug.cgi?id=6524 Bug ID: 6524 Summary: test-hooklib-reject_new_heads failure Product: Mercurial Version: 5.8rc0 Hardware: All OS: NetBSD Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: t...@giga.or.at CC: mercurial-devel@mercurial-scm.org Python Version: --- I see a new test failure in mercurial 5.8 on NetBSD: --- /scratch/devel/py-mercurial/work/mercurial-5.8/tests/test-hooklib-reject_new_heads.t +++ /scratch/devel/py-mercurial/work/mercurial-5.8/tests/test-hooklib-reject_new_heads.t.err @@ -96,7 +96,7 @@ remote: error: pretxnclose.reject_new_heads hook failed: Changes on branch 'default' resulted in multiple heads remote: Changes on branch 'default' resulted in multiple heads abort: push failed on remote - [255] + [100] $ hg phase --cwd b fa942426a6fd 2: draft -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6519] New: "hg pull " is pulling from default instead
https://bz.mercurial-scm.org/show_bug.cgi?id=6519 Bug ID: 6519 Summary: "hg pull " is pulling from default instead Product: Mercurial Version: 5.8rc0 Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: mhent...@mozilla.com CC: mercurial-devel@mercurial-scm.org Python Version: --- My `.hg/hgrc` looks like: ``` [paths] default = https://hg.mozilla.org/mozilla-central mhentges = ssh://hg.mozilla.org/users/mhentges_mozilla.com/central ``` However, when I do `hg pull mhentges`, it pulls from `default` instead: ``` $ hg pull mhentges pulling from https://hg.mozilla.org/mozilla-central searching for changes no changes found $ hg version Mercurial Distributed SCM (version 5.8) (see https://mercurial-scm.org for more information) Copyright (C) 2005-2021 Olivia Mackall and others This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. ``` -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6527] New: Incorrect error message shown when aborting a merge with an ongoing bisect operation
https://bz.mercurial-scm.org/show_bug.cgi?id=6527 Bug ID: 6527 Summary: Incorrect error message shown when aborting a merge with an ongoing bisect operation Product: Mercurial Version: stable branch Hardware: Other OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: tom.ingelbi...@nokia.com CC: mercurial-devel@mercurial-scm.org Python Version: --- Since version 5.1.2-1, Mercurial gives an incorrect error message when aborting a merge while a bisect is still ongoing (admittedly quite a corner case). I'm working on CentOS, where I can easily reproduce it with following minimized scenario: # Set up a small repo hg init echo "lorem ipsum" > textfile; hg add textfile; hg commit -m "First commit" echo "dolor sit amet" >> textfile; hg commit -m "Second commit" # Create second head hg up -r 0 echo "foo" > bar; hg add bar hg commit -m "Additional head for merging" # Run a bisect (without explicitly resetting at the end) hg bisect --reset hg bisect --bad 1 hg bisect --good 0 # Initiate a merge, and abort it hg merge hg merge --abort # Result: following incorrect error message # abort: cannot abort merge with bisect in progress # (use 'hg bisect --continue' or 'hg bisect --abort') The bisect command doesn't recognize either of those two suggested options, though. Note that I only target this incorrect help text in this bug ticket. The decision to refuse aborting a merge with a bisect operation in progress is not what I'm challenging here. I didn't see the issue on versions older than 5.1.2-1, but _only_ because those happily aborted the merge, despite the bisect still being in progress. Since there's no error message, there's also no incorrect hint. I've verified this on 4.5-1, 4.6-1, 4.7.1-1 and 4.9-1. As I could resolve the situation by just running "hg bisect --reset" again, it seems that this is actually the hint that should be displayed (rather than the --continue and --abort options). -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6526] New: hg clone crashes
https://bz.mercurial-scm.org/show_bug.cgi?id=6526 Bug ID: 6526 Summary: hg clone crashes Product: Mercurial Version: 5.2 Hardware: PC OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: ya...@ieee.org CC: mercurial-devel@mercurial-scm.org Python Version: --- Created attachment 2113 --> https://bz.mercurial-scm.org/attachment.cgi?id=2113=edit a1 "hg clone " crashes (see attachment a1.txt). "hg clone --noupdate" does not crash, but running "hg update default" after "hg clone --noupdate" also crashes in a similar way. See attachment a2.txt for the result of "hg --debug update default". -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6525] New: push with local subrepo infer subrepo content to remote-repo
https://bz.mercurial-scm.org/show_bug.cgi?id=6525 Bug ID: 6525 Summary: push with local subrepo infer subrepo content to remote-repo Product: Mercurial Version: 5.7.1 Hardware: PC OS: Windows Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: alexraynepe...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- Created attachment 2111 --> https://bz.mercurial-scm.org/attachment.cgi?id=2111=edit demo push infers content subrepo to remote repo Hallow! i have project Repo and add local Suberpo in that. For some reasons have no remote URL path, so .hgsub declares: ``` subrepo = ``` on a flash drive i got Clone of my main Repo, but subrepo has absent. after push Repo to my Clone on flash - it pushes all content of Subrepo into Clone. So Clone history mixed of Repo and new added Subrepo. I expected that pushing at least creates new subrepo on flash, or breaks with fail. It quite irritate behaviour, especialy if infered subs much more hystory and content then main-repo - it take much place on flash and take much time for useless push. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6534] New: Crash on hg rebase
https://bz.mercurial-scm.org/show_bug.cgi?id=6534 Bug ID: 6534 Summary: Crash on hg rebase Product: Mercurial Version: 5.8rc0 Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: rebase Assignee: bugzi...@mercurial-scm.org Reporter: ja...@jaccovanschaik.net CC: mercurial-devel@mercurial-scm.org Python Version: --- Created attachment 2119 --> https://bz.mercurial-scm.org/attachment.cgi?id=2119=edit Setup script. The attached shell script sets up the preconditions for the error. It occurs when subsequently issuing the command "hg rebase --base B1 --dest tip" The error is as follows: --- %< --- 14:01 OK jacco@occam:~/Test/R1 > hg rebase --base B1 --dest tip rebasing 5:4dc0d1c2ae45 "B1: expand file1, add file4" rebasing 6:9c67f0addbbb "B1: expand file2" saved backup bundle to /home/jacco/Test/R1/.hg/strip-backup/4dc0d1c2ae45-8bc4e8d8-rebase.hg strip failed, backup bundle stored in '/home/jacco/Test/R1/.hg/strip-backup/4dc0d1c2ae45-8bc4e8d8-rebase.hg' strip failed, unrecovered changes stored in '/home/jacco/Test/R1/.hg/strip-backup/4dc0d1c2ae45-737ab3ea-temp.hg' (fix the problem, then recover the changesets with "hg unbundle '/home/jacco/Test/R1/.hg/strip-backup/4dc0d1c2ae45-737ab3ea-temp.hg'") ** unknown exception encountered, please report by visiting ** https://mercurial-scm.org/wiki/BugTracker ** Python 3.9.5 (default, May 11 2021, 08:20:37) [GCC 10.3.0] ** Mercurial Distributed SCM (version 5.8+hg20.9f798c1b0d89) ** Extensions loaded: hgk, rebase Traceback (most recent call last): File "/usr/local/lib/python3.9/dist-packages/mercurial/revlog.py", line 1305, in headrevs return self.index.headrevs() AttributeError: 'revlogoldindex' object has no attribute 'headrevs' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/bin/hg", line 59, in dispatch.run() File "/usr/local/lib/python3.9/dist-packages/mercurial/dispatch.py", line 144, in run status = dispatch(req) File "/usr/local/lib/python3.9/dist-packages/mercurial/dispatch.py", line 250, in dispatch status = _rundispatch(req) File "/usr/local/lib/python3.9/dist-packages/mercurial/dispatch.py", line 294, in _rundispatch ret = _runcatch(req) or 0 File "/usr/local/lib/python3.9/dist-packages/mercurial/dispatch.py", line 470, in _runcatch return _callcatch(ui, _runcatchfunc) File "/usr/local/lib/python3.9/dist-packages/mercurial/dispatch.py", line 480, in _callcatch return scmutil.callcatch(ui, func) File "/usr/local/lib/python3.9/dist-packages/mercurial/scmutil.py", line 155, in callcatch return func() File "/usr/local/lib/python3.9/dist-packages/mercurial/dispatch.py", line 460, in _runcatchfunc return _dispatch(req) File "/usr/local/lib/python3.9/dist-packages/mercurial/dispatch.py", line 1263, in _dispatch return runcommand( File "/usr/local/lib/python3.9/dist-packages/mercurial/dispatch.py", line 918, in runcommand ret = _runcommand(ui, options, cmd, d) File "/usr/local/lib/python3.9/dist-packages/mercurial/dispatch.py", line 1275, in _runcommand return cmdfunc() File "/usr/local/lib/python3.9/dist-packages/mercurial/dispatch.py", line 1261, in d = lambda: util.checksignature(func)(ui, *args, **strcmdopt) File "/usr/local/lib/python3.9/dist-packages/mercurial/util.py", line 1884, in check return func(*args, **kwargs) File "/usr/local/lib/python3.9/dist-packages/hgext/rebase.py", line 1134, in rebase return _dorebase(ui, repo, action, opts) File "/usr/local/lib/python3.9/dist-packages/hgext/rebase.py", line 1202, in _dorebase return _origrebase(ui, repo, action, opts, rbsrt) File "/usr/local/lib/python3.9/dist-packages/hgext/rebase.py", line 1282, in _origrebase rbsrt._finishrebase() File "/usr/local/lib/python3.9/dist-packages/hgext/rebase.py", line 773, in _finishrebase clearrebased( File "/usr/local/lib/python3.9/dist-packages/hgext/rebase.py", line 2114, in clearrebased scmutil.cleanupnodes(repo, replacements, b'rebase', moves, backup=backup) File "/usr/local/lib/python3.9/dist-packages/mercurial/scmutil.py", line 1224, in cleanupnodes repair.delayedstrip( File "/usr/local/lib/python3.9/dist-packages/mercurial/util.py", line 1373, in __exit__ self.close() File "/usr/local/lib/python3.9/dist-packages/mercurial/transaction.py", line 44, in _active return func(self, *args, **kwds) File "/usr/local/lib/python3.9/dist-packages/mercurial/transaction.py", line 620, in close self._postclosecallback[cat](self) File "/usr/local/lib/python3.9/dist-packages/mercurial/repair.py", line 394, in __call__ strip(self.ui, self.repo, roots, self.backup, self.topic) File "/usr/local/lib/python3.9/dist-packages/mercurial/repair.py", line 250, in strip bundle2.applybundle(
[Bug 6533] New: hg commit --interactive doesn't handle deslecting all edits of a rename
https://bz.mercurial-scm.org/show_bug.cgi?id=6533 Bug ID: 6533 Summary: hg commit --interactive doesn't handle deslecting all edits of a rename Product: Mercurial Version: default branch Hardware: All OS: All Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: dpl...@google.com CC: mercurial-devel@mercurial-scm.org Python Version: --- Reproduction: > hg init repo > cd repo > echo foo > foo > hg commit -Am 'commit 1' > hg mv foo bar > echo bar >> bar > hg commit -im 'commit 2' # Deslect the `+bar` diff hunk, but keep the file (rename) selected Expected state: > hg status M bar > hg diff --- a/bar +++ b/bar @@ -1,1 +1,2 @@ foo +bar Actual state: > hg status # No output > hg diff # No output > cat bar foo bar # Hunk was committed despite deselection I've identified the root cause of this error and will send a patch shortly for it. Filing for reference. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6532] New: Pulling from user repo with evolve extension enabled
https://bz.mercurial-scm.org/show_bug.cgi?id=6532 Bug ID: 6532 Summary: Pulling from user repo with evolve extension enabled Product: Mercurial Version: 5.7.1 Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: evolution Assignee: bugzi...@mercurial-scm.org Reporter: zeger...@me.com CC: mercurial-devel@mercurial-scm.org, pierre-yves.da...@ens-lyon.org Python Version: --- Created attachment 2117 --> https://bz.mercurial-scm.org/attachment.cgi?id=2117=edit full traceback I have `evolution = all` enabled and am using the evolve extension (version 10.3.2). When I try to pull from another user's repo I get an error. The other user also has evolution enabled, but is not using the evolve extension. The error message is similar to https://bz.mercurial-scm.org/show_bug.cgi?id=6432 ``` remote: File "/usr/lib64/python3.6/site-packages/mercurial/util.py", line 1747, in __get__ remote: result = self.func(obj) remote: File "/home/zvandeva/.local/lib/python3.6/site-packages/hgext3rd/evolve/stablerangecache.py", line 518, in stablerange remote: cache.update(self) remote: File "/home/zvandeva/.local/lib/python3.6/site-packages/hgext3rd/evolve/genericcaches.py", line 111, in update remote: self.load(repo) remote: File "/home/zvandeva/.local/lib/python3.6/site-packages/hgext3rd/evolve/stablerangecache.py", line 400, in load remote: if self._con is not None: remote: File "/usr/lib64/python3.6/site-packages/mercurial/util.py", line 1747, in __get__ remote: result = self.func(obj) remote: File "/home/zvandeva/.local/lib/python3.6/site-packages/hgext3rd/evolve/stablerangecache.py", line 262, in _con remote: con = self._db() remote: File "/home/zvandeva/.local/lib/python3.6/site-packages/hgext3rd/evolve/stablerangecache.py", line 251, in _db remote: isolation_level=r"IMMEDIATE") remote: sqlite3.OperationalError: unable to open database file ``` Temporarily disabling the evolve extension allows me to pull the changes. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6531] New: Working directory has uncommitted changes after merge
https://bz.mercurial-scm.org/show_bug.cgi?id=6531 Bug ID: 6531 Summary: Working directory has uncommitted changes after merge Product: Mercurial Version: 5.8 Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: aklitz...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- Created attachment 2116 --> https://bz.mercurial-scm.org/attachment.cgi?id=2116=edit Example data to reproduce We found a strange bug on a merge commit. If someone merge changes of a moved file it will show uncommitted changes after applying the bundle or pulling it from repository. It is necessary to pull/unbundle those changeset. If you commit that changeset it will work. Stripping and unbundling it introduces it, too. Steps to reproduce von Mercurial 5.8 1. hg init example 2. cd example 3. hg unbundle ../init.hg 4. hg unbundle ../merge.hg 5. hg update 6. hg status It will show "M new/Test.cpp". Even "hg update -C" won't clear this. Best regards André -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6536] New: test-chg.t is flaky
https://bz.mercurial-scm.org/show_bug.cgi?id=6536 Bug ID: 6536 Summary: test-chg.t is flaky Product: Mercurial Version: default branch Hardware: PC OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: pierre-yves.da...@ens-lyon.org CC: mercurial-devel@mercurial-scm.org Python Version: --- test-chg.t frequently fails with minor output change. We need to adjust it to no longer be flaky. Example run: - https://foss.heptapod.net/octobus/mercurial-devel/-/jobs/220791 - https://foss.heptapod.net/octobus/mercurial-devel/-/jobs/220542 -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6537] New: frequent time-out during `test-py2-chg` CI
https://bz.mercurial-scm.org/show_bug.cgi?id=6537 Bug ID: 6537 Summary: frequent time-out during `test-py2-chg` CI Product: Mercurial Version: default branch Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: pierre-yves.da...@ens-lyon.org CC: mercurial-devel@mercurial-scm.org Python Version: --- It looks like some test are getting stuck (and eventually timeout thankfully) during the `test-py2-chg` CI job. It happens when the CI is loaded, re-run at a quieter time usually get through My attempt to reproduce this on my local machine as failed. This often happens with `test-subrepo-git.t`, - https://foss.heptapod.net/octobus/mercurial-devel/-/jobs/220816 - https://foss.heptapod.net/octobus/mercurial-devel/-/jobs/220819 - https://foss.heptapod.net/octobus/mercurial-devel/-/jobs/220879 - https://foss.heptapod.net/octobus/mercurial-devel/-/jobs/220894 but I also saw `test-commit-interactive.t` having issue too: - https://foss.heptapod.net/octobus/mercurial-devel/-/jobs/220932 -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6538] New: Follow up to issue 6528, parent ordering
https://bz.mercurial-scm.org/show_bug.cgi?id=6538 Bug ID: 6538 Summary: Follow up to issue 6528, parent ordering Product: Mercurial Version: default branch Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: pierre-yves.da...@ens-lyon.org CC: mercurial-devel@mercurial-scm.org Python Version: --- issue6528 was introduced by 49fd21f32695 : changeset: 49092:49fd21f32695 user:Joerg Sonnenberger date:Wed Mar 10 18:09:21 2021 +0100 summary: revlog: guarantee that p1 != null if a non-null parent exists A changeset that was eventually backed out last week as 411dc27fd9fd To sumup 49fd21f32695, swapping p1 and p2 is p1 is nullid destroy the implicit "this file-revision has copy information" marker and corrupt repository. However Joerg Sonnenberger have been warning use about other potential bug that backing out this changeset introduce. such bug would be related to bad order of changelog-revision, however I don't have more details about them. I think we needs: - clearer information from Joerg about these changelog related bug (or someone else to dig them out), - a new changeset to prevent parent swapping on filelog, but allowing it on changelog. - a script to fully scrub a repository to detect and swapped filelog information. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6535] New: hg prints nothing in win8 cmd console
https://bz.mercurial-scm.org/show_bug.cgi?id=6535 Bug ID: 6535 Summary: hg prints nothing in win8 cmd console Product: Mercurial Version: 5.8.1 Hardware: PC OS: Windows Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: alexraynepe...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- Hallow! i setups hg5.8 from x64 msi, and also instals it by pip3 in python 3.8 venv. both have same behaviour: 1) `hg --version` - prints ok, but loose valid encoding for national symbols. 2) any other commands print nothing ! `hg log`, `hg st` - silent hg 5.7 was some problems with national simbols - it prints as empty space, but hg 5.8 - totaly broken. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6512] New: Using shelve's delete and interactive flag together just deletes the shelve
https://bz.mercurial-scm.org/show_bug.cgi?id=6512 Bug ID: 6512 Summary: Using shelve's delete and interactive flag together just deletes the shelve Product: Mercurial Version: unspecified Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: shelve Assignee: bugzi...@mercurial-scm.org Reporter: fah...@faheem.info CC: mercurial-devel@mercurial-scm.org Python Version: --- I assumed that using shelve with the -d (delete) and -i (interactive) flags would delete interactively. Instead, it just deleted the shelve. See the following reproduction script. rm -rf test-shelve hg init test-shelve cd test-shelve echo "First line of foo" >> foo hg add foo hg shelve echo "list shelve" hg shelve --list hg shelve -i -d default echo "list shelve again" hg shelve --list # deleted -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6513] New: Slightly inaccurate description on homepage
https://bz.mercurial-scm.org/show_bug.cgi?id=6513 Bug ID: 6513 Summary: Slightly inaccurate description on homepage Product: Mercurial project Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: bug Priority: wish Component: website Assignee: bugzi...@mercurial-scm.org Reporter: ce@cybercoment.com CC: mercurial-devel@mercurial-scm.org Per https://www.mercurial-scm.org/ "Mercurial efficiently handles projects of any size and kind." Apparently there's a limit; facebook reached it: https://engineering.fb.com/2021/04/29/developer-tools/rust/ "any size and kind" should probably be qualified with "almost". I suppose https://www.mercurial-scm.org/who could be corrected as well. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6514] New: hg status --include with regex does not work correctly with Rust extensions
https://bz.mercurial-scm.org/show_bug.cgi?id=6514 Bug ID: 6514 Summary: hg status --include with regex does not work correctly with Rust extensions Product: Mercurial Version: stable branch Hardware: All OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: mercur...@lukegb.com CC: mercurial-devel@mercurial-scm.org Python Version: --- From my understanding: a .hgignore which matches a folder combined with using hg status --ignored --include '' doesn't seem to compose properly. I experienced this on the 5.8 release tarball. This seems similar to https://bz.mercurial-scm.org/show_bug.cgi?id=6483, but the changeset that fixed that has definitely landed in this change. My test case is https://gist.github.com/lukegb/fd7b67e301b65805f65ddc3cd0b1c66c (which is an adapted copy of this test to make it easier to read: https://github.com/facebookincubator/retrie/blob/master/tests/Ignore.hs#L43-L52) This was prompted by observing that the tests for https://github.com/facebookincubator/retrie don't pass when using a version of Mercurial with the Rust extensions enabled (as part of an effort to compile the Rust extensions for Mercurial in NixOS). -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6516] New: Tags in .hgtags somtimes not usable
https://bz.mercurial-scm.org/show_bug.cgi?id=6516 Bug ID: 6516 Summary: Tags in .hgtags somtimes not usable Product: Mercurial Version: 5.6 Hardware: PC OS: All Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: dirk.heinri...@altum.de CC: mercurial-devel@mercurial-scm.org Python Version: --- Since a few weeks now, we see a strange phenomenon in one of our repositories where newly attached tags are properly recorded in .hgtags, but cannot be used. The only way to fix the problem is to remove those tags by manually editing .hgtags and reattach them. For example: % grep AXC_21.3_11 .hgtags 90a3ad39ec61076700f9ba9c8b484832c73f205c AXC_21.3_110 3ea4e9df54be1502ebb2c58beb1497dfb5ef4fb1 AXC_21.3_112 ac32a874067ed9aab86993de17c5619abd7df21f AXC_21.3_114 f7e8199d0ff44b6c2edec05f703d8d9b132860dd AXC_21.3_115 37a639ce1aee0528897890ee69d5729f60589355 AXC_21.3_116 81ef8873cbc49c68599013e30370e2e2d1810345 AXC_21.3_117 adf801c043e6b2578bf46b00f90fb978e24e3ec6 AXC_21.3_119 % hg id -r AXC_21.3_114 ac32a874067e AXC_21.3_114 % hg id -r AXC_21.3_115 abort: unknown revision 'AXC_21.3_115'! % hg log -r f7e8199d0ff44b6c2edec05f703d8d9b132860dd changeset: 133967:f7e8199d0ff4 user: date:Tue May 04 10:26:17 2021 +0200 summary: This happens for the last 4 tags. Now I edit .hgtags and reattach the tags: % vi .hgtags % hg commit -m "NO-TICKET: Remove unusable tags." % hg tag -m "NO-TICKET: Reattach unusable tag." -r f7e8199d0ff44b6c2edec05f703d8d9b132860dd AXC_21.3_115 % hg tag -m "NO-TICKET: Reattach unusable tag." -r 37a639ce1aee0528897890ee69d5729f60589355 AXC_21.3_116 % hg tag -m "NO-TICKET: Reattach unusable tag." -r 81ef8873cbc49c68599013e30370e2e2d1810345 AXC_21.3_117 % hg tag -m "NO-TICKET: Reattach unusable tag." -r adf801c043e6b2578bf46b00f90fb978e24e3ec6 AXC_21.3_119 % grep AXC_21.3_11 .hgtags 90a3ad39ec61076700f9ba9c8b484832c73f205c AXC_21.3_110 3ea4e9df54be1502ebb2c58beb1497dfb5ef4fb1 AXC_21.3_112 ac32a874067ed9aab86993de17c5619abd7df21f AXC_21.3_114 f7e8199d0ff44b6c2edec05f703d8d9b132860dd AXC_21.3_115 37a639ce1aee0528897890ee69d5729f60589355 AXC_21.3_116 81ef8873cbc49c68599013e30370e2e2d1810345 AXC_21.3_117 adf801c043e6b2578bf46b00f90fb978e24e3ec6 AXC_21.3_119 % hg id -r AXC_21.3_115 f7e8199d0ff4 AXC_21.3_115 Now they can be used again. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6517] New: Incomplete release notes
https://bz.mercurial-scm.org/show_bug.cgi?id=6517 Bug ID: 6517 Summary: Incomplete release notes Product: Mercurial project Version: unspecified Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: wiki Assignee: bugzi...@mercurial-scm.org Reporter: dirk.heinri...@altum.de CC: mercurial-devel@mercurial-scm.org Current Mercurial version is 5.8, but release notes (in the wiki) end at 5.6.1. I'd really like to know what's included in versions 5.7 to 5.8. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6480] New: test-convert-cvs assumes existence of "python"
https://bz.mercurial-scm.org/show_bug.cgi?id=6480
Bug ID: 6480
Summary: test-convert-cvs assumes existence of "python"
Product: Mercurial
Version: 5.7
Hardware: All
OS: NetBSD
Status: UNCONFIRMED
Severity: bug
Priority: wish
Component: Mercurial
Assignee: bugzi...@mercurial-scm.org
Reporter: t...@giga.or.at
CC: mercurial-devel@mercurial-scm.org
Python Version: ---
Not all packaging systems provide a "python" symlink to the python[23] to use.
This makes test-convert-cvs.t fail on pkgsrc systems, with:
--- /scratch/devel/py-mercurial/work/mercurial-5.7/tests/test-convert-cvs.t
+++ /scratch/devel/py-mercurial/work/mercurial-5.7/tests/test-convert-cvs.t.err
@@ -615,9 +615,10 @@
> @@
> ''').lstrip())
> EOF
+ $TESTTMP.sh: python: not found
+ [127]
$ cvscall -q checkout transcoding
- U transcoding/file
Test converting in normal case
--
@@ -625,18 +626,8 @@
(filtering by grep in order to check only form of debug messages)
$ hg convert --config convert.cvsps.logencoding=utf-8,euc-jp,cp932 -q
--debug transcoding transcoding-hg | grep 'transcoding by'
- transcoding by utf-8: 1.1 of file
- transcoding by utf-8: 1.1.1.1 of file
- transcoding by utf-8: 1.2 of file
- transcoding by euc-jp: 1.3 of file
- transcoding by cp932: 1.4 of file
+ [1]
$ hg -R transcoding-hg --encoding utf-8 log -T "{rev}: {desc}\n"
- 5: update tags
- 4: import
- 3: \xe3\x81\x82 (cp932) (esc)
- 2: \xe3\x81\x82 (euc-jp) (esc)
- 1: \xe3\x81\x82 (utf-8) (esc)
- 0: Initial revision
$ rm -rf transcoding-hg
Test converting in error cases
@@ -645,15 +636,13 @@
unknown encoding in convert.cvsps.logencoding
$ hg convert --config convert.cvsps.logencoding=foobar -q transcoding
transcoding-hg
- abort: unknown encoding: foobar
- (check convert.cvsps.logencoding configuration)
- [255]
+ cvslog hook: 0 entries
+ cvschangesets hook: 0 changesets
$ rm -rf transcoding-hg
no acceptable encoding in convert.cvsps.logencoding
$ hg convert --config convert.cvsps.logencoding=utf-8,euc-jp -q transcoding
transcoding-hg
- abort: no encoding can transcode CVS log message for 1.4 of file
- (check convert.cvsps.logencoding configuration)
- [255]
+ cvslog hook: 0 entries
+ cvschangesets hook: 0 changesets
$ rm -rf transcoding-hg
I assume the second and third chunks are followup failures.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6481] New: graphlog's graphshorten option produces a confusing graph shape with extra line-crossings
https://bz.mercurial-scm.org/show_bug.cgi?id=6481
Bug ID: 6481
Summary: graphlog's graphshorten option produces a confusing
graph shape with extra line-crossings
Product: Mercurial
Version: unspecified
Hardware: PC
OS: Mac OS
Status: UNCONFIRMED
Severity: feature
Priority: wish
Component: Mercurial
Assignee: bugzi...@mercurial-scm.org
Reporter: duri...@gmail.com
CC: mercurial-devel@mercurial-scm.org
Python Version: ---
I'm honestly not sure if this is fixable, but reporting from an internal bug
report:
8< --
$ hg init a
$ cd a
$ echo r0 > r0; hg ci -qAm "r0, 'level 0'"; hg phase -p .
$ for i in 1 2 3 4; do
> hg co 0; echo r$i > r$i; hg ci -qAm "r$i, 'level 1'"
> done
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
0 files updated, 0 files merged, 1 files removed, 0 files unresolved
0 files updated, 0 files merged, 1 files removed, 0 files unresolved
0 files updated, 0 files merged, 1 files removed, 0 files unresolved
$ hg merge -r 1; hg ci -qAm "r5, 'level 2', merge r1 and r4"
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
(branch merge, don't forget to commit)
$ echo r6 > r6; hg ci -qAm "r6, 'level 3'"
$ hg co 0
0 files updated, 0 files merged, 3 files removed, 0 files unresolved
$ echo r7 > r7; hg ci -qAm "r7, 'level 1' (again)"
$ cat >> .hg/hgrc <<'EOF'
> [experimental]
> graphshorten=1
>
> [templates]
> tmpl="<<<{label("desc.{phase}", desc)}>>>; parents: {revset("parents(%d)",
rev) % "({label("desc.{phase}", desc)}) "}"
>
> [alias]
> xl = log -G -T"{tmpl}" -r'sort(all(), topo)'
>
> [color]
> desc.draft=bold green
> desc.public=bold white
> EOF
$ hg log -G --style compact
@ 7[tip]:0 87679442b769 1970-01-01 00:00 + test
|r7, 'level 1' (again)
|
| o 6 f06f5b90f5b7 1970-01-01 00:00 + test
| |r6, 'level 3'
| |
| o5:4,1 edcefd3216e0 1970-01-01 00:00 + test
| |\ r5, 'level 2', merge r1 and r4
| | |
+---o 4:0 1b64d1e0d0df 1970-01-01 00:00 + test
| | r4, 'level 1'
| |
+---o 3:0 d392f3869b4c 1970-01-01 00:00 + test
| | r3, 'level 1'
| |
+---o 2:0 3f2d8a334ec1 1970-01-01 00:00 + test
| | r2, 'level 1'
| |
| o 1 fec040477454 1970-01-01 00:00 + test
|/ r1, 'level 1'
|
o 0 5135cd150024 1970-01-01 00:00 + test
r0, 'level 0'
Confusing output: even though r2 and r3 are heads, it looks like they're
ancestors of r4.
$ hg xl
@ <<>>; parents: (r0, 'level 0')
| o <<>>; parents: (r5, 'level 2', merge r1 and r4)
| o<<>>; parents: (r1, 'level 1') (r4,
'level 1')
| |\
+---o <<>>; parents: (r0, 'level 0')
+---o <<>>; parents: (r0, 'level 0')
+---o <<>>; parents: (r0, 'level 0')
| o <<>>; parents: (r0, 'level 0')
|/
o <<>>; parents:
8< --
I'm honestly not sure this is fixable, but if anyone has ideas I'm open to
suggestions.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
Mercurial-devel mailing list
Mercurial-devel@mercurial-scm.org
https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6483] New: hg status -I does not work correctly with the Rust extensions
https://bz.mercurial-scm.org/show_bug.cgi?id=6483 Bug ID: 6483 Summary: hg status -I does not work correctly with the Rust extensions Product: Mercurial Version: default branch Hardware: PC OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: rgo...@octobus.net CC: mercurial-devel@mercurial-scm.org Python Version: --- I just noticed that: $ hg init repo $ cd repo $ touch a.rb b.rb c.sql $ hg add a.rb b.rb c.sql $ HGMODULEPOLICY=rust+c hg st -a -I '**/*.rb' A a.rb A b.rb A c.sql $ HGMODULEPOLICY=c hg st -a -I '**/*.rb' A a.rb A b.rb A c.sql It appears to work correctly when listing unknowns, though. $ HGMODULEPOLICY=rust+c hg st -au -I '**/*.rb' A a.rb A b.rb -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6470] New: test-wireproto-exchangev2-shallow.t is flaky
https://bz.mercurial-scm.org/show_bug.cgi?id=6470 Bug ID: 6470 Summary: test-wireproto-exchangev2-shallow.t is flaky Product: Mercurial Version: unspecified Hardware: PC OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: pierre-yves.da...@ens-lyon.org CC: mercurial-devel@mercurial-scm.org Python Version: --- Their seems to be possible unstability in output order: https://foss.heptapod.net/octobus/mercurial-devel/-/jobs/154367 -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6502] New: Hg archive download in a slow manner.
https://bz.mercurial-scm.org/show_bug.cgi?id=6502 Bug ID: 6502 Summary: Hg archive download in a slow manner. Product: Mercurial Version: 4.6 Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: sasthama...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- We are downloading the repository on a changeset basis instead of cloning. Till 4.0 download completed with a max of 10 secs. After updating the mercurial version to 4.6.2, the download completed in minutes ( Yes, more than 3 minutes ). Due to that, our automated process time is getting increased. Why are we suspecting an issue in Mercurial 4.0? Whatever the changesets generated on 4.0 which downloads faster in earlier and updated versions. But, upcoming commits after updating to 4.6.2 those changesets-based commits alone delay in downloading process. Kindly help us to resolve the slowness issue, which would be much appreciated. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6504] New: regression in url parsing on python 3.9
https://bz.mercurial-scm.org/show_bug.cgi?id=6504 Bug ID: 6504 Summary: regression in url parsing on python 3.9 Product: Mercurial Version: stable branch Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: hgweb Assignee: bugzi...@mercurial-scm.org Reporter: pierre-yves.da...@ens-lyon.org CC: mercurial-devel@mercurial-scm.org Python Version: --- Starting with Python 3.9, mercurial is no longer able to parse hgweb call using ';' as parameter separator. This is the fault of a behavior change of the `urllib.parse.parse_qsl` function: Changed in version 3.9.2: Added separator parameter with the default value of &. Python versions earlier than Python 3.9.2 allowed using both ; and & as query parameter separator. This has been changed to allow only a single separator key, with & as the default separator. They are no obvious way to restore the previous behavior… This result in the following test failure. --- /home/marmoute/src/mercurial-dev/tests/test-archive.t +++ /home/marmoute/src/mercurial-dev/tests/test-archive.t.err @@ -350,49 +350,59 @@ > sys.stderr.write(str(e) + '\n') > EOF $ "$PYTHON" getarchive.py "$TIP" gz | gunzip | tar tf - 2>/dev/null - test-archive-1701ef1f1510/.hg_archival.txt - test-archive-1701ef1f1510/.hgsub - test-archive-1701ef1f1510/.hgsubstate - test-archive-1701ef1f1510/bar - test-archive-1701ef1f1510/baz/bletch - test-archive-1701ef1f1510/foo - test-archive-1701ef1f1510/subrepo/sub + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=gz + + gzip: stdin: unexpected end of file + [2] $ "$PYTHON" getarchive.py "$TIP" bz2 | bunzip2 | tar tf - 2>/dev/null - test-archive-1701ef1f1510/.hg_archival.txt - test-archive-1701ef1f1510/.hgsub - test-archive-1701ef1f1510/.hgsubstate - test-archive-1701ef1f1510/bar - test-archive-1701ef1f1510/baz/bletch - test-archive-1701ef1f1510/foo - test-archive-1701ef1f1510/subrepo/sub + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=bz2 + + bunzip2: Compressed file ends unexpectedly; + perhaps it is corrupted? *Possible* reason follows. + bunzip2: Inappropriate ioctl for device + Input file = (stdin), output file = (stdout) + + It is possible that the compressed file(s) have become corrupted. + You can use the -tvv option to test integrity of such files. + + You can use the `bzip2recover' program to attempt to recover + data from undamaged sections of corrupted files. + + [2] $ "$PYTHON" getarchive.py "$TIP" zip > archive.zip + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=zip $ unzip -t archive.zip Archive: archive.zip - testing: test-archive-1701ef1f1510/.hg_archival.txt*OK (glob) - testing: test-archive-1701ef1f1510/.hgsub*OK (glob) - testing: test-archive-1701ef1f1510/.hgsubstate*OK (glob) - testing: test-archive-1701ef1f1510/bar*OK (glob) - testing: test-archive-1701ef1f1510/baz/bletch*OK (glob) - testing: test-archive-1701ef1f1510/foo*OK (glob) - testing: test-archive-1701ef1f1510/subrepo/sub*OK (glob) - No errors detected in compressed data of archive.zip. +End-of-central-directory signature not found. Either this file is not +a zipfile, or it constitutes one disk of a multi-part archive. In the +latter case the central directory and zipfile comment will be found on +the last disk(s) of this archive. + unzip: cannot find zipfile directory in one of archive.zip or + archive.zip.zip, and cannot find archive.zip.ZIP, period. + [9] test that we can download single directories and files $ "$PYTHON" getarchive.py "$TIP" gz baz | gunzip | tar tf - 2>/dev/null - test-archive-1701ef1f1510/baz/bletch + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=gz;file=baz + + gzip: stdin: unexpected end of file + [2] $ "$PYTHON" getarchive.py "$TIP" gz foo | gunzip | tar tf - 2>/dev/null - test-archive-1701ef1f1510/foo + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=gz;file=foo + + gzip: stdin: unexpected end of file + [2] test that we detect file patterns that match no files $ "$PYTHON" getarchive.py "$TIP" gz foobar - HTTP Error 404: file(s) not found: foobar + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=gz;file=foobar test that we reject unsafe patterns $ "$PYTHON" getarchive.py "$TIP" gz relre:baz - HTTP Error 404: file(s) not found: relre:baz + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=gz;file=relre:baz $ killdaemons.py ERROR: test-archive.t output changed ! Failed test-archive.t: output changed -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org
[Bug 6506] New: testsuite failures on alpine linux x86 (32bit)
https://bz.mercurial-scm.org/show_bug.cgi?id=6506
Bug ID: 6506
Summary: testsuite failures on alpine linux x86 (32bit)
Product: Mercurial
Version: 5.7
Hardware: PC
OS: Linux
Status: UNCONFIRMED
Severity: bug
Priority: wish
Component: Mercurial
Assignee: bugzi...@mercurial-scm.org
Reporter: nc...@alpinelinux.org
CC: mercurial-devel@mercurial-scm.org
Python Version: ---
Some of the tests fails on 32 bit alpine linux, which uses musl libc, with rust
1.51.0.
```
if command -v cargo >/dev/null 2>&1; then \
make rust-tests; \
fi
make[1]: Entering directory
'/home/ncopa/aports/community/mercurial/src/mercurial-5.7'
cd /home/ncopa/aports/community/mercurial/src/mercurial-5.7/rust/hg-cpython \
&& cargo test --quiet --all \
--no-default-features --features "python3-bin "
warning: panic message is not a string literal
--> hg-core/src/copy_tracing.rs:348:42
|
348 | assert!(token < self.path.len(), format!("Unknown token: {}",
token));
|
^^^
|
= note: `#[warn(non_fmt_panic)]` on by default
= note: this is no longer accepted in Rust 2021
= note: this warning originates in a macro (in Nightly builds, run with -Z
macro-backtrace for more info)
warning: 1 warning emitted
warning: panic message is not a string literal
--> hg-core/src/copy_tracing.rs:348:42
|
348 | assert!(token < self.path.len(), format!("Unknown token: {}",
token));
|
^^^
|
= note: `#[warn(non_fmt_panic)]` on by default
= note: this is no longer accepted in Rust 2021
= note: this warning originates in a macro (in Nightly builds, run with -Z
macro-backtrace for more info)
warning: panic message is not a string literal
--> hg-core/src/revlog/node.rs:399:27
|
399 | err => panic!(format!("Should have been TooLong, got {:?}",
err)),
|
^^
|
= note: this is no longer accepted in Rust 2021
= note: this warning originates in a macro (in Nightly builds, run with -Z
macro-backtrace for more info)
warning: 2 warnings emitted
warning: panic message is not a string literal
--> hg-core/tests/test_missing_ancestors.rs:159:16
|
159 | panic!(format!(
| ^
160 | | "Equality assertion failed (left != right)
161 | | left={:?}
162 | | right={:?}
... |
173 | | self.random_seed,
174 | | ));
| |_^
|
= note: `#[warn(non_fmt_panic)]` on by default
= note: this is no longer accepted in Rust 2021
= note: this warning originates in a macro (in Nightly builds, run with -Z
macro-backtrace for more info)
warning: panic message is not a string literal
--> hg-core/tests/test_missing_ancestors.rs:234:16
|
234 | panic!(err_msg);
|^^^
|
= note: this is no longer accepted in Rust 2021
help: add a "{}" format string to Display the message
|
234 | panic!("{}", err_msg);
|^
help: or use std::panic::panic_any instead
|
234 | std::panic::panic_any(err_msg);
| ^^
warning: 2 warnings emitted
running 110 tests
100/110
..
failures:
revlog::index::tests::test_offset stdout
thread 'revlog::index::tests::test_offset' panicked at 'assertion failed:
`(left == right)`
left: `0`,
right: `1`', hg-core/src/revlog/index.rs:353:9
revlog::index::tests::test_uncompressed_len stdout
thread 'revlog::index::tests::test_uncompressed_len' panicked at 'range end
index 16 out of range for slice of length 8',
hg-core/src/revlog/index.rs:180:30
revlog::index::tests::test_base_revision stdout
thread 'revlog::index::tests::test_base_revision' panicked at 'range start
index 16 out of range for slice of length 8',
hg-core/src/revlog/index.rs:188:30
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
revlog::index::tests::test_compressed_len stdout
thread 'revlog::index::tests::test_compressed_len' panicked at 'range end index
12 out of range for slice of length 8', hg-core/src/revlog/index.rs:175:30
failures:
revlog::index::tests::test_base_revision
revlog::index::tests::test_compressed_len
revlog::index::tests::test_offset
revlog::index::tests::test_uncompressed_len
test result: FAILED. 106 passed; 4 failed; 0 ignored; 0 measured; 0 filtered
out; finished in 0.02s
error: test failed, to rerun pass '-p hg-core --lib'
make[1]: *** [Makefile:145: rust-tests] Error
[Bug 6501] New: Rebase switches parent order of merge
https://bz.mercurial-scm.org/show_bug.cgi?id=6501 Bug ID: 6501 Summary: Rebase switches parent order of merge Product: Mercurial Version: unspecified Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: rebase Assignee: bugzi...@mercurial-scm.org Reporter: m...@manueljacob.de CC: mercurial-devel@mercurial-scm.org Python Version: --- $ cat >> $HGRCPATH < [extensions] > rebase = > [experimental] > evolution = all > EOF $ hg init $ touch test1 test2 $ hg add test1 test2 $ hg ci -m base $ echo left > test1 $ hg ci -m left -q $ hg up 0 -q $ echo right1 > test2 $ hg ci -m right1 -q $ hg up 0 -q $ echo right2 > test2 $ hg ci -m right2 -q $ hg up 2 -q $ touch test3 $ hg add test3 $ hg ci -m right $ hg up 1 -q $ hg merge 4 -q $ hg ci -m merge $ hg log -G @changeset: 5:fba4923e310a |\ tag: tip | | parent: 1:429ab2e55fe3 | | parent: 4:590a481a3fab | | user:test | | date:Thu Jan 01 00:00:00 1970 + | | summary: merge | | | o changeset: 4:590a481a3fab | | parent: 2:db5f9ff551fb | | user:test | | date:Thu Jan 01 00:00:00 1970 + | | summary: right | | | | o changeset: 3:ea268a950081 | | | parent: 0:477af4eeb07e | | | user:test | | | date:Thu Jan 01 00:00:00 1970 + | | | summary: right2 | | | | o | changeset: 2:db5f9ff551fb | |/ parent: 0:477af4eeb07e | |user:test | |date:Thu Jan 01 00:00:00 1970 + | |summary: right1 | | o | changeset: 1:429ab2e55fe3 |/ user:test |date:Thu Jan 01 00:00:00 1970 + |summary: left | o changeset: 0:477af4eeb07e user:test date:Thu Jan 01 00:00:00 1970 + summary: base $ hg rebase -d 3 -s 4 rebasing 4:590a481a3fab "right" rebasing 5:fba4923e310a tip "merge" $ hg log -G @changeset: 7:4244bf817b97 |\ tag: tip | | parent: 6:5fe7af8712dd | | parent: 1:429ab2e55fe3 | | user:test | | date:Thu Jan 01 00:00:00 1970 + | | summary: merge | | | o changeset: 6:5fe7af8712dd | | parent: 3:ea268a950081 | | user:test | | date:Thu Jan 01 00:00:00 1970 + | | summary: right | | | o changeset: 3:ea268a950081 | | parent: 0:477af4eeb07e | | user:test | | date:Thu Jan 01 00:00:00 1970 + | | summary: right2 | | | | o changeset: 2:db5f9ff551fb | |/ parent: 0:477af4eeb07e | |user:test | |date:Thu Jan 01 00:00:00 1970 + | |summary: right1 | | o | changeset: 1:429ab2e55fe3 |/ user:test |date:Thu Jan 01 00:00:00 1970 + |summary: left | o changeset: 0:477af4eeb07e user:test date:Thu Jan 01 00:00:00 1970 + summary: base Before the rebase, "left" is the first parent and "right" is the second parent. After the rebase, "right" is the first parent and "left" is the second parent, while "left" should stay the first parent and "right" should stay the second parent. This is basically the same problem as https://bz.mercurial-scm.org/show_bug.cgi?id=6141, but it is easier to add a test for it since reproducing it does not depend on out-of-tree extensions. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6497] New: RFE: hg which command, that identifies where a subcommand is defined
https://bz.mercurial-scm.org/show_bug.cgi?id=6497 Bug ID: 6497 Summary: RFE: hg which command, that identifies where a subcommand is defined Product: Mercurial Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: feature Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: a...@anm.me CC: mercurial-devel@mercurial-scm.org Python Version: --- This is a feature request for a "which" subcommand. Like which in Unix-like environments, "hg which subcommand" should identify where 'subcommand' was defined, be it an alias (including which config file defined the alias, ideally with line number), an extension (possibly including which config file declared its inclusion), or a core command. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6498] New: [evolve] user/username confusion
https://bz.mercurial-scm.org/show_bug.cgi?id=6498 Bug ID: 6498 Summary: [evolve] user/username confusion Product: Mercurial Version: 5.7.1 Hardware: PC OS: All Status: UNCONFIRMED Severity: bug Priority: wish Component: evolution Assignee: bugzi...@mercurial-scm.org Reporter: asheme...@gmail.com CC: mercurial-devel@mercurial-scm.org, pierre-yves.da...@ens-lyon.org Python Version: --- (This seems slightly improved in 5.7.x in that it doesn't allow you to commit without supplying a username thereby limiting shooting yourself in the foot as much, in earlier versions this was less an issue since it seems to have defaulted to your login on Linux/Unix systems.) When using many of evolve's commands with --user "Name " while $HOME/.hgrc has no username set, the command will abort with an "abort: no username supplied", e.g.: $ hg metaedit --user "Name " transaction abort! rollback completed abort: no username supplied (use 'hg config --edit' to set your username) Given how user/username are understood by many people as being synonyms, this can be quite confusing. I also initially got stumped a bit why I couldn't make this work. That is, until I spoke with marmoute and mharbison on IRC. This might be sort of related to bug 3169 and bug 3898. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6499] New: 5.7.1: test-archive.t test failure
https://bz.mercurial-scm.org/show_bug.cgi?id=6499 Bug ID: 6499 Summary: 5.7.1: test-archive.t test failure Product: Mercurial Version: 5.7.1 Hardware: All OS: NetBSD Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: t...@giga.or.at CC: mercurial-devel@mercurial-scm.org Python Version: --- I see a new failure in 5.7.1. It might be that this is also reported in https://bz.mercurial-scm.org/show_bug.cgi?id=6352 but that also reports other problems, so I thought it'd be good to have a separate bug report for this particular issue. Just close it if you disagree :) --- /scratch/devel/py-mercurial/work/mercurial-5.7.1/tests/test-archive.t +++ /scratch/devel/py-mercurial/work/mercurial-5.7.1/tests/test-archive.t.err @@ -350,49 +350,52 @@ > sys.stderr.write(str(e) + '\n') > EOF $ "$PYTHON" getarchive.py "$TIP" gz | gunzip | tar tf - 2>/dev/null - test-archive-1701ef1f1510/.hg_archival.txt - test-archive-1701ef1f1510/.hgsub - test-archive-1701ef1f1510/.hgsubstate - test-archive-1701ef1f1510/bar - test-archive-1701ef1f1510/baz/bletch - test-archive-1701ef1f1510/foo - test-archive-1701ef1f1510/subrepo/sub + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=gz + gunzip: (stdin): unexpected end of file $ "$PYTHON" getarchive.py "$TIP" bz2 | bunzip2 | tar tf - 2>/dev/null - test-archive-1701ef1f1510/.hg_archival.txt - test-archive-1701ef1f1510/.hgsub - test-archive-1701ef1f1510/.hgsubstate - test-archive-1701ef1f1510/bar - test-archive-1701ef1f1510/baz/bletch - test-archive-1701ef1f1510/foo - test-archive-1701ef1f1510/subrepo/sub + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=bz2 + + bunzip2: Compressed file ends unexpectedly; + perhaps it is corrupted? *Possible* reason follows. + bunzip2: Inappropriate ioctl for device + Input file = (stdin), output file = (stdout) + + It is possible that the compressed file(s) have become corrupted. + You can use the -tvv option to test integrity of such files. + + You can use the `bzip2recover' program to attempt to recover + data from undamaged sections of corrupted files. + $ "$PYTHON" getarchive.py "$TIP" zip > archive.zip + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=zip $ unzip -t archive.zip Archive: archive.zip - testing: test-archive-1701ef1f1510/.hg_archival.txt*OK (glob) - testing: test-archive-1701ef1f1510/.hgsub*OK (glob) - testing: test-archive-1701ef1f1510/.hgsubstate*OK (glob) - testing: test-archive-1701ef1f1510/bar*OK (glob) - testing: test-archive-1701ef1f1510/baz/bletch*OK (glob) - testing: test-archive-1701ef1f1510/foo*OK (glob) - testing: test-archive-1701ef1f1510/subrepo/sub*OK (glob) - No errors detected in compressed data of archive.zip. +End-of-central-directory signature not found. Either this file is not +a zipfile, or it constitutes one disk of a multi-part archive. In the +latter case the central directory and zipfile comment will be found on +the last disk(s) of this archive. + unzip: cannot find zipfile directory in one of archive.zip or + archive.zip.zip, and cannot find archive.zip.ZIP, period. + [9] test that we can download single directories and files $ "$PYTHON" getarchive.py "$TIP" gz baz | gunzip | tar tf - 2>/dev/null - test-archive-1701ef1f1510/baz/bletch + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=gz;file=baz + gunzip: (stdin): unexpected end of file $ "$PYTHON" getarchive.py "$TIP" gz foo | gunzip | tar tf - 2>/dev/null - test-archive-1701ef1f1510/foo + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=gz;file=foo + gunzip: (stdin): unexpected end of file test that we detect file patterns that match no files $ "$PYTHON" getarchive.py "$TIP" gz foobar - HTTP Error 404: file(s) not found: foobar + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=gz;file=foobar test that we reject unsafe patterns $ "$PYTHON" getarchive.py "$TIP" gz relre:baz - HTTP Error 404: file(s) not found: relre:baz + HTTP Error 400: no such method: archive;node=1701ef1f1510;type=gz;file=relre:baz $ killdaemons.py ERROR: test-archive.t output changed -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6500] New: KeyError in hg fold
https://bz.mercurial-scm.org/show_bug.cgi?id=6500 Bug ID: 6500 Summary: KeyError in hg fold Product: Mercurial Version: 5.7 Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: normal Component: evolution Assignee: bugzi...@mercurial-scm.org Reporter: z...@zash.se CC: mercurial-devel@mercurial-scm.org, pierre-yves.da...@ens-lyon.org Python Version: 3.7 Not quite sure how I got here, but tip is an almost empty commit that adds a blank line for some reason. It may have been created when attempting to fold pair of commits via histedit, which somehow ended up creating some left-over temporary commit, and also this duplicate commit. Wasn't able to reproduce this in a smaller repo so I'm just dropping the traceback here in the hopes that it makes sense to someone. @ 1d3e tip no-topic | o 5701 topic |/ o f15d topic $ hg fold -r .+.^ --exact transaction abort! rollback completed ** unknown exception encountered, please report by visiting ** https://mercurial-scm.org/wiki/BugTracker ** Python 3.7.3 (default, Jul 25 2020, 13:03:44) [GCC 8.3.0] ** Mercurial Distributed SCM (version 5.7) ** Extensions loaded: absorb, evolve 10.2.0, extdiff, fastannotate, fix, githelp, histedit, patchbomb, purge, rebase, releasenotes, relink, schemes, show, topic 0.21.0, transplant Traceback (most recent call last): File "/usr/lib/python3/dist-packages/mercurial/commandserver.py", line 499, in _serverequest sv.serve() File "/usr/lib/python3/dist-packages/mercurial/commandserver.py", line 403, in serve while self.serveone(): File "/usr/lib/python3/dist-packages/mercurial/commandserver.py", line 377, in serveone handler(self) File "/usr/lib/python3/dist-packages/mercurial/chgserver.py", line 585, in runcommand return super(chgcmdserver, self).runcommand() File "/usr/lib/python3/dist-packages/mercurial/commandserver.py", line 358, in runcommand ret = self._dispatchcommand(req) & 255 File "/usr/lib/python3/dist-packages/mercurial/commandserver.py", line 297, in _dispatchcommand return dispatch.dispatch(req) File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 245, in dispatch status = _rundispatch(req) File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 289, in _rundispatch ret = _runcatch(req) or 0 File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 465, in _runcatch return _callcatch(ui, _runcatchfunc) File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 475, in _callcatch return scmutil.callcatch(ui, func) File "/usr/lib/python3/dist-packages/mercurial/scmutil.py", line 155, in callcatch return func() File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 455, in _runcatchfunc return _dispatch(req) File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 1259, in _dispatch lui, repo, cmd, fullargs, ui, options, d, cmdpats, cmdoptions File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 913, in runcommand ret = _runcommand(ui, options, cmd, d) File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 1270, in _runcommand return cmdfunc() File "/usr/lib/python3/dist-packages/mercurial/dispatch.py", line 1256, in d = lambda: util.checksignature(func)(ui, *args, **strcmdopt) File "/usr/lib/python3/dist-packages/mercurial/util.py", line 1867, in check return func(*args, **kwargs) File "/usr/lib/python3/dist-packages/hgext3rd/evolve/cmdrewrite.py", line 745, in fold commitopts=commitopts) File "/usr/lib/python3/dist-packages/hgext3rd/evolve/rewriteutil.py", line 279, in rewrite newid = repo.commitctx(new) File "/usr/lib/python3/dist-packages/hgext3rd/topic/__init__.py", line 502, in commitctx del ctx.extra()[constants.extrakey] KeyError: b'topic' -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6496] New: test-chg is flaky
https://bz.mercurial-scm.org/show_bug.cgi?id=6496 Bug ID: 6496 Summary: test-chg is flaky Product: Mercurial Version: stable branch Hardware: PC OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: chg Assignee: bugzi...@mercurial-scm.org Reporter: pierre-yves.da...@ens-lyon.org CC: mercurial-devel@mercurial-scm.org Python Version: --- The part about pager and interruption use `sleep(x)` and can fails on heavy load. Here is an example failure. https://foss.heptapod.net/octobus/mercurial-devel/-/jobs/173313 -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6493] New: Changeset 53a5e100b497 references nonexistent "content" subrepo
https://bz.mercurial-scm.org/show_bug.cgi?id=6493 Bug ID: 6493 Summary: Changeset 53a5e100b497 references nonexistent "content" subrepo Product: Mercurial project Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: bug Priority: wish Component: website Assignee: bugzi...@mercurial-scm.org Reporter: p...@bissex.net CC: mercurial-devel@mercurial-scm.org I cloned the hg-website repo to make a patch for one of the two open bugs. When I tried to push my local clone to my server (i.e. for my fork), it died thus: $ hg push ssh://h...@hg.sr.ht/~paulbissex/hg-website pushing to ssh://h...@hg.sr.ht/~paulbissex/hg-website searching for changes abort: subrepo 'content' not found in revision 53a5e100b497 Here's the commit. You can see it does make a change to .hgsub: https://www.mercurial-scm.org/repo/hg-website/rev/53a5e100b497 Attempting to check out that rev produces a 404: cloning subrepo content from https://www.mercurial-scm.org/repo/hg-website/content abort: HTTP Error 404: Not Found Not sure what tactics are applicable here. But this is an obstacle to users (like me) who want to contribute fixes to the website. Happy to pitch in on a fix such as I'm able. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6492] New: Remove or update "version 2.7" parenthetical in Python requirement on Downloads page
https://bz.mercurial-scm.org/show_bug.cgi?id=6492 Bug ID: 6492 Summary: Remove or update "version 2.7" parenthetical in Python requirement on Downloads page Product: Mercurial project Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: bug Priority: wish Component: website Assignee: bugzi...@mercurial-scm.org Reporter: max.ch...@gmail.com CC: mercurial-devel@mercurial-scm.org Mercurial has officially supported Python 3 since version 5.2, which came out in late 2019, over a year ago. The Downloads page (https://www.mercurial-scm.org/downloads) still emphasizes "version 2.7" as a requirement. (This was originally done to indicate a deprecation of Python 2.6 support.) This note is currently tripping people up (see https://www.boringcactus.com/2021/02/22/can-we-please-move-past-git.html). It should either be removed, or updated to reflect the actual supported versions. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6491] New: Repository in a state where files are erroneously identified as missing
https://bz.mercurial-scm.org/show_bug.cgi?id=6491 Bug ID: 6491 Summary: Repository in a state where files are erroneously identified as missing Product: Mercurial Version: 5.6.1 Hardware: PC OS: Other Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: mercur...@mbox.tinloaf.de CC: mercurial-devel@mercurial-scm.org Python Version: --- I managed to get a mercurial repository into a state where a bunch of files (which exist on disk) are detected as missing, and there seems to be no way of "bringing them back" (at least as far as mercurial is considered). I suspect that this could be caused by accessing the same repository (as in: the very same folder on the disk) both from Windows and Linux (inside a WSL 1 container). My Windows mercurial version is 5.6.1, the Linux mercurial version is 5.3.1. The repository is in this weird state (from the Windows side of things): PS D:\development\DEFAULT\efa> hg status PS D:\development\DEFAULT\efa> hg status -d | Measure-Object -line Lines Words Characters Property - - -- 101 So, `status` just says nothing, but `status -d` finds 101 missing files. Weirdly, the Linux client does not see any missing files: lba@One:~/dev/DEFAULT/efa$ hg status -d | wc -l 0 Okay, just restore by `update -C` (on the Windows side): PS D:\development\DEFAULT\efa> hg update -C 101 files updated, 0 files merged, 0 files removed, 0 files unresolved updated to "9a390e7aae73: fixed" 1 other heads for branch "default" However, the files are still missing: PS D:\development\DEFAULT\efa> hg status -d | Measure-Object -line Lines Words Characters Property - - -- 101 In fact, I can run `hg update -C` multiple times successively, and it always claims to update those 101 files: PS D:\development\DEFAULT\efa> hg up -C 101 files updated, 0 files merged, 0 files removed, 0 files unresolved updated to "9a390e7aae73: fixed" 1 other heads for branch "default" PS D:\development\DEFAULT\efa> hg up -C 101 files updated, 0 files merged, 0 files removed, 0 files unresolved updated to "9a390e7aae73: fixed" 1 other heads for branch "default" To make things ever weirder, the files are actually there: PS D:\development\DEFAULT\efa> hg status -d | select -first 1 ! build\docker\Dockerfile PS D:\development\DEFAULT\efa> ls .\build\docker\Dockerfile Directory: D:\development\DEFAULT\efa\build\docker Mode LastWriteTime Length Name - -- -a 2/23/2021 12:29 PM641 Dockerfile I've tried the following three suggestions (by marmoute and nbjoerg in the IRC channel), without luck: * hg up -r null ; hg up * hg debugrebuilddirstate ; hg up -C * rm .\hg\wcache\* ; hg up -C All of them result in the same situation as outlined above. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6495] New: utf-8 encoding error in hg log --style changelog
https://bz.mercurial-scm.org/show_bug.cgi?id=6495 Bug ID: 6495 Summary: utf-8 encoding error in hg log --style changelog Product: Mercurial Version: 5.6.1 Hardware: PC OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: arne_...@web.de CC: mercurial-devel@mercurial-scm.org Python Version: --- Using hg log --style=changelog with old repositories using non-utf-8 encoding, hg aborts with an error. To reproduce: hg clone https://hg.sr.ht/~arnebab/ews && cd ews/Hauptdokument/ews30/ hg log --style=changelog >/dev/null abort: decoding near 'triebe im �berblick ': 'utf-8' codec can't decode byte 0xdc in position 36: invalid continuation byte! Normal log works: hg log >/dev/null -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6507] New: share can't work with repo at samba-path
https://bz.mercurial-scm.org/show_bug.cgi?id=6507 Bug ID: 6507 Summary: share can't work with repo at samba-path Product: Mercurial Version: unspecified Hardware: PC OS: Windows Status: UNCONFIRMED Severity: bug Priority: wish Component: share Assignee: bugzi...@mercurial-scm.org Reporter: alexraynepe...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- hallow! works on win10 ru. have place my shared-repo and original-repo at network file-server at path \\Server\... if my path have national symbools, hg 5.7.1 crash to take status of shared-repo. this checked on py2 and py3 reproducing as: 1) place my repos at national dirs like : \\Server\vector so that original-repo: \\SERVER\Development\vector\spodes\DLMS.gurux\c.hggit\ shared-repo at \\SERVER\Development\vector\vector10c\ware\gurux\dlms-c\ and .hg/sharedpath have: \\SERVER\Development\vector\spodes\DLMS.gurux\c.hggit\ 2) invoke hs status: C:\Windows>c:\Python38\Scripts\hg --debug --traceback status \\SERVER\Development\vector\vector10c\ware\gurux\dlms-c\ Traceback (most recent call last): File "c:\Python38\lib\site-packages\mercurial\dispatch.py", line 1209, in _dispatch repo = hg.repository( File "c:\Python38\lib\site-packages\mercurial\hg.py", line 225, in repository peer = _peerorrepo( File "c:\Python38\lib\site-packages\mercurial\hg.py", line 192, in _peerorrepo obj = _peerlookup(path).instance( File "c:\Python38\lib\site-packages\mercurial\localrepo.py", line 3350, in instance return makelocalrepository(ui, localpath, intents=intents) File "c:\Python38\lib\site-packages\mercurial\localrepo.py", line 546, in makelocalrepository raise error.RepoError(_(b'repository %s not found') % path) mercurial.error.RepoError: b'repository not found' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "c:\Python38\lib\site-packages\mercurial\windows.py", line 162, in posixfile fp = osutil.posixfile(name, mode, buffering) # may raise WindowsError FileNotFoundError: [WinError 2] �� ��� � � : 'SERVER\\Development\\vector\\spodes\\DLMS.gurux\\c.hggit\\requires' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "c:\Python38\lib\site-packages\mercurial\scmutil.py", line 155, in callcatch return func() File "c:\Python38\lib\site-packages\mercurial\dispatch.py", line 455, in _runcatchfunc return _dispatch(req) File "c:\Python38\lib\site-packages\mercurial\dispatch.py", line 1235, in _dispatch return _dispatch(req) File "c:\Python38\lib\site-packages\mercurial\dispatch.py", line 1209, in _dispatch repo = hg.repository( File "c:\Python38\lib\site-packages\mercurial\hg.py", line 225, in repository peer = _peerorrepo( File "c:\Python38\lib\site-packages\mercurial\hg.py", line 192, in _peerorrepo obj = _peerlookup(path).instance( File "c:\Python38\lib\site-packages\mercurial\localrepo.py", line 3350, in instance return makelocalrepository(ui, localpath, intents=intents) File "c:\Python38\lib\site-packages\mercurial\localrepo.py", line 619, in makelocalrepository sourcerequires = _readrequires(sharedvfs, False) File "c:\Python38\lib\site-packages\mercurial\localrepo.py", line 478, in _readrequires requirements = set(vfs.read(b'requires').splitlines()) File "c:\Python38\lib\site-packages\mercurial\vfs.py", line 95, in read with self(path, b'rb') as fp: File "c:\Python38\lib\site-packages\mercurial\vfs.py", line 470, in __call__ fp = util.posixfile(f, mode) File "c:\Python38\lib\site-packages\mercurial\windows.py", line 180, in posixfile raise IOError( FileNotFoundError: [Errno 2] \\SERVER\Development\vector\spodes\DLMS.gurux\c.hggit\requires: �� ��� � � abort: \\SERVER\Development\vector\spodes\DLMS.gurux\c.hggit\requires: �� ��� � � -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6508] New: sparse extention can't avoid sub-repo
https://bz.mercurial-scm.org/show_bug.cgi?id=6508 Bug ID: 6508 Summary: sparse extention can't avoid sub-repo Product: Mercurial Version: 5.7.1 Hardware: PC OS: Windows Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: alexraynepe...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- Hallow! use hg 5.7.1 py2 on win8.1 ru my repo have a big set of sub-repos, most of them - [git] i try checkout sparse of repo - a few directories, that not have any of sub-repos. but checkout sparse - upload all sub-repos. it's awful. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6509] New: Mercurial rust extensions crash
https://bz.mercurial-scm.org/show_bug.cgi?id=6509 Bug ID: 6509 Summary: Mercurial rust extensions crash Product: Mercurial Version: 5.6.1 Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: mathias.dem...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- We're inconsistently seeing this crash in our builds, which run in a CentOS 7 container (host OS is also CentOS 7). Command that runs (inside make): /bin/hg --config ui.ssh='ssh -oStrictHostKeyChecking=no -oUserKnownHostsFile=/dev/null' --config ui.clonebundlefallback=True --config extensions.hgext.purge= -R purge --all Error: *** Error in `/usr/bin/python3': double free or corruption (fasttop): 0x0219ec10 *** *** Error in `/usr/bin/python3': double free or corruption (fasttop): 0x0219ec10 *** *** Error in `/usr/bin/python3': double free or corruption (fasttop): 0x0219ec10 *** *** Error in `/usr/bin/python3': double free or corruption (fasttop): 0x0219ec10 *** Decoded backtrace: Program terminated with signal 6, Aborted. #0 0x7f897eb6b3d7 in raise () from /lib64/libc.so.6 #0 0x7f897eb6b3d7 in raise () from /lib64/libc.so.6 #1 0x7f897eb6cac8 in abort () from /lib64/libc.so.6 #2 0x7f897ebadf67 in __libc_message () from /lib64/libc.so.6 #3 0x7f897ebb4474 in malloc_printerr () from /lib64/libc.so.6 #4 0x7f897ebb9770 in _int_realloc () from /lib64/libc.so.6 #5 0x7f897ebbae12 in realloc () from /lib64/libc.so.6 #6 0x7f897fd53e51 in store_fd (file=0x7f895400dee0, fd=14) at ../path.c:39 #7 0x7f897fd5195f in opendir (name=0x7f8954005e30 "/repo/builder/repo/vobs/esam/build/reborn/buildroot-isam-reborn-x86-qemu-unit-m32/boot/afboot-stm32") at ../libaccess.c:332 #8 0x7f897868c053 in std::sys::unix::fs::readdir::h72e024f03cced67b () from /usr/lib64/python3.6/site-packages/mercurial/rustext.cpython-36m-x86_64-linux-gnu.so #9 0x7f897855a3eb in hg::dirstate::status::list_directory::h0d0649bfa6ff4dfc () from /usr/lib64/python3.6/site-packages/mercurial/rustext.cpython-36m-x86_64-linux-gnu.so #10 0x7f897855ae49 in hg::dirstate::status::Status$LT$M$GT$::traverse_dir::h4c41d7d5b67110c4 () from /usr/lib64/python3.6/site-packages/mercurial/rustext.cpython-36m-x86_64-linux-gnu.so #11 0x7f89784f82da in _$LT$std..panic..AssertUnwindSafe$LT$F$GT$$u20$as$u20$core..ops..function..FnOnce$LT$$LP$$RP$$GT$$GT$::call_once::h24ed0e9c68e77ee4 () from /usr/lib64/python3.6/site-packages/mercurial/rustext.cpython-36m-x86_64-linux-gnu.so #12 0x7f897852227f in _$LT$rayon_core..job..HeapJob$LT$BODY$GT$$u20$as$u20$rayon_core..job..Job$GT$::execute::h41abbd7b1792dfc2 () from /usr/lib64/python3.6/site-packages/mercurial/rustext.cpython-36m-x86_64-linux-gnu.so #13 0x7f897865bdd1 in rayon_core::registry::WorkerThread::wait_until_cold::h3c79165e986a165a () from /usr/lib64/python3.6/site-packages/mercurial/rustext.cpython-36m-x86_64-linux-gnu.so #14 0x7f897865a539 in rayon_core::registry::ThreadBuilder::run::h6af6dd34d0625309 () from /usr/lib64/python3.6/site-packages/mercurial/rustext.cpython-36m-x86_64-linux-gnu.so #15 0x7f897865d8a5 in std::sys_common::backtrace::__rust_begin_short_backtrace::h338dfc6ea17569fd () from /usr/lib64/python3.6/site-packages/mercurial/rustext.cpython-36m-x86_64-linux-gnu.so #16 0x7f897865dfc3 in core::ops::function::FnOnce::call_once$u7b$$u7b$vtable.shim$u7d$$u7d$::ha610835416cffb73 () from /usr/lib64/python3.6/site-packages/mercurial/rustext.cpython-36m-x86_64-linux-gnu.so #17 0x7f897868d24a in std::sys::unix::thread::Thread::new::thread_start::h69f54c4a59452ed6 () from /usr/lib64/python3.6/site-packages/mercurial/rustext.cpython-36m-x86_64-linux-gnu.so #18 0x7f897f613ea5 in start_thread () from /lib64/libpthread.so.0 #19 0x7f897ec339fd in clone () from /lib64/libc.so.6 === Backtrace: = /lib64/libc.so.6(+0x7f474)[0x7f897ebb4474] /lib64/libc.so.6(+0x84770)[0x7f897ebb9770] /lib64/libc.so.6(realloc+0x1d2)[0x7f897ebbae12] /repo/tools/lin86/make/V3.82_a1.6_7/bin/../lib64/libaccess.so(+0x3e51)[0x7f897fd53e51] /repo/tools/lin86/make/V3.82_a1.6_7/bin/../lib64/libaccess.so(opendir+0x6f)[0x7f897fd5195f] /usr/lib64/python3.6/site-packages/mercurial/rustext.cpython-36m-x86_64-linux-gnu.so(+0x1f9053)[0x7f897868c053] /usr/lib64/python3.6/site-packages/mercurial/rustext.cpython-36m-x86_64-linux-gnu.so(+0xc73eb)[0x7f897855a3eb] /usr/lib64/python3.6/site-packages/mercurial/rustext.cpython-36m-x86_64-linux-gnu.so(+0xc7e49)[0x7f897855ae49] /usr/lib64/python3.6/site-packages/mercurial/rustext.cpython-36m-x86_64-linux-gnu.so(+0x652da)[0x7f89784f82da] /usr/lib64/python3.6/site-packages/mercurial/rustext.cpython-36m-x86_64-linux-gnu.so(+0x8f27f)[0x7f897852227f]
[Bug 6486] New: hg diff --git should make a difference between "file did not exists" and "file was empty"
https://bz.mercurial-scm.org/show_bug.cgi?id=6486 Bug ID: 6486 Summary: hg diff --git should make a difference between "file did not exists" and "file was empty" Product: Mercurial Version: default branch Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: sushilkhanch...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- Repo setup: hg init repo cd repo touch a hg ci -Am "empty a" Now run: hg diff -c 0 --git --config experimental.extendedheader.index=full Output: ``` diff --git a/a b/a new file mode 100644 index e69de29bb2d1d6434b8b29ae775ad8c2e48c5391..e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 100644 ``` Whereas, in a git repository output would be: ``` diff --git a/a b/a new file mode 100644 index ..e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 ``` where: '0' * 40 is used for: NULL_BLOB_ID (file does not exists) and 'e69de29bb2d1' is used for EMPTY_BLOB_ID (file is empty) -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6485] New: _enforceinlinesize would cause corruption if transaction is rolled back
https://bz.mercurial-scm.org/show_bug.cgi?id=6485 Bug ID: 6485 Summary: _enforceinlinesize would cause corruption if transaction is rolled back Product: Mercurial Version: default branch Hardware: All OS: All Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: rgo...@octobus.net CC: mercurial-devel@mercurial-scm.org Python Version: --- I haven't looked for a way of triggering the bug, but I thought it would be right to report it now that I've stumbled upon it. Basically, if a revlog switches from being inline to being two separate index and data files and the transaction rolls back and truncates the index file, which has just been rewritten to be a pure index. I intend on fixing this bug in a future patch of my sidedata exchange series, but since I don't know exactly when I will have time, I'd be happy to let someone else fix it. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6488] New: Exception happened during processing request
https://bz.mercurial-scm.org/show_bug.cgi?id=6488 Bug ID: 6488 Summary: Exception happened during processing request Product: Mercurial Version: 5.5.1 Hardware: PC OS: Other Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: i...@brigar.ru CC: mercurial-devel@mercurial-scm.org Python Version: --- OS:> FreeBSD 12.2-RELEASE-p3 GENERIC amd64 HG:> mercurial-5.5_1 PY:> python3.7 INFO: action (hg push) repository size 12G, end result error ERROR:> Exception happened during processing request '/go-pack?cmd=unbundle': Traceback (most recent call last): File "/usr/local/lib/python3.7/site-packages/mercurial/hgweb/server.py", line 123, in do_POST self.do_write() File "/usr/local/lib/python3.7/site-packages/mercurial/hgweb/server.py", line 116, in do_write self.do_hgweb() File "/usr/local/lib/python3.7/site-packages/mercurial/hgweb/server.py", line 236, in do_hgweb for chunk in self.server.application(env, self._start_response): File "/usr/local/lib/python3.7/site-packages/mercurial/hgweb/hgwebdir_mod.py", line 381, in run_wsgi for r in self._runwsgi(req, res): File "/usr/local/lib/python3.7/site-packages/mercurial/hgweb/hgweb_mod.py", line 326, in run_wsgi for r in self._runwsgi(req, res, repo): File "/usr/local/lib/python3.7/site-packages/mercurial/hgweb/hgweb_mod.py", line 353, in _runwsgi rctx, req, res, self.check_perm File "/usr/local/lib/python3.7/site-packages/mercurial/wireprotoserver.py", line 233, in handlewsgirequest _callhttp(repo, req, res, proto, cmd) File "/usr/local/lib/python3.7/site-packages/mercurial/wireprotoserver.py", line 469, in _callhttp rsp = wireprotov1server.dispatch(repo, proto, cmd) File "/usr/local/lib/python3.7/site-packages/mercurial/wireprotov1server.py", line 82, in dispatch return func(repo, proto, *args) File "/usr/local/lib/python3.7/site-packages/mercurial/wireprotov1server.py", line 664, in unbundle repo, gen, their_heads, b'serve', proto.client() File "/usr/local/lib/python3.7/site-packages/mercurial/exchange.py", line 2805, in unbundle gettransaction() File "/usr/local/lib/python3.7/site-packages/mercurial/exchange.py", line 2794, in gettransaction lockandtr[2] = repo.transaction(source) File "/usr/local/lib/python3.7/site-packages/mercurial/localrepo.py", line 2075, in transaction hint=_(b"run 'hg recover' to clean up transaction"), mercurial.error.RepoError: b'abandoned transaction found' -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6482] New: Push to multiple targets
https://bz.mercurial-scm.org/show_bug.cgi?id=6482 Bug ID: 6482 Summary: Push to multiple targets Product: Mercurial Version: unspecified Hardware: PC OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: z...@zash.se CC: mercurial-devel@mercurial-scm.org Python Version: --- Scenario: I have multiple mirrors of my code. I want to push to all of them. Currently: I could set up cronjobs to pull from, or just repeat `hg push ; hg push mirror` etc. Feature request: Allow multiple destinations: $ hg push default mirror backupmirror This is currently an error, "invalid arguments", so shouldn't be BC. Push could be done in serial (like running `hg push` in a loop in the shell) or in parallel to speed it up (can't do that in shell because locks). -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6487] New: Crash on Tortoise workbench patches window, right click patch, select go to...
https://bz.mercurial-scm.org/show_bug.cgi?id=6487 Bug ID: 6487 Summary: Crash on Tortoise workbench patches window, right click patch, select go to... Product: Mercurial Version: 5.7 Hardware: PC OS: Windows Status: UNCONFIRMED Severity: bug Priority: wish Component: mq Assignee: bugzi...@mercurial-scm.org Reporter: rudolph.gutzerha...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- Created attachment 2100 --> https://bz.mercurial-scm.org/attachment.cgi?id=2100=edit workbench when error occured Selecting a patch in the middle of qapplied patches in the patches window on the Tortoise workbench, and right-click select "go to patch" crashes in 5.7 . This worked perfectly in 5.6 . McAfee Anti-virus Windows specifications Edition Windows 10 Pro Version 20H2 Installed on2020-11-22 OS build19042.804 Experience Windows Feature Experience Pack 120.2212.551.0 --- Workbench error window: Traceback (most recent call last): file "hg", line 58, in file "mercurial\dispatch.pyo", line 143, in run file "mercurial\dispatch.pyo"f line 245, in dispatch file "mercurial\dispatch.pyo", line 289, in _rundispatch file "mercurial\dispatch.pyo", line 465, in _runcatch file "mercurial\dispatch.pyo", line 475, in _callcatch file "mercurial\scmutil.pyo", line 155, in callcatch file "mercurial \dispatch.pyo", line 455, in _runcatchfunc file "mercurial\dispatch.pyo", line 1259, in _dispatch file "mercurial\dispatch.pyo", line 913, in runcommand file "mercurial\dispatch.pyo", line 1270, in _runcommand file "mercurial\dispatch.pyo", line 1256, in file "mercurial\util.pyo", line 1867, in check file "mercurial\util.pyo", line 1867, in check file "hgext\mq.pyo", line 4237, in mqcommand file "mercurial\util.pyo", line 1867, in check file "mercurial\commands.pyo", line 6421, in serve file "mercurial \server.pyo", line 164, in runservice file "mercurial\commandserver.pyo", line 469, in run file "mercurial\commandserver.pyo”f line 403, in serve file "mercurial\commandserver.pyo", line 377, in serveone file "mercurial\commandserver.pyo", line 358, in runcommand file "mercurial\commandserver.pyo", line 297, in _dispatchcommand file "mercurial\dispatch.pyo", line 245, in dispatch file "mercurial\dispatch.pyo", line 289, in _rundispatch file "mercurial\dispatch.pyo", line 465, in _runcatch file "mercurial \dispatch.pyo", line 475, in _callcatch file "mercurial\scmutil.pyo", line 155, in callcatch file "mercurial\dispatch.pyo", line 455, in _runcatchfunc file "tortoisehg\util\hgdispatch.pyo", line 23, in _dispatch file "mercurial\dispatch.pyo", line 1259, in .dispatch file "mercurial\dispatch.pyo", line 913, in runcommand file "mercurial\dispatch.pyo", line 1270, in .runcommand file "mercurial \dispatch.pyo", line 1256, in file "mercurial\util.pyo", line 1867, in check file "hgext\mq.pyo", line 3582, in pop file "hgext \mq.pyo", line 1863, in pop file "mercurial\strip.pyo", line 80, in strip file "mercurial\repair.pyo", line 130, in strip file "mercurial \localrepo.pyo", line 200, in wrapper file "mercurialMocalrepo.pyo", line 3106, in destroying file "mercurial\bundlerepo.pyo", line 224, in write NotlmplementedError cmdserver: process exited unexpectedly with code 255 ** unknown exception encountered, please report by visiting ** https://mercurial-scm.org/wiki/BugTracker ** Python 2.7.18 (v2.7.18:8d21aa21f2, Apr 20 2020,13:25:05) [MSC v.1500 64 bit (AMD64)] ** Mercurial Distributed SCM (version 5.7) ** Extensions loaded: mq, patchbomb, rebase, strip, tortoisehg.util.hgcommands, tortoisehg.util.hgdispatch, tortoisehg.util.partialcommit, ti ** unknown exception encountered, please report by visiting ** https://mercurial-scm.org/wiki/BugTracker ** Python 2.7.18 (v2.7.18:8d21aa21f2, Apr 20 2020,13:25:05) [MSC v.1500 64 bit (AMD64)] ** Mercurial Distributed SCM (version 5.7) ** Extensions loaded: mq, patchbomb, rebase, strip, tortoisehg.util.hgcommands, tortoisehg.util.hgdispatch, tortoisehg.util.partialcommit, ti [Code: -1] -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6490] New: hgweb error on /archive/ without node
https://bz.mercurial-scm.org/show_bug.cgi?id=6490 Bug ID: 6490 Summary: hgweb error on /archive/ without node Product: Mercurial Version: default branch Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: normal Component: hgweb Assignee: bugzi...@mercurial-scm.org Reporter: z...@zash.se CC: mercurial-devel@mercurial-scm.org Python Version: 3.7 Found this in logs while looking for errors: [2021-02-21 05:26:03 +] [19488] [ERROR] Error handling request /prosody-modules/archive/ Traceback (most recent call last): File "/usr/lib/python3/dist-packages/gunicorn/workers/sync.py", line 135, in handle self.handle_request(listener, req, client, addr) File "/usr/lib/python3/dist-packages/gunicorn/workers/sync.py", line 181, in handle_request for item in respiter: File "/usr/lib/python3/dist-packages/mercurial/hgweb/hgwebdir_mod.py", line 381, in run_wsgi for r in self._runwsgi(req, res): File "/usr/lib/python3/dist-packages/mercurial/hgweb/hgweb_mod.py", line 326, in run_wsgi for r in self._runwsgi(req, res, repo): File "/usr/lib/python3/dist-packages/mercurial/hgweb/hgweb_mod.py", line 398, in _runwsgi fn = req.qsparams[b'node'] File "/usr/lib/python3/dist-packages/mercurial/hgweb/request.py", line 35, in __getitem__ return self._items[key][-1] KeyError: b'node' Appears to happen if hgweb is hit with /archive/ (no node/rev given). Reproduced on current tip = c82d6363bc9e by ./hg serve curl http://localhost:8080/archive/ (in parallell) -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6577] New: Get Affordable SEO services in Noida to boost your business online
https://bz.mercurial-scm.org/show_bug.cgi?id=6577 Bug ID: 6577 Summary: Get Affordable SEO services in Noida to boost your business online Product: Mercurial Version: 5.9rc1 Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: acl Assignee: bugzi...@mercurial-scm.org Reporter: joesmithjs1...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- Are you searching for best SEO services in Noida for ranking your website? PNJ Sharptech helps you to manage your SEO campaign more efficiently and effectively. We offer you the best SEO services, and with the help of our expertise, we make your website rank quickly and grow your business. Visit- https://www.pnjsharptech.com/seo-services-noida -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6575] New: How can I change my AOL Password?
https://bz.mercurial-scm.org/show_bug.cgi?id=6575 Bug ID: 6575 Summary: How can I change my AOL Password? Product: Mercurial Version: earlier Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: automv Assignee: bugzi...@mercurial-scm.org Reporter: woakeschri...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- AOL provides a highly secured mailing environment to keep the user’s account secure from hackers or spammers. Changing the password of your AOL account gives you an extra protection and a sense of satisfaction. Follow the simple step given below to Change AOL Password successfully. 1. Go to the Account security page. 2. Click on the ‘Change password’ option. 3. Enter your new password and click on the ‘Continue’ button to secure your account. In case you find any issue while changing the password, feel free to write to us and we will get back to you. Visit Us: https://www.limksys.com/aol-password-reset-not-working/ -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6569] New: Take Aid From The Ingenious Geeks To Unlock Cash App Account
https://bz.mercurial-scm.org/show_bug.cgi?id=6569 Bug ID: 6569 Summary: Take Aid From The Ingenious Geeks To Unlock Cash App Account Product: Mercurial Version: earlier Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: bookmarks Assignee: bugzi...@mercurial-scm.org Reporter: js8435...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- It would be wise to take a look at the help and support from the Cash App troubleshooting professionals. Here, you will be able to find out the best remedies and feasible solutions to Unlock Cash App Account within the least time span. However, you can also approach these specialists who will assist you out regarding the same. https://www.squarecashhelps.com/blog/how-to-unlock-cash-app-account/ -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6570] New: Call the tech support team to check the balance on cash app card
https://bz.mercurial-scm.org/show_bug.cgi?id=6570 Bug ID: 6570 Summary: Call the tech support team to check the balance on cash app card Product: Mercurial project Version: unspecified Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: website Assignee: bugzi...@mercurial-scm.org Reporter: js8435...@gmail.com CC: mercurial-devel@mercurial-scm.org If you don’t know how to send money or check balance on a cash app card then you’ve come to the right place. By seeking the help of cash app consultants, it’s easy to know the balance and fix many other technical glitches. Speak to the consultants to overcome cash app glitches. https://www.contact-customer-service.net/blog/check-balance-on-cash-app-card/ -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6567] New: Is It 100% Guaranteed To Get A Cash App Refund Without Any Hassle?
https://bz.mercurial-scm.org/show_bug.cgi?id=6567 Bug ID: 6567 Summary: Is It 100% Guaranteed To Get A Cash App Refund Without Any Hassle? Product: Mercurial project Version: unspecified Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: website Assignee: bugzi...@mercurial-scm.org Reporter: js8435...@gmail.com CC: mercurial-devel@mercurial-scm.org Yes, if you have initiated a wrong payment and your money has been deducted from your account, you will need to apply for a Cash App Refund without wasting your time .As a result, it will enable you to receive your money back to your account flawlessly in a few working days. https://www.contact-customerservice.co/blog/does-cash-app-refund-stolen-money/ -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6568] New: How Is It Possible To Get Money Off Cash App Without Card?
https://bz.mercurial-scm.org/show_bug.cgi?id=6568 Bug ID: 6568 Summary: How Is It Possible To Get Money Off Cash App Without Card? Product: Mercurial project Version: unspecified Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: website Assignee: bugzi...@mercurial-scm.org Reporter: js8435...@gmail.com CC: mercurial-devel@mercurial-scm.org Of course, it is possible to Get Money off Cash App without Card or without your existing bank account. However, you might face some technical errors while doing the same and may also face some difficulties due to the less information. Also, you can take help and support from the troubleshooting professionals who will assist you out. https://www.contactcustomer-service.co/blog/can-i-use-cash-app-without-a-bank-account/ -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6580] New: test-upgrade-repo.t and other failures on s390x (64-bit big endian)
https://bz.mercurial-scm.org/show_bug.cgi?id=6580 Bug ID: 6580 Summary: test-upgrade-repo.t and other failures on s390x (64-bit big endian) Product: Mercurial Version: 5.9 Hardware: Other OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: jcris...@debian.org CC: mercurial-devel@mercurial-scm.org Python Version: --- From the debian build of mercurial 5.9 on s390x: https://buildd.debian.org/status/fetch.php?pkg=mercurial=s390x=5.9-1=1629766216=0 a number of tests are failing. Some of them similar to bug 6188, others I'm not sure, but possibly endianness issues. Failed test-censor.t#revlogv2: output changed Failed test-clone-uncompressed.t#stream-bundle2: output changed Failed test-clone-uncompressed.t#stream-legacy: output changed Failed test-copies-in-changeset.t#sidedata: output changed Failed test-generaldelta.t: output changed Failed test-persistent-nodemap.t: output changed Failed test-sidedata-exchange.t: output changed Failed test-sidedata.t: output changed Failed test-transaction-safety.t#revlogv2: output changed Failed test-upgrade-repo.t: output changed --- /<>/tests/test-upgrade-repo.t +++ /<>/tests/test-upgrade-repo.t.err @@ -1531,9 +1531,8 @@ sparserevlog store $ hg debugsidedata -c 0 - 2 sidedata entries - entry-0001 size 4 - entry-0002 size 32 + abort: cannot read from revlog 00changelog-5e69c5d1.sda; expected 1942585158 bytes from offset 0, data size is 90 + [50] downgrade @@ -1552,6 +1551,8 @@ - changelog - manifest + abort: cannot read from revlog data/foo-1335303a.sda; expected 1942585158 bytes from offset 0, data size is 0 + [50] $ hg debugformat -v format-variant repo config default fncache:yesyes yes @@ -1563,7 +1564,7 @@ persistent-nodemap: no no no (no-rust !) persistent-nodemap: yesyes no (rust !) copies-sdc: no no no - revlog-v2: no no no + revlog-v2: yes no no changelog-v2:no no no plain-cl-delta: yesyes yes compression:zlib zlibzlib (no-zstd !) @@ -1571,14 +1572,16 @@ compression-level: default default default $ cat .hg/requires dotencode - fncache + exp-revlogv2.2 + fncache + persistent-nodemap (rust !) generaldelta - persistent-nodemap (rust !) - revlog-compression-zstd (zstd !) - revlogv1 + revlog-compression-zstd sparserevlog store $ hg debugsidedata -c 0 + abort: cannot read from revlog 00changelog-5e69c5d1.sda; expected 1942585158 bytes from offset 0, data size is 90 + [50] upgrade from hgrc @@ -1587,20 +1590,8 @@ > revlogv2=enable-unstable-format-and-corrupt-my-data > EOF $ hg debugupgraderepo --run --no-backup --quiet - upgrade will perform the following actions: - - requirements preserved: dotencode, fncache, generaldelta, sparserevlog, store (no-zstd !) - preserved: dotencode, fncache, generaldelta, revlog-compression-zstd, sparserevlog, store (zstd no-rust !) preserved: dotencode, fncache, generaldelta, persistent-nodemap, revlog-compression-zstd, sparserevlog, store (rust !) - removed: revlogv1 - added: exp-revlogv2.2 - - processed revlogs: -- all-filelogs -- changelog -- manifest - $ hg debugformat -v format-variant repo config default fncache:yesyes yes @@ -1628,6 +1619,8 @@ sparserevlog store $ hg debugsidedata -c 0 + abort: cannot read from revlog 00changelog-5e69c5d1.sda; expected 1942585158 bytes from offset 0, data size is 90 + [50] Demonstrate that nothing to perform upgrade will still run all the way through ERROR: test-upgrade-repo.t output changed !# Ret was: 0 (test-upgrade-repo.t) -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6579] New: SEO for artists
https://bz.mercurial-scm.org/show_bug.cgi?id=6579 Bug ID: 6579 Summary: SEO for artists Product: Mercurial Version: earlier Hardware: PC OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: blackbox Assignee: bugzi...@mercurial-scm.org Reporter: alinabe...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- Hi, I am Alina. If you are looking seo for artists so, you are in the right place. Here we providing SEO Services at an cheap price as per our consumer budget. Also, we have a well knowledgeable team who gives you the best results. Whether it’s in website traffic, ranking, organic keywords, etc. https://www.firstrankseoservices.com/seo-for-artists -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6581] New: cloning new repository fails
https://bz.mercurial-scm.org/show_bug.cgi?id=6581 Bug ID: 6581 Summary: cloning new repository fails Product: Mercurial Version: 5.9 Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: mathias.dem...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- hg init testrepo-5.9-test3 cd testrepo-5.9-test3 mkdir -p container/isam-build-centos7 touch container/isam-build-centos7/bazel-coverage-generator-sandboxfs-compatibility-0758e3e4f6057904d44399bd666faba9e7f40686.patch hg add hg commit -m foo cd .. hg clone testrepo-5.9-test3 testrepo-5.9-test3-result abort: No such file or directory: '/repo/mdemare/tmp/testrepo-5.9-test3-result/.hg/store/dh/containe/isam-bui/bazel-coverage-generator-sandboxfs-compatibility-0758e3e4d94041277bcd011e1d54c247523c124b4a325686.i' -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6583] New: Essay Writing Services
https://bz.mercurial-scm.org/show_bug.cgi?id=6583 Bug ID: 6583 Summary: Essay Writing Services Product: Mercurial Version: unspecified Hardware: PC OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: automv Assignee: bugzi...@mercurial-scm.org Reporter: johnwill0...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- Hello! My name is John. I have 7 years of experience and i am providing essay writing services to students. I have written essays for many clients and delivered them successfully within the time limit. I am highly skilled in academic writing and provide you well written essays. You can contact me. https://www.speedyassignmenthelp.com/essay-writing-services -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6571] New: Can you dispute a Cash App transaction?
https://bz.mercurial-scm.org/show_bug.cgi?id=6571 Bug ID: 6571 Summary: Can you dispute a Cash App transaction? Product: Mercurial Version: earlier Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: bookmarks Assignee: bugzi...@mercurial-scm.org Reporter: howardpotts...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- As a cash app user you well know that many times contacted the cash app’s merchant and in case, you are unable to get issue resolve the transaction then Can you dispute a Cash App transaction. To do so, from the cash card transaction then you can do it by yourself. If you are facing any issues then you can contact us and get in touch with us. https://www.contact-customerservice.co/blog/how-to-get-cash-app-support/ -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6572] New: Have A Fruitful Discussion With Specialists Via Cash App Customer Service
https://bz.mercurial-scm.org/show_bug.cgi?id=6572 Bug ID: 6572 Summary: Have A Fruitful Discussion With Specialists Via Cash App Customer Service Product: Mercurial Version: default branch Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: blackbox Assignee: bugzi...@mercurial-scm.org Reporter: howardpotts...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- While working on your Cash App account, you might encounter some glitches and hitches due to several complex reasons. In such a case, it would be wise to have a fruitful discussion with a team of Cash App troubleshooting professionals. To do the same, you have to make use of Cash App Customer Service at anytime. https://www.pcmonks.net/cash-app-customer-service-phone-number.html -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6573] New: Is Chime Bank A Real Bank? How Do I Come To Know About The Same?
https://bz.mercurial-scm.org/show_bug.cgi?id=6573 Bug ID: 6573 Summary: Is Chime Bank A Real Bank? How Do I Come To Know About The Same? Product: Mercurial Version: 5.9rc1 Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: bundle2 Assignee: bugzi...@mercurial-scm.org Reporter: howardpotts...@gmail.com CC: mercurial-devel@mercurial-scm.org, pierre-yves.da...@ens-lyon.org Python Version: --- Are you looking for a trustworthy source to understand the right answer to your query i.e. Is Chime Bank A Real Bank? However, it acts as banking service provider but is not a bank so if you are one of those who are clarifying your confusion, you should get in touch with the Chime specialists. https://www.chime-customerservice.net/is-chime-bank-a-real-bank/ -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6574] New: Goof in the interface the reason behind activate Cash App card disillusionment? Find opportunity to help.
https://bz.mercurial-scm.org/show_bug.cgi?id=6574 Bug ID: 6574 Summary: Goof in the interface the reason behind activate Cash App card disillusionment? Find opportunity to help. Product: Mercurial Version: 5.9rc1 Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: blackbox Assignee: bugzi...@mercurial-scm.org Reporter: howardpotts...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- Once in a while, the bumble may transmit in the interface and can activate Cash App card botch. Consequently, the best way to deal with the issue is to complete the plans that are recorded in the tech help gatherings or you can get adequate assistance by looking at some tech help vids on Youtube. https://www.quick-utilities.net/blog/how-to-activate-cash-app-card -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6576] New: Why do the Outlook rules not work in my account?
https://bz.mercurial-scm.org/show_bug.cgi?id=6576 Bug ID: 6576 Summary: Why do the Outlook rules not work in my account? Product: Mercurial Version: earlier Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: acl Assignee: bugzi...@mercurial-scm.org Reporter: woakeschri...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- Outlook rules are set to run on any system automatically to make the system efficient and easy to use. However, when certain changes are made or when some of the files running in the background are corrupt, Outlook Rules not Working issue arises. One of the best possible ways to fix the issue is Resetting the SRS File. Check the instructions below to understand how it is done. • Visit the location on your system: C:\Users\%username%\AppData\Roaming\Microsoft\Outlook • Rename the existing Outlook.srs file to Outlook.old.srs • Restart Outlook. This will create a new and proper SRS file. Hope this helps you in fixing the issue. If not, feel free to write to us and we are up for the discussion. There are numerous possible solutions to this issue. So, get connected with the experts to find which one works for you. Visit Us: https://www.limksys.com/outlook-rules-are-not-working/ -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6578] New: Developing an Employee Recruitment Plan
https://bz.mercurial-scm.org/show_bug.cgi?id=6578 Bug ID: 6578 Summary: Developing an Employee Recruitment Plan Product: Mercurial project Version: unspecified Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: website Assignee: bugzi...@mercurial-scm.org Reporter: myrecruitmen...@gmail.com CC: mercurial-devel@mercurial-scm.org Why is a recruitment plan important? Before you struggle with your recruiting efforts and scratch your head wondering why you aren't able to find the candidates that you're looking for, sit down and come up with a recruiting plan. With the right recruiting strategies and steps in place, you can exponentially increase the quality of your results. You can use our recruitment plan sample above to help you get started. https://recruitmentweb.org.ng/airforce-secondary-school-entrance-exams-result/ -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6590] New: IndexError: list index out of range in picksplitsuccessor in evolve/utility.py
https://bz.mercurial-scm.org/show_bug.cgi?id=6590 Bug ID: 6590 Summary: IndexError: list index out of range in picksplitsuccessor in evolve/utility.py Product: Mercurial Version: stable branch Hardware: PC OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: evolution Assignee: bugzi...@mercurial-scm.org Reporter: sph...@gmail.com CC: mercurial-devel@mercurial-scm.org, pierre-yves.da...@ens-lyon.org Python Version: --- Created attachment 2122 --> https://bz.mercurial-scm.org/attachment.cgi?id=2122=edit Fix for list index out of range error I am on stable, at bcdccdd48d99. I ran `hg evolve` and got the above error message. What seems to be happening is that `_utility.singlesuccessor` throws because it finds multiple successors, but then when picksplitsuccessor tries to handle that, it doesn't find any successors at all. The problem appears to be that singlesuccessor does this loop up through parents until it finds something, but picksplitsuccessor does not. I will attach my attempt to work around the problem, which works for me but uses `:=` and I don't actually understand any of the data model I'm patching. It might be better to pass down the successors that are stored on the `MultipleSuccessorsError` exception, rather than looking them up again? (This fixed my problem locally.) -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6591] New: test-clone-uncompressed.t: test failure
https://bz.mercurial-scm.org/show_bug.cgi?id=6591 Bug ID: 6591 Summary: test-clone-uncompressed.t: test failure Product: Mercurial Version: 5.9.1 Hardware: All OS: NetBSD Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: t...@giga.or.at CC: mercurial-devel@mercurial-scm.org Python Version: --- I see a new test failure in 5.9.1 (not in 5.9): Seems the first problem is using long options for 'mkdir' (--parents instead of -p). --- /scratch/devel/py-mercurial/work/mercurial-5.9.1/tests/test-clone-uncompressed.t +++ /scratch/devel/py-mercurial/work/mercurial-5.9.1/tests/test-clone-uncompressed.t#stream-bundle2.err @@ -97,7 +97,12 @@ name causing issue6581 $ mkdir --parents container/isam-build-centos7/ + mkdir: unknown option -- - + usage: mkdir [-p] [-m mode] dirname ... + [1] $ touch container/isam-build-centos7/bazel-coverage-generator-sandboxfs-compatibility-0758e3e4f6057904d44399bd666faba9e7f40686.patch + touch: container/isam-build-centos7/bazel-coverage-generator-sandboxfs-compatibility-0758e3e4f6057904d44399bd666faba9e7f40686.patch: $ENOENT$ + [1] Add all that @@ -108,7 +113,6 @@ adding 00changelog.n adding 00manifest.d adding 00manifest.i - adding container/isam-build-centos7/bazel-coverage-generator-sandboxfs-compatibility-0758e3e4f6057904d44399bd666faba9e7f40686.patch adding data/foo.d adding data/foo.i adding data/foo.n @@ -178,7 +182,7 @@ $ hg clone server local-clone updating to branch default - 1088 files updated, 0 files merged, 0 files removed, 0 files unresolved + 1087 files updated, 0 files merged, 0 files removed, 0 files unresolved Check that the clone went well @@ -187,7 +191,7 @@ checking manifests crosschecking files in changesets and manifests checking files - checked 3 changesets with 1088 changes to 1088 files + checked 3 changesets with 1087 changes to 1087 files Check uncompressed == @@ -314,8 +318,8 @@ adding changesets adding manifests adding file changes - added 3 changesets with 1088 changes to 1088 files - new changesets 96ee1d7354c4:5223b5e3265f + added 3 changesets with 1087 changes to 1087 files + new changesets 96ee1d7354c4:42e820400e84 $ get-with-headers.py $LOCALIP:$HGPORT '?cmd=getbundle' content-type --bodyfile body --hgproto 0.2 --requestheader "x-hgarg-1=bundlecaps=HG20%2Cbundle2%3DHG20%250Abookmarks%250Achangegroup%253D01%252C02%250Adigests%253Dmd5%252Csha1%252Csha512%250Aerror%253Dabort%252Cunsupportedcontent%252Cpushraced%252Cpushkey%250Ahgtagsfnodes%250Alistkeys%250Aphases%253Dheads%250Apushkey%250Aremote-changegroup%253Dhttp%252Chttps=0==c17445101a72edac06facd130d14808dfbd5c7c2=1" 200 Script output follows @@ -358,8 +362,8 @@ streaming all changes 1093 files to transfer, 102 KB of data (no-zstd !) transferred 102 KB in * seconds (* */sec) (glob) (no-zstd !) - 1093 files to transfer, 98.9 KB of data (zstd !) - transferred 98.9 KB in * seconds (* */sec) (glob) (zstd !) + 1092 files to transfer, 98.6 KB of data + transferred 98.6 KB in * seconds (* */sec) (glob) $ ls -1 clone1/.hg/cache branch2-base @@ -404,12 +408,12 @@ #endif #if zstd no-rust $ f --size --hex --bytes 256 body - body: size=116340 + body: size=115921 : 04 6e 6f 6e 65 48 47 32 30 00 00 00 00 00 00 00 |.noneHG20...| 0010: 9a 07 53 54 52 45 41 4d 32 00 00 00 00 03 00 09 |..STREAM2...| 0020: 06 09 04 0c 5e 62 79 74 65 63 6f 75 6e 74 31 30 |^bytecount10| - 0030: 31 32 37 36 66 69 6c 65 63 6f 75 6e 74 31 30 39 |1276filecount109| - 0040: 33 72 65 71 75 69 72 65 6d 65 6e 74 73 64 6f 74 |3requirementsdot| + 0030: 30 39 39 32 66 69 6c 65 63 6f 75 6e 74 31 30 39 |0992filecount109| + 0040: 32 72 65 71 75 69 72 65 6d 65 6e 74 73 64 6f 74 |2requirementsdot| 0050: 65 6e 63 6f 64 65 25 32 43 66 6e 63 61 63 68 65 |encode%2Cfncache| 0060: 25 32 43 67 65 6e 65 72 61 6c 64 65 6c 74 61 25 |%2Cgeneraldelta%| 0070: 32 43 72 65 76 6c 6f 67 2d 63 6f 6d 70 72 65 73 |2Crevlog-compres| @@ -480,8 +484,8 @@ streaming all changes 1093 files to transfer, 102 KB of data (no-zstd !) transferred 102 KB in * seconds (* */sec) (glob) (no-zstd !) - 1093 files to transfer, 98.9 KB of data (zstd !) - transferred 98.9 KB in * seconds (* */sec) (glob) (zstd !) + 1092 files to transfer, 98.6 KB of data + transferred 98.6 KB in * seconds (* */sec) (glob) #endif Clone with background file closing enabled @@ -526,14 +530,14 @@ bundle2-input-part: "stream2" (params: 3 mandatory) supported applying stream bundle 1093 files to transfer, 102 KB of data (no-zstd !) - 1093 files to transfer, 98.9 KB of data (zstd !) + 1092 files to transfer, 98.6 KB of data starting 4 threads for background file closing
[Bug 6592] New: compression.py requires bytes-like object not 'NoneType'
https://bz.mercurial-scm.org/show_bug.cgi?id=6592 Bug ID: 6592 Summary: compression.py requires bytes-like object not 'NoneType' Product: Mercurial Version: stable branch Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: jjhh.spam.t...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- hg won't run at all. Manjaro Linux (hg same as Arch I think) https://archlinux.org/packages/extra/x86_64/mercurial/ hg version 5.9.1 Updated a few days ago, and this is the first time I tried to use hg since that update. It's hard to believe this bug is in hg, as no-one else has reported it. Below is the traceback from simply running "hg --help". [jh@SSD2 210918 15:23:26 zp0]$ ll /usr/bin/hg -rwxr-xr-x 1 root root 1838 210901_224459.000 /usr/bin/hg* [jh@SSD2 210918 15:23:38 zp0]$ hg --help Traceback (most recent call last): File "/usr/bin/hg", line 61, in dispatch.run() File "/usr/lib/python3.9/importlib/util.py", line 245, in __getattribute__ self.__spec__.loader.exec_module(self) File "", line 850, in exec_module File "", line 228, in _call_with_frames_removed File "/usr/lib/python3.9/site-packages/mercurial/dispatch.py", line 761, in class lazyaliasentry(object): File "/usr/lib/python3.9/site-packages/mercurial/dispatch.py", line 772, in lazyaliasentry @util.propertycache File "/usr/lib/python3.9/importlib/util.py", line 245, in __getattribute__ self.__spec__.loader.exec_module(self) File "", line 850, in exec_module File "", line 228, in _call_with_frames_removed File "/usr/lib/python3.9/site-packages/mercurial/util.py", line 158, in compengines = compression.compengines File "/usr/lib/python3.9/importlib/util.py", line 245, in __getattribute__ self.__spec__.loader.exec_module(self) File "", line 850, in exec_module File "", line 228, in _call_with_frames_removed File "/usr/lib/python3.9/site-packages/mercurial/utils/compression.py", line 812, in i18nfunctions = bundlecompressiontopics().values() File "/usr/lib/python3.9/site-packages/mercurial/utils/compression.py", line 800, in bundlecompressiontopics doc = b'``%s``\n%s' % (bt[0], pycompat.getdoc(engine.bundletype)) TypeError: %b requires a bytes-like object, or an object that implements __bytes__, not 'NoneType' -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6588] New: how to recover file history.d index with obsolete files after grapht?
https://bz.mercurial-scm.org/show_bug.cgi?id=6588 Bug ID: 6588 Summary: how to recover file history.d index with obsolete files after grapht? Product: Mercurial Version: 5.9.1 Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: alexraynepe...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- hallow! use hg v5.8.1 - 5.9.1 after multiple big grapht operations, repo have file with strange index set: 1) on main history, file have set of changes after graphing. cloning repo will take that changes well. 2) when builds filelog (thg use mercurial.filelog) for that file, that log enumerates extinct and obsolete revisions, that was droped by graphting. and new revisions absent in that filelog index. repo verify doesn`t see this index crush. is there any possibility to recover my repo? -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6589] New: pip install with rust extensions is not possible anymore
https://bz.mercurial-scm.org/show_bug.cgi?id=6589 Bug ID: 6589 Summary: pip install with rust extensions is not possible anymore Product: Mercurial Version: 5.7.1 Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: rgo...@octobus.net CC: mercurial-devel@mercurial-scm.org Python Version: --- d13afdd1f6e2 introduced the `pyproject.toml` file. For some reason, that makes `pip install --global-option "--rust"` not build rust anymore. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6557] New: Malpensa Airport ICAO Code
https://bz.mercurial-scm.org/show_bug.cgi?id=6557 Bug ID: 6557 Summary: Malpensa Airport ICAO Code Product: Mercurial project Version: unspecified Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: website Assignee: bugzi...@mercurial-scm.org Reporter: airfleetrat...@gmail.com CC: mercurial-devel@mercurial-scm.org Airport codes are for giving a distinctive identity to an airport. When it comes to Malpensa Airport, you can find two different codes – IATA and ICAO codes. If you want to know about the Malpensa Airport ICAO Code And IATA Code then you can connect us. https://www.airfleetrating.com/airport-codes/malpensa-international-airport/ -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6560] New: test-manifest.t is flaky
https://bz.mercurial-scm.org/show_bug.cgi?id=6560 Bug ID: 6560 Summary: test-manifest.t is flaky Product: Mercurial Version: unspecified Hardware: PC OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: pierre-yves.da...@ens-lyon.org CC: mercurial-devel@mercurial-scm.org Python Version: --- As visible here: https://foss.heptapod.net/octobus/mercurial-devel/-/jobs/233123 I suspect we are using some timestamp for sorting and some loading happens in the same timestamp ? -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6565] New: warning while building a release
https://bz.mercurial-scm.org/show_bug.cgi?id=6565 Bug ID: 6565 Summary: warning while building a release Product: Mercurial Version: 5.9rc1 Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: 7895pul...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- I get this while building a release: ``` mercurial/cext/revlog.c: In function ‘index_pack_header’: mercurial/cext/revlog.c:369:16: warning: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 3 has type ‘int’ [-Wformat=] "version header should go in the docket, not the " ^~ mercurial/cext/revlog.c:370:26: note: format string is defined here "index: %lu", ~~^ %u ``` -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6563] New: Vashikaran specialist near me
https://bz.mercurial-scm.org/show_bug.cgi?id=6563 Bug ID: 6563 Summary: Vashikaran specialist near me Product: Mercurial Version: default branch Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: clonebundles Assignee: bugzi...@mercurial-scm.org Reporter: swamiastrologyswam...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- Best astrologer in India gives you best astrological remedies to control your boyfriend and girlfriend, astrology is very pure and a person can maintain healthy love life with the help of astrological methods given by our astrologer Jitesh Bhai. https://astrologyswami.com/ -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6564] New: Love Problem Solution Baba Ji
https://bz.mercurial-scm.org/show_bug.cgi?id=6564 Bug ID: 6564 Summary: Love Problem Solution Baba Ji Product: Mercurial Version: earlier Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: censor Assignee: bugzi...@mercurial-scm.org Reporter: arjunshastriastrologe...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- Love Problem Solution Baba Ji provide you complete solution for any love problem with the help of vashikaran & Black magic powers. https://onlineloveproblemsolutionastrologer.com/love-problem-solution-baba-ji.html -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6566] New: Purge without --confirm switch still asks for confirmation
https://bz.mercurial-scm.org/show_bug.cgi?id=6566 Bug ID: 6566 Summary: Purge without --confirm switch still asks for confirmation Product: Mercurial Version: 5.8.1 Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: purge Assignee: bugzi...@mercurial-scm.org Reporter: bugreporter5...@protonmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- hg help purge says "--confirm ask before permanently deleting files" so I assume using the purge command without the --confirm switch will permanently delete files without asking. Running the command with and without the switch both seem to do the same thing. Is this a bug? C:\Download\Repository>hg purge permanently delete 1 unkown files? (yN) n abort: removal cancelled C:\Download\Repository>hg purge --confirm permanently delete 1 unkown files? (yN) n abort: removal cancelled C:\Download\Repository>hg --version Mercurial Distributed SCM (version 5.8.1) (see https://mercurial-scm.org for more information) -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6558] New: more test-nointerrupt.t trouble
https://bz.mercurial-scm.org/show_bug.cgi?id=6558 Bug ID: 6558 Summary: more test-nointerrupt.t trouble Product: Mercurial Version: stable branch Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: pierre-yves.da...@ens-lyon.org CC: mercurial-devel@mercurial-scm.org Python Version: --- It looks like we still have failure from time to time. It is currently unclear if this is the test fault or if actual misbehavior are in play : https://foss.heptapod.net/octobus/mercurial-devel/-/jobs/230764 https://foss.heptapod.net/octobus/mercurial-devel/-/jobs/230763 -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6559] New: Followlines button shows +/- wrongly owing to unicode woes
https://bz.mercurial-scm.org/show_bug.cgi?id=6559 Bug ID: 6559 Summary: Followlines button shows +/- wrongly owing to unicode woes Product: Mercurial Version: unspecified Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: hgweb Assignee: bugzi...@mercurial-scm.org Reporter: spivox...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- I'm hosting hgweb under Apache on Debian, and accessing it using Chrome on Debian. When browsing a file, the "Followlines" feature displays a button next to the line number. The button should show a green + and a red - (minus sign), but on my setup the minus sign shows as garbled unicode. I've no idea what combination of operating systems, browser and Apache setup is causing the difficulty, but the fix below should be benign. The fix is simple: in /usr/share/mercurial/templates/static/followlines.js at line 59: minusSpan.textContent = '-'; (where the - is actually a unicode minus), replace this with minusSpan.textContent = '\u2212'; to make the unicode value explicit. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6561] New: test-remotefilelog-prefetch.t
https://bz.mercurial-scm.org/show_bug.cgi?id=6561 Bug ID: 6561 Summary: test-remotefilelog-prefetch.t Product: Mercurial Version: stable branch Hardware: PC OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: pierre-yves.da...@ens-lyon.org CC: mercurial-devel@mercurial-scm.org Python Version: --- The testc can be flaki as displayerd here: https://foss.heptapod.net/octobus/mercurial-devel/-/jobs/233286 -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6607] New: 4 tests are failing on PPC
https://bz.mercurial-scm.org/show_bug.cgi?id=6607 Bug ID: 6607 Summary: 4 tests are failing on PPC Product: Mercurial Version: unspecified Hardware: Other OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: cedric.kr...@b2ck.com CC: mercurial-devel@mercurial-scm.org Python Version: --- This bug has been reported: https://bugs.gentoo.org/815121 Failed test-clone-uncompressed.t#stream-bundle2: output changed Failed test-clone-uncompressed.t#stream-legacy: output changed Failed test-generaldelta.t: output changed Failed test-persistent-nodemap.t: output changed It seems that zstd is not working the same on PPC than on AMD64. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6606] New: "chg init foo" checks .hg/requires file, but "hg init foo" does not
https://bz.mercurial-scm.org/show_bug.cgi?id=6606 Bug ID: 6606 Summary: "chg init foo" checks .hg/requires file, but "hg init foo" does not Product: Mercurial Version: 5.9.1 Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: chg Assignee: bugzi...@mercurial-scm.org Reporter: mplam...@janestreet.com CC: mercurial-devel@mercurial-scm.org Python Version: --- I ran into a surprising difference in behavior between "hg" and "chg": When creating a new hg repo and a parent directory contains .hg/requires, "chg init foo" will parse the requires file and fail if there are any unknown requirements, while "hg init foo" will not. For example: $ mkdir outer $ cd outer $ mkdir .hg $ echo "garbage" > .hg/requires $ chg init inner # fails with unknown requirement: garbage $ hg init inner # succeeds I'm guessing this happens as part of starting the commandserver? The chg command sometimes succeeds if there's already a running commandserver, but reliably fails if there is no running commandserver. -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6604] New: _TextTestResult was removed in favour TextTestResult in Python 3.11
https://bz.mercurial-scm.org/show_bug.cgi?id=6604 Bug ID: 6604 Summary: _TextTestResult was removed in favour TextTestResult in Python 3.11 Product: Mercurial Version: default branch Hardware: PC OS: Linux Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: tir.kar...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- CPython commit : https://github.com/python/cpython/commit/b0a6ede3d0bd6fa4ffe413ab4dfc1059201df25b Following files might need to be updated tests/basic_test_result.py 6:class TestResult(unittest._TextTestResult): tests/run-tests.py 2239:class TestResult(unittest._TextTestResult): -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6605] New: Unable to clone PyPy using a clonebundle
https://bz.mercurial-scm.org/show_bug.cgi?id=6605 Bug ID: 6605 Summary: Unable to clone PyPy using a clonebundle Product: Mercurial Version: 5.9 Hardware: PC OS: All Status: UNCONFIRMED Severity: bug Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: rgo...@octobus.net CC: mercurial-devel@mercurial-scm.org Python Version: --- Try doing the following: $ hg clone https://foss.heptapod.net/pypy/pypy destination directory: pypy applying clone bundle from https://cellar-c2.services.clever-cloud.com/heptapod-foss-clonebundles/pypy/pypy-2020-02-12-13-12-optimized-zstd-v2.hg adding changesets adding manifests adding file changes transaction abort! rollback completed ** Unknown exception encountered with possibly-broken third-party extension "perf" (version N/A) ** which supports versions unknown of Mercurial. ** Please disable "perf" and try your action again. ** If that fixes the bug please report it to the extension author. ** Python 3.9.2 (default, Sep 10 2021, 12:13:36) [GCC 10.2.1 20210110] ** Mercurial Distributed SCM (version 5.9.1+hg2.7538453ec322) ** Extensions loaded: absorb, evolve 10.4.0, histedit, patchbomb, perf, phabricator, rebase, share, topic 0.23.0 Traceback (most recent call last): File "/home/alphare/hg/hg", line 61, in dispatch.run() File "/home/alphare/hg/mercurial/dispatch.py", line 144, in run status = dispatch(req) File "/home/alphare/hg/mercurial/dispatch.py", line 250, in dispatch status = _rundispatch(req) File "/home/alphare/hg/mercurial/dispatch.py", line 294, in _rundispatch ret = _runcatch(req) or 0 File "/home/alphare/hg/mercurial/dispatch.py", line 470, in _runcatch return _callcatch(ui, _runcatchfunc) File "/home/alphare/hg/mercurial/dispatch.py", line 480, in _callcatch return scmutil.callcatch(ui, func) File "/home/alphare/hg/mercurial/scmutil.py", line 153, in callcatch return func() File "/home/alphare/hg/mercurial/dispatch.py", line 460, in _runcatchfunc return _dispatch(req) File "/home/alphare/hg/mercurial/dispatch.py", line 1273, in _dispatch return runcommand( File "/home/alphare/hg/mercurial/dispatch.py", line 918, in runcommand ret = _runcommand(ui, options, cmd, d) File "/home/alphare/hg/mercurial/dispatch.py", line 1285, in _runcommand return cmdfunc() File "/home/alphare/hg/mercurial/dispatch.py", line 1271, in d = lambda: util.checksignature(func)(ui, *args, **strcmdopt) File "/home/alphare/hg/mercurial/util.py", line 1886, in check return func(*args, **kwargs) File "/home/alphare/hg/mercurial/util.py", line 1886, in check return func(*args, **kwargs) File "/home/alphare/hg/hgext/share.py", line 163, in clone return orig(ui, source, *args, **opts) File "/home/alphare/hg/mercurial/util.py", line 1886, in check return func(*args, **kwargs) File "/home/alphare/hg/mercurial/commands.py", line 1955, in clone r = hg.clone( File "/home/alphare/hg/mercurial/hg.py", line 942, in clone exchange.pull( File "/home/alphare/hg/mercurial/exchange.py", line 1668, in pull _maybeapplyclonebundle(pullop) File "/home/alphare/hg/mercurial/exchange.py", line 2779, in _maybeapplyclonebundle if trypullbundlefromurl(repo.ui, repo, url): File "/home/alphare/hg/mercurial/exchange.py", line 2810, in trypullbundlefromurl bundle2.applybundle(repo, cg, tr, b'clonebundles', url) File "/home/alphare/hg/mercurial/bundle2.py", line 375, in applybundle return processbundle(repo, unbundler, lambda: tr, source=source) File "/home/alphare/hg/mercurial/bundle2.py", line 486, in processbundle processparts(repo, op, unbundler) File "/home/alphare/hg/mercurial/bundle2.py", line 494, in processparts _processpart(op, part) File "/home/alphare/hg/mercurial/bundle2.py", line 568, in _processpart handler(op, part) File "/home/alphare/hg/mercurial/bundle2.py", line 2025, in handlechangegroup ret = _processchangegroup( File "/home/alphare/hg/mercurial/bundle2.py", line 498, in _processchangegroup ret = cg.apply(op.repo, tr, source, url, **kwargs) File "/home/alphare/hg/mercurial/extensions.py", line 512, in closure return func(*(args + a), **kw) File "/home/alphare/.local/lib/python3.9/site-packages/hgext3rd/topic/topicmap.py", line 96, in cgapply return orig(self, other, *args, **kwargs) File "/home/alphare/hg/mercurial/changegroup.py", line 444, in apply newrevs, newfiles = _addchangegroupfiles( File "/home/alphare/hg/mercurial/changegroup.py", line 1946, in _addchangegroupfiles added = fl.addgroup( File "/home/alphare/hg/mercurial/filelog.py", line 168, in addgroup return self._revlog.addgroup( File "/home/alphare/hg/mercurial/revlog.py", line 2620, in addgroup for data in deltas: File
[Bug 6603] New: Wrong modified file in hg status in share context
https://bz.mercurial-scm.org/show_bug.cgi?id=6603 Bug ID: 6603 Summary: Wrong modified file in hg status in share context Product: Mercurial Version: 5.7.1 Hardware: PC OS: Linux Status: UNCONFIRMED Severity: feature Priority: wish Component: Mercurial Assignee: bugzi...@mercurial-scm.org Reporter: georges.raci...@octobus.net CC: mercurial-devel@mercurial-scm.org Python Version: --- I have a case where a file is always displayed as modified in `hg status`, even after `hg revert` or `hg update -C` or even after a sequence of updates. The repository was cloned with the `share-pool` configuration item (the `share` extension is active). Recreating the share or recloning the actual repository in the pool resolves the problem. I tried both hg 5.7.1 on Python 3.8 and 5.9.2 on Python 3.9 (the latter with or without Rust). I have not been able in a limited time to find a small reproduction, so I made a tarball with the full repo and an offending share (6MB). Here's how to download the tarball and reproduce the bug (more details in the README file) $ cd /tmp /tmp $ curl -o status-bug.tgz https://static.octobus.net/bug-reproductions/gracinet-status-bug-2021-10-15.tgz /tmp $ tar xzf status-bug.tgz (if one untars in some other directory, the status-bug/share/.hg/sharedpath file will have to be adjusted accordingly). /tmp $ cd status-bug /tmp/status-bug $ ls README share share-pool /tmp/status-bug $ cd share /tmp/status-bug/share $ hg st M heptapod-ci.yml /tmp/status-bug/share $ hg rev heptapod-ci.yml /tmp/status-bug/share $ hg st M heptapod-ci.yml /tmp/status-bug/share $ hg update -C . 1 files updated, 0 files merged, 0 files removed, 0 files unresolved /tmp/status-bug/share $ hg st M heptapod-ci.yml /tmp/status-bug/share $ hg debugdirstate | grep heptapod-ci n 644 1787 unset heptapod-ci.yml (notice the 'unset' mtime) -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
[Bug 6594] New: Need to borrow money from cash app?
https://bz.mercurial-scm.org/show_bug.cgi?id=6594 Bug ID: 6594 Summary: Need to borrow money from cash app? Product: Mercurial Version: default branch Hardware: PC OS: Windows Status: UNCONFIRMED Severity: feature Priority: wish Component: automv Assignee: bugzi...@mercurial-scm.org Reporter: snow68...@gmail.com CC: mercurial-devel@mercurial-scm.org Python Version: --- Need to borrow money from cash app then you have come to the right place to know how to borrow money from the cash app. To borrow money from the cash app you just have to click on this link and then your work will be done in a few seconds. https://www.contact-customerservice.co/blog/how-to-borrow-money-from-cash-app/ -- You are receiving this mail because: You are on the CC list for the bug. ___ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
