COMP90044 Assignment 1: Tigger Solution

This assignment aims to give you practice in Shell programming generally a clear concrete understanding of Git's core semantics
Your task in this assignment is to implement Tigger, a subset of the version control system Git.
Git is a very complex program that has many individual commands. You will implement only a few of the most important commands. You will also be given a number of simplifying assumptions, which make your task easier.
Tigger is a much-loved children's book character known for getting Git commands backwards.
You must implement Tigger in Shell.
Interestingly, early versions of Git made heavy use of Shell and Perl. Reference implementation
Many aspects of this assignment are not fully specified in this document; instead, you must match the behaviour of a reference implementation.
For example, your script tigger-add should match the behaviour of 2041 tigger-add exactly, including producing the same error messages.
Provision of a reference implementation is a common method to provide or define an operational specification, and it's something you will likely need to do after you leave UNSW.
Discovering and matching the reference implementation's behaviour is deliberately part of the assignment.
While the code in the reference implementation is fairly straightforward, reverse-engineering its behaviour is obviously not so simple, and is a nice example of how coming to grips with the precise semantics of an apparently obvious task can still be challenging.
Tigger Commands
Subset 0
Subset 0 commands must be implemented in POSIX-compatible Shell. See the Permitted Languages section for more information.
tigger-init
The tigger-init command creates an empty Tigger repository.
tigger-init should create a directory named .tigger , which it will use to store the repository. It should produce an error
message if this directory already exists.
You should match this, and other error messages exactly. For example:
$ ls -d .tigger ls: cannot access .tigger: No such file or directory
$ ./tigger-init
Initialized empty tigger repository in .tigger
$ ls -d .tigger .tigger
$ ./tigger-init
./tigger-init: error: .tigger already exists
You do not have to use a particular representation to store the repository.
You do not have to create the same files or directories inside .tigger as the reference implementation. You can create whatever files or directories inside .tigger you wish.
Do not store information outside .tigger tigger-add filenames...
The tigger-add command adds the contents of one or more files to the “index”.
Files are added to the repository in a two-step process. The first step is adding them to the index.
You will need to store files in the index somehow in the .tigger sub-directory. For example, you might choose store them in a subdirectory of .tigger .
Only ordinary files in the current directory can be added. You can assume filenames start with an alphanumeric character ([a-zA-Z09]) and will only contain alpha-numeric characters, plus '.', '-' and '_' characters.
The tigger-add command, and other Tigger commands, will not be given pathnames with slashes. tigger-commit -m message
The tigger-commit command saves a copy of all files in the index to the repository.
A message describing the commit must be included as part of the commit command.
Tigger commits are numbered sequentially: they are not hashes, like Git. You must match the numbering scheme.
You can assume the commit message is ASCII, does not contain new-line characters, and does not start with a '-' character. tigger-log
The tigger-log command prints a line for every commit made to the repository: each line should contain the commit number and the commit message.
tigger-show [commit]:filename
The tigger-show should print the contents of the specified filename as of the specified commit. If commit is omitted, the contents of the file in the index should be printed.
You can assume the commit if specified will be a non-negative integer.
For example:
$ ./tigger-init
Initialized empty tigger repository in .tigger
$ echo line 1 > a
$ echo hello world >b
$ ./tigger-add a b
$ ./tigger-commit -m 'first commit'
Committed as commit 0
$ echo line 2 >>a
$ ./tigger-add a
$ ./tigger-commit -m 'second commit'
Committed as commit 1
$ ./tigger-log
1 second commit
0 first commit
$ echo line 3 >>a $ ./tigger-add a
$ echo line 4 >>a $ ./tigger-show 0:a line 1
$ ./tigger-show 1:a line 1
Subset 1
Subset 1 is more difficult. You will need to spend some time understanding the semantics (meaning) of these operations, by running the reference implementation, or researching the equivalent Git operations.
Note the assessment scheme recognises this difficulty.
Subset 1 commands must be implemented in POSIX-compatible Shell. See the Permitted Languages section for more information. tigger-commit [-a] -m message
tigger-commit can have a -a option, which causes all files already in the index to have their contents from the current directory
added to the index before the commit. tigger-rm [--force] [--cached] filenames...
tigger-rm removes a file from the index, or from the current directory and the index.
If the --cached option is specified, the file is removed only from the index, and not from the current directory.
tigger-rm , like git rm , should stop the user accidentally losing work, and should give an error message instead if the removal
The --force option overrides this, and will carry out the removal even if the user will lose work. tigger-status
tigger-status shows the status of files in the current directory, the index, and the repository.
$ ./tigger-init
Initialized empty tigger repository in .tigger
$ touch a b c d e f g h
$ ./tigger-add a b c d e f
$ ./tigger-commit -m 'first commit'
Committed as commit 0
$ echo hello >a
$ echo hello >b
$ echo hello >c
$ ./tigger-add a b
$ echo world >a $ rm d
$ ./tigger-rm e
$ ./tigger-add g $ ./tigger-status a - file changed, different changes staged for commit b - file changed, changes staged for commit c - file changed, changes not staged for commit d - file deleted e - deleted f - same as repo
Subset 2
Subset 2 is extremely difficult. You will need to spend considerable time understanding the semantics of these operations, by running the reference implementation, and/or researching the equivalent Git operations.
Note the assessment scheme recognises this difficulty.
Subset 2 commands must be implemented in POSIX-compatible Shell. See the Permitted Languages section for more information. tigger-branch [-d] [branch-name]
tigger-branch either creates a branch, deletes a branch, or lists current branch names. tigger-checkout branch-name
tigger-checkout switches branches.
Note that, unlike Git, you can not specify a commit or a file: you can only specify a branch. tigger-merge (branch-name|commit) -m message
tigger-merge adds the changes that have been made to the specified branch or commit to the index, and commits them.
$ ./tigger-init
Initialized empty tigger repository in .tigger
$ seq 1 7 >7.txt
$ ./tigger-add 7.txt
$ ./tigger-commit -m commit-1
Committed as commit 0 $ ./tigger-branch b1
$ ./tigger-checkout b1
Switched to branch 'b1'
$ perl -pi -e 's/2/42/' 7.txt
$ cat 7.txt
1
42
3
4
5
6
7
$ ./tigger-commit -a -m commit-2
Committed as commit 1
$ ./tigger-checkout master
If a file has been changed in both branches tigger-merge produces an error message.
Note: if a file has been changed in both branches git examines which lines have been changed and combines the changes if possible. Tigger doe not do this, for example:
$ ./tigger-init
Initialized empty tigger repository in .tigger
$ seq 1 7 >7.txt
$ ./tigger-add 7.txt
$ ./tigger-commit -m commit-1
Committed as commit 0 $ ./tigger-branch b1
$ ./tigger-checkout b1
Switched to branch 'b1'
$ perl -pi -e 's/2/42/' 7.txt
$ cat 7.txt
1
42
3
4
5
6
7
$ ./tigger-commit -a -m commit-2
Committed as commit 1
$ ./tigger-checkout master
Testing
Autotests
As usual, some autotests will be available:
$ 2041 autotest tigger tigger-* ...
You can also run only tests for a particular subset or an individual test:
$ 2041 autotest tigger subset1 tigger-* ...
$ 2041 autotest tigger subset1_13 tigger-* ...
If you are using extra Shell files, include them on the autotest command line.
Autotest and automarking will run your scripts with a current working directory different to the directory containing the script. The directory containing your submission will be in $PATH .
You will need to do most of the testing yourself.
Test Scripts
You should submit ten Shell scripts, named test00.sh to test09.sh , which run tigger commands that test an aspect of Tigger.
The test??.sh scripts do not have to be examples that your program implements successfully.
The test scripts should show how you've thought about testing carefully.
You are only expected to write test scripts testing parts of Tigger you have attempted to implement. For example, if you have not attempted subset 2 you are not expected to write test scripts testing tigger-merge . Permitted Languages
Your programs must be written entirely in POSIX-compatible shell.
Your programs will be run with dash, in /bin/dash . You can assume anything that works with the version of /bin/dash on CSE systems is POSIX compatible.
Start your programs with:
#!/bin/dash
If you want to run these scripts on your own machine — for example, one running macOS — which has dash installed somewhere other than /bin , use:
#!/usr/bin/env dash
You are permitted to use any feature /bin/dash provides.
On CSE systems, /bin/sh is the Bash (Bourne-again shell) shell: /bin/sh is a symlink to /bin/bash . Bash implements many non-POSIX extensions, including regular expressions and arrays. These will not work with /bin/dash , and you are not permitted to use these for the assignment.
You are not permitted to use Perl, Python or any language other than POSIX-compatible shell.
You are permitted to use only these external programs:
basename bunzip2 bzcat bzip2 cat
diff
dirname du echo egrep env expand expr false fgrep find fold getopt getopts grep
gunzip gzip head hostname less ln ls lzcat lzma md5sum
mkdir mktemp more mv
nl
patch
printf
pwd
readlink realpath
rev rm
rmdir sed seq sha1sum sha256sum sha512sum sleep sort
stat strings tac
tail tar tee test time top touch
tr
true
uname
uniq unlzma unxz unzip wc wget which who
xargs xz xzcat yes zcat
uncompress unexpand

Only a few of the programs in the above list are likely to be useful for the assignment.
Note you are permitted to use built-in shell features including: cd , exit , for , if , read , shift and while .
If you wish to use an external program which is not in the above list, please ask in the class forum for it to be added.
Like all good programmers, you should make as few assumptions as possible.
You can assume tigger commands are always run in the same directory as the repository, and only files from that directory are added to the repository.
You can assume the directory in which tigger commands are run will not contain sub-directories apart from .tigger .
You can assume where a branch name is expected a string will be supplied starting with an alphanumeric character ([a-zA-Z0-9]), and only containing alphanumeric characters plus '-' and '_'. In addition a branch name will not be supplied which is entirely numeric. This allows brnach names to be distinguished from commits when merging.
You can assume where a filename is expected a string will be supplied starting with an alphanumeric character ([a-zA-Z0-9]) and only containing alphanumeric characters, plus '.', '-' and '_' characters.
You can assume where a commit number is expected a string will be supplied which is a non-negative integer with no leading zeros. It will not contain white space or any other charcters except digits.
You can assume that tigger-add , tigger-show , and tigger-rm will be given just a filename, not pathnames with slashes.
You do not have to consider file permissions or other file metadata. For example, you do not have to ensure files created by a checkout command have the same permissions as when they were added.
You do not have to handle concurrency. You can assume only one instance of any tigger command is running at any time.
You can assume that only the arguments described above are supplied to tigger commands. You do not have to handle other arguments.
You should match the output streams used by the reference implementations. It writes error messages to stderr: so should you.
You should match the exit status used by the reference implementation. It exits with status 1 after an error: so should you.
You can assume the directory containing your scripts is in $PATH .
You can not assume the directory containing your scripts is the same as the repo.
Your scripts are always run in the directory containing the repository.
Note running . ./library_functions.sh will break during autotests and automarking. There can be subtle problem related to directories, ask for help in the forum.
You can assume arguments will be in the position and order shown in the usage message from the reference implementation. Other orders and positions will not be tested. For example, here is the usage message for tigger-rm :
$ 2041 tigger-rm
usage: tigger-rm [--force] [--cached] <filenames>
So, you assume that if the --force or --cached options are present, they come before all filenames, and if they are both present the --force option will come first.
Tigger error messages include the program name. It is recommended you use $0 however it is also acceptable to hard-code the program name. The automarking and style marking will accept both.
Do not use the modification time of a file to determine whether it has changed. You must use the file contents. Change Log
Version 0.1 Initial release
Version 0.2Reference/Autotest: Fix typo in tigger-rm output
Version 0.3Autotest: Fix autotest not showing enough output
Specification: Added nl utility to the list of allowed external programs
Reference: Correct program name in error messages

Testing
When you think your program is working, you can use autotest to run some simple automated tests:
$ 2041 autotest tigger
2041 autotest will not test everything. Always do your own testing.
Submission
When you are finished working on the assignment, you must submit your work by running give :
$ give cs2041 ass1_tigger tigger-* test??.sh [any-other-files]
You can run give multiple times.
Only your last submission will be marked.
You can check your latest submission on CSE servers with:
$ 2041 classrun check ass1_tigger
You can check the files you have submitted here.
The UNSW standard late penalty for assessment is 5% per day for 5 days - this is implemented hourly for this assignment.
Each hour your assignment is submitted late reduces its mark by 0.2%.
For example, if an assignment worth 60% was submitted 10 hours late, it would be awarded 58.8%.
Beware - submissions more 5 days late will receive zero marks. This again is the UNSW standard assessment policy. Assessment Scheme
This assignment will contribute 15 marks to your final COMP(2041|9044) mark
15% of the marks for assignment 1 will come from hand-marking. These marks will be awarded on the basis of clarity, commenting, elegance and style: in other words, you will be assessed on how easy it is for a human to read and understand your program.
5% of the marks for assignment 1 will be based on the test suite you submit.
80% of the marks for assignment 1 will come from the performance of your code on a large series of tests.
HD (85+) All subsets working; code is beautiful; great test suite
DN (75+) Subset 1 working; good clear code; good test suite
CR (65+) Subset 0 working; good clear code; good test suite
PS (55+) Subset 0 passing some tests; code is reasonably readable; reasonable test suite
PS (50+) Good progress on assignment, but not passing autotests
0% knowingly providing your work to anyone and it is subsequently submitted (by anyone).
0 FL for submitting any other person's work; this includes joint work.
COMP(2041|9044)

academic submitting another person's work without their consent; misconduct paying another person to do work for you.
Intermediate Versions of Work
You are required to submit intermediate versions of your assignment.
Every time you work on the assignment and make some progress you should copy your work to your CSE account and submit it using the give command below. It is fine if intermediate versions do not compile or otherwise fail submission tests. Only the final submitted version of your assignment will be marked.
Attribution of Work
This is an individual assignment.
The work you submit must be entirely your own work, apart from any exceptions explicitly included in the assignment specification above. Submission of work partially or completely derived from any other person or jointly written with any other person is not permitted.
Assignment submissions will be examined, both automatically and manually, for such submissions.

For all enquiries, please email the class account at cs2041@cse.unsw.edu.au
CRICOS Provider 00098G