-
Notifications
You must be signed in to change notification settings - Fork 155
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
Remove emit ReportTimestampOutOfRange so getData is read only #281
base: master
Are you sure you want to change the base?
Conversation
Remove emit ReportTimestampOutOfRange so getData is read only
Remove emit ReportTimestampOutOfRange so getData is read only
🚨 Report Summary
For more details view the full report in OpenZeppelin Code Inspector |
Yea. Good call. Was meaning to do this too. |
@@ -186,10 +186,10 @@ contract MedianOracle is OwnableUpgradeable, IOracle { | |||
.timestamp; | |||
if (reportTimestampPast < minValidTimestamp) { | |||
// Past report is too old. | |||
emit ReportTimestampOutOfRange(providerAddress); | |||
// Deprecated: emit ReportTimestampOutOfRange(providerAddress); |
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.
I think we can just remove it, rather than commenting it out. Dont think any of our off-chain services rely on this log.
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.
I think it is a good idea to leave so that previous logs are still understandable
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.
Looks good... can we also add the view
modifier to the getData()
signature?
Remove emit ReportTimestampOutOfRange so getData is read only