upstream/mercurial-mirror Files · mercurial/help/internals/requirements.txt

tests: add tests for poorly behaving HTTP server...

tests: add tests for poorly behaving HTTP server I've spent several hours over the past few weeks investigating networking failures involving hg.mozilla.org. As part of this, it has become clear that the Mercurial client's error handling when it encounters network failures is far from robust. To prove this is true, I've devised a battery of tests simulating various network failures, notably premature connection closes. To achieve this, I've implemented an extension that monkeypatches the built-in HTTP server and hooks in at the socket level and allows various events to occur based on config options. For example, you can refuse to accept() a client socket or you can close() the socket after N bytes have been sent or received. The latter effectively simulates an unexpected connection drop (and these occur all the time in the real world). The new test file launches servers exhibiting various "bad" behaviors and points a client at them. As the many TODO comments in the test call attention to, Mercurial often displays unhelpful errors when network-related failures occur. This makes it difficult for users to understand what's going on and difficult for server administrators to pinpoint root causes without packet tracing. Upcoming patches will attempt to fix these error handling deficiencies.

Dan Villiom Podlaski Christiansen - - Load All Authors

File last commit:

r31133:23080c03 default


                r32001:c85f19c6

default

Download file

             requirements.txt
        
                    119 lines
            
             | 3.6 KiB
            
                | text/plain
            
             |
                TextLexer

/ mercurial / help / internals / requirements.txt

History | Source | Raw |Copy content |Copy permalink

Gregory Szorc help: document requirements...	r28523
		Repositories contain a file (``.hg/requires``) containing a list of
		features/capabilities that are required for clients to interface
		with the repository. This file has been present in Mercurial since
		version 0.9.2 (released December 2006).

		One of the first things clients do when opening a repository is read
		``.hg/requires`` and verify that all listed requirements are supported,
		aborting if not. Requirements are therefore a strong mechanism to
		prevent incompatible clients from reading from unknown repository
		formats or even corrupting them by writing to them.

		Extensions may add requirements. When they do this, clients not running
		an extension will be unable to read from repositories.

		The following sections describe the requirements defined by the
		Mercurial core distribution.

		revlogv1
Gregory Szorc help: don't try to render a section on sub-topics...	r29747	========
Gregory Szorc help: document requirements...	r28523
		When present, revlogs are version 1 (RevlogNG). RevlogNG was introduced
		in 2006. The ``revlogv1`` requirement has been enabled by default
		since the ``requires`` file was introduced in Mercurial 0.9.2.

		If this requirement is not present, version 0 revlogs are assumed.

		store
Gregory Szorc help: don't try to render a section on sub-topics...	r29747	=====
Gregory Szorc help: document requirements...	r28523
		The store repository layout should be used.

		This requirement has been enabled by default since the ``requires`` file
		was introduced in Mercurial 0.9.2.

		fncache
Gregory Szorc help: don't try to render a section on sub-topics...	r29747	=======
Gregory Szorc help: document requirements...	r28523
		The fncache repository layout should be used.

		The fncache layout hash encodes filenames with long paths and
		encodes reserved filenames.

		This requirement is enabled by default when the store requirement is
		enabled (which is the default behavior). It was introduced in Mercurial
		1.1 (released December 2008).

		shared
Gregory Szorc help: don't try to render a section on sub-topics...	r29747	======
Gregory Szorc help: document requirements...	r28523
		Denotes that the store for a repository is shared from another location
		(defined by the ``.hg/sharedpath`` file).

		This requirement is set when a repository is created via :hg:`share`.

		The requirement was added in Mercurial 1.3 (released July 2009).

Dan Villiom Podlaski Christiansen share: add --relative flag to store a relative path to the source...	r31133	relshared
		=========

		Derivative of ``shared``; the location of the store is relative to the
		store of this repository.

		This requirement is set when a repository is created via :hg:`share`
		using the ``--relative`` option.

		The requirement was added in Mercurial 4.2 (released May 2017).

Gregory Szorc help: document requirements...	r28523	dotencode
Gregory Szorc help: don't try to render a section on sub-topics...	r29747	=========
Gregory Szorc help: document requirements...	r28523
		The dotencode repository layout should be used.

		The dotencode layout encodes the first period or space in filenames
		to prevent issues on OS X and Windows.

		This requirement is enabled by default when the store requirement
		is enabled (which is the default behavior). It was introduced in
		Mercurial 1.7 (released November 2010).

		parentdelta
Gregory Szorc help: don't try to render a section on sub-topics...	r29747	===========
Gregory Szorc help: document requirements...	r28523
		Denotes a revlog delta encoding format that was experimental and
		replaced by generaldelta. It should not be seen in the wild because
		it was never enabled by default.

		This requirement was added in Mercurial 1.7 and removed in Mercurial
		1.9.

		generaldelta
Gregory Szorc help: don't try to render a section on sub-topics...	r29747	============
Gregory Szorc help: document requirements...	r28523
		Revlogs should be created with the generaldelta flag enabled. The
		generaldelta flag will cause deltas to be encoded against a parent
		revision instead of the previous revision in the revlog.

		Support for this requirement was added in Mercurial 1.9 (released
		July 2011). The requirement was disabled on new repositories by
		default until Mercurial 3.7 (released February 2016).

		manifestv2
Gregory Szorc help: don't try to render a section on sub-topics...	r29747	==========
Gregory Szorc help: document requirements...	r28523
		Denotes that version 2 of manifests are being used.

		Support for this requirement was added in Mercurial 3.4 (released
		May 2015). The requirement is currently experimental and is disabled
		by default.

		treemanifest
Gregory Szorc help: don't try to render a section on sub-topics...	r29747	============
Gregory Szorc help: document requirements...	r28523
		Denotes that tree manifests are being used. Tree manifests are
		one manifest per directory (as opposed to a single flat manifest).

		Support for this requirement was added in Mercurial 3.4 (released
		August 2015). The requirement is currently experimental and is
		disabled by default.

	Site-wide shortcuts
/	Use quick search box
g h	Goto home page
g g	Goto my private gists page
g G	Goto my public gists page
g 0-9	Goto bookmarked items from 0-9
n r	New repository page
n g	New gist page

	Repositories
g s	Goto summary page
g c	Goto changelog page
g f	Goto files page
g F	Goto files page with file search activated
g p	Goto pull requests page
g o	Goto repository settings
g O	Goto repository access permissions settings
t s	Toggle sidebar on some pages