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

docs: update go version in CONTRIBUTING. #23310

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jstirnaman
Copy link
Contributor

  • update the Go requirement to 1.18 in CONTRIBUTING.md
  • remove mention of GPG key since it's no longer at the referenced URL and @pierwill verified it's not currently necessary.
  • revisions and cleanup.

Describe your proposed changes here.

  • [ x] Well-formatted commit messages
  • [ x] Rebased/mergeable
  • [ x] Documentation updated or issue created (provide link to issue/pr)
  • [ x] Signed CLA (if not already signed)

- update the Go requirement to 1.18 in CONTRIBUTING.md
- remove mention of GPG key since it's no longer at the referenced URL and @pierwill verified it's not currently necessary.
- revisions and cleanup.

At InfluxData we find `gvm`, a Go version manager, useful for installing Go.
For instructions on how to install it see [the gvm page on github](https://github.com/moovweb/gvm).
With `gvm` installed, run the following commands to install the required go version and set it as the default.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
With `gvm` installed, run the following commands to install the required go version and set it as the default.
With `gvm` installed, run the following commands to install the required Go version and set it as the default.

@@ -13,4 +13,4 @@ These versions of InfluxDB are currently being supported with security updates.

## Reporting a Vulnerability
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
## Reporting a Vulnerability
## Report a vulnerability


$ ./influxd -cpuprofile influxdcpu.prof -memprof influxdmem.prof

# run queries, writes, whatever you're testing
# Run queries, writes, or whatever you're testing.
# Quit out of influxd and influxd.prof will then be written.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
# Quit out of influxd and influxd.prof will then be written.
# Quit influxd to write to influxd.prof.

# Quit out of influxd and influxd.prof will then be written.
# open up pprof to examine the profiling data.
# Run pprof to examine the profiling data.
Copy link
Contributor

Choose a reason for hiding this comment

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

does pprof show what's in influxd.prof?


- Ensure Go can find the protobuf library on your system--check that `LD_LIBRARY_PATH` includes the directory where the `libprotoc.so` library is installed.
- Ensure the `protoc-gen-go` executable in `GOPATH/bin` is on your system path by adding `GOPATH/bin` to `PATH`.

## Generated Go Templates
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
## Generated Go Templates
## Generated Go templates


There will usually be some back and forth as we finalize the change, but once that completes it may be merged.
- Be clear about your requirements and goals.
- Provide examples of the enhancement that you would like to see and tell us why it's important to you.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- Provide examples of the enhancement that you would like to see and tell us why it's important to you.
- Examples of the enhancement that you would like to see, and why it's important to you.

There will usually be some back and forth as we finalize the change, but once that completes it may be merged.
- Be clear about your requirements and goals.
- Provide examples of the enhancement that you would like to see and tell us why it's important to you.
- If you find your feature request already exists as a Github issue, please add a "thumbs up" reaction to indicate your support for that feature.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- If you find your feature request already exists as a Github issue, please add a "thumbs up" reaction to indicate your support for that feature.
{{% note %}}
If you find your feature request already exists as a Github issue, please add a "thumbs up" reaction to indicate your support for that feature.
{{% /note %}}

To submit a pull request, follow these steps:

1. Fork the `influxdata/influxdb` repository.
2. Checkout a feature branch in your fork.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
2. Checkout a feature branch in your fork.
2. Check out a feature branch in your fork (`git checkout <branch name>`).


To submit a pull request, follow these steps:

1. Fork the `influxdata/influxdb` repository.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
1. Fork the `influxdata/influxdb` repository.
1. [Fork the `influxdata/influxdb` repository](https://docs.github.com/en/get-started/quickstart/fork-a-repo) .


1. Fork the `influxdata/influxdb` repository.
2. Checkout a feature branch in your fork.
3. In your feature branch, make your change and run the test suite (given you won't be able to merge if tests fail).
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
3. In your feature branch, make your change and run the test suite (given you won't be able to merge if tests fail).
3. In your feature branch, make your change and run the test suite (you won't be able to merge if tests fail).

@lesam lesam requested review from serenibyss and removed request for lesam April 28, 2022 17:47
Copy link
Contributor

@serenibyss serenibyss left a comment

Choose a reason for hiding this comment

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

LGTM!

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

Successfully merging this pull request may close these issues.

None yet

3 participants