Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

the great static mut massacre #1

Open
lesterrry opened this issue Apr 10, 2022 · 5 comments
Open

the great static mut massacre #1

lesterrry opened this issue Apr 10, 2022 · 5 comments
Labels
bug Something isn't working PAS Probably already fixed & now testing

Comments

@lesterrry
Copy link
Owner

Yes. I'm a dumbass. Yes, this whole thing runs on a single static mut variable. Yes, of course it created problems. I just don't know how to make things any other way.
Anyways, here's the only reasonable thing I've found online

@lesterrry lesterrry added the bug Something isn't working label Apr 10, 2022
@lesterrry
Copy link
Owner Author

What if I just kinda wrap every APP mutation in a reasonable delay?

@lesterrry
Copy link
Owner Author

I really hope this may now be closed...

@lesterrry lesterrry added the PAS Probably already fixed & now testing label Apr 10, 2022
@lesterrry
Copy link
Owner Author

Yay bye baby

@lesterrry
Copy link
Owner Author

yay... segmentation faults are still with us....

@lesterrry lesterrry reopened this Apr 11, 2022
@lesterrry
Copy link
Owner Author

lesterrry commented Apr 11, 2022

Ok so our main goal is to ensure the conversations stay stable, logging in/tying schemes are second thing.

  • Check sending queue safety
  • Find any other APP calls and restrict if possible

lesterrry pushed a commit that referenced this issue Apr 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working PAS Probably already fixed & now testing
Projects
None yet
Development

No branches or pull requests

1 participant