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.

Sign up for GitHub

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

Jump to bottom

node not found when using oras.Copy with certain option #383

Closed
qweeah opened this issue Dec 12, 2022 · 1 comment · Fixed by #384
Closed

node not found when using oras.Copy with certain option #383

qweeah opened this issue Dec 12, 2022 · 1 comment · Fixed by #384

Comments

@qweeah
Copy link
Contributor

qweeah commented Dec 12, 2022 •
edited
Loading

When using oras.Copy to copy the below DAG, if FindSuccessors is provided and successors of a is obtained without fetching , then a not found error will be thrown when copying node a.

   +-> b
a -+-> c
   +-> d
@qweeah qweeah mentioned this issue Dec 12, 2022
Merged
@qweeah
Copy link
Contributor Author

qweeah commented Dec 12, 2022

Related to oras-project/oras#719

shizhMSFT pushed a commit that referenced this issue Dec 12, 2022
@qweeah
fix: use proxy when copying node with successors (#384)
4b1d016 
Resolves #383

Signed-off-by: Billy Zha <jinzha1@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: copy uncached nodes directly from source qweeah/oras-go
1 participant
@qweeah