6543

Results 676 comments of 6543

ok @sahinakkaya cache is now in place - you just need to handle the 102 http status responce by make a sleep and retry later again

![281956029-16c984c1-b77f-46c6-8f28-21a902e6abc6](https://github.com/go-gitea/gitea/assets/24977596/140ea07c-7694-4bdb-b6fa-948a3da8897a) we might even use a dedicated cache at this point ?!? as we do with repo archives -> I used the gitea repo to get this result

Just restart gitea to reset the cache

you are right 102 does invoke a second http call witch is 200. so we can not use that status :/ so I used `216` as it's unused as by...

102 had unexpected sideefects ... ... did chat about the status-code to signal things i guess wrapping it up in a dedicated response struct in body is a way to...

@sahinakkaya you might want to make the VUE code bit better ;)

@hazycora i did resolve the conflicts ... and if you make it a "profile overview" enhancement only e.g. remove the grid and do that in another pull. then we can...

Why not also add this filter option to repo projects?

please dont forcepush just merge target branch in and push new commits ontop to it we do squash-merges :)