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.

Sign up for GitHub

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

Jump to bottom

Double check that the installation on OS X works as expected...? #660

Closed
jgeewax opened this issue Jun 16, 2015 · 3 comments
Closed

Double check that the installation on OS X works as expected...? #660

jgeewax opened this issue Jun 16, 2015 · 3 comments
Assignees
@stephenplusplus

Comments

@jgeewax
Copy link
Contributor

jgeewax commented Jun 16, 2015

I got some feedback that installing on OS X with Node 0.12.x was not as smooth as it should be.

Excluding the typical npm ownership issues (root vs $USER) it seems that sse4_crc32 has some problems and our docs don't really say much about it. Can we do a dry run through all of this and see what's needed to make npm install gcloud an un-eventful process?

The complaints focused around sse4_crc32 and node-gyp, particularly something about --no-parallel being an invalid flag?
@stephenplusplus
Copy link
Contributor

// @anandsuresh

@anandsuresh
Copy link
Contributor

@jgeewax @stephenplusplus I just built the latest master branch of the SSE4_CRC32 library on my macbook and it worked fine. Also did an sudo npm install gcloud without any errors (had to run it as sudo due to the npm ownership issues).

Any chance of getting some logs of the problematic installation?

With regards to the --no-parallel flag, please check out nodejs/node-gyp#426 or Unitech/pm2#434.

@stephenplusplus
Copy link
Contributor

I use gcloud with OS X every day, and have only run into errors when going between v0.10 of Node and v0.12. Doing that without re-installing the dependencies will cause errors.

If more issues pop up around sse4_crc32, I think we should direct users over to their repo for support. There's not much we can do here, aside from discontinue using it, which I don't think we want to do. @anandsuresh has been great with support, so the few times these issues come in, they'll likely be resolved rather quickly.

Feel free to re-open if this is not a satisfying answer.

@sofisl sofisl mentioned this issue Sep 27, 2022
Closed
4 tasks
sofisl pushed a commit that referenced this issue Sep 27, 2022
@gcf-owl-bot
test(nodejs): remove 15 add 16 (#1322) (#660)
d9d4202 
Source-Link: googleapis/synthtool@6981da4
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-nodejs:latest@sha256:3563b6b264989c4f5aa31a3682e4df36c95756cfef275d3201508947cbfc511e

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
@sofisl sofisl mentioned this issue Oct 11, 2022
Merged
4 tasks
sofisl pushed a commit that referenced this issue Oct 11, 2022
@gcf-owl-bot @bcoe
build(node): update client library version in samples metadata (#1356) (
d4a95aa 
#660)

* build(node): add feat in node post-processor to add client library version number in snippet metadata

Co-authored-by: Benjamin E. Coe <[email protected]>
Source-Link: googleapis/synthtool@d337b88
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-nodejs:latest@sha256:d106724ad2a96daa1b8d88de101ba50bdb30b8df62ffa0aa2b451d93b4556641
sofisl pushed a commit that referenced this issue Oct 13, 2022
@gcf-owl-bot @bcoe @sofisl
build(node): update client library version in samples metadata (#1356) (
6784f75 
#660)

* build(node): add feat in node post-processor to add client library version number in snippet metadata

Co-authored-by: Benjamin E. Coe <[email protected]>
Source-Link: googleapis/synthtool@d337b88
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-nodejs:latest@sha256:d106724ad2a96daa1b8d88de101ba50bdb30b8df62ffa0aa2b451d93b4556641
sofisl pushed a commit that referenced this issue Nov 9, 2022
@gcf-owl-bot
test(nodejs): remove 15 add 16 (#1322) (#660)
fdf9c9f 
Source-Link: googleapis/synthtool@6981da4
Post-Processor: gcr.io/cloud-devrel-public-resources/owlbot-nodejs:latest@sha256:3563b6b264989c4f5aa31a3682e4df36c95756cfef275d3201508947cbfc511e

Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
This was referenced Nov 9, 2022
Closed
Merged
Merged
sofisl pushed a commit that referenced this issue Nov 10, 2022
@gcf-owl-bot
chore: new owl bot post processor docker image (#660)
7201827 
gcr.io/repo-automation-bots/owlbot-nodejs:latest@sha256:f93bb861d6f12574437bb9aee426b71eafd63b419669ff0ed029f4b7e7162e3f
@sofisl sofisl mentioned this issue Nov 11, 2022
Merged
4 tasks
sofisl pushed a commit that referenced this issue Nov 11, 2022
@yoshi-automation
feat: added support for custom content types docs: clarified wording …
586ec03 
…around quota usage (#660)

* feat: added support for custom content types docs: clarified wording around quota usage

PiperOrigin-RevId: 323397413

Source-Author: Google APIs <[email protected]>
Source-Date: Mon Jul 27 11:04:11 2020 -0700
Source-Repo: googleapis/googleapis
Source-Sha: ca22cfe3477f1c0095fba606d5a18c52d918a0dd
Source-Link: googleapis/googleapis@ca22cfe

* feat: added support for custom content types docs: clarified wording around quota usage

PiperOrigin-RevId: 323436667

Source-Author: Google APIs <[email protected]>
Source-Date: Mon Jul 27 14:05:51 2020 -0700
Source-Repo: googleapis/googleapis
Source-Sha: 546f389d95dbbc88d9d5a00fae25b29d49a0d5b6
Source-Link: googleapis/googleapis@546f389
sofisl pushed a commit that referenced this issue Nov 17, 2022
@gcf-owl-bot
docs(node): support "stable"/"preview" release level (#1312) (#660)
aa83ad8
@sofisl sofisl mentioned this issue Nov 17, 2022
Merged
4 tasks
@sofisl sofisl mentioned this issue Jan 10, 2023
Merged
4 tasks
sofisl pushed a commit that referenced this issue Jan 10, 2023
@fhinkel
chore(cloud-rad): delete api-extractor config (#660)
5ee149d
sofisl pushed a commit that referenced this issue Jan 24, 2023
@JustinBeckwith
docs: modernize patterns in subset of samples (#660)
fca7d22
sofisl pushed a commit that referenced this issue Jan 25, 2023
@JustinBeckwith
docs: modernize patterns in subset of samples (#660)
42637ed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@stephenplusplus stephenplusplus

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jgeewax @stephenplusplus @anandsuresh