bash script passed to stdin fails after first gum call, unless wrapped in other control flow

[taigrr]

To Reproduce
Steps to reproduce the behavior:
put the following into script.sh:

#!/usr/bin/env bash

A=$(gum input --prompt='AAA: > ' --value='aaa')
B=$(gum input --prompt='BBB: >' --value='bbb')

then run cat script.sh | bash and see that only the first prompt runs.
(if you just run ./script.sh the script behaves as expected.)

Expected behavior
Both prompts should run, and the script should behave the same way when piped as when executed directly.

Similarly:

#!/usr/bin/env bash

A=$(gum input --prompt='AAA: > ' --value='aaa')
echo $A
echo "you won't see $A or this line print out"

Desktop (please complete the following information):

• OS: Linux

Additional context
The script will work if you wrap it in additional control flow:

#!/usr/bin/env bash
if true; then
A=$(gum input --prompt='AAA: > ' --value='aaa')
B=$(gum input --prompt='BBB: >' --value='bbb')
fi

Relevant discord thread

[piero-vic]

This happens because gum input also reads from stdin to set the value. In this case it's reading the part of the content of script.sh. Try run the script without setting the value of gum input.

#!/usr/bin/env bash

A=$(gum input --prompt='AAA: > ')
B=$(gum input --prompt='BBB: >')

You will probably see this.

You can use process substitution if you really need the redirection. It works for me.

bash <(cat script.sh)

[taigrr]

Thanks, but I think you might be describing a different issue. I'm not seeing STDIN eaten. In the coming days I can post a gif.