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

[ft-benchmark] fill actor and context db fields properly #11663

Merged
merged 1 commit into from
Jun 25, 2024

Conversation

MCJOHN974
Copy link
Contributor

Before this changes initiator and context db fields was filled by hardcoded constants. Now they switched to command line arguments. Probably it makes sense to do this arguments required and not default them to "unknown", but don't think it is very important

@MCJOHN974 MCJOHN974 requested review from aborg-dev and mooori June 25, 2024 09:54
@MCJOHN974 MCJOHN974 requested a review from a team as a code owner June 25, 2024 09:54
Copy link

codecov bot commented Jun 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.61%. Comparing base (95ce391) to head (2eb3f3e).
Report is 2 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #11663      +/-   ##
==========================================
- Coverage   71.63%   71.61%   -0.03%     
==========================================
  Files         787      787              
  Lines      161118   161104      -14     
  Branches   161118   161104      -14     
==========================================
- Hits       115415   115368      -47     
- Misses      40653    40687      +34     
+ Partials     5050     5049       -1     
Flag Coverage Δ
backward-compatibility 0.23% <ø> (+<0.01%) ⬆️
db-migration 0.23% <ø> (+<0.01%) ⬆️
genesis-check 1.36% <ø> (+<0.01%) ⬆️
integration-tests 37.77% <ø> (-0.04%) ⬇️
linux 69.00% <ø> (-0.03%) ⬇️
linux-nightly 71.10% <ø> (-0.03%) ⬇️
macos 52.60% <ø> (-0.03%) ⬇️
pytests 1.59% <ø> (+<0.01%) ⬆️
sanity-checks 1.39% <ø> (+<0.01%) ⬆️
unittests 66.21% <ø> (-0.01%) ⬇️
upgradability 0.28% <ø> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

parser.add_argument('--user', type=str, default='unknown', help='User name')
parser.add_argument('--context',
type=str,
default='unknown',
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: Perhaps make user and context required arguments without default, to make sure these fields have meaningful values.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Maybe I agree, but maybe some time we will prefer to see row in db with unknown, unknown rather than see nothing. If you strongly confident that we want this arguments be required let me know I will change them

@@ -111,6 +111,11 @@ def commit_to_db(data: dict) -> None:
type=int,
required=True,
help='Number of users')
parser.add_argument('--user', type=str, default='unknown', help='User name')
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: I think user is a bit ambiguous here. initiator might be clearer and would be in line with the db column name. (In the postgres db naming a column user lead to lint errors, so instead it's named initiator.)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep, it would be better to do this naming consistent with db scheme, but then I will need rename this across all files so probably will do it in another PR

@MCJOHN974 MCJOHN974 added this pull request to the merge queue Jun 25, 2024
Merged via the queue into master with commit fc6f94b Jun 25, 2024
30 checks passed
@MCJOHN974 MCJOHN974 deleted the viktar/ft-benchmark-cli branch June 25, 2024 12:54
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.

3 participants