8d9e25dbdd
I noticed that 3 of the tarsum test cases had expected a tarsum with a sha256 hash of e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 As I've been working with sha256 quite a bit lately, it struck me that this is the initial digest value for sha256, which means that no data was processed. However, these tests *do* process data. It turns out that there was a bug in the test handling code which did not wait for tarsum to end completely. This patch corrects these test cases. I'm unaware of anywhere else in the code base where this would be an issue, though we definitily need to look out in the future to ensure we are completing tarsum reads (waiting for EOF). Docker-DCO-1.1-Signed-off-by: Josh Hawn <josh.hawn@docker.com> (github: jlhawn) |
||
|---|---|---|
| .. | ||
| archive | ||
| broadcastwriter | ||
| chrootarchive | ||
| devicemapper | ||
| fileutils | ||
| graphdb | ||
| httputils | ||
| ioutils | ||
| iptables | ||
| jsonlog | ||
| listenbuffer | ||
| mflag | ||
| mount | ||
| namesgenerator | ||
| networkfs | ||
| parsers | ||
| pools | ||
| promise | ||
| proxy | ||
| reexec | ||
| signal | ||
| stdcopy | ||
| symlink | ||
| sysinfo | ||
| system | ||
| systemd | ||
| tailfile | ||
| tarsum | ||
| term | ||
| testutils | ||
| timeutils | ||
| truncindex | ||
| units | ||
| urlutil | ||
| version | ||
| README.md | ||
README.md
pkg/ is a collection of utility packages used by the Docker project without being specific to its internals.
Utility packages are kept separate from the docker core codebase to keep it as small and concise as possible. If some utilities grow larger and their APIs stabilize, they may be moved to their own repository under the Docker organization, to facilitate re-use by other projects. However that is not the priority.
The directory pkg is named after the same directory in the camlistore project. Since Brad is a core
Go maintainer, we thought it made sense to copy his methods for organizing Go code :) Thanks Brad!
Because utility packages are small and neatly separated from the rest of the codebase, they are a good place to start for aspiring maintainers and contributors. Get in touch if you want to help maintain them!