profile
viewpoint
Benjamin E. Coe bcoe Google Waterloo https://twitter.com/benjamincoe Co-founded Attachments.me, early employee at npm Inc. Maintains yargs, Istanbul, contributes to Node.js. Currently cloud at Google.

bcoe/Adventures-in-Document-Thumbnailing 14

Some thoughts I have about creating thumbnails of common document types.

bcoe/ansible-nagios-config 10

Ansible role for configuring Nagios 4.

bcoe/apidoc-md 9

Generate API documentation for your README from comments in your source-code

bcoe/AFHTTPRequestOperationManager-Timeout 6

Add timeout functionality to AFHTTPRequestOperationManager with Category

bcoe/any-path 4

:rage2: make the keys on an object path.sep agnostic.

AkashaCoin/ravejs 3

RaveJS Beginnings

bcoe/assertassert 3

:trollface: for when you can't decide on an assertion library

bcoe/ansible-pg-wale 2

Configure Heroku's WAL-E for Postgres

ashwinGokhale/IstanbulSplashPage 1

Splash page for Istanbul

bcoe/ansible-elasticsearch 1

Ansible playbook for Elasticsearch

PullRequestReviewEvent

push eventchingor13/release-please

Jeff Ching

commit sha 81fc0f49d75ec66ef1915be26330734abddd11d7

feat: return path along with created release (#1114)

view details

Jeff Ching

commit sha 2265a13b5f1b99a1e7ab92034bd36a68026b7ce6

refactor: rename release-notes to changelog-notes and make it swappable (#1113) Co-authored-by: Benjamin E. Coe <bencoe@google.com>

view details

Benjamin E. Coe

commit sha 4b6ae5049e39e6f5bca10b514256090ea76ef5bd

fix: add back version/major/minor/patch (#1118)

view details

Jeff Ching

commit sha bf9aacdde3a97c453f6e3280035607c97c7dffcd

feat: add `includeComponentInTag` option for strategies and hook up to `--monorepo-tags` (#1119) * feat: add includeComponentInTag option for strategies * hook up --monorepo-tags to includeComponentInTag

view details

Jeff Ching

commit sha 0aeb67b4c4a497b5570bdec10f5ab15e620b235d

fix: Manifest.fromConfig can find latest release version without component (#1123)

view details

Jeff Ching

commit sha 2f3e84c8c51f367cad8baae44c8d9f0727aa02a5

feat: reimplement custom pull request title (#1122)

view details

Jeff Ching

commit sha 26442f14356c387c9117f5d660b532185c8084c4

fix: switch branch delimiter to `--` (#1127)

view details

Benjamin E. Coe

commit sha 88586f71b284ca6d66798dd375b7c056a7cfea7d

Merge branch 'main' into go-version2

view details

push time in 14 hours

PullRequestReviewEvent
PullRequestReviewEvent

issue commentyargs/yargs

How to "catch-all" unhandled exceptions

@peterp have you tried awaiting yargs:

try {
  await yargs.parseAsync()
} catch (err) {
  // do something.
}

If this isn't supporting sub-commands, I think it's a bug we should make an effort to fix.

peterp

comment created time in 20 hours

pull request commentyargs/yargs

fix: array options should not eat positionals

@jly36963 I'm not sure of the best solution for this problem, will need to page the edge case back into memory.

In hindsight, I've never been a big fan of the array type, which seems too magical. Better that you provide arguments like --arr foo,bar,snuh, or --arr one --arr two.

Suggest setting 'greedy-arrays' setting to false

I'm tempted to make this the default behavior when we eventually move to v18 of yargs ... if there's a tweak that an make behavior a bit more intuitive in the interim, I'm all ears.

jly36963

comment created time in 2 days

issue commentWICG/uuid

Secure contexts

the development environment concern is real... and is something we need to address to foster adoption of features limited to secure contexts

What is the plan for addressing these concerns? And what is the timeline for that plan?

Would love to pitch in and help with this problem. Perhaps the answer is a well supported polyfill for secure contexts, that we could point developers towards for their dev environments. Then, when the topic of secure contexts comes up, there's a consistent answer for people.

annevk

comment created time in 2 days

issue closedWICG/uuid

Prose of "generating a random UUID" could be simplified

For "Generating a random UUID", I wonder if we can rewrite the section to either:

  • drop the section entirely, just hook directly into RFC4122 (ideally). If things need to be fixed or better worded, we should update RFC4122 instead. This would be my preference, as I'm concerned about duplication with RFC4122.

  • Or, rewrite the algorithm such that it's more like this:

  1. Let |time-low:string| be ...
  2. Let |time-mid:string| be...
  3. Let |time-high-and-version:string| be..
  4. ... other parts....
  5. Let |parts| be [=list=] « time-low, time-mid... ».
  6. Let |uuid:string| be [=string/Concatenate=] |parts| using separator "-".
  7. Return |uuid|.

closed time in 2 days

marcoscaceres

issue commentWICG/uuid

Prose of "generating a random UUID" could be simplified

I'm personally not opposed to the current text.

👍 I'm going to go ahead and close this ticket than, we can iterate in the upstream spec in the future if we like.

Conformance requirements phrased as algorithms or specific steps may be implemented in any manner

Thanks for pointing out this caveat. In practice it seems like most folks implement UUID v4 with various optimizations that would look pretty ugly in spec text (buffers of random bytes, bit shifting tricks).

marcoscaceres

comment created time in 2 days

PullRequestReviewEvent

push eventgoogleapis/nodejs-security-private-ca

Justin Beckwith

commit sha a52d8381e371f73ef21b22a8faa389235c58c5a8

feat!: default to v1 of the API (#88) refactor!: v1 removes methods 'restoreCertificateAuthority', 'scheduleDeleteCertificateAuthority', 'getReusableConfig', 'listReusableConfigs' refactor!: resource paths have changed for some methods, e.g., certificateAuthorities becomes caPools Co-authored-by: Owl Bot <gcf-owl-bot[bot]@users.noreply.github.com> Co-authored-by: sofisl <55454395+sofisl@users.noreply.github.com> Co-authored-by: Benjamin E. Coe <bencoe@google.com> Co-authored-by: Jeffrey Rennie <rennie@google.com>

view details

push time in 4 days

delete branch googleapis/nodejs-security-private-ca

delete branch : usev1

delete time in 4 days

PR merged googleapis/nodejs-security-private-ca

feat!: default to v1 of the API cla: yes api: security-privateca

refactor!: v1 removes methods 'restoreCertificateAuthority', 'scheduleDeleteCertificateAuthority', 'getReusableConfig', 'listReusableConfigs'

+12 -15

3 comments

4 changed files

JustinBeckwith

pr closed time in 4 days

push eventgoogleapis/nodejs-security-private-ca

bencoe@google.com

commit sha 60b56127bf3ca7099db178b5c1158d8052103929

build: run the generator

view details

push time in 4 days

issue openedgoogleapis/release-please

release-please fails to find existing release for Node.js, results in 422

Problem

release-please is failing to find an existing pull request for yargs/yargs, this results in a 422 error when it attempts to create a branch that already exists (gist available upon request).

Reproducing

node ./build/src/bin/release-please.js release-pr --release-type=node --token=$GITHUB_TOKEN --repo-url=yargs/yargs

created time in 4 days

push eventyargs/yargs

bencoe@google.com

commit sha 3ec7cffe589467867fab28cddf1c3cbd3706d130

build: switch back to v2 of release-please

view details

push time in 4 days

PR closed yargs/yargs

chore: release 17.3.0 autorelease: pending

:robot: I have created a release *beep* *boop*

17.3.0 (2021-11-26)

Features

  • fallback to default bash completion (74c0ba5)

Bug Fixes

  • avoid legacy accessors (#2013) (adb0d11)
  • deps: update dependency yargs-parser to v21 (#2063) (76c1951)
  • don't fail if "fileURLToPath(import.meta.url)" throws (3a44796)

This PR was generated with Release Please. See documentation.

+15 -1

0 comment

2 changed files

bcoe

pr closed time in 4 days

push eventyargs/yargs

Benjamin E. Coe

commit sha 1254c8fc4d837c323e21b05801cd6d2d7b413da1

chore: release 17.3.0

view details

push time in 4 days

PR opened yargs/yargs

chore: release 17.3.0

:robot: I have created a release *beep* *boop*

17.3.0 (2021-11-26)

Features

  • fallback to default bash completion (74c0ba5)

Bug Fixes

  • avoid legacy accessors (#2013) (adb0d11)
  • deps: update dependency yargs-parser to v21 (#2063) (76c1951)
  • don't fail if "fileURLToPath(import.meta.url)" throws (3a44796)

This PR was generated with Release Please. See documentation.

+15 -1

0 comment

2 changed files

pr created time in 4 days

create barnchyargs/yargs

branch : release-v17.3.0

created branch time in 4 days

delete branch yargs/yargs

delete branch : release-v17.3.0

delete time in 4 days

PR closed yargs/yargs

chore: release 17.3.0 autorelease: pending

:robot: I have created a release *beep* *boop*

17.3.0 (2021-11-26)

Features

  • fallback to default bash completion (74c0ba5)

Bug Fixes

  • avoid legacy accessors (#2013) (adb0d11)
  • deps: update dependency yargs-parser to v21 (#2063) (76c1951)
  • don't fail if "fileURLToPath(import.meta.url)" throws (3a44796)

This PR was generated with Release Please. See documentation.

+15 -1

0 comment

2 changed files

github-actions[bot]

pr closed time in 4 days

push eventyargs/yargs

bencoe@google.com

commit sha 375b00b642371bfb3616075a6f657dfa5c27fd98

build: test release-please-action@v3

view details

Colin GILLE

commit sha 3a44796c84e3cb60769841d5883448a396227ade

fix: don't fail if "fileURLToPath(import.meta.url)" throws Co-authored-by: Colin GILLE <colin.gille@blgcloud.com> Co-authored-by: Benjamin E. Coe <bencoe@google.com>

view details

Benjamin E. Coe

commit sha 9246afc0e34d8d169a0516648cfaff712624c9eb

chore: release 17.3.0

view details

push time in 4 days

pull request commentyargs/yargs

fix: don't fail if "fileURLToPath(import.meta.url)" throws

@Congelli501 thank you for the contribution.

Congelli501

comment created time in 4 days

push eventyargs/yargs

Colin GILLE

commit sha 3a44796c84e3cb60769841d5883448a396227ade

fix: don't fail if "fileURLToPath(import.meta.url)" throws Co-authored-by: Colin GILLE <colin.gille@blgcloud.com> Co-authored-by: Benjamin E. Coe <bencoe@google.com>

view details

push time in 4 days

PR merged yargs/yargs

fix: don't fail if "fileURLToPath(import.meta.url)" throws

For usage like:

  • built final project used in a javascript vm
  • project built on unix via webpack and used on windows (path format are incompatible with drive letters on windows)

https://github.com/webpack/webpack/issues/14445

+7 -2

1 comment

1 changed file

Congelli501

pr closed time in 4 days

PullRequestReviewEvent

push eventCongelli501/yargs

Landon Yarrington

commit sha 4965ededd2f7fc761161910d99691d61022e8f5e

build: fix ts build errors (#2071)

view details

bencoe@google.com

commit sha 4e9cb781ffa2cc23f7cd0b5a0c6885c4290aa25e

build: test candidate release of release-please

view details

bencoe@google.com

commit sha 02d111be5300930a5a2815067113d0a80c27c178

build: test candidate release of release-please

view details

bencoe@google.com

commit sha 1579f58af2d0d17bcfd72329e4ec47f5bd8cb40f

build: revert to non-testing version of release-please

view details

bencoe@google.com

commit sha 95a387e467e0ba69dd01840076a4ee0e51077ac2

build: revert to non-testing version of release-please

view details

hardfist

commit sha 6a464b307abacc019a218f6d1c3faf940503a376

docs: add esbuild bundling guide (#2075)

view details

bencoe@google.com

commit sha 375b00b642371bfb3616075a6f657dfa5c27fd98

build: test release-please-action@v3

view details

Benjamin E. Coe

commit sha 0ed267457b35b8f63373b5bb47c23ff1ddcf3d17

Merge branch 'main' into main

view details

push time in 4 days

PullRequestEvent

create barnchyargs/yargs

branch : release-v17.3.0

created branch time in 4 days

more