Closed shibayan closed 4 years ago
Yes, there is indeed some issue with large repos on Linux. @naziml may have more to say about it, though I don't think it's been solved.
Thanks. If the image is included, the size of the repository will increase, so I think it is a problem to be fixed. If I can install custom Kudu, I may be able to help with this problem :)
I'm very excited about App Service on Linux and Docker support.
/cc @nickwalkmsft who will help out with Kudu/Linux is the coming weeks.
Interesting finding. My 32MB repo deploys just fine and i did it quite a few times.
tmp$ du -sh gifinator
32M gifinator
gifinator$ git count-objects -vH
count: 0
size: 0 bytes
in-pack: 254
packs: 1
size-pack: 24.32 MiB
prune-packable: 0
garbage: 0
size-garbage: 0 bytes
Could be more to this story than just the repo size?
I was interested in this problem and I was investigating the cause.
This may be a problem with Mono / XSP. It is very troubling. When receiving a request with Transfer-Encoding: chunked, Mono seems to always return empty as InputStream.
However, it seems that this problem can be avoided by combining nginx and fastcgi-mono.
So it is a bug in mod_mono.
I investigated further, but this is a problem on Mono side. It seems only to wait for referencesource to be acquired or to avoid it with FastCGI.
If the repository size if large git push will fail.
When pushing about 10MB repository, the following trace was output.
Looking at the trace log, an error occurred when receive-pack was called twice. Increasing the size of http.postBuffer with git config avoided errors.
For reference, it is an error log that emphasizing yellow. You can see that receive-pack has been called multiple times. (This is the normal behavior of git)