Andrew Hawker

The scheduler runs in a separate thread and each invocation of each function that needs to be run is executed in a separate thread/process context (depending on the `ctx` param)....

@tomzhu6066 Yeah, I thought about this one a bit. I would _like_ to add a `name` parameter to the `@job` decorator. However, the corner I've painted myself into is how...

@MrMathias Thanks for the good question. I do agree that this has somewhat of a high astonishment factor. The work-around is `.job(second=0, minute=range(0, 60, 10))` but definitely a valid question...

FWIW, [this PR](https://github.com/ahawker/ulid/pull/476) contains an implementation which attempts to give you microsecond guarantees, instead of millisecond, and remain stateless. This does not address concerns of clocks moving backwards in time...

Some random thoughts: It's been ~6 years since I've written C# but I think I'm understanding what you've written :) That sounds similar to my implementation and what I found....

@vpelletier Thank you for taking the the time to do an in-depth review & feedback! Life's gotten a bit busy so it'll be a little slower to tidy this up...

I know https://github.com/ilevkivskyi/com2ann exists for converting py2 comment types to py3 but I am unaware of a tool that does the reverse. For reference, support for comment based types is...

Initial scaffolding and rudimentary benchmarks added in #10

My apologies for the delay, I missed the notifications for this issue. A few versions back, support for monotonic randomness was added to [ulid-py](https://github.com/ahawker/ulid). This made the randomness implementation pluggable...

Any action on this? I was seeing the same in `golang` multiple months back and basically made it a blocker for any long running process trying to embed/use chdb.