Skip to content

Re-think gap-jumping and stall-detection #3673

@joeyparrish

Description

@joeyparrish

I believe gap-jumping and stall-detection could use a redesign. It's not clear that the current algorithms were built with the right requirements in mind.

Let's use this issue:

  1. to discuss requirements and decide what we should be designing/building
  2. to track progress on rebuilding gap-jumping and stall-detection

In #3188 (comment), I suggested:

I would like to get rid of the "small/large" gap concept, to always jump gaps by default, and to completely rethink the behavior and triggers of gap-jumping. I also think it would benefit from combining with stall detection.

Here are other issues that may be related to gap-jumping and could/should be solved by whatever we do next:

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    To do

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions