Generate validation-blind protobuf messages (#43)

Author: lukasbindreiter

.pre-commit-config.yaml

@@ -9,7 +9,7 @@ repos:
     hooks:
       - id: sync-with-uv
   - repo: https://github.com/charliermarsh/ruff-pre-commit
-    rev: v0.15.20
+    rev: v0.15.21
     hooks:
       - id: ruff-check
         args: [--fix, --exit-non-zero-on-fix]

AGENTS.md

@@ -75,7 +75,6 @@ Generated files live under paths such as:
 
 - `tilebox-datasets/tilebox/datasets/datasets/v1/*_pb2*.py`
 - `tilebox-datasets/tilebox/datasets/tilebox/v1/*_pb2*.py`
-- `tilebox-datasets/tilebox/datasets/buf/validate/*_pb2*.py`
 - `tilebox-workflows/tilebox/workflows/workflows/v1/*_pb2*.py`
 
 Regenerate protobuf code with:

CHANGELOG.md

@@ -11,6 +11,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - `tilebox-workflows`: Allow task `execute()` methods to use a `-> None` return annotation when postponed annotation
   evaluation is enabled.
+- `tilebox-datasets` and `tilebox-workflows`: Generate validation-blind protobuf messages without vendoring
+  `buf.validate`, avoiding duplicate descriptor conflicts when applications use their own generated validation rules.
 
 ## [0.55.0] - 2026-07-01
 

buf.gen.datasets.yaml

@@ -19,4 +19,7 @@ inputs:
     paths:
       - "datasets"
       - "tilebox"
-  - module: buf.build/bufbuild/protovalidate
+    # Deliberately generate validation-blind client messages: the SDK does not validate
+    # client-side, and omitting buf.validate avoids conflicts in protobuf's global descriptor pool.
+    exclude_types:
+      - "buf.validate.**"

buf.gen.workflows.yaml

@@ -18,3 +18,7 @@ inputs:
   - module: buf.build/tilebox/api
     paths:
       - "workflows"
+    # Deliberately generate validation-blind client messages: the SDK does not validate
+    # client-side, and omitting buf.validate avoids conflicts in protobuf's global descriptor pool.
+    exclude_types:
+      - "buf.validate.**"

pyproject.toml

@@ -6,7 +6,7 @@ authors = [{ name = "Tilebox, Inc.", email = "support@tilebox.com" }]
 readme = "README.md"
 requires-python = ">=3.10"
 dependencies = [
-    "tilebox-datasets",
+    "tilebox-datasets>=0.56.0",
     "tilebox-grpc",
     "tilebox-storage",
     "tilebox-workflows",

tilebox-datasets/pyproject.toml

@@ -56,7 +56,6 @@ packages = ["tilebox"]
 omit = [
     "tilebox/*/datasets/v1/*",
     "tilebox/*/tilebox/v1/*",
-    "tilebox/*/buf/validate/*",
 ]
 
 [tool.pytest.ini_options]

tilebox-datasets/tests/query/test_time_interval.py

@@ -15,9 +15,9 @@
 
 _TIME_FORMAT = "%Y-%m-%dT%H:%M:%S"
 
-# first time we use pandas takes sometimes a while to import and compile the code, causing hypothesis timeout issues
-# so we warm up the function like this before
-_ = _convert_to_datetime("2026-01-01")
+# Parsing a timezone-suffixed string takes a slower pandas path on first use, which can exceed Hypothesis' deadline.
+# Exercise that path before Hypothesis starts timing generated examples.
+_ = _convert_to_datetime("2026-01-01 00:00:00.000000 UTC")
 
 
 @given(