Bump actions/download-artifact from 4 to 8 - #8
Merged
dvcdsys merged 1 commit intoMar 25, 2026
Conversation
Bumps [actions/download-artifact](https://github.com/actions/download-artifact) from 4 to 8. - [Release notes](https://github.com/actions/download-artifact/releases) - [Commits](actions/download-artifact@v4...v8) --- updated-dependencies: - dependency-name: actions/download-artifact dependency-version: '8' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
dvcdsys
deleted the
dependabot/github_actions/actions/download-artifact-8
branch
March 25, 2026 16:36
dvcdsys
added a commit
that referenced
this pull request
May 14, 2026
After the workspace_repos → git_repos + workspace_projects split,
docs and stale comments still referenced concepts that no longer
exist.
- workspaces.md + doc/WORKSPACES.md: rewrite lifecycle, REST API
reference, webhook URL examples, and clone-dir paths to use
projects.path_hash, /git-repos, /workspaces/{id}/projects, and
/projects/{hash}/reindex.
- Both skills/cix-workspace/SKILL.md and
plugins/cix/skills/cix-workspace/SKILL.md: replace
/workspaces/{id}/repos/{repo_id}/reindex with
/projects/{hash}/reindex. New plugins/cix/scripts/sync-skills.sh
keeps the duplicate copies byte-identical going forward.
- Code comments updated across config.go, callgraph.go,
repocloner.go, githubapi.go, workspaces.go, and
AddExistingProjectDialog.tsx to point at gitrepos /
workspace_projects / projects.path_hash instead of the dead
workspacerepos.* names.
Resolves Fix #8, #9, #10, #19.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
dvcdsys
added a commit
that referenced
this pull request
May 14, 2026
After the workspace_repos → git_repos + workspace_projects split,
docs and stale comments still referenced concepts that no longer
exist.
- workspaces.md + doc/WORKSPACES.md: rewrite lifecycle, REST API
reference, webhook URL examples, and clone-dir paths to use
projects.path_hash, /git-repos, /workspaces/{id}/projects, and
/projects/{hash}/reindex.
- Both skills/cix-workspace/SKILL.md and
plugins/cix/skills/cix-workspace/SKILL.md: replace
/workspaces/{id}/repos/{repo_id}/reindex with
/projects/{hash}/reindex. New plugins/cix/scripts/sync-skills.sh
keeps the duplicate copies byte-identical going forward.
- Code comments updated across config.go, callgraph.go,
repocloner.go, githubapi.go, workspaces.go, and
AddExistingProjectDialog.tsx to point at gitrepos /
workspace_projects / projects.path_hash instead of the dead
workspacerepos.* names.
Resolves Fix #8, #9, #10, #19.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
6 tasks
dvcdsys
added a commit
that referenced
this pull request
May 20, 2026
…s behind NAT Adds a built-in, dashboard-managed outbound tunnel so a NAT'd server gets a public URL for GitHub webhook delivery — no inbound ports, no env feature flag. Backend (internal/tunnels): - Provider abstraction + Manager with runtime Apply (start/stop/reconfigure), mirroring the llama-server sidecar supervisor (exec, exit-watcher, bounded crash-restart, graceful SIGTERM->SIGKILL). - Cloudflare provider (named/quick) and ngrok provider (reserved/ephemeral; authtoken always required; URL parsed from the agent JSON log). - Webhook reconciler: re-points webhook_mode=auto repos at the live tunnel URL on boot and on URL change; new githubapi.UpdateWebhook (PATCH). - buildWebhookURL prefers the live tunnel URL over CIX_PUBLIC_URL. Config in DB, managed from the dashboard (no env flag): - tunnel_config single-row table (migration #8); token encrypted via secrets. - tunnelcfg service + GET/PUT /api/v1/tunnels/config (admin); provider-aware validation. Only deployment infra stays in env (binary paths, metrics addr). Binary management: - GET /api/v1/tunnels/binaries reports installed/path/version/managed. - When missing locally, the dashboard shows manual install instructions (brew/linux) noting Docker bundles them automatically. - CIX_TUNNEL_BIN_MANAGED (true in the Docker images) enables Install/Update: the server downloads agents (raw or .tgz, no shell) into a writable /data/tunnel-bin via POST /api/v1/tunnels/binaries/{provider}/{install,update}. Dashboard: - New admin-only "Managed Tunnels" section (provider select, mode, hostname, token, status, Test/Restart, binary install/update). - "GitHub Tokens" -> "GitHub Integration" with Tokens + Webhook Integrations tabs. Docker: both images bundle cloudflared + ngrok and enable managed updates. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
dvcdsys
added a commit
that referenced
this pull request
Jun 2, 2026
…ixes #8 class) The flat single-slug scheme `chroma_<StorageSlug(id)>` flattened provider+model into one string with `_` as the field separator — but `_` is also what model-name normalization emits. That in-band separator made the legacy-migration heuristic (`hasKnownPrefix`) ambiguous: a legacy ollama model whose name normalized to `ollama_…`/`openai_…`/`voyage_…` (e.g. `openai-community/x`) was misread as already-unified, skipped, and its vectors silently orphaned behind a fresh empty namespace. Worse, `ollama:foo` and a model literally named `ollama-foo` both produced the exact same string — unfixable by any name parsing. Make the separator structural instead: namespace the vector store as a nested directory tree, one path segment per identity field: <ChromaPersistDir>/<kind>/<model-slug>[/<variant>] chroma/ollama/nomic_embed_text chroma/voyage/voyage_code_3/2048_int8 chroma/openai/text_embedding_3_large/256 The provider kind is now its own directory level, derived from the kind (not glued onto the model slug), so it can never collide with a model name. `ollama:foo` → ollama/foo, `ollama:ollama-foo` → ollama/ollama_foo — distinct. The #8 case resolves correctly: openai-community/x → ollama/openai_community_x. Changes - provider.Provider gains StorageComponents() []string — each provider builds its path from its OWN structured fields (never by re-parsing the flattened ID), so the in-band-separator problem can't recur. - config: ChromaDirForSlug(slug) → ChromaDirFor(components) (filepath.Join under the container). - Service: StorageSlug() → StoragePath() []string; reopen + AttachVectorStore thread components. - storage: PrefixLegacyChromaDirs (+ hasKnownPrefix prefix-guessing) → MigrateFlatChromaToNested. Now unambiguous: every flat `chroma_*` sibling is a legacy ollama dir (the old build was ollama-only) and moves to chroma/ollama/<StorageSlug(suffix)>/. StorageSlug(ModelSafeName(m)) == StorageSlug(m), so it lands where the server resolves the identity — even for kind-looking model names. Existing main/prod ollama vectors migrate without a reindex. main.go relocates a legacy Python store at the container path first, then migrates (fail-closed). - Drop vectorstore.WarnIfNamespaceOrphaned — the orphan ambiguity it warned about is gone, so the diagnostic is no longer needed. - Drop the throwaway intermediate flat-unified scheme entirely (dev-branch only; no back-compat). Tests: per-provider StorageComponents incl. the ollama foo vs ollama-foo anti-collision; migration moves flat→nested incl. the kind-looking-name (#8) regression, special-char normalization, idempotency, no-clobber, python-backup skip; switch/reopen tests assert nested paths. Full suite, `go vet` (incl. embed_gate), and `-race` all green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Bumps actions/download-artifact from 4 to 8.
Release notes
Sourced from actions/download-artifact's releases.
... (truncated)
Commits
3e5f45bAdd regression tests for CJK characters (#471)e6d03f6Add a regression test for artifact name + content-type mismatches (#472)70fc10cMerge pull request #461 from actions/danwkennedy/digest-mismatch-behaviorf258da9Add change docsccc058eFix linting issuesbd7976bAdd a setting to specify what to do on hash mismatch and default it toerrorac21fcfMerge pull request #460 from actions/danwkennedy/download-no-unzip15999bfAdd note about package bumps974686eBump the version tov8and add release notesfbe48b1Update test names to make it clearer what they doDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)