Definitely we have to change something here.
I would use a manual triggering granting access through a special
account available only to contributors and commiters.
--
Denis
On 8/27/2015 9:51 AM, Valentin Kulichenko wrote:
Igniters,
We currently have >200 builds in TC queue and it will tak
Igniters,
We currently have >200 builds in TC queue and it will take around 15 hours
to run everything. This is becoming unusable.
It seems to me that it got worse after we switched to pull requests,
because builds are triggered each time someone pushes to the branch that is
tied up with existing
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/42
Ignite 264
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/agoncharuk/ignite ignite-264
Alternatively you can review and apply these changes
On 26.08.2015 21:02, Dmitriy Setrakyan wrote:
> On Wed, Aug 26, 2015 at 9:15 PM, Konstantin Boudnik wrote:
>
>> On Wed, Aug 26, 2015 at 09:07PM, Dmitriy Setrakyan wrote:
>>> On Wed, Aug 26, 2015 at 8:44 PM, Konstantin Boudnik
>> wrote:
Just as a friendly reminder: readme.io hosting still ope
On Wed, Aug 26, 2015 at 9:15 PM, Konstantin Boudnik wrote:
> On Wed, Aug 26, 2015 at 09:07PM, Dmitriy Setrakyan wrote:
> > On Wed, Aug 26, 2015 at 8:44 PM, Konstantin Boudnik
> wrote:
> >
> > > Just as a friendly reminder: readme.io hosting still opens us to the
> > > issue we've been
> > > disc
Thanks Artem! This goes a long way in improving the contribution process in
the project.
D.
On Wed, Aug 26, 2015 at 9:06 PM, Artem Shutak wrote:
> Folks,
>
> I've implemented a script for applying pull-requests by commiters and
> updated info about pull-request contribution way. I think, it sho
GitHub user ashutakGG opened a pull request:
https://github.com/apache/ignite/pull/41
IGNITE-1217: add suffix to commit comment " - Fixes #."
ignite-1217: add suffix to commit comment " - Fixes #."
You can merge this pull request into a Git repository by running:
$ git pull htt
On Wed, Aug 26, 2015 at 09:07PM, Dmitriy Setrakyan wrote:
> On Wed, Aug 26, 2015 at 8:44 PM, Konstantin Boudnik wrote:
>
> > Just as a friendly reminder: readme.io hosting still opens us to the
> > issue we've been
> > discussing at length. Namely - the source of the documentation isn't
> > hoste
+1 for 'instanceName'. 'nodeName' looks confusing as well - I would think
that it should be unique among all nodes.
-Val
On Wed, Aug 26, 2015 at 2:25 AM, Raul Kripalani wrote:
> Agree. The term grid to refer to a single node is very confusing.
> On 19 Aug 2015 08:58, "Semyon Boikov" wrote:
>
>
On Wed, Aug 26, 2015 at 8:44 PM, Konstantin Boudnik wrote:
> Just as a friendly reminder: readme.io hosting still opens us to the
> issue we've been
> discussing at length. Namely - the source of the documentation isn't
> hosted on
> the Apache premises. I remember there were some conversations w
Folks,
I've implemented a script for applying pull-requests by commiters and
updated info about pull-request contribution way. I think, it should be
clear for everyone now. Feel free to comment:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute.
I didn't know about github featu
Yup, big +1's on both points: the versioning schema (thanks a bunch for
digging it up, Brane!) and sticking to a stricter compatibility rules.
Integers are cheap and abundant, but conveying the clear message that say 2.0
isn't compatible with 1.4 because of XYZ in hadoop module is important. It is
Just as a friendly reminder: readme.io hosting still opens us to the issue
we've been
discussing at length. Namely - the source of the documentation isn't hosted on
the Apache premises. I remember there were some conversations with readme.io
folks to add some extras for the imports or something li
On 26.08.2015 15:56, Vladimir Ozerov wrote:
> One more important thing here - distinction between overall compatibility
> and module compatibility. We may face serious bugs which severely affects
> single module/subsystem and fix will break backward ocmpatibility only on
> of that module.
> E.g. cu
I've implemented java preview for cluster and caches screens (metadata
screen will be implemented shortly).
Andrey Novikov, added mockup image for cache metadata (
https://issues.apache.org/jira/browse/IGNITE-1148)
Feedback are very welcome! Just go to http://104.197.2.239 and play with
Web Contr
Hi Devs,
Can anyone give me some hints on the bug
https://issues.apache.org/jira/browse/IGNITE-881
I am going to pick it up.
Thanks,
kcheng
Hi Alexey,
Thank you very much!
I did the changes according your comments;
Dmitriy & Yako can you help to review the code?
https://github.com/apache/ignite/pull/35
Thanks,
kcheng
On Wed, Aug 26, 2015 at 2:17 PM, Alexey Goncharuk <
alexey.goncha...@gmail.com> wrote:
> Ken, I added comments to
One more important thing here - distinction between overall compatibility
and module compatibility. We may face serious bugs which severely affects
single module/subsystem and fix will break backward ocmpatibility only on
of that module.
E.g. currently in IGFS file might be locked for write forever
Vladimir Ozerov created IGNITE-1309:
---
Summary: Platforms: move affinity to Ignite.
Key: IGNITE-1309
URL: https://issues.apache.org/jira/browse/IGNITE-1309
Project: Ignite
Issue Type: Sub-ta
AFAIK currently "Suggest Edit" works well on readme.io.
If someone wants to introduce a new topic, he can ask someone to do that on
dev/user lists.
Sergi
2015-08-26 14:09 GMT+03:00 Alexey Kuznetsov :
> I think contributor should provide at least some text file with a feature
> description.
> But
Github user sboikov closed the pull request at:
https://github.com/apache/ignite/pull/20
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
GitHub user sboikov opened a pull request:
https://github.com/apache/ignite/pull/40
ignite-1307 Do not complete prepare future with null result
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sboikov/incubator-ignite ignite-1307
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/38
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
GitHub user iveselovskiy opened a pull request:
https://github.com/apache/ignite/pull/39
IGNITE-1299: retry file meta unlock transactions introduced.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/iveselovskiy/ignite ignite-1299
Vladimir Ozerov created IGNITE-1308:
---
Summary: Platforms: Move queries to Ignite.
Key: IGNITE-1308
URL: https://issues.apache.org/jira/browse/IGNITE-1308
Project: Ignite
Issue Type: Sub-tas
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/38
Ignite 1302
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-1302
Alternatively you can review and apply these changes
I think contributor should provide at least some text file with a feature
description.
But collaboration on readme.io is a better approach.
I don't know it is possible to introduce new topics on readme.io?
I know that it is possible to suggest "changes".
We could have a special "landing page" for n
Ivan Veselovsky created IGNITE-1307:
---
Summary: NPE in
org.apache.ignite.internal.processors.cache.distributed.near.GridNearOptimisticTxPrepareFuture.MiniFuture#onResult(java.util.UUID,
org.apache.ignite.internal.processors.cache.distributed.ne
Vladimir Ozerov created IGNITE-1306:
---
Summary: Platforms: Move base target class to Ignite.
Key: IGNITE-1306
URL: https://issues.apache.org/jira/browse/IGNITE-1306
Project: Ignite
Issue Typ
GitHub user dmagda opened a pull request:
https://github.com/apache/ignite/pull/37
Portables: optimize cache related implementation and make it backward
compatible
At the Ignite's layer now it's possible to register additional classes
outside of GridPortableContext.
You can merge
Ivan Veselovsky created IGNITE-1305:
---
Summary: IGFS: file meta should be unlocked even if the node is
stopping
Key: IGNITE-1305
URL: https://issues.apache.org/jira/browse/IGNITE-1305
Project: Ignite
Agree. The term grid to refer to a single node is very confusing.
On 19 Aug 2015 08:58, "Semyon Boikov" wrote:
> In my opinion this propery just should be renamed to 'nodeName'.
> Possibility to set node name is very useful in our tests. As I see
> 'setNodeId' is already deprecated in IgniteConfi
I think `instanceName` is good enough (if it will have a proper javadoc).
Sergi
2015-08-26 9:24 GMT+03:00 Semyon Boikov :
> We can add 'nodeName' on ClusterNode API, it is very easy to implement
> since node name is already stored in node attributes.
>
> On Wed, Aug 26, 2015 at 4:44 AM, Dmitriy
Ivan Veselovsky created IGNITE-1304:
---
Summary: Async cache operations in IGFS may cause deadlock related
to topology update
Key: IGNITE-1304
URL: https://issues.apache.org/jira/browse/IGNITE-1304
Pr
Github user ptupitsyn closed the pull request at:
https://github.com/apache/ignite/pull/36
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
Vladimir Ozerov created IGNITE-1303:
---
Summary: Platforms: abstract-out platform context.
Key: IGNITE-1303
URL: https://issues.apache.org/jira/browse/IGNITE-1303
Project: Ignite
Issue Type:
Pavel Tupitsyn created IGNITE-1302:
---
Summary: Platforms .Net: Move common & collections stuff to Ignite
Key: IGNITE-1302
URL: https://issues.apache.org/jira/browse/IGNITE-1302
Project: Ignite
GitHub user ptupitsyn opened a pull request:
https://github.com/apache/ignite/pull/36
IGNITE-1292 Platforms .Net: Move handle registry to Ignite.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ptupitsyn/ignite ignite-1292
Alter
Denis Magda created IGNITE-1301:
---
Summary: Portables: keep portable protocol version in nodes
attributes
Key: IGNITE-1301
URL: https://issues.apache.org/jira/browse/IGNITE-1301
Project: Ignite
I believe that the current contribution process does not require
contributors to enhance/modify the user guide accordingly.
Do you think it would make sense to add this as a requirement to the
process?
Or are committers willing to take care of these docs in their entirety?
Usually it's most effic
Github user iveselovskiy closed the pull request at:
https://github.com/apache/ignite/pull/34
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
On 26.08.2015 08:54, Alexey Goncharuk wrote:
> This particular change does not break the compatibility (a new method is
> being added to the public API), however I am +1 for adding these principles
> to the dev documentation.
Way back when Ignite was still a podling I pointed out this:
http:/
42 matches
Mail list logo
