vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Usage limits 

The following usage limits and restrictions apply to Natural Language Understanding service instances.



  Analyzed text limit 

Natural Language Understanding truncates analyzed text that contains more than 50,000 single-byte or multibyte characters. To view the text that counts toward this limit in your requests, set the return_analyzed_text parameter to true.

You can set a smaller character limit with the limit_text_characters parameter. If you are interested in analyzing only a small portion of your content, this can help you avoid excessive costs.

Example parameters object:

{
"url": "ibm.com",
"limit_text_characters": 10000,
"return_analyzed_text": true,
"features": {
"concepts": {}
}
}





  Request limit 

Each Natural Language Understanding service instance is limited, based on the number of analyze requests being processed. For the Lite plan, the limit is 5 analyze requests per second; for the Standard plan, the limit is 150 analyze requests per second. Analyze requests exceeding these limits may receive a 429: Too Many Requests error.

The limit for the Standard plan can be increased by [opening a support ticket](https://ibm.biz/ibmcloudsupport).

All other requests are rate-limited at 5 requests per second.





  Custom model training limit 

The maximum number of models that can be trained via the Natural Language Understanding customization API in parallel is 3.





  Custom model size limit for Lite pricing plans 

There is a size limit for Knowledge Studio custom models that are deployed to Natural Language Understanding service instances on Lite pricing plans. To remove the custom model size limit, upgrade your Natural Language Understanding service instance to a paid pricing plan. You can find your service instances on the IBM Cloud [resources page](https://cloud.ibm.com/resources).





  Language support 

Different language restrictions apply depending on how you use the service. For details, see the [Language support](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-language-support) page.
* Flag: --prefix PREFIX



* Optional: Together with upload-id-marker, this parameter specifies the multipart upload after which listing should begin.



* Flag: --key-marker value



* Optional: Together with key-marker, specifies the multipart upload after which listing should begin. If key-marker is not specified, the upload-id-marker parameter is ignored.



* Flag: --upload-id-marker value



* Optional: The SIZE of each page to get in the service call. This does not affect the number of items returned in the command's output. Setting a smaller page size results in more calls to the service, retrieving fewer items in each call. This can help prevent the service calls from timing out. (default: 1000).



* Flag: --page-size SIZE



* Optional: The total NUMBER of items to return in the command's output. If the total number of items available is more than the value specified, a NextToken is provided in the command's output. To resume pagination, provide the NextToken value in the starting-token argument of a subsequent command. (default: 0).



* Flag: --max-items NUMBER



* Optional: The REGION where the bucket is present. If this flag is not provided, the program uses the default option that is specified in config.



* Flag: --region REGION



* Optional: Output FORMAT can be only json or text.



* Flag: --output FORMAT











 List objects 



* Action: List files present in a bucket in a user's IBM Cloud Object Storage Account. This operation is currently limited to the 1000 most recently created objects and can't be filtered.
* Usage:ibmcloud cos objects --bucket BUCKET_NAME [--delimiter DELIMITER] [--encoding-type METHOD] [--prefix PREFIX] [--starting-token TOKEN] [--page-size SIZE] [--max-items NUMBER] [--region REGION] [--output FORMAT]
* Parameters to provide:



* The name of the bucket.



* Flag: --bucket BUCKET_NAME
Job size limit 

Code Engine limits the size of jobs and job runs with a maximum of 10 KiB. When you create or update jobs and job runs with the console, CLI, or API, Code Engine checks the size of the job or job run. If the operation exceeds the limit, a size limit exceeded error is given. If you receive this error, try reducing the size of your job or job run in one of the following ways.



* If you use commands and arguments, try reducing the use of these options, make them shorter, or move them into the container image that is used by your job or job run.
* If you use environment variables, try to use fewer environment variables or make them shorter. You can use secrets or configmaps to define environment variables and import them into the job by using the --env-from-secret or --env-from-configmap options with the [job create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-create), [job update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-job-update), [jobrun submit](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-jobrun-submit), and [jobrun resubmit](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-jobrun-resubmit) commands.



For more information about troubleshooting jobs, see [Troubleshooting - Why can't I submit a job run?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-jobrun-submit-fails-cli).







 Function limits 

The following table lists the limits for Functions.



Function limits

 Category Maximum Need to extend the maximum? 

 Length of runtime 120 seconds
If TAG is not specified, the default is latest. The image option is required if the --build-source option is not specified. This value is optional.

--max-scale, --max, --maxscale
: The maximum number of instances that can be used for this application. If you set this value to 0, the application scales as needed. The application scaling is limited only by the instances per the resource quota for the project of your application. See [Limits and quotas for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limits). This value is optional. The default value is 10.

--memory, -m
: The amount of memory set for the instance of the application. Use M for megabytes or G for gigabytes. For valid values, see [Supported memory and CPU combinations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-mem-cpu-combo). This value is optional. The default value is 4G.

--min-scale, --min, --minscale
: The minimum number of instances that can be used for this application. This option is useful to ensure that no instances are running when not needed. This value is optional. The default value is 0.

--mount-configmap, --mount-cm
: Add the contents of a configmap to the file system of your application container by providing a mount directory and the name of a configmap, with the format MOUNT_DIRECTORY=CONFIGMAP_NAME. Each mounted configmap must use a unique mount directory. For each key-value pair in the configmap, a file is added to the specified mount directory where the filename is the key and the contents of the file is the value of the key-value pair.
The file share and the replica must be in two different zones. Review your parameters and change the zones so that the file share and replica are in different zones.





 Invalid value for variable 

The parameters for automation have different requirements for length and value. The most common error is because the parameter is not the correct length. This table lists the various parameters and their lengths:



 Parameter Required length or range 

 prefix less than 11 characters 
 resource_group_name 32 characters 
 bastion_image 41 characters 
 web_image 41 characters 
 app_image 41 characters 
 db_image 41 characters 
 app_min_servers_count Allowed value are between 1 and 1000 
 web_min_servers_count Allowed value are between 1 and 1000 



This table lists the valid values for various parameters:



 Parameter Valid values 

 web_pg_strategy Values are host_spread and power_spread 
 db_pg_strategy Values are host_spread and power_spread 
 app_pg_strategy Values are host_spread and power_spread
"Timestamp": "Thu, 17 Oct 2019 09:22:13 GMT"
}



* Optional: The REGION where the bucket is present. If this flag is not provided, the program uses the default option that is specified in config.



* Flag: --region REGION



* Optional: Output FORMAT can be only json or text.



* Flag: --output FORMAT









 Upload objects by using S3Manager 



* Action: Upload objects to COS concurrently.
* Usage:ibmcloud cos upload --bucket BUCKET_NAME --key KEY --file PATH [--concurrency value] [--max-upload-parts PARTS] [--part-size SIZE] [--leave-parts-on-errors] [--cache-control CACHING_DIRECTIVES] [--content-disposition DIRECTIVES] [--content-encoding CONTENT_ENCODING] [--content-language LANGUAGE] [--content-length SIZE] [--content-md5 MD5] [--content-type MIME] [--metadata MAP] [--region REGION] [--output FORMAT]
* Parameters to provide:



* The name (BUCKET_NAME) of the bucket.



* Flag: --bucket BUCKET_NAME



* The KEY of the object.



* Flag: --key KEY



* The PATH to the file to upload.



* Flag: --file PATH



* Optional: The number of goroutines to spin up in parallel per call to Upload when sending parts. Default value is 5.



* Flag: --concurrency value



* Optional: Max number of PARTS which will be uploaded to S3 that calculates the part size of the object to be uploaded. Limit is 10,000 parts.



* Flag: --max-upload-parts PARTS



* Optional: The buffer SIZE (in bytes) to use when buffering data into chunks and ending them as parts to S3. The minimum allowed part size is 5MB.



* Flag: --part-size SIZE
ibmcloud event-notifications destination update --id ID [--name NAME] [--description DESCRIPTION] [--certificate CERTIFICATE] [--config CONFIG] [--instance-id INSTANCE-ID]
* Parameters to provide:

--id (string)
: Unique identifier for destination. Required.

The maximum length is 36 characters. The minimum length is 36 characters. The value must match regular expression /[a-fA-F0-9]{8}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]{4}-[a-fA-F0-9]/.

--name NAME (string)
: The destination name to be updated.

The maximum length is 255 characters. The minimum length is 1 character. The value must match regular expression /[!a-zA-Z 0-9-_/.?:'";,+=@$%^&() ]/.

--description DESCRIPTION (string)
: The description of the destination.

The default value is . The maximum length is 255 characters. The minimum length is 0 characters. The value must match regular expression /[!a-zA-Z 0-9-_/.?:'";,+=@$%^&() ]/.

--certificate CERTIFICATE (string)
: The certificate file path to be provided. The allowed file type is p8 and p12 certificate.

--config CONFIG ([DestinationConfig examples](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-cli-plugin-event-notifications-clien-cli-destination-config-example-schema))
: The configuration needed to set the destination-specific parameters.

--instance-id
: The unique identifier for IBM Cloud Event Notifications instance.

The maximum length is 36 characters. The minimum length is 36 characters.
The maximum length is 128 characters. The value must match regular expression /^\.\-0-9a-zA-Z] +$/.
--config-id (string): The unique configuration ID. Required.
The maximum length is 128 characters. The value must match regular expression /^\.\-0-9a-zA-Z] ! ! ! ! +$/.
<-- </section "id="section-project-list-config-drafts-cli-options" "> --><-- <section "id="section-project-list-config-drafts-examples" "> --> Example ibmcloud project list-config-drafts --project-id=exampleString --config-id=exampleString
<-- </section "id="section-project-list-config-drafts-examples" "> --><-- <section "id="section-project-list-config-drafts-cli-output" "> --> Example output Sample response for list project configuration drafts. {
"drafts" : {
"version" : 1,
"state" : "MERGED",
"pipeline_state" : "PIPELINE_FAILED",
"href" : "/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/293c3c36-a094-4115-a12b-de0a9ca39be5/drafts/1"
}, {
"version" : 2,
"state" : "ACTIVE",
"pipeline_state" : "PIPELINE_SUCCEEDED",
"href" : "/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/293c3c36-a094-4115-a12b-de0a9ca39be5/drafts/2"
} ] ! ! !
The size can be specified in kibibytes (K), mebibytes (M), gibibytes (G), tebibytes (T), or pebibytes (P). For example, to set the partition size to 100 GiB, enter +100G.
4. After the partition is created, run the w command to save changes to the partition table. Restart your system to verify the newly created partition.







 Step 3 - Formating the volume partition 

/sbin/mkfs -t ext4 /dev/vdb1

To check the size of the partition, run the following command.

fdisk -s /dev/vdb1





 Step 4 - Updating the file systems table 

Update /etc/fstab.

fstab /dev/vdb1

disk_partition=/dev/vdb1
uuid=$(blkid -sUUID -ovalue $disk_partition)
mount_point=$mount_parent/$uuid
echo "UUID=$uuid $mount_point ext4 defaults,relatime 0 0" >> /etc/fstab





 Step 5 - Creating a directory 

mkdir /myvolumedir
mount /dev/vdb1 /myvolumedir





 Step 6 - Mounting the volume as a file system 

mount /dev/vdb1 /myvolumedir





 Step 7 - Accessing the new file system 

To see your new file system, run the following command.

df -k

The command produces an output like the following example.

file system 1K-blocks Used Available Use% Mounted on
udev 4075344 0 4075344 0% /dev
tmpfs 816936 8844 808092 2% /run
/dev/vda2 101330012 1261048 100052580 2% /
tmpfs 4084664 0 4084664 0% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 4084664 0 4084664 0% /sys/fs/cgroup
You can configure up to 300 Block Storage for VPC volumes per account in a region. You can request to increase this quota by [opening support case](https://cloud.ibm.com/docs/vpc?topic=vpc-manage-storage-limit) and specifying in which zone you need more volumes.

You can attach only one boot volume to a virtual server instance at a time, but you can attach up to 12 Block Storage for VPC data volumes to a single instance. For other limitations, see [Volume attachment limits](https://cloud.ibm.com/docs/vpc?topic=vpc-attaching-block-storagevol-attach-limits).



 Boot volumes 

When you create an instance from a stock image, a 100 GB, 3,000 IOPS general-purpose boot volume is created and attached to the instance by default. When you create an instance from a custom image, you can specify a boot volume capacity of 10 GB to 250 GB, depending what the image requires. This capacity can be any size between the minimum size that is supported for the selected image and the maximum supported image size. If the custom image is smaller than 10 GB, the boot volume capacity is rounded up to 10 GB. After the boot volume is created, you can expand the boot volume size to the maximum supported size, which is 250 GB.

You cannot create an image from a boot volume that is encrypted with customer-managed keys and is not 100 GB. Such an operation is not supported.

By default, boot volumes are encrypted by IBM-managed encryption. Optionally, you can use your own root keys (CRKs) by choosing customer-managed encryption during instance creation (see [Customer-managed encryption](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-encryption-aboutvpc-customer-managed-encryption)).

By default, boot volumes are deleted when you delete an instance. You can toggle this setting on or off in the instance details. A boot volume can be unattached only by deleting the instance that it is attached to. A boot volume cannot be detached from an instance while the instance exists.
"state" : "ACTIVE",
"pipeline_state" : "PIPELINE_SUCCEEDED",
"href" : "/v1/projects/db268db0-160b-4911-8f93-89659000a927/configs/9c7afed6-17fb-4c56-a13d-440a78f936bd/drafts/2"
},
"project_id" : "db268db0-160b-4911-8f93-89659000a927",
"version" : 1,
"is_draft" : false,
"state" : "NOT_INSTALLED",
"pipeline_state" : "PIPELINE_SUCCEEDED",
"update_available" : true,
"created_at" : "2023-02-22T19:51:23.253Z",
"updated_at" : "2023-02-22T19:51:23.253Z"
}
<-- </section "id="section-project-config-get-cli-output" "> --><-- </section "id="section-project-cli-config-get-command" "> --><-- <section "id="section-project-cli-config-update-command" "> --> ibmcloud project config-update Update a configuration in a project by the ID. ibmcloud project config-update --project-id PROJECT-ID --id ID --locator-id LOCATOR-ID] --input INPUT] --setting SETTING] --name NAME] --labels LABELS] --description DESCRIPTION] --authorizations AUTHORIZATIONS] --compliance-profile COMPLIANCE-PROFILE] !
<-- <section "id="section-project-config-update-cli-options" "> --> Command options --project-id (string): The unique project ID. Required.
The maximum length is 128 characters.
PV Size <30.00 GiB / not usable 3.00 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 7679 - Changed <- new number of physical extents
Free PE 2560
Allocated PE 5119
PV UUID dehWT5-VxgV-SJsb-ydyd-1Uck-JUA9-B9w0cO

--- Physical Segments ---
Physical extent 0 to 5118:
Logical volume /dev/vg00/vol_projects
Logical extents 6399 to 11517
Physical extent 5119 to 7678:
FREE
2. Resize Logical Volume.

 lvextend -l +100%FREE -r /dev/vg00/vol_projects
Size of logical volume vg00/vol_projects changed from 49.99 GiB (12798 extents) to 59.99 GiB (15358 extents).
Logical volume vg00/vol_projects successfully resized.
resize2fs 1.42.9 (28-Dec-2013)
Filesystem at /dev/mapper/vg00-vol_projects is mounted on /projects; on-line resizing required
old_desc_blocks = 7, new_desc_blocks = 8
The filesystem on /dev/mapper/vg00-vol_projects is now 15726592 blocks long.

 lvdisplay
--- Logical volume ---
LV Path /dev/vg00/vol_projects
LV Name vol_projects
VG Name vg00
LV UUID z1lukZ-AuvR-zjLr-u1kK-eWcp-AHjX-IcnerW
LV Write Access read/write
LV Creation host, time acs-kyungmo-lamp.tsstesting.com, 2021-12-07 19:34:39 -0600
LV Status available
 open 1
LV Size 59.99 GiB <--- new logical volume size
Current LE 15358
Segments 4
Allocation inherit
"locks" : "lock-example-1", "lock-example-2" ]
} ]
} ],
"first" : {
"href" : "https://us-south.secrets-maanger.cloud.ibm.com/88b75b20-aa21-4174-85c9-1feb3cc93c9a/api/v2/secrets_locks?limit=50"
},
"previous" : {
"href" : "https://us-south.secrets-maanger.cloud.ibm.com/88b75b20-aa21-4174-85c9-1feb3cc93c9a/api/v2/secrets_locks?offset=50&limit=50"
},
"last" : {
"href" : "https://us-south.secrets-maanger.cloud.ibm.com/88b75b20-aa21-4174-85c9-1feb3cc93c9a/api/v2/secrets_locks?offset=200&limit=50"
},
"limit" : 50,
"next" : {
"href" : "https://us-south.secrets-maanger.cloud.ibm.com/88b75b20-aa21-4174-85c9-1feb3cc93c9a/api/v2/secrets_locks?offset=150&limit=50"
},
"offset" : 100,
"total_count" : 1
}







 ibmcloud secrets-manager secret-locks 

List the locks that are associated with a specified secret. Note: If the --all-pages option is not set, the command will only retrieve a single page of the collection.

ibmcloud secrets-manager secret-locks --id ID [--offset OFFSET] [--limit LIMIT] [--sort SORT] [--search SEARCH]



 Command options 

--id (string)
: The ID of the secret. Required.

The maximum length is 36 characters.
[Shows the JSON source for a document that has been classified with the package_container class.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/json-classifier-found.png)

Figure 2. Document classifier enrichment syntax



 Document classifier limits 

The number of document classifiers and labels that you can create per service instance depends on your Discovery plan type.



Document classifier plan limits

 Limit Enterprise Premium Cloud Pak for Data 

 Number of document classifiers per service instance 20 20 Unlimited 
 Number of labeled data rows 20,000 20,000 20,000 
 Maximum size in MB of training data after enrichment 1,024 1,024 1,024 
 Number of labels 1,000 1,000 1,000 
 Number of target fields 50 50 50
ibmcloud project config-check --project-id PROJECT-ID --id ID --x-auth-refresh-token X-AUTH-REFRESH-TOKEN] --is-draft IS-DRAFT] !
<-- <section "id="section-project-config-check-cli-options" "> --> Command options --project-id (string): The unique project ID. Required.
The maximum length is 128 characters. The value must match regular expression /^\.\-0-9a-zA-Z] +$/.
--id (string): The unique config ID. Required.
The maximum length is 128 characters. The value must match regular expression /^\.\-0-9a-zA-Z] ! ! ! ! ! +$/.
--x-auth-refresh-token (string): The IAM refresh token.
The maximum length is 512 characters. The minimum length is 0 characters. The value must match regular expression /^$|^(?\s).\S$/.
--is-draft (bool): To specify whether the validation check triggers against the draft or the active version of the configuration.
The default value is true.
<-- </section "id="section-project-config-check-cli-options" "> --><-- <section "id="section-project-config-check-examples" "> --> Example ibmcloud project config-check --project-id=exampleString --id=exampleString --x-auth-refresh-token=exampleString --is-draft=true
<-- </section "id="section-project-config-check-examples" "> --><-- <section "id="section-project-config-check-cli-output" "> --> Example output Sample response for a project configuration. {
<-- <section "id="section-project-config-install-cli-options" "> --> Command options --project-id (string): The unique project ID. Required.
The maximum length is 128 characters. The value must match regular expression /^\.\-0-9a-zA-Z] +$/.
--id (string): The unique config ID. Required.
The maximum length is 128 characters. The value must match regular expression /^\.\-0-9a-zA-Z] ! ! ! ! +$/.
<-- </section "id="section-project-config-install-cli-options" "> --><-- <section "id="section-project-config-install-examples" "> --> Example ibmcloud project config-install --project-id=exampleString --id=exampleString
<-- </section "id="section-project-config-install-examples" "> --><-- <section "id="section-project-config-install-cli-output" "> --> Example output Sample response for a project configuration. {
"id" : "293c3c36-a094-4115-a12b-de0a9ca39be5",
"definition" : {
"name" : "env-stage",
"description" : "Stage environment configuration, which includes services common to all the environment regions. There must be a blueprint configuring all the services common to the stage regions. It is a terraform_template type of config that points to a github repo hosting the terraform modules that can be deployed via Schematics Workspace.",
"labels" : "env:stage", "governance:test", "build:0" ],
Environment variable values can have a maximum length of 12288.

--outbound-only
: If this parameter is set, only outbound connections are allowed from your Hyper Protect Virtual Server instance. Use the internal IP address to connect to this Virtual Server from other Virtual Servers created by the same IBM Cloud account in the same region.





 Example input 

ibmcloud hpvs instance-create MyHPVS lite-s dal13 -g Default --ssh "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQCgguQtzV39LpP/iHAtjwo+4Z5QdASG73dwBlFIsTn5kPOaVYFHhzhvA/xMbLqDpxfYP/YzwU4rXNXMhCr4hlsruPXt5Ak4y83GmnNL8e+oq8lxU/afymje4PcYLnkm8WQvkreIEBaB73VOUKiLSSbdVljUk6a1LB347bCf72Oob8JpY4Pb3N4idrigSoCc+V4JVkz4pXD2Hoyar4J5I2527Ho+vUqdf5FoK9mFRUqtI8NTLKynL2/qVsCgTeUxnOknDjPE0+nqwyNI4toYozcISYb63K9Je6UBT4JaIQXMbdMhDH00wVH7R26SamKqS2iazcUBnZgN4//Vnic+US90ybsqvTuP/OQpHXwfdjshOEsz5PULZKbWgidsfA7aW3pjv1uijCPIrTFOsaAPktMCzhfJzaeFC0VIXweN7/2PT/Zl7U9Ys36CmmLaXfLotXxPWmbGUyRfavPN1Znhqph7v9w94E7JcngQ7sn+l+nkpYg5qdcBFZZ3kNhT4PVRbXE="





 Example output 

OK