Open jmshelby opened 10 years ago
Ugh, super annoying. Can you send me/upload the actual tar file you're using?
it looks like it might be this setting:
'path_output' => 'var/package',
If it's inside the current directory (or anything relative) it seem to have this problem (maybe tar'ing itself in an endless loop). What really threw me was when I changed the path output to '~/some_other_dir' and it still happened ... it's because the tilde wasn't special for some reason, and it thought that I was specifying the '~/' dir relative from where I was running (same as 'var/package', a relative directory).
Only when I changed the output path to an absolute path (i.e. /Users/jmshelby/...) did the script finally work for me. So I think that's the answer: the path_output config requires an absolute path (or maybe just outside of your project path) and tilde's aren't special for some reason.
So might not be an issue exactly .... but good to know ...
Just playing around a little more ... it looks like it's fine to use a directory inside my current project, so long as the 'path_output' value is an absolute path. So just using DIR. '/var/package' works just fine.
THanks for the research -- I'll see if we can get a bug fix in place so this doesn't happen -- or at least the command fails with a warning instead of spinning off forever like that.
When I try running this script (as the phar packaged on master), it seems to get past untar'ing, and then either freezes up, or goes into an endless loop where all my memory get's taken up and I have to kill the process. No sign of any package or output file getting created.
Here is the output of packaging up astorm/PulsestormLauncher (as a quick example):