| Age | Commit message (Collapse) | Author | Lines |
|
It read the config the 404 test had written, so it could not run alone
with --run.
|
|
An empty cache passed just as well when nothing was cached at all.
|
|
A first request that left no list behind made the second scan again,
and the test passed just the same.
|
|
|
|
|
|
A value cgit does not know as a period turns the statistics page off,
so a typo such as "decade" read the same as leaving stats off on
purpose. The empty value stays quiet because a cached repolist writes
it for a repository that turned stats off.
|
|
The include run checked only the line in the outer file, so a warning
from the included one could have named the outer file and passed.
|
|
The messages hold the trash directory's path and were matched as
patterns, so a checkout path holding a bracket or a star would break
them.
|
|
Without the fold of a carriage return before a newline, repo.path keeps
a trailing one and the repository cannot be opened, and no test had a
file saved that way. Semicolon comments and a line with no equals sign
were untested too.
|
|
Nothing reached the guard that stops a file including itself, so its
loss would have gone unseen until a site's own cgitrc recursed until
the stack gave out.
|
|
|
|
The 404 page names only the repository and nothing reached the log, so
a mistyped repo.path left no trace of the path cgit had tried.
|
|
atoi reads "yes" or "true" as 0, so repo.hide=yes, or cgit.hide true
in a scanned repository's git config, silently did nothing. The values
keep that meaning, since honouring them now would hide repositories on
upgrade, but each one is logged with its file and line.
|
|
A missing or unreadable cgitrc left only "No repositories found" and an
empty log, the commonest first mistake with no trace of its cause. A
scanned repository's own cgitrc stays quiet, since most have none.
|
|
|
|
The one-line request wrappers go with them. Configs with several
repositories, a key out of place on purpose, the cache on or no
repository of their own stay written out.
|
|
|
|
The check asked for the summary page, which never runs an about filter,
so it passed with exec:/bin/true where no such file exists, and with a
filter that does not exist at all. Its first line read the stderr the
previous test left behind. execvp searches the PATH, so a plain true
runs the same everywhere.
|
|
skip_line stopped at a NUL as well as at a newline, so the rest of the
comment after one was read as a setting.
|
|
|
|
|
|
|
|
|