From: Eric Nielsen <ericbn@hey.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: zargs with -P intermittently failing in zsh 5.9 and macOS
Date: Tue, 24 May 2022 11:09:07 -0500 [thread overview]
Message-ID: <9162a41e493cabeb0c8fb7c770f6b35035a0be0e@hey.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1195 bytes --]
Hi, I'm seeing zargs with -P intermittently fail with in zsh 5.9 in
macOS. Here's the information I could gather so far.
Minimal reproducible example:
% f() { curl -Sso /dev/null 'https://example.com'; return 0 }
% autoload -Uz zargs
% setopt xtrace
% zargs -n 1 -P 0 -- {1..13} -- f
Expected the status code to be 0. Most of the times I get 123 instead.
The xtrace output shows:
+(eval):6> case 19 (<1-125>|128)
+(eval):8> ret=123
at least once, even though f always returned 0. Added the extra return 0
in f to force that return code.
If f is simplified, I don't see the error. If the -P 0 is removed, I
don't see the error. If the range is shortened, the error will be less
frequent. Even with {1..13} it happens to sometimes succeed in my Mid
2015 2.2 GHz Quad-Core Intel Core i7.
This is not reproducible with earlier versions of zsh or with the
/bin/zsh bundled with macOS (zsh version 5.8.1 in macOS 12.4). This is
reproducible with zsh 5.9 installed both via homebrew or macports. This
is so far not reproducible in other OSs.
Information comes from https://github.com/Homebrew/homebrew-
core/issues/101937 and https://github.com/zimfw/zimfw/discussions/459.
Kind regards,
Eric
[-- Attachment #2: Type: text/html, Size: 3737 bytes --]
next reply other threads:[~2022-05-24 16:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 16:09 Eric Nielsen [this message]
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
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=9162a41e493cabeb0c8fb7c770f6b35035a0be0e@hey.com \
--to=ericbn@hey.com \
--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).