Bug Showcase

Check out what we got for you in HasBugs. When you are at one Bug, you can navigate to previous and next with the arrows.

cabal-1

Cabal starts multiple processes to build a project. 'cabal run' termination does not terminate all child processes automatically as well. The solution is to use 'withCreateProcess' rather than 'createProcess' and throw an asynchronous exception from the main thread when a termination is wanted.

[system-test] [os] [multi-threading] [multi-processing]
cabal-2

Users can use 'cabal init' to bootstrap projects. 'cabal init -i' does not automatically fill in author name and e-mail anymore. The solution is to add a guess (=default) to the prompt.

[missing-value] [golden-test] [unit-test]
cabal-3

Cabal provides and parses it's own configuration file. The used method 'cabal HEAD' is confused by trailing whitespaces in 'default-language' tags. The solution is to fix parsing by changing 'some anyChar' to 'munch1 isAlphaNum'. This way, only characters are parsed into a language.

[parsing] [whitespace] [system-test]
cabal-4

Cabal supports a dry-run-feature, which runs a subset of the specified commands.The '--dry-run' did not actually dry-run for commands 'v2-configure', 'v2-freeze', 'v2-run', and 'v2-exec'. Instead, the dry-run flag was ignored and the commands did perform a few actions. The fix is to add if-expressions where needed in the commands' code to perform the dry-run as expected.

[missing-cases] [system-test]
cabal-5

When initialising a project with the '--no-comments' flag, cabal fields that would normally be commented out still had comments in front of them. Expected behaviour is that comments are not present in front of any fields, commented out or not. Solution is to always remove comments when the '--no-comments' flag is set.

[logic] [refactoring] [golden-test] [system-test]
cabal-6

Multiple concurrent builds would sometimes give an error similar to 'ghc-pkg: cannot create: /home/edsko/path/to/main-package/dist-newstyle/packagedb/ghc-7.10.3 already exists' because packagedbs would be made at the same time. The solution is to initialise packagedbs at the start of the build process rather than when needed.

[concurrency] [file-management] [system-test]
duckling-1

Duckling tries to recognize quantities and numbers, including 'millions' in german language. The previous regex did not account for millions, which use a different (rarer) pronomina. The fix is to adjust the regex with an additional case.

[unit-test] [language] [regex]
duckling-2

Duckling can parse multiple items, and sometimes these can be ambigious depending on their context. In the spanish, 'una hora' can either refer to 1PM or to 1 hour, which was not properly recognized before. The fix is to account for this ambiguity with the existing ambiguity logic.

[unit-test] [time] [parsing] [ambiguity]
duckling-3

Duckling recognizes times mentioned in a text, but fails to (extensively) parse combined times such as `2 hours and 30 minutes`. Instead of parsing it to 150 minutes, it is parsed into 120 minutes and 30 minutes. The fix adds combinator rules based on keywords and changes the rule-application-order.

[unit-test] [time] [parsing]