Homepage (for you) section is broken

[remahmoud]

Select Topic Area

Bug

Body

[samanyuneelson]

same for me (only on smaller screens)

[torn4dom4n]

It happens on both my laptop and my phone.

[remahmoud]

they fix the bug now 👍

[Nukealbert]

Bug is still coming to my home screen

[remahmoud]

@Nukealbert i think it's browser cache you can refresh the cache by Ctrl+F5

[saxbophone]

@Nukealbert i think it's browser cache you can refresh the cache by Ctrl+F5

I'm doing Cmd + Shift + R for force-refresh with Chrome on Mac and the layout issue is still persisting, are you sure it's been fixed?

[remahmoud]

@saxbophone I think not all the servers have been updated, because the problem has been fixed with me.

[saxbophone]

@saxbophone I think not all the servers have been updated, because the problem has been fixed with me.

Ah, gotcha, thanks! I even tried restarting my browser and still got the glitch, so I think you're probably right, we just have to wait for the change to propagate.

[saxbophone]

Can confirm that I get the same issue:

[Kreuger]

I thought this was a Firefox issue. Clearing the cache didnt help me.

[Newbie012]

Broken on mobile

[ghost]

Also broken here clear cache don't fix (maybe a propagation of the fix problem).

[davidf9265]

Same for me, any size of screen. Issue seems to be related with my specific content (compared with my friend feed and bug didn't appear on his account). Seems to be easy to fix, container styles appear not to be very responsive or relative.

[tarikjabiri]

Same here

[remahmoud]

The bug has not been fixed yet 😕

[lodembeep]

Don’t tell me that people at microsoft are unable to fix a simple frontend issue …

the bug is still live on mobile (ios)

[saxbophone]

I can confirm that the issue still persists for me. After 3 days, I don't think it's a cache propagation issue. May be more likely that manifestation of the bug depends on what content is displayed on the page, hence why some users see it and others don't:

[ghost]

After 48 hours, it is neither ISP nor CDN or cache

IT seem you clearly don't know how cache of this size do work and how many time it can remain in the worse case ...

[lodembeep]

IT doesn’t matter since they must be standard …

[ghost]

IT doesn’t matter since they must be standard …

OH god yet another i know everything that now nothing and talk about standard i'm out

[saxbophone]

Please stop arguing about which of you is more knowledgeable about ISPs, CDNs and caching. Most people are reading here to focus on the issue at hand.

[lodembeep]

IT doesn’t matter since they must be standard …

OH god yet another i know everything that now nothing and talk about standard i'm out

…

[saxbophone]

@davidjarzebowski Any chance we can get an update from Github about whether or not youse are aware of this UI issue?

[ghost]

Do you have a source for that? It was claimed earlier that it had been updated and yet it's been three days with no change for some of us. Seems an awfully long propagation time, no?

yes my own use on my vpn in hertzner in germany (but i cannot talk about all server in all EU)

I meant, do you have a source with positive confirmation from Github that they've had an issue and rolled out a fix (I mean like a bugfix announcement or something, not first-hand experience, though your experience is noted).

ah that no, but since many user had the problem and it's fixed (and i do not think it's fixed itself), i guess someone have fixed it, (or unbroken it (depending of what's the bug is))

but i do think they will do a post mortem once fixed (if it's a bug comming from them ?)

[ghost]

Still not fixed/propagated

not because it's not fixed for you that it's automatically means that all EU is broken ya know ?

[saxbophone]

Thanks for confirming that —the reason I ask is because it's clear that some people are still experiencing the bug, others not, and I wanted to know if the claim that it had been fixed, was based on an assumption based on experience, or from some press release of some kind from GH. Anyway, it's still broken for some of us and not for others! 😅 Have a good night all, hopefully David can enlighten us about what the ding-dang-diddly-doo-glum-fiddle-dosh is going on! ☺️

[lodembeep]

GN.
Was fun to argue with you @BirdInFire

[queenofcorgis]

@saxbophone thanks for posting, I totally understand that this is frustrating, but please refrain from tagging individual GitHub staff members for updates as they may not be the best point of contact and it goes against the spirit of our Code of Conduct .

[TheMonDon]

I am also having this issue, thought I was the only one.

[ghost]

No we (nearly) all had it, but some of us already have received (we guess) a fix (since it work again), so normally (if it's really fixed) must come to you too soon.

[Caballero-Arepa]

Same here

[queenofcorgis]

Hi there from GitHub 👋🏼 we are tracking this internally and investigating further. We appreciate your patience in the interim. I'll share an update here when I have one. Thank you all for your reporting, screenshots, and additional input.

[saxbophone]

@XxSonicGhostxX I think you replied to the wrong email thread bud

[remahmoud]

@XxSonicGhostxX you at the wrong place 👎

[saxbophone]

To be clear, people are criticising your posts because you seem to be talking about something completely unrelated to this Github discussion thread, about which you are getting emails about updates to because you commented on it some days ago. If you don't want to participate in this discussion or receive updates, you can click the unsubscribe link in the email notifications you get.

For reference, this thread is located at: https://github.com/orgs/community/discussions/55493

Hopefully, if you have a look at what we can see on our end, you can appreciate why your posts come across as spam as you seem to be asking questions about something completely unrelated to what this discussion thread is about (it's about a UI bug in Github).

If you've got general issues with your Github account, Github Support are the ones to contact, not this place (this is just a discussion thread among ordinary users).

[SunderB]

I can also confirm this has occurred to me on multiple devices (Safari on iPad & Firefox for Android). On phones it is basically unusable.
Here's a screenshot on the iPad

'Following' does not have this issue.

[pachico]

Same for Brave.
Is this a way to force people to install the mobile app?
Because that's what I had to do to have any readability.

[alflanagan]

Seeing this on 5/23/2023 on a fresh load of the page in Safari, on a Mac M1 notebook.

[saxbophone]

Don't look now, but it looks like it's fixed for me! :)

[queenofcorgis]

Confirming that this has been investigated and resolved. Please do let us know if you're continuing to encounter any issues.

[remahmoud]

Thanks 👍

[queenofcorgis]

Thank you @remahmoud and everyone else for reporting 🙇🏼‍♀️ !