Skip to content
This repository was archived by the owner on Jan 30, 2025. It is now read-only.
This repository was archived by the owner on Jan 30, 2025. It is now read-only.

Deadlock when emitting and processing events #553

@ankur22

Description

@ankur22

The ordering of events that are emitted is sometimes lost due to the use of the goroutine during the emit to the handlers.

This was found to eventually cause a deadlock in cloud runs.

To overcome this issue we tried to remove the goroutine, but the use of buffered channels didn't help in reducing the possibility of other deadlocks.

We still need to find a robust and maintainable solution whereby the order of the emitted events is somehow kept when the event is emitted to the handlers.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingeventsCDP or internal events related.nextMight be eligible for the next planning (not guaranteed!)

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions