Cloud pubsub emulator does not handle 202 response code correctly on push endpoints.
Small discrepancy between the emulator and the production Cloud Pub/Sub.
When responding to a push subscription with http code 202 the emulator will output the following message:
[pubsub] INFO: Failed to push to endpoint '<endpoint here>': Fetched url '<url here>' but got a response code that is not an acknowledgement: 202
Whereas per existing Cloud Pub/Sub documentation this should be considered a valid ack response for push endpoints:
(I haven't explicitely tested other response codes but I'm fairly certain that 204 and 200 are correctly handled, didn't test 201 and 102.)