Skip to content

THRIFT-4811: Add CMake config file and targets. (see #4752)#1748

Merged
jeking3 merged 5 commits intoapache:masterfrom
soroshsabz:master
Mar 15, 2019
Merged

THRIFT-4811: Add CMake config file and targets. (see #4752)#1748
jeking3 merged 5 commits intoapache:masterfrom
soroshsabz:master

Conversation

@soroshsabz
Copy link
Copy Markdown
Contributor

ITNOA

Add cmake config module, this issue is duplicate THRIFT-4752.

@soroshsabz
Copy link
Copy Markdown
Contributor Author

It is some similar to PR #1709

@soroshsabz
Copy link
Copy Markdown
Contributor Author

soroshsabz commented Feb 27, 2019

@jeking3 why test failed with below error?

error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502 Bad Gateway

is it for my commit?!

@soroshsabz
Copy link
Copy Markdown
Contributor Author

soroshsabz commented Feb 27, 2019

@Jens-G why your JOB="Autotools (Ubuntu Bionic)" SCRIPT="autotools.sh" is passed and does not clone git clone https://go.googlesource.com/net /thrift/src/test/go/src/golang.org/x/net and does not see any error like error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502 Bad Gateway?

How to request retest this PR?

thanks

@soroshsabz
Copy link
Copy Markdown
Contributor Author

@jeking3 I think the error on travis because for internal problem, I recheck it in my master and travis does not report any issue. did you can retest it?

thanks

@jeking3
Copy link
Copy Markdown
Contributor

jeking3 commented Feb 28, 2019

Copy link
Copy Markdown
Contributor

@jeking3 jeking3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Need to resolve build issues and some minor comments here.

* Add bin variable into cmake Config module

* Exclude cygwin

* Resolved some review problem
* Resolved some review problem
@soroshsabz
Copy link
Copy Markdown
Contributor Author

@jeking3 I mitigate appveyor problem, and resolved problem in your review. travis-ci arise irrelative problem, I think if you rerun these test, my PR pass it, because it is passed in my fork travis-ci and appveyor

Please rereview this PR

thank you very much

jeking3 and others added 2 commits March 1, 2019 17:05
Change error message.

Co-Authored-By: soroshsabz <soorosh_abi@hotmail.com>
@soroshsabz
Copy link
Copy Markdown
Contributor Author

@jeking3 I applied your suggestion, and answer to your question and pass all tests. I'm grateful to rereview it.

thanks

@philomely
Copy link
Copy Markdown

philomely commented Mar 4, 2019

I fixed a bug of thrift lua version. not sure where to put it. wonder if anyone can take a look. link:
https://github.com/philomely/thrift/pull/1/commits/e5de1d7363b6ae80945658a69ec5ccf456262d79

@jeking3
Copy link
Copy Markdown
Contributor

jeking3 commented Mar 5, 2019

I fixed a bug of thrift lua version. not sure where to put it. wonder if anyone can take a look. link:
philomely@e5de1d7

This seems a but out of place. Check to see if there is an open issue in the Apache Jira for thrift. If not, create one. Then submit a pull request to github. Thanks.

@jeking3
Copy link
Copy Markdown
Contributor

jeking3 commented Mar 5, 2019

@emmenlau could you review? Thanks.

@philomely
Copy link
Copy Markdown

I fixed a bug of thrift lua version. not sure where to put it. wonder if anyone can take a look. link:
philomely@e5de1d7

This seems a but out of place. Check to see if there is an open issue in the Apache Jira for thrift. If not, create one. Then submit a pull request to github. Thanks.

i do no have privilege to open issue. i'm pretty sure it's a bug and a big one. I don't have much time for this. you guy should take care of it.

@soroshsabz
Copy link
Copy Markdown
Contributor Author

@jeking3 any update? I think incremental improvement is a good approach :D

thanks a lot :)

@jeking3
Copy link
Copy Markdown
Contributor

jeking3 commented Mar 9, 2019

@philomely If you submit a pull request from your fork's philomely-patch-1 branch into apache/master then we'll see if the CI build agrees with you. Thanks.

@jeking3
Copy link
Copy Markdown
Contributor

jeking3 commented Mar 9, 2019

@emmenlau could you review? Thanks.

@jeking3 jeking3 self-assigned this Mar 9, 2019
@jeking3 jeking3 added the releng Release Engineering label Mar 9, 2019
@jeking3
Copy link
Copy Markdown
Contributor

jeking3 commented Mar 13, 2019

So I have one concern here. If I look back at THRIFT-4752 I see this exchange:

#1709 (comment)

My assumption was that you would commit changes back to @emmenlau and then those would be reflected here jointly. But instead, this new PR contains no credit to @emmenlau even though it was derived from that work.

@emmenlau
Copy link
Copy Markdown
Member

I agree that its a bit sad that this PR is not cleanly based on my PR. It makes it also a lot harder to review the changes.

@soroshsabz
Copy link
Copy Markdown
Contributor Author

soroshsabz commented Mar 13, 2019

@jeking3 The point is that I had not seen anyone else doing anything about this, even though I was searching. so I written this PR from scratch (new) with my point of view, but after I found @emmenlau work, I want to continue those work but because my work does not derived from that work and does not get any help from that, accordingly I think it is very hard to continue from @emmenlau work, because all PR must be change (In fact, it should be completely erased and my changes would be replaced.), So I create new PR. :D

@soroshsabz
Copy link
Copy Markdown
Contributor Author

@emmenlau because it is not totaly based on your PR, it is not have any relation between two PRs and codes. I did not have any help from your PR. :)

Of course, thank you very much for reviewing my PR and telling my issues.

@jeking3
Copy link
Copy Markdown
Contributor

jeking3 commented Mar 13, 2019

Thanks for the explanation, that sounds reasonable to me. When two people end up working on the same thing these kinds of collisions can happen. I just want to make sure everyone involved is okay with using THRIFT-4811 as the solution.

@soroshsabz
Copy link
Copy Markdown
Contributor Author

@jeking3 So any problem exist?

@philomely
Copy link
Copy Markdown

@jeking3 I made one
#1761

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

releng Release Engineering

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants