Looks like commit b043befaf6c67530a2ea13b266d17240cddd7180 broke something. It keeps throwing the error "File does not exist or is unreadable".
Description
Description
Details
Details
Related Changes in Gerrit:
| Subject | Author | Repo | Branch | Lines +/- | |
|---|---|---|---|---|---|
| Make Git2Pages respect proxy using $wgHTTPProxy | Galorefitz | mediawiki/extensions/Git2Pages | master | +26 -4 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Galorefitz | T115206 "File does not exist or is unreadable" behind a proxy | |||
| Resolved | Dereckson | T117954 Implement a method to get proxy value from $wgHTTPProxy and http_proxy |
Event Timeline
Comment Actions
The issue seems to be proxy related. The extension doesn't seem to be accounting for proxy settings.
Comment Actions
So taking care of proxy settings solves the issue of cloning repositories hosted online, but when the extension tries to clone a local repository, it gives a memory error and dies.
remote: Counting objects: 226, done. remote: fatal: Out of memory, calloc failed error: git upload-pack: git-pack-objects died with error. fatal: git upload-pack: aborting due to possible repository corruption on the remote side. remote: aborting due to possible repository corruption on the remote side. fatal: protocol error: bad pack header error: Could not fetch origin
or
fatal: Out of memory? mmap failed: Cannot allocate memory fatal: The remote end hung up upon initial contact error: Could not fetch origin fatal: Out of memory? mmap failed: Cannot allocate memory fatal: The remote end hung up upon initial contact
I am not sure how this can be fixed. I am not even sure I understand why it's throwing this error.
Comment Actions
There is another error. The branch, when entered, gets escaped twice. Gonna submit a patch right now fixing the proxy issue. Cloning from local repos still doesn't work.
Comment Actions
Change 250055 had a related patch set uploaded (by Galorefitz):
Make Git2Pages respect proxy using $wgHTTPProxy
Comment Actions
Change 250061 had a related patch set uploaded (by Galorefitz):
Remove mutliple wfEscapeShelArg() calls on $branch
Comment Actions
For the memory error - there's an extra argument you can add to wfShellExec to override built in memory limits. Might be good to add a config variable to the extension to set a different memory limit then the default one, which is usually quite restrictive.
Comment Actions
There were two patches. The one for this bug is already submitted. I ended up submitting another one after that (the one that was for a different bug).