dminca commented 2022年08月10日 21:42:12 +02:00

Steps to reproduce

1. Login on Codeberg
2. Use it intensively for 5-10 minutes (go through repos, navigate to all sorts of pages)
3. Open a random repo

What you see

4. The page is not loading

What you should see

4. Loaded Codeberg page

Details

I've reproduced this issue on

• MacOS Monterey 12.5
• Safari Version 15.6 (17613.3.9.1.5)
• No browser extensions installed

In the attached screen recording you'll see that 3 resources, namely:

• icon_inverted.svg
• codeberg.js
• codeberg.css

are not loading properly.

Uploaded the video on PeerTube as well in case you can't watch the video:

📹 https://tube.tchncs.de/w/tVeci3TZEAE9cCWwGvmDE7

<!-- NOTE: If your issue is a security concern, please send an email to contact@codeberg.org (and if related to Gitea also to security@gitea.io) instead of opening a public issue. Thank you. Welcome to the Codeberg Community Tracker. This is the right place for bug reports, feature requests and feedback. It's the central place where we track progress and discuss, so please open issues here unless you are sure it's directly related to a specific Codeberg product and only some contributors there need to join the discussion. Easy rule: If you are unsure, report it here. When reporting bugs or asking for features in the software itself, please understand that Codeberg is a fork of Gitea. Please always check upstream (→ see FAQ) if your there is already an open issue. If not, you'd really help us if you could directly get in touch with the maintainers and open an issue here if you think a wider audience should know about that (e. g. when discussing hotfixes, backports or when discussing whether some feature should become part of Gitea or a Codeberg "add-on"). If you don't have a GitHub account, please mention this and we'll gladly forward your report to the Gitea maintainers. Thank you for reporting your findings and giving feedback on Codeberg. ## Some FAQ: ### What does upstream mean? Upstream refers to Gitea, the software Codeberg is built upon. If we ask you if you can report upstream, please visit https://github.com/go-gitea/gitea/issues and check for the bug there and report elsewise. It's usually good if the person interested in a feature or bugfix opens the request to react to questions and join the discussion. We would usually just fire the report, but won't find the time to properly react to that ... **If you do not have a GitHub account**, just tell us and we'll happily forward the report for you. ### I just noticed a typo in the sign_up / sing_up route when regis... No, this is not a typo, but intentional. It was a quick fix to avoid spammers targetting our instance and it actually worked out quite well to rename the route from sign_up to sing_up (few people notice, nice to see you have sharp eyes) ... we might have to take more effective countermeasures in the future, but for now we're actually quite good with that one ... ### How can I help? If you want to help improving Codeberg as a community home for software development, we'll gladly welcome your contribution. Check out the docs about improving Codeberg https://docs.codeberg.org/improving-codeberg/ and have a look at the open issues, especially those that are looking for contribution https://codeberg.org/Codeberg/Community/issues?state=open&labels=105 - some of them don't even require much coding knowledge. We are also happy if you forward bug reports to Gitea if the original author hasn't done that yet or hasn't got a GitHub account. --> # Steps to reproduce 1. Login on Codeberg 2. Use it intensively for 5-10 minutes (go through repos, navigate to all sorts of pages) 3. Open a random repo ## What you see 4. The page is not loading ## What you should see 4. Loaded Codeberg page # Details I've reproduced this issue on * MacOS Monterey 12.5 * Safari Version 15.6 (17613.3.9.1.5) * No browser extensions installed In the attached screen recording you'll see that 3 resources, namely: * `icon_inverted.svg` * `codeberg.js` * `codeberg.css` are not loading properly. Uploaded the video on PeerTube as well in case you can't watch the video: 📹 https://tube.tchncs.de/w/tVeci3TZEAE9cCWwGvmDE7

dminca commented 2022年08月10日 23:13:50 +02:00

Related to #640

Related to #640

fnetX commented 2022年08月10日 23:24:41 +02:00

Indeed, we're still facing a heavy performance issue with Codeberg Pages :-(

It's a little unfortunate that important Codeberg assets are served from our flaky tool (occassional temporary outages, usually only affecting a handful of requests, that is). OTOH it makes the issue a higher priority for us.

We're on it, but still trying many things to locate the issue.

Indeed, we're still facing a heavy performance issue with Codeberg Pages :-( It's a little unfortunate that important Codeberg assets are served from our flaky tool (occassional temporary outages, usually only affecting a handful of requests, that is). OTOH it makes the issue a higher priority for us. We're on it, but still trying many things to locate the issue.

jwildeboer commented 2022年08月13日 11:20:09 +02:00

I often experience this problem on codeberg.org itself.

If it gets stuck on Safari (which happens to me quite regularly, unfortunately), it is in my case ALWAYS

• codeberg.js
• codeberg.css
• icon_inverted.svg

that fail to get sent. Maybe this helps to find the root cause.

I often experience this problem on codeberg.org itself. If it gets stuck on Safari (which happens to me quite regularly, unfortunately), it is in my case ALWAYS * codeberg.js * codeberg.css * icon_inverted.svg that fail to get sent. Maybe this helps to find the root cause.

dminca commented 2022年08月13日 12:21:32 +02:00

Sometime emptying caches helps, but not always

image

Sometime emptying caches helps, but not always 

Gusted commented 2022年08月13日 12:54:12 +02:00

Hi everyone,

I don't have Apple/Safari myself, so this require some help from you people. If you open the Dev Tools(you want to open this before navigating to the site that has the non-loading assets) and then navigate to the "Network" tab and go to one the non-loading asset's request. Is there some indication which HTTP version is being used(either HTTP/1.1 or HTTP/2)?

Hi everyone, I don't have Apple/Safari myself, so this require some help from you people. If you open the Dev Tools(you want to open this before navigating to the site that has the non-loading assets) and then navigate to the "Network" tab and go to one the non-loading asset's request. Is there some indication which HTTP version is being used(either HTTP/1.1 or HTTP/2)?

jwildeboer commented 2022年08月13日 13:09:38 +02:00

icon_inverted.svg:

GET /logo-kit/icon_inverted.svg HTTP/1.1
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.6 Safari/605.1.15
Accept: image/webp,image/png,image/svg+xml,image/*;q=0.8,video/*;q=0.8,*/*;q=0.5
Accept-Language: en-GB,en;q=0.9
Connection: keep-alive
Accept-Encoding: gzip, deflate, br
Host: design.codeberg.org

codeberg.js:

GET /design-kit/codeberg.js HTTP/1.1
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.6 Safari/605.1.15
Accept: */*
Accept-Language: en-GB,en;q=0.9
Connection: keep-alive
Accept-Encoding: gzip, deflate, br
Host: design.codeberg.org

codeberg.css:

:method: GET
:scheme: https
:authority: codeberg.org
:path: /assets/codeberg.css
Cookie: _csrf=_Rsof-IFVkvT9Th3EwsD9BsnZY46MTY2MDM4ODE3NDgxNjAzMzY4Ng; i_like_gitea=478687e3ea5db1da; lang=en-US; gitea_awesome=jwildeboer; gitea_incredible=c00cdb136c42932457e4ca47145ff2da5d1043ec3d2613180d1b89a181681f39e5e658d7ca0f
Accept: text/css,*/*;q=0.1
Host: codeberg.org
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.6 Safari/605.1.15
Accept-Language: en-GB,en;q=0.9
Accept-Encoding: gzip, deflate, br
Connection: keep-alive

HTH

icon_inverted.svg: ``` GET /logo-kit/icon_inverted.svg HTTP/1.1 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.6 Safari/605.1.15 Accept: image/webp,image/png,image/svg+xml,image/*;q=0.8,video/*;q=0.8,*/*;q=0.5 Accept-Language: en-GB,en;q=0.9 Connection: keep-alive Accept-Encoding: gzip, deflate, br Host: design.codeberg.org ``` codeberg.js: ``` GET /design-kit/codeberg.js HTTP/1.1 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.6 Safari/605.1.15 Accept: */* Accept-Language: en-GB,en;q=0.9 Connection: keep-alive Accept-Encoding: gzip, deflate, br Host: design.codeberg.org ``` codeberg.css: ``` :method: GET :scheme: https :authority: codeberg.org :path: /assets/codeberg.css Cookie: _csrf=_Rsof-IFVkvT9Th3EwsD9BsnZY46MTY2MDM4ODE3NDgxNjAzMzY4Ng; i_like_gitea=478687e3ea5db1da; lang=en-US; gitea_awesome=jwildeboer; gitea_incredible=c00cdb136c42932457e4ca47145ff2da5d1043ec3d2613180d1b89a181681f39e5e658d7ca0f Accept: text/css,*/*;q=0.1 Host: codeberg.org User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.6 Safari/605.1.15 Accept-Language: en-GB,en;q=0.9 Accept-Encoding: gzip, deflate, br Connection: keep-alive ``` HTH

Gusted commented 2022年08月13日 13:41:36 +02:00

Thank you for that information, it's interesting it's using the HTTP/1.1 (So it's not trying to re-use an HTTP/2 connection, which is slow due to the workaround by #640). Does Safari by any chance have some kind of "Timings" tab? That should give some more pointers if the receiving or waiting part is slow.

image

Thank you for that information, it's interesting it's using the HTTP/1.1 (So it's not trying to re-use an HTTP/2 connection, which is slow due to the workaround by #640). Does Safari by any chance have some kind of "Timings" tab? That should give some more pointers if the receiving or waiting part is slow. 

jwildeboer commented 2022年08月13日 13:45:35 +02:00

As mentioned in #640 (comment) it gets stuck forever. the GET goes out and no reply ever comes back. I took that screenshot there after 90 seconds of waiting. Should it happen again, I will take a screenshot of the timing diagram too.

HTH

As mentioned in https://codeberg.org/Codeberg/Community/issues/640#issuecomment-583773 it gets stuck forever. the GET goes out and no reply ever comes back. I took that screenshot there after 90 seconds of waiting. Should it happen again, I will take a screenshot of the timing diagram too. HTH

Ghost commented 2022年12月24日 11:33:23 +01:00

Is this still an issue?

Is this still an issue?

fnetX commented 2022年12月24日 16:07:36 +01:00

I think the Gitea migration also fixed this instability. We can reopen if this reappears.

I think the Gitea migration also fixed this instability. We can reopen if this reappears.