-
Notifications
You must be signed in to change notification settings - Fork 9
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
Make ArtifactCallback
work for puts to remote repositories
#123
Comments
@quintesse Let me check out the code ... after 1M years ... |
@quintesse afais, AbstractNodeRepositoryManager.addContent() has it's only impl in RootRepositoryManager. |
@alesj as you can read from the |
And after some more debugging I can tell you that when uploading the |
@quintesse ok, I must admit I don't follow all the details. When I added it, I tried to find the right download place, |
Well it was not so much that I was asking for permission but for help because I'm not sure at all how to do it ;) But I'll just see what I can break ;) |
Right now the
ArtifactCallback
is only called when downloading something from a remote repository and ignored when uploading to it.Although there might be a different way to solve this, because I'd also like for the callback to be used for local operations, so that for example a copy operation from one local repo to another would also use the callback.
That way the progress report for uploading would automatically work because it would really be showing the progress of the read operations of the local repository.
Thing is all those operations go through
AbstractNodeRepositoryManager.addContent()
and not throughRootRepositoryManager.putContent()
where the callback is being handled and I'm not sure what the best way is to handle this. Wdyt @alesj ?The text was updated successfully, but these errors were encountered: