Details
Critical Description
When creating a new Eventing function via the UI in macOS a problem is preventing Eventing functions from being created or imported.
New function made in the UI Case 1 (no edit to Javascript)
Accepting the "default" Javascript code for the function (no edits) somehow the function doesn't actually get saved,
After returning to the Eventing page we see a status '...' indicating unknown
And then eventually due to the new resyncing logic between UI's CLI and REST commands in 10 "status" updates it is removed from the UI (since it was not saved in the 'backend')
Note the functionality in Linux works fine.
+New function made in the UI Case 2 (edit to JavaScript)+
Modifying the "default" Javascript code for the function (just add a space) the function does get saved.
After returning to the Eventing page we see a status 'undeployed'
In this case the resyncing logic allows it to stay in the UI.
However it can not be deployed via the UI's "deploy" button (refer to case-2_issues.png)
Note the functionality in Linux works fine.
+Importing a function via the UI Case 3+
Similar behavior to case 1 above.
Note the functionality in Linux works fine.
Other
I have added all the log files and attached via "logs.tar.gz"
