profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/crrobinson14/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Chad Robinson crrobinson14 Media Lantern Denver, CO USA https://www.medialantern.com/

actionhero/actionhero 2258

Actionhero is a realtime multi-transport nodejs API Server with integrated cluster capabilities and delayed tasks

crrobinson14/hotpi 6

Raspberry-Pi Based Boiler Control System

crrobinson14/crone 4

Redis-backed task queue and scheduler for NodeJS

crrobinson14/lambda-meta 3

AWS Lambda Metadata Wrappers

crrobinson14/class_style_filter 1

Drupal Class to Style Input Filter

crrobinson14/cognito-admin 1

Cognito User Pools Admin Panel

crrobinson14/grunt_schema_update 1

Database schema update utility for grunt-based builds and deployments

crrobinson14/actionhero 0

actionhero.js is a multi-transport nodejs API Server with integrated cluster capabilities and delayed tasks

crrobinson14/actionhero-angular-bootstrap-cors-csrf 0

angular.actionhero.com: Actionhero + Angular + Bootstrap + CORS + CSRF Demo Site

created tagVerdocs/js-sdk

tagv1.0.2

Verdocs SDK for Javascript / Typescript

created time in 5 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha 64242fdde5d24a4d453e82393a3766d867049b73

1.0.2

view details

push time in 5 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha b7d0fe1dc0c4fcdae995331a7d281310e990256c

Fix two lint issues

view details

push time in 5 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha a1aea674d538e144239d2305cdfbbd9bdd06ad8a

Update docs with new Templates endpoints

view details

push time in 5 days

push eventVerdocs/js-sdk

leadsoft

commit sha e290e2cdbe223dd2581fea72f15588c0cef1525e

Added new endpoints for rForm modules

view details

leadsoft

commit sha 676cff2102c1fec5c9260ab7d4570591ffe93c7a

Added endpoints for rForm modules

view details

Chad Robinson

commit sha 22b856bcfda282525b9a178aa90fd9b4ab760736

Merge pull request #1 from Verdocs/leadsoft/update-rform-endpoints Added new endpoints for rForm modules

view details

push time in 7 days

Pull request review commentVerdocs/js-sdk

Added new endpoints for rForm modules

 export * as Documents from './Documents'; export * as HTTP from './HTTP'; export * as Organizations from './Organizations';+export * as Signatures from './Signatures';

@leadsoft Let's start a Templates module to contain Validators/Signatures/etc as discussed.

leadsoft

comment created time in 7 days

PullRequestReviewEvent
PullRequestReviewEvent

push eventVerdocs/js-sdk

Chad Robinson

commit sha 576d68533dd09978683a1efe3b0cd56b5b82ec73

Update core dependencies.

view details

push time in 7 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha e6bc2eb3f372994bc99cc191c6ecc1afd11d53b6

Flesh out more high level docs

view details

push time in 7 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha e226c1c4ef8aba478f3007d4cf7392397dc145cd

Regenerate group docs

view details

push time in 7 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha c0b9ebf692d48bca9ce9ef60458ce68f413b8a55

Begin expanding group docs

view details

push time in 7 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha 4bbbd0a5158f81728f2a15b4fb46735761fdc572

Experiment with additional comment blocks.

view details

push time in 7 days

created tagVerdocs/js-sdk

tagv1.0.1

Verdocs SDK for Javascript / Typescript

created time in 7 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha 317d3a5827d558cebadaf718e3b958588280d244

1.0.1

view details

push time in 7 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha 8937ebc5b96b69dcbc2157f61b7af63d73ff28ce

Add test stubs and docs for Api Keys

view details

push time in 7 days

MemberEvent

push eventVerdocs/js-sdk

Chad Robinson

commit sha 717d31ad33652c7eb4ea090dc01e4048f9b0e948

Prepare package for publication

view details

push time in 11 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha abc801f4755fcfcc0bdab732d2c46a6a24979fce

Test reduction of documentation diff sizes.

view details

push time in 11 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha 5afb8e302a90748cded3df7472835feacc0cc6ff

Add gitRevision flag to typedoc to reduce future diff sizes.

view details

push time in 11 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha 64f04beceb386d28e01de3f561224775e2e1d82f

Address linter issues.

view details

push time in 11 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha fb278cbe0f74e8cfefbc1cb10dde521199e5faea

Remove HTML docs from repo, rename Markdown docs.

view details

push time in 11 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha 34c7ea0e0b1ab24ed63e2b7f6c32069290db980d

Refactor modules to simplify imports.

view details

push time in 11 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha 4c3fec6ff692a393785065ffdd45a738c68d569e

Refactor: Add a level of hierarchy to streamline app imports

view details

push time in 11 days

issue commentfirebase/firebase-functions

Error: The request was aborted because there was no available instance.

This thread doesn't seem like it needs more "venting," but the linked issue-tracker posts don't allow commenting so I guess I have no choice but to chime in here.

As I see it, from a developer's perspective the problem here is twofold:

  1. Yes, retrying requests is generally a Good Thing. But despite some side references above, this "need" is very lightly documented in the official Firebase docs. There are lots of claims about how it infinitely scales, but nothing I can find about how it might fail. Please tell me what I'm missing from this doc: https://firebase.google.com/docs/functions/callable None of the docs include "exponential backoff / retry" wrapper code or any hint that this is going to be a regular problem, and it's certainly not a problem with other FaaS offerings. It's hard to avoid the impression that Google is shifting blame for a genuine problem.

  2. The whole "no change was made, all that's happened is we're logging something you never saw before" claim doesn't wash. As others have reported above, our app is now (last 48 hours, that's why I'm here) suddenly experiencing a dramatic increase in this type of failure. But it's not related to a workload spike. The function our app is calling is in development. It only gets called once an hour at most, by our development team. We're seeing about a 5% failure rate when we do, but it's certainly not workload related. 5% doesn't sound like a lot but we're lucky we caught it in dev, because if we deployed this now we'd be swimming in user complaints.

Honestly I think @samodadela's https://github.com/firebase/firebase-functions/issues/962#issuecomment-920677241 above is my biggest fear. Sure, we can go re-engineer our app to add exponential backoffs to all calls. But Firebase has no mechanism to do that for scheduled functions or firestore triggers. "Just add retry options" CAN'T be the final answer here.

dimavedenyapin

comment created time in 11 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha cfc4bfe61ebad699a5ec8b982f94b020acf246cd

Test more doc updates

view details

push time in 12 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha 6ec87bdd02d2fe0ae1fad7653db487471336bd3b

Flesh out more docs

view details

push time in 12 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha 458266e5ec42ff156756fbd25252b0ef904b197d

Flesh out more module files.

view details

push time in 12 days

push eventVerdocs/js-sdk

Chad Robinson

commit sha f666edd6a58a42efc6e1320203fa3275f6f7c981

Flesh out remaining Profiles endpoints.

view details

push time in 12 days