Skip to content

refactor(follower): use normal feed for one-off changes #795

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

Merged
merged 1 commit into from
Apr 22, 2025

Conversation

eiri
Copy link
Contributor

@eiri eiri commented Apr 8, 2025

PR summary

Use normal feed mode for changes follower one-off FINITE mode.

Fixes: s1115 / i445

Note: An existing issue is required before opening a PR.

PR Checklist

Please make sure that your PR fulfills the following requirements:

  • The commit message follows the
    Angular Commit Message Guidelines.
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • New tests
  • Build/CI related changes
  • Documentation content changes
  • Other (please describe) - performance improvement

What is the current behavior?

Currently the changes follower uses longpoll feed type is for both start (LISTEN) and start_one_off (FINITE) cases.

What is the new behavior?

Switch to use the normal feed type for start_one_off (FINITE) mode to avoid waiting unnecessarily till timeout on empty feeds.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

@eiri eiri force-pushed the i445-follower-one-off branch from a298a14 to 6db629a Compare April 22, 2025 12:48
@ricellis ricellis merged commit 8be0fd7 into main Apr 22, 2025
10 checks passed
@ricellis ricellis deleted the i445-follower-one-off branch April 22, 2025 13:04
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

Successfully merging this pull request may close these issues.

3 participants