Kris Leech
Kris Leech
@hamadmj I will, if noone else does, but I can't give you a date, your welcome to submit your code as a PR (with failing spec) and I will have...
@hamadmj Does you `unpublish_event` on your fork work? https://github.com/hamadmj/chalk_dust/commit/490f6a5868015a99fa64a017aab2e1d1471fbdd9
Thanks for your work on this. Have you been running this in production using 3.x? Do we know this still works with Ruby 2.6 and 2.7 in production? What are...
Let's drop support for 2.6 and I'll bump the major version. Would you mind updating this PR to remove the commit which adds `ruby2_keywords` and we can do a release....
It would be great if someone could look in to a PR for this. I also not familiar with the problems with `Thread.current` and fibers.
> This approach still fails in one case - when you call to_s on an anonymous class, you get a name like . I guess the problem is the `xxxxx`...
I'd love to get Ruby 3.0 support in Wisper. But it would need to be backwards compatible. Otherwise we would need to release a new major version dropping Ruby 2.x...
We can do a major version release which drops support for 2.6, we need to document it in the CHANGELOG, that it is a breaking change.
That's a great article. Which PR is it that is not part of a release?
The PR was https://github.com/krisleech/wisper/pull/181 There was no entry in CHANGELOG which is why it hasn't been released.