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

Runtime error during startup since new release #4066

Closed
Jeblii opened this issue Aug 6, 2024 · 4 comments
Closed

Runtime error during startup since new release #4066

Jeblii opened this issue Aug 6, 2024 · 4 comments

Comments

@Jeblii
Copy link

Jeblii commented Aug 6, 2024

Description

Since the new release, we have noticed that a RuntimeError is raised whereas previously it did not. We are running jobs on databricks with Kedro pipeline; some jobs using python wheels and others as a notebook. We initialize the pipeline in the following manner

configure_project(self.package_name)
        with KedroSession.create(
            env: str =self.env,
            conf_source: pathlib.Path =self.conf_source,
            extra_params: Optional[dict] =self.runtime_params,
        ) as session:

Running the pipeline results in the following error:

RuntimeError: Pipeline encountered errors during the run: ["Failed to read the file: /databricks/driver/pyproject.toml.\n[Errno 2] No such file or directory: '/databricks/driver/pyproject.toml'"]<Title>

Expected Result

No error raised. I am not sure of the reason why a pyproject.toml has to be supplied on databricks.

Your Environment

  • Kedro version used (pip show kedro or kedro -V): 0.19.7
  • Python version used (python -V): 3.9
  • Operating system and version: Databricks 12.2 LTS
@merelcht
Copy link
Member

merelcht commented Aug 7, 2024

Hi @Jeblii, I happened to be testing things on Databricks yesterday, and I noticed the same message in my logs, but it's not actually causing failures for me. Are you sure there isn't another error that's the real issue?

@Jeblii
Copy link
Author

Jeblii commented Aug 12, 2024

My apologies! I wasn't fully clear in my opening message. It indeed does not raise actively, but it seems to log the message with level Error. We noticed that this wasn't the case before the latest release. Is this the expected behaviour?

@merelcht
Copy link
Member

@Jeblii , thanks for clarifying! This definitely isn't expected. I've created a ticket to address it: kedro-org/kedro-plugins#804. We'll prioritise to fix this.

@merelcht
Copy link
Member

Fixed in kedro-org/kedro-plugins#806

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

No branches or pull requests

2 participants