Cargo registry yuklamalari ishlaydi, ammo Git bog‘liqliklari muvaffaqiyatsiz

Cargo proksisini o‘zgartirishdan oldin ishlamagan source URLni o‘qing. Registry metadata, crate archive va Git dependency turli fetching va authentication paths ishlatishi mumkin. SSH Git URLga HTTPSdan boshqa transport arrangement ham kerak.

Cargo’ning tegishli HTTP requests uchun route shunday belgilanadi:

[http]
proxy = "http://203.0.113.10:8080"

Documentation endpointni HTTP proxyingiz bilan almashtiring. Public proxy ishlatishga ruxsat berilgan public registry path uchun candidates HTTP proxy listda bor. Bu external Git executable ayni configurationni olganini isbotlamaydi.

Agar ishlamagan source Git bo‘lsa, Cargo built-in implementation o‘rniga Git CLI tanlashi mumkin:

[net]
git-fetch-with-cli = true

CARGO_NET_GIT_FETCH_WITH_CLI=true uni bitta command uchun tanlaydi. External Git endi o‘zining proxy configuration va credentialsiga muhtoj. Bir xil launch environmentda bir xil Git URLni solishtiring; boshqa terminalda ishlaydigan unrelated repository test emas.

Missing revision, repository permission denial yoki SSH host-key error implementation almashtirilgandan keyin ham o‘sha muammo bo‘lib qoladi. Bu option supported client tanlash usuli, umumiy dependency repair emas.

Diagnosisni project yoki command scopeda saqlang: global Git va user Cargo settings boshqa workspacega ta’sir qilishi mumkin. Registry URL package data tanlaydi, intermediary emas. Git path ishlagach, to‘liq intended Cargo operationni qayta ishga tushiring, chunki archives, redirects va build-time downloads boshqa routes qo‘shishi mumkin.