New validation checks/tests added in the past month are not SHELL agnostic and can create problems with users not using BASH as their SHELL. A simple bypass command-line option to avoid this validation checklist prior to job submission to the scheduler should help these users continue to use galyleo in the near-term. However, long-term the best solution would be to either create SHELL agnostic checks/tests and/or create checks/tests that are specific to the most common SHELLs in use and have galyleo use the appropriate checks based on the user's SHELL.
mkandes
commented
2 years ago
New validation checks/tests added in the past month are not SHELL agnostic and can create problems with users not using BASH as their SHELL. A simple bypass command-line option to avoid this validation checklist prior to job submission to the scheduler should help these users continue to use galyleo in the near-term. However, long-term the best solution would be to either create SHELL agnostic checks/tests and/or create checks/tests that are specific to the most common SHELLs in use and have galyleo use the appropriate checks based on the user's SHELL.