You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You scan 100 assets of the same type. At 51 the provider crashes for any reason. Then all following assets using the same provider also return errors since the provider runtime is not restarted.
To Reproduce
Scan multiple assets of same type eg. with asset inventory. Force a panic during the first scan eg. by returning a panic when a resource is called. All following assets return as error.
// TODO: we probably want to check here if the provider is dead and restart it
// if r.Provider.Instance.isCloseOrShutdown() {
// }
Expected behavior
Within a scan we do not recover the runtime. We only check for a dead runtime when we start scanning a new asset. If the runtime is dead, we restart the provider. Otherwise we keep the existing runtime as we do right now.
The text was updated successfully, but these errors were encountered:
Describe the bug
You scan 100 assets of the same type. At 51 the provider crashes for any reason. Then all following assets using the same provider also return errors since the provider runtime is not restarted.
To Reproduce
Scan multiple assets of same type eg. with asset inventory. Force a panic during the first scan eg. by returning a panic when a resource is called. All following assets return as error.
Related to missing check here
cnquery/providers/runtime.go
Lines 207 to 211 in 9364945
Expected behavior
Within a scan we do not recover the runtime. We only check for a dead runtime when we start scanning a new asset. If the runtime is dead, we restart the provider. Otherwise we keep the existing runtime as we do right now.
The text was updated successfully, but these errors were encountered: