Tag: availability
Allocated resources are not released properly.
Using the spawn
or forkserver
start method without importing the main module might lead to unexpected behavior (for example, it might cause a RuntimeError
).
Using naive datetime objects might cause time zone related issues.
This code uses deprecated methods, which suggests that it has not been recently reviewed or maintained.
Improper multiprocessing API usage with wrong parameters might lead to deadlocks.
The os.close()
does not work on some platforms.
Sequence modification while iterating over it might cause unexpected bugs.
The Process.terminate
API might cause data corruption of shared resources.
Response metadata was not checked to verify that it is not None
.
Insecure ways of creating temporary files and directories can lead to race conditions, privilege escalation, and other security vulnerabilities.
Incorrect binding of SNS publish operations with the subscribe
or create_topic
operations might lead to latency issues.
Not setting the connection timeout parameter can cause a blocking socket connection.
Recreating AWS clients in each Lambda function invocation is expensive.
Failure to end a child process that doesn't terminate before its timeout expires can result in leaked resources.
Using the get
method from the dict
class without default values can cause runtime exceptions.
Overriding environment variables that are reserved by AWS Lambda might lead to unexpected behavior.