Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Javascript missing in 19.x and 20.x releases #1017

Closed
xvilo opened this issue Sep 18, 2023 · 8 comments
Closed

Javascript missing in 19.x and 20.x releases #1017

xvilo opened this issue Sep 18, 2023 · 8 comments
Labels

Comments

@xvilo
Copy link
Contributor

xvilo commented Sep 18, 2023

Hi, this morning I tried updating the chart for our deployment from 18.0.1 to the latest 19.x ánd 20.x chart releases. Updating from 23.3.1 to 23.6.1 and from 23.6.1 to 23.8.0.

However, from 23.6.1 and onwards I can't open serveral sections of the web interface due to missing javascript. An example is https://sentry.example.com/_static/dist/sentry/chunks/app_views_discover_index_tsx.6ed2f1bf1018c7e0321a.js ends-up on a 404 in browser and with curl:

$ curl -vvv https://sentry.example.com/_static/dist/sentry/chunks/app_views_discover_index_tsx.6ed2f1bf1018c7e0321a.js
*   Trying [xxxx:xxxxx:xxxx:xxxxx]:443...
* Connected to sentry.example.com ([2a01:7c8:e001:151::408d](xxxx:xxxxx:xxxx:xxxxx)) port 443 (#0)
* ALPN: offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-AES256-GCM-SHA384
* ALPN: server accepted h2
* Server certificate:
*  subject: CN= sentry.example.com
*  start date: Aug 13 06:58:28 2023 GMT
*  expire date: Nov 11 06:58:27 2023 GMT
*  subjectAltName: host "sentry.example.com" matched cert's "sentry.example.com"
*  issuer: C=US; O=Let's Encrypt; CN=R3
*  SSL certificate verify ok.
* using HTTP/2
* h2 [:method: GET]
* h2 [:scheme: https]
* h2 [:authority: sentry.example.com]
* h2 [:path: /_static/dist/sentry/chunks/app_views_discover_index_tsx.6ed2f1bf1018c7e0321a.js]
* h2 [user-agent: curl/8.1.2]
* h2 [accept: */*]
* Using Stream ID: 1 (easy handle 0x12c00a800)
> GET /_static/dist/sentry/chunks/app_views_discover_index_tsx.6ed2f1bf1018c7e0321a.js HTTP/2
> Host: sentry.example.com
> User-Agent: curl/8.1.2
> Accept: */*
> 
< HTTP/2 404 
< date: Mon, 18 Sep 2023 09:11:42 GMT
< content-type: text/plain
< content-length: 0
< cache-control: max-age=0, must-revalidate
< x-frame-options: deny
< x-content-type-options: nosniff
< x-xss-protection: 1; mode=block
< strict-transport-security: max-age=15724800; includeSubDomains
< 
* Connection #0 to host sentry.example.com left intact

I tried checking in the container itself, if the file exists but I couldn't find the source directory of Sentry. I also couldn't find a related issue. Is there an easy way to rebuild the CSS ourselves, or did anyone else also experience this?

Edit:
I see that _static/dist/sentry/assets/zero-inbox-issues.bc85154a17398bf2a8c4.svg is also missing for some reason

Edit 2:
Login screen is also fully broken now

@xvilo
Copy link
Contributor Author

xvilo commented Sep 18, 2023

@xvilo
Copy link
Contributor Author

xvilo commented Oct 13, 2023

A workaround I found that works is adding the following annotation to the ingress definition for now:

ingress:
  annotations:
    nginx.ingress.kubernetes.io/configuration-snippet: |
      proxy_hide_header Content-Disposition;

@Mokto
Copy link
Contributor

Mokto commented Nov 13, 2023

This issue is stale because it has been open for 30 days with no activity.

@Mokto Mokto added the stale label Nov 13, 2023
@xvilo
Copy link
Contributor Author

xvilo commented Nov 17, 2023

#1049

@Mokto
Copy link
Contributor

Mokto commented Dec 18, 2023

This issue is stale because it has been open for 30 days with no activity.

@Mokto Mokto added the stale label Dec 18, 2023
@xvilo
Copy link
Contributor Author

xvilo commented Dec 18, 2023

It’s still an issue

@Mokto Mokto removed the stale label Dec 19, 2023
@Mokto
Copy link
Contributor

Mokto commented Jan 18, 2024

This issue is stale because it has been open for 30 days with no activity.

@Mokto Mokto added the stale label Jan 18, 2024
@Mokto
Copy link
Contributor

Mokto commented Feb 2, 2024

This issue was closed because it has been inactive for 14 days since being marked as stale.

@Mokto Mokto closed this as not planned Won't fix, can't repro, duplicate, stale Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants