Ibaraki DoujiOriginal post
Rank 5: Hypervisor
Follow up of https://discord.com/channels/564160730845151244/1549368393826705468
When testing 2.3.0 here is what i found
Bugs
API
- Gitlab/Gitea group/organizations projects cannot be used with VCS (see : https://discord.com/channels/564160730845151244/1551954715447787641 )
- Gitlab VCS events doesnt work (see : https://discord.com/channels/564160730845151244/1552055386092343347 )
Infra
- Clickhouse continuously growing in size
- Clickhouse High CPU Usage by default (see : https://discord.com/channels/564160730845151244/1548697030900187296 )
UI
- Gitlab Self-Hosted VCS shows gitlab.com URL in project settings
- When loading the console i see a 404 request going to
/v1/console/plansnot sure if it's supposed to be here. - In the functions/sites deployment, the active deployment shows "Global CDN" and "DDoS protection" which are cloud spacific
- In a functions/sites domains, there is a request going to
/v1/domainswhich is not supposed to be here
Others infos
- In 2.3.0 VectorsDB/DocumentsDB are not visible in the UI, it is intended and will be released in a later version once it's more stable. So i would recommend disabling embedding as well to free up some resources while thoses DBs are disabled.
- Firewall feature is not ready yet, it will be available in Self-Hosted tho we don't have an ETA yet
Workarounds
Clickhouse continuously growing
See : https://discord.com/channels/564160730845151244/1549798467491205260
Official fixes
-# none for now
-# I will update this message if i find more bugs or others people find some so we have kinda of a mega thread to resolve all issues in self hosted
Summary
The user reported bugs with the Self-Hosted 2.3.0 version and provided details about their issues. They later posted a follow-up confirming that the problems have been resolved, indicating that any necessary fixes or workarounds were found.