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

Don't Latch on NotActive activation #11

Open
slominskir opened this issue Jul 16, 2024 · 3 comments
Open

Don't Latch on NotActive activation #11

slominskir opened this issue Jul 16, 2024 · 3 comments

Comments

@slominskir
Copy link
Member

The special NotActive activation placeholder appears to be triggering a Latch:

image

@slominskir
Copy link
Member Author

Similarly:

image

In the OnDelay case, this may be because state is ActiveLatched. We need to guard against OnDelay as well if NotActive, and perhaps also when Latched. This gets confusing as you start to mix and match overrides: JeffersonLab/jaws#24

@slominskir
Copy link
Member Author

Effective processor does not appear to latch on NoActivation. More investigation needed. Perhaps on startup some channels take too long to connect to EPICS and result in ChannelErrors, which eventually resolve to NotActive. In this case the issue might be the audit logger is capturing the wrong state: expected would be type ChannelError, not type NotActive.

@slominskir
Copy link
Member Author

The unexpected part is the activation type. Perhaps the stream join on override isn't grabbing the updated activation type? Starting from empty history a fresh restart results in the following notification history examples:

Example 1:
image

Example 2:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant