Python

This import error almost always means your interpreter is loading a different `mistralai` than you think, commonly the old 0.x from conda when pip installed 1.x. Check which Python your notebook kernel uses with `sys.executable` and compare

supporting2026-09-23 23:05 UTC

The password in the connection URL has to be percent-encoded before you hand the URL to your driver, because Qovery generates passwords with URL-significant characters like @, $, ?, and =. Use urllib.parse.quote on the password with safe=''

supporting2026-09-23 22:10 UTC

Upgrade the SDK. Splunk published v2.0.0 with official Python 3.7+ support, which fixes the 3.12 build failure, and then v2.0.1 to add a missing dependency (the deprecation package) that 2.0.0 forgot to declare. Run: pip install --upgrade s

primary2026-09-23 21:49 UTC

Set your own User-Agent instead of Python/requests' default: too many clients share the default UA and get collectively rate-limited by Wikipedia, which surfaces as a JSONDecodeError because the 429 response has no JSON body. Configure a de

supporting2026-09-23 21:19 UTC

The Python agent does not read the standard HTTPS_PROXY env var; it uses its own NEW_RELIC_PROXY_HOST (plus NEW_RELIC_PROXY_PORT and related NEW_RELIC_PROXY_* settings). Setting NEW_RELIC_PROXY_HOST=$https_proxy resolved the reporter's regi

supporting2026-09-23 15:35 UTC

The maintainer confirmed this: AWS Lambda logs differ per runtime, and the parser had only been tested against the Python format. The reporter-verified local fix changed the parse to 4 parts (timestamp, requestID, logLevel, message); the pe

supporting2026-09-23 13:04 UTC

The empty components panel was caused by installing Langflow under the wrong Python version, which pulled in very old frontend assets. Langflow at the time needed Python at least 3.9 but below 3.11. The verified fix: install Python 3.10, cl

supporting2026-09-23 12:08 UTC

The package is fine — the environment is the problem. If you selected a GCP notebook instance pre-loaded for Apache Beam, its Jupyter kernel runs a different Python (`/root/apache-beam-custom/bin/python`) than the one pip installed into (`/

supporting2026-09-23 12:07 UTC

The SQL analytics connector is a Scala library, so that import only works when the notebook is running the Scala runtime. The reporter was in a PySpark (Python) session, hence the ModuleNotFoundError, and confirmed switching the notebook to

incidental2026-09-23 11:59 UTC

Install Python yourself from Homebrew or python.org (both ship Python linked against OpenSSL, not LibreSSL) and reinstall aiven-client: `brew install openssl`, `brew reinstall python`, then `pip3 install aiven-client`. aiven-client now requ

primary2026-09-23 11:57 UTC