vania-janet/multiturn-rag-retrieval-data huggingface dataset:
: The following updates are included in this release:



* Add support for running pre and post compile scripts using NPM and Bower to install front-end JavaScript and CSS libraries.
* Move buildpack from Beta status to GA status







 26 August 2016 

Updated Liberty buildpack v3.2-20160822-2200
: The buildpack contains updated versions of IBM JRE: 8 SR3 FP10 and 7.1 SR3 FP50.



* The monthly Liberty runtime version was updated to the [2016.8.0.0](https://developer.ibm.com/wasdev/blog/2016/07/28/beta-websphere-liberty-and-tools-august-2016/) release.
* The service plug-in that provides auto-configuration support for the SQL Database service was updated to always use the JVM's trusted certificates when connecting to the service over TLS.



Updated Node.js buildpack v3.7-20160826-1101
: This release of the buildpack supports IBM SDK for Node.js runtime versions: 0.10.45, 0.10.46, 0.12.14, 0.12.15, 4.4.7, 4.5.0, 6.2.2, and 6.4.0. The default is now 4.5.0.

This release includes bug fixes, including those from the [Cloud Foundry’s Node.js buildpack 1.5.18](https://github.com/cloudfoundry/nodejs-buildpack/tree/v1.5.18).

The release removes support for the strongpm App Management handler as announced in [IBM Cloud Node.js Buildpack v3.3 – FIPS mode and more](https://www.ibm.com/blogs/cloud-archive/2016/05/node-buildpack-update-fips-mode/).

Note that there is a known issue when using Node.js 6.x and Development Mode. As a work around you will need to restage your app after enabling Development Mode before you can begin using it.





 22 July 2016
* Return - A collection of type SoftLayer_Container_Network_CdnMarketplace_Configuration_Mapping_Path.

[Origin path container](https://cloud.ibm.com/docs/CDN?topic=CDN-path-origin-container)



--------------------





 deleteOriginPath 

Deletes and existing origin path for an existing CDN, and for a particular customer. To be deleted, the domain mapping must be in either a RUNNING or CNAME_CONFIGURATION state.



* Parameters:



* uniqueId- (Required) The unique ID of the mapping to which this origin path belongs.
* path- (Required) Path to be deleted.



* Return - A status message if the delete was successful, otherwise an exception is thrown.



--------------------





 listOriginPath 

Lists the origin paths for an existing mapping based on the uniqueId.



* Parameters:



* uniqueId- (Required) Provide the unique ID of the mapping for which you want to list origin paths.



* Return - A collection of objects of type SoftLayer_Container_Network_CdnMarketplace_Configuration_Mapping_Path.

[Origin path container](https://cloud.ibm.com/docs/CDN?topic=CDN-path-origin-container)



--------------------







 API for Multiple File Purge 



 createPurgeGroup 

Creates a purge group. A purge group contains multiple file paths and allows you to purge all of these files in one API call. You can save a purge group to be a favorite (permanent) group or not. For more information, see [With multiple file purges, what's the difference between a favorite group and an unfavorite group?](https://cloud.ibm.com/docs/CDN?topic=CDN-faqswhat-different-two-type-favorite-group).

There's also a rate limit to the purge actions.
For more information, see [Understanding customization](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-customIntro).

Voices updated for improved speech synthesis
: The service features improved expressiveness and naturalness for the most frequently used voices. The improvements are based on Recursive Neural Network (RNN)-based prosody prediction from input text. They are made available as a new service engine and voice-model updates for the following languages:



* en-US_AllisonVoice
* en-US_LisaVoice
* en-US_MichaelVoice
* es-ES_EnriqueVoice
* fr-FR_ReneeVoice



New customization ID parameter for word pronunciation
: The GET /v1/pronunciation method now accepts an optional customization_id query parameter. The parameter obtains a word translation from a specified custom model. If the custom model does not contain the word, the method returns the word's default pronunciation. For more information, see the [API & SDK reference](https://cloud.ibm.com/apidocs/text-to-speech).

When using the GET /v1/pronunciation method without a customization ID and for a language other than US English, you can request a word's pronunciation only in IBM SPR notation. For a language other than US English, you must specify spr with the method's format option.

New support for audio/basic audio format
: The list of supported audio formats now includes audio/basic, which provides single-channel audio that is encoded using 8-bit u-law (or mu-law) data that is sampled at 8 kHz. For more information, see [Using audio formats](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-audio-formats).

HTTP and WebSocket interfaces can now return warnings
: The HTTP and WebSocket /v1/synthesize methods can return a warnings response that includes messages about invalid query parameters or JSON fields that are included with a request. The format of the warnings changed. The following example shows the previous format:
: This release of the buildpack supports IBM SDK for Node.js runtime versions: 0.10.47, 0.10.48, 0.12.16, 0.12.17, 4.6.1, 4.6.2, 6.7.0, and 6.9.1. The default is now 4.6.2.

Note that Node.js v6 was promoted to LTS status on October 18, 2016 and will soon become the buildpack's default runtime. Node.js v0.10 reached end of life on October 31, 2016 and will soon no longer be included in the buildpack. See [Node.js version long-term support and the SDK for Node.js buildpack](https://www.ibm.com/blogs/bluemix/2016/11/node-version-support-and-sdk-buildpack/) for more details.

Bugs affecting the trace and inspector App Management handlers, when used in conjunction with Node.js v6, have been addressed in this release. See [Managing Liberty and Node.js apps](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-app_management) for more information about how the inspector handler is changing now that Node.js v6 has integrated the inspector capability.





 1 November 2016 

Updated Liberty buildpack v3.4.1-20161030-2241
: The buildpack contains a fix for a problem starting certain types of apps. Specifically, apps deployed as a server directory or a packaged server with the app files in the dropins directory.





 21 October 2016 

Updated Liberty buildpack v3.4-20161018-2004
: The default Liberty runtime version 16.0.0.3 was updated to include [PI68805](https://www.ibm.com/support/pages/apar/PI68805) and [PI69141](https://www.ibm.com/support/pages/apar/PI69141) fixes.
{ "Key": "deletetest/testfile3.txt" },
{ "Key": "deletetest/testfile4.txt" },
{ "Key": "deletetest/testfile5.txt" }
]
}
return cos.deleteObjects({
Bucket: bucketName,
Delete: deleteRequest
}).promise()
.then((data) => {
console.log(Deleted items for ${bucketName});
console.log(data.Deleted);
})
.catch((e) => {
console.log(ERROR: ${e.code} - ${e.message}n);
});
}
Show more

SDK References



* [deleteObjects](https://ibm.github.io/ibm-cos-sdk-js/AWS/S3.htmldeleteObjects-property)







 Delete a bucket 

function deleteBucket(bucketName) {
console.log(Deleting bucket: ${bucketName});
return cos.deleteBucket({
Bucket: bucketName
}).promise()
.then(() => {
console.log(Bucket: ${bucketName} deleted!);
})
.catch((e) => {
console.error(ERROR: ${e.code} - ${e.message}n);
});
}

SDK References



* [deleteBucket](https://ibm.github.io/ibm-cos-sdk-js/AWS/S3.htmldeleteBucket-property)







 Execute a multi-part upload 

function multiPartUpload(bucketName, itemName, filePath) {
var uploadID = null;

if (!fs.existsSync(filePath)) {
Your access groups can be found by clicking Access groups in the Manage access section of the left navigation.
6. From the list of services, select Key Protect and click Next to open the Resources section.
7. In the Resources section, use the radio buttons to select whether you assign access over all resources or only specific resources. If you select Specific resources you are asked to provide an Attribute type (for example, a Key ring ID, where the string equals the ID). The Add a condition box allows you add more attributes to the policy you create in the next step. When you are ready, click Next to create the policy. Note that you can click Edit if you want to go back to the list of services.
8. In the Roles and access section, you can assign access over the resources you have selected. For more information about the difference between Service access roles and Platform access roles, check out [Platform roles and service roles](https://cloud.ibm.com/docs/key-protect?topic=key-protect-manage-accessmanage-access-roles). The box to the right of the selection options dynamically updates to provide a summary of the access that would be assigned if the selected options are kept. Review the provided list of access carefully. Note that a JSON version of the policy can be viewed (and copied) by clicking JSON in the tab marked [UI|JSON] to the right of the Create policy header.
9. When you are satisfied with your policy, click Add. This creates the selected policy over the selected resources. The Access summary column shows the created policy. If there is an error, you can Remove or Edit the access in this section.







 Granting access to a single key in an instance 

Calling the [list keys API](https://cloud.ibm.com/apidocs/key-protectgetkeys) will not return keys that you have assigned individual access to (that only you can access, in other words, even if you have the access over those keys and you are the one making the call). Calling this API will, however, return the keys in key rings you have access to.
C_SignFinal* m_SignFinal SignFinal Finishes a multiple-part signature operation. 
 C_SignRecoverInit N/A N/A Initializes a signature operation, where the data is recovered from the signature. 
 C_SignRecover N/A N/A Signs single-part data, where the data is recovered from the signature. 
 N/A m_SignSingle SignSingle IBM extension, nonstandard extension, combination of SignInit and Sign. Signs or MACs data in one pass, with one call, without constructing intermediate digest state. Does not return any state to host other than the result. 
 C_VerifyInit* m_VerifyInit VerifyInit Initializes a verification operation. 
 C_Verify* m_Verify Verify Verifies a signature on single-part data. 
 C_VerifyUpdate* m_VerifyUpdate VerifyUpdate Continues a multiple-part verification operation. 
 C_VerifyFinal* m_VerifyFinal VerifyFinal Finishes a multiple-part verification operation. 
 C_VerifyRecoverInit N/A N/A Initializes a verification operation where the data is recovered from the signature. 
 C_VerifyRecover N/A N/A Verifies a signature on single-part data, where the data is recovered from the signature. 
 N/A m_VerifySingle VerifySingle IBM extension, nonstandard extension, combination of VerifyInit and Verify. Signs or MACs data in one pass, with one call, without constructing intermediate digest state. Does not return any state to host other than verification result. 
 C_DigestEncryptUpdate N/A N/A Continues simultaneous multiple-part digesting and encryption operations. 
 C_DecryptDigestUpdate N/A N/A Continues simultaneous multiple-part decryption and digesting operations. 
 C_SignEncryptUpdate N/A N/A Continues simultaneous multiple-part signature and encryption operations. 
 C_DecryptVerifyUpdate N/A N/A Continues simultaneous multiple-part decryption and verification operations. 
 C_GenerateKey* m_GenerateKey GenerateKey Generates a secret key.
But that peer cannot join a channel that is configured with application capability 2.x.
* If a channel application capability level is upgraded to 2.x before the peer 1.4.x image is upgraded to 2.x, the peer stops functioning and needs to be upgraded to the 2.x image.
* It is possible for a peer that is running a 2.x image to join a channel with application capability 1.4 and another channel with application capability 2.x at the same time. But smart contracts on the peer in .cds format use the [legacy smart contract deployment](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v14) process where they have to be instantiated on the channel with application capability 1.4. Smart contracts on the peer in tar.gz format follow the [Fabric 2.x smart contract lifecycle](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2) process on the channel with application capability 2.x.



Like the orderer and channel capabilities, the application capability level can be edited through a channel configuration update. The orderer capability can also be specified during the creation of a channel, but will require the approval of the ordering service.

If you are using the SDK to create or edit a channel, take caution to not submit a channel configuration with an invalid application capability. Because application capabilities are not validated by the ordering service, invalid application capabilities are not flagged. Because the peers cannot process capabilities that do not exist, the peers will crash when attempting to read the configuration block containing an invalid capability. Because the peers will be unable to progress beyond this configuration block, it will not be possible to reverse this configuration block and submit another one to "fix" the problem. A channel in this state is unrepairable.









 Tuning your ordering service 

Performance of a blockchain platform can be affected by many variables such as transaction size, block size, network size, as well as limits of the hardware. The orderer node includes a set of tuning parameters that together can be used to control orderer throughput and performance.
Details like gateway ids, security tokens, acl files and log level for each gateway can be provided here. If the user has chosen to run the client as a windows service the client will launch with the configurations provided. If the user has not chosen to launch the client as a windows service, the configurations will be stored for further use. In either case, the configurations are stored in %Installation_directory%/ibm/securegateway/client/securegw_service.config.
7. Starting version 1.5.0, the client comes with a fully functional client UI. You can configure it from the installer itself. The user can provide the password and the port number (default is 9003) from which the client UI will be launched.



If the user chooses to launch the client with connection to multiple gateways, please take care while providing the configuration values. The gateway ids needs to be separated by spaces. The security tokens, acl files and log levels should to be delimited by --. If you don't want to provide any of these three values for a particular gateway, please use 'none'.

Note:Please ensure that there are no residual white spaces.

Note:Please note that the acl files should be placed in %Installation_directory%/ibm/securegateway/client directory or relative to that path.





 Starting an interactive client session 

To start the client, open a command prompt with administrative privileges and run the following commands:

cd "<Installation_directory>ibmsecuregatewayclient"
secgw.cmd

Alternatively, navigate to <Installation_directory>ibmsecuregatewayclient and double-click secgw.cmd.

Note:You can choose to use the configurations stored in <Installation_directory>ibmsecuregatewayclientsecuregw_service.config file or provide the details interactively.

Return to [Getting Started - Adding a Client](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-add-client).







 DataPower 

DataPower has an embedded version of the Secure Gateway Client.
High-Availability 

IBM Cloud® Databases for PostgreSQL is a managed cloud database service that is fully integrated into the IBM Cloud environment. The database, storage, and supporting infrastructure all run in IBM Cloud.

Databases for PostgreSQL provides replication, fail-over, and high-availability features to protect your databases and data from infrastructure maintenance, upgrades, and failures. Deployments contain a cluster with two data members, a leader and a replica. Both members contain a copy of your data by using asynchronous replication, with a distributed consensus mechanism to maintain cluster state and handle failovers. If the leader becomes unreachable, the cluster initiates a failover, and the replica is promoted to leader. The replica rejoins the cluster and your cluster continues to operate normally.

Databases for PostgreSQL will, at times, do controlled switchovers under normal operation. These switchovers are no-data-loss events that result in resets of active connections. There is a period of up to 15 seconds where reconnections can fail. At times, unplanned failovers might occur due to unforeseen events on the operating environment. These can take up to 45 seconds, but can be less. In both cases, potential exists for the downtime to be longer.

You can extend high-availability further by adding [PostgreSQL members](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-horizontal-scaling) to the instance, for greater in-region redundancy, or by provisioning [read-only replicas](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-read-only-replicas) for cross-regional failover or read offloading.

Databases for PostgreSQL is designed and built to provide a robust, resilient, and performant Database as a Service offering.
: Name of the region, for example, us-south or eu-gb. If not specified, the region logged into, or targeted, will be used.

--output JSON
: If specified, output will be returned in JSON format. If JSON is not specified, output will be returned in a tabular format.

--force
: The command will be run without prompting the user whether or not to continue with the command.

help | --help | -h
: List options available for the command.







 ibmcloud atracker config report 

Use the following command to return a report about the IBM Cloud Activity Tracker Event Routing service configuration. This report will include any issues in the configuration.

ibmcloud atracker config report --output YAML
As the default is public, if there are no public endpoints then none will be found and you will receive an error: {"errors":"not_found"}. Use the -e private flag to use private endpoints.







 Examples 

Display how to connect to a deployment.

ibmcloud cdb deployment-connections MyPSQL

(Shows a connection string and a CLI command string)

Connect to a deployment as admin.

ibmcloud cdb deployment-connections MyPSQL --start

When run, the plug-in prompts for the admin password, then runs the CLI command string. The command that is used in the CLI command string must be installed.

Show all details of how to make a connection to a deployment for a particular user and password combination.

ibmcloud cdb cxn MyPSQL -a -u auser -p auserpassword







 ibmcloud cdb deployment-cacert 

Short version - cacert

Display the self-signed certificate that is used for verifying TLS/SSL connections to the deployment. The result is, by default, output to the console but can be saved to a file too.

ibmcloud cdb deployment-cacert <deployment name or CRN> [--user <userid>] [--save] [--certroot <path>] [--json]



 Command options 



* --user <userid> or -u By default, the admin user is used to obtain the certificate. This flag optionally allows a user to be specified where the deployment supports per user certificates.
* --save or -s Save the decoded certificate into the certificate root directory. The default is $HOME/.cloud/plugins/cdb/cdbcerts/.
* --certroot <path> or -c Use the path as the certificate root directory. If the path doesn't exist, it is created automatically. Works with the --save flag. The certificate root value can also be set in the $CERTROOT environment variable.
* --json or -j Display results as JSON.







 Examples
It's powered with a simple outlet power supply 5V 1A. My Questions Will I have any problems leaving the Arduino turned on all the time? li Is there some other Arduino board better recommended for this? li Are there any precautions that I need to heed regarding this? li ul ",
"tags": "<arduino-uno><web-server><ethernet>",
"title": "Is an Arduino capable of running 24 7?",
"upModVotes": 49,
"userId": "11",
"userReputation": 4535,
"username": "sachleen",
"views": 3234
}, {
"accepted": 0,
"answer": "A couple of things to keep in mind outside of Sachleen's mention of Milli's Like any electronics heat can be disruptive. The micro controller itself isn't likely going to be a huge issue from the perspective of heat but other components like the power supply might cause issues. li If your code uses EEPROMWrite a be aware that the EEPROM is only rated for something in the neighbourhood of 100 000 writes. li ul ",
"answerScore": "24",
"authorUserId": "3",
"authorUsername": "Butzke",
"downModVotes": 0,
"id": 3,
"subtitle": "I'm making a simple Arduino web server and I want to keep it turned on all the time. So it must endure to stay working continuously. I'm using an Arduino Uno with a Ethernet Shield. It's powered with a simple outlet power supply 5V 1A. My Questions Will I have any problems leaving the Arduino turned on all the time? li Is there some other Arduino board better recommended for this? li Are there any precautions that I need to heed regarding this? li ul ",
"tags": "<arduino-uno><web-server><ethernet>",
Works with the --save flag. The certificate root value can also be set in the $CERTROOT environment variable.
* --only [app or cli] or -o Show only the settings that are relevant to app connections or cli connections.
* --json or -j Display results as JSON.
* --endpoint-type or -e Endpoint type for returned connection strings, either public or private. Default is public. As the default is public, if there are no public endpoints then none will be found and you will receive an error: {"errors":"not_found"}. Use the -e private flag to use private endpoints.







 Examples 

Display how to connect to a deployment.

ibmcloud cdb deployment-connections MyPSQL

(Shows a connection string and a CLI command string)

Connect to a deployment as admin.

ibmcloud cdb deployment-connections MyPSQL --start

When run, the plug-in prompts for the admin password, then runs the CLI command string. The command that is used in the CLI command string must be installed.

Show all details of how to make a connection to a deployment for a particular user and password combination.

ibmcloud cdb cxn MyPSQL -a -u auser -p auserpassword







 ibmcloud cdb deployment-cacert 

Short version - cacert

Display the self-signed certificate that is used for verifying TLS/SSL connections to the deployment. The result is, by default, output to the console but can be saved to a file too.

ibmcloud cdb deployment-cacert <deployment name or CRN> [--user <userid>] [--save] [--certroot <path>] [--json]



 Command options 



* --user <userid> or -u By default, the admin user is used to obtain the certificate. This flag optionally allows a user to be specified where the deployment supports per user certificates.
* --save or -s Save the decoded certificate into the certificate root directory.