-
Notifications
You must be signed in to change notification settings - Fork 741
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
[BUG] github_actions_runner_group: invalid memory address or nil pointer dereference #1524
Comments
@cwthrivent thanks for catching this! The diff between v5.15.0 and v5.14.0 is here. Is there anything suspicious in there to you? |
Hi all, one of our users of our Pulumi bridged provider is also hitting this and is unable to refresh this resource
|
That's obnoxious. I'm not seeing anything obvious in the diff...the data source for repositories doesn't look like it was touched at all during those versions. |
Hi, I think in case of the runner group the error is caused by an incorrect handling of the "Not Modified" Header. The Runner Group logic tries to read the already existing Runner Group which will return a 304 and thus the returned runner group will be nil.
This never was a problem as until the commit introducing the "selected_workflows" all attributes on the runnerGroup were accessed using the Get-Methods, which internally handle the case of the runnerGroup being null. However, the selected_workflows logic directly accesses the field on the runnerGroup which will cause a nil pointer. Imho, the code simply needs an early return within the resourceGithubActionsRunnerGroupRead method in case the above mentioned method runs into a 304 response. I can provide a pull request fixing this behavior if desired. |
It seems that the
github_actions_runner_group
resource
and thegithub_repository
data
source types have memory errors starting on provider versionv5.15.0
. This issue is not present onv5.14.0
and earlier.Copying logs from my comment from #1485 here:
Error message (Terraform v1.3.0, provider v5.16.0)
Stack trace
The text was updated successfully, but these errors were encountered: