-
Notifications
You must be signed in to change notification settings - Fork 22
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
panic v3.116.1 --continue-on-error sigsegv sementation violation #435
Comments
@tusharshahrs do you by any chance have a bit more of a reproduction than just the command? I'll try to reproduce it, but having a clear repro example would be super helpful. |
@tgummerer here are the details on the issue:
this happened just once after updating to the recent version, I haven't had a chance to try again. The pulumi code creates a GitHub repo with BranchProtection resource. The BranchProtection has
|
I's not clear to me from a cursory look if this is a |
Thanks for the details! Having had a look at this, the stack trace looks exactly the same as pulumi/pulumi-go-provider#186, so it looks like a Given the details above, I had a look at the providers. I'm gonna go ahead and transfer the issue over to the |
There were two breaking changes since, pulumi/pulumi-go-provider#227 and pulumi/pulumi-go-provider#231. Hopefully fixes #435
Hi @tusharshahrs, we just released v0.11.0 of the command provider, updated to the latest pulumi-go-provider that has the fix @tgummerer identified as a likely culprit. Could you verify whether the new version fixes the issue? |
thanks, this is what I'm getting now:
and running another stack
|
Ok, thank you for trying. The first error, We'll continue to look into your issue. |
The logging error is now fixed in pulumi-command v0.11.1. |
What issue is this tracking now? AFAICT, both of the issues noted in #435 (comment) are fixed in the latest release of this provider? |
We're currently operating under the assumption that all issues are fixed but haven't had confirmation. @alayshia is checking directly with the customer. I was going to keep the issue open until we have confirmation. |
As the issue is fixed from our point of view, I'll close this issue. Please feel free to re-open if this in error. |
What happened?
Example
Ran the following command:
Output of
pulumi about
pending
pulumi cli:
3.116.1
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: