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

Decay score is rewritten at upsert even if the score passed at creation is the same #6452

Closed
SamuelHassine opened this issue Mar 23, 2024 · 0 comments
Closed

Decay score is rewritten at upsert even if the score passed at creation is the same #6452

SamuelHassine opened this issue Mar 23, 2024 · 0 comments
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone
Release 6.0.8

Comments

@SamuelHassine
Copy link
Member

Description

Decay score is rewritten at upsert even if the score passed at creation is the same
@SamuelHassine SamuelHassine added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Mar 23, 2024
SamuelHassine added a commit that referenced this issue Mar 23, 2024
@SamuelHassine
[backend] Fix the decay score upsert (#6452)
6525c07
@SamuelHassine SamuelHassine added solved use to identify issue that has been solved (must be linked to the solving PR) and removed needs triage use to identify issue needing triage from Filigran Product team labels Mar 23, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.8 milestone Mar 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Milestone
Release 6.0.8
Development

No branches or pull requests
1 participant
@SamuelHassine