-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
[Transfer ownership] Receiver not informed about transfer taking some time #18272
Labels
Milestone
Comments
wiswedel
added
bug
0. Needs triage
Pending check for reproducibility or if it fits our roadmap
labels
Dec 6, 2019
So we just update the initial acceptance notification that it can take some time? |
Fine for me |
Care to shoot in a PR yourself? SInce you already touched the code. And then you can word it how you think it should be worded ;) |
wiswedel
added a commit
that referenced
this issue
Dec 9, 2019
note about incoming transfer taken out by background job resolves #18272 Signed-off-by: Sascha Wiswedel <sascha.wiswedel@nextcloud.com>
gary-kim
pushed a commit
that referenced
this issue
Dec 16, 2019
note about incoming transfer taken out by background job resolves #18272 Signed-off-by: Sascha Wiswedel <sascha.wiswedel@nextcloud.com>
gary-kim
pushed a commit
that referenced
this issue
Dec 16, 2019
note about incoming transfer taken out by background job resolves #18272 Signed-off-by: Sascha Wiswedel <sascha.wiswedel@nextcloud.com>
gary-kim
pushed a commit
that referenced
this issue
Dec 16, 2019
note about incoming transfer taken out by background job resolves #18272 Signed-off-by: Sascha Wiswedel <sascha.wiswedel@nextcloud.com>
gary-kim
pushed a commit
that referenced
this issue
Dec 16, 2019
note about incoming transfer taken out by background job resolves #18272 Signed-off-by: Sascha Wiswedel <sascha.wiswedel@nextcloud.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
While the ownership transfer initiator sees a hint, It may take some time until the process is done, the receiver doesn't know that the transfer actually happens with the next background job (which could take some time, depending on the server config). So the receiver has to assume something went wrong after accepting but not seeing anything coming in.
The text was updated successfully, but these errors were encountered: