profile
viewpoint

apex/up 7939

Deploy infinitely scalable serverless apps, apis, and sites in seconds to AWS.

apex/gh-polls 1675

Polls for user feedback in GitHub issues

JustinTulloss/zeromq.node 1664

Node.js bindings to the zeromq library

c4milo/gsync 334

gSync is an rsync based library for sending delta updates of files to a remote server.

apex/static 296

The static site anti-framework – general-purpose library, purpose-built commands for various domains

koajs/koa-hbs 154

Handlebars templates for Koa.js

apex/gui 132

GitHub readme UI components

littlstar/axis360 122

Axis360 is a panoramic (360 video) rendering engine

apex/apex-ui-slim 76

Apex monochrome Atom theme UI (slim variant)

littlstar/starplate 68

Lightning fast template and view engine built on top of Incremental DOM and Babel (ES6 Templates + Incremental DOM working together)

pull request commentapex/rpc

TS: use camel case in object field names

The generated approach is what I did with validation in the Go server portion and it works pretty nicely https://github.com/apex/rpc/blob/master/generators/gotypes/gotypes.go#L155-L168.

The schemas can get pretty huge so I don't think that would be ideal, especially for the browser JS client. I guess the JS client would be another reason to consider just leaving the fields as-is (timestamp stuff still applies though), but the extra bulk isn't really worth it there just for camelcase IMO.

kklas

comment created time in 5 days

release apex/up

v1.6.2

released time in 6 days

push eventapex/up

TJ Holowaychuk

commit sha c5ca649cd8bf1bb12c1fbbaec72130a98b89942f

Release v1.6.2-pro

view details

TJ Holowaychuk

commit sha ef62b9e282bd7f58ce5299ed289ecaf02a321858

Release v1.6.2

view details

push time in 6 days

startedbradfitz/shotizam

started time in 6 days

push eventapex/up

TJ Holowaychuk

commit sha 3899667a65f6d700c57ea79cb22116d73fa843a7

update .goreleaser.yml to remove drawin 386

view details

TJ Holowaychuk

commit sha e938b6308ab88422e347c3bb645e25c0872779f2

fix Stripe dep, Go is just randomly updating them...

view details

TJ Holowaychuk

commit sha abecacc31209bd5984f5d16596cdeef81a8673c7

Release v1.6.0-pro

view details

TJ Holowaychuk

commit sha 755e08a6568eef3d3017201bec1e84f22fa36d62

Release v1.6.1-pro

view details

push time in 6 days

delete tag apex/up

delete tag : v1.6.0

delete time in 6 days

pull request commentapex/up

change timeout through UP-TIMEOUT header. Closes #814

hmm great it's 100mb haha.. Go mod is really messing things up, I'll look into what's causing the bloat

t1bb4r

comment created time in 6 days

pull request commentapex/up

change timeout through UP-TIMEOUT header. Closes #814

Just uploading v1.6.0, should be up pretty soon

t1bb4r

comment created time in 6 days

created tagapex/up

tagv1.6.0

Deploy infinitely scalable serverless apps, apis, and sites in seconds to AWS.

created time in 6 days

release apex/up

v1.6.0

released time in 6 days

delete tag apex/up

delete tag : v1.6.0

delete time in 6 days

release apex/up

v1.6.0

released time in 6 days

created tagapex/up

tagv1.6.0

Deploy infinitely scalable serverless apps, apis, and sites in seconds to AWS.

created time in 6 days

push eventapex/up

TJ Holowaychuk

commit sha 5d36abd172b9075d7c94388f9de12838523d06ff

Release v1.6.0

view details

push time in 6 days

push eventapex/up

TJ Holowaychuk

commit sha 0b5ee77eb5b6a122fbc446e3dc60ac6f30090e91

update tj/go for git fix

view details

TJ Holowaychuk

commit sha c46d5b67aab38d22d988a59a1e256bf6cce38192

change id field to request_id

view details

TJ Holowaychuk

commit sha d5e15dfec65e2b7a86f0bb08a5a9b192458feb98

add support for X-Up-Timeout header field. Closes #815 the use-case was to bypass API Gateway by calling the Lambda function directly with a request event, thus no longer bound to the proxy.timeout max of 25s

view details

push time in 6 days

PR closed apex/up

change timeout through UP-TIMEOUT header. Closes #814

See #814

This change allows the timeout to be increased when calling lambda directly while keeping the timeout specified in the config as a default.

The tests run for 50seconds longer now because that's how long the timeout is set, let me know if I should reduce it.

+15 -1

2 comments

2 changed files

t1bb4r

pr closed time in 6 days

pull request commentapex/up

change timeout through UP-TIMEOUT header. Closes #814

awesome thanks! I tweaked it a little, I'll QA and get a release out right away

t1bb4r

comment created time in 6 days

created tagtj/staticgen

tagv1.1.0

Static website generator that lets you use HTTP servers and frameworks you already know

created time in 6 days

push eventtj/staticgen

TJ Holowaychuk

commit sha 9b13d39ada83055ce1dc62446fdb35df52f2d180

Release v1.1.0

view details

push time in 6 days

push eventtj/staticgen

Nick Hudkins

commit sha bd0b3ec2121dfbe746d2dc0a53920595d1d6d87f

respect Allow404 configuration

view details

TJ Holowaychuk

commit sha 3a9162e852c80cdd9e4a2f38c770188a3cf3cdaf

Merge pull request #16 from nickhudkins/allow-404 Respect Allow404 Configuration

view details

push time in 6 days

PR merged tj/staticgen

Respect Allow404 Configuration

@tj I made this change locally for myself to be able to allow 404s after reading #12.

Understanding that you may have a different implementation in mind, if not, here's a pass at it.

If you have some other plan, I am also happy to tackle that, as I expect that you may have a few balls in the air 😉

+6 -0

0 comment

2 changed files

nickhudkins

pr closed time in 6 days

Pull request review commenttj/staticgen

Respect Allow404 Configuration

 func (c *Crawler) visit(ctx context.Context, t Target) ([]*url.URL, Resource, er  	// http error 	if res.StatusCode >= 300 {-		return nil, r, fmt.Errorf("%s response", res.Status)+		shouldIgnore := c.Allow404 && res.StatusCode == 404+		err := fmt.Errorf("%s response", res.Status)

perfect thanks!

nickhudkins

comment created time in 6 days

PullRequestReviewEvent

Pull request review commenttj/staticgen

Respect Allow404 Configuration

 func (c *Crawler) visit(ctx context.Context, t Target) ([]*url.URL, Resource, er  	// http error 	if res.StatusCode >= 300 {-		return nil, r, fmt.Errorf("%s response", res.Status)+		shouldIgnore := c.Allow404 && res.StatusCode == 404+		err := fmt.Errorf("%s response", res.Status)

LGTM! The only thing I would change is to move the if res.StatusCode = 404 && c.Allow404 above 187 since it checks StatusCode already we don't need to nest it in the branch

nickhudkins

comment created time in 7 days

PullRequestReviewEvent

issue commentelm/browser

Currently no way of using preventDefault on window events

need this as well, there seems to be a disconnect between browser/html events, keypress etc are missing from the html package too

wolfadex

comment created time in 11 days

startedkraklin/elm-debug-transformer

started time in 12 days

push eventtj/vscode-snippets

TJ Holowaychuk

commit sha 425ad0ac2a768fed3668649b99c74d6a714cbc41

refactor elm snippets

view details

push time in 12 days

issue commentaws/serverless-application-model

Create machine-readable SAM spec

There's https://github.com/aws/serverless-application-model/blob/develop/samtranslator/validator/sam_schema/schema.json , but it doesn't seem up-to-date, it's missing HttpApi.

jlhood

comment created time in 12 days

push eventtj/tj

TJ Holowaychuk

commit sha ee91697afae4db4623cd231a1cef413de48f398c

docs

view details

push time in 12 days

startedflix/flix

started time in 13 days

push eventtj/sponsors

TJ Holowaychuk

commit sha de5a43c8ff579dfc39fcbe05228d734ae9036e96

add apex/rpc to docs

view details

push time in 13 days

pull request commenttj/gobinaries

Setting CGO_ENABLED=0

It should be ok now, I purged the CF cache and GCP builds

ItalyPaleAle

comment created time in 14 days

created tagapex/parsers

tagv1.2.1

Performant Go log format parsers.

created time in 14 days

push eventapex/parsers

TJ Holowaychuk

commit sha 8f732bb35953ee0cc1e6b282250388e315b7e6b4

change HerokuScale event to accommodate multiple dynos Heroku seems to output all of them for some reason

view details

TJ Holowaychuk

commit sha edb2a13a8e2c446a7c54e8ffd57077fc80679c92

Release v1.2.1

view details

push time in 14 days

push eventapex/parsers

TJ Holowaychuk

commit sha 11ad0e90f782c58857903fad82d02a003e1ef522

remove HerokuScale event they seem to show all of the dynos in these logs, so it would require more complex parsing

view details

push time in 14 days

push eventtj/gobinaries

TJ Holowaychuk

commit sha d62cc321d3781fd3f04babc98e37f4fb009ec249

update dockerfile to Go 1.15

view details

TJ Holowaychuk

commit sha bffcba3445f8eca5ff56fcb563d10a5c180619e1

Release v1.2.0

view details

push time in 14 days

created tagtj/gobinaries

tagv1.2.0

Golang binaries compiled on-demand for your system

created time in 14 days

push eventtj/gobinaries

TJ Holowaychuk

commit sha 1568ee90fa8db4100dfe1233bcab57270dbf3652

Release v1.2.0

view details

push time in 14 days

push eventtj/gobinaries

Alessandro (Ale) Segala

commit sha bb12e4e095c687ea469163b2c55505752faa168b

Setting CGO_ENABLED=0 This makes the binaries fully static also on Linux/amd64 so they work on Alpine too

view details

TJ Holowaychuk

commit sha 0503daf98c532eb3e27f553487ca08c78303091b

Merge pull request #32 from ItalyPaleAle/disable-cgo Setting CGO_ENABLED=0

view details

push time in 14 days

PR merged tj/gobinaries

Setting CGO_ENABLED=0

This makes the binaries fully static also on Linux/amd64 so they work on Alpine too. Should fix #4

To address the biggest concern: yes, this makes it impossible to build binaries that have dependencies on native code (CGo). This should not really be an issue, however: gobinaries is designed for cross-compilation, which means CGo wasn't usable before anyways. In fact, CGO_ENABLED is already disabled when cross-compiling; this PR disables it for Linux/amd64 too.

+1 -0

2 comments

1 changed file

ItalyPaleAle

pr closed time in 14 days

issue closedtj/gobinaries

Alpine support

Sounds like you have to build with musl-gcc: https://www.reddit.com/r/golang/comments/4cxrcv/whats_the_proper_way_to_build_golang_apps_for/

closed time in 14 days

tj

pull request commenttj/gobinaries

Setting CGO_ENABLED=0

SGTM!

ItalyPaleAle

comment created time in 14 days

pull request commenttj/go-redirects

Add license to be more explicit about MIT

thanks!

MadLittleMods

comment created time in 18 days

push eventtj/go-redirects

Eric Eastwood

commit sha d24569fd0116145fff9c1831b543d07cdf96823f

Add license to be more explicit about MIT There is a MIT badge on the readme but we were slightly unclear if that was enough, https://gitlab.com/gitlab-org/gitlab-pages/-/merge_requests/336#note_409856646

view details

TJ Holowaychuk

commit sha fd1ba1020b3792bd2db5ccd461656651955d9c57

Merge pull request #1 from MadLittleMods/add-license Add license to be more explicit about MIT

view details

push time in 18 days

PR merged tj/go-redirects

Add license to be more explicit about MIT

Add license to be more explicit about MIT

There is a MIT badge on the readme but we were slightly unclear if that was enough, https://gitlab.com/gitlab-org/gitlab-pages/-/merge_requests/336#note_409856646

+22 -0

1 comment

1 changed file

MadLittleMods

pr closed time in 18 days

pull request commentapex/rpc

TS: use camel case in object field names

Snake-case doesn't bother me here but if we're solving for timestamps anyway we might as well. I still kind of like plain objects over using Maps personally, more just from a UX perspective, from a technical perspective I definitely agree.

I suppose the simplest would just be some simple encode/decode functions per-type, could be fancier but basically:

function encodeGetAlertsInput(o) {
  const v = {}
  
  if (Object.hasOwnProperty.call(o, 'projectId')) {
      v.projectId = o.projectId
  }

  return v
}

function decodeGetAlertsOutput(o) {
  const v = {}
  // ... map o.alerts with decodeAlert blah blah
  return v
}

function decodeAlert(o) {
  const v = {}
  
  if (Object.hasOwnProperty.call(o, 'created_at')) {
    v.createdAt = o.created_at
  }

  if (Object.hasOwnProperty.call(o, 'updated_at')) {
    v.updatedAt = o.updatedAt
  }

  // ... other fields

  return v
}

And sneak the timestamp -> Date conversion in there as well. Any thoughts on a cleaner solution there? Since we're generating we might as well make it as performant as possible I guess.

kklas

comment created time in 20 days

pull request commentapex/rpc

TS: use camel case in object field names

At the moment it allows arbitrary objects:

        {
          "name": "fields",
          "description": "the log fields.",
          "type": "object"
        },

Which I'm using for user-defined event fields. I didn't think about that before, but to convert between the cases we'd pretty much have to generate the conversion functions from the types I guess, feels a bit ugly though

kklas

comment created time in 21 days

pull request commentapex/rpc

TS: use camel case in object field names

Looks pretty good to me, I think the only tricky part is say for example you have a nested object passed to a call which should not be camel-cased. In my case the user_id in add_events({ events: [{ fields: { user_id: xxx } }] }) should be left as-is, so I think just blindly recursing could lead to errors.

We could generate some functions specific to the generated types, but I'm still not sure it's worth it

kklas

comment created time in 21 days

issue commentapex/up

Add timeout config option when invoking lambda directly.

Hmm yeah you're right, a header field should work fine, I'll check that out this week

t1bb4r

comment created time in 21 days

issue closedapex/roadmap

Minor UX improvements

These are relatively small so I'm going to group them all here.

  • [x] Add result limit status bar input
  • [x] Add shadow to timeseries when scrolling
  • [x] Add event wrapping option
  • [x] Fix missing pointer cursor for saved searches
  • [x] Fix bug where id field is appended after filtering
  • [x] Add project to webhook JSON
  • [x] Change Slack message color for INFO level events

closed time in 22 days

tj

created tagapex/logs

tagv0.9.20

Apex Logs client for Go.

created time in 22 days

release apex/logs

v0.9.20

released time in 22 days

created tagapex/logs

tagv0.9.19

Apex Logs client for Go.

created time in 22 days

release apex/logs

v0.9.19

released time in 22 days

created tagapex/logs

tagv0.9.18

Apex Logs client for Go.

created time in 22 days

release apex/logs

v0.9.18

released time in 22 days

issue closedapex/roadmap

Alternate themes

I have a dark theme almost ready to go, but I don't think there's a way to change the PWA title bar dynamically.

  • [x] make sure all components utilize color vars
  • [x] add build watcher
  • [x] separate theme builds
  • [x] fix shadows
  • [x] style alerts
  • [x] fix number selection, remove the arrows
  • [x] fix popovers, too dark
  • [x] fix search history background hover color
  • [x] style dark events
  • [x] style dark timeseries
  • [x] style overlay
  • [x] add light theme scrollbar styling
  • [x] style dark JSON
  • [x] style dark sign-in
  • [x] style dark search input buttons
  • [x] remove opinionated choices from base theme
  • [x] refactor to move more app-specific styling to theme
  • [x] better warning / danger colors
  • [x] detect dark mode automatically: https://stackoverflow.com/questions/56393880/how-do-i-detect-dark-mode-using-javascript
  • [x] find solution around Parcel's limitations for serving the themes
  • [x] add theme setting in config menu with color variants
  • [x] choose color variants
  • [ ] add to marketing site
  • [ ] add twitter profile image
  • [ ] QA other browsers

closed time in 22 days

tj

issue openedapex/roadmap

Theme variants

Decided to defer this for now, but it'd be nice to have more color variants, easy little thing to add but needs a bit of UI for the config.

created time in 22 days

issue commentapex/log

The level of logging for Trace should not be locked to Info.

Hmm if you have an error the trace should be using the error severity: https://github.com/apex/log/blob/master/entry.go#L156, but yeah as you mentioned there's no way to tweak the initial Trace event, I'm not sure what would be best there.

I always enable INFO level in production personally, it's better to have more info than not enough, which is partly why I started https://apex.sh/logs/ :D, it's cost-effective enough to hold onto all those INFOs. I'm not against adding something like TraceAt() but wouldn't the Stop(err) be enough in the case you're mentioning?

J0eJ0h

comment created time in 22 days

issue commentapex/logs-js

Team member emails not received

no problem! I'll get that fixed in the next release, let me know if there are any other issues

obibring

comment created time in 25 days

issue commentapex/logs-js

Team member emails not received

Ahh sorry about that, they should still be able to sign-in, it just adds a database record at the moment.

For security reasons I can't send an email with a sign-in token unfortunately, but I should at least send a link to the UI so they can sign-in from there instead of having to share the link with co-workers.

obibring

comment created time in 25 days

issue commentapex/logs

Is this the repo for the command line tool?

It's basically just some gcloud commands, nothing too interesting :D

mhart

comment created time in 25 days

issue commentparcel-bundler/website

Document serving static files

I just get Name already registered with serializer, which seems to still be an open bug

mischnic

comment created time in 25 days

issue commentparcel-bundler/website

Document serving static files

ah damn it's v2, which seems broken :'(

mischnic

comment created time in 25 days

issue commentparcel-bundler/parcel

How to serve static files?

Would be nice to have an option to serve assets as an SPA would

saratonite

comment created time in 25 days

startedClementTsang/bottom

started time in 25 days

issue commentapex/up

Add timeout config option when invoking lambda directly.

Sounds pretty reasonable to me! The only problem I guess is that you can only really have one timeout configuration, so if you set it above ~30 it will lead to API Gateway handling the timeout instead of Up. I think the response was always plain-text or maybe it was JSON I forget, but there's not much control over that response

t1bb4r

comment created time in 25 days

pull request commentapex/rpc

TS: use camel case in object field names

Awesome! I'll take a look soon

kklas

comment created time in 25 days

issue openedapex/roadmap

Refactor UI to use web-components

Long-term I'd like to move more towards Elm and use web components for the individual components which are too complex to represent in Elm, so utilizing WC will be the first step.

created time in 25 days

push eventapex/rpc

TJ Holowaychuk

commit sha 42684dd25e61956edc4e6c2f6a06a49b53b8df91

add rpc.WriteResponse() benchmark

view details

push time in 25 days

startedgoccy/go-json

started time in 25 days

startedgoccy/go-reflect

started time in 25 days

issue commentapex/logs

Is this the repo for the command line tool?

No sorry the product itself is closed source, I'm just using this repo for the tarballs. If I end up hitting a decent milestone maybe I'll open-source it some day

mhart

comment created time in 25 days

release apex/logs

v0.9.17

released time in a month

created tagapex/logs

tagv0.9.17

Apex Logs client for Go.

created time in a month

create barnchvisionmedia/apex

branch : master

created branch time in a month

created repositoryvisionmedia/apex

Old apex/apex

created time in a month

push eventtj/tj

TJ Holowaychuk

commit sha b125398ed432ce0fca0ae2cbb24dd9b39c970380

Update Readme.md

view details

push time in a month

startedjustinethier/cyclone

started time in a month

issue commentapex/rpc

[TS types] can we have camel casing for field names?

It's definitely doable to recurse, but I'm not sure it's really worth the pain, I don't mind the snake-case much personally but I don't use any linters

kklas

comment created time in a month

issue openedapex/roadmap

Integration guides

  • [ ] Add sections to the docs navigation
  • [ ] Add guides for each integration and language (make sure to mention JSON output for Heroku/Lambda)
  • [ ] Add FAQ section to marketing site
  • [ ] Add alerts section to marketing site
  • [ ] Add integrations section to marketing site

created time in a month

IssuesEvent

issue commentapex/rpc

[TS types] can we have camel casing for field names?

oh actually I just remembered why it's this way, because TS will serialize the fields incorrectly. If fields are defined as project_id in the schema, then you get projectId since — as far as I know — there's no easy way to map JSON property names in TS like there is in Go for example.

kklas

comment created time in a month

created tagapex/rpc

tagv0.3.2

Simple RPC style APIs with generated clients & servers.

created time in a month

push eventapex/rpc

TJ Holowaychuk

commit sha 81774d79d4d38fc617644acac3267b6cc23685c2

Revert "fix camel-casing of TS type field names" This reverts commit 370c3659c52d568eddfc788ce96e739e153104e9.

view details

TJ Holowaychuk

commit sha 7264abc52510be180eee61b3d709fb8136a4a365

Release v0.3.2

view details

push time in a month

issue closedapex/rpc

[TS types] can we have camel casing for field names?

Currently it's snake_cased: https://github.com/apex/rpc/blob/master/generators/tstypes/testdata/todo_types.ts#L4

I'm using prettier on my codebase which is a very opinionated code formatter and I guess many other people are too considering the number of stars it has on github.

Prettier is strict about using camelCasing for object field names so it gives me very annoying eslint errors when I try to instantiate api types.

It would be great if we had a flag in the generator to generate camelCased fields instead. WDYT?

closed time in a month

kklas

issue commentapex/rpc

[TS types] can we have camel casing for field names?

370c365 thanks!

kklas

comment created time in a month

created tagapex/rpc

tagv0.3.1

Simple RPC style APIs with generated clients & servers.

created time in a month

push eventapex/rpc

TJ Holowaychuk

commit sha 370c3659c52d568eddfc788ce96e739e153104e9

fix camel-casing of TS type field names

view details

TJ Holowaychuk

commit sha f26ef1b1b1375911d4b5167aa5be4f3f13a540cb

Release v0.3.1

view details

push time in a month

created tagapex/rpc

tagv0.3.0

Simple RPC style APIs with generated clients & servers.

created time in a month

push eventapex/rpc

TJ Holowaychuk

commit sha 9b9dace0be772c8505ed050b0344a7bf9039514c

Release v0.3.0

view details

push time in a month

issue commentapex/rpc

[TS types] can we have camel casing for field names?

somehow I missed that haha, yeah I think we should use whatever is idiomatic for the target language, so SGTM, I'll fix that today

kklas

comment created time in a month

issue openedapex/rpc

Crystal client

created time in a month

created tagapex/logs

tagv0.9.16

Apex Logs client for Go.

created time in a month

release apex/logs

v0.9.16

released time in a month

push eventapex/parsers

push time in a month

push eventapex/parsers

TJ Holowaychuk

commit sha b3b5707c6f4fef5fd9e38e555ed0b13884901dbc

add HerokuProcessStop event with Signal

view details

TJ Holowaychuk

commit sha be1c001a072a69af69313c656d282c641f582286

fix HerokuProcessStop event, looks like Heroku changed the format

view details

push time in a month

push eventapex/parsers

TJ Holowaychuk

commit sha 514a7fa8c4e6a9e67e7812376369267192dc04d1

docs

view details

push time in a month

issue commenttj/go-naturaldate

Support "6 month" with the future direction

SGTM, happy to take a look at a PR, might be a little while until I can get to it

NightMachinary

comment created time in a month

more