EventBus icon indicating copy to clipboard operation
EventBus copied to clipboard

[Go] Lightweight eventbus with async compatibility for Go

Results 28 EventBus issues
Sort by recently updated
recently updated
newest added

See [golang mutexes aren't recursive / re-entrant](https://nirandas.com/blog/golang-mutexes-arent-recursive-re-entrant) `Bus.Publish(...)` method locks mutex and calls callbacks under lock, so any access to the bus in callback will cause deadlock. The following example...

In line 141 `func Publish` ``` // Publish executes callback defined for a topic. Any additional argument will be transferred to the callback. func (bus *EventBus) Publish(topic string, args ...interface{})...

Hello, Thank you for this beautifully simple and functional library. Can you please release a version so that we can use it instead of master? This helps in shielding our...

Fix #35 Fix #52 This PR does not holds lock during whole publish process. It saves from deadlocks when callbacks also trying to publish something or manage subscription on the...

### Current behaviour The `main` function Publish an `event1` and relative handler of `event1`, publish `event2`, but the `event2` handler is not calling, and the program is not exited. ```golang...

For those of us using go modules, it would be nice to support it. Pretty straightforward here since this is only one package. BTW, the go version number doesn't mean...

Because of wg's counter can't be a negative number, if call Wait() and then call Add(1) before Wait() complete, it will throw a panic "WaitGroup is reused before previous Wait...

Hi! My issue is the following: I'm currently implementing a connection between 2 different code into the same computer. So I have a server and a client. I run the...

SubscribeOnce removal was not reliable in the case that more then one SubscribeOnce handler is registered. The problem is simple to reproduce by running the changed unit test against the...