mirror of
https://github.com/vale981/ray
synced 2025-03-06 02:21:39 -05:00
5d6bc5360d
## Why are these changes needed? - Fixes the jobs tab in the new dashboard. Previously it didn't load. - Combines the old job concept, "driver jobs" and the new job submission conception into a single concept called "jobs". Jobs tab shows information about both jobs. - Updates all job APIs: They now returns both submission jobs and driver jobs. They also contains additional data in the response including "id", "job_id", "submission_id", and "driver". They also accept either job_id or submission_id as input. - Job ID is the same as the "ray core job id" concept. It is in the form of "0100000" and is the primary id to represent jobs. - Submission ID is an ID that is generated for each ray job submission. It is in the form of "raysubmit_12345...". It is a secondary id that can be used if a client needs to provide a self-generated id. or if the job id doesn't exist (ex: if the submission job doesn't create a ray driver) This PR has 2 deprecations - The `submit_job` sdk now accepts a new kwarg `submission_id`. `job_id is deprecated. - The `ray job submit` CLI now accepts `--submission-id`. `--job-id` is deprecated. **This PR has 4 backwards incompatible changes:** - list_jobs sdk now returns a list instead of a dictionary - the `ray job list` CLI now prints a list instead of a dictionary - The `/api/jobs` endpoint returns a list instead of a dictionary - The `POST api/jobs` endpoint (submit job) now returns a json with `submission_id` field instead of `job_id`. |
||
|---|---|---|
| .. | ||
| public | ||
| src | ||
| .env.production.local | ||
| .gitignore | ||
| package-lock.json | ||
| package.json | ||
| README.rst | ||
| tsconfig.json | ||
This project was bootstrapped with `Create React App <https://github.com/facebook/create-react-app>`__. Available Scripts ----------------- In the project directory, you can run: ``npm start`` ~~~~~~~~~~~~~ Runs the app in the development mode. Open `http://localhost:3000 <http://localhost:3000>`__ to view it in the browser. The page will reload if you make edits. You will also see any lint errors in the console. ``npm test`` ~~~~~~~~~~~~ Launches the test runner in the interactive watch mode. See the section about `running tests <https://facebook.github.io/create-react-app/docs/running-tests>`__ for more information. ``npm run build`` ~~~~~~~~~~~~~~~~~ Builds the app for production to the ``build`` folder. It correctly bundles React in production mode and optimizes the build for the best performance. The build is minified and the filenames include the hashes. Your app is ready to be deployed! See the section about `deployment <https://facebook.github.io/create-react-app/docs/deployment>`__ for more information. ``npm run eject`` ~~~~~~~~~~~~~~~~~ Note: this is a one-way operation. Once you ``eject``, you can’t go back! If you aren’t satisfied with the build tool and configuration choices, you can ``eject`` at any time. This command will remove the single build dependency from your project. Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except ``eject`` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own. You don’t have to ever use ``eject``. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it. Learn More ---------- You can learn more in the `Create React App documentation <https://facebook.github.io/create-react-app/docs/getting-started>`__. To learn React, check out the `React documentation <https://reactjs.org/>`__.