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

Removed unreferenced time series and geo points #184

Conversation

jo-asplin-met-no
Copy link
Contributor

No description provided.

@lukas-phaf
Copy link
Contributor

Can we decouple this from the merge-backend-duration-and-level-changes branch, and merge it directly to main?

The regular DB cleanup is now triggered in a separate goroutine
that is not invoked as part of handling a call to PutObservations.
This simplifies code, avoids synchronization, and allows calls to
PutObservations to return sooner.
@jo-asplin-met-no
Copy link
Contributor Author

Can we decouple this from the merge-backend-duration-and-level-changes branch, and merge it directly to main?

Fine by me, since i guess this is unrelated to that merge-backend... task anyway. But what's the best way to do that?

@jo-asplin-met-no
Copy link
Contributor Author

Maybe the easiest is to create an altogether new branch (based off main) + PR ?

@jo-asplin-met-no
Copy link
Contributor Author

Another solution is maybe to just merge into merge-backend-... as planned, but in addition create a new branch/PR for getting the relevant commits into main? As you can tell, I don't feel proficient enough in git to see what would be the best solution.

@lukas-phaf
Copy link
Contributor

I am not a git expert either. I tried making a merge request for your branch against master, but that gives a huge amount of changes, I think because the merge-backend-duration-and-level-changes are your branch are behind main. Rebasing on main of your branch might work, but it is probably a nightmare.

Personally, I would create patch from this PR, and apply it to master to create a new PR (so what you suggest above).

@Jeffrey-Vervoort-KNMI, do you have a suggestion how to handle this? This is currently a branch of a branch, but the code is unrelated to that branch, and it would be better if it goes straight into main.

@jo-asplin-met-no
Copy link
Contributor Author

Hm, I think the best is simply to start from scratch, i.e. create a new branch off main, add a single commit with the net change, and then a PR for that. Stay tuned ...

@jo-asplin-met-no jo-asplin-met-no removed the request for review from lukas-phaf September 24, 2024 08:34
@jo-asplin-met-no jo-asplin-met-no deleted the issue_167_complete_cleanup branch September 24, 2024 08:39
@jo-asplin-met-no
Copy link
Contributor Author

Done! Forget this PR and use this one instead!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants