GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Add explanation more about feast ui with react, especially in project list part · Issue #3332 · feast-dev/feast

Add explanation more about feast ui with react, especially in project list part #3332

New issue
Copy link
New issue
Copy link
Closed
#3939
Closed
Add explanation more about feast ui with react, especially in project list part#3332
#3939
Copy link
Labels
good first issueGood for newcomersGood for newcomerskind/featureNew feature or requestNew feature or request

Description

@dfd19
dfd19
opened on Nov 7, 2022
Issue body actions

I need more explanation about how to run feast ui with customize with react.

I have read feast/ui/README.md and found out the explanation of "registryPath" in project-list.json is too low. When i try it, i always get error

Error

Error: Unable to properly parse Project List JSON. Check that your project list is formatted properly.
    at new ProjectListError (http://localhost:3000/static/js/bundle.js:34704:24)
    at anticipatedProjectListErrors (http://localhost:3000/static/js/bundle.js:34717:12)
    at http://localhost:3000/static/js/bundle.js:34738:30
  1. even i try to change registry path to nonexistent file, it still has same error. why does it happened? and where should i save the registry file? is it in react public? or is it in root project react? i kinda confused how to save the location of file and what relative path of registryPath refer to?

  2. i have tried feast registrydump, i assume this is the file that wants to be read by react feast UI right? and its result is basically registry in JSON. andin Readme.md in feast ui, it's also state that registry in project-list.json has type file json. but, in https://github.com/feast-dev/feast/blob/master/ui/public/projects-list.json the type file of "registryPath" is ".db", it kinda make me more confused. so which one is the correct one? json or .db?

  3. I have registry offline saved as file in S3. based on tutorial, the type file is .pb. I know i can fetch the file and add it on react, but can it be read by Feast React? I already try but the error is still same as i stated before.

it'd be great if the README.md in feast/ui updated to be clear about how to run it. all my question stated basically i just want to know how to run feast ui with customize react.

P.S. Thank you for help me out, This is my first time to write issue in github. im sorry if this is not proper way to ask.

Reacted by bjakubowskiVNSNY and Tom Steenbergen

Activity

  1. dfd19
    added
    kind/featureNew feature or requestNew feature or request
    on Nov 7, 2022
  2. rushabh31 commented on Feb 10, 2023

    @rushabh31
    rushabh31
    on Feb 10, 2023
    More actions

    @dfd19 Were you able to find out where to place project-list.json?

  3. stale commented on Jun 10, 2023

    @stale
    staleBot
    on Jun 10, 2023
    More actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

  4. stale
    added
    wontfixThis will not be worked onThis will not be worked on
    on Jun 10, 2023
  5. stale
    closed this as completedon Aug 10, 2023
  6. priyathamv commented on Feb 7, 2024

    @priyathamv
    priyathamv
    on Feb 7, 2024
    More actions

    @rushabh31 I was facing the same issue. Then I found that there is a typo in the documentation. The file name has to be projects-list.json and not project-list.json

  7. jeremyary
    reopened this on Feb 7, 2024
  8. stale
    removed
    wontfixThis will not be worked onThis will not be worked on
    on Feb 7, 2024
  9. jeremyary commented on Feb 7, 2024

    @jeremyary
    jeremyary
    on Feb 7, 2024
    Collaborator
    More actions

    referenced typo in last comment seems to need correction to me as well, easy fix here w/a quick README update

  10. jeremyary
    added
    good first issueGood for newcomersGood for newcomers
    on Feb 7, 2024
  11. jeremyary
    closed this as completedin #3939on Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueGood for newcomersGood for newcomerskind/featureNew feature or requestNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.