I’m getting intermittent access to the Wiki and MantisBT today.
One attempt might go through (with delayed response) while the next (a few seconds later) reports “Insufficient Storage”
This is annoying on the wiki. But a real deterrent to using the MantisBT system. (Mantis forgets the form contents on a failed commit. Going ‘back’ work inasmuch as it reloads the blank form from same URL. There is no restoration of cached data.)
# Insufficient Storage
The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request. There is insufficient free space left in your storage allocation.
Additionally, a 507 Insufficient Storage error was encountered while trying to use an ErrorDocument to handle the request.
Yes the *Broken project website URL" Error validation is related, but that was from “23 hours ago” and does not apply at this moment.
The important one for the Web component at the moment seems to be the “Could not merge the repository. Error” ?
Weblate could not merge upstream changes while updating the repository.
Rebasing (1/8)
dropping 8b5d43dc1f6a440679c45ffca9465933f7f0089f Translated using Weblate (Slovak) – patch contents already upstream
Rebasing (2/8)
dropping 67c867c6c6e71b94e1faf17e0f21270a7c08de8c Translated using Weblate (Russian) – patch contents already upstream
Rebasing (3/8)
Auto-merging lang/cs.json
CONFLICT (content): Merge conflict in lang/cs.json
error: could not apply bc3d21a… Translated using Weblate (Czech)
Could not apply bc3d21a… Translated using Weblate (Czech)
(1)
Typical workflow for fixing merge conflicts
The exported Weblate repository can be shallow by default, so this workflow works best from an up-to-date upstream checkout. Cloning from the exported Weblate repository or using an outdated upstream checkout can fail even when Weblate and upstream are in sync. See the FAQ below for details.
Open an existing checkout of the upstream repository or perform a fresh one.
Commit all pending changes in Weblate and lock the translation component.
wlc commit; wlc lock
Add Weblate exported repository as a remote.
git remote add weblate Making sure you're not a bot! ; git remote update weblate
Merge Weblate changes and resolve any conflicts.
git merge weblate/main
Rebase Weblate changes on top of upstream and resolve any conflicts.
git rebase origin/main
Push changes into upstream repository.
git push origin main
Weblate should now be able to see updated repository and you can unlock it.
wlc pull ; wlc unlock
Check the FAQ for info on how to resolve this.
Appeared 6/21/26, 3:35:21 AM, last seen 18 hours ago
I investigated and found add that on June 18, I accidentally clicked “squash & merge” instead of “rebase & merge” on a Weblate commit, which broke the sync.
Can you please reset the Web component on Weblate for me, so it syncs again?
That is possible but all changes made in Weblate since the merge conflict will be lost. If you want to go down that route I suggest manually merging the 8 commits in Weblate first.
I don’t have admin access to Weblate; if it’s possible to not discard them, that would of course be preferable. Too bad I only noticed after almost three months.
For example current traffic has been sitting at between 2 to 4 times normal for the last few days with the site working no issue; but spiking occasionally to 6 to 8 times normal traffic and that is when you would be getting that message; this last happened between 11am to 1pm yesterday Australian time; see image that also shows traffic is unfortunately increasing again in the last few hours but not as sharply but still causing the Error 507 for some users but not all users, so sorry nothing to do but wait for the AI bot traffic to pass again while it happens!
Not directly related but since last days (might be also linked with a web navigator update), via cloudflare DNS, it seems that they “sniff more” on client side (delay : few secondes, one maybe two) for some web sites with client side scripts. Just the feeling that they want to filter or generate a clean traffic cause of AI bots or attacks.
