You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a job task should run a notebook, the notebook_task.source indicates whether the path is a workspace path or should be located via the git-source configured in the job settings.
Currently we always treat the path on a notebook task as a workspace paths, which fails if it's a path relative to the git-source.
In the long-term: we should support linting these as well.
Additional Context
One of the downstream errors that we currently see is attempts to download workspace paths without a leading slash (/). (Such relative paths are invalid workspace paths.)
Here is where we (currently) do not distinguish between workspace and git-source paths. (Fixed in #2924.)
The text was updated successfully, but these errors were encountered:
we do support linting git repos with lint-local-code command. git integration works the way that only the owner of the git token can access the repo and no the administrator.
Is there an existing issue for this?
Problem statement
When a job task should run a notebook, the
notebook_task.source
indicates whether the path is a workspace path or should be located via the git-source configured in the job settings.Currently we always treat the path on a notebook task as a workspace paths, which fails if it's a path relative to the git-source.
Proposed Solution
Fixed
OSError: [Errno 95]
bug inassess_workflows
task by skipping GIT-sourced workflows from static code analysis #2924.Additional Context
One of the downstream errors that we currently see is attempts to download workspace paths without a leading slash (
/
). (Such relative paths are invalid workspace paths.)Here is where we (currently) do not distinguish between workspace and git-source paths.(Fixed in #2924.)The text was updated successfully, but these errors were encountered: