When testing my rules on the Business Rules service on Bluemix, I get the following error:
"Unable to run test
Error when executing the ruleset /MyRuleApp/1.0/myrules/1.0
An error occurred while the rule session was called:
com.ibm.rules.res.xu.internal.XUException:
An error occurred during
the ruleset execution. ilog.rules.engine.IlrUserRuntimeException:
null object when invoking public void myMethod()"
I had misconstructed the input parameter (it was missing the opening brace):
"foo": {
"name": "foo",
"id": "bar"
}
}
Once I added the opening brace I could run the test successfully.
Related
The errror we get:-
An unknown server-side error occurred while processing the command. Original error: Cannot execute command waitFor, server reponse {
"isError": true,
"response": "Timeout while executing waitFor: TimeoutException after 0:00:20.000000: Future not completed\n",
"type": "_extensionType",
"method": "ext.flutter.driver"
}
refer this article for your error
https://github.com/appium-userland/appium-flutter-driver/issues/98
I'm having a go at creating my first data fusion pipeline.
The data is going from Google Cloud Storage csv file to Big Query.
I have created the pipeline and carried out a preview run which was successful but after deployment trying to run resulted in error.
I pretty much accepted all the default settings apart from obviously configuring my source and destination.
Error from Log ...
com.google.api.client.googleapis.json.GoogleJsonResponseException: 403
Forbidden
{
"code" : 403,
"errors" : [ {
"domain" : "global",
"message" : "Required 'compute.firewalls.list' permission for
'projects/xxxxxxxxxxx'",
"reason" : "forbidden"
} ],
"message" : "Required 'compute.firewalls.list' permission for
'projects/xxxxxxxxxx'"
}
After deployment run fails
Do note that as a part of creating an instance, you must set up permissions [0]. The role "Cloud Data Fusion API Service Agent" must be granted to the exact service account, as specified in that document, which has an email address that begins with "cloud-datafusion-management-sa#...".
Doing so should resolve your issue.
[0] : https://cloud.google.com/data-fusion/docs/how-to/create-instance#setting_up_permissions
I created the "UDO" & "UDT", register it using object registration wizard but whenever I try to access the table via Service Layer I am getting the following error can you one please let me know some solution on this :
{
"error": {
"code": -1000,
"message": {
"lang": "en-us",
"value": "Unknown entity."
}
}
}
Restart the service, and try again
/etc/init.d/b1s restart
Stop the service for about 2 minutes and then start it again:
/etc/init.d/b1s stop
...
/etc/init.d/b1s start
While following the steps in 'Deploying your chaincode from IBM Bluemix Blockchain documentation, I'm getting the following error:
Response Body
{
"jsonrpc": "2.0",
"error": {
"code": -32001,
"message": "Deployment failure",
"data": "Error when deploying chaincode: Error getting chaincode package bytes: Error getting code 'go get' failed with error: \"exit status 2\"\n# github.com/VrushaliW1/BluemixApp1\n/opt/gopath/_usercode_/583850129/src/github.com/VrushaliW1/BluemixApp1/Asgn1.go:38: stub.GetFunctionAndParameters undefined (type shim.ChaincodeStubInterface has no field or method GetFunctionAndParameters)\n/opt/gopath/_usercode_/583850129/src/github.com/VrushaliW1/BluemixApp1/Asgn1.go:75: stub.GetFunctionAndParameters undefined (type shim.ChaincodeStubInterface has no field or method GetFunctionAndParameters)\n/opt/gopath/_usercode_/583850129/src/github.com/VrushaliW1/BluemixApp1/Asgn1.go:193: cannot use new(SimpleChaincode) (type *SimpleChaincode) as type shim.Chaincode in argument to shim.Start:\n\t*SimpleChaincode does not implement shim.Chaincode (wrong type for Init method)\n\t\thave Init(shim.ChaincodeStubInterface) ([]byte, error)\n\t\twant Init(shim.ChaincodeStubInterface, string, []string) ([]byte, error)\n"
},
"id": 0
}
Tried referring to the links :
IBM Blockchain (Hyperledger) - "Error when deploying chaincode"
"Error getting chaincode package bytes" when deploying chaincode on hyperledger via REST
The go code build rightly but still I'm getting this failure error with 'Shim interface' issue. Is still anything wrong in the Go code?
The issue appears to be related to the Go code in the Asgn1.go file. The message is indicating that the signature of the Init function was Init(shim.ChaincodeStubInterface) ([]byte, error) rather than Init(shim.ChaincodeStubInterface, string, []string) ([]byte, error).
For an example chaincode that works with Hyperledger Fabric version 0.6.1, refer to the “Learn Chaincode” example chaincode at https://github.com/IBM-Blockchain/learn-chaincode/blob/v2.0/finished/chaincode_finished.go. Note that the signature of the Init function is Init(stub shim.ChaincodeStubInterface, function string, args []string) ([]byte, error).
I'm running a simple Hyperledger network on Bluemix. I can deploy, and invoke, but not query. The chaincode function, Init sets up a value for var, "abc" ... stub.PutState("abc", []byte(strconv.Itoa(Aval)))
I should be able to query "abc" as validation the code is ready to use. Instead, I'm seeing this error:
"... Error:Failed to launch chaincode spec(Could not get deployment
transaction for - LedgerError - ResourceNotFound:
ledger: resource not found)"
The query json is:
{
"jsonrpc": "2.0",
"method": "query",
"params": {
"type": 1,
"chaincodeID": {
"name": "my chaincode id"
},
"ctorMsg": {
"function": "read",
"args": [
"abc"
]
},
"secureContext": "user_type1_3"
},
"id": 0
}
The following is the list of probable causes of the error
Could not get deployment transaction for - LedgerError -
ResourceNotFound: ledger: resource not found
1. Chaincode did not get deployed correctly. To check if the
chaincode was deployed correctly, you need to check the peer logs to
see if there were any errors when the deploy transaction was sent.
2. Chaincode got deployed correctly, but the consensus mechanism hasnt
yet completed. You should ideally wait for a few minutes after
deploying a chaincode before you try to query it.
3. The Chaincode got deployed, but the chaincode ID/name specified
while trying to send a query is incorrect. You need to make sure you
use the same chaincode ID that comes in the response when you deploy
a chaincode.