Handle RecursionError exception in perform_request (issue 1602)

[hmilkovi]

Propagate RecursionError if it happends on lower levels so when used like:

import sys
import inspect
import elasticsearch

es_client = elasticsearch.Elasticsearch("http://localhost:9200/")
print(f"Recursion limit: {sys.getrecursionlimit()}")

def rec():
    print(len(inspect.stack()))
    es_client.index(index='testing', body={'test': 'test'}, request_timeout=1)
    rec()

rec()

doesn't crash python interpreter with core dump.

Personal opinion is that this is really needed when we you web servers like uwsgi, gunicorn as
then the whole web server dies and doesn't return http 500 status code.

Related issue: #1602

[elasticmachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[cla-checker-service]

❌ Author of the following commits did not sign a Contributor Agreement:
e182f58, , 508b935, 9a08a30,

Please, read and sign the above mentioned agreement if you want to contribute to this project

[sethmlarson]

Gotcha, so the problem really is that we're swallowing the RecursionError out of except Exception:? If that's the case let's do something simpler, instead the very first branch under except Exception: check for RecursionError and reraise without modifying the exception.

Also you'll need to sign the CLA for me to merge.

[hmilkovi]

Yes that's the case :) . Does accepting CLA take some time to propagate or as I have signed it?

[sethmlarson]

@hmilkovi Did you sign the CLA with the same email address as the one used in your Git commits?

[hmilkovi]

CLA check (read up in docs that I need to comment again)

[hmilkovi]

I have changed email on my last commit. Do I need to change it on all or is it easier to make this changes on new branch and new PR?
I want to contribute as private entity with private email.

Sorry for bothering you with that.

[sethmlarson]

Yeah creating a new PR is probably best

[hmilkovi]

Closing this one for #1609 .
Now CLA is fine :)