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

Fixed issue where the detection was also running on the output folder triggering a chain update event #158

Merged
merged 10 commits into from
Nov 15, 2024

Conversation

GitHK
Copy link
Contributor

@GitHK GitHK commented Nov 15, 2024

What do these changes do?

Previous version was updating every second the outputs. Corrected the issue. Only updates when inputs change (which is how it should work).

Modified tests to detect this situation and only trigger once per change in inputs.

Related issue number

Checklist

  • I think the code is well written
  • I updated the table of contents (make toc)
  • Unit tests for the changes exist
  • Documentation reflects the changes
  • Runs in the swarm
  • If you design a new module, add your user to .github/CODEOWNERS

@GitHK GitHK changed the title Fix too eager detection Fixed issue where the detection was also running on the output folder triggering a chain update event Nov 15, 2024
@GitHK GitHK self-assigned this Nov 15, 2024
@GitHK GitHK added the t:bug Something isn't working label Nov 15, 2024
@GitHK GitHK added this to the Event Horizon milestone Nov 15, 2024
@GitHK GitHK marked this pull request as ready for review November 15, 2024 09:02
@GitHK GitHK merged commit 41a9dc7 into master Nov 15, 2024
1 check passed
@GitHK GitHK deleted the fix-too-eager-detection branch November 15, 2024 09:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
t:bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants