zsh-workers
 help / color / mirror / code / Atom feed
From: "Jun. T" <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Subject: Re: zargs with -P intermittently failing in zsh 5.9 and macOS
Date: Thu, 26 May 2022 20:21:53 +0900	[thread overview]
Message-ID: <76D2EBB8-A3C5-4466-82C2-ED2BBF919F44@kba.biglobe.ne.jp> (raw)
In-Reply-To: <F4E8CACF-ED46-4809-8977-37213538A0FE@kba.biglobe.ne.jp>


> 2022/05/26 17:57, Jun T <takimoto-j@kba.biglobe.ne.jp> wrote:
> 
>        curl -so /dev/null 'https://example.com' & _zajobs+=( $! )

Sorry, curl fails (connection refused) if I test on my another Mac
in my home.

#!/bin/zsh
f () { curl -so /dev/null 'https://example.com'; return 0 }
_zajobs=()
(   # works OK if not run in a subshell
    np=20   #  try increasing this if you do not get $? = 19
    for ((i=0; i<$np; ++i)); do
        f & _zajobs+=( $! )
    done

    #sleep 1    # works OK if 'sleep 1' is added here
    wait        # works OK if this line is commented out
    for p in $_zajobs; do
        wait $p
        echo $p $?
    done
)

With this f(), the first pid in $_zajobs has the highest probability
to give $? = 19. If I replace f() by
f {} { date > /dev/null }
that takes much shorter time, and set np=20, then I get $? = 19 only
sometimes (not frequently), and the last (or the second last) pid in
$_zajobs has high probability to fail.



  reply	other threads:[~2022-05-26 11:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24 16:09 Eric Nielsen
2022-05-24 17:32 ` Bart Schaefer
2022-05-24 20:21   ` Eric Nielsen
2022-05-24 20:35     ` Bart Schaefer
2022-05-26  8:57   ` Jun T
2022-05-26 11:21     ` Jun. T [this message]
2022-05-27  3:39     ` Bart Schaefer
2022-05-27  4:18       ` Lawrence Velázquez
2022-05-27  5:29       ` Jun T
2022-05-27 16:10         ` Bart Schaefer
2022-05-27 17:25           ` Jun. T
2022-05-29  3:30             ` Bart Schaefer
2022-05-29 14:47               ` Jun. T
2022-05-29 20:07                 ` Bart Schaefer
2022-05-30 11:16                   ` Jun T
2022-06-07  6:51                     ` Jun T
2022-06-09  2:56                       ` Bart Schaefer
2022-06-12 16:43                 ` Eric Nielsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=76D2EBB8-A3C5-4466-82C2-ED2BBF919F44@kba.biglobe.ne.jp \
    --to=takimoto-j@kba.biglobe.ne.jp \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).