Skip to content
This repository has been archived by the owner on Feb 3, 2025. It is now read-only.

Unsafe aliasing in rust after adding first federation #933

Open
TonyGiorgio opened this issue Jan 3, 2024 · 1 comment
Open

Unsafe aliasing in rust after adding first federation #933

TonyGiorgio opened this issue Jan 3, 2024 · 1 comment
Assignees
Labels
bug Something isn't working fedimint

Comments

@TonyGiorgio
Copy link
Contributor

TonyGiorgio commented Jan 3, 2024

recursive use of an object detected which would lead to unsafe aliasing in rust

I think this is because how I'm swapping in GlueDB after it inits a federation for the first time if none existed. Doesn't seem to hurt anything but probably not safe. A better approach would be to empty init GlueDB but do not start it until a federation is added.

@TonyGiorgio TonyGiorgio added bug Something isn't working fedimint labels Jan 3, 2024
@TonyGiorgio TonyGiorgio self-assigned this Jan 3, 2024
@TonyGiorgio
Copy link
Contributor Author

This is happening somewhere in FederationClient::new but only when adding for the first time. But it's happening either kind of inconsistently or the error log is showing up in different places sometimes. Hard to tell but nothing important I think. Postponing for later, nothing is presenting itself as a problem.

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
bug Something isn't working fedimint
Projects
None yet
Development

No branches or pull requests

1 participant