Fixed wrong column name

[MasonXon]

Refactor column name frame_npu_image_01 to frame_npu_image_01

Summary by CodeRabbit

• New Features

  • Enhanced data seeding process for space_resources, runtime_frameworks, and runtime_architectures tables.
  • Improved handling of conflicts during data insertion.

• Bug Fixes

  • Modified column name from frame_npu_image_01 to frame_npu_image in the runtime_frameworks table, including adjustments to constraints.

• Chores

  • Updated sequence values for various ID sequences to ensure they reflect the maximum IDs in their respective tables.

[coderabbitai]

Walkthrough

This pull request focuses on modifying SQL initialization scripts across multiple deployment configurations (Docker Compose, Docker, and Helm Chart). The primary change involves renaming the column frame_npu_image_01 to frame_npu_image in the runtime_frameworks table. The scripts include conditional column renaming, dropping NOT NULL constraints, and updating data seeding processes for space_resources, runtime_frameworks, and runtime_architectures tables. The modifications ensure consistent database initialization across different deployment environments.

Changes

File	Change Summary
docker-compose/init-scripts/initialize.sql	- Renamed frame_npu_image_01 to frame_npu_image column - Added conditional NOT NULL constraint removal - Inserted seed data with ON CONFLICT handling - Updated sequence values for tables
docker/etc/server/initialize.sql	- Renamed frame_npu_image_01 to frame_npu_image column - Added conditional NOT NULL constraint removal - Inserted seed data with ON CONFLICT handling - Updated sequence values for tables
helm-chart/charts/csghub/charts/server/initialize.sql	- Renamed frame_npu_image_01 to frame_npu_image column - Added conditional NOT NULL constraint removal

Possibly related PRs

• Refactor initialize sql script to compatible with ce and ee #79: Modifications to initialize.sql script, including column renaming in runtime_frameworks table

Suggested reviewers

• wayneliu0019

Poem

🐰 In databases deep and wide,
Columns dance, constraints subside
From frame_npu_image_01 to new,
A rabbit's script rings crisp and true!
Seeds of data, sequences align
Migration magic, simply divine! 🔧

---

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

[starship-github]

The StarShip CodeReviewer was triggered but terminated because it encountered an issue: No files need to be reviewed based on the configured file extension policy.

Tips

CodeReview Commands (invoked as MR or PR comments)

• @codegpt /review to trigger an code review.
• @codegpt /evaluate to trigger code evaluation process.
• @codegpt /describe to regenerate the summary of the MR.
• @codegpt /secscan to scan security vulnerabilities for the MR or the Repository.
• @codegpt /help to get help.

CodeReview Discussion Chat

There are 2 ways to chat with Starship CodeReview:

• Review comments: Directly reply to a review comment made by StarShip.
  Example:
  • @codegpt How to fix this bug?
• Files and specific lines of code (under the "Files changed" tab):
  Tag @codegpt in a new review comment at the desired location with your query.
  Examples:
  • @codegpt generate unit testing code for this code snippet.

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 MR/PR comments.

CodeReview Documentation and Community

• Visit our Documentation
  for detailed information on how to use Starship CodeReview.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d79a278 and 88827ea.

📒 Files selected for processing (3)

• docker-compose/init-scripts/initialize.sql (1 hunks)
• docker/etc/server/initialize.sql (1 hunks)
• helm-chart/charts/csghub/charts/server/initialize.sql (1 hunks)

🔇 Additional comments (2)

docker/etc/server/initialize.sql (1)

105-105: Same issue as in Helm Chart initialization script.

docker-compose/init-scripts/initialize.sql (1)

105-105: Same issue as in Helm Chart initialization script.

[coderabbitai]

🛠️ Refactor suggestion

Consider checking for both old and new column names during migration.

The EXISTS check only looks for the new column name frame_npu_image. This could cause issues if the script runs on a database where the column hasn't been renamed yet.

Consider modifying the check to handle both column names:

-            AND column_name = 'frame_npu_image'
+            AND column_name IN ('frame_npu_image_01', 'frame_npu_image')

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	AND column_name = 'frame_npu_image'
	AND column_name IN ('frame_npu_image_01', 'frame_npu_image')

[starship-github]

The StarShip CodeReviewer was triggered but terminated because it encountered an issue: The MR state is not opened.

Tips

CodeReview Commands (invoked as MR or PR comments)

• @codegpt /review to trigger an code review.
• @codegpt /evaluate to trigger code evaluation process.
• @codegpt /describe to regenerate the summary of the MR.
• @codegpt /secscan to scan security vulnerabilities for the MR or the Repository.
• @codegpt /help to get help.

CodeReview Discussion Chat

There are 2 ways to chat with Starship CodeReview:

• Review comments: Directly reply to a review comment made by StarShip.
  Example:
  • @codegpt How to fix this bug?
• Files and specific lines of code (under the "Files changed" tab):
  Tag @codegpt in a new review comment at the desired location with your query.
  Examples:
  • @codegpt generate unit testing code for this code snippet.

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 MR/PR comments.

CodeReview Documentation and Community

• Visit our Documentation
  for detailed information on how to use Starship CodeReview.

[starship-github]

The StarShip CodeReviewer was triggered but terminated because it encountered an issue: The MR state is not opened.

Tips

CodeReview Commands (invoked as MR or PR comments)

• @codegpt /review to trigger an code review.
• @codegpt /evaluate to trigger code evaluation process.
• @codegpt /describe to regenerate the summary of the MR.
• @codegpt /secscan to scan security vulnerabilities for the MR or the Repository.
• @codegpt /help to get help.

CodeReview Discussion Chat

There are 2 ways to chat with Starship CodeReview:

• Review comments: Directly reply to a review comment made by StarShip.
  Example:
  • @codegpt How to fix this bug?
• Files and specific lines of code (under the "Files changed" tab):
  Tag @codegpt in a new review comment at the desired location with your query.
  Examples:
  • @codegpt generate unit testing code for this code snippet.

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 MR/PR comments.

CodeReview Documentation and Community

• Visit our Documentation
  for detailed information on how to use Starship CodeReview.