rodric rabbah
rodric rabbah
The current implementation doesn’t persist a message that’s undergoing a retry. If we extend this to 24hrs say the message has to be persisted otherwise the provider risks losing it....
Won't we end up re-engineering this provider? In other words, we should funnel all events through the kafka provider and have a single place for dealing with backoff/retry policies, etc....
@maximann fork the repo, then you can create branches in your own fork, and submit a pull request.
Any reason not to run as python 3? Could normalize utf8 string handling.
yes i think we should remove them.
The status code you return for a web action is not the same as the status code that is generated by the system and part of the response object. The...
From: https://github.com/apache/openwhisk/blob/b00678d30604d0ffb45792fdcd4b61714cfffd1c/common/scala/src/main/scala/org/apache/openwhisk/core/entity/ActivationResult.scala#L36-L45 The `statusCode` is removed from the activation result. This is a CLI bug.
https://github.com/apache/openwhisk-client-go/blob/49c58e00354d315ce82766c785c69193df0514e8/whisk/activation.go#L59 The Go serialization is assuming the field is present and when it is not it default to 0. It's a bug in that library (ugh https://github.com/apache/openwhisk-cli/issues/148).
I'm curious, @ShubhamGupta9582 are you trying to modify the CLI to report the web action status code? What you ran into is clearly a bug that should be fixed in...
The fields are hard coded and called “x-ibm-...“ as in: `x-ibm-configuration` `x-ibm-rate-limit`