vertex-ai-samples
vertex-ai-samples copied to clipboard
feat: Add notebook for Wide & Deep on Vertex Pipelines
REQUIRED: Add a summary of your PR here, typically including why the change is needed and what was changed. Include any design alternatives for discussion purposes.
Adding a notebook to show how to use Wide & Deep on Vertex Pipelines.
REQUIRED: Fill out the below checklists or remove if irrelevant
- If you are opening a PR for
Official Notebooksunder the notebooks/official folder, follow this mandatory checklist:
- [x] Use the notebook template as a starting point.
- [x] Follow the style and grammar rules outlined in the above notebook template.
- [x] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
- [x] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
- [x] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
- [x] This notebook has been added to the CODEOWNERS file under the
Official Notebookssection, pointing to the author or the author's team. - [x] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.
- If you are opening a PR for
Community Notebooksunder the notebooks/community folder:
- [ ] This notebook has been added to the CODEOWNERS file under the
Community Notebookssection, pointing to the author or the author's team. - [ ] Passes all the required formatting and linting checks. You can locally test with these instructions.
- If you are opening a PR for
Community Contentunder the community-content folder:
- [ ] Make sure your main
Content Directory Nameis descriptive, informative, and includes some of the key products and attributes of your content, so that it is differentiable from other content - [ ] The main content directory has been added to the CODEOWNERS file under the
Community Contentsection, pointing to the author or the author's team. - [ ] Passes all the required formatting and linting checks. You can locally test with these instructions.
Check out this pull request on ![]()
See visual diffs & provide feedback on Jupyter Notebooks.
Powered by ReviewNB
File /workspace/workspace/env/lib/python3.9/site-packages/google/cloud/aiplatform/pipeline_jobs.py:461, in PipelineJob._block_until_complete(self) Step #5: Step #4: 458 # Error is only populated when the job state is Step #5: Step #4: 459 # JOB_STATE_FAILED or JOB_STATE_CANCELLED. Step #5: Step #4: 460 if self._gca_resource.state in _PIPELINE_ERROR_STATES: Step #5: Step #4: --> 461 raise RuntimeError("Job failed with:\n%s" % self._gca_resource.error) Step #5: Step #4: 462 else: Step #5: Step #4: 463 _LOGGER.log_action_completed_against_resource("run", "completed", self) Step #5: Step #4: Step #5: Step #4: RuntimeError: Job failed with: Step #5: Step #4: code: 9 Step #5: Step #4: message: "The DAG failed because some tasks failed. The failed tasks are: [exit-handler-1].; Job (project_id = python-docs-samples-tests, job_id = 5977069453404274688) is failed due to the above error.; Failed to handle the job: {project_number = 1012616486416, job_id = 5977069453404274688}"