Page 1 of 1

BGforge Hive server error

Posted: Mon Jun 17, 2024 10:01 am
by TungPham
Greetings,

I am a member of VI translation team, and today we met this issue quite often.

Image
Image
Image

Method of reproduce: Adding a female version, translating, editing, or doing anything else will basically cause this problem.

It was previously difficult for us to work on BGforge Hive because of the current poor connection, but this issue only started to arise today.

Thanks in advance.

Re: BGforge Hive server error

Posted: Mon Jun 17, 2024 2:12 pm
by Magus
I think you managed to trigger a weblate bug, it's been churning some data all day long today.
Nevertheless, for investigataion I need actual urls, actual words entered, so I could go and reproduce it myself.
After a restart, it's calmed down a bit, you can check it out.

Whatever you mean by "current poor connection", I have no idea, and won't have any idea unless you provide details. As far as I know, it works perfectly (other than today's issue).
 

Re: BGforge Hive server error

Posted: Tue Jun 18, 2024 7:49 am
by TungPham
Thank you for the response.

The issue just happened again, in this link.

And this is the string I was translating when the message appeared.

For the "poor connection", my country is currently having some cable issues and our connection to the outside is quite slow.

Edit: Actually, today this issue happens every time I tried to save a female version:
Server ErrorThe server had serious problems serving your request, and this error has been recorded as 618541748edc43cbb2ce6af4ea939f92.

in this string.

Edit 2: I got a workaround by adding the female version, go back to male, then Save and continue will work.

Re: BGforge Hive server error

Posted: Wed Jun 19, 2024 7:58 am
by Magus
OK, I don't see any errors in the last day, but they start to appear again, feel free to let me know.

Re: BGforge Hive server error

Posted: Sun Jun 23, 2024 1:16 am
by Magus
I see some intermittent errors (a few per day). I think those are actually bugs, but I'm afraid we're too far behind upstream (v4 vs v5) to submit them. Would need to upgrade first, and that's not an easy task.
So, for now, if they are not overly disturbing, probably easier to just let it be.