SLURM job crashes if Conda is not installed

[Andrew-S-Rosen]

Environment

• Covalent version: 0.220.0
• Covalent-Slurm plugin version: 0.12.1
• Python version: Python 3.9.16
• Operating system: Ubuntu

What is happening?

Note: this one is motivated by some "getting started" snags by a colleague of mine, @rwexler.

covalent-slurm-plugin/covalent_slurm_plugin/slurm.py

Lines 337 to 346 in bcf2049

	# sets up conda environment
	slurm_conda = f"""
	source $HOME/.bashrc
	conda activate {conda_env_str}
	retval=$?
	if [ $retval -ne 0 ] ; then
	>&2 echo "Conda environment {conda_env_str} is not present on the compute node. "\
	"Please create the environment and try again."
	exit 99
	fi

Because of this line, there is currently no way to use the plugin if you aren't using conda. There are many situations in which the user may not want to use an Anaconda environment. For instance, maybe the user is loading an HPC-hosted Python module, which they've installed packages with via pip. They would have to load the module in their prerun_commands but otherwise shouldn't be required to use conda.

How can we reproduce the issue?

Submit a job without conda in the PATH.

What should happen?

Covalent should support running with Python in the PATH but not necessarily relying on Conda.

Any suggestions?

Only add the conda-related lines if conda_env is not False.

[santoshkumarradha]

@arosen93 thank you for this ! this is an side effect of initial versions of covalent being only installable from conda due to few non python dependencies. But that's not the case now, I assume everything should work sans conda check. @wjcunningham7 can you confirm this?