Github user mccheah commented on the pull request:
https://github.com/apache/spark/pull/9615#issuecomment-157555075
I don't think the javax.ws.rs classes are actually compatible with each
other.
I just tried another experiment. I took my Spark package hacked to remove
the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7753#issuecomment-157474249
Merged build finished. Test FAILed.
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9137
---
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
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157481690
@zsxwing do you plan to update this? We should get some version of this
change in 1.6 if the netty rpc layer is left as the default.
---
If your project is set up for
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9749#issuecomment-157482003
Thanks, updated!
---
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
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9759#discussion_r45110623
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/datasources/json/JsonParsingOptionsSuite.scala
---
@@ -93,22 +93,29 @@ class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9774#issuecomment-157496810
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9774#issuecomment-157496804
**[Test build #46105 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46105/consoleFull)**
for PR 9774 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9773#issuecomment-157496705
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9165#issuecomment-157497025
Awesome, thanks Sean !
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7888#issuecomment-157499848
Merged build finished. Test PASSed.
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9755
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9697
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9656#issuecomment-157507309
**[Test build #46109 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46109/consoleFull)**
for PR 9656 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9081#issuecomment-157474071
This seems like a good idea, but I'd propose we delay refactoring until
after the 1.6 release.
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7753#issuecomment-157474157
**[Test build #46092 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46092/consoleFull)**
for PR 7753 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7753#issuecomment-157474253
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9649
---
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
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9740#issuecomment-157475631
Merging to master and 1.6.
---
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
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/9662#discussion_r45107210
--- Diff:
docker-integration-tests/src/test/scala/org/apache/spark/sql/jdbc/PostgresIntegrationSuite.scala
---
@@ -72,11 +78,17 @@ class
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9755#issuecomment-157479690
**[Test build #46100 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46100/consoleFull)**
for PR 9755 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9755#issuecomment-157480078
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/9760#issuecomment-157499965
It's an estimation based on LongType/DoubleType, it means most of the
tables with primitive types will not be affected.
---
If your project is set up for it, you can
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7888#issuecomment-157499693
**[Test build #46101 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46101/consoleFull)**
for PR 7888 at commit
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9774#discussion_r45117143
--- Diff: core/src/main/scala/org/apache/spark/rdd/SqlNewHadoopRDD.scala ---
@@ -95,6 +95,8 @@ private[spark] class SqlNewHadoopRDD[V: ClassTag](
}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7888#issuecomment-157499853
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9749#issuecomment-157507154
Rebased to pull PipelineSuite from master.
I removed the failing part of the PipelineSuite. It was not really needed
since other tests already check that
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9761#issuecomment-157476581
Merged build finished. Test PASSed.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9761#issuecomment-157476583
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/9530#issuecomment-157483860
sasl encryption for file transfers (instead of having to configure ssl for
the driver's file server). lower overhead in the driver. but nothing really
critical.
---
If
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9749#issuecomment-157484976
**[Test build #46102 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46102/consoleFull)**
for PR 9749 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157484857
> @zsxwing do you plan to update this? We should get some version of this
change in 1.6 if the netty rpc layer is left as the default.
Agree. Just working on
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9773#issuecomment-157495284
ok to test
---
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
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9773#issuecomment-157495244
Test cases please for any bug fix. Look at `HiveDataFrameAnalyticsSuite`
as an example (since i think we have to put this in the hive package for it to
work).
---
GitHub user nongli opened a pull request:
https://github.com/apache/spark/pull/9774
[WIP] [SPARK-11787] [SQL] Improve Parquet scan performance when usingâ¦
⦠flat schemas.
WIP: this still needs to implement more types and some type conversion
logic.
This patch
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9755#issuecomment-157500767
LGTM. Merged into master and branch-1.6. Thanks!
---
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
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/9770#discussion_r45104665
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/ScalaReflection.scala
---
@@ -719,6 +719,12 @@ trait ScalaReflection {
}
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9761
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9755#issuecomment-157480076
Merged build finished. Test PASSed.
---
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
Github user choochootrain commented on the pull request:
https://github.com/apache/spark/pull/9367#issuecomment-157485843
sounds good, i'll go ahead and squash the commits and submit a pr to master
and branch 1.6
---
If your project is set up for it, you can reply to this email and
GitHub user vanzin opened a pull request:
https://github.com/apache/spark/pull/9772
[SPARK-11786] [core] Tone down messages from akka error monitor.
There messages happen normally during the app's lifecycle, so printing
out ERROR logs all the time is misleading, and can actually
Github user huaxingao commented on the pull request:
https://github.com/apache/spark/pull/9773#issuecomment-157490181
hiveContext.table("db_name.table") works but
hiveContext.read.table("db_name.table")
throws an org.apache.spark.sql.catalyst.analysis.NoSuchTableException
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9773#issuecomment-157496694
**[Test build #46106 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46106/consoleFull)**
for PR 9773 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9774#issuecomment-157496807
Merged build finished. Test FAILed.
---
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
GitHub user mengxr opened a pull request:
https://github.com/apache/spark/pull/9776
[SPARK-11764] [ML] make Param.jsonEncode/jsonDecode support Vector
This PR makes the default read/write work with simple
transformers/estimators that have params of type `Param[Vector]`. @jkbradley
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9773#issuecomment-157496702
Merged build finished. Test FAILed.
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9731#issuecomment-157500087
I'm going to go ahead and merge this, as it's a bug fix update anyway,
passes, and should make sure there's no exploit of this form. We may not be
alone in getting some
GitHub user dtolpin opened a pull request:
https://github.com/apache/spark/pull/9775
invFunc=none work properly with python's reduceByKeyAndWindow
invFunc is optional and can be None. Instead of invFunc (the parameter)
invReduceFunc (a local function) was checked for trueness (that
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/9749#discussion_r45118179
--- Diff:
mllib/src/test/scala/org/apache/spark/ml/util/DefaultReadWriteTest.scala ---
@@ -19,23 +19,30 @@ package org.apache.spark.ml.util
import
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9760
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/9697#issuecomment-157502370
Merged to master/1.6
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9740
---
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
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9530#issuecomment-157477553
/cc @rxin is it too risky if adding this one to 1.6?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9749#issuecomment-157477581
LGTM except one minor issue commented inline.
---
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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/9530#issuecomment-157482127
Does it buy us anything to add this to 1.6?
---
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
Github user choochootrain commented on a diff in the pull request:
https://github.com/apache/spark/pull/9367#discussion_r45110137
--- Diff:
core/src/test/scala/org/apache/spark/scheduler/TaskResultGetterSuite.scala ---
@@ -119,5 +123,64 @@ class TaskResultGetterSuite extends
GitHub user huaxingao opened a pull request:
https://github.com/apache/spark/pull/9773
SPARK-11778:parse table name before it is passed to lookupRelation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/huaxingao/spark
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9772#issuecomment-157488833
**[Test build #46103 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46103/consoleFull)**
for PR 9772 at commit
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9165#issuecomment-157491868
Rebase
---
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
Github user jbonofre commented on the pull request:
https://github.com/apache/spark/pull/9165#issuecomment-157491651
Last screenshot showing that it still works ;)
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9165#issuecomment-157494809
**[Test build #46104 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46104/consoleFull)**
for PR 9165 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9749#issuecomment-157494838
Merged build finished. Test FAILed.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9749#issuecomment-157494727
**[Test build #46102 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46102/consoleFull)**
for PR 9749 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9776#issuecomment-157505023
Merged build finished. Test FAILed.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9776#issuecomment-157505025
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9748#issuecomment-157506147
**[Test build #46108 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46108/consoleFull)**
for PR 9748 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9776#issuecomment-157507596
**[Test build #2082 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2082/consoleFull)**
for PR 9776 at commit
Github user vanzin commented on a diff in the pull request:
https://github.com/apache/spark/pull/9780#discussion_r45144962
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala ---
@@ -492,6 +492,18 @@ private[spark] class TaskSchedulerImpl(
}
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/9656#issuecomment-157560211
And yes, SPARK-11672 should be resolved now.
---
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
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/9780#issuecomment-157560195
LGTM, indeed a nice improvement :).
---
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
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/9741#discussion_r45146703
--- Diff:
streaming/src/test/scala/org/apache/spark/streaming/StreamingListenerSuite.scala
---
@@ -161,6 +162,14 @@ class StreamingListenerSuite extends
Github user sun-rui commented on a diff in the pull request:
https://github.com/apache/spark/pull/9743#discussion_r45146926
--- Diff: R/pkg/inst/tests/test_sparkSQL.R ---
@@ -294,9 +294,13 @@ test_that("create DataFrame with complex types", {
test_that("create DataFrame from a
Github user sun-rui commented on the pull request:
https://github.com/apache/spark/pull/9743#issuecomment-157564288
LGTM except a minor comment on coding style
---
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
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/9785#issuecomment-157564161
@shivaram @sun-rui
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9741#issuecomment-157564157
**[Test build #46134 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46134/consoleFull)**
for PR 9741 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9785#issuecomment-157565183
Merged build finished. Test FAILed.
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9785#issuecomment-157565179
**[Test build #46135 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46135/consoleFull)**
for PR 9785 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9785#issuecomment-157565185
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9785#issuecomment-157567575
Merged build finished. Test FAILed.
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9785#issuecomment-157567577
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/9782#issuecomment-157567637
I have merged this, but this wont auto-close as it is not to the master
branch. Please close this PR.
---
If your project is set up for it, you can reply to this email
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9741#issuecomment-157567560
LGTM
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9785#issuecomment-157567574
**[Test build #46137 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46137/consoleFull)**
for PR 9785 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9786#issuecomment-157569932
**[Test build #46138 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46138/consoleFull)**
for PR 9786 at commit
Github user fayeshine commented on the pull request:
https://github.com/apache/spark/pull/9656#issuecomment-157572390
Scalastyle checks failed at following occurrences:
[error]
Github user pankajarora12 commented on the pull request:
https://github.com/apache/spark/pull/8357#issuecomment-157572336
In one of our project we have 25 requests/second that are coming in through
automated system.
Executor time per request is 50ms (as it is just a look up
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9779#issuecomment-157578249
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9779#issuecomment-157578149
**[Test build #46124 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46124/consoleFull)**
for PR 9779 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9051#issuecomment-157578245
retest this please
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9779#issuecomment-157578248
Merged build finished. Test PASSed.
---
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
GitHub user yhuai opened a pull request:
https://github.com/apache/spark/pull/9788
[SPARK-11792] [SQL] SizeEstimator cannot provide a good size estimation of
UnsafeHashedRelations
https://issues.apache.org/jira/browse/SPARK-11792
You can merge this pull request into a Git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9764#issuecomment-157580796
**[Test build #46149 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46149/consoleFull)**
for PR 9764 at commit
Github user tnachen commented on the pull request:
https://github.com/apache/spark/pull/9301#issuecomment-157558208
We started to add ubuntu and versions since it wasn't explicit what OS
image it was built upon.
@andrewor14 what are these docker images used for? I'm trying to
Github user jerryshao commented on a diff in the pull request:
https://github.com/apache/spark/pull/9780#discussion_r45144733
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala ---
@@ -492,6 +492,18 @@ private[spark] class TaskSchedulerImpl(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157560994
Merged build finished. Test FAILed.
---
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
Github user brkyvz commented on the pull request:
https://github.com/apache/spark/pull/9403#issuecomment-157561019
Hi @lordnynex. Why did you think this causes Hive tests to fail? That was
most probably a flaky test.
Regarding publishing a non-aggregated stream, yes that is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9481#issuecomment-157560996
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/9782#issuecomment-157561666
Merging this. thanks for fixing this @zsxwing
---
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
GitHub user felixcheung opened a pull request:
https://github.com/apache/spark/pull/9785
[SPARK-11339][SPARKR] Document the list of functions in R base package that
are masked by functions with same name in SparkR
Added tests for function that are reported as masked, to make sure
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/8714#issuecomment-157563810
@jerryshao I'll have a look later today.
---
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
301 - 400 of 939 matches
Mail list logo
