Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2824#issuecomment-59686863
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21906/consoleFull)
for PR 2824 at commit
Github user manishamde commented on a diff in the pull request:
https://github.com/apache/spark/pull/2607#discussion_r19069043
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/tree/loss/LeastSquaresError.scala
---
@@ -0,0 +1,45 @@
+/*
+ * Licensed to the Apache
GitHub user JoshRosen opened a pull request:
https://github.com/apache/spark/pull/2852
[WIP] Add WebUITableBuilder to simplify table-building code
This work-in-progress commit illustrates a weekend hack project that I came
up with for significantly simplifying the web UI's table
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2852#issuecomment-59687664
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21907/consoleFull)
for PR 2852 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2852#issuecomment-59687734
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/2852#issuecomment-59687732
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21907/consoleFull)
for PR 2852 at commit
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/2824#issuecomment-59688035
Hi @JoshRosen , I just set `transferToEnabled` to false as default value,
unless users explicitly set it to true, `transferTo` will not be enabled.
Currently,
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2824#issuecomment-59688343
HI @jerryshao,
Changing the default is exactly what I had in mind. This looks good to me!
(Going to bed now; I'll merge this tomorrow and backport to
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/2824#issuecomment-59688531
Thanks a lot :).
---
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 baishuo commented on the pull request:
https://github.com/apache/spark/pull/2842#issuecomment-59688527
@JoshRosen @pwendell I know the reason of this problemã In idea, I
should right click the project and click maven-reimport
---
If your project is set up for it,
Github user baishuo closed the pull request at:
https://github.com/apache/spark/pull/2842
---
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/2839#issuecomment-59688582
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/2839#issuecomment-59688580
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21905/consoleFull)**
for PR 2839 at commit
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/2667#discussion_r19069469
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/evaluation/RankingMetrics.scala ---
@@ -0,0 +1,115 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2839#issuecomment-59682641
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21905/consoleFull)
for PR 2839 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2743#issuecomment-59681217
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21900/consoleFull)
for PR 2743 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-59690664
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21908/consoleFull)
for PR 2607 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2824#issuecomment-59691398
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/2824#issuecomment-59691389
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21906/consoleFull)
for PR 2824 at commit
GitHub user liyezhang556520 opened a pull request:
https://github.com/apache/spark/pull/2853
[SPARK-4005][CORE] handle message replies in receive instead of in the
individual private methods
In BlockManagermasterActor, when handling message type UpdateBlockInfo, the
message
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2853#issuecomment-59697011
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21909/consoleFull)
for PR 2853 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-59697993
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21908/consoleFull)
for PR 2607 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2607#issuecomment-59697998
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/2853#issuecomment-59706895
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/1567#issuecomment-59706916
test 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2853#issuecomment-59706889
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21909/consoleFull)
for PR 2853 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1567#issuecomment-59707432
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21911/consoleFull)
for PR 1567 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1567#issuecomment-59708199
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/1567#issuecomment-59714668
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/1567#issuecomment-59714664
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21911/consoleFull)
for PR 1567 at commit
GitHub user tsliwowicz opened a pull request:
https://github.com/apache/spark/pull/2854
Block Manager - Double Register Crash
In long running contexts, we encountered the situation of double
register without a remove in between. The cause for that is unknown, and
assumed a temp
GitHub user preaudc opened a pull request:
https://github.com/apache/spark/pull/2855
[SPARK-3967] Ensure that files are fetched atomically
tempFile is created in the same directory than targetFile, so that the
move from tempFile to targetFile is always atomic
You can merge this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2854#issuecomment-59722949
Can one of the admins verify this patch?
---
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/2855#issuecomment-59722947
Can one of the admins verify this patch?
---
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/2342#issuecomment-59723719
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21912/consoleFull)
for PR 2342 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2342#issuecomment-59723812
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21912/consoleFull)
for PR 2342 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2342#issuecomment-59723813
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/2816#issuecomment-59724233
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21913/consoleFull)
for PR 2816 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2342#issuecomment-59724241
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21914/consoleFull)
for PR 2342 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2342#issuecomment-59724343
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/2342#issuecomment-59724340
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21914/consoleFull)
for PR 2342 at commit
Github user tsliwowicz commented on the pull request:
https://github.com/apache/spark/pull/1358#issuecomment-59724452
@mateiz - @KashiErez and I went on a different route. The killer issue was
that there is a System.exit(1) in BlockManagerMasterActor which was a huge
robustness issue
Github user saucam commented on the pull request:
https://github.com/apache/spark/pull/2841#issuecomment-59726357
This PR also fixes :
https://issues.apache.org/jira/browse/SPARK-1847
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2816#issuecomment-59732528
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21913/consoleFull)
for PR 2816 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2816#issuecomment-59732530
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/2856
[SPARK-4008] Fix kryo with fold in KryoSerializerSuite
`zeroValue` will be serialized by `spark.closure.serializer` but
`spark.closure.serializer` only supports the default Java serializer. So it
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2856#issuecomment-59734858
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21915/consoleFull)
for PR 2856 at commit
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2673#issuecomment-59736352
This is the gist of dependency tree for artifacts published by this patch.
https://gist.github.com/ScrapCodes/a5857e57d828b4b787ff
---
If your project is set up for
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2856#issuecomment-59745195
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21915/consoleFull)
for PR 2856 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2856#issuecomment-59745203
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user YanTangZhai opened a pull request:
https://github.com/apache/spark/pull/2857
[SPARK-4009][SQL]HiveTableScan should use makeRDDForTable instead of
makeRDDForPartitionedTable for partitioned table when partitionPruningPred is
None
HiveTableScan should use makeRDDForTable
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2857#issuecomment-59751379
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21916/consoleFull)
for PR 2857 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2857#issuecomment-59751519
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21916/consoleFull)
for PR 2857 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2857#issuecomment-59751523
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/2857#issuecomment-59755633
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21917/consoleFull)
for PR 2857 at commit
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2729#issuecomment-59756273
Yes, as @mridulm pointed out. This should not be settable by the users on
yarn. It should automatically use the yarn approved directories. We have logic
in there for
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2857#issuecomment-59758705
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/2857#issuecomment-59758697
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21917/consoleFull)
for PR 2857 at commit
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/2615#issuecomment-59761949
Hey @pwendell, I have updated this patch to include effective pom changes.
So that you can try it out. Also I think this is ready for review !
---
If your project is
Github user ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/2615#discussion_r19086365
--- Diff: core/pom.xml ---
@@ -264,6 +284,10 @@
scopetest/scope
/dependency
dependency
+ groupIdcom.twitter/groupId
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2615#issuecomment-59763811
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21918/consoleFull)
for PR 2615 at commit
Github user mdagost commented on the pull request:
https://github.com/apache/spark/pull/2636#issuecomment-59769268
@MLnick It doesn't look like `pairRDDToPython` does the trick. I tried
```{python}
def userFeatures(self):
juf = self._java_model.userFeatures()
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/2728#issuecomment-59771521
So one issue is that the scheme was added to properly handle when yarn
using https (SPARK-3286). If client mode isn't passing the scheme then that is
probably broken.
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/2783#issuecomment-59772318
Other comments?
---
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 witgo opened a pull request:
https://github.com/apache/spark/pull/2858
[SPARK-4010][Web UI]Spark UI returns 500 in yarn-client mode
The problem caused by #1966
CC @YanTangZhai @andrewor14
You can merge this pull request into a Git repository by running:
$ git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2858#issuecomment-59781548
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21919/consoleFull)
for PR 2858 at commit
GitHub user ryan-williams opened a pull request:
https://github.com/apache/spark/pull/2859
fix broken links in README.md
seems like `building-spark.html` was renamed to `building-with-maven.html`?
Is Maven the blessed build tool these days, or SBT? I couldn't find a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2859#issuecomment-59782880
Can one of the admins verify this patch?
---
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 mdagost commented on the pull request:
https://github.com/apache/spark/pull/2636#issuecomment-59784360
@davies Your idea of adding something like `fromTupleRDD` to
`PythonMLLibAPI` seems to be the way to go. I'm just doing some cleanup and
will push `userFeatures` and
Github user ryan-williams commented on the pull request:
https://github.com/apache/spark/pull/2848#issuecomment-59785816
@preaudc see last commit, I applied this change to the `case _` as well,
per your suggestion!
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2615#issuecomment-59791098
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user devldevelopment commented on the pull request:
https://github.com/apache/spark/pull/2837#issuecomment-59791166
Ok thanks for the feedback guys, if this feature is no longer wanted or
needed maybe be can close it (the JIRA 576)? Generally I'm getting to grips
with scala
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2615#issuecomment-59791090
**[Tests timed
out](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21918/consoleFull)**
for PR 2615 at commit
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/2667#issuecomment-59793960
Jenkins, add to whitelist.
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/2667#issuecomment-59794008
test 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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2667#issuecomment-59794882
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21920/consoleFull)
for PR 2667 at commit
Github user shivaram commented on a diff in the pull request:
https://github.com/apache/spark/pull/2851#discussion_r19096569
--- Diff: core/src/main/scala/org/apache/spark/HeartbeatReceiver.scala ---
@@ -30,7 +30,8 @@ import org.apache.spark.util.ActorLogReceive
private[spark]
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2859#issuecomment-59795665
No, the reverse actually. The site has not been rebuilt though to expose
the new page. This has been asked several times so I hope the site can be
refreshed.
---
If
Github user ryan-williams commented on the pull request:
https://github.com/apache/spark/pull/2859#issuecomment-59796389
I see. Do you want to:
* leave the broken links,
* add some basic building with sbt commands to the README, or
* point them at the building-with-maven
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2667#issuecomment-59796463
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21921/consoleFull)
for PR 2667 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2858#issuecomment-59797312
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/2858#issuecomment-59797300
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21919/consoleFull)
for PR 2858 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/2859#issuecomment-59797568
The issue is that the docs in `master` are all consistent, and think
contain the correct current state of instructions. But on Github you see
`master`'s `README.md` but
Github user ryan-williams commented on the pull request:
https://github.com/apache/spark/pull/2859#issuecomment-59799405
Interesting. What do you mean by both links? The current links to
`building-spark.html`, as well as the `building-with-maven.html` links I've
submitted here? The
Github user mccheah commented on the pull request:
https://github.com/apache/spark/pull/2828#issuecomment-59803881
@JoshRosen agreed with @ash211, this is really good.
Are there any actual comments on the PR, or can it be merged? =)
---
If your project is set up for it, you
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/2844#issuecomment-59803868
LGTM now, 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 project does not have this
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2824
---
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 JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2824#issuecomment-59805036
I've merged this into `master` and `branch-1.1`.
Thanks a lot :).
Thank YOU (and @mridulm) for helping to diagnose this really subtle bug!
---
If
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1658#issuecomment-59805377
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21922/consoleFull)
for PR 1658 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1658#issuecomment-59805569
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/1658#issuecomment-59805565
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21922/consoleFull)
for PR 1658 at commit
GitHub user liancheng opened a pull request:
https://github.com/apache/spark/pull/2860
[SPARK-3537][SQL] Refines in-memory columnar table statistics
This PR refines in-memory columnar table statistics:
1. adds 3 more statistics for in-memory table columns: `count`,
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2860#discussion_r19099520
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/columnar/ColumnStats.scala ---
@@ -24,11 +24,13 @@ import
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2860#discussion_r19099771
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/columnar/ColumnStats.scala ---
@@ -185,15 +196,16 @@ private[sql] class StringColumnStats extends
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2860#issuecomment-59806948
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21923/consoleFull)
for PR 2860 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/2849#issuecomment-59807087
Hey @olegz is there an associated JIRA for this? If so could you include it
in the title?
---
If your project is set up for it, you can reply to this email and have
Github user ryan-williams commented on the pull request:
https://github.com/apache/spark/pull/2848#issuecomment-59807140
Jenkins, test this please. Does that work if I am not an admin?
@pwendell agreed, the logic is a little tricky but I couldn't find a
simpler way to express
Github user liancheng commented on a diff in the pull request:
https://github.com/apache/spark/pull/2860#discussion_r1919
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/PlannerSuite.scala ---
@@ -76,4 +76,24 @@ class PlannerSuite extends FunSuite {
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2848#issuecomment-59807368
Jenkins, 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
Github user olegz commented on the pull request:
https://github.com/apache/spark/pull/2849#issuecomment-59807570
@andrewor14 done.
---
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
1 - 100 of 383 matches
Mail list logo
