there is no uploaded file i.e. all bits already in the resources pool. Change-Id: I9b4e0396b0461cc6bcc084dfec37f36a0b7517d2
…riority queue that prevents duplicate entries. This is combination of multiple commits that includes implementation of the PriorityQueue, PrioritySet with optional key object."
… queue that prevents duplicate entries. This is combination of multiple commits that includes implementation of the PriorityQueue, PrioritySet with optional key object. Change-Id: I7124d04ad1483b7ead44712a6221f6c636260700
- expose 'top' var which holds request-per-second stats for all apps - add expose_all_apps config parameter which determines if we expose rps stats for all apps Change-Id: Id66f92c66bbe500c9977f606f86346a1d287aa4b
Logging these clogs up our logs and provides little value as we've either 1) already logged the error condition that caused us to throw the CloudError, or 2) already logged the error due to an unhandled exception. Test plan: - None :O Change-Id: Iba4e79c6069e708d341d75291145a8dd359cba3b
This diff attempts to provide more robust error handling around all stages of app packaging. App packaging failures should now be propagated back to the user instead of being silently ignored. Specifically, we do the following: - Raise an instance of AppPackageError if the initial unpacking of the application fails for any reason. - Raise an instance of AppPackageError if any stage of resource pool synchronization fails. We replace VCAP.defer with a method that defers the computation and propagates exceptions back to the calling fiber. - Raise an instance of AppPackageError if the final repacking of the application fails. The specific errors are caught and logged (along with backtraces) before wrapping them in AppPackageErrors. Test plan: - New unit tests pass - BVTs pass - Deployed the sample node app with symlinks outside the app directory. Now fails with "Error 402: App packaging failed: 'Failed synchronizing resource pool'" Change-Id: I5367ae196408851a9f5bd72b0f8cb994c7e23931
Test plan: - Unit tests pass - Bumped timeout in config, verified with long running staging app Change-Id: Id71825a11436f55cafe9ff8768a0ed976151fea3
If the ENV variable CLOUD_FOUNDRY_CONFIG_PATH is defined, config files are picked up from that location. This allows components installed by the chef scripts to be run by hand. i.e. without using the wrapper vcap/dev_setup/bin/vcap_dev <start/stop> Change-Id: Ib6c971c6642bcb3b24186169e1c768ee70ba8d7b