Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JournaledDAO operations fails on node v4.x #356

Open
drish opened this issue May 15, 2017 · 6 comments
Open

JournaledDAO operations fails on node v4.x #356

drish opened this issue May 15, 2017 · 6 comments
Assignees

Comments

@drish
Copy link
Contributor

drish commented May 15, 2017

@mdittmer I found the reason why the journaled dao tests were only failing on node v4.x.

nodejs/node#5862

on node v4.x fs.readFile were only understanding file names instead of file names and file descriptors as the JournaledDAO is currently using, making it fail on node v4.x

should I go ahead and tweak the journaled dao implementation to something that accommodates node v4.x too ? or is it not a big deal at this moment ?

cc @adamvy @mdittmer

@kgrgreer
Copy link
Collaborator

@drish Go ahead if it can be done easily, but otherwise, do we have any real need to support v4? I think we can just make v6+ be a requirement.

@mdittmer
Copy link
Collaborator

I think this is fine. @jacksonic do you want to update our Travis CI config to stop building 4, 5, and 6?

@adamvy
Copy link
Contributor

adamvy commented May 15, 2017 via email

@jacksonic
Copy link
Member

jacksonic commented May 15, 2017 via email

@drish
Copy link
Contributor Author

drish commented May 15, 2017

thanks, making journaled dao to support v4 would probably break the api, since atm journaled dao works with file descriptors.

@drish
Copy link
Contributor Author

drish commented May 15, 2017

once node v4 are disabled I can re enable journaled dao tests.

@drish drish self-assigned this Jul 13, 2017
sarthak-marwaha pushed a commit to sarthak-marwaha/foam2 that referenced this issue May 26, 2021
…eptionToastTranslation

[NP-3799] ClientRuntimeException toast title/message and translation
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

No branches or pull requests

5 participants