Skip to content
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

fix entry logic to not re-fetch data for the initial team #8349

Merged
merged 1 commit into from
Nov 18, 2024
Merged

Conversation

enahum
Copy link
Contributor

@enahum enahum commented Nov 15, 2024

Summary

We made some improvements to the performance of login here #8306 but there were two bugs that are fixed in this PR.

  1. We were requesting channels, posts and others for the initial team even though we already have that data.
  2. The exclusion of threads in DMs was checking for version 10.2.0 which is wrong, that PR just landed in master, so for the time being we just dedupe the models.

Ticket Link

N/A

Release Note

NONE

@enahum enahum added 2: Dev Review Requires review by a core commiter CherryPick/Approved Meant for the quality or patch release tracked in the milestone labels Nov 15, 2024
@enahum enahum added this to the v2.23.0 milestone Nov 15, 2024
@enahum enahum requested review from larkox and rahimrahman November 15, 2024 08:32
Copy link
Contributor

@rahimrahman rahimrahman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 quick question.

Comment on lines -293 to -297
// this is to keep backwards compatibility with servers that send the
// threads for DM / GM regardless for every team
const version = await getConfigValue(database, 'Version');
const hasThreadExclusions = isMinimumServerVersion(version, 10, 2, 0);

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can understand changes in the file /actions/remote/entry/common.ts, but what do these changes have anything to do with not re-fetching data for the initial team?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The initial team selected first is already fetching its data, here we were not filtering this fetching the same data again

@enahum enahum merged commit 59a49b3 into main Nov 18, 2024
31 checks passed
@mattermost-build
Copy link
Contributor

Cherry pick is scheduled.

@enahum enahum deleted the fix-entry branch November 18, 2024 09:49
mattermost-build pushed a commit that referenced this pull request Nov 18, 2024
@mattermost-build mattermost-build added CherryPick/Done Successfully cherry-picked to the quality or patch release tracked in the milestone and removed CherryPick/Approved Meant for the quality or patch release tracked in the milestone labels Nov 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2: Dev Review Requires review by a core commiter CherryPick/Done Successfully cherry-picked to the quality or patch release tracked in the milestone release-note-none
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants