-
Notifications
You must be signed in to change notification settings - Fork 375
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
feat: new txtar command adduser
#1471
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #1471 +/- ##
==========================================
- Coverage 55.87% 55.65% -0.23%
==========================================
Files 430 431 +1
Lines 65618 67201 +1583
==========================================
+ Hits 36667 37402 +735
- Misses 26083 26866 +783
- Partials 2868 2933 +65
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Related with #1269 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you provide more details or/and example regarding the use of the sleep
command? As mentioned in #1471 (comment) , I'm a bit apprehensive about introducing this command.
adduser
and sleep
adduser
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
maybe you can move txtar
tests inside gno.land/pkg/integration/testdata
as they are only here to test the adduser
feature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a really cool feature 💯
I've left some comments that should be addressed before we proceed, namely the initial accounts that are available to node starts with txtar
Co-authored-by: Hariom Verma <hariom18599@gmail.com>
…o feat/txtar-sleep-adduser
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for taking a look at the comments 🙏
I've opened up an issue to discuss how we orchestrate txtar nodes, to avoid further blocking this PR:
#1484 (comment)
<!-- please provide a detailed description of the changes made in this pull request. --> As I've started to think about creating txtar tests for contracts with logic depending on contract calls from multiple users and durations since previous contract calls, the addition of the `adduser` command seems to be necessary. <details><summary>Contributors' checklist...</summary> - [x] Added new tests, or not needed, or not feasible - [x] Provided an example (e.g. screenshot) to aid review or the PR is self-explanatory - [x] Updated the official documentation or not needed - [x] No breaking changes were made, or a `BREAKING CHANGE: xxx` message was included in the description - [ ] Added references to related issues and PRs - [ ] Provided any useful hints for running manual tests - [ ] Added new benchmarks to [generated graphs](https://gnoland.github.io/benchmarks), if any. More info [here](https://github.com/gnolang/gno/blob/master/.benchmarks/README.md). </details> --------- Co-authored-by: Hariom Verma <hariom18599@gmail.com>
As I've started to think about creating txtar tests for contracts with logic depending on contract calls from multiple users and durations since previous contract calls, the addition of the
adduser
command seems to be necessary.Contributors' checklist...
BREAKING CHANGE: xxx
message was included in the description