<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gevent on nanta - Data Engineering</title><link>https://nanta-data.dev/en/tags/gevent/</link><description>Recent content in Gevent on nanta - Data Engineering</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 nanta</copyright><lastBuildDate>Fri, 27 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://nanta-data.dev/en/tags/gevent/index.xml" rel="self" type="application/rss+xml"/><item><title>Why BigQuery Hangs in Superset: The gevent and gRPC Incompatibility</title><link>https://nanta-data.dev/en/posts/bigquery-bi-integration/</link><pubDate>Fri, 27 Feb 2026 00:00:00 +0000</pubDate><guid>https://nanta-data.dev/en/posts/bigquery-bi-integration/</guid><description>We integrated BigQuery with both Redash and Superset for per-user BI access. Redash had a known schema browsing limitation. Superset hit a much worse problem — queries executed successfully on BigQuery but results never came back, blocking indefinitely. The root cause: gunicorn&amp;rsquo;s gevent worker monkey-patches Python&amp;rsquo;s threading primitives, which deadlocks gRPC calls inside the BigQuery SDK. Switching the worker type to gthread resolved it. We contributed a docs fix upstream.</description></item></channel></rss>