@phikai (this issue can be closed)

Related to https://github.com/serde-rs/serde/issues/723

This seems to work now. I assume something was fixed and updated after mentioning it in the support room.

It still takes a little while to load but that's just how Element is.

Unable to view room when not signed in

Reproduction instructions

1. Open a new incognito window
2. Visit https://app.gitter.im/#/room/#FreeCAD_FreeCAD:gitter.im
3. Wait a long time and see the "Your Element is misconfigured" screen
4. Uncaught (in promise) ReferenceError: Cannot access 'V' before initialization errors in the console

Your Element is misconfigured

Unexpected error preparing the app. See the console for details.

Uncaught (in promise) ReferenceError: Cannot access 'V' before initialization
    at Object.J (init.js:1:870139)
    at b.start (ReadyWatchingStore.ts:38:30)
    at get instance (WidgetLayoutStore.ts:71:35)
    at ./react-sdk/src/stores/widgets/WidgetLayoutStore.ts (WidgetLayoutStore.ts:526:48)
    at u (bootstrap:19:32)
    at ./react-sdk/src/utils/WidgetUtils.ts (init.js:1:2222865)
    at u (bootstrap:19:32)
    at ./react-sdk/src/stores/ActiveWidgetStore.ts (init.js:1:2009328)
    at u (bootstrap:19:32)
    at ./react-sdk/src/stores/WidgetStore.ts (init.js:1:2036417)

I also had this but eventually it loaded after a minute or two (crazy 🤯). Signed in with GitHub in Chrome.

Also seeing #18 (closed) for reference

Unable to view room when not signed in

Reproduction instructions

1. Open a new incognito window
2. Visit https://app.gitter.im/#/room/#FreeCAD_FreeCAD:gitter.im
3. Wait a long time and see the "Your Element is misconfigured" screen
4. Uncaught (in promise) ReferenceError: Cannot access 'V' before initialization errors in the console

Your Element is misconfigured

Unexpected error preparing the app. See the console for details.

Uncaught (in promise) ReferenceError: Cannot access 'V' before initialization
    at Object.J (init.js:1:870139)
    at b.start (ReadyWatchingStore.ts:38:30)
    at get instance (WidgetLayoutStore.ts:71:35)
    at ./react-sdk/src/stores/widgets/WidgetLayoutStore.ts (WidgetLayoutStore.ts:526:48)
    at u (bootstrap:19:32)
    at ./react-sdk/src/utils/WidgetUtils.ts (init.js:1:2222865)
    at u (bootstrap:19:32)
    at ./react-sdk/src/stores/ActiveWidgetStore.ts (init.js:1:2009328)
    at u (bootstrap:19:32)
    at ./react-sdk/src/stores/WidgetStore.ts (init.js:1:2036417)

My comment doesn't indicate that this can be accomplished by the user themselves.

The extension marketplace in the Web IDE is disabled. According to these docs it's possible to enable the extension marketplace (Preferences -> Integrations -> Enable extension marketplace -> I understand -> Save changes) but this option isn't available on GitLab.com probably because the feature flag isn't turned on.

In whatever manner the controls can exist, having a non-technical user go through convoluted instructions to enable these controls isn't amazing.

Thank you @laurenbarker and @mpenagos-ext 🦌

I was browsing my old blog post and noticed that the content is cut-off about a quarter of the way through (page content HTML is not even on the page).

You can see the full blog post still exists in the repo so it seems to be a CMS/build issue.

What is/are the relevant URL(s)

https://about.gitlab.com/blog/2018/05/30/journey-in-native-unicode-emoji/

Briefly describe the bug

The blog post cuts off a quarter of the way through the content.

Notice the content is cut-off in the middle of a table at Full font-stack | Small emoji font-stack

This is a recent regression with the new look of blog posts.

If possible, please specify how to reproduce the bug

Just visit the page and notice the content is cut-off in the middle of a table

Please provide any relevant screenshots or screencasts

What is your window size, browser, operating system, and versions

• Chrome Version 119.0.6045.159
• Firefox 119.0.1 (64-bit)

What computing device are you using?

Linux Desktop (Manjaro, Arch-based with XFCE)

What type of input are you attempting to use?

Webpage interactivity is often tied to a specific device event.

• Touchscreen
• Touchpad
• Mouse click
• Mouse click and drag
• Scrollwheel
• Keyboard
• Stylus
• Other (please specify)

Have you tried a fresh incognito window? Could this be related to cookies or account type/state?

• I tried a fresh incognito window & it had no impact.
• The problem goes away when using an incognito window.
• The problem only happens when certain cookies are set to a specific value (please specify below).

Please list any browser plugins you have enabled

Why do we ask for this? Certain website bugs may be caused by plugins. For example: Adblock, noscript, ghostery, safe browsing.

(not relevant, reproducible in multiple browsers, incognito, etc)

Are you blocking javascript or any other resources?

Javascript is needed for certain website functionality.

• I AM blocking javascript or other resources.
• I am NOT blocking javascript or other resources.

What is your geographic location

Why do we ask for this? Certain bugs may be geographically related. For example, if you're in the European Union, it could be related to GDPR policy and cookies.

United States

What type of network are you connected to?

Type

• Wired
• Wifi
• Cellular (4G, 5G, etc)
• Satellite
• Other

Location

• Home
• Workplace
• Travel facility (hotel, airport, conference center, etc)
• Public venue (restaurant, library, cafe, etc)
• VPN
• Other

Hardware

• I am behind a network security appliance such as a firewall
• I am using a pi-hole or other hardware-based traffic blocker
• Other

/cc @gl-website

I'm not sure if the issue still exists.

But my use case is gone since Gitter fully migrated to Matrix and I no longer work at Element.

Originally tracked by webapp#2613

Transfer GSuite account from troupe.co to gitter.im. Currently we use troupe.co as the primary address and gitter.im is the verified alias.

• Nowadays, we only really use email and the aliases
• We no longer have any Android apps in the Play Store to worry about

Do we need to just change the primary domain?

• https://support.google.com/a/answer/7009324?hl=en
• https://admin.google.com/ac/domains/manage?action_id=CHANGE_PRIMARY_DOMAIN

Todo

• Do we need to worry about SSO logins? Will they still work after we change the domain?
  • Yes, not all sites play well with the migration and it's best to change the email over to something you control in the mean time.
  • Switch all of the Gitter accounts over to @gitter.im emails instead of the @troupe.co domain.
    • You can see which sites are being signed in with at https://myaccount.google.com/permissions
  • https://webapps.stackexchange.com/questions/119369/changing-primary-domain-in-g-suite-and-access-to-other-google-services
  • https://www.reddit.com/r/gsuite/comments/kv6srs/changing_primary_domains_trouble_with_sso_eg_slack/
  • https://www.reddit.com/r/gsuite/comments/gyj6nf/oauth_history_and_changing_primary_domain/
  • http://pomba.net/2021/01/migrating-primary-domains-in-gsuite-google-workspace-an-epic-odyssey/
• Change the primary domain for GSuite from troupe.co to gitter.im
• Archive and backup any Google Drive docs (haven't needed anything here in years)

Switched the primary domain over to gitter.im ✅

A bunch of 503 Service Unavailable for the https://gitter.ems.host/_matrix/client/... type requests? That would definitely be the cause of it not loading anything.

It would be nice if HTTP requests were included in rageshake logs to get a clearer picture. Can you share a screenshot of the network panel and some URL's that are giving you a 503? (be sure not click on a request and leak your access token)

Looking at Grafana, I don't see any 503 errors for the past month from Synapse itself (the homeserver). So I'm a bit confused on what you're seeing and would have to be from another layer.

Grafana query

sum(increase(synapse_http_server_response_time_seconds_bucket{code="503",le="+Inf",index=~"$index",instance="$instance"}[$bucket_size]))

Still loading after three hours.

What account are you using (what's your MXID)?

Are you using https://app.gitter.im/ ?

Perhaps it is some issue in your network or browser blocking certain requests? Do you know how to open the browser devtools and see what network requests are going on? Is there anything of interest (any long-running or failed requests)?

The gitter.im homeserver looks like it's running fine.

Is there any means of speeding it up?

No, if it's a /sync problem. But 3 hours seems too long in any case so I suspect there is something else going on.

@zerophase It's a little unclear what you mean by "Gitter" and "Element". https://app.gitter.im/ is just a Gitter branded version of Element Web and if you downloaded Element Desktop, it's using the same Element Web core. Can you clarify?

Are you signed into the same account when you try with various clients?

If you have an especially large account and haven't used it in a while like you mentioned, it may take a while to sync. I suspect if your account syncs fine with another client, it will sync fine with https://app.gitter.im/ and maybe the server was just working on your response behind the scenes and by the time you tried another client, it finally was responding.

There are various references across the internet about being able to access https://dashboards.gitlab.com/

One last thing: our Grafana dashboards are open, so if you're interested in digging into our metrics in more detail, visit dashboards.gitlab.com and explore!

-- https://about.gitlab.com/blog/2018/10/11/gitlab-com-stability-post-gcp-migration/#tldr-conclusion

Other references:

• https://grafana.com/blog/2019/06/24/a-look-inside-gitlabs-public-dashboards/
• https://twitter.com/sytses/status/1242621522180583424
• https://news.ycombinator.com/item?id=28463325

But when I try to visit https://dashboards.gitlab.com/ now, it just gives a DNS name not resolved error.

Did this change with the GitLab IPO on 2021-10-14? Why are the dashboards no longer public?