vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Why do I get the message "You do not have permission to perform this action." when trying to use the App Configuration service instance? 

When you try to use App Configuration service instance you are unable to perform any action.

  What’s happening 

When you try to access any feature in App Configuration service instance either through the console or API or CLI, you may encounter an error similar to any of the following examples:

You do not have permission to perform this action. Contact your service Administrator.

or

{
"message": "Unauthorized"
}

  Why it’s happening 

This is due to the reason that you are trying to access the App Configuration service instance from a Network Zone which is outside of the defined Network zone in your account's Context-based restrictions settings.

  How to fix it 

To resolve the issue, make sure that your Context-based restrictions settings in the account are updated to allow the IP addresses that correspond with your network in the Network Zone's Allowed IP addresses.

As an administrator of your App Configuration service instance perform the following steps:



1.  In the IBM Cloud console, click Manage > Context-based restrictions.
2.  Go to Network zones and then select the required Network Zone and select Edit from the overflow menu.
3.  In the Allowed IP addresses, include the required IP addresses that you want to enable access to the App Configuration service instance.
4.  Click Update.



For more information, see [Managing access with context-based restrictions](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-access-control-cbr).
Now that your Periodic timer (cron) subscription is created, go to the Event subscriptions page to [view a listing of defined subscriptions](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cronview-eventing-cron-app-ui).
6. To update a subscription, navigate to your Periodic timer (cron) subscription page. From the Event subscriptions page, click the name of the subscription that you want to update.
7. From your Periodic timer (cron) subscription page, let's change the data in the event message. From the Custom event data tab, change the event data to hello sunshine. Click Save to save your changes.
8. Because the myapp application references the sample cron application, which prints information to log files, you can view the logs. View the application logs for the myapp event consumer application and see that the event message is hello sunshine. See [Viewing application logs from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-view-logsview-applogs-ui).







 Subscribing to Periodic timer (cron) events for an application with the CLI 

Before you begin



* [Set up your Code Engine CLI environment](https://cloud.ibm.com/docs/codeengine?topic=codeengine-install-cli).
* [Create a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).
* [Create an application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-create). For example, create an application that is called myapp that uses the icr.io/codeengine/cron image. This image is built from cron.go, available from the [Samples for IBM Cloud Code Engine GitHub repo](https://github.com/IBM/CodeEngine/tree/main/cron)
For example, if your subscription specifies --path /event, the event is sent to https://<base application URL>/events.

Events are sent to applications as HTTP POST requests. For more information, see [HTTP headers and body information for events](https://cloud.ibm.com/docs/codeengine?topic=codeengine-eventing-cosevent-producersub-header-body-cos).



 Subscribing to IBM Cloud Object Storage events for an application from the console 

You can create and update IBM Cloud Object Storage event subscriptions for an application from the console.

Before you begin



* [Create a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).
* [Create an application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-appdeploy-app-console). For example, create an application that is called myapp that uses the icr.io/codeengine/cos-event image. This image is built from cos-listen.go, available from the [Samples for IBM Cloud Code Engine GitHub repo](https://github.com/IBM/CodeEngine/tree/main/cos-event).



Complete the following steps to create and update an IBM Cloud Object Storage event subscription for an application from the console.



1. From the [Code Engine Projects page](https://cloud.ibm.com/codeengine/projects), go to your project.
2. From the Overview page, click Event subscriptions.
3. From the Event subscriptions page, click Create to create your subscription.
4. From the Create an event subscription page, complete the following steps.



1. For Event type, select the Cloud Object Storage tile. Click Next.
2. For General, provide a name for the Object Storage subscription, for example, mycos. You can optionally provide event attributes. Note that if the Object Storage event consumer is an application, event attributes are available as HTTP headers.
This action is not permitted on this resource: Please contact IBM Key Protect or open a service ticket to enable this feature

Reason code: FEATURE_RESTRICTED_ERR





 HTTP status code 

403 - Forbidden

The HTTP 403 Forbidden client error status response code indicates that the server understood the request but refuses to authorize it.

This status is similar to 401, but in this case, re-authenticating will make no difference. The access is permanently forbidden and tied to the application logic, such as insufficient rights to a resource.





 Context 

You are attempting to create, update, or use an instance policy with a feature that is not supported.

For example, instance policy was created for an allowedIp address range, which only supports IPv4 addresses. You then made a request to the instance with an IPv6 address, which returns this error.







 32 - This request requires that the key version... 



 Message 

This request requires that the key version is later than current registration key version

Reason code: KEY_VERSION_INVALID





 HTTP status code 

422 - Unprocessable Entity

The HTTP 422 Unprocessable Entity response status code indicates that the server understands the content type of the request entity, and the syntax of the request entity is correct, but it was unable to process the contained instructions.

The client should not repeat this request without modification.





 Context 

This error applies to keys used for "Registrations."

When a service, such as Cloud Object Storage (COS), tries to replace or restore a key it checks the timestamp of the key.

If the key timestamp is less than the timestamp of the key used by the registration then this error occurs.

The key used buy the service must have a timestamp equal to or greater than the registration's key.

Registrations are associations between root keys and other cloud resources, such as Cloud Object Storage (COS) buckets or Cloud Databases deployments.

For more information about Registrations, see [viewing associations between root keys and encrypted IBM Cloud resources](https://cloud.ibm.com/docs/key-protect?topic=key-protect-view-protected-resources).







 33 - This root key has been rotated within... 



 Message
You do not have to update the smart contract package in this case, but it is required to increment the smart contract version. 
 Change the lifecycle endorsement policy for the channel From the Channels tab, click Channel details and click the Settings icon and then click through to the Lifecycle endorsement policy step. 
 A new organization joins the channel and wants to approve a smart contract proposal. From the Channels tab, click the tile of the proposed smart contract and click Begin approval process. After providing the identity from your wallet, click Add file to upload the package or Existing package to select a package already installed on another peer in your organization, and optionally choose which peers to install it on. 
 A new organization joins the channel and wants their peers to be able to endorse transactions for a committed smart contract. From the Channels tab, click the tile of the committed smart contract and click Begin approval process. After providing the identity from your wallet, click Add file to upload the package or Existing package to select a package that is already installed on another peer in your organization, and optionally choose which peers to install it on. 



More details on the lifecycle deployment scenarios are available in the [Fabric documentation](https://hyperledger-fabric.readthedocs.io/en/release-2.2/chaincode_lifecycle.html?highlight=Fabric%20chaincode%20lifecycledeployment-scenarios)





 Specifying a smart contract endorsement policy 

Every smart contract must have a smart contract endorsement policy, that is specified during the smart contract definition. The endorsement policy specifies the set of organizations, the peers, on a channel that can execute the smart contract and independently validate the transaction output. For example, an endorsement policy can specify that a transaction is added to the ledger only if a majority of the members on the channel endorse the transaction. The organization that proposes the definition can select from among the members who have installed the smart contract to become validators, and sets the endorsement policy for all channel members.
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]{12}/.

[--topic-id TOPIC-ID] (string)
: The topic ID to be set for subscription.

The maximum length is 150 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]{12}/.

[-attributes ATTRIBUTES] ([SubscriptionCreateAttributes](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-cli-plugin-event-notifications-clien-cli-subscription-example-schema))
: The attributes to be set for subscription.
* Examples:



* The following example shows the format of the SubscriptionCreateAttributes object.

{
"add_notification_payload" : true,
"signing_enabled" : true
}
* Attributes flag syntax in case of SMS subscription to be created.

{
"to" :["+19667895490", "+19845678321"]
}
* Attributes flag syntax in case of email subscription to be created.

{
"to" :["entest@gmail.com"],
"add_notification_payload": true,
"reply_to_mail": "en@ibm.com",
"reply_to_name": "EYS ORG",
"from_name":"ABC ORG"
}
* The following example shows the format of the SubscriptionCreateAttributes object for slack.

{
Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.<-- </section "id="section-en-notice-accept" "> --><-- <section "id="section-en-notice-downstream" "> --> 10. Automatic Licensing of Downstream Recipients Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.<-- </section "id="section-en-notice-downstream" "> --><-- <section "id="section-en-notice-patents" "> --> 11. Patents A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based.
BXNUI2039E 

Message: The starter ID, "{0}", wasn't copied because the Git repository that associated with the boilerplate template isn't accessible.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2040E 

Message: The metadata for the starter ID, "{0}", could not be registered.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2041E 

Message: The starter registry metadata could not be read.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2042E 

Message: An archive of the "{0}" starter could not be created.

Go to [[IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2043E 

Message: The template metadata URL, {0}, is invalid. Error: "{1}".

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2044E 

Message: The starter metadata URL {0} is invalid because the host name is invalid.

The host name must include only alphanumeric and dash characters.

Try again.





 BXNUI2045E 

Message: The "{0}" service doesn't exist.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2046E 

Message: The service categories could not be read.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2047E 

Message: The "{0}" service exists.
Why can't I log in to an account I was recently added to? 

You need to accept an invitation to become an active user in a new IBM Cloud® account.

  What’s happening 

You can't log in to an account you were recently added to.

  Why it’s happening 

This problem can commonly occur by one of the following reasons:



*  You didn't accept the invitation to join the account.
*  The invitation expired. You have 30 days to accept an invitation.
*  The inviter canceled your invitation.



  How to fix it 

Complete the following steps to accept the invitation. If your invitation expired, contact the inviter or the account owner.



*  If you're new to IBM Cloud®, you receive an email that contains all the information you need. Click the invitation link to join the account.
*  As an existing member of IBM Cloud®, you can accept the invitation in your notifications, by email, or by using the CLI to onboard to the new account. To accept invitations in the CLI, use the [ibmcloud login](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_cliaccept-invitation-to-join-a-new-account-) command.



After you completed all the steps and you still get an error, contact [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).
parameters = jsonencode([])
}
}

* How do I associate a public gateway while creating multiple zones with a Subnet for each zone?


{

"StatusCode": 400,
"Headers": {

"Cache-Control": ["max-age=0, no-cache, no-store, must-revalidate"],
"Cf-Cache-Status": ["DYNAMIC"],
"Cf-Ray": ["6ab6a5e86ac41b69-DEL"],
"Connection": ["keep-alive"],
"Content-Length": ["261"],
"Content-Type": ["application/json; charset=utf-8"],
"Date": ["Tue, 09 Nov 2021 11:19:47 GMT"],
"Expect-Ct": ["max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct""],
"Expires": ["-1"],
"Pragma": ["no-cache"],
"Server": ["cloudflare"],
"Strict-Transport-Security": ["max-age=31536000; includeSubDomains"],
"Vary": ["Accept-Encoding"],
"X-Content-Type-Options": ["nosniff"],
"X-Request-Id": ["37b94c40-a4bf-4942-a0da-45dc5434d610"],
"X-Xss-Protection": ["1; mode=block"]
},
"Result": {

"errors": [{

"code": "bad_field",
"message": "Failed to attach public gateway of different zone to the subnet",
"target": {

"name": "public_gateway.id",
BXNUI2052E 

Message: The login attempt failed.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2053E 

Message: The login attempt failed because the access token request could not be encoded.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2054E 

Message: IBM Cloud requires authorization with scope {0}.

Try logging in again and providing the requested authorization.





 BXNUI2055E 

Message: The attempt to connect to Cloud Foundry failed because of the following exception: "{0}."

If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2056E 

Message: Your user information could not be retrieved.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2057E 

Message: JSON cannot be pretty-printed.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2058E 

Message: The request is unauthorized because it does not have the required scope, {0}.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2059E 

Message: A service cannot be published with "ibm_created" or "3rd_party" tags. These tags can be set only by an administrator.





 BXNUI2060E 

Message: The usage information could not be processed.

If you see this message again, go to the [IBM Cloud status page](https://cloud.ibm.com/status?selected=status) to check whether a service or component has an issue.
Refresh the Red Hat packages on your machine.

subscription-manager refresh

If you see an error such as Network error, unable to connect to server. Please see /var/log/rhsm/rhsm.log for more information., check the security group and other network settings for your machine to make sure that you have connectivity to the internet.
2. Enable the package repositories on your machine. For example, enable RHEL 8 package requirements.

subscription-manager repos --enable rhel-8-for-x86_64-appstream-rpms
subscription-manager repos --enable rhel-8-for-x86_64-baseos-rpms



2. Make sure that your machine meets the other [host minimum requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs), such as minimum CPU and memory sizes.
3. [Run the registration script](https://cloud.ibm.com/docs/satellite?topic=satellite-attach-hosts) on your machine again.
Restricting domains for account invitations 

You can restrict membership to your account based on the domain of the users that are added to your allowlist. This way, only users with a specific domain or domains can be invited to the account. To update this setting, you must be assigned the editor role or higher on the IAM Identity Service.

Domain restrictions are implemented by setting email patterns. For example, @ibm.com, @.ibm.com, @?.ibm.com. A single asterisk * represents any sequence of zero or more characters in a string, except the sequence ends if a period . or at sign @ is found. A double asterisk  represents any sequence of zero or more characters in the string without limit. A question mark ? represents any single character.

Let's take a closer look at the example @.ibm.com. The username part of the email address specifies . Since the sequence is not limited by ., an email address like my.name.is.bob@us.ibm.com is valid. The subdomain us is also valid because it is a string of letters, where the sequence ends with ..



  Enabling domain restrictions for account invitations 

To enable domain restrictions for account invitations, complete the following steps:



1.  In the IBM Cloud console, go to Manage > Access (IAM) > Settings.
2.  In the Account section, enable the User domains setting.
3.  Enter the domains that can access the account. Any domain that isn't added to this list is restricted.
4.  Click Add.
5.  Click Save.







  Disabling domain restrictions for account invitations 

When you disable the User domains setting, you can send account invitations to any domain, which removes the previously set allowed domain access. To disable restrictions on specific domains, complete the following steps:



1.  Go to Manage > Access (IAM) > Settings in the IBM Cloud console.
2.  In the Account section, disable the User domains setting.
3.  Select an option for disabling the setting.



1.  To disable the setting and save the allowlist of domains, select Disable and save domains.
2.  To disable the setting and delete the allowlist, select Disable and delete domains.



4.  Click Yes.
It is not necessary that the app or job exist when you create the event subscription with the console. However, when the subscription is created, the status of the subscription reflects that the consumer does not exist. You must create the app or job before the subscription is in a ready state and can receive events through this subscription. For this example, use the kafka-receiver-app application that references the icr.io/codeengine/kafka-receiver image. If your app does not exist, provide the name of your application and [create your application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-appdeploy-app-console) after you create the Kafka subscription. For applications only, you can optionally specify a path. By default, events are routed to the root URL of the destination application. You can send events to a different destination within the app by specifying a path. For example, if your subscription path specifies /events, the events are sent to https://<base application URL>/events. Click Next to proceed.
8. For Summary, review the settings for your Kafka event subscription and make changes, if needed. When ready, click Create to create the Kafka subscription.







 Sending events to the receiving app from the console 

Now that your Kafka event subscription, which references the kafka-receiver-app application, is created, use the kafka-sender-app to send message events to the receiver application.



1. Start logging for the receiver application to [view application logs from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-view-logsview-applogs-ui) to see events.
2. (optional) Start logging for the sender application to [view application logs from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-view-logsview-applogs-ui) to see information about events that are sent.
3.
exampledb=> SELECT * FROM list_subscriptions();

disable_subscription

Arguments:
subscription_name Name the subscription channel to disable
db_name The name of the replicated database

Usage:
exampledb=> SELECT disable_subscription('subs1','exampledb');

enable_subscription

Arguments:
subscription_name Name the subscription channel to enable
db_name The name of the replicated database

Usage:
exampledb=> SELECT enable_subscription('subs1','exampledb');

refresh_subscription

This function is used to refresh a subscription on the subscriber after changes are made on the publisher, like adding or removing a table.

Arguments:
subscription_name Name the subscription channel to refresh
db_name The name of the replicated database

Usage:
exampledb=> SELECT refresh_subscription('subs1','exampledb');







 Setting up Logical Replication on the Publisher 

To configure your external PostgreSQL as a publisher,



* Edit your local pg_hba.conf and add the following

hostssl replication replicator 0.0.0.0/0 md5
hostssl all replicator 0.0.0.0/0 md5

The "replicator" field is the user that you set up with the [PostgreSQL privilege REPLICATION](https://www.postgresql.org/docs/current/sql-createrole.htmlreplication).
* Edit your local postgresql.conf with the required [logical replication configuration](https://www.postgresql.org/docs/current/logical-replication-config.html). Set wal_level to 'logical', and set listen_addresses='' to accept connections from any host.

listen_addresses=''
wal_level = logical
* Restart your PostgreSQL server.



Now you can define a publisher on the database and add the tables that you want to replicate to the subscriber.