Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

johnboulle/clockwork #37

Open
joeblubaugh opened this issue Dec 10, 2019 · 2 comments
Open

johnboulle/clockwork #37

joeblubaugh opened this issue Dec 10, 2019 · 2 comments

Comments

@joeblubaugh
Copy link

joeblubaugh commented Dec 10, 2019 •
edited by adamdecaf

Where is the project currently hosted?

https://github.com/jonboulle/clockwork

What languages other than Go does the project utilize?

only Go

When was the project's last activity?

Jan 4 2019 - last merged PR

Does the project have a maintainer, or a maintainer looking for someone to take over the project?

The current maintainer has been inactive since January

What active projects replicate the popular functionality of this project, if any?

There's github.com/benbjohnson/clock but it's also unmaintained and buggy (see #35)

What are some example projects that make use of this package?

kubectl uses it in several packages. coreOS uses this in several packages. etcd uses this in several packages.

Are there any outstanding critical bugs that result in the library being totally unusable or insecure?

There's no time.Timer support in the package, and issues about it have been open for years.

Please provide a link to the project importers from https://godoc.org.

https://godoc.org/github.com/jonboulle/clockwork?importers

What else would you like to mention about the project?

This package has many, many more importers than benbjohnson/clock and seems similarly unmaintained and incomplete.
@cristaloleg
Copy link
Member

404 ?

@adamdecaf
Copy link
Member

The link looks to be https://github.com/jonboulle/clockwork

yrashk added a commit to yrashk/bpxe that referenced this issue May 21, 2021
@yrashk
Problem: timer events are sent manually
181c343 
For the time being, all timer events are being sent
manually in tests. This is not enough for a functioning
BPMN engine.

Solution: introduce `timer` package

This is something to be used by the engine initiate timer
events. It's not yet integrated into the engine.

Speaking of the mock time implementation, and picking
https://github.com/benbjohnson/clock.

It is known to have issues and is not actively maintained,
here's a short overview:

gofrs/help-requests#37

There are other alternatives, and I tried a few of them,
but for some reason they don't seem to work for the tests I wrote:

https://github.com/derision-test/glock
https://github.com/microsoft/clock
@yrashk yrashk mentioned this issue May 21, 2021
Merged
yrashk added a commit to yrashk/bpxe that referenced this issue May 21, 2021
@yrashk
Problem: timer events are sent manually
97ffa84 
For the time being, all timer events are being sent
manually in tests. This is not enough for a functioning
BPMN engine.

Solution: introduce `timer` package

This is something to be used by the engine initiate timer
events. It's not yet integrated into the engine.

Speaking of the mock time implementation, and picking
https://github.com/benbjohnson/clock.

It is known to have issues and is not actively maintained,
here's a short overview:

gofrs/help-requests#37

There are other alternatives, and I tried a few of them,
but for some reason they don't seem to work for the tests I wrote:

https://github.com/derision-test/glock
https://github.com/microsoft/clock
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@adamdecaf @cristaloleg @joeblubaugh