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
buguse for describing something not working as expectedexportFunctional scope : EXPORTsolveduse to identify issue that has been solved (must be linked to the solving PR)
Improve bulk Stix loader to support 100K+ relations loading in one bulk.
The error is due to a nodejs limitation where function doesnt support more than 100K parameters. This limitation throw the error "Maximum call size exceeded" when we use spread operators to add result in the global accumulation array.
Reproducible Steps
Steps to create the smallest reproducible scenario:
Get a platform with lot of massive reports
Create a taxii sharing focus on reports
Consume the taxii collection
Expected Output
List of reports correctly exported.
Actual Output
Execution failure for "Maximum call size exceeded"
Additional information
Improvement is done with 2 different approaches.
Accumulate the result in a callback instead of spread the complete list at the end.
Improve nested connections internal filter to be based on query terms to prevent field explosions
The text was updated successfully, but these errors were encountered:
buguse for describing something not working as expectedexportFunctional scope : EXPORTsolveduse to identify issue that has been solved (must be linked to the solving PR)
Description
Improve bulk Stix loader to support 100K+ relations loading in one bulk.
The error is due to a nodejs limitation where function doesnt support more than 100K parameters. This limitation throw the error "Maximum call size exceeded" when we use spread operators to add result in the global accumulation array.
Reproducible Steps
Steps to create the smallest reproducible scenario:
Expected Output
List of reports correctly exported.
Actual Output
Execution failure for "Maximum call size exceeded"
Additional information
Improvement is done with 2 different approaches.
The text was updated successfully, but these errors were encountered: