profile
viewpoint

kevinswiber/calypso 19

A common query interface for data stores, featuring a SQL-like query language.

ExpressGateway/express-gateway-plugin-lambda 4

Proxy to AWS Lambda functions with Express Gateway

kevinswiber/caql-js-compiler 4

A CaQL compiler that converts queries into executable JavaScript.

kevinswiber/calypso-level 3

A calypso driver for LevelUP-compatible data stores.

kevinswiber/api-media-type 2

A Node.js module exporting a map of common media type names to registered IANA media type names. Built specifically to serve the needs of Web APIs.

kevinswiber/apigee-edgemicro-docker 2

Dockerize Apigee Edge Microgateway

kevinswiber/calypso-usergrid 2

A Usergrid session for Calypso.

kevinswiber/caql 2

Calypso Query Language Parser & AST

kevinswiber/express-gateway-plugin-http-cache 2

An HTTP-aware cache for Express Gateway.

issue commentpostmanlabs/postman-app-support

Postman waits endlessly when he receives a 102 statuscode.

Since the server has already responded with this code, how do you suggest that it responds again with another status code?

For the server this request has already been completed, there is nothing in the pipeline.

Hi, @anderjoy. HTTP clients that understand 102 Processing should leave the connection open. This is essentially a keep-alive ping to inform the client that the request has 1) been received and 2) is actually being handled by the server.

We use this code to notify the customer that the request is still processing, that they should wait a few seconds and try again. In our understanding, this code helps to avoid problems in the "retry pattern" since the verb "post" is not idempotent.

Consider perhaps returning a 202 Accepted response on the initial request. This can help model a job pattern in API design. In the 202 response, it's sometimes common to include a Location header that points to a resource that will return a status update for the job (e.g., received, processing, complete). If attempting to notify the client that the request has already been received on subsequent, identical calls, consider returning a 400 Bad Request with details in the representation that explain the request has already been received.

I did the test with another test application, and the result was different from Postman, in it, when receiving 102 status code the application does not "freeze" and shows the correct response code: 102 Processing.

Not all HTTP clients understand 102 Processing. It has, for all intents and purposes, been deprecated at this point. HTTP clients that don't understand 1xx response status codes will typically ignore it and close the connection after receiving the response.

Postman's behavior here models exactly what's expected in an HTTP client that actually supports 102, IMHO.

anderjoy

comment created time in a month

issue commentpostmanlabs/postman-app-support

Unable to Obtain OAuth Access Code

This appears to be an issue with the authorization popup as a result of receiving a WWW-Authenticate header. I know Electron-based apps have had issues with this in the past. This can now be intercepted with the login event, though a custom dialog would have to be crafted. https://www.electronjs.org/docs/api/app#event-login

danchirillo

comment created time in a month

issue commentpostmanlabs/postman-app-support

Ability to write API responses into the Postman Working Directory

Hey @georgesunil81, one option would be to store these values in Environment Variables using the Tests sandbox.

https://learning.postman.com/docs/postman/variables-and-environments/variables/#using-variables-in-scripts

You could use pm.environment.set('result', JSON.stringify(pm.response.json())) to store an object value and const val = JSON.parse(pm.environment.get('result')) to retrieve an object value.

georgesunil81

comment created time in a month

issue commentpostmanlabs/postman-app-support

Postman strips everything following a hash symbol from query parameters

Hi there.

Postman doesn't automatically URI-encode values in Params. You can highlight what you want to encode, right-click, and select EncodeURIComponent to do this manually. Reference: https://learning.postman.com/docs/postman/sending-api-requests/requests/#sending-parameters

image

Additional Background:

URI Syntax and HTTP implementations treat anything after a crosshatch (#) as a fragment identifier intended only for the User-Agent, so anything after the crosshatch won't actually make its way to the server. If the # character isn't intended as a URI fragment identifier, it must be URI-encoded (%23).

coccoinomane

comment created time in a month

startedmatt-ball/postman-cli

started time in 2 months

push eventnodesource/docker-nsolid

Johannes Würbach

commit sha 2d4249a963c308bd75f9fb92ae044f2bfba7d42b

Update to alpine 3.10

view details

push time in 4 months

PR merged nodesource/docker-nsolid

Update to alpine 3.10

Update alpine to latest (3.10) as 3.5 is getting fairly old (3.5.3 released 2018-09-11 https://git.alpinelinux.org/aports/commit/?h=3.5-stable&id=c93942e1ed93cd55bf8235955d4bb397ddda5a50).

Fixes https://github.com/nodesource/docker-nsolid/issues/32

+5 -5

2 comments

5 changed files

johanneswuerbach

pr closed time in 4 months

issue closednodesource/docker-nsolid

Update Alpine distribution versions

One of our customers is requesting newer versions of Alpine in our Docker images, current Alpine version at this moment is 3.8.2 (Released Dec 20, 2018) the one used in our current images is 3.5.3.

closed time in 4 months

edsadr

PR opened nodesource/homebrew-nsolid

Reviewers
dubnium -> erbium

Signed-off-by: Kevin Swiber kswiber@gmail.com

+1 -1

0 comment

1 changed file

pr created time in 4 months

create barnchnodesource/homebrew-nsolid

branch : kevinswiber/dubnium-to-erbium

created branch time in 4 months

issue commentfanout/reconnecting-eventsource

Change in the default export in lib?

@joyheron Thanks for looking into this! The trouble comes in with supporting both ES6 and CommonJS use cases (and then doing so across multiple versions of Node.js). The workaround you are using is a common one, though the developer experience is a bit unfortunate.

joyheron

comment created time in 5 months

push eventnodesource/homebrew-nsolid

Kevin Swiber

commit sha 48c28d7653f569fec4899a0d7752a29208a519f7

3.7.1 Signed-off-by: Kevin Swiber <kswiber@gmail.com>

view details

push time in 5 months

push eventnodesource/nsolid-azure

Kevin Swiber

commit sha fce1f31f38e59c392ff7836cd236faf959c53554

3.7.1 Signed-off-by: Kevin Swiber <kswiber@gmail.com>

view details

push time in 5 months

push eventnodesource/nsolid-gcp

Kevin Swiber

commit sha e0157a27662afdd36965cef3688b86009d097807

3.7.1 Signed-off-by: Kevin Swiber <kswiber@gmail.com>

view details

push time in 5 months

push eventnodesource/nsolid-aws

Kevin Swiber

commit sha b9116f991359ad5d64b5daaa34f02a83517524c5

3.7.1 Signed-off-by: Kevin Swiber <kswiber@gmail.com>

view details

push time in 5 months

delete branch nodesource/docker-nsolid

delete branch : erbium-fixes

delete time in 5 months

push eventnodesource/docker-nsolid

Adrian Estrada

commit sha 1b6e0c3a8fe696d0eaba56346a71cbd52c38ece8

Updating some docs for latest N|Solid and erbium

view details

push time in 5 months

push eventnodesource/docker-nsolid

Johannes Würbach

commit sha f8b2171bd50389886c3673c38ae1cc198e5fc80b

Add erbium images

view details

push time in 5 months

PR merged nodesource/docker-nsolid

Add erbium images

Add images for Node Erbium (v12), which should available now https://nodesource.com/blog/announcing-NSolid-V3.7.0

+24 -24

1 comment

17 changed files

johanneswuerbach

pr closed time in 5 months

issue commentfanout/reconnecting-eventsource

Change in the default export in lib?

Hey @joyheron, apologies. I just saw that you're using faucet-pipeline. You must be using faucet-pipeline-esnext. In your faucet config, please set an exclusion for reconnecting-eventsource.

Example:

module.exports = {
  js: [{
    source: './main.js',
    target: './bundle.js',
    esnext: {
      exclude: ["reconnecting-eventsource"]
    }
  }]
}

Hope this helps!

joyheron

comment created time in 5 months

issue commentfanout/reconnecting-eventsource

Change in the default export in lib?

Hi @joyheron, can you share your rollup config? This seems to work for me when I use the commonjs plugin. https://github.com/rollup/rollup-plugin-commonjs

joyheron

comment created time in 5 months

fork kevinswiber/reconnecting-eventsource

A small decorator for the JavaScript EventSource API that automatically reconnects

fork in 5 months

push eventnodesource/homebrew-nsolid

Kevin Swiber

commit sha d3505582e891e40316b6dc0bfda7c3ab5eb56813

3.7.0 Signed-off-by: Kevin Swiber <kswiber@gmail.com>

view details

push time in 5 months

push eventnodesource/nsolid-azure

Kevin Swiber

commit sha 9a2ea9d431ee9ff1c92b26bc9ea059c80efa1e6f

3.7.0 Signed-off-by: Kevin Swiber <kswiber@gmail.com>

view details

push time in 5 months

push eventnodesource/nsolid-gcp

Kevin Swiber

commit sha a9840d6c809804fc1ba1089755ddca31caff617e

3.7.0 Signed-off-by: Kevin Swiber <kswiber@gmail.com>

view details

push time in 5 months

push eventnodesource/nsolid-aws

Kevin Swiber

commit sha 750b68f8e6c7ee939206b0fe108f9fab161c541c

3.7.0 Signed-off-by: Kevin Swiber <kswiber@gmail.com>

view details

push time in 5 months

startedopticdev/optic

started time in 6 months

push eventnodesource/homebrew-nsolid

Kevin Swiber

commit sha 075b97fd8779ba50e2e68ec9dd7d3938b55cd83b

3.6.1

view details

push time in 6 months

push eventnodesource/nsolid-azure

Kevin Swiber

commit sha d11e55aa38a40ad2ff1d41dc09a284ff72f39b11

3.6.1

view details

push time in 6 months

push eventnodesource/nsolid-gcp

Kevin Swiber

commit sha ff223b02863342581d309379302864fa6d4a88c8

3.6.1

view details

push time in 6 months

push eventnodesource/nsolid-aws

Kevin Swiber

commit sha 162c5ad201a4232d42b24f984cc3339703624dad

3.6.1

view details

push time in 6 months

created tagkevinswiber/pulldown-cmark

tagv0.5.3-admonitions

created time in 6 months

delete tag kevinswiber/pulldown-cmark

delete tag : v0.5.3-admonitions

delete time in 6 months

push eventkevinswiber/pulldown-cmark

Kevin Swiber

commit sha cd6752fc61c9102a7f91e2b221dd4b4bb08093f8

Fixing admonitions flags on src/main.rs Signed-off-by: Kevin Swiber <kswiber@gmail.com>

view details

push time in 6 months

push eventkevinswiber/mdBook

Kevin Swiber

commit sha 9696d60864655d096858ecacb254cb282e175541

Updating pulldown-cmark to use latest admonitions fork. Signed-off-by: Kevin Swiber <kswiber@gmail.com>

view details

push time in 6 months

created tagkevinswiber/pulldown-cmark

tagv0.5.3-admonitions

created time in 6 months

delete tag kevinswiber/pulldown-cmark

delete tag : v0.5.3-admonitions

delete time in 6 months

push eventkevinswiber/pulldown-cmark

Kevin Swiber

commit sha 57274b5f5370a75aaaf28dcfbe2223ea300d77bc

Reducing number of loops on admonition detection. Signed-off-by: Kevin Swiber <kswiber@gmail.com>

view details

push time in 6 months

push eventkevinswiber/pulldown-cmark

Kevin Swiber

commit sha 31e21c754bd8923a7f5ddefc324f5bc06b16c154

Adding mroe admonition tests, cleaning up dead code. Signed-off-by: Kevin Swiber <kswiber@gmail.com>

view details

push time in 6 months

create barnchkevinswiber/mdBook

branch : kevinswiber/customizations

created branch time in 6 months

created tagkevinswiber/pulldown-cmark

tagv0.5.3-admonitions

created time in 6 months

delete tag kevinswiber/pulldown-cmark

delete tag : v0.5.3-admonitions

delete time in 6 months

push eventkevinswiber/pulldown-cmark

Kevin Swiber

commit sha 3da74b9c9b1a0f9b39b0b40e1d18781063b2a229

Fixing bug in admonitions. Signed-off-by: Kevin Swiber <kswiber@gmail.com>

view details

push time in 6 months

created tagkevinswiber/pulldown-cmark

tagv0.5.3-admonitions

created time in 6 months

create barnchkevinswiber/pulldown-cmark

branch : admonitions-v5

created branch time in 6 months

fork kevinswiber/mdBook

Create book from markdown files. Like Gitbook but implemented in Rust

fork in 6 months

more