Closed ijakas-syn closed 1 year ago
@bradegler Do you have any ideas what could be causing this? The action looks fine and I can't seem to figure out why it isn't working.
@ijakas-syn - my apologies, I didn't see the comment in the previous issue. Can you test directly against the SHA of the commit? My suspicion is that the v0
tag is your issue. If this works I'll get a new release cut for you.
- id: notebook-review
uses: 'google-github-actions/run-vertexai-notebook@2bf5927d84b327136b45692e7b21c85a3204e06e'
with:
gcs_source_bucket: '${{ env.GCS_SOURCE }}'
gcs_output_bucket: '${{ env.GCS_OUTPUT }}'
allowlist: '${{ needs.changes.outputs.notebooks_files }}
That is a good use case for this action. I'm excited to hear if you get it working and please continue to reach out as you have issue - happy to help.
Thanks for the response, it works perfectly when I test directly against the SHA of the commit. Maybe you can just change the input name of the kernel variable in the README to kernel_name
before for the new release.
TL;DR
I still have the same problem when it comes to running the notebook on Vertex. The last commit should have changed it but there is still no value for the kernel name.
Expected behavior
Arguments: --input-notebook=bucket/somedir_sample_notebook.ipynb; --output-notebook=bucket/somedir_sample_notebook.ipynb; --kernel-name=python3;
Observed behavior
Arguments: --input-notebook=bucket/somedir_sample_notebook.ipynb; --output-notebook=bucket/somedir_sample_notebook.ipynb; --kernel-name=
Action YAML
Log output
Additional information
Sorry for raising such a similar issue to the last one, I left a comment on it but I don't know if you have seen it since the issue is closed. Don't want to bother you, I have an idea for a simple MLOps project utilizing Vertex AI and this would be a great way to both deploy the pipelines from the notebook and have version control so I am excited to try it out.