Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add perplexity prompter #327

Merged
merged 1 commit into from
Jan 11, 2025
Merged

add perplexity prompter #327

merged 1 commit into from
Jan 11, 2025

Conversation

Southclaws
Copy link
Owner

No description provided.

Copy link

vercel bot commented Dec 23, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
storyden ⬜️ Ignored (Inspect) Visit Preview Jan 11, 2025 1:56pm
storyden-homepage ⬜️ Ignored (Inspect) Visit Preview Jan 11, 2025 1:56pm

Copy link

coderabbitai bot commented Dec 23, 2024

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The pull request introduces significant changes to the Semdex service's asker functionality. A new configuration structure is established with additional fields for asker provider and Perplexity API key. The asker implementation has been refactored to support multiple providers, with a default implementation and a new Perplexity-specific asker. The changes enable more flexible question-answering capabilities by allowing different AI providers to be used dynamically based on configuration.

Changes

File Change Summary
internal/config/config.go Added AskerProvider and PerplexityAPIKey fields to Config struct
app/services/semdex/asker/asker.go Refactored New function to return semdex.Asker, added buildContextPrompt function
app/services/semdex/asker/default.go Introduced defaultAsker struct with Ask method
app/services/semdex/asker/perplexity.go Added new Perplexity AI provider implementation with streaming API support
app/services/semdex/semdexer/semdexer.go Removed fx.Annotate for asker dependency injection

Sequence Diagram

sequenceDiagram
    participant User
    participant Asker
    participant Searcher
    participant AIProvider
    
    User->>Asker: Ask query
    Asker->>Searcher: Retrieve context
    Searcher-->>Asker: Return search results
    Asker->>AIProvider: Send augmented prompt
    AIProvider-->>Asker: Stream response
    Asker-->>User: Deliver answer
Loading

Poem

🐰 A Rabbit's Ode to Askers New

Providers dance, a flexible crew
Perplexity joins the chatty line
Searching deep with logic divine
From context rich to answers bright
Our asker leaps with coding might!

🌟 Hop, hop, hooray! 🌟


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 31d5838 and 565c6f3.

⛔ Files ignored due to path filters (2)
  • go.mod is excluded by !**/*.mod
  • go.sum is excluded by !**/*.sum, !**/*.sum
📒 Files selected for processing (5)
  • app/services/semdex/asker/asker.go (3 hunks)
  • app/services/semdex/asker/default.go (1 hunks)
  • app/services/semdex/asker/perplexity.go (1 hunks)
  • app/services/semdex/semdexer/semdexer.go (1 hunks)
  • internal/config/config.go (1 hunks)

Finishing Touches

  • 📝 Generate Docstrings (Beta)

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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 using 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 generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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 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 for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (2)
internal/infrastructure/ai/perplexity.go (2)

19-21: Correct the typo for the timeout constant name.
It appears there is a typographical error: "DefautTimeout" should be "DefaultTimeout" for clarity and consistency.

-	DefautTimeout   = 10 * time.Second
+	DefaultTimeout  = 10 * time.Second

73-82: Consider making the API key field configurable for Perplexity.
Currently, it uses cfg.OpenAIKey. If this key is specific to Perplexity, rename it to reflect "PerplexityKey" in the config for improved clarity and maintainability. Otherwise, ensure that using cfg.OpenAIKey is intentional.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between eb54157 and c77df16.

⛔ Files ignored due to path filters (2)
  • go.mod is excluded by !**/*.mod
  • go.sum is excluded by !**/*.sum, !**/*.sum
📒 Files selected for processing (2)
  • internal/infrastructure/ai/ai.go (1 hunks)
  • internal/infrastructure/ai/perplexity.go (1 hunks)
🔇 Additional comments (2)
internal/infrastructure/ai/perplexity.go (1)

136-177: Revisit unsubscribing logic in streaming callback.
In lines 145, 151, and 166, the subscription is managed multiple times (subscribe once and unsubscribe twice). Make sure that unsubscribing more than once doesn't produce undefined behavior or race conditions.

internal/infrastructure/ai/ai.go (1)

24-26: Implement configuration checks for Perplexity initialization.
Ensure that all relevant Perplexity configuration fields (endpoint, key, model) are validated. Otherwise, the function may succeed with incorrect configuration.

internal/infrastructure/ai/perplexity.go Outdated Show resolved Hide resolved
internal/infrastructure/ai/perplexity.go Outdated Show resolved Hide resolved
@Southclaws Southclaws force-pushed the perplexity branch 2 times, most recently from c5c614e to 31d5838 Compare December 29, 2024 13:07
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (4)
internal/infrastructure/ai/perplexity.go (3)

18-18: Typographical error: "DefautTimeout" → "DefaultTimeout"
Consider correcting this constant name for clarity and consistency.

-	DefautTimeout   = 10 * time.Second
+	DefaultTimeout  = 10 * time.Second

72-81: Validate API key presence
If cfg.PerplexityAPIKey is empty, subsequent API calls will fail. Consider returning an error early to avoid silently configured instances.

func newPerplexity(cfg config.Config) (*Perplexity, error) {
	if cfg.PerplexityAPIKey == "" {
+		return nil, fmt.Errorf("Perplexity API key is missing")
	}
    s := &Perplexity{
        ...
    }
    return s, nil
}

78-78: Use renamed constant
After renaming DefautTimeout, ensure that references are updated accordingly.

-	httpTimeout: DefautTimeout,
+	httpTimeout: DefaultTimeout,
internal/config/config.go (1)

53-53: Secure API key handling
Use a secrets manager or environment variable best practices to avoid accidental logging or exposure of PerplexityAPIKey.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c77df16 and 31d5838.

⛔ Files ignored due to path filters (2)
  • go.mod is excluded by !**/*.mod
  • go.sum is excluded by !**/*.sum, !**/*.sum
📒 Files selected for processing (3)
  • internal/config/config.go (1 hunks)
  • internal/infrastructure/ai/ai.go (1 hunks)
  • internal/infrastructure/ai/perplexity.go (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • internal/infrastructure/ai/ai.go
🔇 Additional comments (3)
internal/infrastructure/ai/perplexity.go (3)

130-132: Validate r.Choices length before usage
Accessing r.Choices[0] might cause an out-of-range error if len(r.Choices) is zero.

	return &Result{
-		Answer: r.Choices[0].Message.Content,
+		Answer: func() string {
+			if len(r.Choices) > 0 {
+				return r.Choices[0].Message.Content
+			}
+			return ""
+		}(),
	}, nil

206-208: Avoid panic in placeholder method
Return an error or a stub instead of calling panic("not implemented").

func (o *Perplexity) EmbeddingFunc() func(ctx context.Context, text string) ([]float32, error) {
-	panic("not implemented")
+	return func(ctx context.Context, text string) ([]float32, error) {
+		return nil, fmt.Errorf("embedding not implemented yet")
+	}
}

187-191: ⚠️ Potential issue

Guard against empty Choices during streaming
If len(cr.Choices) is zero, accessing cr.Choices[0].Delta.Content or cr.Choices[0].FinishReason will cause an out-of-range error.

-			outch <- cr.Choices[0].Delta.Content
-
-			if cr.Choices[0].FinishReason == "stop" {
-				break
-			}
+			if len(cr.Choices) > 0 {
+				outch <- cr.Choices[0].Delta.Content
+				if cr.Choices[0].FinishReason == "stop" {
+					break
+				}
+			}

Likely invalid or redundant comment.

@Southclaws Southclaws merged commit 0721fd0 into main Jan 11, 2025
4 checks passed
@Southclaws Southclaws deleted the perplexity branch January 11, 2025 14:03
@coderabbitai coderabbitai bot mentioned this pull request Jan 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant