-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Description
Environment details:
Go CLI binary installed locally.
whisk CLI version 2016-10-11T11:00:00+00:00
whisk API build 2016-10-18T16:51:12Z
whisk API build number whisk-build-1201-accelerate
Steps to reproduce the issue:
Start the activation logs polling using this command.
wsk -v activation poll
...then invoke an action.
The URL for retrieving the activation logs does not update the "since" parameter to the start from the invoked activation "start" time. It is still asking for all logs since polling started.
According to @rabbah the maximum number of activations returned is two hundred. Once that number of activations has been recorded in the system, no new activations will come through in the API response.
Looking at the code, should the since parameter be pulled from the activations returned here:
https://github.com/openwhisk/openwhisk/blob/master/tools/cli/go-whisk-cli/commands/activation.go#L310-L320
This was the behaviour in the previous Python CLI.
According to @rabbah due to the "eventual consistency" model for the system, activations may be recorded after API response is returned that occurred BEFORE the response's final activation start time". If that last time is used as the since parameter, those logs will never be displayed. The client could handle this by setting the since to to the last activation start time minus a fixed offset.