-
Notifications
You must be signed in to change notification settings - Fork 160
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
Volume dumping restriction manager #292
Volume dumping restriction manager #292
Conversation
6fac7ee
to
c14925d
Compare
Hey, @samparsky Should I start reviewing this PR or still you are adding some code in it? |
@satyamakgec Currently adding more tests. Will let you know when I am done |
b76aa75
to
0937471
Compare
@satyamakgec Please kindly review this PR |
contracts/modules/TransferManager/VolumeDumpingRestrictionManager.sol
Outdated
Show resolved
Hide resolved
contracts/modules/TransferManager/VolumeDumpingRestrictionManager.sol
Outdated
Show resolved
Hide resolved
contracts/modules/TransferManager/VolumeDumpingRestrictionManager.sol
Outdated
Show resolved
Hide resolved
@samparsky left some comments on the PR. and you can also improve the test coverage of your contracts although it is good please try to make it |
5222dcf
to
628cf87
Compare
@satyamakgec I have made the changes suggested above. This returns $ node_modules/.bin/solidity-coverage the following error which seems odd, given that
|
Yes @samparsky we are facing this issue, Once we resolve that then your PR also start building in Travis. |
contracts/modules/TransferManager/VolumeDumpingRestrictionManager.sol
Outdated
Show resolved
Hide resolved
contracts/modules/TransferManager/VolumeDumpingRestrictionManager.sol
Outdated
Show resolved
Hide resolved
contracts/modules/TransferManager/VolumeDumpingRestrictionManager.sol
Outdated
Show resolved
Hide resolved
@satyamakgec Please review, the changes suggested have been implemented |
c2028d7
to
1acfa9e
Compare
@satyamakgec Please review, the changes suggested have been implemented |
contracts/modules/TransferManager/VolumeDumpingRestrictionManager.sol
Outdated
Show resolved
Hide resolved
|
||
if (_amount <= allowedRemainingAmount){ | ||
volumeTally[_from][periodId] = volumeTally[_from][periodId].add(_amount); | ||
return Result.VALID; |
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.
As above should return Result.NA here not Result.VALID
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.
When should Result.VALID
be used?
contracts/modules/TransferManager/VolumeDumpingRestrictionManager.sol
Outdated
Show resolved
Hide resolved
contracts/modules/TransferManager/VolumeDumpingRestrictionManager.sol
Outdated
Show resolved
Hide resolved
contracts/modules/TransferManager/VolumeDumpingRestrictionManager.sol
Outdated
Show resolved
Hide resolved
contracts/modules/TransferManager/VolumeDumpingRestrictionManager.sol
Outdated
Show resolved
Hide resolved
1acfa9e
to
0dcb580
Compare
@adamdossa @satyamakgec Please review, the changes suggested have been implemented |
@samparsky Thanks for all your hard work and patience. we are in the process of reviewing the code. it may take a couple of days to finalize the module. So please bear me. I will try to send you an update as soon as possible. |
@satyamakgec @adamdossa It would be helpful if this PR can be reviewed & merged. |
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.
Also, try to increase the branch coverage it is 80 % but we are expecting b/w 95% - 100%
contracts/modules/TransferManager/VolumeDumpingRestrictionManager.sol
Outdated
Show resolved
Hide resolved
contracts/modules/TransferManager/VolumeDumpingRestrictionManager.sol
Outdated
Show resolved
Hide resolved
contracts/modules/TransferManager/VolumeDumpingRestrictionManager.sol
Outdated
Show resolved
Hide resolved
contracts/modules/TransferManager/VolumeDumpingRestrictionManager.sol
Outdated
Show resolved
Hide resolved
contracts/modules/TransferManager/VolumeDumpingRestrictionManager.sol
Outdated
Show resolved
Hide resolved
contracts/modules/TransferManager/VolumeDumpingRestrictionManagerFactory.sol
Outdated
Show resolved
Hide resolved
contracts/modules/TransferManager/VolumeDumpingRestrictionManager.sol
Outdated
Show resolved
Hide resolved
6b6ca11
to
579c596
Compare
@satyamakgec I have implemented the changes you have suggested. VolumeDumpingRestrictionTMFactory.sol - 96% I still have some questions,
It would be awesome to get a response |
@samparsky Thanks for the changes Yes you are right it is not matching with the design. I will give you more information after the internal discussion on design. |
@satyamakgec @adamdossa I am waiting on your decision |
Hey @samparsky sorry for the delay. The logic looks as - |
@satyamakgec That means the calculation of the limit is correct, As for the logic of the rolling period is calculated thus The assumption is there is no rollover of tokens transfer i.e. if you have 10k limit in a period & you only transfer 5k you don't get the remaining 5k rolled over to the next period endtime - 200 currentTime = 101 currentTime = 102 currentTime = 120 currentTime = 150 It would be great if we can work together to close the PR asap, its taken quite a very long time. |
@satyamakgec @adamdossa Still waiting on you |
Hey we are at Devcon so the coming week will be pretty much busy. I will
catch you up after the devcon.
Cheers
…On Mon, Oct 29, 2018, 12:25 Omidiora Samuel ***@***.***> wrote:
@satyamakgec <https://github.com/satyamakgec> @adamdossa
<https://github.com/adamdossa> Still waiting on you
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#292 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AN5_BVgFNplBi81eBBsugxyI20QexsSaks5upuW4gaJpZM4W_Q-U>
.
|
@satyamakgec Hello, how was Devcon? Hoping we can conclude on this, this week |
@samparsky Devcon was good and yes we can conclude this week. |
@samparsky please do resolve the above issues and update your branch so I can give this module a green light |
883f8e1
to
1157d95
Compare
added more tests added movePeriod amounts added changes
1157d95
to
bb73259
Compare
@satyamakgec I have implemented the suggested changes. I changed the implementation of the |
Bounty paid. Thanks a lot for your contribution @samparsky . |
@maxsam4 Any reason why the PR wasn't merged? |
@samparsky We have decided to merge this module and #320 It would not have been fair of us to ask you guys to do the required change so we'll be doing them ourselves. |
Please check if the PR fulfills these requirements
What kind of change does this PR introduce?
#268
What is the current behavior?
(You can also link to an open issue here)
What is the new behavior?
(Define and describe any new functionality. Clarify if this is a feature change)
Does this PR introduce a breaking change?
No
Any Other information: