-
Notifications
You must be signed in to change notification settings - Fork 54
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
[NADE] Enable Code Generation by default in Snow App Bundle #1167
Conversation
e29182a
to
d3d2184
Compare
src/snowflake/cli/plugins/nativeapp/codegen/snowpark/python_processor.py
Outdated
Show resolved
Hide resolved
@@ -140,7 +140,7 @@ def _execute_in_sandbox( | |||
|
|||
if completed_process.returncode != 0: | |||
cc.warning( | |||
f"Could not fetch Snowpark objects from {py_file} due to the following error:\n {completed_process.stderr}" | |||
f"Could not fetch Snowpark objects from {py_file} due to the following Snowpark-internal error:\n {completed_process.stderr}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
errors here aren't necessarily snowpark
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My understanding is that any sandbox or execution environment based errors have been captured in lines 130 to 139. So if we get to this stage, we must have invoked the jinja file and then received a response accordingly. Is that incorrect?
Either way, I can remove the "Snowpark-internal" phrase.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Errors that can go to stderr include bugs in our driver and just Python errors in user code. Labelling them all as Snowpark would be misleading.
src/snowflake/cli/plugins/nativeapp/codegen/snowpark/callback_source.py.jinja
Show resolved
Hide resolved
src/snowflake/cli/plugins/nativeapp/codegen/snowpark/callback_source.py.jinja
Outdated
Show resolved
Hide resolved
src/snowflake/cli/plugins/nativeapp/codegen/snowpark/python_processor.py
Show resolved
Hide resolved
src/snowflake/cli/plugins/nativeapp/codegen/snowpark/callback_source.py.jinja
Show resolved
Hide resolved
src/snowflake/cli/plugins/nativeapp/codegen/snowpark/python_processor.py
Show resolved
Hide resolved
20291df
to
87b07a9
Compare
810a40b
to
a6f2fb0
Compare
commit for Mike's documentation
…import, introduced fn which relies on another in the same file
…sses when using real config.toml connection locally, pushing to test on Github now fix code quality failure, loosen restriction on checking stderr when CLI's config.toml has insufficient permissions
160fa78
to
b429cf6
Compare
Pre-review checklist
Changes description
Snowpark Annotation Processing in Native Apps through Code Generation of SQL is hidden behind a feature flag up until 2.4.0. But with 2.5.0, we want to make this widely available, without any feature flags. This PR removes the condition, and also adds an E2E test that ensures we get to a working app state.