Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

read job_conf directly from config_dir instead of computing it again from config_file #15596

Merged
merged 2 commits into from Jun 20, 2023

Conversation

bernt-matthias
Copy link
Contributor

config_dir should be the same as os.path.dirname(self.app.config.config_file) but config_dir is computed anyway in the config module

How to test the changes?

(Select all options that apply)

  • I've included appropriate automated tests.
  • This is a refactoring of components with existing test coverage.
  • Instructions for manual testing are as follows:
    1. [add testing steps and prerequisites here if you didn't write automated tests covering all your changes]

License

  • I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

should be the same as `os.path.dirname(self.app.config.config_file)`
but `config_dir` is computed anyway in the config module
@github-actions github-actions bot added this to the 23.1 milestone Feb 16, 2023
@nsoranzo nsoranzo requested a review from jdavcs February 16, 2023 14:04
@nsoranzo nsoranzo added area/configuration Galaxy's configuration system kind/bug labels Feb 16, 2023
lib/galaxy/jobs/__init__.py Outdated Show resolved Hide resolved
Co-authored-by: Nicola Soranzo <nicola.soranzo@gmail.com>
@jdavcs jdavcs merged commit 3204092 into galaxyproject:dev Jun 20, 2023
@jdavcs
Copy link
Member

jdavcs commented Jun 20, 2023

Thank you, @bernt-matthias! (we should have merged this months ago!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/configuration Galaxy's configuration system area/jobs kind/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants