Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Feast UI in remote instance

See original GitHub issue

Does web UI work fine if feast is installed in a remote instance? I face the below error on running ‘feast ui’.

Error Loading Project Configs
There was an error loading the Project Configurations. Please check that feature_store.yaml file is available and well-formed.

However the sample project which is in feast/ui works fine on npm start.

Please could you help or let me know what I am missing?

Issue Analytics

State:
Created a year ago
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

arumugaguru-mindtreecommented, Jul 6, 2022

Feast is installed in GCP and I access the server using ssh.

Earlier the request for registry.json was pointing to http://0.0.0.0:888/registry.json. But this was resolved with the 0.22 version. After upgrading to 0.22, I believed this should work fine now. But still the above error is seen. In the web UI console(chrome), I get the Zod error:

ZodError: [
  {
    "code": "invalid_enum_value",
    "options": [
      "FLOAT",
      "INT64",
      "STRING",
      "BOOL",
      "BYTES",
      "INT32",
      "DOUBLE",
      "UNIX_TIMESTAMP",
      "INVALID",
      "BYTES_LIST",
      "STRING_LIST",
      "INT32_LIST",
      "INT64_LIST",
      "DOUBLE_LIST",
      "FLOAT_LIST",
      "BOOL_LIST",
      "UNIX_TIMESTAMP_LIST",
      "NULL"
    ],
    "path": [
      "entities",
      0,
      "spec",
      "valueType"
    ],
    "message": "Invalid enum value. Expected 'FLOAT' | 'INT64' | 'STRING' | 'BOOL' | 'BYTES' | 'INT32' | 'DOUBLE' | 'UNIX_TIMESTAMP' | 'INVALID' | 'BYTES_LIST' | 'STRING_LIST' | 'INT32_LIST' | 'INT64_LIST' | 'DOUBLE_LIST' | 'FLOAT_LIST' | 'BOOL_LIST' | 'UNIX_TIMESTAMP_LIST' | 'NULL'"
  },
  {
    "code": "invalid_enum_value",
    "options": [
      "FLOAT",
      "INT64",
      "STRING",
      "BOOL",
      "BYTES",
      "INT32",
      "DOUBLE",
      "UNIX_TIMESTAMP",
      "INVALID",
      "BYTES_LIST",
      "STRING_LIST",
      "INT32_LIST",
      "INT64_LIST",
      "DOUBLE_LIST",
      "FLOAT_LIST",
      "BOOL_LIST",
      "UNIX_TIMESTAMP_LIST",
      "NULL"
    ],
    "path": [
      "entities",
      1,
      "spec",
      "valueType"
    ],
    "message": "Invalid enum value. Expected 'FLOAT' | 'INT64' | 'STRING' | 'BOOL' | 'BYTES' | 'INT32' | 'DOUBLE' | 'UNIX_TIMESTAMP' | 'INVALID' | 'BYTES_LIST' | 'STRING_LIST' | 'INT32_LIST' | 'INT64_LIST' | 'DOUBLE_LIST' | 'FLOAT_LIST' | 'BOOL_LIST' | 'UNIX_TIMESTAMP_LIST' | 'NULL'"
  }
]
    at yk (index.mjs:449:23)
    at n.value (index.mjs:561:16)
    at n.value (index.mjs:541:29)
    at useLoadRegistry.ts:35:47
```

The feature repo that I use is the sample one that is created by default using feast init. No other changes are done to the repo.

I hope this info helps.

0reactions

adchiacommented, Jul 19, 2022

Should be fixed now I think in Feast 0.22.1!

Top Results From Across the Web

Unable to access data in Feast UI when deployed ...

Run feast ui --host <instance private ip> in EC2 instance. Specifications. Version: 0.21.2; Platform: EC2; Subsystem: Possible Solution.

Python feature server

The Python feature server is an HTTP endpoint that serves features with JSON I/O. This enables ... A remote feature server on AWS...

Creating a Feature Store with Feast | by Kedion - Medium

In PART 3, we are going to show you how you could integrate Feast into a Python API and a React web application....

How to Trigger the Feast Workflow using FlyteRemote

You can use FlyteConsole to launch, monitor, and introspect Flyte executions. However here, let's use flytekit.remote to interact with the Flyte backend. from ......

Scalable and Programmable Serving

In this quick-start example we will define a simple “hello world” deployment, deploy it behind HTTP locally, and query it.