What happened in your environment?
- when i exec
oras push xxx/xxx/test:v1 test.txt ,then i got a fail msg . but i add the --debug flag ,like oras push xxx/xxx/test:v1 test.txt --debug. it push successfully.
- this problem dose not apper in normal registry,like harbor,docker hub
- i catch access log find that when i exec cmd
oras push xxx/xxx/test:v1 test.txt, the url of calling get service token like this https://127.0.0.1/service/token?service=hg-registry&scope=repository%3Ahg-ns1%2Ftest%3Apull and when i exec cmd oras push xxx/xxx/test:v1 test.txt --debug,the url is https://127.0.0.1/service/token?service=hg-registry&scope=repository%3Ahg-ns1%2Ftest%3Apush%2Cpull
there is something diff between within --debug and without --debug
What did you expect to happen?
No response
How can we reproduce it?
just exec the command and catch access log
What is the version of your ORAS CLI?
from 1.2.0 to latest 1.2.2 also has this problem
What is your OS environment?
every linux system
Are you willing to submit PRs to fix it?
What happened in your environment?
oras push xxx/xxx/test:v1 test.txt,then i got a fail msg . but i add the--debugflag ,likeoras push xxx/xxx/test:v1 test.txt --debug. it push successfully.oras push xxx/xxx/test:v1 test.txt, the url of calling get service token like thishttps://127.0.0.1/service/token?service=hg-registry&scope=repository%3Ahg-ns1%2Ftest%3Apulland when i exec cmdoras push xxx/xxx/test:v1 test.txt --debug,the url ishttps://127.0.0.1/service/token?service=hg-registry&scope=repository%3Ahg-ns1%2Ftest%3Apush%2Cpullthere is something diff between within
--debugand without--debugWhat did you expect to happen?
No response
How can we reproduce it?
just exec the command and catch access log
What is the version of your ORAS CLI?
from 1.2.0 to latest 1.2.2 also has this problem
What is your OS environment?
every linux system
Are you willing to submit PRs to fix it?