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

illegal hardware instruction (core dumped) on importing gcloud #425

Closed
wingedrhino opened this issue Mar 4, 2015 · 20 comments · Fixed by #488
Closed

illegal hardware instruction (core dumped) on importing gcloud #425

wingedrhino opened this issue Mar 4, 2015 · 20 comments · Fixed by #488
Assignees
Labels
🚨 This issue needs some love. triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Milestone

Comments

@wingedrhino
Copy link

I have a laptop running a Penryn CPU (Intel T4400), Fedora 21 x86_64 and Node.js installed from the official repositories (currently v0.10.33).

The only line of code in my app is:

var gcloud = require('gcloud');

And this happens:

zsh: illegal hardware instruction (core dumped)  node gcloud.js

PS: This is different from #424 because it happens on a different machine. Infact #424 happened after I attempted to run the code on a different machine (i.e, google compute cloud).

@ryanseys
Copy link
Contributor

ryanseys commented Mar 4, 2015

Hmm, strange. Have you seen this error before with other modules? I've heard of this issue happening with strange hardware like Raspberry Pis. Considering I don't have access to your hardware, which looks like the issue here, I'd suggest compiling NodeJS from source if you can, preferably the latest version (0.12.0) and if you cannot do that I'd look into whether https://github.com/Voxer/sse4_crc32 (a library we use in this module) is the culprit here. Perhaps try installing and using that module on its own and seeing if you run into any issues similar to the one you've listed here.

Edit: Another library worth messing with: https://github.com/broofa/node-uuid

@wingedrhino
Copy link
Author

Looks like this happened because of sse4_crc32.

Setup:

npm install sse4_crc32

Script

console.log('Importing sse4_crc32');
var SSE4CRC32 = require("sse4_crc32");
console.log('invoking sse4');
var output = SSE4CRC32.calculate("my string");
console.log('invoked sse4. output below');
console.log(output);
console.log('end');

Output

Importing sse4_crc32
invoking sse4
zsh: illegal hardware instruction (core dumped)  node require-test.js

Similar test with node-uuid created no problems.

I raised an issue sse4_crc32's repository.

@ryanseys
Copy link
Contributor

So sse4_crc32 3.0.0 now has software fallback so maybe we should use it instead of the fast-crc library. Might not eliminate this issue but will help reduce the number of layers between our library and the library at hand.

@ryanseys
Copy link
Contributor

Flawed fallback detection filed here: https://github.com/Voxer/sse4_crc32/issues/24

@anandsuresh
Copy link
Contributor

@ryanseys SSE4_CRC32 release v3.1.0 fixes hardware detection issues. I've tested it on my macbook and our SmartOS boxes and it works just fine. Feel free to upgrade your dependencies and try again.

@ryanseys
Copy link
Contributor

@mahtuag Can you confirm that the latest version in master no longer gives you the illegal hardware instruction (core dumped) issue? Thanks!

@wingedrhino
Copy link
Author

@ryanseys Sorry about the delay. Issue is still reproducible.

@anandsuresh
Copy link
Contributor

@mahtuag I'm guessing you're compiling using GCC since you're running Linux. What version of the compiler are you using?

Also, can you please paste the build log in this thread?

Thanks

@ryanseys
Copy link
Contributor

ryanseys commented May 3, 2015

You can rebuild your dependencies using npm rebuild.

@wingedrhino
Copy link
Author

@anandsuresh @ryanseys rebuilding did not seem to help. Next I re-installed gcloud and it pulled in recent changes. Issue is gone now.

@anandsuresh
Copy link
Contributor

Sweet. Good luck.
On May 4, 2015 5:11 PM, "Gautham Thyagarajan" [email protected]
wrote:

@anandsuresh https://github.com/anandsuresh @ryanseys
https://github.com/ryanseys rebuilding did not seem to help. Next I
re-installed gcloud and it pulled in recent changes. Issue is gone now.


Reply to this email directly or view it on GitHub
#425 (comment)
.

@ofekd
Copy link

ofekd commented May 11, 2015

Happens here as well:

> require('sse4_crc32')
zsh: illegal hardware instruction (core dumped)  node

I am running Arch linux, Node 0.12.2, Intel Core2Quad Q6600, latest gcloud.

Thanks

@jgeewax jgeewax added the type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. label May 11, 2015
@jgeewax jgeewax added this to the Core Stable milestone May 11, 2015
@ryanseys
Copy link
Contributor

That sucks. We should either have software fallback or just log a warning that hash verification is not available. @stephenplusplus thoughts here?

@stephenplusplus
Copy link
Contributor

I thought SSE4_CRC had software fallback detection? @anandsuresh anything you can think of?

@anandsuresh
Copy link
Contributor

That is a wee bit strange. The default behavior is that when h/w support is not available, it falls back to the software table method.

@ofekd: A couple of things:

  • Can you run node -e "console.log(require('sse4_crc32').isHardwareCrcSupported())" to see if it returns true? If so, then there is an issue with the H/w detection function on your platform.
  • Can you paste in a build log so I can try and figure out what seems to be the issue? Specifically, the versions of all the tools in the build-chain (node, npm, node-gyp, python, gcc, etc.)

@anandsuresh
Copy link
Contributor

But before you try any of the steps I listed in the last email, can you ensure that you are running the latest version of gcloud (see 2 comments above your last one) and try again? @mahtuag managed to fix the same problem by re-installing gcloud from scratch.

@ryanseys
Copy link
Contributor

@ofekd Yeah run npm rebuild to rebuild your dependencies and see. :)

@ofekd
Copy link

ofekd commented May 27, 2015

Hey guys, sorry for not answering I was abroad. Still need me to test things out?

@anandsuresh
Copy link
Contributor

Please do @ofekd

@ofekd
Copy link

ofekd commented Jul 1, 2015

Did some tests, still an issue. Re-installed (rm -rf node_modules) to use v0.16, still not working. Also consider my web app is developed inside a docker container, and I still got the error after rebuilding the container.

Ran the command requested:

$ node -e "console.log(require('sse4_crc32').isHardwareCrcSupported())"
zsh: illegal hardware instruction (core dumped)  node -e "console.log(require('sse4_crc32').isHardwareCrcSupported())"

build log:

$ npm install sse4_crc32 --verbose                              
npm info it worked if it ends with ok
npm verb cli [ 'node', '/usr/bin/npm', 'install', 'sse4_crc32', '--verbose' ]
npm info using [email protected]
npm info using [email protected]
npm verb install initial load of /home/ofek/app/package.json
npm verb readDependencies loading dependencies from /home/ofek/app/package.json
npm verb cache add spec sse4_crc32
npm verb addNamed "*" is a valid semver range for sse4_crc32
npm verb addNameRange registry:https://registry.npmjs.org/sse4_crc32 not in flight; fetching
npm verb request uri https://registry.npmjs.org/sse4_crc32
npm verb request no auth needed
npm info attempt registry request try #1 at 2:35:47 PM
npm verb request id 18f1920aca116567
npm verb etag "8FT7R0WJ7E0JOS7TVJ9GN4MUE"
npm http request GET https://registry.npmjs.org/sse4_crc32
npm http 304 https://registry.npmjs.org/sse4_crc32
npm verb etag https://registry.npmjs.org/sse4_crc32 from cache
npm verb get saving sse4_crc32 to /home/ofek/.npm/registry.npmjs.org/sse4_crc32/.cache.json
npm verb addNamed "3.2.0" is a plain semver version for sse4_crc32
npm verb afterAdd /home/ofek/.npm/sse4_crc32/3.2.0/package/package.json not in flight; writing
npm verb afterAdd /home/ofek/.npm/sse4_crc32/3.2.0/package/package.json written
npm info install [email protected] into /home/ofek/app
npm info installOne [email protected]
npm verb installOne of sse4_crc32 to /home/ofek/app not in flight; installing
npm verb lock using /home/ofek/.npm/_locks/sse4-crc32-1649bde0a028f4fb.lock for /home/ofek/app/node_modules/sse4_crc32
npm verb unbuild node_modules/sse4_crc32
npm verb gentlyRm don't care about contents; nuking /home/ofek/app/node_modules/sse4_crc32
npm verb tar unpack /home/ofek/.npm/sse4_crc32/3.2.0/package.tgz
npm verb tar unpacking to /home/ofek/app/node_modules/sse4_crc32
npm verb gentlyRm don't care about contents; nuking /home/ofek/app/node_modules/sse4_crc32
npm verb write writing to /home/ofek/app/node_modules/sse4_crc32/package.json
npm info preinstall [email protected]
npm verb readDependencies loading dependencies from /home/ofek/app/node_modules/sse4_crc32/package.json
npm verb readDependencies loading dependencies from /home/ofek/app/node_modules/sse4_crc32/package.json
npm verb cache add spec nan@^1.7.0
npm verb addNamed ">=1.7.0 <2.0.0" is a valid semver range for nan
npm verb addNameRange registry:https://registry.npmjs.org/nan not in flight; fetching
npm verb cache add spec bindings@~1.2.1
npm verb addNamed ">=1.2.1 <1.3.0" is a valid semver range for bindings
npm verb addNameRange registry:https://registry.npmjs.org/bindings not in flight; fetching
npm verb request uri https://registry.npmjs.org/nan
npm verb request no auth needed
npm info attempt registry request try #1 at 2:35:49 PM
npm verb etag "CWMZR9BQ6YD6KL99MGG0CU5U5"
npm http request GET https://registry.npmjs.org/nan
npm verb request uri https://registry.npmjs.org/bindings
npm verb request no auth needed
npm info attempt registry request try #1 at 2:35:49 PM
npm verb etag "BCS5XYG9ISNJFNKEL5FLOI5HX"
npm http request GET https://registry.npmjs.org/bindings
npm http 304 https://registry.npmjs.org/bindings
npm verb etag https://registry.npmjs.org/bindings from cache
npm verb get saving bindings to /home/ofek/.npm/registry.npmjs.org/bindings/.cache.json
npm verb addNamed "1.2.1" is a plain semver version for bindings
npm verb afterAdd /home/ofek/.npm/bindings/1.2.1/package/package.json not in flight; writing
npm verb afterAdd /home/ofek/.npm/bindings/1.2.1/package/package.json written
npm http 304 https://registry.npmjs.org/nan
npm verb etag https://registry.npmjs.org/nan from cache
npm verb get saving nan to /home/ofek/.npm/registry.npmjs.org/nan/.cache.json
npm verb addNamed "1.8.4" is a plain semver version for nan
npm verb afterAdd /home/ofek/.npm/nan/1.8.4/package/package.json not in flight; writing
npm verb afterAdd /home/ofek/.npm/nan/1.8.4/package/package.json written
npm info install [email protected] into /home/ofek/app/node_modules/sse4_crc32
npm info install [email protected] into /home/ofek/app/node_modules/sse4_crc32
npm info installOne [email protected]
npm verb installOne of bindings to /home/ofek/app/node_modules/sse4_crc32 not in flight; installing
npm info installOne [email protected]
npm verb installOne of nan to /home/ofek/app/node_modules/sse4_crc32 not in flight; installing
npm verb lock using /home/ofek/.npm/_locks/bindings-31cc07a172d1d292.lock for /home/ofek/app/node_modules/sse4_crc32/node_modules/bindings
npm verb lock using /home/ofek/.npm/_locks/nan-ac60946936438812.lock for /home/ofek/app/node_modules/sse4_crc32/node_modules/nan
npm verb unbuild node_modules/sse4_crc32/node_modules/bindings
npm verb unbuild node_modules/sse4_crc32/node_modules/nan
npm verb gentlyRm don't care about contents; nuking /home/ofek/app/node_modules/sse4_crc32/node_modules/bindings
npm verb gentlyRm don't care about contents; nuking /home/ofek/app/node_modules/sse4_crc32/node_modules/nan
npm verb tar unpack /home/ofek/.npm/bindings/1.2.1/package.tgz
npm verb tar unpacking to /home/ofek/app/node_modules/sse4_crc32/node_modules/bindings
npm verb gentlyRm don't care about contents; nuking /home/ofek/app/node_modules/sse4_crc32/node_modules/bindings
npm verb tar unpack /home/ofek/.npm/nan/1.8.4/package.tgz
npm verb tar unpacking to /home/ofek/app/node_modules/sse4_crc32/node_modules/nan
npm verb gentlyRm don't care about contents; nuking /home/ofek/app/node_modules/sse4_crc32/node_modules/nan
npm verb write writing to /home/ofek/app/node_modules/sse4_crc32/node_modules/bindings/package.json
npm info preinstall [email protected]
npm verb readDependencies loading dependencies from /home/ofek/app/node_modules/sse4_crc32/node_modules/bindings/package.json
npm verb readDependencies loading dependencies from /home/ofek/app/node_modules/sse4_crc32/node_modules/bindings/package.json
npm verb about to build /home/ofek/app/node_modules/sse4_crc32/node_modules/bindings
npm info build /home/ofek/app/node_modules/sse4_crc32/node_modules/bindings
npm info linkStuff [email protected]
npm verb linkBins [email protected]
npm verb linkMans [email protected]
npm verb rebuildBundles [email protected]
npm info install [email protected]
npm info postinstall [email protected]
npm verb unlock done using /home/ofek/.npm/_locks/bindings-31cc07a172d1d292.lock for /home/ofek/app/node_modules/sse4_crc32/node_modules/bindings
npm verb write writing to /home/ofek/app/node_modules/sse4_crc32/node_modules/nan/package.json
npm info preinstall [email protected]
npm verb readDependencies loading dependencies from /home/ofek/app/node_modules/sse4_crc32/node_modules/nan/package.json
npm verb readDependencies loading dependencies from /home/ofek/app/node_modules/sse4_crc32/node_modules/nan/package.json
npm verb about to build /home/ofek/app/node_modules/sse4_crc32/node_modules/nan
npm info build /home/ofek/app/node_modules/sse4_crc32/node_modules/nan
npm info linkStuff [email protected]
npm verb linkBins [email protected]
npm verb linkMans [email protected]
npm verb rebuildBundles [email protected]
npm info install [email protected]
npm info postinstall [email protected]
npm verb unlock done using /home/ofek/.npm/_locks/nan-ac60946936438812.lock for /home/ofek/app/node_modules/sse4_crc32/node_modules/nan
npm verb about to build /home/ofek/app/node_modules/sse4_crc32
npm info build /home/ofek/app/node_modules/sse4_crc32
npm info linkStuff [email protected]
npm verb linkBins [email protected]
npm verb linkMans [email protected]
npm verb rebuildBundles [email protected]
npm verb rebuildBundles [ 'bindings', 'nan' ]
npm info install [email protected]

> [email protected] install /home/ofek/app/node_modules/sse4_crc32
> node-gyp rebuild

gyp info it worked if it ends with ok
gyp verb cli [ 'node',
gyp verb cli   '/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli   'rebuild' ]
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2.7" in the PATH
gyp verb `which` succeeded python2.7 /usr/bin/python2.7
gyp verb check python version `python2.7 -c "import platform; print(platform.python_version());"` returned: "2.7.10\n"
gyp verb get node dir no --target version specified, falling back to host node version: v0.12.5
gyp verb command install [ 'v0.12.5' ]
gyp verb install input version string "v0.12.5"
gyp verb install installing version: 0.12.5
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version is already installed, need to check "installVersion"
gyp verb got "installVersion" 9
gyp verb needs "installVersion" 9
gyp verb install version is good
gyp verb get node dir target node version installed: 0.12.5
gyp verb build dir attempting to create "build" dir: /home/ofek/app/node_modules/sse4_crc32/build
gyp verb build dir "build" dir needed to be created? /home/ofek/app/node_modules/sse4_crc32/build
gyp verb build/config.gypi creating config file
gyp verb build/config.gypi writing out config file: /home/ofek/app/node_modules/sse4_crc32/build/config.gypi
gyp verb config.gypi checking for gypi file: /home/ofek/app/node_modules/sse4_crc32/config.gypi
gyp verb common.gypi checking for gypi file: /home/ofek/app/node_modules/sse4_crc32/common.gypi
gyp verb common.gypi found gypi file
gyp verb gyp gyp format was not specified; forcing "make"
gyp info spawn python2.7
gyp info spawn args [ '/usr/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/home/ofek/app/node_modules/sse4_crc32/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/ofek/app/node_modules/sse4_crc32/common.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/usr/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/home/ofek/.node-gyp/0.12.5/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/home/ofek/.node-gyp/0.12.5',
gyp info spawn args   '-Dmodule_root_dir=/home/ofek/app/node_modules/sse4_crc32',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.' ]
gyp verb command build []
gyp verb build type Release
gyp verb architecture x64
gyp verb node dev dir /home/ofek/.node-gyp/0.12.5
gyp verb `which` succeeded for `make` /usr/bin/make
gyp info spawn make
gyp info spawn args [ 'V=1', 'BUILDTYPE=Release', '-C', 'build' ]
make: Entering directory '/home/ofek/app/node_modules/sse4_crc32/build'
  g++ '-DNODE_GYP_MODULE_NAME=sse4_crc32' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DBUILDING_NODE_EXTENSION' '-DNDEBUG' -I/home/ofek/.node-gyp/0.12.5/src -I/home/ofek/.node-gyp/0.12.5/deps/uv/include -I/home/ofek/.node-gyp/0.12.5/deps/v8/include -I../node_modules/nan  -fPIC -pthread -Wall -Wextra -Wno-unused-parameter -m64 -msse4.2 -O3 -ffunction-sections -fdata-sections -fno-tree-vrp -fno-omit-frame-pointer -fno-rtti -fno-exceptions -MMD -MF ./Release/.deps/Release/obj.target/sse4_crc32/src/sse4_crc32.o.d.raw  -c -o Release/obj.target/sse4_crc32/src/sse4_crc32.o ../src/sse4_crc32.cpp
  g++ -shared -pthread -rdynamic -m64  -Wl,-soname=sse4_crc32.node -o Release/obj.target/sse4_crc32.node -Wl,--start-group Release/obj.target/sse4_crc32/src/sse4_crc32.o -Wl,--end-group 
  rm -rf "Release/sse4_crc32.node" && cp -af "Release/obj.target/sse4_crc32.node" "Release/sse4_crc32.node"
make: Leaving directory '/home/ofek/app/node_modules/sse4_crc32/build'
gyp info ok 
npm verb unsafe-perm in lifecycle true
npm info postinstall [email protected]
npm verb unlock done using /home/ofek/.npm/_locks/sse4-crc32-1649bde0a028f4fb.lock for /home/ofek/app/node_modules/sse4_crc32
npm verb validateInstall loading /home/ofek/app/package.json for validation
[email protected] node_modules/sse4_crc32
├── [email protected]
└── [email protected]
npm verb exit [ 0, true ]
npm info ok 

@yoshi-automation yoshi-automation added 🚨 This issue needs some love. triage me I really want to be triaged. labels Apr 6, 2020
sofisl pushed a commit that referenced this issue Sep 16, 2022
Co-authored-by: gcf-owl-bot[bot] <78513119+gcf-owl-bot[bot]@users.noreply.github.com>
Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
sofisl pushed a commit that referenced this issue Oct 5, 2022
Co-authored-by: gcf-owl-bot[bot] <78513119+gcf-owl-bot[bot]@users.noreply.github.com>
Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
sofisl pushed a commit that referenced this issue Oct 5, 2022
Co-authored-by: gcf-owl-bot[bot] <78513119+gcf-owl-bot[bot]@users.noreply.github.com>
Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
sofisl pushed a commit that referenced this issue Oct 8, 2022
Co-authored-by: gcf-owl-bot[bot] <78513119+gcf-owl-bot[bot]@users.noreply.github.com>
Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com>
sofisl pushed a commit that referenced this issue Oct 12, 2022
- [ ] Regenerate this pull request now.

Committer: @summer-ji-eng
PiperOrigin-RevId: 424244721

Source-Link: googleapis/googleapis@4b6b01f

Source-Link: googleapis/googleapis-gen@8ac83fb
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiOGFjODNmYmE2MDZkMDA4YzdlOGE0MmU3ZDU1YjY1OTZlYzRiZTM1ZiJ9
sofisl pushed a commit that referenced this issue Nov 10, 2022
This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [@types/mocha](https://togithub.com/DefinitelyTyped/DefinitelyTyped) | devDependencies | major | [`^7.0.0` -> `^8.0.0`](https://renovatebot.com/diffs/npm/@types%2fmocha/7.0.2/8.0.0) |

---

### Renovate configuration

:date: **Schedule**: "after 9am and before 3pm" (UTC).

:vertical_traffic_light: **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

:recycle: **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

:no_bell: **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [WhiteSource Renovate](https://renovate.whitesourcesoftware.com). View repository job log [here](https://app.renovatebot.com/dashboard#googleapis/nodejs-text-to-speech).
sofisl pushed a commit that referenced this issue Nov 10, 2022
* changes without context

        autosynth cannot find the source of changes triggered by earlier changes in this
        repository, or by version upgrades to tools such as linters.

* chore(nodejs_templates): add script logging to node_library populate-secrets.sh

Co-authored-by: Benjamin E. Coe <[email protected]>

Source-Author: BenWhitehead <[email protected]>
Source-Date: Wed Jun 10 22:24:28 2020 -0400
Source-Repo: googleapis/synthtool
Source-Sha: e7034945fbdc0e79d3c57f6e299e5c90b0f11469
Source-Link: googleapis/synthtool@e703494
sofisl pushed a commit that referenced this issue Nov 11, 2022
Delete `SharePoint` item from TOC.

Source-Author: F. Hinkelmann <[email protected]>
Source-Date: Tue Aug 11 11:25:41 2020 -0400
Source-Repo: googleapis/synthtool
Source-Sha: bd0deaa1113b588d70449535ab9cbf0f2bd0e72f
Source-Link: googleapis/synthtool@bd0deaa

Co-authored-by: gcf-merge-on-green[bot] <60162190+gcf-merge-on-green[bot]@users.noreply.github.com>
sofisl pushed a commit that referenced this issue Nov 11, 2022
This PR was generated using Autosynth. 🌈

Synth log will be available here:
https://source.cloud.google.com/results/invocations/29069528-f186-4ec9-92b5-d225fd8530ec/targets

- [ ] To automatically regenerate this PR, check this box.
sofisl pushed a commit that referenced this issue Nov 11, 2022
…new Uptime check feature. Uptime HTTP(S) checks can now be GET or POST (#425)
sofisl pushed a commit that referenced this issue Nov 11, 2022
sofisl pushed a commit that referenced this issue Nov 11, 2022
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
sofisl pushed a commit that referenced this issue Sep 14, 2023
…ncy versions (#425)

This PR was generated using Autosynth. 🌈

Synth log will be available here:
https://source.cloud.google.com/results/invocations/690c7a47-5578-464e-a3d6-7b377467cdd9/targets

- [ ] To automatically regenerate this PR, check this box.

Source-Link: googleapis/synthtool@fdd03c1
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚨 This issue needs some love. triage me I really want to be triaged. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants