Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / darcy-framework/synq issues and pull requests
#28 - Cleanup pom
Pull Request -
State: closed - Opened by alechenninger almost 9 years ago
#27 - Add PollEvent overrides for FailPollEvent (fixes #9)
Pull Request -
State: closed - Opened by alechenninger almost 9 years ago
#26 - Fail in event thread using try/catch instead of uncaught exceptions
Pull Request -
State: closed - Opened by alechenninger almost 9 years ago
#25 - Uncaught exception in sleeping thread
Issue -
State: closed - Opened by jwilson100 almost 9 years ago
- 1 comment
#24 - Allowing injecting different "clock"
Issue -
State: open - Opened by alechenninger over 9 years ago
- 1 comment
Labels: enhancement, tests
#23 - Add non static version of API
Issue -
State: open - Opened by alechenninger almost 10 years ago
Labels: enhancement
#22 - Add shouldNotExpect as alternative to failIf
Pull Request -
State: closed - Opened by alechenninger almost 10 years ago
- 1 comment
#21 - Lone FailEvent should be able to return the item under examination instead of null in some cases
Issue -
State: open - Opened by alechenninger almost 10 years ago
Labels: enhancement
#20 - Allow filtering of events
Issue -
State: open - Opened by alechenninger about 10 years ago
Labels: enhancement
#19 - Context lost in ThreadedPollEvent exceptions
Issue -
State: closed - Opened by alechenninger over 10 years ago
Labels: bug
#18 - Address thread safety concerns?
Issue -
State: closed - Opened by alechenninger over 10 years ago
- 2 comments
Labels: question
#17 - Consider API for default timeouts?
Issue -
State: open - Opened by alechenninger over 10 years ago
- 1 comment
Labels: enhancement, question
#16 - waffle.io Badge
Pull Request -
State: closed - Opened by waffle-iron over 10 years ago
- 1 comment
#15 - HamcrestConditions toString is prone to RuntimeExceptions
Issue -
State: closed - Opened by alechenninger over 10 years ago
- 1 comment
Labels: bug
#14 - MultiEvent describedAs should affect inner event like all other fluent modifications
Issue -
State: closed - Opened by alechenninger over 10 years ago
- 1 comment
Labels: bug
#13 - Exception handling redesign
Issue -
State: closed - Opened by alechenninger over 10 years ago
- 2 comments
Labels: bug, enhancement
#12 - Thread crashes in MultiEventTest?
Issue -
State: closed - Opened by alechenninger over 10 years ago
Labels: bug
#11 - FailEvent evaluates exception message at creation, not at time of failure
Issue -
State: closed - Opened by alechenninger over 10 years ago
Labels: bug
#10 - InterruptedExceptions are not being handled correctly
Issue -
State: closed - Opened by alechenninger over 10 years ago
- 1 comment
Labels: bug
#9 - Some interfaces need to override Event's default "fluent" methods to return instances of the same type
Issue -
State: closed - Opened by alechenninger over 10 years ago
- 2 comments
Labels: bug
#8 - Timeout messages' duration is in ISO-8601 standard format instead of plain English
Issue -
State: open - Opened by alechenninger over 10 years ago
Labels: bug, ready
#7 - describedAs doesn't work
Issue -
State: closed - Opened by alechenninger over 10 years ago
- 1 comment
Labels: bug
#6 - API to react to specific event in a MultiEvent?
Issue -
State: open - Opened by alechenninger over 10 years ago
Labels: enhancement, question
#5 - Better timeout messages
Issue -
State: closed - Opened by alechenninger over 10 years ago
- 3 comments
Labels: enhancement
#4 - SequentialEvent timeout message is misleading
Issue -
State: closed - Opened by alechenninger over 10 years ago
- 1 comment
Labels: bug
#3 - There are no unit tests
Issue -
State: closed - Opened by alechenninger over 10 years ago
- 3 comments
Labels: refactor
#2 - Fail conditions are not associated with throwables in Event API
Issue -
State: closed - Opened by alechenninger over 10 years ago
Labels: bug
#1 - Javac 1.8 thinks Event methods are too ambiguous, Eclipse java 1.8 compiler don't care
Issue -
State: closed - Opened by alechenninger over 10 years ago
- 3 comments
Labels: bug