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.

Sign up for GitHub

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

Jump to bottom

xtriggers not sequence-specific #3283

Closed
hjoliver opened this issue Aug 11, 2019 · 0 comments · Fixed by #3287
Closed

xtriggers not sequence-specific #3283

hjoliver opened this issue Aug 11, 2019 · 0 comments · Fixed by #3287
Assignees
@hjoliver
Labels
bug
Milestone
cylc-7.8.4

Comments

@hjoliver
Copy link
Member

hjoliver commented Aug 11, 2019 •
edited

Describe the bug

Unlike task triggers, xtriggers are not being tied to the cycling sequence. So a task that has different xtriggers in different sequences will end up getting all the xtriggers every time.

REF: https://cylc.discourse.group/t/different-clock-triggers-for-different-cycles/120

Credit @trwhitcomb for finding this 👍

Release version(s) and/or repository branch(es) affected?

Up to and including 7.8.3

Pull requests welcome!
This is an Open Source project - please consider contributing a bug fix
yourself (please read CONTRIBUTING.md before starting any work though).
@hjoliver hjoliver added the bug label Aug 11, 2019
@hjoliver hjoliver added this to the next-release milestone Aug 11, 2019
@hjoliver hjoliver self-assigned this Aug 11, 2019
This was referenced Aug 12, 2019
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hjoliver hjoliver

Labels
bug
Projects
None yet
Milestone
cylc-7.8.4
Development

Successfully merging a pull request may close this issue.

xtrigger sequence fix - master hjoliver/cylc-flow
1 participant
@hjoliver