upstream/mercurial-mirror Files · tests/helpers-testrepo.sh

hgweb: render next pages on /graph incrementally...

hgweb: render next pages on /graph incrementally Previously, when user scrolled down to see the next page on /graph, all hgweb did was re-render everything that would be visible (by simply incrementing revcount). It was not efficient at all, and this patch makes /graph page behave similarly to the regular /log: every new page only consists of new changesets, no duplication, and only jsdata is based on the full set of changesets required to build accurate graph. This is achieved by adding "?graphtop=<node>" to the next page URL template, effectively remembering where the graph started, and using that value to create the new `tree` that covers the whole visible graph. That variable is then used to produce jsdata for redrawing graph client-side. nextentry is used for the same purpose as on /log page (to format the next page URL), but it's not a part of the graph.

Yuya Nishihara - - Load All Authors

File last commit:

r33201:45d6e276 default


                r35410:f84b0125

default

Download file

             helpers-testrepo.sh
        
                    53 lines
            
             | 1.7 KiB
            
                | application/x-sh
            
             |
                BashLexer
            
             / tests / helpers-testrepo.sh
          
                    History
                
                 |
                  Annotation
                 | Raw
                 |Copy content
                 |Copy permalink

      # In most cases, the mercurial repository can be read by the bundled hg, but

      # that isn't always true because third-party extensions may change the store

      # format, for example. In which case, the system hg installation is used.

      #

      # We want to use the hg version being tested when interacting with the test

      # repository, and the system hg when interacting with the mercurial source code

      # repository.

      #

      # The mercurial source repository was typically orignally cloned with the

      # system mercurial installation, and may require extensions or settings from

      # the system installation.

      syshg () {

          (

              syshgenv

              exec hg "$@"

          )

      }

      # Revert the environment so that running "hg" runs the system hg

      # rather than the test hg installation.

      syshgenv () {

          . "$HGTEST_RESTOREENV"

          HGPLAIN=1

          export HGPLAIN

      }

      # The test-repo is a live hg repository which may have evolution markers

      # created, e.g. when a ~/.hgrc enabled evolution.

      #

      # Tests may be run using a custom HGRCPATH, which do not enable evolution

      # markers by default.

      #

      # If test-repo includes evolution markers, and we do not enable evolution

      # markers, hg will occasionally complain when it notices them, which disrupts

      # tests resulting in sporadic failures.

      #

      # Since we aren't performing any write operations on the test-repo, there's

      # no harm in telling hg that we support evolution markers, which is what the

      # following lines for the hgrc file do:

      cat >> "$HGRCPATH" << EOF

      [experimental]

      evolution = createmarkers

      EOF

      # Use the system hg command if the bundled hg can't read the repository with

      # no warning nor error.

      if [ -n "`hg id -R "$TESTDIR/.." 2>&1 >/dev/null`" ]; then

          alias testrepohg=syshg

          alias testrepohgenv=syshgenv

      else

          alias testrepohg=hg

          alias testrepohgenv=:

      fi

	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

				# In most cases, the mercurial repository can be read by the bundled hg, but
				# that isn't always true because third-party extensions may change the store
				# format, for example. In which case, the system hg installation is used.
				#
				# We want to use the hg version being tested when interacting with the test
				# repository, and the system hg when interacting with the mercurial source code
				# repository.
				#
				# The mercurial source repository was typically orignally cloned with the
				# system mercurial installation, and may require extensions or settings from
				# the system installation.
				syshg () {
				(
				syshgenv
				exec hg "$@"
				)
				}

				# Revert the environment so that running "hg" runs the system hg
				# rather than the test hg installation.
				syshgenv () {
				. "$HGTEST_RESTOREENV"
				HGPLAIN=1
				export HGPLAIN
				}

				# The test-repo is a live hg repository which may have evolution markers
				# created, e.g. when a ~/.hgrc enabled evolution.
				#
				# Tests may be run using a custom HGRCPATH, which do not enable evolution
				# markers by default.
				#
				# If test-repo includes evolution markers, and we do not enable evolution
				# markers, hg will occasionally complain when it notices them, which disrupts
				# tests resulting in sporadic failures.
				#
				# Since we aren't performing any write operations on the test-repo, there's
				# no harm in telling hg that we support evolution markers, which is what the
				# following lines for the hgrc file do:
				cat >> "$HGRCPATH" << EOF
				[experimental]
				evolution = createmarkers
				EOF

				# Use the system hg command if the bundled hg can't read the repository with
				# no warning nor error.
				if [ -n "`hg id -R "$TESTDIR/.." 2>&1 >/dev/null`" ]; then
				alias testrepohg=syshg
				alias testrepohgenv=syshgenv
				else
				alias testrepohg=hg
				alias testrepohgenv=:
				fi