Skip to content

Conversation

@srpurani
Copy link
Member

@srpurani srpurani commented Mar 4, 2020

  • FDK should log before and after a call completes. This is achieved by adding log lines to handleRequest.
  • The boilerplate code in the init image should have a log message printed to serve as an example.

 * FDK should log before and after a call completes. This is achieved by adding log lines to handleRequest.
 * The boilerplate code in the init image should have a log message printed to serve as an example.
defer cancel()

logFrameHeader(r)
log.Println("Request started")
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think log.Println flushes, is this a problem? (I can see it might be, if the customer's trying to figure out why there code isn't running, but maybe it's out of scope for this change?)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It appears to flush, I think the problem was in Python fdk iirc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants