tinybird 0.0.1.dev253__tar.gz → 0.0.1.dev254__tar.gz

{tinybird-0.0.1.dev253 → tinybird-0.0.1.dev254}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
 Name: tinybird
-Version: 0.0.1.dev253
+Version: 0.0.1.dev254
 Summary: Tinybird Command Line Tool
 Home-page: https://www.tinybird.co/docs/forward/commands
 Author: Tinybird

{tinybird-0.0.1.dev253 → tinybird-0.0.1.dev254}/tinybird/tb/__cli__.py

@@ -4,5 +4,5 @@ __description__ = 'Tinybird Command Line Tool'
 __url__ = 'https://www.tinybird.co/docs/forward/commands'
 __author__ = 'Tinybird'
 __author_email__ = 'support@tinybird.co'
-__version__ = '0.0.1.dev253'
-__revision__ = '3bc2143'
+__version__ = '0.0.1.dev254'
+__revision__ = '269e345'

{tinybird-0.0.1.dev253 → tinybird-0.0.1.dev254}/tinybird/tb/modules/agent/agent.py

@@ -30,11 +30,13 @@ from tinybird.tb.modules.agent.memory import clear_history
 from tinybird.tb.modules.agent.models import create_model, model_costs
 from tinybird.tb.modules.agent.prompts import (
     datafile_instructions,
+    endpoint_optimization_instructions,
     plan_instructions,
     resources_prompt,
     sql_instructions,
 )
-from tinybird.tb.modules.agent.tools.append import append
+from tinybird.tb.modules.agent.tools.analyze import analyze_file, analyze_url
+from tinybird.tb.modules.agent.tools.append import append_file, append_url
 from tinybird.tb.modules.agent.tools.build import build
 from tinybird.tb.modules.agent.tools.create_datafile import create_datafile
 from tinybird.tb.modules.agent.tools.deploy import deploy
@@ -45,7 +47,6 @@ from tinybird.tb.modules.agent.tools.get_openapi_definition import get_openapi_d
 from tinybird.tb.modules.agent.tools.mock import mock
 from tinybird.tb.modules.agent.tools.plan import plan
 from tinybird.tb.modules.agent.tools.preview_datafile import preview_datafile
-from tinybird.tb.modules.agent.tools.read_fixture_data import read_fixture_data
 from tinybird.tb.modules.agent.tools.request_endpoint import request_endpoint
 from tinybird.tb.modules.agent.utils import TinybirdAgentContext, show_input
 from tinybird.tb.modules.build_common import process as build_process
@@ -112,11 +113,13 @@ You have access to the following tools:
 5. `deploy` - Deploy the project to Tinybird Cloud.
 6. `deploy_check` - Check if the project can be deployed to Tinybird Cloud before deploying it.
 7. `mock` - Create mock data for a landing datasource.
-8. `read_fixture_data` - Read a fixture data file present in the project folder.
-9. `append` - Append existing fixture to a datasource.
-10. `get_endpoint_stats` - Get metrics of the requests to an endpoint.
-11. `get_openapi_definition` - Get the OpenAPI definition for all endpoints that are built/deployed to Tinybird Cloud or Local.
-12. `execute_query` - Execute a query against Tinybird Cloud or Local.
+8. `analyze_file` - Analyze the content of a fixture file present in the project folder.
+9. `analyze_url` - Analyze the content of an external url.
+9. `append_file` - Append a file present in the project to a datasource.
+10. `append_url` - Append an external url to a datasource.
+11. `get_endpoint_stats` - Get metrics of the requests to an endpoint.
+12. `get_openapi_definition` - Get the OpenAPI definition for all endpoints that are built/deployed to Tinybird Cloud or Local.
+13. `execute_query` - Execute a query against Tinybird Cloud or Local.
 13. `request_endpoint` - Request an endpoint against Tinybird Cloud or Local.
 
 # When creating or updating datafiles:
@@ -133,21 +136,11 @@ You have access to the following tools:
 - If the user does not specify anything about the desired schema, create a schema like this:
 SCHEMA >
     `data` String `json:$`
+
 - Use always json paths with .ndjson files.
 
 # When user wants to optimize an endpoint:
-First check if the query is optimized. E.g is filtering by a column present in the sorting key.
-Avoid when possible to update the landing datasource.
-Check endpoint stats to analyze how the endpoint is performing. Use `get_endpoint_stats` tool to get the stats.
-You can use `request_endpoint` tool to check if the endpoint is working as expected.
-You can use `execute_query` tool to execute a query against Tinybird Cloud or Local, to test different queries.
-When your data is in Tinybird, you can create intermediate data sources to preprocess data and make the endpoints faster. This can be done by using materialized views or copy pipes.
-- Copy pipes capture the result of a pipe at a specific point in time and write it to a target data source. They can run on a schedule or run on demand, making them ideal for event-sourced snapshots, data experimentation, and deduplication with snapshots.
-- Materialized views continuously re-evaluate a query as new events are inserted, maintaining an always up-to-date derived dataset. Unlike copy pipes which create point-in-time snapshots, materialized views provide real-time transformations of your data.
-Each approach has its own strengths and use cases:
-- Use copy pipes when you need scheduled or on-demand snapshots of your data.
-- Use materialized views when you need continuous, real-time transformations.
-Finally, update the existing endpoint itself, do not add a new one.
+{endpoint_optimization_instructions}
 
 IMPORTANT: If the user cancels some of the steps or there is an error in file creation, DO NOT continue with the plan. Stop the process and wait for the user before using any other tool.
 IMPORTANT: Every time you finish a plan and start a new resource creation or update process, create a new plan before starting with the changes.
@@ -200,8 +193,10 @@ Today is {datetime.now().strftime("%Y-%m-%d")}
                 Tool(deploy, docstring_format="google", require_parameter_descriptions=True, takes_ctx=True),
                 Tool(deploy_check, docstring_format="google", require_parameter_descriptions=True, takes_ctx=True),
                 Tool(mock, docstring_format="google", require_parameter_descriptions=True, takes_ctx=True),
-                Tool(read_fixture_data, docstring_format="google", require_parameter_descriptions=True, takes_ctx=True),
-                Tool(append, docstring_format="google", require_parameter_descriptions=True, takes_ctx=True),
+                Tool(analyze_file, docstring_format="google", require_parameter_descriptions=True, takes_ctx=True),
+                Tool(analyze_url, docstring_format="google", require_parameter_descriptions=True, takes_ctx=True),
+                Tool(append_file, docstring_format="google", require_parameter_descriptions=True, takes_ctx=True),
+                Tool(append_url, docstring_format="google", require_parameter_descriptions=True, takes_ctx=True),
                 Tool(
                     get_endpoint_stats, docstring_format="google", require_parameter_descriptions=True, takes_ctx=True
                 ),
@@ -281,8 +276,8 @@ def run_agent(
     token = config.get("token", None)
     host = config.get("host", None)
     user_token = config.get("user_token", None)
-    workspace_id = config.get("id", None)
-    workspace_name = config.get("name", None)
+    workspace_id = config.get("id", "")
+    workspace_name = config.get("name", "")
     try:
         if not token or not host or not workspace_id or not user_token:
             yes = click.confirm(
@@ -443,9 +438,9 @@ def mock_data(
     )
 
 
-def analyze_fixture(config: dict[str, Any], fixture_path: str) -> dict[str, Any]:
+def analyze_fixture(config: dict[str, Any], fixture_path: str, format: str = "json") -> dict[str, Any]:
     local_client = get_tinybird_local_client(config, test=False, silent=True)
-    meta, _data = _analyze(fixture_path, local_client, Path(fixture_path).suffix.lstrip("."))
+    meta, _data = _analyze(fixture_path, local_client, format)
     return meta
 
 

{tinybird-0.0.1.dev253 → tinybird-0.0.1.dev254}/tinybird/tb/modules/agent/prompts.py

@@ -147,3 +147,240 @@ def get_resource_type(path: Path) -> str:
     elif path.suffix.lower() == ".connection":
         return "connection"
     return "unknown"
+
+
+endpoint_optimization_instructions = """
+<endpoint_optimization_instructions>
+## Endpoint Optimization Instructions
+### Step 1: Identify Performance Issues
+1. Analyze the endpoint's query performance metrics
+2. Look for endpoints with high latency or excessive data scanning
+3. Check read_bytes/write_bytes ratios to detect inefficient operations
+
+### Step 2: Apply the 5-Question Diagnostic Framework
+
+#### Question 1: Are you aggregating or transforming data at query time?
+**Detection:**
+- Look for `count()`, `sum()`, `avg()`, or data type casting in published API endpoints
+- Check if the same calculations are performed on every request
+
+**Fix:**
+- Create Materialized Views to pre-aggregate data at ingestion time
+- Move transformations from query time to ingestion time
+- Example transformation:
+  ```sql
+  -- Before (in endpoint)
+  SELECT date, count(*) as daily_count 
+  FROM events 
+  GROUP BY date
+  
+  -- After (in Materialized View)
+  ENGINE "AggregatingMergeTree"
+  ENGINE_PARTITION_KEY "toYYYYMM(date)"
+  ENGINE_SORTING_KEY "date"
+  AS SELECT 
+    date,
+    count(*) as daily_count
+  FROM events
+  GROUP BY date
+  ```
+
+#### Question 2: Are you filtering by fields in the sorting key?
+**Detection:**
+- Examine WHERE clauses in queries
+- Check if filtered columns are part of the sorting key
+- Look for filters on partition keys instead of sorting keys
+
+**Fix:**
+- Ensure sorting key includes frequently filtered columns
+- Order sorting key columns by selectivity (most selective first)
+- Guidelines:
+  - Use 3-5 columns in sorting key
+  - Place `customer_id` or tenant identifiers first for multi-tenant apps
+  - Avoid `timestamp` as the first sorting key element
+  - Never use partition key for filtering
+
+**Example Fix:**
+```sql
+-- Before
+ENGINE_SORTING_KEY "timestamp, customer_id"
+
+-- After (better for multi-tenant filtering)
+ENGINE_SORTING_KEY "customer_id, timestamp"
+```
+
+#### Question 3: Are you using the best data types?
+**Detection:**
+- Scan for overly large data types:
+  - String where UUID would work
+  - Int64 where UInt32 would suffice
+  - DateTime with unnecessary precision
+  - Nullable columns that could have defaults
+
+**Fix:**
+- Downsize data types:
+  ```sql
+  -- Before
+  id String,
+  count Int64,
+  created_at DateTime64(3),
+  status Nullable(String)
+  
+  -- After
+  id UUID,
+  count UInt32,
+  created_at DateTime,
+  status LowCardinality(String) DEFAULT 'pending'
+  ```
+- Use `LowCardinality()` for strings with <100k unique values
+- Replace Nullable with default values using `coalesce()`
+
+#### Question 4: Are you doing complex operations early in the pipeline?
+**Detection:**
+- Look for JOINs or aggregations before filters
+- Check operation order in multi-node pipes
+
+**Fix:**
+- Reorder operations: Filter → Simple transforms → Complex operations
+- Example:
+  ```sql
+  -- Before
+  SELECT * FROM (
+    SELECT a.*, b.name 
+    FROM events a 
+    JOIN users b ON a.user_id = b.id
+  ) WHERE date >= today() - 7
+  
+  -- After
+  SELECT a.*, b.name 
+  FROM (
+    SELECT * FROM events 
+    WHERE date >= today() - 7
+  ) a
+  JOIN users b ON a.user_id = b.id
+  ```
+
+#### Question 5: Are you joining two or more data sources?
+**Detection:**
+- Identify JOINs in queries
+- Check read_bytes/write_bytes ratio in Materialized Views
+- Look for full table scans on joined tables
+
+**Fix Options:**
+1. Replace JOIN with subquery:
+   ```sql
+   -- Before
+   SELECT e.*, u.name 
+   FROM events e 
+   JOIN users u ON e.user_id = u.id
+   
+   -- After
+   SELECT e.*, 
+     (SELECT name FROM users WHERE id = e.user_id) as name
+   FROM events e
+   WHERE user_id IN (SELECT id FROM users)
+   ```
+
+2. Optimize Materialized View JOINs:
+   ```sql
+   -- Before (inefficient)
+   SELECT a.id, a.value, b.value 
+   FROM a 
+   LEFT JOIN b USING id
+   
+   -- After (optimized)
+   SELECT a.id, a.value, b.value 
+   FROM a 
+   LEFT JOIN (
+     SELECT id, value 
+     FROM b 
+     WHERE b.id IN (SELECT id FROM a)
+   ) b USING id
+   ```
+
+### Step 3: Implementation Actions
+
+#### For Schema Changes:
+1. Update the datasource schema
+2. Update the sorting keys and data types
+3. Update dependent pipes and endpoints
+
+#### For Query Optimizations:
+1. Create Materialized Views for repeated aggregations
+2. Rewrite queries following best practices
+3. Test performance improvements
+
+#### For JOIN Optimizations:
+1. Evaluate if JOIN is necessary
+2. Consider denormalization strategies
+3. Use Copy Pipes for historical data recalculation
+4. Implement filtered JOINs in Materialized Views
+
+#### In general:
+1. If you need to iterate an existing resource, do not create a new iteration, just update it with the needed changes.
+
+## Monitoring and Validation
+
+### Monitoring:
+1. Set up alerts for endpoints exceeding latency thresholds
+2. Review of tinybird.pipe_stats_rt (realtime stats of last 24h) and tinybird.pipe_stats (historical stats aggregated by day)
+3. Track processed data patterns over time
+4. Monitor for query pattern changes
+
+### Success Metrics:
+- Reduced query latency
+- Lower data scanning (read_bytes)
+- Improved read_bytes/write_bytes ratio
+- Consistent sub-second API response times
+
+## Code Templates
+
+### Materialized View Template:
+```sql
+NODE materialized_view_name
+SQL >
+  SELECT 
+    -- Pre-aggregated fields
+    toDate(timestamp) as date,
+    customer_id,
+    count(*) as event_count,
+    sum(amount) as total_amount
+  FROM source_table
+  GROUP BY date, customer_id
+
+TYPE materialized
+DATASOURCE mv_datasource_name
+ENGINE "AggregatingMergeTree"
+ENGINE_PARTITION_KEY "toYYYYMM(date)"
+ENGINE_SORTING_KEY "customer_id, date"
+```
+
+### Optimized Query Template:
+```sql
+NODE endpoint_query
+SQL >
+  -- Step 1: Filter early
+  WITH filtered_data AS (
+    SELECT * FROM events
+    WHERE customer_id = {{ String(customer_id) }}
+      AND date >= {{ Date(start_date) }}
+      AND date <= {{ Date(end_date) }}
+  )
+  -- Step 2: Simple operations
+  SELECT 
+    date,
+    sum(amount) as daily_total
+  FROM filtered_data
+  GROUP BY date
+  ORDER BY date DESC
+```
+
+## Best Practices Summary
+
+1. **Think ingestion-time, not query-time** - Move computations upstream
+2. **Index smartly** - Sorting keys should match filter patterns
+3. **Size appropriately** - Use the smallest viable data types
+4. **Filter first** - Reduce data before complex operations
+5. **JOIN carefully** - Consider alternatives and optimize when necessary
+</endpoint_optimization_instructions>
+"""

tinybird-0.0.1.dev254/tinybird/tb/modules/agent/tools/analyze.py

@@ -0,0 +1,79 @@
+import json
+from pathlib import Path
+from urllib.parse import urlparse
+
+import click
+from pydantic_ai import RunContext
+
+from tinybird.tb.modules.agent.utils import TinybirdAgentContext
+from tinybird.tb.modules.feedback_manager import FeedbackManager
+
+
+def analyze_file(ctx: RunContext[TinybirdAgentContext], fixture_pathname: str):
+    """Analyze a fixture data file present in the project folder
+
+    Args:
+        fixture_pathname (str): a path or an external url to a fixture file. Required.
+
+    Returns:
+        str: The content of the fixture data file.
+    """
+    try:
+        ctx.deps.thinking_animation.stop()
+        click.echo(FeedbackManager.highlight(message=f"» Analyzing {fixture_pathname}..."))
+        fixture_path = Path(ctx.deps.folder) / fixture_pathname.lstrip("/")
+
+        if not fixture_path.exists():
+            click.echo(FeedbackManager.error(message=f"No fixture data found for {fixture_pathname}."))
+            ctx.deps.thinking_animation.start()
+            return f"No fixture data found for {fixture_pathname}. Please check the path of the fixture and try again."
+
+        fixture_extension = fixture_path.suffix.lstrip(".")
+        response = ctx.deps.analyze_fixture(fixture_path=str(fixture_path), format=fixture_extension)
+        click.echo(FeedbackManager.success(message="✓ Done!\n"))
+        ctx.deps.thinking_animation.start()
+        # limit content to first 10 rows
+        data = response["preview"]["data"][:10]
+        columns = response["analysis"]["columns"]
+
+        return f"#Result of analysis of {fixture_pathname}:\n##Columns:\n{json.dumps(columns)}\n##Data sample:\n{json.dumps(data)}"
+    except Exception as e:
+        ctx.deps.thinking_animation.stop()
+        click.echo(FeedbackManager.error(message=f"Error analyzing {fixture_pathname}: {e}"))
+        ctx.deps.thinking_animation.start()
+        return f"Error analyzing {fixture_pathname}: {e}"
+
+
+def analyze_url(ctx: RunContext[TinybirdAgentContext], fixture_url: str):
+    """Analyze a fixture file present in an external url
+
+    Args:
+        fixture_url (str): an external url to a fixture file. Required.
+
+    Returns:
+        str: The analysis with the columns and the first 10 rows of the fixture data file.
+    """
+    try:
+        ctx.deps.thinking_animation.stop()
+        is_url = urlparse(fixture_url).scheme in ("http", "https")
+        click.echo(FeedbackManager.highlight(message=f"» Analyzing {fixture_url}..."))
+        if not is_url:
+            click.echo(FeedbackManager.error(message=f"{fixture_url} is not a valid url."))
+            ctx.deps.thinking_animation.start()
+            return f"{fixture_url} is not a valid url. Please check the url and try again."
+
+        fixture_extension = fixture_url.split(".")[-1]
+
+        response = ctx.deps.analyze_fixture(fixture_path=fixture_url, format=fixture_extension)
+        click.echo(FeedbackManager.success(message="✓ Done!\n"))
+        ctx.deps.thinking_animation.start()
+        # limit content to first 10 rows
+        data = response["preview"]["data"][:10]
+        columns = response["analysis"]["columns"]
+
+        return f"#Result of analysis of URL {fixture_url}:\n##Columns:\n{json.dumps(columns)}\n##Data sample:\n{json.dumps(data)}"
+    except Exception as e:
+        ctx.deps.thinking_animation.stop()
+        click.echo(FeedbackManager.error(message=f"Error analyzing {fixture_url}: {e}"))
+        ctx.deps.thinking_animation.start()
+        return f"Error analyzing {fixture_url}: {e}"

tinybird-0.0.1.dev254/tinybird/tb/modules/agent/tools/append.py

@@ -0,0 +1,87 @@
+import click
+from pydantic_ai import RunContext
+
+from tinybird.tb.modules.agent.utils import TinybirdAgentContext, show_confirmation, show_input
+from tinybird.tb.modules.feedback_manager import FeedbackManager
+
+
+def append_file(ctx: RunContext[TinybirdAgentContext], datasource_name: str, fixture_pathname: str) -> str:
+    """Append existing fixture to a datasource
+
+    Args:
+        datasource_name: Name of the datasource to append fixture to
+        fixture_pathname: Path to the fixture file to append
+
+    Returns:
+        str: Message indicating the success or failure of the appending
+    """
+    try:
+        ctx.deps.thinking_animation.stop()
+        confirmation = show_confirmation(
+            title=f"Append fixture {fixture_pathname} to datasource {datasource_name}?",
+            skip_confirmation=ctx.deps.dangerously_skip_permissions,
+        )
+
+        if confirmation == "review":
+            click.echo()
+            feedback = show_input(ctx.deps.workspace_name)
+            ctx.deps.thinking_animation.start()
+            return (
+                f"User did not confirm appending {fixture_pathname} fixture and gave the following feedback: {feedback}"
+            )
+
+        if confirmation == "cancel":
+            ctx.deps.thinking_animation.start()
+            return f"User rejected appending {fixture_pathname} fixture. Skip this step"
+
+        ctx.deps.thinking_animation.stop()
+        click.echo(FeedbackManager.highlight(message=f"\n» Appending {fixture_pathname} to {datasource_name}..."))
+        ctx.deps.append_data(datasource_name=datasource_name, path=fixture_pathname)
+        click.echo(FeedbackManager.success(message=f"✓ Data appended to {datasource_name}"))
+        ctx.deps.thinking_animation.start()
+        return f"Data appended to {datasource_name}"
+    except Exception as e:
+        ctx.deps.thinking_animation.stop()
+        click.echo(FeedbackManager.error(message=e))
+        ctx.deps.thinking_animation.start()
+        return f"Error appending fixture {fixture_pathname} to {datasource_name}: {e}"
+
+
+def append_url(ctx: RunContext[TinybirdAgentContext], datasource_name: str, fixture_url: str) -> str:
+    """Append existing fixture to a datasource
+
+    Args:
+        datasource_name: Name of the datasource to append fixture to
+        fixture_url: external url to the fixture file to append
+
+    Returns:
+        str: Message indicating the success or failure of the appending
+    """
+    try:
+        ctx.deps.thinking_animation.stop()
+        confirmation = show_confirmation(
+            title=f"Append URL {fixture_url} to datasource {datasource_name}?",
+            skip_confirmation=ctx.deps.dangerously_skip_permissions,
+        )
+
+        if confirmation == "review":
+            click.echo()
+            feedback = show_input(ctx.deps.workspace_name)
+            ctx.deps.thinking_animation.start()
+            return f"User did not confirm appending URL {fixture_url} and gave the following feedback: {feedback}"
+
+        if confirmation == "cancel":
+            ctx.deps.thinking_animation.start()
+            return f"User rejected appending URL {fixture_url}. Skip this step"
+
+        ctx.deps.thinking_animation.stop()
+        click.echo(FeedbackManager.highlight(message=f"\n» Appending {fixture_url} to {datasource_name}..."))
+        ctx.deps.append_data(datasource_name=datasource_name, path=fixture_url)
+        click.echo(FeedbackManager.success(message=f"✓ Data appended to {datasource_name}"))
+        ctx.deps.thinking_animation.start()
+        return f"Data appended to {datasource_name}"
+    except Exception as e:
+        ctx.deps.thinking_animation.stop()
+        click.echo(FeedbackManager.error(message=e))
+        ctx.deps.thinking_animation.start()
+        return f"Error appending URL {fixture_url} to {datasource_name}: {e}"

{tinybird-0.0.1.dev253 → tinybird-0.0.1.dev254}/tinybird.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.2
 Name: tinybird
-Version: 0.0.1.dev253
+Version: 0.0.1.dev254
 Summary: Tinybird Command Line Tool
 Home-page: https://www.tinybird.co/docs/forward/commands
 Author: Tinybird

{tinybird-0.0.1.dev253 → tinybird-0.0.1.dev254}/tinybird.egg-info/SOURCES.txt

@@ -87,6 +87,7 @@ tinybird/tb/modules/agent/models.py
 tinybird/tb/modules/agent/prompts.py
 tinybird/tb/modules/agent/utils.py
 tinybird/tb/modules/agent/tools/__init__.py
+tinybird/tb/modules/agent/tools/analyze.py
 tinybird/tb/modules/agent/tools/append.py
 tinybird/tb/modules/agent/tools/build.py
 tinybird/tb/modules/agent/tools/create_datafile.py
@@ -99,7 +100,6 @@ tinybird/tb/modules/agent/tools/get_openapi_definition.py
 tinybird/tb/modules/agent/tools/mock.py
 tinybird/tb/modules/agent/tools/plan.py
 tinybird/tb/modules/agent/tools/preview_datafile.py
-tinybird/tb/modules/agent/tools/read_fixture_data.py
 tinybird/tb/modules/agent/tools/request_endpoint.py
 tinybird/tb/modules/datafile/build.py
 tinybird/tb/modules/datafile/build_common.py

tinybird-0.0.1.dev253/tinybird/tb/modules/agent/tools/append.py

@@ -1,47 +0,0 @@
-import click
-from pydantic_ai import RunContext
-
-from tinybird.tb.modules.agent.utils import TinybirdAgentContext, show_confirmation, show_input
-from tinybird.tb.modules.feedback_manager import FeedbackManager
-
-
-def append(ctx: RunContext[TinybirdAgentContext], datasource_name: str, fixture_pathname: str) -> str:
-    """Append existing fixture to a datasource
-
-    Args:
-        datasource_name: Name of the datasource to append fixture to
-        fixture_pathname: Path to the fixture file to append
-
-    Returns:
-        str: Message indicating the success or failure of the appending
-    """
-    try:
-        ctx.deps.thinking_animation.stop()
-        confirmation = show_confirmation(
-            title=f"Append existing fixture for datasource {datasource_name}?",
-            skip_confirmation=ctx.deps.dangerously_skip_permissions,
-        )
-
-        if confirmation == "review":
-            click.echo()
-            feedback = show_input(ctx.deps.workspace_name)
-            ctx.deps.thinking_animation.start()
-            return (
-                f"User did not confirm appending {fixture_pathname} fixture and gave the following feedback: {feedback}"
-            )
-
-        if confirmation == "cancel":
-            ctx.deps.thinking_animation.start()
-            return f"User rejected appending {fixture_pathname} fixture. Skip this step"
-
-        ctx.deps.thinking_animation.stop()
-        click.echo(FeedbackManager.highlight(message=f"\n» Appending {fixture_pathname} to {datasource_name}..."))
-        ctx.deps.append_data(datasource_name=datasource_name, path=fixture_pathname)
-        click.echo(FeedbackManager.success(message=f"✓ Data appended to {datasource_name}"))
-        ctx.deps.thinking_animation.start()
-        return f"Data appended to {datasource_name}"
-    except Exception as e:
-        ctx.deps.thinking_animation.stop()
-        click.echo(FeedbackManager.error(message=e))
-        ctx.deps.thinking_animation.start()
-        return f"Error appending fixture {fixture_pathname} to {datasource_name}: {e}"

tinybird-0.0.1.dev253/tinybird/tb/modules/agent/tools/read_fixture_data.py

@@ -1,36 +0,0 @@
-import json
-from pathlib import Path
-
-import click
-from pydantic_ai import RunContext
-
-from tinybird.tb.modules.agent.utils import TinybirdAgentContext
-from tinybird.tb.modules.feedback_manager import FeedbackManager
-
-
-def read_fixture_data(ctx: RunContext[TinybirdAgentContext], fixture_pathname: str):
-    """Read fixture data in the project folder
-
-    Args:
-        fixture_pathname (str): a path to a fixture file. Required.
-
-    Returns:
-        str: The content of the fixture data file.
-    """
-    ctx.deps.thinking_animation.stop()
-    click.echo(FeedbackManager.highlight(message=f"» Analyzing {fixture_pathname}..."))
-    fixture_path = Path(ctx.deps.folder) / fixture_pathname.lstrip("/")
-
-    if not fixture_path.exists():
-        click.echo(FeedbackManager.error(message=f"No fixture data found for {fixture_pathname}."))
-        ctx.deps.thinking_animation.start()
-        return f"No fixture data found for {fixture_pathname}. Please check the name of the fixture and try again."
-
-    response = ctx.deps.analyze_fixture(fixture_path=str(fixture_path))
-    click.echo(FeedbackManager.success(message="✓ Done!\n"))
-    ctx.deps.thinking_animation.start()
-    # limit content to first 10 rows
-    data = response["preview"]["data"][:10]
-    columns = response["analysis"]["columns"]
-
-    return f"#Result of analysis of {fixture_pathname}:\n##Columns:\n{json.dumps(columns)}\n##Data sample:\n{json.dumps(data)}"