(Catching up on a backlog of emails, hence my belated reply)
I just checked the spark-prs app engine logs and it appears that our JIRA
API calls are failing due to a CAPTCHA check (same issue as before). Based
on https://jira.atlassian.com/browse/JRASERVER-40362, it sounds like this
is a fairly
Let actually me just take a look by myself and bring some updates soon.
2020년 4월 30일 (목) 오전 9:13, Hyukjin Kwon 님이 작성:
> WDYT @Josh Rosen ?
> Seems
> https://github.com/databricks/spark-pr-dashboard/blob/1e799c9e510fa8cdc9a6c084a777436bebeabe10/sparkprs/controllers/tasks.py#L131-L142
> this
>
There was a typo in the previous email. I am re-sending:
Hm, I thought you meant you prefer 3. over 4 but don't mind particularly.
I don't mean to wait for more feedback. It looks likely just a deadlock
which will be the worst case.
I was suggesting to pick one way first, and stick to it. If we
WDYT @Josh Rosen ?
Seems
https://github.com/databricks/spark-pr-dashboard/blob/1e799c9e510fa8cdc9a6c084a777436bebeabe10/sparkprs/controllers/tasks.py#L131-L142
this
isn't working anymore.
Does it make sense to move it to native Jira-GitHub integration
Hm, I thought you meant you prefer 3. over 4 but don't mind particularly.
I don't mean to wait for more feedback. It looks likely just a deadlock
which will be the worst case.
I was suggesting to pick one way first, and stick to it. If we find out
something later, we can discuss
more about
Thank you so much for doing this, Xiao!
On Wed, Apr 29, 2020 at 11:09 AM Xiao Li wrote:
> Hi all,
>
> This is the bi-weekly Apache Spark digest from the Databricks OSS team.
> For each API/configuration/behavior change, an *[API] *tag is added in
> the title.
>
> CORE
>
Hi all,
This is the bi-weekly Apache Spark digest from the Databricks OSS team.
For each API/configuration/behavior change, an *[API] *tag is added in the
title.
CORE
Not sure what you mean. The native integration will auto-link from a Jira
ticket to the PRs that mention that ticket. I don't think it will update
the ticket's status, though.
Would you like me to file a ticket with Infra and see what they say?
On Tue, Apr 28, 2020 at 12:21 AM Hyukjin Kwon
Sorry I'm not sure what your last email means. Does it mean you are putting it
up for a vote or just waiting to get more feedback? I disagree with saying
option 4 is the rule but agree having a general rule makes sense. I think we
need a lot more input to make the rule as it affects the
I think I am not seeing explicit objection here but rather see people tend
to agree with the proposal in general.
I would like to step forward rather than leaving it as a deadlock - the
worst choice here is to postpone and abandon this discussion with this
inconsistency.
I don't currently target
Hi All,
Following on from the below email I sent *11 DAYS ago now*, so far we have
had *one reply *from mahout cc:d to me (thank you Trevor) , and had *ONE
PERSON* sign up to the new hadoop-migrati...@infra.apache.org -
that is out of a total of *OVER 7000* people signed up to the 13 mailing
11 matches
Mail list logo
