Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
larger
environment. The workflow includes permissions for writing id-tokens, accessing issues, reading contents and pull-requests. It checks out the code with a full fetch-depth, installs Python 3.10, and uses hatch 1.9.4. The key step in this workflow is the execution of nightly tests using the databrickslabs/sandbox/acceptance action, which creates issues if necessary. The workflow utilizes several secrets, including VAULT_URI, GITHUB_TOKEN, ARM_CLIENT_ID, and ARM_TENANT_ID, and sets the TEST_NIGHTLY environment variable to true. Additionally, the workflow is part of a concurrency group called "single-acceptance-job-per-repo", ensuring that only one acceptance job runs at a time per repository.file
is now deprecated and replaced withfiles
, andplugin
is deprecated and replaced withplugins
. New arguments have been added, includingbinary
,gcov_args
,gcov_executable
,gcov_ignore
,gcov_include
,report_type
,skip_validation
, andswift_project
. Comprehensive documentation on these changes can be found in the release notes and changelog.RuntimeBackend
exception handling (#328). In this release, we have made significant improvements to the exception handling in theRuntimeBackend
component, addressing issues reported in tickets #328, #327, #326, and #325. We have updated theexecute
andfetch
methods to handle exceptions more gracefully and changed exception handling from catchingException
to catchingBaseException
for more comprehensive error handling. Additionally, we have updated thepyproject.toml
file to use a newer version of thedatabricks-labs-pytester
package (0.2.1 to 0.5.0) which may have contributed to the resolution of these issues. Furthermore, thetest_backends.py
file has been updated to improve the readability and user-friendliness of the test output for the functions testing if aNotFound
,BadRequest
, orUnknown
exception is raised when executing and fetching statements. Thetest_runtime_backend_use_statements
function has also been updated to printPASSED
orFAILED
instead of returning those values. These changes enhance the robustness of the exception handling mechanism in theRuntimeBackend
class and update related unit tests.Dependency updates: