- Add @duckdb/node-bindings as explicit dependency
- Mark all DuckDB native binding packages as external in build config
- This ensures native modules are available at runtime without bundling
- Implemented tests for Slack notification skip logic based on issue and assumption conditions.
- Updated the main task to skip notifications when no issues are found and no major assumptions exist.
- Enhanced workflow to handle undefined `isSlackFollowUp` correctly, ensuring proper message formatting and notification sending.
- Added new deployment functionality to handle both models and documentation in a single request.
- Introduced new schemas for unified deployment requests and responses using Zod.
- Updated deployment handlers to process and validate models and docs together.
- Enhanced logging to provide detailed information about deleted models and docs during deployment.
- Refactored existing code to integrate the new deployment structure, ensuring backward compatibility with previous functionalities.
- Added `TURBOPUFFER_REGION` to the environment configuration.
- Modified the `createClient` function to utilize the new `TURBOPUFFER_REGION` variable.
- Updated the `generateNamespace` function to return the data source ID directly instead of prefixing it.
- Adjusted various tests and sync job logic to reflect changes in namespace generation and ensure consistency across the application.
- Introduced the `processSyncJob` function to handle the complete workflow for syncing searchable values, including fetching credentials, querying distinct values, deduplication, generating embeddings, and upserting to Turbopuffer.
- Added support for the `@buster/search` package in the project configuration.
- Updated dependencies to version 4.0.2 for `@trigger.dev/build`, `@trigger.dev/core`, and `@trigger.dev/sdk`.
- Enhanced logging for better traceability during the sync process.
- Added bucketName to S3 integration responses and handlers to support bucket-specific operations.
- Updated tests to reflect the inclusion of bucketName in integration creation and retrieval processes.
- Improved error handling for fetching bucket names from the vault during S3 integration retrieval.
These changes improve the S3 integration management by allowing for more granular control and visibility of storage buckets.
- Simplified S3 integration handler functions by consolidating imports and improving code readability.
- Updated error handling in the S3 integration process to enhance clarity and maintainability.
- Refactored storage provider functions to utilize a more modular approach, separating concerns for better organization.
- Introduced utility functions for common operations, improving code reuse and reducing duplication.
These changes enhance the overall structure and maintainability of the S3 integration management features.
- Added routes for creating, retrieving, and deleting S3 integrations in the API.
- Introduced handlers for S3 integration operations, including validation of user permissions and storage credentials.
- Updated database schema to support S3 integrations, including a new table and associated queries.
- Integrated storage provider logic to handle S3, R2, and GCS configurations.
- Enhanced error handling and response structures for integration operations.
This commit lays the groundwork for managing storage integrations within the application, allowing users to connect and manage their S3 storage solutions.
- Upgraded '@aws-sdk/client-s3' to version 3.873.0 across multiple packages.
- Introduced caching mechanisms for metric data retrieval in the getMetricDataHandler function.
- Updated API endpoints to support report_file_id for cache lookups and data retrieval.
- Enhanced error handling and logging for cache operations.
- Refactored related components to accommodate new caching logic and parameters.
dal
Nate Kelley
Nate Kelley
wellsbunk5
Wells Bunker