//! when it is called 'rustc' it behaves as a proxy to 'rustc'. //! //! This scheme is further used to distinguish the Rustup installer, //! called 'rustup-init', which is again just the rustup binary under a //! different name. rami3l mentioned this issue Aug 22, 202...
Hi, rustup-init is unable to fetch data from behind my proxy: sdass@xxxxxxx:~ > rustup-init -v -y --default-toolchain nightly verbose: installing toolchain 'nightly-x86_64-unknown-linux-gnu' verbose: toolchain directory: '/home/sdass/.ru...
By company size Enterprises Small and medium teams Startups By use case DevSecOps DevOps CI/CD View all use cases By industry Healthcare Financial services Manufacturing Government View all industries View all solutions Resources Topics AI DevOps Security Software Development View all...
(dataPath: URL.applicationSupportDirectory.path(percentEncoded: false).appending("/").appending(UUID().uuidString), cachePath: URL.cachesDirectory.path(percentEncoded: false).appending("/").appending(UUID().uuidString)) .slidingSyncVersionBuilder(versionBuilder: .proxy(url: "https://ssync.dev....
[command]git config --get-all http.proxy 2019-11-21T16:22:29.1631478Z ##[command]git -c http.extraheader="AUTHORIZATION: basic ***" fetch --force --tags --prune --progress --no-recurse-submodules --depth=2 origin +refs/heads/*:refs/remotes/origin/* +refs/pull/66547/merge:refs/...
Running git config --global --unset http.proxy before npm init wasm-app www fixed it for me. FWIW, I don't think that's the core issue, since I've have never had git configured to use a proxy. The script for cloning the project is fairly simple. Given the fact that this bug ...