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

Custom functions not tracked after restarting #10245

Open
stevenkaspar opened this issue May 19, 2024 · 0 comments
Open

Custom functions not tracked after restarting #10245

stevenkaspar opened this issue May 19, 2024 · 0 comments
Labels
k/bug Something isn't working

Comments

@stevenkaspar
Copy link

Version Information

Server Version:
CLI Version (for CLI related issue): 2.37.0

Environment

local

What is the current behaviour?

When i restart the hasura container using the hasura/graphql-engine:v2.37.0.cli-migrations-v3, custom functions that i have tracked before and show in metadata files (see screenshots) are untracked and i must manually add them back by clicking "TRACK"

What is the expected behaviour?

It's expected that tracked custom functions would pull from metadata files

How to reproduce the issue?

idk - sorry

Screenshots or Screencast

Screenshot 2024-05-19 at 6 20 43 AM

Screenshot 2024-05-19 at 6 20 37 AM

Please provide any traces or logs that could help here.

no errors. functions are just untracked

Any possible solutions/workarounds you're aware of?

i am going to try calling the metadata API to reenable on startup

Keywords

Custom Functions, Untracked

@stevenkaspar stevenkaspar added the k/bug Something isn't working label May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
k/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant