grayside
Repos
80
Followers
29
Following
20

Samples for Cloud Run

133
68

Outrigger command line tool

12
7

:diamond_shape_with_a_dot_inside:Emblem Giving is a sample application that demonstrates a serverless architecture with continuous delivery, and trouble recovery.

99
28

Events

restore commented mocha config

Created at 5 days ago
issue comment
🐞 Can't connect to docker daemon when using nerdctl

Not sure if a new issue is called for, but I've gone through this and linked resource pretty thoroughly and I don't see workable guidance for using dagger + nerdctl.

Created at 6 days ago

Sample: List available voices [tts_list_voices]

Samples: Synthesize Speech (text, ssml, string, local file)

Samples: extract speech synthesis samples

s/var/const/g

Samples: add quickstart

Samples: change printed output after writing mp3 files

Samples: update with prettier

$ npm run generate-scaffolding

Samples: fix lint error for unused closure arg var

Samples: use simple SSML examples, eg. Hello there.

Update links and whatnot

making lint and samples work in circle

samples package.json

Merge branch 'samples' of github.com:googleapis/nodejs-text-to-speech into samples

Update synthesize.js sample CLI help to show existing TXT and SSML resource files

Merge branch 'samples' of github.com:googleapis/nodejs-text-to-speech into samples

s/SSML Gender/SSML Voice Gender/g

Samples: update writing bytes to mp3 files to be async

Update quickstart to write mp3 file asynchronously

Samples: Use async I/O when writing MP3 files

Created at 1 week ago
testing: skip unrelated Cloud Run testing on PR checks

I've added comments, some additional logging on positive test matching, and added a check to run the tests if Cloud Run Kokoro config is updated.

Created at 1 week ago

testing: run tests on Cloud Run kokoro config update

Created at 1 week ago

Revert "chore(deps): update python docker tag to v3.11"

This reverts commit ee092e112bc56c970c5b52a5364c386d7f007c29.

This change breaks debugging in Cloud Code with the following error:

      > [cloud-run-python-hello-world-7d675c67f5-hjhf9 cloud-run-python-hello-world-container] time="2022-11-18T22:18:45Z" level=warning msg="Debugging support for Python 3.11 not found: may require manually installing \"debugpy\""
      > [cloud-run-python-hello-world-7d675c67f5-hjhf9 cloud-run-python-hello-world-container] /usr/local/bin/python: No module named debugpy
      > [cloud-run-python-hello-world-7d675c67f5-hjhf9 cloud-run-python-hello-world-container] time="2022-11-18T22:18:45Z" level=fatal msg="error launching python debugging: exit status 1"
 - deployment/cloud-run-python-hello-world failed. Error: container cloud-run-python-hello-world-container terminated with exit code 1.

Merge pull request #1174 from sushicw/undo-python311

Created at 1 week ago
Revert "chore(deps): update python docker tag to v3.11"

This reverts commit ee092e112bc56c970c5b52a5364c386d7f007c29.

The upgrade to 3.11 breaks debugging in Cloud Code with the following error:

      > [cloud-run-python-hello-world-7d675c67f5-hjhf9 cloud-run-python-hello-world-container] time="2022-11-18T22:18:45Z" level=warning msg="Debugging support for Python 3.11 not found: may require manually installing \"debugpy\""
      > [cloud-run-python-hello-world-7d675c67f5-hjhf9 cloud-run-python-hello-world-container] /usr/local/bin/python: No module named debugpy
      > [cloud-run-python-hello-world-7d675c67f5-hjhf9 cloud-run-python-hello-world-container] time="2022-11-18T22:18:45Z" level=fatal msg="error launching python debugging: exit status 1"
 - deployment/cloud-run-python-hello-world failed. Error: container cloud-run-python-hello-world-container terminated with exit code 1.
Created at 1 week ago
Revert "chore(deps): update python docker tag to v3.11"

/gcbrun

Created at 1 week ago
docs: add guidance on contributor workflows

This PR codifies some of the change criteria from internal discussions into the repository CONTRIBUTING.

Created at 1 week ago
grayside create branch contribution-flows
Created at 1 week ago
Release Management & Versioning

We would like to publish release notes and maintain versioning for the samples guide to ensure we have a clear mechanism for communicating updates.

  • Release notes should recognize all kinds of contributions, but we are only interested in versioning the samples guide content
  • Release notes should leverage DPE release tooling & conventions where possible
  • Release notes should separate content changes (of general interest) from site infrastructure changes (mainly interesting for contributors)

Proposal

  • Use https://github.com/google-github-actions/release-please-action to automate release creation and version updates
  • Use GitHub's automatically generated release notes (separate content & site changes)
    • Categories like Breaking, Guide Updates, Infrastructure Changes, Other Work
  • Use https://github.com/bcoe/conventional-release-labels to apply conventional commit directives in PR titles as PR labels
  • Use https://github.com/actions/labeler to automatically apply content, site, and automation labels:
    • .github/** => automation
    • content/** => content
    • layouts/**, package*, config.toml => site

This would address some of the label consideration in #37

Created at 1 week ago
Proposal: Define common line length to avoid horizontal scrolls

Related: #89

Created at 1 week ago
Proposal: Guidance on link within samples

I appreciate the value and challenge being raised here, we need a more specific proposal to evaluate.

Created at 1 week ago
Proposal: make Go snippets runnable

That seems at odds with or be able to paste it more easily into a main func.

Created at 1 week ago

expand insignificant pattern matching

Created at 1 week ago