Hotfix: Fix score calculation after de-allocation #200
Conversation
This file contains 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
fix: score calculation after de-allocation
nauttiilus
pushed a commit
to nauttiilus/compute-subnet
that referenced
this pull request
Oct 1, 2024
Hotfix: Fix score calculation after de-allocation
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.
• Updated version numbers in compute/init.py
• Enhanced error handling and resilience in calculate_pow_score.py by using default values with the .get() method.
• Updated SQL queries in challenge.py to retrieve the last 60 entries per UID instead of filtering by the last 12 hours.
• Removed redundant SSH port checks and logging.
• Improved score synchronization and error handling in validator.py.