Repacking of the repository

[ktf]

I am doing:

git clone -n https://github.com/llvm/llvm-project /build/nomad/alloc/8740274f-f4f8-d560-be56-0eee5f040bd0/ci/local/o2-alidist-dataflow/sw/SOURCES/Clang/v15.0.7/llvmorg-15.0.7 --dissociate --reference /build/nomad/alloc/8740274f-f4f8-d560-be56-0eee5f040bd0/ci/local/o2-alidist-dataflow/sw/MIRROR/clang --filter=tree:0

and it takes relatively long doing the repacking of the repository due to the --dissociate.

I contacted the Github support and they told me that they can trigger some automated gc / optimisation on their side upon request, however it must be asked by the repository maintainer.

Any chance you could reach out to them and ask for such operation to be performed?

[Sirraide]

LLVM is a rather big repository with a long commit history, so cloning it can take a while in my experience; that said, I’m not really familiar w/ what --dissociate does...

CC @tstellar @boomanaiden154 I remember you being knowledgeable about github-related issues in the past, maybe you have an idea as to what we should do here?

[llvmbot]

@llvm/issue-subscribers-infrastructure

Author: Giulio Eulisse (ktf)

I am doing:

git clone -n https://github.com/llvm/llvm-project /build/nomad/alloc/8740274f-f4f8-d560-be56-0eee5f040bd0/ci/local/o2-alidist-dataflow/sw/SOURCES/Clang/v15.0.7/llvmorg-15.0.7 --dissociate --reference /build/nomad/alloc/8740274f-f4f8-d560-be56-0eee5f040bd0/ci/local/o2-alidist-dataflow/sw/MIRROR/clang --filter=tree:0

and it takes relatively long doing the repacking of the repository due to the --dissociate.

I contacted the Github support and they told me that they can trigger some automated gc / optimisation on their side upon request, however it must be asked by the repository maintainer.

Any chance you could reach out to them and ask for such operation to be performed?

[boomanaiden154]

I'm not too familiar with this. The last time this was brought up (from what I've seen) was in this thread on Discourse. @joker-eph handled it previously, although I guess any maintainer.

I'm not sure that will help too much in this case though given Github repacks across the entire fork network rather than just llvm/llvm-project itself. Might not be a bad idea to do this again though given it's been about a year.

[joker-eph]

I will ping them on the email thread I had with them right now.
It was disappointing last time because of how they operate across forks indeed :(

[joker-eph]

Just got an answer:

I have engaged my engineering team to perform this oepration. Once this has bene done I will be sure to update you here!

[singiamtel]

Any news on this?

[joker-eph]

They came back to me the next day to confirm it was done. I personally couldn't see a difference though :(