-
Notifications
You must be signed in to change notification settings - Fork 87
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
[BUG]: Assessment.assess_workflows
task fails with <class 'astroid.exceptions.AstroidSyntaxError>
#3457
Comments
Assessment.assess_workflows
task fails with <class 'astroid.exceptions.AstroidSyntaxError>
@bwmann89 : Thanks for reporting. The |
Sure @JCZuurmond I've attached the cluster logs for stdout, stderr, and log4jactive, as well as the task output, which is under parse_logs_run_output.txt. |
Hi @bwmann89 , could you share the output of the |
Hi @JCZuurmond my apologies, just attached assess_workflows task output, and this is for UCX 0.53.1, but I encountered the same issue. |
Could you share the logs by downloading the file from the logs folder? These logs are truncated: |
Yeah, just attached that. |
@bwmann89 : Thank you. The code being linted contains a syntax error as it contains Jupyter magic. Currently, we only support valid Python code, excluding Jupyter syntax, hence I marked this issue as a "won't fix". See the linked PR for more details, we expect you to solve this manually |
Is there an existing issue for this?
Current Behavior
parse_logs task is failing with the following error message repeated in the stderr output:
return`: <class 'astroid.exceptions.AstroidSyntaxError'>: Parsing Python code failed:
invalid syntax (, line 68). Report this as an issue on UCX GitHub.
Expected Behavior
This task should complete successfully without any errors
Steps To Reproduce
Databricks E2 environment with 0.52 version of UCX. Running UCX [assessment] job in an environment where we have many managed tables that are in a separate Glue catalog.
Cloud
AWS
Operating System
Linux
Version
latest via Databricks CLI
Relevant log output
The text was updated successfully, but these errors were encountered: