hapijs / ammo Goto Github PK

Currently, all bytes of a range stream are processed before signalling 'end'.

Ideally, once the end of the range has been reached ,'end' is signalled, and processing is stopped.

Context

• node version: 10.15.3
• module version: 3.1.1

What are you trying to achieve or the steps to reproduce ?

v3 is missing the API.md file

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:

• CircleCI
• Travis CI
• Buildkite
• CodeShip
• Azure Pipelines
• TeamCity
• Buddy
• AppVeyor
  But Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

I am looking at the source trying to figure out how to use this - am I correct that ammo only deals with automatically returning the correct headers and does not provide any kind of incoming parsing of the Range request for my use in the code? i.e. that I still need to regex it to extract the range?

Thanks for your time