I'm getting a fatal error during the latest Webcore HPM update (1.0.88). Despite following the instructions to reboot the hub prior to updating, it rolls back during the update, then the hub load starts reporting as severe.
Any ideas what's going on with it? How do I get it installed? Or is it better to skip this update and wait for a resolution?
This is a known issue that is being looked at. The webCoRE Piston app has grown in size to the point that the update is timing out. If you need to update, manually import the code for each webCoRE app, unmatch webCoRE in HPM and then re-Match clicking the assume code is current box.
I think I might be confused a bit. I thought WebCore was now a built in app for HE.
I installed it via the Apps page.
I don't see any Webcore apps on the app code page.
Thanks
It is both. Community version may receive an update a little sooner but for the most part they are the same. Community version exists to support those that at were using it prior to it moving to built-in. Built-in version is not subject to the update timeouts when upgrading.
When trying to update the piston code it just seems to keep continuously loading when I hit the save button after importing. Any idea why this would happen?
The piston code is the largest of the webCoRE application. It takes a long time to load. That's the reason why it fails when trying to install via HPM (it's timing out) and why it takes so long when installing it manually. It takes in excess of 7 minutes - probably longer, I haven't actually timed it, to load the 'Piston' code. Give it more time to complete. If it never completes, that's a different issue.
I still can't update this via HPM, it fails every time. Is it now just broken basically and the only way is to update the code manually? I'm just nervous about doing it that way in case I mess something up...
The piston code is currently too large to run through HPM, but as long as you edit, import and save the following, preferably in the order listed, you won't have a problem:
body - The body of the request as a String. Any encoding should be done before passing to the system.
params - the parameters to use to build the http call. Possible values:
uri - The uri to send the request to
queryString - The raw, already-escaped query string.
query - Add these parameters to the existing query string. If any of the parameters already exist in the query, these values will not replace them. Multiple values for the same query parameter may be added by putting them in a list.
headers - Request headers
path - The path component of this request. The value may be absolute or relative to the current path.
contentType - The content-type used for any data in the request body, as well as the Accept content-type that will be used for parsing the response.
requestContentType - Assign a different content-type for the request than is expected for the response.
body - The request body. If this is a Map or Array, the system will take care of encoding it based on the requestContentType.
timeout(since 2.0.9) - timeout in seconds for the request, max timeout is 300