maybe its by u using base64url and the first time not .. normal behavior
On Fri, Jan 29, 2021, 03:13 Jean-Jacques Brucker <
jeanjacquesbruc...@gmail.com> wrote:
>
> 100 % reproducible on my Debian, package version 5.1-2:
>
>
>
> $ echo "dc30a6d79f3b47e310b8b9f5fbadba57" | tee >( xxd -r -p | base
On Fri, Jan 29, 2021 at 12:33:17AM +0100, Jean-Jacques Brucker wrote:
> $ echo "dc30a6d79f3b47e310b8b9f5fbadba57" | tee >( xxd -r -p | base64) |
> tee >(xxd -r -p | basenc --base64url )
> dc30a6d79f3b47e310b8b9f5fbadba57
> 3DCm1587R+MQuLn1+626Vw==
> 3DCm1587R-MQuLn1-626Vz0Vhw==
Yes, there is a r
is commenting the #(if|endif) lines right way ?
cause.. it buggs still
im prepraring a paste with the codes and some bugs .. takes some time to
code the paste to flat text system and depaste
On Wed, Jan 27, 2021, 22:10 Chet Ramey wrote:
> On 1/27/21 4:07 PM, Alex fxmbsw7 Ratchev wrote:
> > tha
On 29/01/2021 19.50, Greg Wooledge wrote:
> Yes, there is a race condition bug, but it's in your script, not in bash.
It seems to come out in linear order. I think what we're seeing here is
what Oğuz observed:
$ echo -e 'dc30a6d79f3b47e310b8b9f5fbadba57
3DCm1587R+MQuLn1+626Vw==' |xxd -r -p |base6
On 1/28/21 6:33 PM, Jean-Jacques Brucker wrote:
100 % reproducible on my Debian, package version 5.1-2:
$ echo "dc30a6d79f3b47e310b8b9f5fbadba57" | tee >( xxd -r -p | base64) |
tee >(xxd -r -p | basenc --base64url )
dc30a6d79f3b47e310b8b9f5fbadba57
3DCm1587R+MQuLn1+626Vw==
3DCm1587R-MQuLn
On 1/29/21 7:50 AM, Alex fxmbsw7 Ratchev wrote:
is commenting the #(if|endif) lines right way ?
cause.. it buggs still
You have to uncomment the fix; that one's not live.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
C
im sorry big time.. can you point me out how
i just commented the #if and #endif s , thought thatd enable the code .. in
parse and tab
On Fri, Jan 29, 2021, 14:57 Chet Ramey wrote:
> On 1/29/21 7:50 AM, Alex fxmbsw7 Ratchev wrote:
> > is commenting the #(if|endif) lines right way ?
> >
> > cause
Big thanks for all.
Indeed there is no bug, and IMO even nothing to improve in bash.
What put me wrong is that such erroneous command "work down" when first
"xxd -r -p | base64" output don't begin with hexadecimals characters.
This happens most often, and then second "xxd -r -p" will ignore
