Skip to content

Fix building with node 10.0.0#71

Open
Paxa wants to merge 15 commits into
Southern:masterfrom
stormwin:master
Open

Fix building with node 10.0.0#71
Paxa wants to merge 15 commits into
Southern:masterfrom
stormwin:master

Conversation

@Paxa

@Paxa Paxa commented Jul 7, 2018

Copy link
Copy Markdown

I found this useful patch in #68 (i'm not an author of this changes)

Thank you @stormwin

@stormwin

stormwin commented Jul 8, 2018

Copy link
Copy Markdown

If i have more free time, i will fix backward incompatibilities with older nodejs versions. The problem is with OpenSSL version that is changed from 1.0.x to 1.1.x in nodeJS v10.x

@stormwin

stormwin commented Jul 8, 2018

Copy link
Copy Markdown

OK, finally it work on every nodejs version.

@Paxa

Paxa commented Jul 9, 2018

Copy link
Copy Markdown
Author

Bravo!

@jacobpdq

Copy link
Copy Markdown

@Southern bump plz (needed for node-solid)

@alexanderkhivrych

Copy link
Copy Markdown

plz merge it

@alexanderkhivrych

Copy link
Copy Markdown

ASAP

@alexanderkhivrych

alexanderkhivrych commented Jul 19, 2018

Copy link
Copy Markdown

build already green

@alexanderkhivrych

Copy link
Copy Markdown

@stormwin

@stormwin

Copy link
Copy Markdown

I am also waiting for this merge. Till then, i am using my own fork in my projects

@jacobpdq

jacobpdq commented Jul 19, 2018 via email

Copy link
Copy Markdown

@alexanderkhivrych

Copy link
Copy Markdown

@Southern

@Paxa

Paxa commented Jul 23, 2018

Copy link
Copy Markdown
Author

Guys, you can just use it from github: yarn add stormwin/node-x509 or npm i stormwin/node-x509

@yorkie

yorkie commented Jul 28, 2018

Copy link
Copy Markdown
Collaborator

@Paxa Thanks for this patch very much, may I ask you not to change the coding style, such that we could merge them only with building patch :)

@yorkie yorkie mentioned this pull request Jul 28, 2018
@Paxa

Paxa commented Jul 28, 2018

Copy link
Copy Markdown
Author

@yorkie I just created a PR from @stormwin fork

@eduardocruz

Copy link
Copy Markdown

Did the project die?

@adamhamlin

Copy link
Copy Markdown

Bump

@mbwhite

mbwhite commented Nov 16, 2018

Copy link
Copy Markdown
Contributor

Can this be merged please?

@yorkie yorkie left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

@Paxa Thanks, but I found you changed the indent to a tab or 4 spaces which could make the source is hard to review, please remove those coding style changes.

Comment thread include/x509.h
Local<Value> try_parse(const std::string& dataString);
Local<Value> verify(const std::string& dataString);
Local<Value> try_parse(const std::string &dataString);
Local<Value> verify(const std::string &dataString);

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Could you please revert these style changes?

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

i wish someone just edited these files using github inline edit :)

Comment thread include/x509.h
char* real_name(char *data);
char* trim(char *data, int len);
char *real_name(char *data);
char *trim(char *data, int len);

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Ditto.

Comment thread src/addon.cc
Nan::New<FunctionTemplate>(get_issuer)->GetFunction());
Nan::Set(exports, Nan::New<String>("parseCert").ToLocalChecked(),
Nan::New<FunctionTemplate>(parse_cert)->GetFunction());
}

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Please use the 2 spaces as indents.

@yorkie

yorkie commented Nov 17, 2018

Copy link
Copy Markdown
Collaborator

Can this be merged please?

@mbwhite Sorry for the late, already leave comments here though the CI is pass :)

@stormwin

Copy link
Copy Markdown

OK, i will try to fix this styling stuffs and also will try to fix some warnings for node v11. Will do a new commits today or tomorrow

@ghost

ghost commented Nov 23, 2018

Copy link
Copy Markdown

@stormwin you awesome!
thanks for fixing this,
hoping to see it merged

@okonon

okonon commented Nov 30, 2018

Copy link
Copy Markdown

Bump. @stormwin any chance that you fixed that styling ?

yorkie pushed a commit that referenced this pull request Dec 19, 2018
This is the #71 but with corrected formatting as per the discussion in #71 
Thank you to those who worked on fix; aim here is to get the fix merged as it is needed by
many projects

Signed-off-by: Matthew B. White <whitemat@uk.ibm.com>
@okonon

okonon commented Jan 11, 2019

Copy link
Copy Markdown

Anyone can resolve the conflicts?

@prompt-bot

Copy link
Copy Markdown

there any follow up?

@mbwhite

mbwhite commented Mar 17, 2019

Copy link
Copy Markdown
Contributor

there any follow up?

We would have preferred to use this repo - but due to schedules we had to fork and republished to npm.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants