this post was submitted on 12 Jun 2023
117 points (100.0% liked)
Beehaw Support
2798 readers
1 users here now
Support and meta community for Beehaw. Ask your questions about the community, technical issues, and other such things here.
A brief FAQ for lurkers and new users can be found here.
Our September 2024 financial update is here.
For a refresher on our philosophy, see also What is Beehaw?, The spirit of the rules, and Beehaw is a Community
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Thanks for all the hard work. It's seen and appreciated.
On the existing bugs/issues, are these issues with the Lemmy code in general or with the specific implementation here? Do you all need help triaging or finding root cause of issues? I am a test engineer and might be able to help out with digging into finding problems.
We will post in beehaw support when we have specific issues, we did this a few days ago and there's already merge requests to fix it
I'll keep a closer eye on things and maybe I can lend a hand for future problems. Glad they are getting addressed!
There is, certainly, a memory leak somewhere in the Lemmy software. @[email protected] has been trying to identify the precise location(s).
I'm sure the Lemmy developers would like help triaging and finding root cause of issues! Here's where you can find their repos : https://github.com/LemmyNet/
They're Lemmy-wide I believe. Have a second account on lemmy.world and I've seen at least the first and third bugs happen there too.