Greg Slepak

Not sure yet if this should be closed, re-opening automatic close by GH

Update: This problem is still happening, because `giAcceptGroupInvite` eventually calls `giCheckIfJoinedChatroom` via `giLogin` => `cy.giCheckIfJoinedGeneralChatroom(username)` => `cy.giCheckIfJoinedChatroom(CHATROOM_GENERAL_NAME, username)`. And we have this call in `user3 joins the ${groupName1} group and...

This shows a comparison of a passing (left) and failing (right) build, suggesting that either the last two messages (u2 and u3) are reversed, or the u3 message is missing,...

Because this heisenbug is such a persistent problem, I've commented out the test as a temporary measure until someone is able to figure it out: ```js cy.getByDT('conversationWrapper').within(($el) => { if...

It turns out commenting that out in #2280 just leads to a different, related heisenbug!  I attempted a fix, which [didn't work](https://github.com/okTurtles/group-income/actions/runs/10230030171/job/28304488155), so...

Possibly related heisenbug that appears when all of that code is commented out [in this build](https://github.com/okTurtles/group-income/actions/runs/10253330956/job/28365706772):  Here's the video for this one: https://github.com/user-attachments/assets/49b45c88-afb4-4921-8d8d-25051d4dda31...

And yet a different one, also in group-chat, this time *with [video from Cypress Dashboard](https://cloud.cypress.io/projects/q6whky/runs/2890/test-results/8af7d000-7dd9-413c-a9e6-b959450e9498/video?actions=%5B%5D&browsers=%5B%5D&groups=%5B%5D&isFlaky=%5B%5D&modificationDateRange=%7B%22startDate%22%3A%221970-01-01%22%2C%22endDate%22%3A%222038-01-19%22%7D&orderBy=EXECUTION_ORDER&oses=%5B%5D&specs=%5B%5D&statuses=%5B%7B%22value%22%3A%22FAILED%22%2C%22label%22%3A%22FAILED%22%7D%5D&testingTypesEnum=%5B%5D&utm_source=github)*! 

Might've been fixed by @corrideat in #2294

@corrideat while I could add these to reverse proxy config, that would mean that others who are running Group Income might not get these headers as other servers could be...

After reloading the chatroom it's now correctly showing up on the PWA 🤔