Skip to content

epic/B11: delete local NVMS implementation after repoint#227

Open
KooshaPari wants to merge 1 commit into
mainfrom
epic/B11-delete-local-nvms-impl
Open

epic/B11: delete local NVMS implementation after repoint#227
KooshaPari wants to merge 1 commit into
mainfrom
epic/B11-delete-local-nvms-impl

Conversation

@KooshaPari

@KooshaPari KooshaPari commented Jun 25, 2026

Copy link
Copy Markdown
Owner

User description

Deletes the local NVMS implementation (backend/nvms Go module, backend/nvms.rs Rust parser, backend/odin.nvms config) after B10 repoint to external phenotype-sdk. Updates Taskfile.yml and justfile to remove stale backend/nvms references.


CodeAnt-AI Description

Remove the old local NVMS backend and its stale build references

What Changed

  • Deleted the local NVMS implementation, including its Go services, support libraries, Rust parser, examples, and related module files
  • Removed NVMS from Go formatting and hygiene checks so repo tasks only point to the remaining backend
  • Removed the old NVMS entries from the project manifest and packaging files

Impact

✅ Fewer broken build checks
✅ No stale NVMS paths in repo tasks
✅ Cleaner project layout for the new external NVMS setup

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

Deletes the local NVMS implementation (backend/nvms Go module, backend/nvms.rs Rust parser, backend/odin.nvms config) after B10 repoint to external phenotype-sdk. Updates Taskfile.yml and justfile to remove stale backend/nvms references.
@codeant-ai

codeant-ai Bot commented Jun 25, 2026

Copy link
Copy Markdown

CodeAnt AI is reviewing your PR.

@codeant-ai

codeant-ai Bot commented Jun 25, 2026

Copy link
Copy Markdown

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@github-actions

Copy link
Copy Markdown

Legacy Tooling Scan Report

Severity Count
Critical 0
High 0
Medium 0
Low 0

No violations detected.

This is a WARN-mode scan. Fix before strict enforcement begins.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request completely removes the backend/nvms engine and all of its associated components, including the Spin services (demonstrator, provisioner, builder, and nvms), its core libraries, models, and example configuration files. Additionally, the project's task runners (Taskfile.yml and justfile) have been updated to remove references to the deleted nvms directory, leaving backend/byteport as the sole primary Go backend. As there are no review comments provided, I have no additional feedback to offer.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

@sonarqubecloud

Copy link
Copy Markdown

@codeant-ai codeant-ai Bot added the size:XS This PR changes 0-9 lines, ignoring generated files label Jun 25, 2026
@codeant-ai

codeant-ai Bot commented Jun 25, 2026

Copy link
Copy Markdown

CodeAnt AI finished reviewing your PR.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8bf4ada1f0

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread backend/nvms/go.mod
@@ -1,22 +0,0 @@
module nvms

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Remove nvms from active CI workflows

After deleting this module, the active PR/push workflow still includes backend/nvms in the Go vet/build matrix and feeds ${{ matrix.module }}/go.mod to actions/setup-go (.github/workflows/ci.yaml:20-34 and .github/workflows/ci.yaml:43-57); the Audit workflow also enters working-directory: backend/nvms before its go.mod guard (.github/workflows/audit.yml:171-178). Any PR or push with this commit now checks out a tree without backend/nvms/go.mod or the directory, so these workflow legs fail before the updated Taskfile/just recipes matter; please remove or repoint those workflow entries with the module deletion.

Useful? React with 👍 / 👎.

@kilo-code-bot

kilo-code-bot Bot commented Jun 26, 2026

Copy link
Copy Markdown

Code Review Summary

Status: 4 Issues Found | Recommendation: Address before merge

Overview

Severity Count
CRITICAL 2
WARNING 2
SUGGESTION 0
Issue Details (click to expand)

CRITICAL

File Line Issue
.github/workflows/ci.yaml 23 Still references backend/nvms in matrix - will cause CI failure after merge when nvms is deleted
.github/workflows/ci.yaml 46 Still references backend/nvms in matrix - will cause CI failure after merge when nvms is deleted

WARNING

File Line Issue
.github/workflows/ci.yaml 74 Still references backend/nvms in gofmt check - will fail after nvms deletion
.github/workflows/audit.yml 151-178 Still references backend/nvms/go.sum and working-directory: backend/nvms - will cause failures after merge
Files Reviewed
  • Taskfile.yml - Clean (removes nvms references correctly)
  • justfile - Clean (no nvms references)
  • .github/workflows/ci.yaml - Stale nvms references remain
  • .github/workflows/ci.yml - Stale nvms reference in gofmt check (line 109)
  • .github/workflows/audit.yml - Stale nvms references in govulncheck job

Fix these issues in Kilo Cloud


Reviewed by laguna-m.1-20260312:free · Input: 1M · Output: 7.1K · Cached: 277.9K

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XS This PR changes 0-9 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant