Skip to content

Coalesce nodes should wait for 3 subsequent values before unsubscribing from previous node #1332

@shsms

Description

@shsms

What happened?

On slow component streams, the resampler takes time to stabilize on a value. During this time, there will be intermittent values in original streams. This causes the coalesce nodes to cycle between subscribing and unsubscribing from next components.

What did you expect instead?

Coalesce nodes should unsubscribe from secondary sources only when the primary has stabilized with at least 3 subsequent good values.

Affected version(s)

No response

Affected part(s)

Data pipeline (part:data-pipeline)

Extra information

No response

Metadata

Metadata

Assignees

Labels

priority:highAddress this as soon as possibletype:bugSomething isn't working

Type

No type

Projects

Status

To do

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions