Issues with submodules: Direct fetching of that commit failed.

[shaunsingh]

Describe the bug
git submodule update fails with the following output:

~/I/Upsilon (upsilon-dev ✓) λ git submodule update
Cloning into '/Users/shauryasingh/IdeaProjects/Upsilon/apps/atomic'...
Cloning into '/Users/shauryasingh/IdeaProjects/Upsilon/apps/rpn'...
Submodule path 'apps/atomic': checked out '69f7a06ba53eaae9ba2ab8f0c0318e2f77455f4d'
fatal: remote error: upload-pack: not our ref b51172c32fdfb5a36c7526799965d6f3da613d69
Fetched in submodule path 'apps/rpn', but it did not contain b51172c32fdfb5a36c7526799965d6f3da613d69. Direct fetching of that commit failed.

This is because you updated the submodules to use your forks (https://github.com/Lauryy06/Upsilon/commit/84d88a3e8d50a9f8665117fad7372008416f5066) but you didn't update the commits they were pinned to

I recommend you update those pins to match the latest commit on each repo

As expected, the commit before that (https://github.com/Lauryy06/Upsilon/commit/00b5d4b9fe58c7a018e9b31ae74a189bf464a23e) clones and builds just fine

To Reproduce
Steps to reproduce the behavior:

1. Clone repo
2. error should popup if you use the --recursive flag

Expected behavior
Upsilon should download/build as expected

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• Upsilon Version: [go to settings > about > Upsilon Version and type the version here]

[Lauryy06]

Thanks for the issue, I fixed it by pushing my changes on the RPN repository.