Frühere Suchanfragen
Suchoptionen
Verwaltet von:
Anoxinon e.V. 
Hey everyone, we apologize for the current unexpected downtime.
We have had a long-standing issue where certain data could not be stored properly. For example, Git allows users to have both a main and a MAIN branch (different casing), but Codeberg could not store it, because our database was case-insensitive.
We have been preparing and testing a fix (which is currently converting the database tables). However, we missed that certain operations would fail during the migration.
…
… To prevent any damage and inconsistencies because of failing queries, we have temporarily disabled access to Codeberg.org while the conversion is running.
We don't have a good estimate about how long this will take, but the largest tables are converted and we expect the operation to complete within some minutes.
We apologize for the oversight and the interruption to your workflows. Thank you for your patience and support.
We are back online. I hope you all enjoyed the break.
@Codeberg Thanks to the sysadmin team for the work you do, and for being so transparent! :)
@Codeberg As Dale Cooper would say: "It was a damn good coffee" that I had during this little oopsie :)
@Codeberg danke für euren Einsatz!
@Codeberg Damn, I missed it ;P
Thanks for the detailed update 
@Simx72 10/10 for the effort ~n
@Codeberg 
I just thought immediately or i'd forget it
@Codeberg Congratulations for fixing the outage faster than #Bitbucket, which is still down 
@Codeberg is Codeberg pages down currently ?
@GreyLinux
I am having issues cloning and fetching... Please note I have nothing to commit at present, so have not tested pushing
@Codeberg
I believe you are using MySQL for your back end, and if so, you can set the entire database or entire tables to use case sensitive utf8.
IIRC you can use an ALTER statement to alter an existing database or table make it case sensitive
@nikatjef That's what we did, but the operation took 5 to 10 minutes on some tables.
However, some queries where failing when they compared or joined across tables with different collation while the conversion was ongoing.
@Codeberg as always, you guys work really hard at doing maintenance work while also not making it take a long time, i mostly dont use codeberg often so the downtimes i would never or rarely notice