+ dev list
Vladimir, Igniters,
Don't we wipe out the metadata on a cache destroy? Is it an issue or done
on purpose?
--
Denis
On Wed, Oct 31, 2018 at 11:28 AM wt wrote:
> i am testing code and part of my tests is adding\removing tables. In one of
> the tests i add a table then destroy it
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
Hi Stan,
Thanks for the extensive analysis. Alex G. could you please step in and
share your thoughts. Seems it's time to revisit IEP-4 and prioritize the
gaps.
--
Denis
On Wed, Oct 31, 2018 at 7:56 AM Stanislav Lukyanov
wrote:
> Hi Igniters,
>
> I've been looking into various scenarios of
GitHub user antonovsergey93 opened a pull request:
https://github.com/apache/ignite/pull/5250
IGNITE-10134 fix bug in --cache list --config command.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Nikolai Kulagin created IGNITE-10137:
Summary: [TC Bot] Add button 'Expand all' on 'PR failures' page
Key: IGNITE-10137
URL: https://issues.apache.org/jira/browse/IGNITE-10137
Project: Ignite
Hi Vyacheslav,
I'm sorry I almost gave up with this donation
http://apache-ignite-developers.2346864.n4.nabble.com/Re-Place-Ignite-Abbrev-Plugin-to-ASF-Ignite-supplementary-git-repo-tp32745p32764.html
because
we need someone to sign a software grant agreement, but there were several
people who
I've double checked, we are really able to use IDEA inspection's to
inspect abbreviations by inspection's structure search and replace
templates.
It rather not intuitive and requires complex regex patterns.
Also, at first sight, it shouldn't be difficult to work with the
project's local
Sergey Kozlov created IGNITE-10136:
--
Summary: NPE in PartitionUpdateCountersMessage
Key: IGNITE-10136
URL: https://issues.apache.org/jira/browse/IGNITE-10136
Project: Ignite
Issue Type: Bug
David Harvey created IGNITE-10135:
-
Summary: Documentation link to
ClusterNodeAttributeAffinityBackupFilter
Key: IGNITE-10135
URL: https://issues.apache.org/jira/browse/IGNITE-10135
Project: Ignite
Hi Igniters,
I would like to share with Apache Ignite community a slightly updated
comittership bar guide. It is a not strict rule, but a recommendation:
https://cwiki.apache.org/confluence/display/IGNITE/Committership+Bar+Guidance
There were no significant changes. PMC agreed to avoid counting
IGNITE-9365 Force backups to different AWS availability zones using only
Spring XML
This deserves documentation enhancements:
https://apacheignite.readme.io/docs/affinity-collocation
What is the mechanism for proposing an update for 2.7?
On Fri, Nov 2, 2018 at 6:31 AM Andrey Kuznetsov wrote:
ARomantsov created IGNITE-10134:
---
Summary: control.sh --cache list . --config not working on big
cache setup
Key: IGNITE-10134
URL: https://issues.apache.org/jira/browse/IGNITE-10134
Project: Ignite
GitHub user dmitrievanthony opened a pull request:
https://github.com/apache/ignite/pull/5249
IGNITE-10133: Switch to per-node TensorFlow worker strategy.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Anton Dmitriev created IGNITE-10133:
---
Summary: ML: Switch to per-node TensorFlow worker strategy
Key: IGNITE-10133
URL: https://issues.apache.org/jira/browse/IGNITE-10133
Project: Ignite
GitHub user isapego opened a pull request:
https://github.com/apache/ignite/pull/5248
IGNITE-9897: ODBC fix for PDO when used with unixODBC
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9897
zzzadruga opened a new pull request #58: IGNITE-10125 Uniform style for buttons
URL: https://github.com/apache/ignite-teamcity-bot/pull/58
Uniform style for buttons: "Inspect" from PR selection, "Show graph" from
Master Trends, "More >>" from PR Failures
Taras Ledkov created IGNITE-10132:
-
Summary: TC: the thin client suites (PHP, nodejs etc) must
contains log of the Ignite node
Key: IGNITE-10132
URL: https://issues.apache.org/jira/browse/IGNITE-10132
GitHub user gvvinblade opened a pull request:
https://github.com/apache/ignite/pull/5247
IGNITE-10109 MVCC TX: data become inconsistent after several updates
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user xtern opened a pull request:
https://github.com/apache/ignite/pull/5246
TC test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xtern/ignite IGNITE-9858-TC
Alternatively you can review and apply these changes as the
Igor Seliverstov created IGNITE-10131:
-
Summary: Wrong processing of loaded from store keys on backup
nodes.
Key: IGNITE-10131
URL: https://issues.apache.org/jira/browse/IGNITE-10131
Project:
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/5245
IGNITE-10052: Restart node during TX causes vacuum error.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
GitHub user dgovorukhin opened a pull request:
https://github.com/apache/ignite/pull/5244
Ignite-2.4.12-wd
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.4.12-wd
Alternatively you can review and
GitHub user xtern opened a pull request:
https://github.com/apache/ignite/pull/5243
IGNITE-10080
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xtern/ignite IGNITE-10080
Alternatively you can review and apply these changes as
Sergey Antonov created IGNITE-10130:
---
Summary: Add option to API for disable triggering cache
interceptor.
Key: IGNITE-10130
URL: https://issues.apache.org/jira/browse/IGNITE-10130
Project: Ignite
GitHub user rkondakov opened a pull request:
https://github.com/apache/ignite/pull/5242
IGNITE-10129: Disable Vacuum warnings if mvcc is not enabled.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5238
---
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5237
---
Github user zstan closed the pull request at:
https://github.com/apache/ignite/pull/5240
---
GitHub user zstan opened a pull request:
https://github.com/apache/ignite/pull/5241
IGNITE-10128 Race in read\write cache configurations.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10128
GitHub user zstan opened a pull request:
https://github.com/apache/ignite/pull/5240
GG-14379 Race in read\write cache configurations.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10128
I like your idea about auto updates.
In this case, abbr-plugin should be improved to check and download
updates from external URI or local repo.
Looks like it could be implemented using Intellij's SDK virtual file [1].
But as I can see that abbreviations list update is the very rare case,
Igor Seliverstov created IGNITE-10129:
-
Summary: MVCC TX: do not log Vacuum warnings if mvcc is not enabled
Key: IGNITE-10129
URL: https://issues.apache.org/jira/browse/IGNITE-10129
Project:
Stanilovsky Evgeny created IGNITE-10128:
---
Summary: IO race during read\write cache configurations.
Key: IGNITE-10128
URL: https://issues.apache.org/jira/browse/IGNITE-10128
Project: Ignite
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5196
---
Ryabov Dmitrii created IGNITE-10127:
---
Summary: GridCacheRebalancingSyncSelfTest ignores check result
Key: IGNITE-10127
URL: https://issues.apache.org/jira/browse/IGNITE-10127
Project: Ignite
No, I meant under Ignite's git so any change to resource file arrives with
project workspace updates and gets automatically picked up by plugin.
Makes sense?
--Yakov
Great news!
Future release is about to contain mission critical Ignite workers liveness
monitoring, introduced in IGNITE-6587.
пт, 2 нояб. 2018 г. в 13:23, Nikolay Izhikov :
> Hello, Guys.
>
> Good news! We have 2 final tickets for 2.7.
> So release date is very near!
>
> Let's collect new
Hello, Guys.
Good news! We have 2 final tickets for 2.7.
So release date is very near!
Let's collect new features and improvements of Ignite 2.7 and includes it to
release notes and other documents.
Can you answer and describe your contributions?
signature.asc
Description: This is a
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4689
---
Hi Yakov,
Thanks so much for your analysis.
Parser expects chunks to be complete and has all the data to read entire
> message, but this is not guaranteed and single message can arrive in
> several chunks.
This is indeed the the assumption to my implementation. I have not come up
a another
GitHub user Max-Pudov opened a pull request:
https://github.com/apache/ignite/pull/5239
IGNITE-10126
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-10126
Alternatively you can review and apply
Yes, it's under git already in Dmitry Pavlov's GitHub account [1].
AFAIK donation to ASF is in progress [2]. (Dmitry Pavlov, please,
correct me if I'm wrong)
[1]
https://github.com/dspavlov/ignite-abbrev-plugin/blob/master/src/abbreviation.properties
[2]
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/4632
---
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/5238
IGNITE-6856
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6856
Alternatively you can review and apply these
Agree with Vyacheslav - reviewers can either fix the issues or ask to fix
them. After several PRs new contributors will get used with project
requirements.
As far as one time contributions, they are usually pretty simple and should
not take any significant time to fix. If one time contirbutor
Denis, there were email notifications from wiki on corresponding edits =)
--Yakov
Github user SomeFire closed the pull request at:
https://github.com/apache/ignite/pull/5083
---
Nikolai Kulagin created IGNITE-10125:
Summary: [TC Bot] Uniform style for buttons
Key: IGNITE-10125
URL: https://issues.apache.org/jira/browse/IGNITE-10125
Project: Ignite
Issue Type:
Nikolai Kulagin created IGNITE-10124:
Summary: [TC Bot] Redesign and refactor UI
Key: IGNITE-10124
URL: https://issues.apache.org/jira/browse/IGNITE-10124
Project: Ignite
Issue Type:
Github user asfgit closed the pull request at:
https://github.com/apache/ignite/pull/5069
---
GitHub user agoncharuk opened a pull request:
https://github.com/apache/ignite/pull/5237
IGNITE-10123 Disable events in IgniteLogicalRecoveryTest
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite
I've faced such practice.
Very first my contribution, when I have not been familiar with style
guidelines, Yakov Zhdanov kindly fixed code style issues himself.
I think it depends on a reviewer:
- in one case reviewer can fix issues independently
- in other case ask a contributor to solve them
Alexey Goncharuk created IGNITE-10123:
-
Summary: Intermittent OOME errors in PDS indexing tests
Key: IGNITE-10123
URL: https://issues.apache.org/jira/browse/IGNITE-10123
Project: Ignite
GitHub user voropava opened a pull request:
https://github.com/apache/ignite/pull/5236
Ignite 2.5.1 p150
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p150
Alternatively you can review and
Andrey, Dmitry,
If we have a practice of formatting a code before merge by committer
then it is already much better. But do we have such a practice?
As for me personally. I have not felt much discomfort with abbreviations.
I already used them extensively. Even "cctx", "ccfg" which are not
Peter Ivanov created IGNITE-10122:
-
Summary: Move Web-Console Frontend/Backend Docker images build to
dedicated directory
Key: IGNITE-10122
URL: https://issues.apache.org/jira/browse/IGNITE-10122
Vasiliy Sisko created IGNITE-10121:
--
Summary: Web console: Create documentation how to run Web agent as
Docker image
Key: IGNITE-10121
URL: https://issues.apache.org/jira/browse/IGNITE-10121
Hi Ivan,
provided that committer has installed ignite-abbrev-plugin it is not a big
deal to abbreviate common words before a merge.
I had the same impression about abbreviations when I came to the project:
"all other development world tends to expose as much meaning as it is
humanly possible in
Yuriy Sergeev created IGNITE-10120:
--
Summary: Create docker images for Web Console Frontend & Backend
Key: IGNITE-10120
URL: https://issues.apache.org/jira/browse/IGNITE-10120
Project: Ignite
Ivan, I agree with you: some our code style rules are really uncommon.
As for one-time contributions, if somebody decides to make a contribution
to some project, it's ok to adopt that project rules. Moreover, reviewing
committer can silently fix minor code style issues himself upon merge.
пт, 2
Andrey, Yakov,
Actually my concert is more about one-time contributions. I imagine
the following. Someone finds a bug a decides to contribute a fix.
I think it is quite common scenario in Open Source.
He creates a PR and awaits a review. I think that a smooth and fast
review process will
Yuriy Sergeev created IGNITE-10119:
--
Summary: Remove BETA sticker/label from WC
Key: IGNITE-10119
URL: https://issues.apache.org/jira/browse/IGNITE-10119
Project: Ignite
Issue Type: Task
62 matches
Mail list logo
