[PLUGIN-1953] Support for client credentials Grant type #910
Annotations
7 errors and 1 warning
|
build
Process completed with exit code 1.
|
|
SalesforceSourceConfigTest.testPKChunkWithRestrictedQuery:
SalesforceSourceConfigTest#L248
No constructor found in class 'io.cdap.plugin.salesforce.plugin.connector.SalesforceConnectorConfig' with parameter types: [ java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, null, null, null, java.lang.String, java.lang.Long, java.lang.Long, java.lang.Integer, java.lang.Boolean ].
|
|
Test mechanism:
Test mechanism#L1
Misplaced or misused argument matcher detected here:
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:284)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:284)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:285)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:285)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:286)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:286)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:287)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:287)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:287)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:288)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:288)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:289)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:289)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:290)
You cannot use argument matchers outside of verification or stubbing.
Examples of correct usage of argument matchers:
when(mock.get(anyInt())).thenReturn(null);
doThrow(new RuntimeException()).when(mock).someVoidMethod(anyObject());
verify(mock).someMethod(contains("foo"))
This message may appear after an NullPointerException if the last matcher is returning an object
like any() but the stubbed method signature expect a primitive argument, in this case,
use primitive alternatives.
when(mock.get(any())); // bad use, will raise NPE
when(mock.get(anyInt())); // correct usage use
Also, this error might show up because you use argument matchers with methods that cannot be mocked.
Following methods *cannot* be stubbed/verified: final/private/equals()/hashCode().
Mocking methods declared on non-public parent classes is not supported.
|
|
SalesforceSourceConfigTest.testPKChunkWithChunkSizeAboveMax:
SalesforceSourceConfigTest#L267
No constructor found in class 'io.cdap.plugin.salesforce.plugin.connector.SalesforceConnectorConfig' with parameter types: [ java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, null, null, null, java.lang.String, java.lang.Long, java.lang.Long, java.lang.Integer, java.lang.Boolean ].
|
|
Test mechanism:
Test mechanism#L1
Misplaced or misused argument matcher detected here:
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:284)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:284)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:285)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:285)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:286)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:286)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:287)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:287)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:287)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:288)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:288)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:289)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:289)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:290)
You cannot use argument matchers outside of verification or stubbing.
Examples of correct usage of argument matchers:
when(mock.get(anyInt())).thenReturn(null);
doThrow(new RuntimeException()).when(mock).someVoidMethod(anyObject());
verify(mock).someMethod(contains("foo"))
This message may appear after an NullPointerException if the last matcher is returning an object
like any() but the stubbed method signature expect a primitive argument, in this case,
use primitive alternatives.
when(mock.get(any())); // bad use, will raise NPE
when(mock.get(anyInt())); // correct usage use
Also, this error might show up because you use argument matchers with methods that cannot be mocked.
Following methods *cannot* be stubbed/verified: final/private/equals()/hashCode().
Mocking methods declared on non-public parent classes is not supported.
|
|
SalesforceSourceConfigTest.testPKChunkWithChunkSizeBelowMin:
SalesforceSourceConfigTest#L277
No constructor found in class 'io.cdap.plugin.salesforce.plugin.connector.SalesforceConnectorConfig' with parameter types: [ java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, java.lang.String, null, null, null, java.lang.String, java.lang.Long, java.lang.Long, java.lang.Integer, java.lang.Boolean ].
|
|
Test mechanism:
Test mechanism#L1
Misplaced or misused argument matcher detected here:
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:284)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:284)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:285)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:285)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:286)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:286)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:287)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:287)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:287)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:288)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:288)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:289)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:289)
-> at io.cdap.plugin.salesforce.plugin.source.batch.SalesforceSourceConfigTest.testPKChunkInvalidConfig(SalesforceSourceConfigTest.java:290)
You cannot use argument matchers outside of verification or stubbing.
Examples of correct usage of argument matchers:
when(mock.get(anyInt())).thenReturn(null);
doThrow(new RuntimeException()).when(mock).someVoidMethod(anyObject());
verify(mock).someMethod(contains("foo"))
This message may appear after an NullPointerException if the last matcher is returning an object
like any() but the stubbed method signature expect a primitive argument, in this case,
use primitive alternatives.
when(mock.get(any())); // bad use, will raise NPE
when(mock.get(anyInt())); // correct usage use
Also, this error might show up because you use argument matchers with methods that cannot be mocked.
Following methods *cannot* be stubbed/verified: final/private/equals()/hashCode().
Mocking methods declared on non-public parent classes is not supported.
|
|
build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
reports-23837585944
|
117 KB |
sha256:010ac0062d952a08be6ce82a13a14f734ffeb4ce33037f04acd232e58fe8c05f
|
|