v2.0.9

• added "without_lines" method to "Localization": returns a variant of a given localization with a given line removed.
• added "sample" method to "Localization": samples lines from a given localization according to their suspiciousness values.

v2.0.8

• fixed bug that caused Travis to attempt to upload package to PyPI for each build configuration (rather than just once).
• added "restricted_to_lines" method to "Localization" class

v2.0.7

• added support for containers with custom entrypoints by dumping the state of the environment upon launching the container to /.environment as a read-only file.
• added bug coverage command
• added is_alive to container manager
• fixed API regressions caused by transforming Container.bug from a Bug instance to a strspecifying the name of the bug.
• added len to FileLineSet
• added zero-argument constructor to FileLineSet
• added lines property to TestSuiteCoverage
• added files property to FileLineSet

v2.0.6

• bug fix: fixed bad keyword arguments that caused the container launch command to crash.
• bug fix: ensure that sources directory exists before attempting to write registry file.

v2.0.5

• restored Python 3.5 compatibility
• added mypy to Travis configuration

v2.0.4

• fixed bug in parsing of gcovr reports
• decreased overhead of extracting coverage information from gcovr report
• added verbose flag to command (and test) execution
• the bug validate command now supports the --verbose flag

v2.0.3

• moved coverage extraction to a dedicated coverage manager
• added source code instrumentation to coverage extraction process
• refactored coverage-related data structures
• added FileLineSet container class
• simplified Language enum
• fixed regression in "patch" method for container manager

v2.0.2

• fixes regression in "bug validate" and compilers caused by migration of functionalities from Container to ContainerManager

v2.0.1

• moved "provision" methods from Tool and Container classes to their respective managers

v2.0.0

• implemented new universal file format: manifest files may now provide multiple resources (rather than a single bug or tool), and no longer need to provide instructions for building a Docker image for bugs/tools. Build instructions (soon to be known as blueprints) are now stored separately from bug and tool descriptions.
• added ability to add local directories as sources
• added basic logging mechanisms (logs are stored in logs subdirectory within BugZoo installation directory).
• bad manifest files no longer cause BugZoo to crash: BugZoo will attempt to extract as many resources as possible from the file, and will ignore any malformed resources.
• bugs, tools, and build instructions (blueprints) no longer need to be associated with a dataset or source. This change should make it easier for users to dynamically create ephemeral resources.