Skip to content

msglist test: Make double-fetch-glitch test robust to layout changes #285

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
Aug 25, 2023

Conversation

gnprice
Copy link
Member

@gnprice gnprice commented Aug 24, 2023

Since adding this test, we've repeatedly seen it break upon changes that affect how tall the messages are:
https://chat.zulip.org/#narrow/stream/243-mobile-team/topic/flutter.3A.20double-fetch.20glitch.20gone.3F/near/1631114
e.g. in #245 as I was about to merge it just now.

In particular, the length of this pump for the fling-scroll has needed adjustments. Automate that by just finding out empirically how far is far enough to trigger the fetch, and proceeding from there.

Since adding this test, we've repeatedly seen it break upon
changes that affect how tall the messages are:
  https://chat.zulip.org/#narrow/stream/243-mobile-team/topic/flutter.3A.20double-fetch.20glitch.20gone.3F/near/1631114

In particular, the length of this pump for the fling-scroll has
needed adjustments.  Automate that by just finding out empirically
how far is far enough to trigger the fetch, and proceeding from there.
@chrisbobbe
Copy link
Collaborator

Thanks! Merging.

@chrisbobbe chrisbobbe merged commit 8831c2d into zulip:main Aug 25, 2023
@gnprice gnprice deleted the pr-test branch August 25, 2023 19:39
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.

2 participants