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
Hi @sschuetz2bit. Firstly: thanks for raising this issue.
Could you give me a bit more information about what sample you tried to run, exactly? Also would be great to know what version of adfpy you were using that gave you this error.
Thanks for the info, and sorry for the slow response on this.
Would you be able to provide the versions of the packages installed? It does sound like an SDK interface change that wasn't properly taken into account here.
I think it indeed was caused by a SDK interface change. This showed up initially in this commit but I didn't create a new release following that patch... Sorry about that. I've just released version 0.2.0 that does include this cap on the SDK version. I've also added an issue #28 to upgrade the SDK version (which should include any additional required parameters to avoid this kind of error)
Activity
danielvdende commentedon Apr 12, 2023
Hi @sschuetz2bit. Firstly: thanks for raising this issue.
Could you give me a bit more information about what sample you tried to run, exactly? Also would be great to know what version of
adfpyyou were using that gave you this error.Thanks!
sschuetz2bit commentedon Apr 14, 2023
Hi @danielvdende
I saw that the references need the mandatory paramater type.
as example:
PipelineReference(*, type: str | _models.PipelineReferenceType, reference_name: str, name: str | None = None, **kwargs: Any)
Pipeline reference type. Required. "PipelineReference"
these are missing (maybe it was a change in the SDK interface)
locally it worked after adding a type to all references
danielvdende commentedon May 1, 2023
Thanks for the info, and sorry for the slow response on this.
Would you be able to provide the versions of the packages installed? It does sound like an SDK interface change that wasn't properly taken into account here.
danielvdende commentedon May 5, 2023
I think it indeed was caused by a SDK interface change. This showed up initially in this commit but I didn't create a new release following that patch... Sorry about that. I've just released version 0.2.0 that does include this cap on the SDK version. I've also added an issue #28 to upgrade the SDK version (which should include any additional required parameters to avoid this kind of error)
sschuetz2bit commentedon May 5, 2023
Hi Daniel, thank you. i will test it!