b1594c59f5
inotify event is trigged immediately there's data written to disk. But at the time that the inotify event is received, the json line might not fully saved to disk. If the json decoder tries to decode in such case, an io.UnexpectedEOF will be trigged. We used to retry for several times to mitigate the io.UnexpectedEOF error. But there are still flaky tests caused by the partial log entries. The daemon knows exactly when there are new log entries emitted. We can use the pubsub package to notify all the log readers instead of inotify. Signed-off-by: Shijiang Wei <mountkin@gmail.com> try to fix broken test. will squash once tests pass Signed-off-by: Shijiang Wei <mountkin@gmail.com> |
||
---|---|---|
.. | ||
aaparser | ||
archive | ||
authorization | ||
broadcaster | ||
chrootarchive | ||
devicemapper | ||
directory | ||
discovery | ||
filenotify | ||
fileutils | ||
gitutils | ||
graphdb | ||
homedir | ||
httputils | ||
idtools | ||
integration | ||
ioutils | ||
jsonlog | ||
jsonmessage | ||
locker | ||
longpath | ||
loopback | ||
mflag | ||
mount | ||
namesgenerator | ||
parsers | ||
pidfile | ||
platform | ||
plugins | ||
pools | ||
progress | ||
promise | ||
proxy | ||
pubsub | ||
random | ||
reexec | ||
registrar | ||
signal | ||
stdcopy | ||
streamformatter | ||
stringid | ||
stringutils | ||
symlink | ||
sysinfo | ||
system | ||
tailfile | ||
tarsum | ||
term | ||
tlsconfig | ||
truncindex | ||
urlutil | ||
useragent | ||
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!