You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and if in the CLI extension, we directly return the poller, like "return client.job.begin_start(resource_group, service, name, job_execution_template)"
Then the CLI SDK will fail to do deserialization for the polymorphism support, like below example:
> az spring job start -n hello-world-job --debug
...
Mason try to reproduce issue in _start_initial, "pipeline_response": f<azure.core.pipeline.PipelineResponse object at 0x000001DBAE8CC790>, "cls": <function JobOperations.begin_start.<locals>.<lambda> at 0x000001DBAE89D300>, "deserialized.job_snapshot.source.type": BuildResult, "deserialized.job_snapshot.trigger_config.trigger_type": Manual
azext_spring.vendored_sdks.appplatform._serialization: Discriminator type is absent or null, use base class UserSourceInfo.
azext_spring.vendored_sdks.appplatform._serialization: Discriminator trigger_type is absent or null, use base class JobTriggerConfig.
Mason try to reproduce issue in get_long_running_output, "pipeline_response": f<azure.core.pipeline.PipelineResponse object at 0x000001DBAE8CC790>, "cls": None, "deserialized.job_snapshot.source.type": None, "deserialized.job_snapshot.trigger_config.trigger_type": None
...output
{
"endTime": null,
"jobSnapshot": {
"managedComponentReferences": [],
"provisioningState": null,
"source": {
"buildResultId": "/subscriptions/0753feba-86f1-4242-aff1-27938fb04531/resourceGroups/jiec-rg-target/providers/Microsoft.AppPlatform/Spring/jiec-e-df-eus-acs-gen1/buildServices/default/builds/hello-world-job/results/2",
"type": null,
"version": null
},
"template": {
"args": null,
"environmentVariables": [],
"resourceRequests": {
"cpu": "1",
"memory": "2Gi"
}
},
"triggerConfig": {
"triggerType": null
}
},
"name": "hello-world-job-0511054547125-7fc078",
"startTime": null,
"status": "Pending",
"template": {
"args": null,
"environmentVariables": [],
"resourceRequests": {
"cpu": null,
"memory": null
}
}
}
Expected behavior
Expect output by CLI like below in the right:
Screenshots
If applicable, add screenshots to help explain your problem.
thanks for opening the issue @jiec-msft . We know what's causing this issue, it's a known bug in LRO, in case the LRO finish immediately while the return is a polymorphic type. Polymorphic deserialization pops from the resulting JSON, and if the LRO is done twice, we deserialize twice, but the second time the discriminator is not here anymore so we're not returning the polymorphic child.
Since there's a customer ticket we're going to restart our discussions on how best to solve this issue
Describe the bug
Deserialization issue for the polymorphism support with python SDK generated in swagger PR.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Expect output by CLI like below in the right:
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
{
"azure-cli": "2.56.0",
"azure-cli-core": "2.56.0",
"azure-cli-telemetry": "1.1.0",
"extensions": {
"aks-preview": "0.5.137",
"spring": "1.24.0"
}
}
The text was updated successfully, but these errors were encountered: