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

Fix datetime interval sc #614

Merged
merged 1 commit into from
Oct 12, 2022
Merged

Conversation

samuelmanzanera
Copy link
Member

Description

Using SC datetime's trigger with UNIX timestamp from a pastime, causes the worker to crash.
Hence, this fix ensures the worker will only trigger date time UNIX timestamp in the future.

Type of change

  • Bug fix (non-breaking change which fixes an issue)

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

@samuelmanzanera samuelmanzanera added bug Something isn't working smart contracts Involve smart contracts labels Oct 7, 2022
@samuelmanzanera samuelmanzanera changed the base branch from master to develop October 7, 2022 14:41
@samuelmanzanera samuelmanzanera self-assigned this Oct 11, 2022
@samuelmanzanera samuelmanzanera merged commit 8b92a8a into develop Oct 12, 2022
@samuelmanzanera samuelmanzanera deleted the fix_datetime_interval_SC branch October 12, 2022 08:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working smart contracts Involve smart contracts
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants