Passing a parent process object in a child process can prevent its garbage collection.
An integer overflow might might cause security issues when it is used for resource management or execution control.
Calls to mutually exclusive methods were found in the code.
Using naive datetime objects might cause time zone related issues.
Response metadata was not checked to verify that it is not
Missing pagination on a paginated call can lead to inaccurate results.
When you process and remove an item from the
JoinableQueue without calling
JoinableQueue.task_done(), a semaphore overflow exception might be thrown.
Improper multiprocessing API usage with wrong parameters might lead to deadlocks.
Incorrect binding of SNS publish operations with the
create_topic operations might lead to latency issues.
Recreating AWS clients in each Lambda function invocation is expensive.
Not setting the connection timeout parameter can cause a blocking socket connection.
Failure to end a child process that doesn't terminate before its timeout expires can result in leaked resources.
APIs that are not recommended were found.
Sequence modification while iterating over it might cause unexpected bugs.
Not checking which items have failed can lead to loss of data.
Overriding environment variables that are reserved by AWS Lambda might lead to unexpected behavior.
Hardcoding an IP address can cause security problems.
Not setting the S3 bucket owner condition might introduce a risk of accidentally using a wrong bucket.