re-initializing bash complains about happi completion

[tangkong]

(pcds-5.3.1) [roberttk@psbuild-rhel7-01  ~]$ bash
bash: complete: happi: no completion specification
(pcds-5.3.1) [roberttk@psbuild-rhel7-01  ~]$

I don't know where this comes from but I'm looking around

[klauer]

Try bash -v?

[tangkong]

...
. "/cds/group/pcds/pyps/conda/py39/envs/pcds-5.3.1/etc/conda/deactivate.d/happi.sh"
#!/bin/bash
# This deactivates fzf-based fuzzy finding for happi searches.
# This is meant to be sourced from bash.

if [[ "${BASH}" =~ .*"bash" ]]; then
    # Do nothing
    :
else
    echo "'happi' deactivation: only bash shell is supported. Used shell: ${BASH}"
    return
fi

[ -n "$BASH" ] && complete -r happi
bash: complete: happi: no completion specification
...

Apparently happens on sourcing pcds_conda.
I also can't reproduce the output by manually activating/deactivating environments... weird. I wonder how much of a "just me" problem this is.

[klauer]

I can reproduce it with:

$ source pcds_conda
$ bash

and having the 'conda initialize' blurb in my own bashrc, but not otherwise.

conda initialize

# >>> conda initialize >>>
# !! Contents within this block are managed by 'conda init' !!
__conda_setup="$('/cds/home/k/klauer/miniforge3/bin/conda' 'shell.bash' 'hook' 2> /dev/null)"
if [ $? -eq 0 ]; then
    eval "$__conda_setup"
else
    if [ -f "/cds/home/k/klauer/miniforge3/etc/profile.d/conda.sh" ]; then
        . "/cds/home/k/klauer/miniforge3/etc/profile.d/conda.sh"
    else
        export PATH="/cds/home/k/klauer/miniforge3/bin:$PATH"
    fi
fi
unset __conda_setup
# <<< conda initialize <<<

My guess is that the above sees an active environment based on environment variables, tries to deactivate it, but completion information isn't transferred to the sub-shell that we just started?