| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Update misspell to 0.5.1 and add `misspellings.csv` (#30573) | silverwind | 2024-04-27 | 1 | -2/+2 |
| | | | | | | | Misspell 0.5.0 supports passing a csv file to extend the list of misspellings, so I added some common ones from the codebase. There is at least one typo in a API response so we need to decided whether to revert that and then likely remove the dict entry. | ||||
| * | Fix missed doer (#30231) | Lunny Xiao | 2024-04-08 | 1 | -3/+3 |
| | | | | | | Fix #29879 Co-authored-by: Giteabot <teabot@gitea.io> | ||||
| * | Even more `db.DefaultContext` refactor (#27352) | JakobDev | 2023-10-03 | 1 | -1/+1 |
| | | | | | | | | | Part of #27065 --------- Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> Co-authored-by: delvh <dev.lh@web.de> | ||||
| * | More `db.DefaultContext` refactor (#27265) | JakobDev | 2023-09-29 | 1 | -10/+10 |
| | | | | | | | | Part of #27065 This PR touches functions used in templates. As templates are not static typed, errors are harder to find, but I hope I catch it all. I think some tests from other persons do not hurt. | ||||
| * | Add context parameter to some database functions (#26055) | Lunny Xiao | 2023-07-22 | 1 | -1/+1 |
| | | | | | | To avoid deadlock problem, almost database related functions should be have ctx as the first parameter. This PR do a refactor for some of these functions. | ||||
| * | For API attachments, use API URL (#25639) | Lunny Xiao | 2023-07-10 | 1 | -5/+5 |
| | | | | | | | | Fix #25257 --------- Co-authored-by: Giteabot <teabot@gitea.io> | ||||
| * | Store and use seconds for timeline time comments (#25392) | 6543 | 2023-06-23 | 1 | -0/+12 |
| | | | | | | | | | | | | this will allow us to fully localize it later PS: we can not migrate back as the old value was a one-way conversion prepare for #25213 --- *Sponsored by Kithara Software GmbH* | ||||
| * | Add context cache as a request level cache (#22294) | Lunny Xiao | 2023-02-15 | 1 | -7/+7 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To avoid duplicated load of the same data in an HTTP request, we can set a context cache to do that. i.e. Some pages may load a user from a database with the same id in different areas on the same page. But the code is hidden in two different deep logic. How should we share the user? As a result of this PR, now if both entry functions accept `context.Context` as the first parameter and we just need to refactor `GetUserByID` to reuse the user from the context cache. Then it will not be loaded twice on an HTTP request. But of course, sometimes we would like to reload an object from the database, that's why `RemoveContextData` is also exposed. The core context cache is here. It defines a new context ```go type cacheContext struct { ctx context.Context data map[any]map[any]any lock sync.RWMutex } var cacheContextKey = struct{}{} func WithCacheContext(ctx context.Context) context.Context { return context.WithValue(ctx, cacheContextKey, &cacheContext{ ctx: ctx, data: make(map[any]map[any]any), }) } ``` Then you can use the below 4 methods to read/write/del the data within the same context. ```go func GetContextData(ctx context.Context, tp, key any) any func SetContextData(ctx context.Context, tp, key, value any) func RemoveContextData(ctx context.Context, tp, key any) func GetWithContextCache[T any](ctx context.Context, cacheGroupKey string, cacheTargetID any, f func() (T, error)) (T, error) ``` Then let's take a look at how `system.GetString` implement it. ```go func GetSetting(ctx context.Context, key string) (string, error) { return cache.GetWithContextCache(ctx, contextCacheKey, key, func() (string, error) { return cache.GetString(genSettingCacheKey(key), func() (string, error) { res, err := GetSettingNoCache(ctx, key) if err != nil { return "", err } return res.SettingValue, nil }) }) } ``` First, it will check if context data include the setting object with the key. If not, it will query from the global cache which may be memory or a Redis cache. If not, it will get the object from the database. In the end, if the object gets from the global cache or database, it will be set into the context cache. An object stored in the context cache will only be destroyed after the context disappeared. | ||||
| * | Move `convert` package to services (#22264) | KN4CK3R | 2022-12-29 | 1 | -0/+175 |
| Addition to #22256 The `convert` package relies heavily on different models which is [disallowed by our definition of modules](https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#design-guideline). This helps to prevent possible import cycles. Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> | |||||
 |
index : gitea.git | |
| Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD: https://github.com/go-gitea/gitea | www-data |
| summaryrefslogtreecommitdiffstats |