Skip to content

fix: update stale issue/PR state in similar threads#61

Merged
Kavirubc merged 1 commit intosimiligh:mainfrom
mahsumaktas:fix/stale-issue-state-59
Feb 15, 2026
Merged

fix: update stale issue/PR state in similar threads#61
Kavirubc merged 1 commit intosimiligh:mainfrom
mahsumaktas:fix/stale-issue-state-59

Conversation

@mahsumaktas
Copy link
Copy Markdown
Contributor

@mahsumaktas mahsumaktas commented Feb 14, 2026

Summary

Fixes #59 — Closed issues and PRs were incorrectly shown as "Open" in Simili bot comments.

Root Cause

When issues/PRs are indexed into Qdrant, their state is stored at index time. When the issue is later closed or reopened, the stored state is never updated because:

  1. Bulk indexer (simili index) did not store state or title in payload at all
  2. No state-update path existed — the only option was full re-embedding (expensive and unnecessary)
  3. Similarity search defaulted missing state to "open", masking the problem

Changes

File Change
qdrant/types.go Add SetPayload to VectorStore interface
qdrant/client.go Implement SetPayload — updates payload fields without re-uploading vectors
steps/indexer.go Detect closed/reopened events → patch state via SetPayload (no re-embed)
commands/index.go Include state and title in bulk indexer payloads
steps/similarity.go Default missing state to "unknown" instead of "open"
steps/response_builder.go Render unknown state as in status column
gemini/prompts.go Pass actual state to LLM prompt instead of assuming open

How It Works

Close event → indexer detects EventAction="closed"
           → generates deterministic UUID (same as original index)
           → calls SetPayload(id, {state: "closed"})
           → Qdrant updates payload in-place, vector untouched
           → next similarity search reads correct state

Testing

  • go build ./...
  • go vet ./...
  • go test ./... ✅ (all 8 packages pass)

Backward Compatibility

  • Existing indexed points without state field will show instead of incorrectly showing Open
  • Running simili index --repo ... will now store state for all new/updated points
  • No breaking changes to config or CLI flags

Summary by CodeRabbit

  • New Features

    • Optimized indexing for state-only changes (e.g., when issues are opened or closed) to skip unnecessary re-embedding and improve performance.
    • Issue state and title fields now tracked alongside indexed content.
  • Improvements

    • Enhanced state handling for similar issues with more explicit and consistent display logic to properly handle all state variations.

Issues and PRs indexed in Qdrant retained their original state forever.
When a similar thread was later closed, it still appeared as 'Open' in
bot comments because the vector DB payload was never updated.

Root causes:
1. Bulk indexer (index command) did not store 'state' or 'title' in payload
2. No mechanism to update state on close/reopen events without re-embedding
3. Similarity search defaulted missing state to 'open'

Changes:
- Add SetPayload method to Qdrant client (update payload without re-upload)
- Add VectorStore.SetPayload to the interface
- Indexer: detect close/reopen events and patch state via SetPayload
- Bulk indexer: include 'state' and 'title' fields in chunked payloads
- Similarity search: default missing state to 'unknown' instead of 'open'
- Response builder: render 'unknown' state as '—' in the status column
- LLM prompts: pass through actual state instead of assuming 'open'

Fixes #59

Signed-off-by: Mahsum Aktas <mahsum@mahsumaktas.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Feb 14, 2026

📝 Walkthrough

Walkthrough

The PR fixes a bug where closed issues and PRs incorrectly display as "Open" in similarity suggestions. It adds state and title fields to chunk payloads, implements a SetPayload method for updating Qdrant points without re-embedding, detects state-change-only events to optimize indexing, and updates status derivation logic across multiple components.

Changes

Cohort / File(s) Summary
Qdrant Vector Store Enhancement
internal/integrations/qdrant/types.go, internal/integrations/qdrant/client.go
Added SetPayload method to VectorStore interface and Client implementation to update payload fields on existing points without re-uploading vectors, enabling efficient state updates.
Index Payload Enhancement
cmd/simili/commands/index.go
Extended chunk payload to include "state" (issue.GetState()) and "title" (issue.GetTitle()) fields before upserting to Qdrant.
Status Derivation Logic
internal/integrations/gemini/prompts.go, internal/steps/response_builder.go, internal/steps/similarity.go
Fixed status representation: changed from hard-coded "Open" default to deriving status directly from state field, with explicit handling of empty/unknown states, ensuring closed issues display correctly throughout response building and similar-issue detection.
State-Change Optimization
internal/steps/indexer.go
Added isStateChangeOnly() helper to detect state-change-only events and introduced updateState() method to patch only the state field via SetPayload, bypassing expensive re-embedding for closure events.

Sequence Diagram

sequenceDiagram
    participant Event as Webhook Event
    participant Indexer as Indexer.Run()
    participant StateDetect as isStateChangeOnly()
    participant UpdatePath as updateState()
    participant EmbedPath as Embedding Pipeline
    participant Qdrant as Qdrant

    Event->>Indexer: Issue state changed
    Indexer->>StateDetect: Check if state-change-only
    
    alt State Change Only
        StateDetect-->>Indexer: true
        Indexer->>UpdatePath: updateState(collectionName)
        UpdatePath->>Qdrant: SetPayload(state field only)
        Qdrant-->>UpdatePath: ✓ Updated
        UpdatePath-->>Indexer: Marked as indexed
    else Full Reindex Required
        StateDetect-->>Indexer: false
        Indexer->>EmbedPath: Fetch comments & build content
        EmbedPath->>EmbedPath: Generate embedding
        EmbedPath->>Qdrant: Upsert point with state & title
        Qdrant-->>EmbedPath: ✓ Upserted
        EmbedPath-->>Indexer: Marked as indexed
    end
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

Suggested reviewers

  • Kavirubc

Poem

🐰 Hop hop, the state's now true!
No more faking "open blue,"
Closed stays closed in every view,
SetPayload skips the work we're through!
State-change fast, no re-embed too,
Simili's fixed—hip hip, wahoo! 🎉

🚥 Pre-merge checks | ✅ 5 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 75.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The PR title clearly and concisely describes the main fix: addressing stale issue/PR state display in similar threads, which directly matches the core objective of fixing closed issues shown as open.
Linked Issues check ✅ Passed All code changes comprehensively address issue #59: state and title are now included in payloads [index.go], a lightweight state-update path bypasses re-embedding [indexer.go], missing state defaults to 'unknown' instead of 'open' [similarity.go], and status rendering handles unknown states [response_builder.go, gemini/prompts.go].
Out of Scope Changes check ✅ Passed All changes are directly scoped to fixing issue #59: adding state/title to payloads, implementing state-only updates via SetPayload, detecting state-change events, and correcting state display logic. No unrelated changes are present.
Merge Conflict Detection ✅ Passed ✅ No merge conflicts detected when merging into main

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Comment @coderabbitai help to get the list of available commands and usage tips.

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • No explicit step-by-step reproduction steps
  • Missing environment details
  • Add explicit reproduction steps to demonstrate the bug (e.g., create issue, close it, observe Simili bot comment)
  • Include relevant environment details (e.g., Qdrant version, Simili bot version) if applicable
Similar Threads
Similarity Thread Status
83% #48 Similar Issue Open
81% #48 feat: CLI PR indexing (#46) & standardized embe... Open
81% #48 Similar Issue Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Lack of explicit step-by-step reproduction instructions
  • No explicit 'Expected vs. Actual' behavior statement
  • Add clear, step-by-step instructions to reproduce the bug
  • Specify the 'Expected Behavior' and 'Actual Behavior' when the bug occurs
Similar Threads
Similarity Thread Status
83% #48 Similar Issue Open
81% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Missing explicit step-by-step reproduction instructions
  • Include clear, numbered reproduction steps to demonstrate the bug, even if the root cause is well-understood.
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

Copy link
Copy Markdown

@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: 1

🤖 Fix all issues with AI agents
In `@internal/steps/indexer.go`:
- Around line 73-76: When isStateChangeOnly(ctx) is true, s.updateState(ctx,
collectionName) may fail if the point is missing — catch the error from
s.updateState and, instead of returning immediately, attempt the full indexing
path used for non-state changes (i.e., invoke the same full-index handler/code
that runs when isStateChangeOnly is false); if the fallback full-indexing
succeeds, proceed normally, otherwise return the error from the full-index
attempt. Ensure you log or surface both the original updateState error and the
fallback result for debugging and keep existing context (ctx, collectionName)
when calling the fallback.

Comment thread internal/steps/indexer.go
Comment on lines +73 to +76
// For close/reopen events, only update the state payload — no need to re-embed.
if isStateChangeOnly(ctx) {
return s.updateState(ctx, collectionName)
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

Fallback needed if state-only update fails.

If the point doesn’t exist (e.g., issue never indexed or index was reset), updateState will return an error and the event won’t be indexed at all. Consider falling back to full indexing on failure to keep state fresh and avoid pipeline errors.

🛠️ Suggested fallback to full indexing
-	if isStateChangeOnly(ctx) {
-		return s.updateState(ctx, collectionName)
-	}
+	if isStateChangeOnly(ctx) {
+		if err := s.updateState(ctx, collectionName); err == nil {
+			return nil
+		} else {
+			log.Printf("[indexer] State-only update failed; falling back to full index: %v", err)
+		}
+	}
📝 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
// For close/reopen events, only update the state payload — no need to re-embed.
if isStateChangeOnly(ctx) {
return s.updateState(ctx, collectionName)
}
// For close/reopen events, only update the state payload — no need to re-embed.
if isStateChangeOnly(ctx) {
if err := s.updateState(ctx, collectionName); err == nil {
return nil
} else {
log.Printf("[indexer] State-only update failed; falling back to full index: %v", err)
}
}
🤖 Prompt for AI Agents
In `@internal/steps/indexer.go` around lines 73 - 76, When isStateChangeOnly(ctx)
is true, s.updateState(ctx, collectionName) may fail if the point is missing —
catch the error from s.updateState and, instead of returning immediately,
attempt the full indexing path used for non-state changes (i.e., invoke the same
full-index handler/code that runs when isStateChangeOnly is false); if the
fallback full-indexing succeeds, proceed normally, otherwise return the error
from the full-index attempt. Ensure you log or surface both the original
updateState error and the fallback result for debugging and keep existing
context (ctx, collectionName) when calling the fallback.

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 9.5/10 (Excellent)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • The 'Changes' table appears to be truncated
  • Ensure all intended details in tables are fully visible
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • No explicit reproduction steps
  • No environment details (e.g., OS, specific versions of Simili/Qdrant)
  • While the problem is well-described, adding explicit steps to reproduce the incorrect state display would enhance completeness.
  • Specify the environment where the bug was observed (e.g., OS, Simili bot version, Qdrant version) for full context, though less critical for a fix description.
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 9.2/10 (Excellent)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Missing explicit step-by-step reproduction instructions
  • Add explicit step-by-step instructions to reproduce the bug, even if simple (e.g., '1. Close an issue. 2. Observe Simili bot comments on similar threads.').
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Missing explicit reproduction steps
  • No environment details (e.g., OS, Simili version, Qdrant version)
  • Add explicit step-by-step instructions on how to reproduce the bug
  • Specify the operating system and versions of Simili bot and Qdrant used when the bug was observed
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • No explicit verification steps for the fix
  • No environment details specified
  • Add a 'Verification Steps' section to outline how to confirm the fix is working (e.g., 'After applying the fix, close an issue and observe Simili bot comments on similar threads to ensure its state is correctly reflected as 'Closed').
  • While not strictly necessary for this specific issue, for future issues, consider adding environment details if they could be relevant.
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • No explicit step-by-step reproduction guide (though the problem is clearly described)
  • No environment details (OS, version, etc.)
  • Add explicit reproduction steps, e.g., '1. Create an issue. 2. Close it. 3. Observe Simili bot comment on a similar thread.'
  • Specify the environment where the issue was observed (e.g., GitHub Enterprise, Simili bot version)
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Missing explicit step-by-step reproduction instructions
  • While the root cause is very clear, adding explicit step-by-step reproduction instructions would make the issue even more robust for future reference or new contributors.
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Missing explicit reproduction steps
  • No environment details (e.g., Simili version, Qdrant version, OS)
  • Add explicit step-by-step reproduction instructions
  • Specify relevant environment details (e.g., Simili bot version, Qdrant version, operating system)
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Missing explicit reproduction steps
  • No environment details (e.g., bot version, Qdrant version)
  • No screenshot demonstrating the incorrect state
  • Add explicit step-by-step instructions to reproduce the bug
  • Specify the environment details where the bug was observed (e.g., Simili bot version, Qdrant version, GitHub platform)
  • Include a screenshot showing a 'closed' issue/PR incorrectly displayed as 'open' by the Simili bot
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Lack of explicit reproduction steps
  • No concrete example of an affected issue/PR
  • Add explicit steps to reproduce the bug (e.g., '1. Close an issue. 2. Wait for Simili bot to comment on a similar thread. 3. Observe the state of the closed issue in the bot's comment.')
  • Provide a link to an example issue/PR where the incorrect state was observed
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • No explicit reproduction steps provided within this issue (relies on [Bug]: Closed Issues and PRs are shown as Open in Simili Comment #59)
  • No specific environment details (e.g., Simili bot version, Qdrant version) mentioned
  • Briefly outline the reproduction steps or expected behavior for verification within this issue, even if linking to the original bug.
  • Specify relevant environment details, such as the versions of Simili bot and Qdrant being used or targeted.
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • No explicit reproduction steps provided (though the problem is clearly described)
  • No environment details (e.g., Simili bot version, Qdrant version) specified
  • For future bug reports, include explicit steps to reproduce the incorrect behavior
  • Consider adding relevant version information for the affected systems (e.g., Simili bot, Qdrant) if applicable
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 9.0/10 (Excellent)
The issue is well-described.

Classification

Category Value
Labels
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 9.5/10 (Excellent)
The issue is well-described.

Classification

Category Value
Labels
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • No explicit step-by-step reproduction steps
  • No environment details (OS, version, etc.)
  • Add explicit steps to reproduce the bug, e.g., '1. Close an issue/PR. 2. Observe Simili bot comment on a similar thread.'
  • Specify the environment where the bug was observed (e.g., 'Observed on Simili bot running on GitHub Actions')
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Missing explicit reproduction steps
  • Missing environment details
  • Add explicit step-by-step instructions to reproduce the bug (e.g., create issue, close it, observe bot comments)
  • Include relevant environment details such as Simili bot version, Qdrant version, and Go version
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 9.0/10 (Excellent)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Explicit reproduction steps are not provided (though easily inferable)
  • Environment details (e.g., bot version, deployment platform) are not specified
  • For future bug reports, include explicit, step-by-step reproduction instructions.
  • Consider adding environment details relevant to the bot's operation or data storage.
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 9.2/10 (Excellent)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Missing explicit reproduction steps
  • No environment details
  • Include explicit step-by-step reproduction instructions for clarity, even for a fix
  • Specify relevant environment details (e.g., Simili bot version, Qdrant version) for comprehensive context
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 9.2/10 (Excellent)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Missing explicit 'Steps to Reproduce' section
  • Missing environment details (e.g., Simili bot version, Qdrant version)
  • For future bug reports, include a dedicated 'Steps to Reproduce' section.
  • Specify relevant environment details (e.g., Simili bot version, Qdrant version, OS) for better context.
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • No explicit step-by-step reproduction instructions
  • No environment details (OS, versions, etc.)
  • No specific error logs provided
  • For future bug reports, include explicit step-by-step reproduction instructions to verify the fix or reproduce the original bug.
  • Specify the operating system, relevant software versions, and any other environmental factors where the bug was observed.
  • Include any relevant error messages or logs that were observed when the bug occurred.
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Explicit step-by-step reproduction steps for the original bug are not included
  • No environment details (e.g., bot deployment environment, specific versions)
  • For future bug reports, include explicit step-by-step reproduction instructions
  • Specify relevant environment details if they could impact the bug or fix
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • No explicit step-by-step reproduction instructions
  • Missing specific environment details
  • Include a dedicated 'Steps to Reproduce' section for clarity, even for a fix description
  • Provide relevant environment details (e.g., OS, versions of key dependencies like Qdrant, Go)
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 9.5/10 (Excellent)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • No explicit 'Steps to Reproduce' section
  • Missing environment details (e.g., specific Qdrant version, Go version, if relevant)
  • Add a dedicated 'Steps to Reproduce' section, even if simple, to ensure clarity for all readers.
  • Include relevant environment details (OS, specific library/tool versions) if the bug or fix is dependent on them.
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • No explicit reproduction steps provided
  • Missing environment details (e.g., specific versions of Simili bot, Qdrant, or OS)
  • Add explicit steps to reproduce the incorrect behavior for verification purposes
  • Include relevant environment details such as Simili bot version, Qdrant version, or operating system if applicable
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 9.9/10 (Excellent)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Missing explicit reproduction steps for the original bug
  • While the problem is clearly described, adding step-by-step instructions to reproduce the 'stale state' problem could enhance completeness for future reference or verification.
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 9.2/10 (Excellent)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • No explicit step-by-step reproduction instructions
  • For future bug reports, consider adding explicit step-by-step reproduction instructions, even if the problem is clearly described.
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 9.5/10 (Excellent)
The issue is well-described.

Classification

Category Value
Labels
Quality Improvements
  • For future bug reports, consider explicitly listing environment details (e.g., Qdrant version, Simili bot version) even for internal code fixes, though it's less critical here.
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 9.5/10 (Excellent)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Body truncated at the end
  • Ensure the full content is provided without truncation
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Missing explicit environment details
  • Specify the operating system, Simili bot version, and Qdrant version where this issue was observed or is relevant.
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Truncated 'Changes' table
  • No explicit verification steps
  • Complete the 'Changes' table to show all proposed modifications
  • Add a 'How to Test' section to guide verification of the fix
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Lack of explicit reproduction steps
  • No environment details specified
  • Add an explicit 'Steps to Reproduce' section to guide verification
  • Include relevant environment details (e.g., Simili bot version, Qdrant version, deployment environment) for completeness
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.5/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Missing explicit reproduction steps
  • Add step-by-step instructions to reproduce the bug
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Explicit reproduction steps are not included in this issue
  • Consider adding explicit reproduction steps for self-containment, even if linked to another issue
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Missing explicit reproduction steps
  • Add explicit steps to reproduce the bug, even if simple
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.5/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Missing explicit reproduction steps
  • No environment details (e.g., Simili bot version, Qdrant version)
  • Add explicit step-by-step instructions to reproduce the bug
  • Specify relevant environment details such as the Simili bot version and Qdrant version
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 9.5/10 (Excellent)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • 'Changes' section is truncated
  • No explicit environment details
  • Complete the 'Changes' section to show all proposed modifications
  • Add environment details if specific configurations or platforms are relevant to the fix
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.5/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Missing explicit environment details (e.g., specific versions of Simili bot, Qdrant)
  • Include specific environment details (e.g., 'Tested on Simili bot vX.Y.Z, Qdrant vA.B.C') to enhance completeness, even for a fix description.
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 9.5/10 (Excellent)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • No explicit step-by-step reproduction guide for the original bug
  • No environment details (OS, version, etc.)
  • For future bug reports, consider adding explicit reproduction steps.
  • Specify relevant environment details if the issue is environment-dependent.
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.5/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • No explicit 'Steps to Reproduce' section
  • Missing environment details
  • Add a concise 'Steps to Reproduce' section, even if it summarizes the original bug ([Bug]: Closed Issues and PRs are shown as Open in Simili Comment #59)
  • Include relevant environment details (e.g., OS, specific versions of dependencies) if they could impact the fix or its testing
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.5/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Missing explicit step-by-step reproduction instructions
  • The 'Changes' section is truncated, making the last point incomplete
  • No environment details (OS, version, etc.) are specified
  • Add clear, concise steps to reproduce the bug
  • Ensure all sections, especially 'Changes', are fully detailed and complete
  • Include relevant environment details if they could impact the fix or reproduction
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.8/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Missing explicit reproduction steps for the original bug
  • For future bug reports, include step-by-step instructions to reproduce the original problem
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 8.5/10 (Good)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • No explicit reproduction steps provided (though implied by summary and root cause)
  • Missing environment details (e.g., OS, specific software versions)
  • Include step-by-step instructions to reproduce the bug, even if it's a fix for a known issue (referencing [Bug]: Closed Issues and PRs are shown as Open in Simili Comment #59 is good, but self-contained steps are better)
  • Specify the operating system, relevant software versions (e.g., Qdrant, Go), and any other pertinent environment configurations
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@Kavirubc Kavirubc merged commit 1ff197c into similigh:main Feb 15, 2026
6 checks passed
@github-project-automation github-project-automation Bot moved this from Todo to Done in simili-bot-v1-release Feb 15, 2026
@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 9.0/10 (Excellent)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • Missing explicit environment details
  • Add specific versions of Simili bot, Qdrant, and other relevant components if applicable
Similar Threads
Similarity Thread Status
85% #48 Similar Issue Open
84% #48 feat: CLI PR indexing (#46) & standardized embe... Open

Generated by Simili Bot

@gh-simili-bot
Copy link
Copy Markdown
Contributor

Simili Triage Report

Note

Quality Score: 9.0/10 (Excellent)
The issue could be improved. See suggestions below.

Classification

Category Value
Labels
Quality Improvements
  • No explicit verification steps for the fix
  • Add a 'Verification Steps' section detailing how to confirm the fix works (e.g., 'Close an issue/PR and observe Simili bot comments to ensure the state is correctly displayed as 'Closed').
Similar Threads
Similarity Thread Status
85% #48 Similar Issue
84% #48 feat: CLI PR indexing (#46) & standardized embe...

Generated by Simili Bot

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

Labels

Projects

No open projects

Development

Successfully merging this pull request may close these issues.

[Bug]: Closed Issues and PRs are shown as Open in Simili Comment

3 participants