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

task: Troubleshoot schema hashes and reconsider saving updated branches during init #4781

Open
ogenstad opened this issue Oct 30, 2024 · 0 comments
Labels
group/backend Issue related to the backend (API Server, Git Agent) type/task Body of work related to an epic

Comments

@ogenstad
Copy link
Contributor

Component

API Server / GraphQL

Task Description

The PR #4769 made a change saves a branch back to the database during initialization if the hash defined on the branch object in the database is different compared to the full hash of the schema after it has been loaded in the database. In theory this is something that should not happen. We need to spend a bit more time to troubleshoot this to see when and why it can occur and fix those instances.

After doing so we could revert the changes when we save the brach information back to the database. We might still want some type of recovery in place but at that point we should use some form of lock to avoid having multiple workers trying to update the same information during server restarts.

@ogenstad ogenstad added group/backend Issue related to the backend (API Server, Git Agent) type/task Body of work related to an epic labels Oct 30, 2024
@ogenstad ogenstad added this to the Infrahub - 1.1 milestone Oct 30, 2024
@exalate-issue-sync exalate-issue-sync bot removed this from the Infrahub - 1.1 milestone Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
group/backend Issue related to the backend (API Server, Git Agent) type/task Body of work related to an epic
Projects
None yet
Development

No branches or pull requests

1 participant