caojiafeng
caojiafeng
I just found out that one can `use FooBar` first to prevent the situation. ``` elixir defmodule FooBar do defmacro __using__(_) do quote do defoverridable Module.definitions_in(__MODULE__) Module.definitions_in(__MODULE__) |> IO.inspect end...
@edgurgel Here it is.
Thanks a lot! I followed your suggestion, commit and publish it back on flowScheduler, still get errors. I replace the `sink.store` with an non-interrupted `sleep(3s)`, while it's sleeping, I canceled...
Sorry for my pool expression. After subscribing to a kafka flux, the flux chain is running background. Some time later，user may want to stop the program through the subscription returned...
@OlegDokuka thanks for the link! The thread calling `cancel` and the thread committing offsets are running concurrently. I'm curious, If scheduler's thread is blocking on committing offset, and at the...
@OlegDokuka Thanks you very much! It's so so brilliant! Cann't wait to try it now!
The connectable flux and latch did works! However, one problem remains. After disposing kafka flux, it becomes inactive, and the commit mono will never returned, because the commit event is...
@OlegDokuka awesome! It's works perfectly now. I think I need to read into some reactor code to fully digest the solution.
Glad to see this! we at starcoin have been using 0x0000000...0000001 long time ago due to the same reason (0x1 can be confusing and only these special addresses are shortend)
Same problem here.