Is your feature request related to a problem? Please describe.
Cloud-trace team is taking over cloud-trace-nodejs agent, and trying to create a new team for us.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

It's easy to omit a comma or add a extra trailing comma in the json. We should be able to catch these before break at runtime.

Adding this label to a PR should force kokoro to rerun the build

In teams.json, there is an explicit repos field which allows a team to indicate repositories that they are tracking work on.

The repository GoogleCloudPlatform/cloud-sql-go-connector has been added to this field, however this repository is not be appropriately tracked by SLOs.

Failing jobs:

• sloth-sheet-sync
• sloth-bigquery-sync

We need to update teams.json and repos.json to reflect the new structure of the code-build-run team. We'll break out 3 new teams:

• serverless: for cloud run, app engine, and other related products
• operations: for cloud operations, observability, etc
• devplat: for developer tools, anthos and gke

The container api and related microservices repos should be broken out of the devplat grouping

After setting SLOTH_GITHUB_TOKEN, running sloth produces this:

$ sloth
/usr/local/lib/node_modules/@justinbeckwith/sloth/build/src/issue.js:23
    throw new Error('Please access the `Yoshi Drift Key` secret in go/valentine, and set the `DRIFT_API_KEY` env var.');
    ^

Error: Please access the `Yoshi Drift Key` secret in go/valentine, and set the `DRIFT_API_KEY` env var.
    at Object.<anonymous> (/usr/local/lib/node_modules/@justinbeckwith/sloth/build/src/issue.js:23:11)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/@justinbeckwith/sloth/build/src/slo.js:16:17)
    at Module._compile (module.js:652:30)

What is this for? If someone wanted to use sloth to monitor a different set of repos, could this be omitted?

Adding tracking issue for the work to add new repos and apis to the code-build-run team.

The release PR #597 is still in a pending state after several hours

Example: https://github.com/googleapis/sloth/runs/3336077502?check_suite_focus=true

Currently:
sloth --csv

Repo,Total,P0,P1,P2,Untriaged,Out of SLO
google/google-api-dotnet-client,7,0,1,3,0,3
google/google-api-go-client,14,0,3,5,1,6

Desired:
sloth --csv

Repo,Lang,Total,P0,P1,P2,Untriaged,Out of SLO
google/google-api-dotnet-client,dotnet,7,0,1,3,0,3
google/google-api-go-client,go,14,0,3,5,1,6

In particular, I'd like to assign issues to @andrewsg in https://github.com/googleapis/google-cloud-python

Issue for the C++ Bigtable client is attributed to Storage and Databases team instead of the C++ team.

All issues in google-cloud-cpp should be attributed to the C++ team by default.

Using a json file to manage our team membership was a great idea when we really cared about managing membership across 3 GitHub organizations. These days, most of our work is done in the googleapis organization. I'm creating this issue to track the removal of users.json so teams can be directly managed. A few details:

• sync-repo-settings bot will still automatically assign the yoshi-<language> and yoshi-<language>-admins teams by convention to all appropriate language focused repos.
• The yoshi-<language> and yoshi-<language>-admins teams will be moved out from the top level yoshi group, and will instead live on the top level
• The users who currently live in the yoshi-<language>-admins group will have the maintainer bit on the yoshi-<language> teams

Hello! Autosynth couldn't regenerate sloth. 💔

Here's the output from running synth.py:

Cloning into 'working_repo'...
Switched to branch 'autosynth'
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 256, in <module>
    main()
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 196, in main
    last_synth_commit_hash = get_last_metadata_commit(args.metadata_path)
  File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 149, in get_last_metadata_commit
    text=True,
  File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 403, in run
    with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'text'

Google internal developers can see the full log here.

The following code:

are completely wipe the spreadsheet and there is a moment of nothing.

It should delete only unnecessary data after batchUpdate.

🤖 Here's what the next release of @justinbeckwith/sloth would look like.

4.0.1 (2019-05-17)

Bug Fixes

• remove suprious log (#230) (cf361b0)
• use the drift prod enpoint (#229) (e20e160)
• deps: update dependency update-notifier to v3 (#227) (34fb1a6)

release created at #232

The release PR #807 is still in a pending state after several hours

This commit here fixed one bug, and introduced another:
02b4a3b

For language focused teams like C++, this makes sense. We want the team to own the issue, and not the API owner.

The problem is the docs-samples repos :) In those cases, we want the API to be evaluated first, and then the repository.

Without thinking on it some more, I can't think of a way to satisfy both of these conditions without some real changes. For now - I would like to roll this change back and come up with a less disruptive plan.

The following samples repositories maintained by the Anthos/GKE DPEs are missing from the sloth sync process:

• Anthos Config Management Samples
• Anthos Service Mesh Samples
• Kubernetes Engine Samples

The release PR #651 is still in a pending state after several hours

So I don't have to keep buggin @JustinBeckwith

@tequilarista to action when appropriate resources are in place

• Rollback #845
• Add Workflows API

As of today sloth runs on my personal k8s cluster, using a personal access token provisioned from my account. This is bad for so many reasons that I don't even have to list them 😆

I would like to make the running of sloth tag-issues an automated task that uses the yoshi-automation account. To set this up, we need:

• An environment where nodejs 10 is installed (the node:10-alpine docker image is great)
• The SLOTH_GITHUB_TOKEN environment variable must be set to a valid GitHub token
• Run the command npx https://github.com/googleapis/sloth tag-issues
• Do that every 3 minutes :)

Please do let me know if you have any concerns or questions!

Proposal

Reduce number of duplicate entries of individuals across teams to make managing permissions more straightforward

• Reduce Yoshi direct membership to a minimum number of people. Rely on sub teams to manage this
• All repositories contain the yoshi team, so having all people in each language team is redundant
• Create yoshi-contractors to migrate contractor team members off of parent yoshi team.
• Remove contractors from individual language teams. The rights given via yoshi are sufficient.
• Give Yoshi team write access to all repositories (some currently have read)
• Enable master branch protection on all repositories
• Create CODEOWNERS files for all repositories

Desired:
sloth --apis --csv

API,Total,P0,P1,P2,Untriaged,Out of SLO
spanner,7,0,1,3,0,3
pubsub,14,0,3,5,1,6

@JustinBeckwith can you cut a new release with the csv-string changes from #69? Thanks!

From the Usage section: "You need to go create a personal access token in GitHub".

Which scopes are needed for this?

Failed attempt by renovate:
#1006

The release PR #597 is still in a pending state after several hours

You have a problem with your .repo-metadata.json file:

Result of scan 📈:

• must have required property 'library_type' in .repo-metadata.json
• must have required property 'release_level' in .repo-metadata.json

☝️ Once you address these problems, you can close this issue.

Need help?

• Schema definition: lists valid options for each field.
• API index: for gRPC libraries api_shortname should match the subdomain of an API's hostName.
• Reach out to go/github-automation if you have any questions.

This issue provides visibility into Renovate updates and their statuses. Learn more

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• chore(deps): update actions/setup-node action to v2
• chore(deps): update codecov/codecov-action action to v2

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• chore(deps): update dependency gts to v3
• chore(deps): update dependency mocha to v9 (mocha, @types/mocha)
• fix(deps): update dependency meow to v10

• Check this box to trigger a request for Renovate to run again on this repository

Andrew is onboarding this week as a new Agendaless contractor for Node.js.

With both repos.json and DRIFT responsible for tracking GitHub repositories, it means there are two sources of truth. We should make DRIFT the single source of truth. Let's use this issue to track down all usages of repos.json that need to be rationalized.

• autosynth
• google-cloud-node
• github-repo-automation
• repo-automation-bots
• This repository!

• Update the repos.json and teams.json files to include the anthos-samples repository

Need to add them to team

Actually it's harmless, but it failed with:

message: 'Range (all_apis!A2320:Z12320) exceeds grid limits. Max rows: 2319, max columns: 26',

Downstream tools use a naive filter to identify auth-related repos, resulting in duplicate reporting of OOSLO issues in Core and Auth.

We should define an 'auth' team in teams.json and assign appropriate repos (for Java, Go, Python) to that team.

The scheduler jobs are failing.

sloth-cloud-apis-sync is failing constantly.

sloth-sheet-sync is flaky.

I was looking at the logs for the new sloth tag-issues kokoro job and noticed this in the logs.

Error: octokit.authenticate() is deprecated. Use "auth" constructor option instead.
    at authenticate (/home/node/.npm/_npx/9/lib/node_modules/@justinbeckwith/sloth/node_modules/@octokit/rest/plugins/authentication-deprecated/authenticate.js:4:16)
    at Object.<anonymous> (/home/node/.npm/_npx/9/lib/node_modules/@justinbeckwith/sloth/build/src/util.js:27:6)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.<anonymous> (/home/node/.npm/_npx/9/lib/node_modules/@justinbeckwith/sloth/build/src/issue.js:25:16)

Hello! Autosynth couldn't regenerate sloth. 💔

Here's the output from running synth.py:

2020-05-14 06:37:10,235 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/sloth
2020-05-14 06:37:10,238 synthtool [ERROR] > Failed executing git clone --single-branch https://github.com/googleapis/sloth.git /home/kbuilder/.cache/synthtool/sloth:

fatal: could not create work tree dir '/home/kbuilder/.cache/synthtool/sloth': No space left on device

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 600, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 472, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 519, in _inner_main
    working_repo_path = synthtool_git.clone(f"https://github.com/{args.repository}.git")
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 83, in clone
    shell.run(cmd, check=True)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'clone', '--single-branch', 'https://github.com/googleapis/sloth.git', PosixPath('/home/kbuilder/.cache/synthtool/sloth')]' returned non-zero exit status 128.

Google internal developers can see the full log here.

Update ownership plz. :)