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

RCOCOA-2285: Wire up the new progress notifications #8492

Merged
merged 15 commits into from May 2, 2024

Conversation

nirinchev
Copy link
Member

@nirinchev nirinchev commented Feb 19, 2024

This is based on a branch that is the result of merging #8539 and master. Will rebase once #8539 is merged. It depends on an unreleased Core version, so most of the workflows will fail.

Fixes #8476

Copy link
Collaborator

@dianaafanador3 dianaafanador3 left a comment

Choose a reason for hiding this comment

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

Overall everything looks pretty good on initial review. I left some comments and some questions. I guess this is missing some more testing but I do think the API is so simple there is not much to test here, but to test it against flexible sync.

contrib/Development.md Outdated Show resolved Hide resolved
Realm/ObjectServerTests/RealmServer.swift Show resolved Hide resolved
RealmSwift/Sync.swift Show resolved Hide resolved

Whenever the progress reporting mode is `forCurrentlyOutstandingWork`, that value
will monotonically increase until it reaches 1.0. If the progress mode is `reportIndefinitely`, the
value will monotonically increase until it reaches 1.0, but may subsequently decrease if new server data
Copy link
Collaborator

Choose a reason for hiding this comment

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

What happens if there is a download/upload while another download/upload happens?, wouldn't that mean that in some cases the value will not increase monotonically?

Copy link
Member Author

Choose a reason for hiding this comment

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

Hm.. good question, I'll try and investigate this.

Realm/RLMAsyncTask.h Outdated Show resolved Hide resolved
Realm/RLMSyncSession.h Outdated Show resolved Hide resolved
Realm/RLMSyncSession.mm Show resolved Hide resolved
Realm/ObjectServerTests/SwiftObjectServerTests.swift Outdated Show resolved Hide resolved
Realm/ObjectServerTests/SwiftObjectServerTests.swift Outdated Show resolved Hide resolved
@nirinchev nirinchev force-pushed the ni/progress-notifications branch 2 times, most recently from 2c4e1ff to bec6712 Compare April 23, 2024 11:21
@nirinchev nirinchev changed the base branch from master to ni/master+tg-app-services-split April 23, 2024 11:21
@nirinchev nirinchev marked this pull request as ready for review April 23, 2024 15:33
@nirinchev nirinchev changed the base branch from ni/master+tg-app-services-split to tg/app-services-split April 29, 2024 10:05
Base automatically changed from tg/app-services-split to master April 29, 2024 15:07
Copy link
Collaborator

@dianaafanador3 dianaafanador3 left a comment

Choose a reason for hiding this comment

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

LGTM! Just some minor comments

Realm/ObjectServerTests/SwiftFlexibleSyncServerTests.swift Outdated Show resolved Hide resolved
@nirinchev
Copy link
Member Author

The CI failures seem to be github related (502s).

@nirinchev nirinchev requested a review from tgoyne May 1, 2024 22:59
@nirinchev nirinchev merged commit 452588e into master May 2, 2024
3 checks passed
@nirinchev nirinchev deleted the ni/progress-notifications branch May 2, 2024 10:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support for progress notifications during bootstrap
3 participants