-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Skip test for sending telemetry events #12568
base: main
Are you sure you want to change the base?
Conversation
Update `main` with latest from public CLI repo
…ming-user-that-telemetry-is-enabled-on [cli] Inform user of telemetry tracking and opt them in
…d-events-to-public-telemetry-bridge-from-cli-2 Send events to the telemetry bridge
Update main oct 25
…ry-url Update telemetry endpoint
merge from upstream
Co-authored-by: Austin Merrick <[email protected]>
…oesnt-block-the-cli' of github.com:vercel/vercel-cli-private into jeffsee/zero-2730-send-telemetry-in-a-subprocess-that-doesnt-block-the-cli
…in-a-subprocess-that-doesnt-block-the-cli Send telemetry in a subprocess that doesn't block the CLI from exiting
Private main
…d-off-version [cli] update text to be consistent with agreed version
Erikarowland/merge main
…12566) The way we were previously sending the telemetry event wasn't compatible with our ability to invoke the CLI from `ts-node` because finding the `send-telemetry` module wasn't in the expected path. Instead, the `sendToSubprocess` function invokes the CLI with the `telemetry flush` command, providing the events as a stringified JSON argument.
|
No description provided.