status
stringclasses 1
value | repo_name
stringlengths 9
24
| repo_url
stringlengths 28
43
| issue_id
int64 1
104k
| updated_files
stringlengths 8
1.76k
| title
stringlengths 4
369
| body
stringlengths 0
254k
⌀ | issue_url
stringlengths 37
56
| pull_url
stringlengths 37
54
| before_fix_sha
stringlengths 40
40
| after_fix_sha
stringlengths 40
40
| report_datetime
unknown | language
stringclasses 5
values | commit_datetime
unknown |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
closed | fastify/fastify | https://github.com/fastify/fastify | 271 | ["docs/Routes.md", "fastify.js", "lib/handleRequest.js", "test/async-await.js", "test/listen.test.js"] | reply.view() throws inside async function | Basically you can't use reply.view ([point-of-view](https://github.com/fastify/point-of-view) plugin) inside async function.
```javascript
const fastify = require('fastify')();
fastify.register(require('point-of-view'), {
engine: {
handlebars: require('handlebars')
},
templates: './templates'
});
fastify.get('/view', async function (request, reply) {
var vars = await new Promise(function (resolve) {
setTimeout(resolve, 200, { text: 'hello there' })
})
reply.view('index.hbs',vars)
})
fastify.listen(3000);
```
throws error
```
_http_outgoing.js:489
throw new Error('Can\'t set headers after they are sent.');
^
Error: Can't set headers after they are sent.
at validateHeader (_http_outgoing.js:489:11)
at ServerResponse.setHeader (_http_outgoing.js:496:3)
at Reply.header (/Volumes/Test/Fastify/node_modules/fastify/lib/reply.js:110:12)
at _readCallback (/Volumes/Test/Fastify/node_modules/point-of-view/index.js:59:14)
at tryToString (fs.js:514:3)
at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:502:12)
``` | https://github.com/fastify/fastify/issues/271 | https://github.com/fastify/fastify/pull/273 | ed2e1afc0e163e8f27da16a92668a3ec8e5c36a6 | 4ae1654b9fd49a80142e211bf1ce29a4be73224f | "2017-09-21T08:09:12Z" | javascript | "2017-09-21T08:46:44Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 261 | ["package.json"] | An in-range update of request is breaking the build 🚨 |
## Version **2.82.0** of [request](https://github.com/request/request) just got published.
<table>
<tr>
<th align=left>
Branch
</th>
<td>
<a href="/fastify/fastify/compare/greenkeeper%2Frequest-2.82.0">Build failing 🚨</a>
</td>
</tr>
<tr>
<th align=left>
Dependency
</td>
<td>
request
</td>
</tr>
<tr>
<th align=left>
Current Version
</td>
<td>
2.81.0
</td>
</tr>
<tr>
<th align=left>
Type
</td>
<td>
devDependency
</td>
</tr>
</table>
This version is **covered** by your **current version range** and after updating it in your project **the build failed**.
As request is “only” a devDependency of this project it **might not break production or downstream projects**, but “only” your build or test tools – **preventing new deploys or publishes**.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
<details>
<summary>Status Details</summary>
- ❌ **coverage/coveralls** Coverage pending from Coveralls.io [Details](https://coveralls.io/builds/13342638)
- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/fastify/fastify/builds/277483731?utm_source=github_status&utm_medium=notification)
</details>
---
<details>
<summary>Commits</summary>
<p>The new version differs by 27 commits.</p>
<ul>
<li><a href="https://urls.greenkeeper.io/request/request/commit/0ab5c36b6715ae054b8398c80791fdd65be69f72"><code>0ab5c36</code></a> <code>2.82.0</code></li>
<li><a href="https://urls.greenkeeper.io/request/request/commit/ffdf0d3270a2c4427c4777cb8be7775dcdecdd95"><code>ffdf0d3</code></a> <code>Updating deps.</code></li>
<li><a href="https://urls.greenkeeper.io/request/request/commit/43868364c3e277d83c73faa8354ba2fd5af3ef1d"><code>4386836</code></a> <code>Merge branch 'master' of github.com:request/request</code></li>
<li><a href="https://urls.greenkeeper.io/request/request/commit/15274078b978b5869397e7770e68e7147fb9bd95"><code>1527407</code></a> <code>Merge pull request #2703 from ryysud/add-nodejs-v8-to-travis</code></li>
<li><a href="https://urls.greenkeeper.io/request/request/commit/3afcbf8a3e86dcd5c06aab0cd4eec5b11508b3e5"><code>3afcbf8</code></a> <code>Merge branch 'master' of github.com:request/request</code></li>
<li><a href="https://urls.greenkeeper.io/request/request/commit/479143d546d6dff378da0e5fac5801dd3bf01f15"><code>479143d</code></a> <code>Update of hawk and qs to latest version (#2751)</code></li>
<li><a href="https://urls.greenkeeper.io/request/request/commit/169be114952d3a769b13e2f321ab5736d69804bc"><code>169be11</code></a> <code>Add Node.js v8 to Travis CI</code></li>
<li><a href="https://urls.greenkeeper.io/request/request/commit/643c43ab7be269a1efaa080ff05a18fff3f64cd7"><code>643c43a</code></a> <code>Fixed some text in README.md (#2658)</code></li>
<li><a href="https://urls.greenkeeper.io/request/request/commit/e8fca511ba2800a809c7759a1c09ea33a440e4fb"><code>e8fca51</code></a> <code>chore(package): update aws-sign2 to version 0.7.0 (#2635)</code></li>
<li><a href="https://urls.greenkeeper.io/request/request/commit/e9992031105190e7a132ab0b5d0876073598db46"><code>e999203</code></a> <code>Update README to simplify & update convenience methods (#2641)</code></li>
<li><a href="https://urls.greenkeeper.io/request/request/commit/6f286c81586a90e6a9d97055f131fdc68e523120"><code>6f286c8</code></a> <code>lint fix, PR from pre-standard was merged with passing tests</code></li>
<li><a href="https://urls.greenkeeper.io/request/request/commit/a76559325fb43adfad26c7c63d8a7c5900b618ef"><code>a765593</code></a> <code>Add convenience method for HTTP OPTIONS (#2541)</code></li>
<li><a href="https://urls.greenkeeper.io/request/request/commit/52d6945858a2d4d1a44f9dd5a8b14f0bb502fb49"><code>52d6945</code></a> <code>Add promise support section to README (#2605)</code></li>
<li><a href="https://urls.greenkeeper.io/request/request/commit/b12a6245d9acdb1e13c6486d427801e123fdafae"><code>b12a624</code></a> <code>refactor(lint): replace eslint with standard (#2579)</code></li>
<li><a href="https://urls.greenkeeper.io/request/request/commit/29a0b172d6f7b5e9f5e344c5758a672e7814d90f"><code>29a0b17</code></a> <code>Merge pull request #2598 from request/greenkeeper-codecov-2.0.2</code></li>
</ul>
<p>There are 27 commits in total.</p>
<p>See the <a href="https://urls.greenkeeper.io/request/request/compare/a0cdc704c19e63e6f1740e173bb003c51eef524c...0ab5c36b6715ae054b8398c80791fdd65be69f72">full diff</a></p>
</details>
<details>
<summary>Not sure how things should work exactly?</summary>
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
</details>
---
Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:
| https://github.com/fastify/fastify/issues/261 | https://github.com/fastify/fastify/pull/2867 | 1941d6ed087f5e0f54a2afb35763e4585b198b80 | d1972a6ba6f06bd462f33dfd7a338eed969b51e5 | "2017-09-20T02:40:47Z" | javascript | "2021-02-22T08:08:43Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 260 | ["package.json"] | Gracefully shutdown | The server should shutdown gracefully that implicit
- Handle SIGINT, SIGTERM
```js
process.on('SIGTERM', function onSigterm () {
// fire onClose hook
// close server
})
``` | https://github.com/fastify/fastify/issues/260 | https://github.com/fastify/fastify/pull/2867 | 1941d6ed087f5e0f54a2afb35763e4585b198b80 | d1972a6ba6f06bd462f33dfd7a338eed969b51e5 | "2017-09-19T23:18:40Z" | javascript | "2021-02-22T08:08:43Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 257 | ["docs/Reply.md", "test/handler-context.test.js"] | Get route options inside handler or inside preHandler hook | Hi,
First of all : great job on this !
Maybe a little feature request : can we have an access to route options inside an handler or inside the preHandler hook ?
Here is a sample code :
```js
fastify.get('/', { foo: 'bar' }, async (req, res) => {
// Something like this ?
const { foo } = req.route;
// foo === 'bar'
});
fastify.addHook('preHandler', (req, res, next) => {
// Or like this ?
const { foo } = req.routeOptions;
// foo === 'bar'
});
```
It can be useful to add some metadatas on routes and read them in hooks, no ?
Thanks ! | https://github.com/fastify/fastify/issues/257 | https://github.com/fastify/fastify/pull/570 | 78daf5345fd5fce3f9015d97a6b7de380eb2493d | ea5bcec7c5875365fea1dbe898dc94cd6acaf778 | "2017-09-19T20:35:40Z" | javascript | "2017-12-21T15:32:19Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 256 | ["README.md", "appveyor.yml"] | Add Windows CI | e.g AppVeyor | https://github.com/fastify/fastify/issues/256 | https://github.com/fastify/fastify/pull/274 | e6fd58b83c6d07c518a879d88491df17e81d89c3 | cbc2557a150796f93d47d78b91b98cee37f42b9b | "2017-09-19T20:01:32Z" | javascript | "2017-09-21T10:16:28Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 251 | ["docs/Logging.md"] | document logging options | https://github.com/fastify/fastify/blob/b29a9e3f2e9f564fb6e4198676c062be7b1ca0bf/fastify.js#L43 is not documented anywhere. | https://github.com/fastify/fastify/issues/251 | https://github.com/fastify/fastify/pull/254 | b659b6d73b1f6580a2555c52b514be4712068d22 | 4d18767ea9b73951ab524dbe1afbe2d8973ca987 | "2017-09-19T15:15:35Z" | javascript | "2017-09-20T09:38:41Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 250 | ["docs/Logging.md"] | remove pino-http from docs | https://github.com/fastify/fastify/blob/master/docs/Logging.md still mentions pino-http | https://github.com/fastify/fastify/issues/250 | https://github.com/fastify/fastify/pull/254 | b659b6d73b1f6580a2555c52b514be4712068d22 | 4d18767ea9b73951ab524dbe1afbe2d8973ca987 | "2017-09-19T15:13:52Z" | javascript | "2017-09-20T09:38:41Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 248 | ["docs/Server-Methods.md", "fastify.js", "test/input-validation.js"] | schemaCompiler api | At the moment the only way to change the `schemaCompiler` function is to assign a new function with
```js
fastify.schemaCompiler = newSchenaCompiler
```
Since all our apis are functions based, we should create an api for this as well to be consistent with our system.
related: https://github.com/fastify/fastify/pull/187
cc @allevo | https://github.com/fastify/fastify/issues/248 | https://github.com/fastify/fastify/pull/253 | d5cbb4d93791e4da0c7606ba07ec589559526081 | 207ad8fd27dd0f4eff2cd0776327327db663e175 | "2017-09-19T14:40:23Z" | javascript | "2017-09-21T06:47:19Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 247 | ["package.json"] | Support async functions as hooks. | As titled. | https://github.com/fastify/fastify/issues/247 | https://github.com/fastify/fastify/pull/2323 | 667d4644eab09f27bc30cad6e7378f5fc82cb9e8 | cfca9198232b9ec833ee05c41501c76238886d70 | "2017-09-19T14:37:09Z" | javascript | "2020-06-08T13:05:08Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 243 | ["fastify.js", "lib/hooks.js", "package.json", "test/close.test.js"] | An in-range update of avvio is breaking the build 🚨 |
## Version **2.1.0** of [avvio](https://github.com/mcollina/avvio) just got published.
<table>
<tr>
<th align=left>
Branch
</th>
<td>
<a href="/fastify/fastify/compare/greenkeeper%2Favvio-2.1.0">Build failing 🚨</a>
</td>
</tr>
<tr>
<th align=left>
Dependency
</td>
<td>
avvio
</td>
</tr>
<tr>
<th align=left>
Current Version
</td>
<td>
2.0.4
</td>
</tr>
<tr>
<th align=left>
Type
</td>
<td>
dependency
</td>
</tr>
</table>
This version is **covered** by your **current version range** and after updating it in your project **the build failed**.
avvio is a direct dependency of this project **this is very likely breaking your project right now**. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:
<details>
<summary>Status Details</summary>
- ❌ **coverage/coveralls** Coverage pending from Coveralls.io [Details](https://coveralls.io/builds/13323486)
- ❌ **continuous-integration/travis-ci/push** The Travis CI build failed [Details](https://travis-ci.org/fastify/fastify/builds/277012379?utm_source=github_status&utm_medium=notification)
</details>
---
<details>
<summary>Release Notes</summary>
<strong>v2.1.0</strong>
<ul>
<li>Updated encapsulation handling for <code>ready</code>, <code>after</code>, <code>onClose</code>, <code>close</code> when a server is given to avvio - <a href="https://urls.greenkeeper.io/mcollina/avvio/pull/23" class="issue-link js-issue-link" data-url="https://github.com/mcollina/avvio/issues/23" data-id="258476822" data-error-text="Failed to load issue title" data-permission-text="Issue title is private">#23</a></li>
</ul>
</details>
<details>
<summary>Commits</summary>
<p>The new version differs by 11 commits.</p>
<ul>
<li><a href="https://urls.greenkeeper.io/mcollina/avvio/commit/28e0d460716a15a2b89cd495a79ee65fff5cc3db"><code>28e0d46</code></a> <code>Bumped v2.1.0</code></li>
<li><a href="https://urls.greenkeeper.io/mcollina/avvio/commit/49c88737127f067bbb3c1df5b1a6fec7dd261ac3"><code>49c8873</code></a> <code>Merge pull request #23 from mcollina/ready-close-context</code></li>
<li><a href="https://urls.greenkeeper.io/mcollina/avvio/commit/f1b6860c3a5d5d153804530fee5c35f26edfeb33"><code>f1b6860</code></a> <code>Updated docs</code></li>
<li><a href="https://urls.greenkeeper.io/mcollina/avvio/commit/99b87af44fd389d2aa43ba753ed28c358c966e43"><code>99b87af</code></a> <code>Updated function signature</code></li>
<li><a href="https://urls.greenkeeper.io/mcollina/avvio/commit/f6b6ec9be9a5a1b3dbd962714b792ede8aca48e2"><code>f6b6ec9</code></a> <code>Updated docs</code></li>
<li><a href="https://urls.greenkeeper.io/mcollina/avvio/commit/3314f8439f32a32db04d589d52cc5f94bbe8b9a1"><code>3314f84</code></a> <code>Updated test</code></li>
<li><a href="https://urls.greenkeeper.io/mcollina/avvio/commit/a1c88268e7c4a3e6d03a0c0f9b0036c3eb08cb19"><code>a1c8826</code></a> <code>Provide encapsulation only if initialized with a server</code></li>
<li><a href="https://urls.greenkeeper.io/mcollina/avvio/commit/a87421e03388f6af791406d775c9c5328b17b40d"><code>a87421e</code></a> <code>Updated encapsulate functions</code></li>
<li><a href="https://urls.greenkeeper.io/mcollina/avvio/commit/ca9ada9803feb09105e8c8ba390ba305966a82f0"><code>ca9ada9</code></a> <code>Updated test</code></li>
<li><a href="https://urls.greenkeeper.io/mcollina/avvio/commit/77a1244843c572968d9db14c3dcaeb7211ce77cc"><code>77a1244</code></a> <code>Updated encapsulation handling</code></li>
<li><a href="https://urls.greenkeeper.io/mcollina/avvio/commit/968eedbcc140bcc7f7e49f3de5754c7b23ec77d2"><code>968eedb</code></a> <code>Updated .gitignore</code></li>
</ul>
<p>See the <a href="https://urls.greenkeeper.io/mcollina/avvio/compare/7549f8a779e34f10364d34f1c0b9bd76a07bda7a...28e0d460716a15a2b89cd495a79ee65fff5cc3db">full diff</a></p>
</details>
<details>
<summary>Not sure how things should work exactly?</summary>
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
</details>
---
Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:
| https://github.com/fastify/fastify/issues/243 | https://github.com/fastify/fastify/pull/244 | 66e14852d3e2c4918e2465453e2b446a399cfc41 | ddd9c170944e1763a629defab8f11ccfb772d54a | "2017-09-18T20:14:53Z" | javascript | "2017-09-18T22:58:21Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 238 | ["docs/Getting-Started.md", "docs/Reply.md", "docs/Routes.md", "lib/handleRequest.js", "lib/reply.js", "test/async-await.js", "test/logger.test.js", "test/promises.test.js"] | async + reply.send | Hi,
this handle responses always empty body with 200 status code
```js
fastify.get('/', async (req, reply) => {
reply.send({})
})
```
Maybe we need to figure out how to report (or throw an exception)
I lost 30minutes last time... 😢 | https://github.com/fastify/fastify/issues/238 | https://github.com/fastify/fastify/pull/241 | 43436c28c69c3c26e7e3143c56ba755e9f142892 | 18b5992e371c910d2989c1574b61bc03a84f370b | "2017-09-17T22:00:03Z" | javascript | "2017-09-19T14:16:48Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 237 | ["fastify.js", "lib/hooks.js", "package.json", "test/close.test.js"] | Problem encapsulation during close | Hi,
I have encountered a bug in encapsulation during the [fastify-example-twitter](https://github.com/fastify/fastify-example-twitter) development. My code is like this:
```js
'use strict'
const fastify = require('fastify')()
const fp = require('fastify-plugin')
const fm = require('fastify-mongodb')
fastify.register(function(f, o, done) {
f.register(fm, { url: 'mongodb://localhost/yyy' }, err => {
if(err) return done(err)
fastify.get('/', (req, reply) => reply.send({}))
done()
})
})
fastify.listen(3008, err => {
console.log('fastify is up!', err)
setTimeout(() => {
console.log('closing...')
fastify.close(err => {
console.log('closed', err)
})
}, 1000)
})
```
`fastify-mongodb` plugin [registers an `onClose` hook](https://github.com/fastify/fastify-mongodb/blob/master/index.js#L25)
When `fastify` is going to shut down, the plugin refers to the decorators that has set for the cleaning up. But it seems that there the fastify instance is not the instance used in the start up!
In fact the script exits with a non-0 code and prints this error:
```
/Users/allevo/repos/fastify-example-twitter/server/node_modules/fastify-mongodb/index.js:32
fastify.mongo.db.close(done)
^
TypeError: Cannot read property 'db' of undefined
at close (/Users/allevo/repos/fastify-example-twitter/server/node_modules/fastify-mongodb/index.js:32:16)
at Boot.closeWithCbOrNextTick (/Users/allevo/repos/fastify-example-twitter/server/node_modules/avvio/boot.js:239:7)
at release (/Users/allevo/repos/fastify-example-twitter/server/node_modules/fastq/queue.js:127:16)
at Object.resume (/Users/allevo/repos/fastify-example-twitter/server/node_modules/fastq/queue.js:61:7)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
``` | https://github.com/fastify/fastify/issues/237 | https://github.com/fastify/fastify/pull/244 | 66e14852d3e2c4918e2465453e2b446a399cfc41 | ddd9c170944e1763a629defab8f11ccfb772d54a | "2017-09-17T21:51:19Z" | javascript | "2017-09-18T22:58:21Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 214 | [".github/workflows/links-check.yml"] | "http-method-override" header | Because of https://github.com/fastify/fastify/pull/170, no hooks are fired before routing.
Unfortunately an API that allows the `http-method-ovveride` header to override the http method should replace the `method` request property with the header value. See [method-override](https://github.com/expressjs/method-override) for an example
How we can handle this?
Maybe a `prepareRequest` method can be useful :fearful:
@mcollina @delvedor thoughts? | https://github.com/fastify/fastify/issues/214 | https://github.com/fastify/fastify/pull/5300 | 5fe74e58de4de685283794c9e520ef800d5f6f59 | 37b9b3d947d79ae8e5d26e62b9a4b11fb9812c75 | "2017-09-12T21:26:26Z" | javascript | "2024-02-01T14:34:24Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 212 | ["fastify.js", "test/listen.test.js", "test/route.test.js"] | HTTP server errors not surfaced | Errors emitted by the HTTP server aren't passed to the listen callback, I understand that you can access the `server` property but surely we can do better here? :)
```javascript
'use strict'
const fastify = require('fastify')
const s1 = fastify()
const s2 = fastify()
s1.listen(3000)
s2.listen(3000, err => {
console.error(err) // no exception
})
s2.server.on('error', err => {
console.error(err) // listen EADDRINUSE :::3000
})
``` | https://github.com/fastify/fastify/issues/212 | https://github.com/fastify/fastify/pull/215 | 7a9dfebf3b26a610a2a69e13069100d51f5b7fdc | db00917fee9e1ba9d95e9af4bb80ad95ffa79188 | "2017-09-12T17:43:06Z" | javascript | "2017-09-12T22:22:35Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 179 | ["test/listen.test.js"] | Will it listen on socket, not port? | Something similar to
```javascript
fastify.listen('./www/app.sock', function (err) {
if (err) throw err
console.log(`server listening on ${fastify.server.address().port}`)
})
```
I mean, node's ``http`` and ``https`` are able to work with sockets. But is ``fastify`` handle routing and other functionality over socket correctly? | https://github.com/fastify/fastify/issues/179 | https://github.com/fastify/fastify/pull/259 | 29d0bdf9f6fd0013ce51e7cfed35f262cfb5ed47 | b3dc5d98aa54c031595858c9c34957ce24f3b301 | "2017-09-08T09:23:49Z" | javascript | "2017-09-20T15:13:10Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 135 | ["docs/Server-Methods.md", "fastify.js", "lib/reply.js", "package.json", "test/404s.test.js", "test/500s.test.js", "test/middleware.test.js", "test/plugin.test.js"] | Custom routes for 404 and 500 | As titled, we should be able to make these customizable, ideally supporting the plugin encapsulation. | https://github.com/fastify/fastify/issues/135 | https://github.com/fastify/fastify/pull/266 | 2cb7efbe263a2f40429fbdb837f327698036a6f8 | 4f4e6d77978d509b0a9f98143120a8a3ee72d5e4 | "2017-07-17T06:53:57Z" | javascript | "2017-09-25T12:53:22Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 104 | ["package.json"] | An in-range update of ajv is breaking the build 🚨 |
## Version **5.1.6** of [ajv](https://github.com/epoberezkin/ajv) just got published.
<table>
<tr>
<th align=left>
Branch
</th>
<td>
<a href="/fastify/fastify/compare/greenkeeper%2Fajv-5.1.6">Build failing 🚨</a>
</td>
</tr>
<tr>
<th align=left>
Dependency
</td>
<td>
ajv
</td>
</tr>
<tr>
<th align=left>
Current Version
</td>
<td>
5.1.5
</td>
</tr>
<tr>
<th align=left>
Type
</td>
<td>
dependency
</td>
</tr>
</table>
This version is **covered** by your **current version range** and after updating it in your project **the build failed**.
ajv is a direct dependency of this project **this is very likely breaking your project right now**. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this :muscle:
<details>
<summary>Status Details</summary>
- ❌ **coverage/coveralls** Coverage pending from Coveralls.io [Details](https://coveralls.io/builds/11995398)
- ❌ **continuous-integration/travis-ci/push** The Travis CI build could not complete due to an error [Details](https://travis-ci.org/fastify/fastify/builds/243460172?utm_source=github_status&utm_medium=notification)
</details>
---
<details>
<summary>Commits</summary>
<p>The new version differs by 8 commits.</p>
<ul>
<li><a href="https://urls.greenkeeper.io/epoberezkin/ajv/commit/ff9f93a71282a7e8a6a71409dd325660730ec765"><code>ff9f93a</code></a> <code>5.1.6</code></li>
<li><a href="https://urls.greenkeeper.io/epoberezkin/ajv/commit/0d6ae42c0f38e09a406b73dc80889bd279cf8038"><code>0d6ae42</code></a> <code>fix: traverse only schema objects, fixes #521</code></li>
<li><a href="https://urls.greenkeeper.io/epoberezkin/ajv/commit/daf7d6b7b0a7a43c47741b4f5cf461c17f5a6382"><code>daf7d6b</code></a> <code>docs: using with draft-04</code></li>
<li><a href="https://urls.greenkeeper.io/epoberezkin/ajv/commit/9f0b563d3f87384e758c74bb35f05f29df8408bb"><code>9f0b563</code></a> <code>Merge pull request #508 from epoberezkin/greenkeeper/nyc-11.0.2</code></li>
<li><a href="https://urls.greenkeeper.io/epoberezkin/ajv/commit/55727d9f13222d4c2b09445e74a3483e62683df8"><code>55727d9</code></a> <code>test: remove node v0.12, v5, add v8 to travis test</code></li>
<li><a href="https://urls.greenkeeper.io/epoberezkin/ajv/commit/eac59028ccfdbd39940eae28ed8c72ea6f455397"><code>eac5902</code></a> <code>chore(package): update nyc to version 11.0.2</code></li>
<li><a href="https://urls.greenkeeper.io/epoberezkin/ajv/commit/f1c9f15ea800bd84e23a57e8c30edcd48f60d682"><code>f1c9f15</code></a> <code>Merge pull request #507 from epoberezkin/greenkeeper/chai-4.0.1</code></li>
<li><a href="https://urls.greenkeeper.io/epoberezkin/ajv/commit/d74a381ed8152d35b46429e4446c128d6176d6df"><code>d74a381</code></a> <code>chore(package): update chai to version 4.0.1</code></li>
</ul>
<p>See the <a href="https://urls.greenkeeper.io/epoberezkin/ajv/compare/526baa57ad0eed295f9571cf0ee84da5847095d3...ff9f93a71282a7e8a6a71409dd325660730ec765">full diff</a></p>
</details>
<details>
<summary>Not sure how things should work exactly?</summary>
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).
</details>
---
Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:
| https://github.com/fastify/fastify/issues/104 | https://github.com/fastify/fastify/pull/4581 | c6a40ebe3ec9aaa2886d8ba7646fea88559412f6 | 2e9526e6245421570a5ef54d3676421f617dc4d7 | "2017-06-15T22:51:03Z" | javascript | "2023-02-13T15:35:50Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 84 | ["package.json"] | Out schema for non 2xx response | Currently the out schema is applied to every response.
Is there a way to set a "global" out schema for all non 2xx request?
Or apply the out schema only to the 2xx response?
Any suggestions? | https://github.com/fastify/fastify/issues/84 | https://github.com/fastify/fastify/pull/4694 | 3ef63afbb71b2ebda1bc1c2080bc1130e31dbaa7 | 2e9b31952e727cca78b06f65af4a8cc7f56bc609 | "2017-05-12T17:02:15Z" | javascript | "2023-04-25T16:29:30Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 55 | ["lib/contentTypeParser.js", "package.json"] | Serving static files | I haven't found any documentation about serving static files, then @mcollina put me on the right path suggesting to try a middleware for it.
[Express serve-static](https://github.com/expressjs/serve-static) works like a charm to map a folder to `/`:
```js
fastify.use(serveStatic(`${__dirname}/public`))
```
```sh
> curl http://localhost:8888/index.html
<html>
<head><title>public/index.html</title></head>
<body>Hello world!</body>
</html>
```
but I couldn't find a way to map a path to the public folder.
If I wanted to do the same on Express I would have something on the lines of
```js
app.use('/assets', serveStatic(`${__dirname}/dist`))
```
It would be a nice addition | https://github.com/fastify/fastify/issues/55 | https://github.com/fastify/fastify/pull/4305 | aacd099f3e71308dff86059b86500cd65673ce97 | 3dd23fec705c6d2662fbf4fdf1dfc1480fa03793 | "2017-03-21T16:20:28Z" | javascript | "2022-09-30T16:24:34Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 51 | ["lib/contentTypeParser.js", "package.json"] | 'use string' typo | See here https://github.com/fastify/fastify/blob/master/benchmarks/koa.js#L1 | https://github.com/fastify/fastify/issues/51 | https://github.com/fastify/fastify/pull/4305 | aacd099f3e71308dff86059b86500cd65673ce97 | 3dd23fec705c6d2662fbf4fdf1dfc1480fa03793 | "2017-03-16T19:40:17Z" | javascript | "2022-09-30T16:24:34Z" |
closed | fastify/fastify | https://github.com/fastify/fastify | 32 | [".github/workflows/integration.yml", ".github/workflows/package-manager-ci.yml"] | Multiple response types | Is there a way to define multiple response types? For example a route response my have a different structure for a success/error response.
I have a route that returns an array of objects on success, but an error object on failure. | https://github.com/fastify/fastify/issues/32 | https://github.com/fastify/fastify/pull/5341 | ef3a755b058f70e3a6e56a5d53a73e6c715550cd | 8345c9bfb13a78ba0268ed06bd886d0a2a70df59 | "2016-12-22T18:18:34Z" | javascript | "2024-03-01T14:23:10Z" |