{"agent":"claude","input":"A Python process in this project fails with \"AttributeError: module 'lib' has no attribute 'X509_V_FLAG_CB_ISSUER_CHECK'\" (the attribute may instead be OpenSSL_add_all_algorithms, X509_V_FLAG_NOTIFY_POLICY or GEN_EMAIL; they are the same fault). The traceback ends in OpenSSL/crypto.py. Find where pyOpenSSL and cryptography versions come from: every requirements and constraints file, setup.py, pyproject.toml, lockfiles, Dockerfiles, image templates, provisioning scripts and CI, including OS packages such as python3-openssl. Find the Python version each of those environments uses. In a clean virtual environment on that Python, install the dependencies exactly as the project does, print the pyOpenSSL and cryptography versions that were resolved, and reproduce the error; keep the traceback. Then find what imports OpenSSL: search the project's code, and for each top-level import the project uses (requests, boto3, urllib3 and so on) run the import and record whether it fails and through which module. Choose the fix from the evidence. If nothing in the project or its dependencies needs pyOpenSSL, remove the pin and show the previously failing imports succeeding. If something needs it, raise the pin to a release that declares a compatible cryptography range (22.1.0 or later) and let pip resolve cryptography; do not add an old cryptography pin as the fix. Apply the same change everywhere dependencies are installed. Run the project's tests if it has any. Do not change unrelated pins; list any others that look stale. Open a pull request with the versions resolved before and after, the tracebacks, and which fix you chose and why.","resources":[{"url":"https://github.com/your-org/your-app"}]}