when I tested my smart contract in Kovan, the oracle (0xc57B33452b4F7BB189bB5AfaE9cc4aBa1f7a4FD8) listed in Contract Addresses failed to fulfill my request.
As I checked the failed transaction, I've found out that the signature in the InputData was fulfillOracleRequest2 whereas other successful transactions' InputData contained fulfillOracleRequest. So the root cause of the issue seems to be the discrepancy between ChainlinkClient's version(v0.8) and the oracle's version.
Does anybody know of any oracle compatible with ChainlinkClient v0.8 in Kovan?
I've basically gone through the official tutorial to Use Any API except for the version of ChainlinkClient(The tutorial noted v0.6 but I used v0.8).
By updating #chainlink/contracts from 0.1.7 to 0.2.1 (and by adjusting the path to ChainlinkClient.sol), my requests started to get fulfilled.
Related
We're using odoo.sh platform with odoo14. The installed wkhtmltopdf is wkhtmltopdf_paas_wrapper 0.12.5, we can't upgrade to 0.12.6 because the access is very limited we cant use 'sudo' to apt-install. To temporarily solve this, we decided to use the 0.12.5 version. But it returns "Unable to call host printing service (HTTPError)" even with the right arguments. I've already tried it with the staging and production server, but still the same result. The ticket I've sent hasn't been replied to yet. This is so frustrating, I'm going bonkers...please help.
here's a screenshot:
ps: unrecognized argument error was intentional so I can display the available args. I've also crossed out the project domain. Thank you
Apparently, to properly execute the package, it should not have been "wkhtmltopdf" but instead "wkhtmltopdf.bin". I've overridden the ir_actions_report.py to change the package name. Here's the snippet of the original source code:
They shouldve known better, its a paid platform.
We have Oracle11gR1 and Oracle18c.
Perl clients(11.7.0.1) have to access to both version so far.
But Oracle client(11.7.0.1) were recommended to upgrade to new one(12.1.0.2)
according to Doc ID 207303.1 - 'Client / Server Interoperability Support Matrix '
I'd like to hava 2 version of DBD:Oracle on the same clinet.
one for 11.7.0.1.
another for 12.1.0.2.
Because We can back to stable one immediately if new one caused problems.
How can I do that?
or
Impossible? Why?
I was successfully to install the following,
oracle-instantclient12.1-devel-12.1.0.2.0-1.i386.rpm
oracle-instantclient12.1-basic-12.1.0.2.0-1.i386.rpm
After re-install DBD::Oracle,V$SESSION_CONNECT_INFO shows them to '12.1.0.2'.that's I expected.
My Question is
How to switch back and force between 2 version of Oracle clinet of DBD::Oracle for just in case.
Because We can back to stable one immediataly if new one caused problems.
Ideally, By changing $ORACLE_HOME or $LD_LIBRARY_PATH could be achieved I hope.
Otherwise, A lot of task will be needed like that changing $ORACLE_HOME or $LD_LIBRARY_PATH and re-complile DBD:Oracle to switch them in everytimes.
Does anyone have good advise?
Thanks in advance.
I have 2 questions:
Can I run spring-data-elastic v4.0.1.RELEASE (with org.elasticsearch:elasticsearch 7.6.2 ) with ES client running on 7.4.0??? If not, what combination can I use for 7.4.0 client? We are migrating to AWS and I need to use 7.4.0 version of client.
I have parent/child relationship (configured as join datatype field). Could pls somebody provide a documentation or explain, how to use either ElasticsearchRestTemplate or ElasticsearchOperations to correctly insert/update both parent and child records?
Thank you.
Best regards,
Robert
ad 1): from the Elasticsearch documentation I can't at the moment find anything in the breaking changes sections that would prevent using a 7.4.0 client library, but that does not mean there aren't any. But that does not mean that there aren't any. Recently there was a breaking change in the Java classes (from 7.7 to 7.8) and I got the information:
our compatability focus is on the HTTP APIs and we don’t offer any guarantees on the code itself. There’s more background here: https://github.com/elastic/elasticsearch/issues/22707#issuecomment-274163711
So I'd say, write a small test app and with the corresponding libraries, start a local ES 7.4 and test it.
ad 2): adding the join-type mapping ang implementing the corresponding inserts etc. is currently worked on and will hopefully be available in version 4.1.
I am able to connect to Db2 on z/OS with the IBM universal JDBC driver file db2jcc4.jar using IBM JDK 1.8 that is bundled with WebSphere 9. Every thing works fine and I can browse the catalog and execute queries. I used Squirrel SQL version 4.0.0.
But when I switch my JDK to the Open JDK 8 or 12 while keeping everything else the same, I get the following error. What should be done to fix this error? What is the difference between IBM JDK and Open JDK, which causes the DB2 connection to work with one JDK and fail with the other?
Here is one of matching articles of your case:
JDBC application may receive error "Security mechanism not supported"
https://www.ibm.com/support/pages/jdbc-application-may-receive-error-security-mechanism-not-supported
Resolving The Problem
Set the following property :
securityMechanism = ENCRYPTED_USER_PASSWORD_AND_DATA_SECURITY (13)
Alternatively you can set property retryWithAlternativeSecurityMechanism to YES(1).
Hope this helps.
According to IBM's documentation for their IBM Data Server Driver for JDBC and SQLJ, error code -4214 is an "Authorization failed" error -- and you know that much. But you can get more specific information about the problem if you call SQLException.getMessage. I think you may have done that already, but it's not entirely clear.
My semi-educated guess is that you haven't yet followed the configuration steps in IBM's driver documentation in the section "Configuring the Java Runtime Environment to Use SSL":
https://www.ibm.com/support/knowledgecenter/SSEPGG_11.5.0/com.ibm.db2.luw.apdv.java.doc/src/tpc/imjcc_t0054066.html
You'll have to apply some common sense knowledge to those instructions to adapt them for the OpenJDK, and this might not be an IBM supported combination depending on what/how you do it. If you can somehow use the IBMJSSE2 Provider, that'd be nice.
I think Mao and Mustaccio probably have the right ideas, and probably you're just missing the server certificate in your truststore. The instructions linked above walk you through how to configure that.
While installing Oracle fusion Middleware 11g web tier utilities at step 7 following error occurs and stops installation process.
Installation Failed. Prepare Session failed SEVERE:Values for the following variables could not be obtained from the command line or response file(s): MYORACLESUPPORT_USERNAME(MyOracleSupportUsername) Silent install cannot continue.
I could not figure out what is wrong , please help ...
The message suggests you're doing a silent install, so have you created/modified a response file as described in the documentation? The MYORACLESUPPORT_USERNAME is mentioned here, but its interaction with the other parameters isn't always obvious. There is more detail here.
Assuming you don't want to get security updates, you need to set DECLINE_SECURITY_UPDATES to TRUE (although I seem to recall having to supply the MSO credentials anyway, but not sure which version I saw that and it seemed like a bug). If you do want security updates then leave that as FALSE and set the MSO credentials to appropriate values.