Testing failed deliveries

[jyasskin]

I'd like to have my app follow the GH best practice of checking for failed deliveries and asking for them to be redelivered, but it's hard to test that using Smee because smee.io always returns a 200 response code. Might it be possible to have smee.io return an error code if no client is connected to the channel?

[wolfy1339]

Can you share more details? What url are you looking at?

It wouldn't make much sense to respond with anything other than 200 for the web page (browser interface), as all the data loaded successfully.

Also note that smee isn't meant to be used for production use, it's meant to help during development.

[jyasskin]

Ultimately, I'm hoping to cause a page like https://github.com/settings/apps/<app-name-here>/advanced to show a failed delivery so that I can then locally test the app's recovery logic that asks github to try to re-deliver that delivery. One way to accomplish this is to change the app's Webhook URL to a non-existent URL. If you don't think there's a reasonable way to get smee to cause deliveries to fail, I'll wind up using that.

I was imagining that there could be some way to configure a smee channel so that when github posts to it, it returns a failure code instead of a 200. I think the 200 is happening at

smee.io/lib/server.js

Line 327 in 922d925

return reply.status(200).send()

I had guessed that the configuration could happen just by whether anything was subscribed to the channel, but the Redis layer of indirection might make that difficult.