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

feat(backend): backend error handling strategy #89

Merged
merged 28 commits into from
Jan 15, 2025

Conversation

NarwhalChen
Copy link
Collaborator

@NarwhalChen NarwhalChen commented Jan 11, 2025

Summary by CodeRabbit

Release Notes

  • Error Handling

    • Introduced comprehensive error handling across multiple system components
    • Added new error classes for specific scenarios like configuration issues, file operations, and model interactions
    • Enhanced error logging and retry mechanisms
  • Code Structure

    • Refactored error management in build system handlers
    • Improved input validation across various modules
    • Implemented more robust error propagation strategies
  • Retry Mechanism

    • Added a centralized retry handler for managing transient errors
    • Implemented linear backoff strategy for retrying failed operations
  • Testing

    • Removed some test files related to model providers and project initialization

Copy link

coderabbitai bot commented Jan 11, 2025

Caution

Review failed

The pull request is closed.

Warning

There were issues while running some tools. Please review the errors and either fix the tool’s configuration or disable the tool if it’s a critical failure.

🔧 eslint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

backend/src/build-system/context.ts

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-prettier".

(The package "eslint-plugin-prettier" was not found when loaded as a Node module from the directory "/backend".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-prettier@latest --save-dev

The plugin "eslint-plugin-prettier" was referenced from the config file in "backend/.eslintrc.js".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.

Walkthrough

This pull request introduces a comprehensive error handling and validation framework across multiple build system handlers. The changes focus on implementing a robust error management strategy by introducing new error classes in errors.ts, enhancing input validation, and improving error propagation mechanisms. The modifications span various handlers in the backend, adding specific error types like RetryableError, NonRetryableError, and domain-specific errors to provide more granular error handling.

Changes

File Change Summary
backend/src/build-system/errors.ts Added comprehensive error hierarchy with RetryableError and NonRetryableError base classes
backend/src/build-system/context.ts Added retry handling and global promise tracking mechanisms
backend/src/build-system/retry-handler.ts Introduced new RetryHandler singleton for managing retry logic
Multiple handler files Updated to use new error classes, improved input validation, enhanced error propagation

Sequence Diagram

sequenceDiagram
    participant Handler
    participant RetryHandler
    participant ModelService
    
    Handler->>RetryHandler: Attempt operation
    alt Operation fails with retryable error
        RetryHandler->>ModelService: Retry operation
        alt Retry successful
            ModelService-->>RetryHandler: Return result
            RetryHandler-->>Handler: Return result
        else Max retries exceeded
            RetryHandler-->>Handler: Throw final error
        end
    else Operation successful
        ModelService-->>Handler: Return result
    end
Loading

Possibly related PRs

Suggested labels

enhancement, error-handling, refactoring

Suggested reviewers

  • Sma1lboy
  • ZHallen122

Poem

🐰 Errors dance, a coded ballet,
Retry and catch, they find their way
Robust and strong, our handlers sing
Of resilience that errors bring!
Code marches on, no fear in sight 🚀


📜 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 a78d34f and 85c09f1.

📒 Files selected for processing (18)
  • backend/src/build-system/__tests__/test.model-provider.spec.ts (0 hunks)
  • backend/src/build-system/__tests__/test.spec.ts (0 hunks)
  • backend/src/build-system/context.ts (11 hunks)
  • backend/src/build-system/errors.ts (1 hunks)
  • backend/src/build-system/handlers/backend/code-generate/index.ts (2 hunks)
  • backend/src/build-system/handlers/backend/file-review/file-review.ts (2 hunks)
  • backend/src/build-system/handlers/backend/requirements-document/index.ts (4 hunks)
  • backend/src/build-system/handlers/database/requirements-document/index.ts (1 hunks)
  • backend/src/build-system/handlers/database/schemas/schemas.ts (2 hunks)
  • backend/src/build-system/handlers/file-manager/file-arch/index.ts (1 hunks)
  • backend/src/build-system/handlers/file-manager/file-generate/index.ts (4 hunks)
  • backend/src/build-system/handlers/file-manager/file-structure/index.ts (4 hunks)
  • backend/src/build-system/handlers/product-manager/product-requirements-document/prd.ts (2 hunks)
  • backend/src/build-system/handlers/ux/datamap/index.ts (1 hunks)
  • backend/src/build-system/handlers/ux/sitemap-document/uxsmd.ts (2 hunks)
  • backend/src/build-system/handlers/ux/sitemap-structure/index.ts (1 hunks)
  • backend/src/build-system/handlers/ux/sitemap-structure/sms-page.ts (5 hunks)
  • backend/src/build-system/retry-handler.ts (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.

@NarwhalChen NarwhalChen force-pushed the feature-backend-error-handling-strategy branch from 1446ee3 to 169556e Compare January 11, 2025 21:21
@Sma1lboy Sma1lboy changed the title Feature backend error handling strategy feat(backend): backend error handling strategy Jan 12, 2025
Copy link
Owner

Choose a reason for hiding this comment

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

remove this change please, or put all into test-utils

@@ -17,12 +21,6 @@ export class FileStructureHandler implements BuildHandler<FileStructOutput> {
readonly id = 'op:FILE:STRUCT';
private readonly logger: Logger = new Logger('FileStructureHandler');

/**
Copy link
Owner

Choose a reason for hiding this comment

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

why remove this?

this.name = 'ModelTimeoutError';
}
}

Copy link
Owner

Choose a reason for hiding this comment

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

adding long description for each erorr

error instanceof RateLimitExceededError
) {
throw error; // Retryable errors will be handled externally.
}
Copy link
Owner

Choose a reason for hiding this comment

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

try {
      modelResponse = await this.callModel(context, backendCodePrompt);
    } catch (error) {

      throw error    
}

model: 'gpt-4o-mini',
messages: [{ content: filePrompt, role: 'system' }],
});
} catch (error) {
Copy link
Owner

Choose a reason for hiding this comment

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

this error handle with some issue just throw ModelUnavlible right now. non retry

await fs.writeFile(filePath, newContent, 'utf-8');
this.logger.log(`Successfully modified ${fileName}`);
} catch (error) {
this.handleFileProcessingError(fileName, error);
Copy link
Owner

Choose a reason for hiding this comment

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

you don't need extract this func

* @param context The builder context.
* @param prompt The generated prompt.
*/
private async callModel(
Copy link
Owner

Choose a reason for hiding this comment

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

if using callModel anywhere make it as export function and reuse it

* Calls the language model to generate database requirements.
* @param prompt The generated prompt.
*/
private async callModel(prompt: string): Promise<string> {
Copy link
Owner

Choose a reason for hiding this comment

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

dito

success: true,
data: schemaContent,
};
private handleModelErrors(error: any, stage: string): never {
Copy link
Owner

Choose a reason for hiding this comment

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

dito. remove this

@NarwhalChen NarwhalChen marked this pull request as ready for review January 15, 2025 02:42
@NarwhalChen NarwhalChen merged commit 5a2307c into main Jan 15, 2025
1 of 3 checks passed
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.

2 participants