Eliminate Data Races from CwtchPeer / Profile #289

Closed
opened 2019-11-12 20:38:39 +00:00 by sarah · 1 comment
Owner

A result of the eventbus integration. We modify peer from 2 goroutines (the event bus handler and directly via the UI/interface)

We should move all updates/requests to the event bus as standard practice

A result of the eventbus integration. We modify peer from 2 goroutines (the event bus handler and directly via the UI/interface) We should move all updates/requests to the event bus as standard practice
sarah added the
bug
label 2019-11-12 20:38:39 +00:00
dan self-assigned this 2020-01-28 22:27:23 +00:00
Author
Owner

This has been fixed by various refactors over the last few months. If anything we are a bit too conservative on the locking now and most of the profile/peer interactions can be flattened or removed entirely. Closing in favour of new issues which can be logged as we discover them.

This has been fixed by various refactors over the last few months. If anything we are a bit too conservative on the locking now and most of the profile/peer interactions can be flattened or removed entirely. Closing in favour of new issues which can be logged as we discover them.
sarah closed this issue 2020-10-08 20:42:44 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cwtch.im/cwtch#289
No description provided.