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.

Sign up for GitHub

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

Jump to bottom

Different handling label analysis if result already calculated #21

Merged
merged 2 commits into from
Sep 11, 2023
Merged

Different handling label analysis if result already calculated #21

merged 2 commits into from
Sep 11, 2023

Commits on Sep 11, 2023

  1. Different handling label analysis if result already calculated 

    This change is intended to work with the PATCHing of labels by the CLI after collecting them.
Currently doing that doesn't trigger another task in the worker. SO if the labels arraive after we finished calculating we are left with incomplete results on the database. That is fine as the CLI will calculate again.

I think this change might have been a bit premature, but the idea is to have a different way of handling the calculation if we already have results. Then we simply calculate the final result using the saved labels and add in the requested labels that we might not have had the first time around. This would be much much faster than calculating everything again.
    @giovanni-guidini
    giovanni-guidini committed Sep 11, 2023
    Configuration menu
    Copy the full SHA
    66ab117 View commit details
    Browse the repository at this point in the history

  2. chore: Update branch 

    Updating branch and making sure all tests are OK.
    @giovanni-guidini
    giovanni-guidini committed Sep 11, 2023
    Configuration menu
    Copy the full SHA
    03509a2 View commit details
    Browse the repository at this point in the history