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

Make a clean interface for jobs #939

Open
wants to merge 13 commits into
base: main
Choose a base branch
from

Conversation

javiermtorres
Copy link
Contributor

What's changing

Work in a cleaner job/backend interface mechanism

Refs #413

How to test it

Steps to test the changes:

Additional notes for reviewers

Anything you'd like to add to help the reviewer understand the changes you're proposing.

I already...

  • Tested the changes in a working environment to ensure they work as expected
  • Added some tests for any new functionality
  • Updated the documentation (both comments in code and product documentation under /docs)
  • Checked if a (backend) DB migration step was required and included it if required

@javiermtorres javiermtorres changed the title Javiermtorres/issue 413 separate interfaces Make a clean interface for jobs Feb 19, 2025
@javiermtorres javiermtorres force-pushed the javiermtorres/issue-413-separate-interfaces branch 2 times, most recently from 749e962 to 411d8d7 Compare February 21, 2025 16:29
@javiermtorres javiermtorres marked this pull request as ready for review February 21, 2025 16:29
@@ -173,6 +173,7 @@ services:
- RAY_WORKER_GPUS_FRACTION
- LUMIGATOR_API_CORS_ALLOWED_ORIGINS
- MLFLOW_TRACKING_URI
- PYTHONPATH=/mzai/lumigator/backend:/mzai/lumigator/jobs
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like this should go into the dockerfile? This is required for the thing to work

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't like hard coding these paths into the docker file. We may need more flexibility. Let's talk about it on Monday.

Copy link
Contributor

@njbrake njbrake left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think there was a bad merge because there are still some changes in here that we've discussed previously

@javiermtorres javiermtorres force-pushed the javiermtorres/issue-413-separate-interfaces branch from 411d8d7 to fc162ce Compare February 21, 2025 16:41
@javiermtorres
Copy link
Contributor Author

@njbrake yes, I'll try to go through the usual suspects (mlflow, services/jobs)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants