duplicate key value violates unique constraint "contentcuration_contentnode_pkey"

[sentry]

Sentry Issue: STUDIO-EDT

duplicate key value violates unique constraint "contentcuration_contentnode_pkey"
DETAIL:  Key (id)=(5af2bd99d8904611a9e9e111797c3075) already exists.

[sentry]

Sentry issue: STUDIO-EE0

[rtibbles]

From local testing this seems to be happening because when users have more than one tab open, the leader election is not properly causing syncing to happen from only one tab.

[rtibbles]

This seems to be caused by this issue in leader elections: https://github.com/pubkey/broadcast-channel/issues/414 although it seems to manifest particularly quickly in our case.

[sentry]

Sentry issue: STUDIO-EJA

[sentry]

Sentry issue: STUDIO-EK3

[sentry]

Sentry issue: STUDIO-EK4

[sentry]

Sentry issue: STUDIO-EK5