search

flyteorg / flyte

Scalable and flexible workflow orchestration platform that seamlessly unifies data, ML and analytics stacks.
https://flyte.org
Apache License 2.0
5.65k stars 629 forks source link

[BUG] Flyte Console in Sandbox is blank on Firefox #4669

Open ozzieba opened 9 months ago

ozzieba commented 9 months ago

Describe the bug

After running flyte demo start and navigating to localhost:30080 in Firefox, I get forwarded to /console, but then a blank white screen. Dev tools show the errorsbelow; Chromium works as expected. Firefox 116.0.2 on Ubuntu (Snap) Running with --safe-mode so no extensions etc

Any ideas? Thanks!

Expected behavior

Flyte console shows up on Firefox

Are you sure this issue hasn't been raised already?

Have you read the Code of Conduct?

Additional context to reproduce

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://unpkg.com/react-dom@16.13.1/umd/react-dom.production.min.js. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 301.

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://unpkg.com/react@16.13.1/umd/react.production.min.js. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 301.

The resource from “http://unpkg.com/react-dom@16.13.1/umd/react-dom.production.min.js” was blocked due to MIME type (“”) mismatch (X-Content-Type-Options: nosniff).
[console](http://localhost:8080/console)
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://unpkg.com/react-dom@16.13.1/umd/react-dom.production.min.js. (Reason: CORS request did not succeed). Status code: (null).

The resource from “http://unpkg.com/react@16.13.1/umd/react.production.min.js” was blocked due to MIME type (“”) mismatch (X-Content-Type-Options: nosniff).
[console](http://localhost:8080/console)
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://unpkg.com/react@16.13.1/umd/react.production.min.js. (Reason: CORS request did not succeed). Status code: (null).

<script> source URI is not allowed in this document: “http://unpkg.com/react@16.13.1/umd/react.production.min.js”. [console:1:657](http://localhost:8080/console)
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://unpkg.com/react-dom@16.13.1/umd/react-dom.production.min.js. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 301.

The resource from “http://unpkg.com/react-dom@16.13.1/umd/react-dom.production.min.js” was blocked due to MIME type (“”) mismatch (X-Content-Type-Options: nosniff).
[console](http://localhost:8080/console)
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://unpkg.com/react-dom@16.13.1/umd/react-dom.production.min.js. (Reason: CORS request did not succeed). Status code: (null).

<script> source URI is not allowed in this document: “http://unpkg.com/react-dom@16.13.1/umd/react-dom.production.min.js”. [console:1:754](http://localhost:8080/console)
ReferenceError: React is not defined
    87363 http://localhost:8080/console/assets/main.45f88a8b477bfdbb918d.js:1
    r http://localhost:8080/console/assets/main.45f88a8b477bfdbb918d.js:1
    65417 http://localhost:8080/console/assets/main.45f88a8b477bfdbb918d.js:1
    r http://localhost:8080/console/assets/main.45f88a8b477bfdbb918d.js:1
    i http://localhost:8080/console/assets/main.45f88a8b477bfdbb918d.js:1
    O http://localhost:8080/console/assets/main.45f88a8b477bfdbb918d.js:1
    <anonymous> http://localhost:8080/console/assets/main.45f88a8b477bfdbb918d.js:1
    <anonymous> http://localhost:8080/console/assets/main.45f88a8b477bfdbb918d.js:1
$ snap info firefox
name:      firefox
summary:   Mozilla Firefox web browser
publisher: Mozilla✓
store-url: https://snapcraft.io/firefox
license:   unset
description: |
  Firefox is a powerful, extensible web browser with support for modern web application
  technologies.
commands:
  - firefox
  - firefox.geckodriver
snap-id:      3wdHCAVyZEmYsCMFDE9qt92UV8rC8Wdk
tracking:     latest/stable/ubuntu-22.04
refresh-date: 35 days ago, at 11:55 EST
channels:
  latest/stable:    121.0-1.1    2023-12-20 (3600) 257MB -
  latest/candidate: 121.0-1.1    2023-12-20 (3600) 257MB -
  latest/beta:      122.0b4-1    2023-12-29 (3614) 275MB -
  latest/edge:      123.0a1      2023-12-22 (3610) 292MB -
  esr/stable:       115.6.0esr-1 2023-12-19 (3542) 252MB -
  esr/candidate:    115.6.0esr-1 2023-12-11 (3542) 252MB -
  esr/beta:         ↑                                    
  esr/edge:         ↑                                    
installed:          116.0.2-1               (2987) 248MB -
$ cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"
$ flytectl version
{
  "App": "flytectl",
  "Build": "2eb0674",
  "Version": "0.8.5",
  "BuildTime": "2024-01-03 10:56:06.572755497 -0500 EST m=+0.012082110"
}{
  "App": "controlPlane",
  "Build": "unknown",
  "Version": "unknown",
  "BuildTime": "2024-01-03 15:13:27.450614178 +0000 UTC m=+0.010128880"
$ kubectl get po -o yaml -n flyte|grep image
      image: kubernetesui/dashboard:sandbox
      imagePullPolicy: Never
      image: docker.io/kubernetesui/dashboard:sandbox
      imageID: sha256:07655ddf2eebe5d250f7a72c25f638b27126805d61779741b4e62e69ba080558
      image: registry:sandbox
      imagePullPolicy: Never
      image: docker.io/library/registry:sandbox
      imageID: sha256:f5352b75f67e2e2df2bf2d96509248d1f618b8aa66d8b8c89d21e29111424881
      image: docker.io/bitnami/postgresql:sandbox
      imagePullPolicy: Never
      image: docker.io/bitnami/bitnami-shell:sandbox
      imagePullPolicy: Never
      image: docker.io/bitnami/postgresql:sandbox
      imageID: sha256:a729f5f0de5fa39ba4d649e7366d499299304145d2456d60a16b0e63395bd61a
      image: docker.io/bitnami/bitnami-shell:sandbox
      imageID: sha256:11e23119f2c697a4d756a33d130370517aa268908f2e8dce5345385ca467099f
      image: docker.io/bitnami/minio:sandbox
      imagePullPolicy: Never
      image: docker.io/bitnami/bitnami-shell:sandbox
      imagePullPolicy: Never
      image: docker.io/bitnami/minio:sandbox
      imageID: sha256:83c8830c18680f53476a5661a17323d1d8836f2d0a4ac2fbdf441eb48645c799
      image: docker.io/bitnami/bitnami-shell:sandbox
      imageID: sha256:11e23119f2c697a4d756a33d130370517aa268908f2e8dce5345385ca467099f
      image: moby/buildkit:sandbox
      imagePullPolicy: Never
      image: docker.io/moby/buildkit:sandbox
      imageID: sha256:be698b50dea43af34127e039497efd8130328673aecabe2de9d3dd17bed63a15
    - image: envoyproxy/envoy:sandbox
      imagePullPolicy: Never
      image: docker.io/envoyproxy/envoy:sandbox
      imageID: sha256:a2fdd8ef6039e901a0a940b5583d0c7a81722ed1f4d2e677285faf43e3cbe61e
      image: flyte-binary:sandbox
      imagePullPolicy: Never
      image: bitnami/postgresql:sandbox
      imagePullPolicy: Never
      image: docker.io/library/flyte-binary:sandbox
      imageID: sha256:5173ab4a663c82c340ed7424eaa335f7c31bbb9335a11ea0692fb485256eca3a
      image: docker.io/bitnami/postgresql:sandbox
      imageID: sha256:a729f5f0de5fa39ba4d649e7366d499299304145d2456d60a16b0e63395bd61a
      image: ghcr.io/flyteorg/flyteagent:1.10.1
      imagePullPolicy: IfNotPresent
      image: ghcr.io/flyteorg/flyteagent:1.10.1
      imageID: ghcr.io/flyteorg/flyteagent@sha256:8d4f9d20f5628b8926ab0a8e4284a395abdc8b9c1a7d8a679a377619d4fbedf6
welcome[bot] commented 9 months ago

Thank you for opening your first issue here! 🛠

dosubot[bot] commented 9 months ago

🤖

Thanks for reporting this issue, it seems like a CORS (Cross-Origin Resource Sharing) issue. To better understand and diagnose the problem, could you please provide the following additional information:

  1. Can you confirm if you have any specific network configurations or firewall settings that might be blocking the requests?
  2. Have you tried clearing your browser cache or tried using a different browser?
  3. Could you provide the exact version of Flyte you are using?
  4. Are there any additional error messages in the console that you haven't included in your report?

This information will help us in identifying the root cause of the issue. Thanks for your cooperation.

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

eapolinario commented 8 months ago

I was not able to repro this. Just for kicks, can you try again but use 127.0.0.1 instead of localhost?

kumare3 commented 2 months ago

Let's close this issue, @samhita-alla do you see this