[wp-hackers] Future Posting Fix Request
false.hopes at gmail.com
Tue Jul 25 18:24:00 GMT 2006
On 7/25/06, Andy Skelton <skeltoac at gmail.com> wrote:
> When I wrote the Argyle pinging code that would eventually be pasted
> into the cron code, it worked beautifully on every machine I tested. I
> mean it was a thing of perfect beauty. Then it got committed to core
> and hell broke loose for a small fraction of testers. I grabbed one of
> the afflicted and got access to his server for experimentation. That
> was several months ago now so the details are fading from memory but I
> will try to illuminate this thread with what I can recall.
> The exact issue is not that PHP as CGI cannot open the socket to the
> local machine. The socket opens and the targeted script begins to run.
> At some point during execution, a conspiracy of factors causes the
> script to abort without any errors. Output was one factor I recall
> finding; an echo or a print would halt the script. That was easily
> fixed. The second factor was tougher. Opening another socket (e.g. a
> pingback to another blog) was okay but a subsequent attempt to open a
> socket would kill the script.
>From what I've tried (which lasted a whole 5 minutes before I had to
run off and forgot all about it for a while), I couldn't even get the
socket to open. Hopefully, however, you're right on this. Later
tonight I will potentially try to set up an Apache + CGI PHP + xdebug2
and APD and see what I can find. If that doesn't work, I'll start
doing stack traces (I need the practice for my PHP extension writing
anyways) and hopefully whatever it is, we can fix the problem. If
anyone has any secondary setup where the future posting stuff is known
to fail, and would like to donate a bit of space for testing, it would
be greatly appreciated.
> This should be tested again by someone who can reproduce the problem.
> The code is now very different from what I remember writing.
I know I modified a little bit of the sockets code, what I thought may
have been just for clarity at the time, but its been a while since I
looked at the cron code as well, so who knows? :D
More information about the wp-hackers