Genevieve L'Esperance

+1 To this. It would be great if image/build status conditions contained a message or reason with some description of the failure for faster debugging on easily-identifiable failures. https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#typical-status-properties Slack...

This is a great idea! Would this look like a new field on the Image or Build resource that points to a url for a specified `project.toml` that is separate...

Which `crane` are you referring to ? I tried with a different image to a different registry and on the first run it failed but the second it succeeded. The...

Ya wanna make a PR or are you noting this for the other repo?

Do you want to make this a var that defaults to `pcf-optional` but we can overwrite to `initial` using the var?

Hey @arctica. Since you have a reproduction, have you been able to test the changes you've proposed to v8go to see if any resolve the issue?

@arctica Yes! We'd be interested in seeing your implementation if you're able to publish it.

Yes, you're correct it would be great to have the other supported attributes exposed in the library. It was a TODO on the original PR that added the profiler: https://github.com/rogchap/v8go/pull/167....

The changes look good. 1. Could you update the changelog to reflect these two new functions on nodes? 2. Are there test assertions in the node suite that could cover...

You may be able to pass in the actual function from the function template with: ```go if err := info.This().Object().Set("hello", fn.GetFunction(info.Context())); err != nil { ```