Re: [DISCUSS] Notifications for ignite-3 repository
Actually a first attempt was not successful. And the reason was "main" branch name. I asked INFRA folks assistance and as I understood they configured GitBox HEAD to be "main" branch HEAD. I suppose it did the trick and we should not see ignite-3 PR notifications on dev-list anymore. 2020-12-22 13:05 GMT+03:00, Ivan Pavlukhin : > Ticket was merged. Thanks to all participants. > > 2020-12-21 10:12 GMT+03:00, Ivan Pavlukhin : >> Folks, >> >> I will merge the PR tomorrow if there is no objections. >> >> 2020-12-19 0:56 GMT+03:00, Valentin Kulichenko >> : >>> Folks, >>> >>> Can someone take a look at this PR? I'm generally OK with the change, >>> but >>> I'm not familiar with the mechanisms used here. >>> >>> -Val >>> >>> On Thu, Dec 17, 2020 at 11:16 PM Ivan Pavlukhin >>> wrote: >>> Igniters, I noticed notifications about PRs in ignite-3 repository sent to dev-list. I suppose we should configure notifications similar to main ignite repository. I prepared a ticket [1] and PR for this. Please review. [1] https://issues.apache.org/jira/browse/IGNITE-13875 -- Best regards, Ivan Pavlukhin >>> >> >> >> -- >> >> Best regards, >> Ivan Pavlukhin >> > > > -- > > Best regards, > Ivan Pavlukhin > -- Best regards, Ivan Pavlukhin
[jira] [Created] (IGNITE-13895) SSL usage in ducktape tests
Sergei Ryzhov created IGNITE-13895: -- Summary: SSL usage in ducktape tests Key: IGNITE-13895 URL: https://issues.apache.org/jira/browse/IGNITE-13895 Project: Ignite Issue Type: Task Reporter: Sergei Ryzhov Assignee: Sergei Ryzhov SSL usage in ducktape tests -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (IGNITE-13896) Javadoc build failed due to new not grouped packages
Aleksey Plekhanov created IGNITE-13896:
--
Summary: Javadoc build failed due to new not grouped packages
Key: IGNITE-13896
URL: https://issues.apache.org/jira/browse/IGNITE-13896
Project: Ignite
Issue Type: Bug
Affects Versions: 2.10
Reporter: Aleksey Plekhanov
Assignee: Aleksey Plekhanov
Fix For: 2.10
Fail on:
{noformat}
mvn initialize -Pjavadoc
{noformat}
Error:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-antrun-plugin:1.7:run
(javadoc-postprocessing-new) on project apache-ignite: An Ant BuildException
has occured: Execution failed due to: 'Other Packages' section should not be
present, all packages should have corresponding documentation groups:
/Users/sbt-plekhanov-as/IdeaProjects/ignite/target/javadoc/core/overview-summary.html;Please
add packages description to parent/pom.xml into (maven-javadoc-plugin)
/ /
{noformat}
Packages in the "Other packages" section:
{noformat}
org.apache.ignite.kubernetes.configuration
org.apache.ignite.maintenance
{noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13897) .NET Service can't assign correct type to passed array parameters
Yaroslav Molochkov created IGNITE-13897:
---
Summary: .NET Service can't assign correct type to passed array
parameters
Key: IGNITE-13897
URL: https://issues.apache.org/jira/browse/IGNITE-13897
Project: Ignite
Issue Type: Bug
Components: platforms
Affects Versions: 2.9
Reporter: Yaroslav Molochkov
Assignee: Yaroslav Molochkov
This issue relates to IGNITE-12823.
Ignite client calls deployed service and fails with the following exception:
{code:java}
Apache.Ignite.Core.Common.JavaException: class
org.apache.ignite.IgniteException: Failed to invoke proxy: there is no method
'processSomething' in type 'SomeService' with (Int32, Object[]) arguments
at
org.apache.ignite.internal.processors.platform.callback.PlatformCallbackUtils.inLongOutLong(Native
Method)
at
org.apache.ignite.internal.processors.platform.callback.PlatformCallbackGateway.serviceInvokeMethod(PlatformCallbackGateway.java:942)
at
org.apache.ignite.internal.processors.platform.services.PlatformAbstractService.invokeMethod(PlatformAbstractService.java:214)
at
org.apache.ignite.internal.processors.platform.services.PlatformAbstractService.invokeMethod(PlatformAbstractService.java:185)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.apache.ignite.internal.processors.service.GridServiceProxy$ServiceProxyCallable.callService(GridServiceProxy.java:491)
at
org.apache.ignite.internal.processors.service.GridServiceProxy$ServiceProxyCallable.call(GridServiceProxy.java:469)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1847)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:598)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:7077)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:592)
at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:521)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1368)
at
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:2130)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1907)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1528)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$5300(GridIoManager.java:241)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.execute(GridIoManager.java:1421)
at
org.apache.ignite.internal.managers.communication.TraceRunnable.run(TraceRunnable.java:55)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{code}
Service interface itself looks like this:
{code:java}
public interface SomeService
{
int processSomething(int foo, Parameter[] parameters);
}
public class Parameter
{
private int id;
private ParamValue[] _values;
public Parameter(int id, ParamValue[] _values)
{
this.id = id;
this._values = _values;
}
}
public class ParamValue
{
private int id;
private double val;
public ParamValue(int id, double val)
{
this.id = id;
this.val = val;
}
}
{code}
And the call to the service:
{code:java}
var svc = igniteServices.GetServiceProxy(name, false);
var result = svc.processSomething(id, parameters);
{code}
Now, if this is a server node then call is successful. If the call goes from
the client node then we'll get the error above.
Fix in IGNITE-12823 addresses particular code execution path where the
execution flow goes through PlatformServices class. Yet in this case our code
goes through PlatformAbstractService. I think that the fix of casting arrays
should be positioned a little bit lower in the call stack (or higher in code
hierarchy) so all execution paths are covered simultaneously.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[MTCGA]: new failures in builds [5802237] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *New Critical Failure in master-nightly MVCC Cache 7 https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_MvccCache7?branch=%3Cdefault%3E Changes may lead to failure were done by - vd_pyatkov https://ci.ignite.apache.org/viewModification.html?modId=912714 - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 21:52:26 23-12-2020
Re: [DISCUSS] Notifications for ignite-3 repository
Ivan, thank you for fixing this! On Wed, Dec 23, 2020 at 11:13 AM Ivan Pavlukhin wrote: > Actually a first attempt was not successful. And the reason was "main" > branch name. I asked INFRA folks assistance and as I understood they > configured GitBox HEAD to be "main" branch HEAD. I suppose it did the > trick and we should not see ignite-3 PR notifications on dev-list > anymore. > > 2020-12-22 13:05 GMT+03:00, Ivan Pavlukhin : > > Ticket was merged. Thanks to all participants. > > > > 2020-12-21 10:12 GMT+03:00, Ivan Pavlukhin : > >> Folks, > >> > >> I will merge the PR tomorrow if there is no objections. > >> > >> 2020-12-19 0:56 GMT+03:00, Valentin Kulichenko > >> : > >>> Folks, > >>> > >>> Can someone take a look at this PR? I'm generally OK with the change, > >>> but > >>> I'm not familiar with the mechanisms used here. > >>> > >>> -Val > >>> > >>> On Thu, Dec 17, 2020 at 11:16 PM Ivan Pavlukhin > >>> wrote: > >>> > Igniters, > > I noticed notifications about PRs in ignite-3 repository sent to > dev-list. I suppose we should configure notifications similar to main > ignite repository. I prepared a ticket [1] and PR for this. Please > review. > > [1] https://issues.apache.org/jira/browse/IGNITE-13875 > > -- > > Best regards, > Ivan Pavlukhin > > >>> > >> > >> > >> -- > >> > >> Best regards, > >> Ivan Pavlukhin > >> > > > > > > -- > > > > Best regards, > > Ivan Pavlukhin > > > > > -- > > Best regards, > Ivan Pavlukhin >
[jira] [Created] (IGNITE-13898) Change default location for ignite-bin and ignite-work folders
Valentin Kulichenko created IGNITE-13898:
Summary: Change default location for ignite-bin and ignite-work
folders
Key: IGNITE-13898
URL: https://issues.apache.org/jira/browse/IGNITE-13898
Project: Ignite
Issue Type: Sub-task
Reporter: Valentin Kulichenko
Currently, {{ignite-bin}} and {{ignite-work}} folders are created in the
current directory. This might be confusing because the script can be run out of
any folder, which makes the behavior unpredictable.
Let's create these folders somewhere under {{$HOME}} instead.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (IGNITE-13899) Remove demo artifacts from the CLI module
Valentin Kulichenko created IGNITE-13899:
Summary: Remove demo artifacts from the CLI module
Key: IGNITE-13899
URL: https://issues.apache.org/jira/browse/IGNITE-13899
Project: Ignite
Issue Type: Sub-task
Reporter: Valentin Kulichenko
The CLI module is currently named {{cli-demo}} and also contains the
{{demo-module-all}} submodule.
This needs to be cleaned up. Let's also check for any other demo artifacts that
might be there.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
