search

panoratech / Panora

One API to connect your data sources to your LLMs
https://docs.panora.dev
Apache License 2.0
856 stars 179 forks source link

Fix Sync Feature #467

Closed mit-27 closed 4 months ago

mit-27 commented 4 months ago

Implemented Changes

vercel[bot] commented 4 months ago

@mit-27 is attempting to deploy a commit to the Panora Team on Vercel.

A member of the Team first needs to authorize it.

changeset-bot[bot] commented 4 months ago

⚠️ No Changeset found

Latest commit: 66aedfb2f278bb5760181c9350de2fa0aa12f07a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

coderabbitai[bot] commented 4 months ago

Walkthrough

The recent updates focus on enhancing the synchronization feature across various modules and services within the project. Key changes include integrating the CoreSyncService for initial synchronization, updating error handling in utility functions, and modifying the API reference documentation. Additionally, the connector update script has been refined, and the GitlabCommentMapper class has been improved for better handling of user and ticket IDs.

Changes

File Path Change Summary
.../connections.controller.ts Integrated CoreSyncService for initial sync, updated handleCallback method, added logging and redirect.
.../connections.module.ts Added new modules for CRM, ticketing, and syncing services, included CoreSyncService provider.
.../sync/sync.service.ts Added initialSync method, updated getSyncStatus method, imported necessary services and types.
.../ticketing/@lib/@utils/index.ts Modified error handling logic for tcg_contact retrieval.
.../utils/types/original/original.ticketing.ts Updated type declarations for OriginalAccountInput, OriginalCollectionInput, etc.
docs/api-reference/introduction.mdx Updated base URL information, changed tab title from "US Servers" to "Cloud," removed "EU Servers" tab.
scripts/connectorUpdate.js Updated variable names and file paths for connectors.
.../ticketing/comment/services/gitlab/mappers.ts Updated assignment of opts with user_id and ticket_id in GitlabCommentMapper class.

Sequence Diagram(s) (Beta)

sequenceDiagram
    participant Client
    participant ConnectionsController
    participant CoreSyncService
    participant CRMService
    participant AccountingService
    participant MarketingAutomationService
    participant TicketingService

    Client ->> ConnectionsController: handleCallback()
    ConnectionsController ->> CRMService: await crmService.handleCallback()
    ConnectionsController ->> AccountingService: await accountingService.handleCallback()
    ConnectionsController ->> MarketingAutomationService: await marketingAutomationService.handleCallback()
    ConnectionsController ->> TicketingService: await ticketingService.handleCallback()
    ConnectionsController ->> CoreSyncService: initialSync()
    CoreSyncService ->> Database: Sync Data
    CoreSyncService -->> ConnectionsController: Sync Complete
    ConnectionsController -->> Client: Redirect with status

Assessment against linked issues

Objective Addressed Explanation
Initial sync should trigger after connection creation (#431) ✅
Maintain sync order based on object associations (#431) ✅

Poem

In the code where sync does dance, We’ve made enhancements, took a chance. With services now in perfect tune, Data flows like a gentle monsoon. Bugs are squashed, the sync is bright, Our codebase shines in the moonlight. 🌙

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share - [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)
Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit .` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai generate interesting stats about this repository and render them as a table.` - `@coderabbitai show all the console.log statements in this repository.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
gitguardian[bot] commented 4 months ago

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | | | -------------- | ------------------ | ------------------------------ | ---------------- | --------------- | -------------------- | | [9763120](https://dashboard.gitguardian.com/workspace/489351/incidents/9763120) | Triggered | Generic High Entropy Secret | 66aedfb2f278bb5760181c9350de2fa0aa12f07a | docs/mint.json | [View secret](https://github.com/panoratech/Panora/commit/66aedfb2f278bb5760181c9350de2fa0aa12f07a#diff-c91a604899dfef4b2494c317f4fd39a7f22b79986095f580399347293d534debR10) |
🛠 Guidelines to remediate hardcoded secrets
1. Understand the implications of revoking this secret by investigating where it is used in your code. 2. Replace and store your secret safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/secrets-detection-engine/detectors/generics/generic_high_entropy_secret#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data. To avoid such incidents in the future consider - following these [best practices](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to catch secret before it leaves your machine and ease remediation.

🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.