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

chore: remove unused third_party directory #486

Merged
merged 1 commit into from
May 16, 2019

Conversation

nolanmar511
Copy link
Contributor

@nolanmar511 nolanmar511 commented May 15, 2019

I couldn't find any strong evidence that we used the third_party directory; it should be safe to delete (assuming integration tests pass).

Closes #478

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label May 15, 2019
@kalyanac kalyanac merged commit 50a6f4e into googleapis:master May 16, 2019
aabmass added a commit to aabmass/cloud-profiler-nodejs that referenced this pull request Jul 21, 2023
This caused an issue where the proto definitions in `protos/` are
incompatible with those returned from pprof. The fix I assumed was to
regenerate the protos with `npm run protos`, however this fails because
the third_party directory was removed in googleapis#486.

To make things work, I instead just imported the same proto definitions
from pprof library. I will delete the now unused `protos/` directory for
the next major version release as someone could theoretically have been
importing them from build, just to be safe.
aabmass added a commit to aabmass/cloud-profiler-nodejs that referenced this pull request Jul 24, 2023
This caused an issue where the proto definitions in `protos/` are
incompatible with those returned from pprof. The fix I assumed was to
regenerate the protos with `npm run protos`, however this fails because
the third_party directory was removed in googleapis#486.

To make things work, I instead just imported the same proto definitions
from pprof library. I will delete the now unused `protos/` directory for
the next major version release as someone could theoretically have been
importing them from build, just to be safe.
aabmass added a commit that referenced this pull request Jul 24, 2023
This caused an issue where the proto definitions in `protos/` are
incompatible with those returned from pprof. The fix I assumed was to
regenerate the protos with `npm run protos`, however this fails because
the third_party directory was removed in #486.

To make things work, I instead just imported the same proto definitions
from pprof library. I will delete the now unused `protos/` directory for
the next major version release as someone could theoretically have been
importing them from build, just to be safe.
aabmass added a commit to aabmass/cloud-profiler-nodejs that referenced this pull request Jul 24, 2023
Fixes googleapis#879, take two of googleapis#883 with correct commit message.

This caused an issue where the proto definitions in `protos/` are incompatible with those returned from pprof. The fix I assumed was to regenerate the protos with `npm run protos`, however this fails because the third_party directory was removed in googleapis#486.

To make things work, I instead just imported the same proto definitions from pprof library. I will delete the now unused `protos/` directory for the next major version release as someone could theoretically have been importing them from build, just to be safe.
aabmass added a commit that referenced this pull request Jul 24, 2023
Fixes #879, take two of #883 with correct commit message.

This caused an issue where the proto definitions in `protos/` are incompatible with those returned from pprof. The fix I assumed was to regenerate the protos with `npm run protos`, however this fails because the third_party directory was removed in #486.

To make things work, I instead just imported the same proto definitions from pprof library. I will delete the now unused `protos/` directory for the next major version release as someone could theoretically have been importing them from build, just to be safe.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants