-
Notifications
You must be signed in to change notification settings - Fork 459
feat: Adding client-proxy and clickhouse to e2b-artifacts #3210
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,5 @@ | ||
| { | ||
| "packages/docker-reverse-proxy": "0.2.2" | ||
| "packages/docker-reverse-proxy": "0.2.2", | ||
| "packages/client-proxy": "0.0.0", | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🟡 The client-proxy's telemetry version won't match the release tag. Extended reasoning...The mismatch
const (
serviceName = "client-proxy"
// ...
version = "1.2.0"
)and tel, err := telemetry.New(ctx, nodeID, serviceName, commitSHA, version, instanceID)This PR seeds Why the existing plumbing doesn't fix it
Contrast with the sibling pattern this PR copiesThe
The client-proxy publish job omits that last piece and the underlying plumbing was never added. Step-by-step proof
Impact and fixTelemetry data-quality only — nothing crashes and the proxy works correctly. Two fixes, either works:
(clickhouse-migrator has no comparable in-binary version constant so it isn't affected.) |
||
| "packages/clickhouse": "0.0.0" | ||
| } | ||
Uh oh!
There was an error while loading. Please reload this page.