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

[Bug]: A bad "type" browser URL leads to an NPE #769

Closed
anthonylasso opened this issue Apr 25, 2023 · 0 comments
Closed

[Bug]: A bad "type" browser URL leads to an NPE #769

anthonylasso opened this issue Apr 25, 2023 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@anthonylasso
Copy link
Contributor

anthonylasso commented Apr 25, 2023

Expected Behavior

When a faulty or non-existent browser URL is entered, the page should gracefully display the error to the user.

Actual Behavior

Currently the app displays an error when running locally in node, or crashes back to the homepage with faulty breadcrumb artifacts:

Screenshot 2023-04-25 at 1 41 52 PM

badTypePathError.mov

Steps To Reproduce

  1. Enter an non-existent resource path.
  2. If running on NPM locally, an error will display.
  3. If running in docker, the app crashes back to the homepage with faulty breadcrumbs displaying.

What mode are you running Featureform in?

Local

What version of Python are you running?

3.7

Featureform Python Package Version

0.7.3

Featureform Helm Chart Version

No response

Kubernetes Version

No response

Relevant log output

No response

@anthonylasso anthonylasso added the bug Something isn't working label Apr 25, 2023
@anthonylasso anthonylasso self-assigned this Apr 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant