Skip to content

Fault recovery policy #11

@makingthematrix

Description

@makingthematrix

Sometimes an event source is based on a function that may throw an exception. For now, there is no established policy how to deal with it and no unit tests. Generators ignore failures and keep going, but in some other cases the event source might stop working.

I'm thinking of an enum:

enum RecoveryPolicy:
  case Ignore
  case Panic
  case RetryAndIgnore(attempts: Int)
  case RetryAndPanic(attempts: Int)

It would be given to an event source on creation (Ignore could be the default option) and all subsequent event sources created by transformations would get the same as the original one. In case of .zip a priority would have to be decided.

More later.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions