-
Notifications
You must be signed in to change notification settings - Fork 843
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
AppsListPublishingCredentialsFuture.Result() panics after 16.2.1 -> 17.x.x upgrade #2090
Comments
@katbyte what version of go-autorest are you using? There were some changes to the futures implementation in v17 that requires an updated go-autorest as well (v10.9+). |
Oh sorry @jhendrixMSFT, I should have thought to include that. Here is what we are using: [14:59:22] kt@snowbook:~/hashi/..3../terraform-providers/terraform-provider-azurerm$ govendor list | egrep autorest
v github.com/Azure/go-autorest/autorest =v10.11.2 v10.11.2
v github.com/Azure/go-autorest/autorest/adal =v10.11.2 v10.11.2
v github.com/Azure/go-autorest/autorest/azure =v10.11.2 v10.11.2
v github.com/Azure/go-autorest/autorest/azure/cli =v10.11.2 v10.11.2
v github.com/Azure/go-autorest/autorest/date =v10.11.2 v10.11.2
v github.com/Azure/go-autorest/autorest/to =v10.11.2 v10.11.2
v github.com/Azure/go-autorest/autorest/validation =v10.11.2 v10.11.2
[14:59:30] kt@snowbook:~/hashi/..3../terraform-providers/terraform-provider-azurerm$ |
Thanks I can repro this. The HTTP response is a 200 and there are no async operation headers which leads me to believe this operation isn't really a LRO. Still investigating. |
@katbyte I have a fix for this in go-autorest, should be merged later today. |
Fix is now available in https://github.com/Azure/go-autorest/releases/tag/v10.11.4 |
Hello,
Looking to update to v17 of the SDK but it appears
AppsListPublishingCredentialsFuture.Result()
now panics. Switching back to16.2.1
causes the code runs just fine.I have now tried versions 17.0.0, 17.1.0, 17.2.0, 17.3.0, 17.4.0 and they all panic.
The Panic:
Calling code:
(changing to
WaitForCompletionRef
does not put a pause to the panic)The text was updated successfully, but these errors were encountered: