Carlos Fuentes
Carlos Fuentes
Can you paste the errors you faced?
Maybe you can try to isolate a single test and see what might be wrong. See [tap#only](https://node-tap.org/docs/api/only/)
I've been digging into this lately, and I've seen a similar pattern when you error within your `onSend` hook. Fastify handles the error, but re-calls the same hook once more,...
>So basically, this bug happens when the error is happening at or after the onSend lifecycle stage?! At ```js 'use strict' const fastify = require('.')() fastify.addHook('onSend', (req, reply, payload, done)...
Hey! Each Cloud Function has a unique URI, for instance, you can already achieve what you are looking for, though the trick is how to use the `functions-framework` to allow...
Thanks for the clarification, I see what you mean now 🤔 The only way to achieve that I can think of is to use the [lazy local-variable initialization strategy](https://firebase.google.com/docs/functions/tips#do_lazy_initialization_of_global_variables). By...
>functionNames.txt Not so sure where this fits exactly, but the rest LGTM 👍
Would you like to contribute by adding your findings and results to Fastify's documentation?
>Apart from charset the only other parameter which could occur in the content-type header would be boundary=, I think? Which presumably would be case sensitive, but which wouldn't matter for...
Oh, sorry I didn't explain myself correctly, didn't mean like properly sync and find a solution 😅 I was referring to just handling the type, subtype, and parameters case scenario...