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

sdb: support any fs.depth starting values. #58

Merged
merged 1 commit into from
Nov 19, 2024
Merged

sdb: support any fs.depth starting values. #58

merged 1 commit into from
Nov 19, 2024

Conversation

ericonr
Copy link
Member

@ericonr ericonr commented Nov 14, 2024

Unlike the {E,P}BPM and FOFB SDB filesystems, which start at fs.depth=1, the Timing SDB filesystem has a single item, at fs.depth=0. Instead of hardcoding anything specific, we can simply support any starting depth.

Without this change, printing Timing SDB information hit the indentation assertion, due to underflow when subtracting 1 from 0.

@henriquesimoes
@gustavosr8

Unlike the {E,P}BPM and FOFB SDB filesystems, which start at fs.depth=1,
the Timing SDB filesystem has a single item, at fs.depth=0. Instead of
hardcoding anything specific, we can simply support any starting depth.

Without this change, printing Timing SDB information hits the
indentation assertion, due to underflow when subtracting 1 from 0.
@ericonr ericonr merged commit 2192e40 into master Nov 19, 2024
25 checks passed
@ericonr ericonr deleted the sdb-depth branch November 19, 2024 18:07
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.

2 participants