Repository navigation
fix(quota): una ventana con reset futuro ya no cuenta como agotada - #99
Merged
Merged
Conversation
Automated verification
typechecktestsbuild |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Argon quedaba bloqueado con 'quota exhausted (100% remaining)' porque el criterio miraba solo que el resetTime del grupo estuviera en el futuro. Las familias con una sola ventana semanal siempre tienen ese reset adelante, asi que el modelo se apagaba para todo el periodo. Ahora el grupo se declara seco solo cuando remainingFraction esta en cero o por debajo de un margen de 0.01, y un dato faltante fail-open. El mismo criterio se aplica en el calculo de tiempo de espera, para que el mensaje y la decision no se contradigan. Verificado: 1184 pruebas en verde (46 archivos), typecheck limpio y build sin errores.