mateo-berri 0a763bf00d fix(proxy): read a bucket config's include tree off the event loop ... Reading a config from a bucket ran a blocking boto3 GET straight from the event loop for every object in the include tree, and on GCS it built a new bucket client per object, each one starting a flush task that never ends. S3 reads now go through a worker thread, and one bucket client serves the whole include tree.		2026-09-06 02:05:18 -07:00
..
test_gcs_bucket_base.py	fix(proxy): read a bucket config's include tree off the event loop	2026-09-06 02:05:18 -07:00