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

Use a defaultdict for BlockInfo in htex scale-in #3300

Merged
merged 3 commits into from Mar 28, 2024

Conversation

benclifford
Copy link
Collaborator

This is to accomodate upcoming expansion of the block_info dictionary to include data from an additional source (the list of blocks known to the scaling code)

This change arises from a review of PR #3232, an earlier prototype of that expansion work.

Changed Behaviour

Behaviourally, this shouldn't change anything: it changes invalid block accesses from key errors into blocks that are infinitely idle and completely unloaded. However there are no indexes into block_info except in code that is adding block information, so this situation should not arise.

Type of change

  • Code maintenance/cleanup

This is to accomodate upcoming expansion of the block_info dictionary to
include data from an additional source (the list of blocks known to the
scaling code)

This change arises from a review of PR #3232, an earlier prototype of that
expansion work.

Behaviourally, this shouldn't change anything: it changes invalid
block accesses from key errors into blocks that are infinitely idle and
completely unloaded. However there are no indexes into block_info except
in code that is adding block information, so this situation should
not arise.
Copy link
Collaborator

@khk-globus khk-globus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep. Nice.

@benclifford benclifford merged commit aed4256 into master Mar 28, 2024
6 checks passed
@benclifford benclifford deleted the benc-defaultdict-BlockInfo branch March 28, 2024 13:11
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.

None yet

2 participants