Correctly parse libraries in service.jobs#168
Correctly parse libraries in service.jobs#168judahrand wants to merge 1 commit intodatabricks:mainfrom
libraries in service.jobs#168Conversation
|
this file is auto-generated and will silently be rewritten in other releases. we'll have to fix bug on generator template side |
I'd debug it myself but since the OpenAPI spec isn't available anywhere in raw form that's a bit tricky. Could you make in available, please? |
|
@judahrand it's proprietary for now :) |
Well sort of... it could mostly be reverse engineered from this SDK I'd guess. Also seems like an unhelpful thing to make proprietary given that it defines how to interact with the Databricks service. Surely Databricks wants as many services as possible to integrate with Databricks? You used to publish your JobsAPI 2.1 YAML... but that seems to have been yanked. |
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## main #168 +/- ##
=======================================
Coverage 53.26% 53.26%
=======================================
Files 30 30
Lines 18190 18190
=======================================
Hits 9688 9688
Misses 8502 8502
☔ View full report in Codecov by Sentry. |
|
@judahrand we first want a few good official SDKs that work the same, configure the same, and feel the same and are available for every major language :) thanks for your bug reports! |
|
I suspect that the issue might actually be in the OpenAPI definitions for the Jobs API since it only seems to happen for the Jobs service and not other services. |
|
Fixing with more entities in #178 |
Changes
Pretty self explanatory. Currently, this is correct in most places but is wrong in the
jobsservice. I suspect there is either a bug in theservice.py.tmplor a mistake in the OpenAPI spec.I'd debug it myself but since the OpenAPI spec is available anywhere in raw form that's a bit tricky. Could you make in available, please?
Tests
make testrun locallymake fmtapplied