Anton Tayanovskyy

Yeah we can pretest the PR against all the providers again before merging. But I'm curious what you find on the Check issues. Thanks!

I understand this is still blocked right. Marking it as such, we'll revisit periodically.

/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin aba55507613bf68bf53e0b3f62e87bb453101f69 Error: fatal: remote error: upload-pack: not our ref aba55507613bf68bf53e0b3f62e87bb453101f69 The process '/usr/bin/git' failed with exit code 128 Waiting 19...

This seems to have been triggered by repository dispatch but I'm confused where it's coming from. @guineveresaenger is this one of your PRs? Appreciate pointers. Doesn't look like P1 though.

Thanks for reporting this @Rez0k and sorry that Pulumi is not working as expected for you. Could you please include a more complete program as well as output of `pulumi...

Hi @Rez0k I'm having another look here, it would be really great to have a minimal fully working repro to make sure I narrow in on your exact issue. But...

https://github.com/pulumi/pulumi-aws/issues/2095 is another issue that runs into very similar problems with this resource. I believe this is unrelated to using `--refresh`. We'll circle back here when we have a good...

From @komalali : okay I have some new information. I ran 2 separate deployments, pulumi refresh and pulumi update instead of 1 remediate-drift which does the pulumi update --refresh. When...

I haven't been able to repro on the original program from @komalali as it does not create `${TMPDIR}/pulumi-asset-${HASH}` files but instead stores literal JS code in the Pulumi state file....

``` | 5.43.0 | no repro | | 6.2.0 | no repro | | 6.5.0 | no repro | | 6.6.0 | no repro | | 6.6.1 | reproduces |...