summaryrefslogtreecommitdiff
path: root/tests/resources
Commit message (Collapse)AuthorAgeFilesLines
* #6154 git_status_list_new case insensitive fixMiguel Arroz2022-01-014-0/+2
|
* Merge pull request #6124 from csware/config-parsingEdward Thomson2021-12-231-0/+10
|\ | | | | Config parsing
| * Config parsing confused by continuations that start with quotesSven Strickroth2021-12-061-0/+10
| | | | | | | | | | | | (fixes issue #6089) Signed-off-by: Sven Strickroth <email@cs-ware.de>
* | Merge pull request #6101 from mkhl/fix/instead-ofEdward Thomson2021-12-231-9/+32
|\ \ | | | | | | remotes: fix insteadOf/pushInsteadOf handling
| * | update remote/insteadof testsMartin Kühl2021-11-111-9/+32
| |/ | | | | | | | | | | | | | | | | | | | | | | | | we want to test: - an anonymous repo (a url) - a named repo with a url - a named repo with a url and pushurl and for each of these matching configuration: - only insteadOf - only pushInsteadOf - both insteadOf and pushInsteadOf this change adds test cases for all of these combinations.
* | Add a branch with a empty reflog into testrepo.gitYoichi Nakayama2021-10-222-0/+1
|/
* Add test for revert+rename bug.Colin Stolley2021-09-158-0/+11
|
* Add test config parsingBasile Henry2021-09-091-0/+5
| | | | | This tests parsing a multiline string containing multiple quoted comment chars. See #6019
* opts: test GIT_OPT_SET_SSL_CERT_LOCATIONSEdward Thomson2021-08-293-0/+82
| | | | | Include a self-signed certificate for test.libgit2.org:1443 that we can use to verify that GIT_OPT_SET_SSL_CERT_LOCATIONS works.
* filter: introduce GIT_BLOB_FILTER_ATTRIBUTES_FROM_COMMITEdward Thomson2021-07-227-0/+5
| | | | | Provide a mechanism to filter using attribute data from a specific commit (making use of `GIT_ATTR_CHECK_INCLUDE_COMMIT`).
* Add testcaseKartikaya Gupta2021-05-1213-0/+11
|
* commit-graph: Support lookups of entries in a commit-graphlhchavez2021-01-101-0/+0
| | | | | | | | | | This change introduces `git_commit_graph_entry_find()` and `git_commit_graph_entry_parent()`. These two functions allow a much faster lookup of commits by ID, since the ODB does not need to be consulted, the commit object does not need to be inflated, and the contents of the commit object do not need to be parsed. Part of: #5757
* commit-graph: Introduce a parser for commit-graph fileslhchavez2021-01-101-0/+0
| | | | | | | | This change is the first in a series to add support for git's commit-graph. This should speed up commit graph traversals by avoiding object parsing and allowing some operations to terminate earlier. Part of: #5757
* multipack: Introduce a parser for multi-pack-index fileslhchavez2020-10-051-0/+0
| | | | | | | This change is the first in a series to add support for git's multi-pack-index. This should speed up large repositories significantly. Part of: #5399
* Fix config file parsing with multi line values containing quoted partsSven Strickroth2020-09-181-0/+10
| | | | Signed-off-by: Sven Strickroth <email@cs-ware.de>
* blame: add option to ignore whitespace changesCarl Schwan2020-04-1425-1/+5
|
* Fix segfault when calling git_blame_buffer()lhchavez2020-03-234-1/+5
| | | | | | | | This change makes sure that the hunk is not null before trying to dereference it. This avoids segfaults, especially when blaming against a modified buffer (i.e. the index). Fixes: #5443
* refs: refuse to delete HEADJosh Bleecher Snyder2020-01-151-0/+1
| | | | | | | This requires adding a new symbolic ref to the testrepo fixture. Some of the existing tests attempt to delete HEAD, expecting a different failure. Introduce and use a non-HEAD symbolic ref instead. Adjust a few other tests as needed. Fixes #5357
* Disallow NTFS Alternate Data Stream attacks, even on Linux/macOSJohannes Schindelin2019-12-104-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A little-known feature of NTFS is that it offers to store metadata in so-called "Alternate Data Streams" (inspired by Apple's "resource forks") that are copied together with the file they are associated with. These Alternate Data Streams can be accessed via `<file name>:<stream name>:<stream type>`. Directories, too, have Alternate Data Streams, and they even have a default stream type `$INDEX_ALLOCATION`. Which means that `abc/` and `abc::$INDEX_ALLOCATION/` are actually equivalent. This is of course another attack vector on the Git directory that we definitely want to prevent. On Windows, we already do this incidentally, by disallowing colons in file/directory names. While it looks as if files'/directories' Alternate Data Streams are not accessible in the Windows Subsystem for Linux, and neither via CIFS/SMB-mounted network shares in Linux, it _is_ possible to access them on SMB-mounted network shares on macOS. Therefore, let's go the extra mile and prevent this particular attack _everywhere_. To keep things simple, let's just disallow *any* Alternate Data Stream of `.git`. This is libgit2's variant of CVE-2019-1352. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
* config_entries: micro-optimize storage of multivarsPatrick Steinhardt2019-11-051-0/+40000
| | | | | | | | | | | | | | | | | | | | | | | Multivars are configuration entries that have many values for the same name; we can thus micro-optimize this case by just retaining the name of the first configuration entry and freeing all the others, letting them point to the string of the first entry. The attached test case is an extreme example that demonstrates this. It contains a section name that is approximately 500kB in size with 20.000 entries "a=b". Without the optimization, this would require at least 20000*500kB bytes, which is around 10GB. With this patch, it only requires 500kB+20000*1B=20500kB. The obvious culprit here is the section header, which we repeatedly include in each of the configuration entry's names. This makes it very easier for an adversary to provide a small configuration file that disproportionally blows up in memory during processing and is thus a feasible way for a denial-of-service attack. Unfortunately, we cannot fix the root cause by e.g. having a separate "section" field that may easily be deduplicated due to the `git_config_entry` structure being part of our public API. So this micro-optimization is the best we can do for now.
* Merge pull request #5195 from tiennou/fix/commitish-smart-pushPatrick Steinhardt2019-09-131-0/+1
|\ | | | | smart: use push_glob instead of manual filtering
| * smart: use push_glob instead of manual filteringEtienne Samson2019-08-211-0/+1
| | | | | | | | | | | | | | | | | | | | The code worked under the assumption that anything under `refs/tags` are tag objects, and all the rest would be peelable to a commit. As it is completely valid to have tags to blobs under a non `refs/tags` ref, this would cause failures when trying to peel a tag to a commit. Fix the broken filtering by switching to `git_revwalk_push_glob`, which already handles this case.
* | tests: add a subdirectory to crlf testsEdward Thomson2019-08-1112-5/+25
| | | | | | | | | | Add a subdirectory in the crlf.git bare repository that has a second-level .gitattribute file.
* | filter: test we can filter a blob in a bare repoEdward Thomson2019-08-1167-0/+23
|/
* attr: ensure regular attr files can have whitespaceethomson/ignore_spacesEdward Thomson2019-05-241-0/+7
| | | | | | Unlike ignore files, gitattribute files can have flexible whitespace at the beginning of the line. Ensure that by adding new ignore rules that we have not impeded correct parsing of attribute files.
* index: preserve extension parsing errorsEtienne Samson2019-01-247-0/+15
| | | | | | | Previously, we would clobber any extension-specific error message with an "extension is truncated" message. This makes `read_extension` correctly preserve those errors, takes responsibility for truncation errors, and adds a new message with the actual extension signature for unsupported mandatory extensions.
* Convert tests/resources/push.sh to LF endingslhchavez2019-01-151-55/+55
| | | | | This changes that file to use UNIX line-endings, which makes sense since this is a UNIXy file.
* Get rid of some test files that were accidentally committedTyler Wanek2019-01-142151-11979/+0
|
* crlf_data: add corpus of known-good odb-filtered dataEdward Thomson2018-12-036257-0/+32690
| | | | | | | | | | Use the crlf data scripts to produce a corpus of known-good data in "git" format (aka ODB format) from a variety of files with different line endings. `git` created these files running `git add` to stage the contents then extracting the data from the repository. We'll use these to ensure that we create identical contents when we add files into the index.
* crlf: re-use existing crlf script to create odbEdward Thomson2018-12-0322-118/+63
| | | | | | Re-use the existing crlf data generation script for creating the to-odb dataset. Also, store the actual file contents instead of the ID so that we can identify differences instead of detecting that differences exist.
* crlf: script to generate expected crlf data for adding files to indexSven Strickroth2018-12-0322-3/+232
| | | | | | | | | | Include a shell script that will generate the expected data of OIDs and failures for calling git.git to capture its output as a test resource. Right now, there is no need to differentiate different systems as git behaves the same on all systems IIRC. Signed-off-by: Sven Strickroth <email@cs-ware.de>
* crlf_data: move to a "to_workdir" folderEdward Thomson2018-12-031370-3/+4
| | | | | | | Move the crlf_data folders reponsible for holding the state of the filters going into the working directory to "to_workdir" variations of the folder name to accommodate future growth into the "to odb" filter variation. Update the script to create these new folders as appopriate.
* apply tests: ensure we can patch a modified fileEdward Thomson2018-11-051-0/+0
| | | | | | | | Patch application need not be on an unmodified file; applying to an already changed file is supported provided the patch still applies cleanly. Add tests that modifies the contents of a file then applies the patch and ensures that the patch applies cleanly, and the original changes are also kept.
* checkout: fix test fixture missing objectscmn/validity-tree-from-unowned-indexEdward Thomson2018-10-203-0/+0
| | | | | | | | | | | | | | | The testrepo test fixture has an index file that's damaged, missing an object. The index previously had an entry of `src/index.c` with id 3161df8cbf3a006b4ef85be6497a0ea6bde98541, but that object was missing in the repository. This commit adds an object to the repository and updates the index to use that existing blob. Similarly, the index has an entry for `readme` with an id of 97328ac7e3bd0bcd3900cb3e7a624d71dd0df888. This can be restored from other test repositories. With these fixed, now the write tree from index tests can pass since they validate object existence.
* tests: verify diff stats with renames in subdirectoryPatrick Steinhardt2018-10-0412-1/+8
| | | | | | | | | | | Until now, we didn't have any tests that verified that our format for renames in subdirectories is correct. While our current behaviour is no different than for renames that do not happen with a common prefix shared between old and new file name, we intend to change the format to instead match the format that upstream git uses. Add a test case for this to document our current behaviour and to show how the next commit will change that format.
* Merge pull request #4727 from libgit2/cmn/null-oid-existing-treeEdward Thomson2018-08-261-0/+0
|\ | | | | tree: accept null ids in existing trees when updating
| * tree: accept null ids in existing trees when updatingCarlos Martín Nieto2018-07-181-0/+0
| | | | | | | | | | | | | | | | | | When we add entries to a treebuilder we validate them. But we validate even those that we're adding because they exist in the base tree. This disables using the normal mechanisms on these trees, even to fix them. Keep track of whether the entry we're appending comes from an existing tree and bypass the name and id validation if it's from existing data.
* | Write a test.Nelson Elhage2018-08-141-0/+1
|/
* mailmap: Updates tests for new API and featuresNika Layzell2018-06-146-1/+5
|
* mailmap: Clean up the mailmap fixture's .gitted directoryNika Layzell2018-06-1413-543/+0
|
* mailmap: Add a bunch of tests for the new mailmap functionalityNika Layzell2018-06-1455-0/+596
|
* checkout: add a failing test for refusing a symlinked .gitmodulesCarlos Martín Nieto2018-05-225-0/+1
| | | | | We want to reject these as they cause compatibility issues and can lead to git writing to files outside of the repository.
* tests: add information about the crlf data generatorEdward Thomson2018-04-172-0/+87
| | | | | The CRLF data generator is somewhat obscure; add information about how to use it and what it does.
* tests: crlf: update POSIX test data to reflect Git 2.9+ behaviorSven Strickroth2018-04-1731-70/+70
| | | | | | Update with vanilla Git 2.11.0 on Debian Signed-off-by: Sven Strickroth <email@cs-ware.de>
* tests: crlf: update Windows test data to reflect Git 2.9+ behaviorSven Strickroth2018-04-1735-80/+80
| | | | | | Update with "git version 2.11.0.windows.3" Signed-off-by: Sven Strickroth <email@cs-ware.de>
* revwalk: fix uninteresting revs sometimes not limiting graphwalkPatrick Steinhardt2018-04-128-0/+17
| | | | | | | | | | | | | | | When we want to limit our graphwalk, we use the heuristic of checking whether the newest limiting (uninteresting) revision is newer than the oldest interesting revision. We do so by inspecting whether the first item's commit time of the user-supplied list of revisions is newer than the last added interesting revision. This is wrong though, as the user supplied list is in no way guaranteed to be sorted by increasing commit dates. This could lead us to abort the revwalk early before applying all relevant limiting revisions, outputting revisions which should in fact have been hidden. Fix the heuristic by instead checking whether _any_ of the limiting commits was made earlier than the last interesting commit. Add a test.
* testrepo: add new branchEdward Thomson2018-02-233-0/+3
| | | | | | Add a new branch to the `testrepo` repository, where the `README` file has changed to executable. This branch enables typechange tests between the new `executable` branch and `master`.
* tests: add rename-rewrite scenarios to "renames" repositoryPatrick Steinhardt2018-02-207-0/+3
| | | | | | | Add two more scenarios to the "renames" repository. The first scenario has a major rewrite of a file and a delete of another file, the second scenario has a deletion of a file and rename of another file to the deleted file. Both scenarios will be used in the following commit.
* Add failing test case for virtual commit merge base issueEdward Thomson2018-02-0426-0/+9
|
* Introduce additional criss-cross merge branchesEdward Thomson2018-02-0468-0/+11
|
View Lorry Controller Status