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

v2.0.0-alpha.2 Console assets not found #6610

Closed
mirzap opened this issue Feb 25, 2021 · 8 comments
Closed

v2.0.0-alpha.2 Console assets not found #6610

mirzap opened this issue Feb 25, 2021 · 8 comments
Labels
support/needs-triage Needs to be triaged so that we have enough information to add this to our backlog
Milestone

Comments

@mirzap
Copy link

mirzap commented Feb 25, 2021

I have specified HASURA_GRAPHQL_CONSOLE_ASSETS_DIR in my docker file to /srv/console-assets but after the upgrade to the v2.0.0-alpha.2 those are not to be found.

I've tried setting to /srv as suggested here but it's the same:

image

@jflambert
Copy link
Contributor

jflambert commented Feb 26, 2021

Yes I mentioned this to @scriptonist in #6600, which I will now close in favor of this new issue.

@tirumaraiselvan tirumaraiselvan added the support/needs-triage Needs to be triaged so that we have enough information to add this to our backlog label Mar 1, 2021
@0x777
Copy link
Member

0x777 commented Mar 2, 2021

@mirzap @jflambert This will be fixed in 2.0.0-alpha.3, till then setting HASURA_GRAPHQL_CONSOLE_ASSETS_DIR to /srv should work.

I've tried setting to /srv as suggested here but it's the same:

@mirzap Maybe the docker image was not re-built after the environment variable is changed?

@mirzap
Copy link
Author

mirzap commented Mar 2, 2021

@0x777 Great! When can we expect 3rd alpha?

I do down -v everytime, which removes docker containers and volumes and it still happens... For now I'm using cloud assets.

@mirzap
Copy link
Author

mirzap commented Mar 4, 2021

I'm testing on alpha.3. Still neither /srv nor /srv/console-assets work. When I enter the container files exist in /srv/console-assets

image

{
  "type": "http-log",
  "timestamp": "2021-03-04T16:59:04.248+0000",
  "level": "error",
  "detail": {
    "operation": {
      "error": {
        "path": "$",
        "error": "resource does not exist",
        "code": "not-found"
      },
      "request_id": "eedbaef6-09f8-4858-9594-b01b90b78f37",
      "response_size": 65,
      "raw_query": ""
    },
    "request_id": "eedbaef6-09f8-4858-9594-b01b90b78f37",
    "http_info": {
      "status": 404,
      "http_version": "HTTP/1.1",
      "url": "/console/assets/versioned/vendor.js.gz",
      "ip": "172.21.0.1",
      "method": "GET",
      "content_encoding": null
    }
  }
}

@kolharsam
Copy link
Contributor

kolharsam commented Mar 4, 2021

@mirzap I can confirm that this issue has been fixed in 2.0.0-alpha.3. Setting HASURA_GRAPHQL_CONSOLE_ASSETS_DIR to /srv/console-assets works now. Please make sure that you're setting HASURA_GRAPHQL_ENABLE_CONSOLE to true as well.

@mirzap
Copy link
Author

mirzap commented Mar 4, 2021

Yes, setting HASURA_GRAPHQL_ENABLE_CONSOLE did the trick.

@coco98 coco98 added this to the v2.0.0 stable milestone Mar 5, 2021
@jflambert
Copy link
Contributor

Seems to work now. Maybe close this issue?

@beerose
Copy link
Contributor

beerose commented Mar 9, 2021

Fixed in f2724c9

@beerose beerose closed this as completed Mar 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
support/needs-triage Needs to be triaged so that we have enough information to add this to our backlog
Projects
None yet
Development

No branches or pull requests

7 participants