Skip to content
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

revert: "feat: Put back telemetry" #1001

Merged
merged 1 commit into from
Sep 5, 2023
Merged

revert: "feat: Put back telemetry" #1001

merged 1 commit into from
Sep 5, 2023

Conversation

loderunner
Copy link
Contributor

This reverts commit 4be7e3a.

Checklist

=========

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have checked for similar issues and haven't found anything relevant.
  • This is not a security issue (which should be reported here: https://circleci.com/security/)
  • I have read Contribution Guidelines.

Internal Checklist

  • I am requesting a review from my own team as well as the owning team
  • I have a plan in place for the monitoring of the changes that I am making (this can include new monitors, logs to be aware of, etc...)

Changes

=======

  • Put itemized changes here, preferably in imperative mood, i.e. "Add
    functionA to fileB"

Rationale

=========

What was the overarching product goal of this PR as well as any pertinent
history of changes

Considerations

==============

Why you made some of the technical decisions that you made, especially if the
reasoning is not immediately obvious

Screenshots

============

Before

Image or [gif](https://giphy.com/apps/giphycapture)

After

Image or gif where change can be clearly seen

Here are some helpful tips you can follow when submitting a pull request:

  1. Fork the repository and create your branch from main.
  2. Run make build in the repository root.
  3. If you've fixed a bug or added code that should be tested, add tests!
  4. Ensure the test suite passes (make test).
  5. The --debug flag is often helpful for debugging HTTP client requests and responses.
  6. Format your code with gofmt.
  7. Make sure your code lints (make lint). Note: This requires Docker to run inside a local job.

@loderunner loderunner requested review from a team as code owners September 5, 2023 17:45
@loderunner loderunner self-assigned this Sep 5, 2023
@loderunner loderunner merged commit a516872 into develop Sep 5, 2023
@loderunner loderunner deleted the revert-telemetry branch September 5, 2023 17:58
JulesFaucherre added a commit that referenced this pull request Sep 6, 2023
JulesFaucherre added a commit that referenced this pull request Sep 7, 2023
* Revert "revert: "feat: Put back telemetry" (#1001)"

This reverts commit a516872.

* fix: Fix runner token telemetry event

* fix: Allow runner commands to run their PersistentPreRun

With cobra, when you define a PersistentPreRun in a child command, you
overwrite all the command's parents PersistentPreRun. When introducing
telemetry, we used the PersistentPreRun to send the events, this made
the runner commands not call the PersistentPreRun in
cmd/runner/runner.go which defines the 'opts.r' value. In the commands
the 'opts.r' was nil, thus causing nil pointer deference panic.

This commit uses the PreRunE to send the telemetry event instead of the
PersistentPreRun to avoid this issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants