I've been using VSCode to create/update GitHub repros for a long time, but today I have a new problem. I can't create/upload a new Rust project, but I can create/upload a non-Rust project. I need to ask if there's anything different with a Rust project to any other type.
However, I did rename the project before trying to commit. I renamed the main folder from XXX to XXX-YYY-ZZ, and also the name in Cargo.toml and Cargo.lock. Is this the problem, or is there something wrong with the name?
What error are you getting, at what step of the process? Please quote (or screenshot if necessary) the error exactly.
Latest attempt...
2025-03-04 20:54:17.370 [info] > git ls-files --stage -- /Users/mike/Documents/Rust/Atomic-Repeater-v5/Cargo.toml [19ms]
2025-03-04 20:54:17.371 [info] > git show --textconv :Cargo.toml [21ms]
2025-03-04 20:54:17.387 [info] > git cat-file -s a65be93a0832e4fcac4bc194b684c4b91e174ec5 [17ms]
2025-03-04 20:54:31.774 [info] > git log --format=%H%n%aN%n%aE%n%at%n%ct%n%P%n%D%n%B -z --shortstat --diff-merges=first-parent -n50 --skip=0 --topo-order --decorate=full --stdin [164ms]
2025-03-04 20:54:44.353 [info] > git push -u origin main [6538ms]
2025-03-04 20:54:44.353 [info] error: RPC failed; HTTP 400 curl 22 The requested URL returned error: 400
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly
Everything up-to-date
2025-03-04 20:54:44.369 [info] > git config --get commit.template [15ms]
2025-03-04 20:54:44.369 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/main refs/remotes/main [14ms]
2025-03-04 20:54:44.385 [info] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [14ms]
2025-03-04 20:54:44.390 [info] > git status -z -uall [20ms]
What program is this a log from? What command did you give it?
The program is Visual Studio Code (VSCODE), and the command is executed by the button labeled Publish Branch, which exec git push -u origin main. Of course, the project had previously been committed to the local repro.
PS the full command with error...
git push -u origin main
error: RPC failed; HTTP 400 curl 22 The requested URL returned error: 400
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly
Everything up-to-date
The requested URL returned error: 400 suggests that the remote repository you are trying to push to does not exist. This indicates your local repository’s remote configuration is incorrect. Perhaps you set it up before you decided to rename your project?
Run git remote -v to see what the current configuration for the remote origin is.
To fix the problem (if this is the problem), run git remote set-url origin <URL goes here> with the proper repository URL provided by GitHub.
After a lot of experiment, creating, deleting GitHub repros and using new local repros, I think I've identified the problem...
If any file has extended attributes, the repro becomes useless after attempting to commit to GitHub.. IE if a file permissions ends with an "at" character.
This seems ridiculous, but if this is the case perhaps Microsoft is to blame.
As far as I remember, this is the first time I've used git on macOS. I normally develop on which ever linux m/c I'm deploying on - but using VSCode Remote SSH from the Mac to edit and compile. It makes life easy for me.
My latest investigation discovered: I can commit using the Microsoft GitHub Desktop App, but not with their Visual Studio. Both are the latest versions downloaded today. This is on a Mac, so I shouldn't be surprised.