-
Notifications
You must be signed in to change notification settings - Fork 11
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
AdjustBlockRange enhancement #874
Comments
Can you elaborate on the use case of this new feature? |
First - LastArg(last) is used in multiple commands and I believe it should have same adjustment properties as RangeArg(first,last). |
Example use of |
I see, this is more about a behavior change when using aida-db with no metadata. Instead of introducing a new flag works? Current: throw an error asking users to generate metadata if it doesn't exist (@Lubomir-Jahn can you confirm this?). |
Current behavior is that if opening AidaDB or reading its metadata somehow fails, we throw a warning and use user arguments as they are, without any adjustments to the range. If this is the case and user call for the first/last/lastpatch keyword, the default value for given keyword is used. |
Currently it doesn't even get tu printing out the warning.
|
!
before the block number (alternatively#
)The text was updated successfully, but these errors were encountered: