wxiaoguang

Fix #30992

Data race during testing

3

``` === TestOrgProjectAccess (tests/integration/org_project_test.go:17) ================== WARNING: DATA RACE Read at 0x000008956640 by goroutine 272626: code.gitea.io/gitea/models/unit.Type.UnitGlobalDisabled() /home/runner/work/gitea/gitea/models/unit/unit.go:170 +0x257 code.gitea.io/gitea/models/repo.getUnitsByRepoID() /home/runner/work/gitea/gitea/models/repo/repo_unit.go:331 +0x230 code.gitea.io/gitea/models/repo.(*Repository).LoadUnits() /home/runner/work/gitea/gitea/models/repo/repo.go:361 +0xa7 code.gitea.io/gitea/models/repo.(*Repository).GetUnit() /home/runner/work/gitea/gitea/models/repo/repo.go:435 +0x46 code.gitea.io/gitea/models/repo.(*Repository).IsTimetrackerEnabled() /home/runner/work/gitea/gitea/models/repo/issue.go:35 +0x5e code.gitea.io/gitea/models/issues.(*Issue).IsTimetrackerEnabled()...

PackageDescriptor.Metadata might be nil (and maybe not only for maven). This is only a quick fix. The new `if` block is written intentionally to avoid unnecessary indenting to the existing...

Fix "force private" logic

2

When creating a repo, the "FORCE_PRIVATE" config option should be respected, `readonly` doesn't work for checkbox, so it should use `disabled` attribute.

When comparing files between the base repo and forked repo, the "blob excerpt" link should point to the forked repo, because the commit doesn't exist in base repo. Thanks to...

Fix project column title overflow

1

By the way: * Re-format the "color.go" to Golang code style * Remove unused `overflow-y: scroll;` from `.project-column` because there is `overflow: visible`

[Bug] Safari: non-https site reports `undefined is not an object (evaluating 'navigator.clipboard.write')`

1

### Reproduction Steps * Use monaco-editor on a "http" site (v0.48.0), (do not use localhost, use local IP like `http://192.168.1.20`) * Use Safari to open the page, input anything *...

Fix missing memcache import

2

Regression of #30417, the "memcache" import was not kept by mistake. Fix #31102

Thanks to @graelo and @silverwind for figuring out the problem. Fix #31101