Can't checkout f239034d5eb0790ee7639b2523367a71e298fd21 from libigl

[amlankar]

I was trying to clone the repository but it seems git can't checkout this commit (f239034d5eb0790ee7639b2523367a71e298fd21) from libigl.

What I've tried:

• This also happens if I try to clone the smoothing repository (it didn't happen when I did the assignment)
• I cloned only the libigl repository and tried to checkout this commit and I got the same error
• I can open https://github.com/libigl/libigl/tree/f239034d5eb0790ee7639b2523367a71e298fd21 in the browser just fine

[alecjacobson]

Thanks for pointing this out. I'm in the process of fixing gp assignments to work with libigl v2.0.0

[amlankar]

Closing since it worked for the other assignment.

[songfeil]

Hi, how did you solve the problem? Since when I was trying to clone the repo it reported:

• error: Server does not allow request for unadvertised object f239034d5eb0790ee7639b2523367a71e298fd21
• Fetched in submodule path 'shared/libigl', but it did not contain f239034d5eb0790ee7639b2523367a71e298fd21. Direct fetching of that commit failed.

And then it fails.

[amlankar]

Maybe this repo isn't fixed yet, the deformation assignment does work now.

…

On Thu, Oct 25, 2018 at 7:49 PM songfeil ***@***.***> wrote: Hi, how did you solve the problem? Since when I was trying to clone the repo it reported: - error: Server does not allow request for unadvertised object f239034d5eb0790ee7639b2523367a71e298fd21 - Fetched in submodule path 'shared/libigl', but it did not contain f239034d5eb0790ee7639b2523367a71e298fd21. Direct fetching of that commit failed. And then it fails. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#29 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHR5PID5QRAwRZN6ncMHVd4_aNbDgFxNks5uok31gaJpZM4Xex14> .

[alecjacobson]

I fixed it just now. Hopefully it works.

[songfeil]

Hi, it works now.
It seems I can't create a pull request from the original repo to my forked one since it said no changes, but deleting the repo and forking it again seems to apply the changes.
Thank you!