Skip to content
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

Tables from Azure and AWS returns this invalid memory address or nil pointer dereference #4279

Closed
jeffreymp17 opened this issue May 21, 2024 · 9 comments
Labels
bug Something isn't working stale No recent activity has been detected on this issue/PR and it will be closed

Comments

@jeffreymp17
Copy link

jeffreymp17 commented May 21, 2024

Describe the bug
There are some tables that returns this error invalid memory address or nil pointer dereference when we execute a query
for example Azure tables

SELECT 
  scc.id, 
  sub.subscription_id, 
  sub.display_name, 
  scc.email, 
  scc.alert_notifications, 
  scc.alerts_to_admins 
FROM 
  azure_security_center_contact AS scc 
  INNER JOIN azure_subscription AS sub ON sub.subscription_id = scc.subscription_id 
WHERE 
  scc.alert_notifications = 'On';

and this one


select
  sa.subscription_id,
  sa.name,
  sa.id as resource,
  sa.network_rule_default_action,
  resource_group,
  sub.display_name as subscription
from
  azure_storage_account sa,
  azure_subscription sub
where
  sub.subscription_id = sa.subscription_id and
  sa.network_rule_default_action = 'Allow';

GCP queries

select 
  name, 
  cluster_name, 
  config ->> 'imageType' as image_type, 
  location, 
  project 
from 
  gcp_kubernetes_node_pool 
where 
  config ->> 'imageType' != 'COS_CONTAINERD';
select 
  name, 
  cluster_name, 
  initial_node_count, 
  version, 
  status, 
  project, 
  autoscaling -> 'enabled' as autoscaling_enabled, 
  location 
from 
  gcp_kubernetes_node_pool 
where 
  autoscaling ->> 'enabled' != 'true' 
  or autoscaling = '{}';

Steampipe version (steampipe -v)
Example: v0.19.3

To reproduce
Execute the queries added in the description

Expected behavior
Should not receive this error invalid memory address or nil pointer dereference and return results

Additional context
Add any other context about the problem here.

@jeffreymp17 jeffreymp17 added the bug Something isn't working label May 21, 2024
@ParthaI
Copy link

ParthaI commented May 22, 2024

Hello, @jeffreymp17, sorry to see that you are experiencing the error. Could you please try with the latest Steampipe CLI version and the latest plugin version? Please let us know if the error still persists. Thanks!

@jeffreymp17
Copy link
Author

jeffreymp17 commented Jun 19, 2024

I updated steampipe to v0.23.2 and the issue is still happening, but in this case are GCP tables

@jeffreymp17
Copy link
Author

@ParthaI is there a plan to review this issue?
Thanks in advance

@ParthaI
Copy link

ParthaI commented Jun 26, 2024

Hello @jeffreymp17,

As per my observation, there was a breaking change in the Steampipe SDK version 5.10.0. However, this issue has been fixed in SDK version 5.10.1. I have pushed a commit to the update-steampipe-sdk-version-5.10.1 branch in the GCP plugin, updating the SDK version to 5.10.1.

Could you please try using the PR branch and let me know if the issue still persists?

Steps to build the plugin from the update-steampipe-sdk-version-5.10.1 branch:

  1. Clone the repository: git clone https://github.com/turbot/steampipe-plugin-gcp.git
  2. Navigate to the repository:cd steampipe-plugin-gcp
  3. Checkout the specified branch:git checkout update-steampipe-sdk-version-5.10.1
  4. Build the plugin:make
  5. Execute the query.

Note: Before running the query, please terminate all running Steampipe processes.

Thanks!

@jeffreymp17
Copy link
Author

Hi @ParthaI, after trying this approach the errors are gone. I think it is working fine. What is the ETA for publishing the fix?

@MoisesTabar211
Copy link

Good morning @ParthaI this fix is working correctly, do you have an ETA for the release of the fix? Please let us know

@ParthaI
Copy link

ParthaI commented Aug 14, 2024

Hi @jeffreymp17, @MoisesTabar211, we have already released these versions, could you please upgrade your environment and try again?

Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.

@github-actions github-actions bot added the stale No recent activity has been detected on this issue/PR and it will be closed label Oct 14, 2024
Copy link

This issue was closed because it has been stalled for 90 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale No recent activity has been detected on this issue/PR and it will be closed
Projects
None yet
Development

No branches or pull requests

3 participants