-
Notifications
You must be signed in to change notification settings - Fork 7
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
Tests from iconv-lite are not passing #7
Comments
@bpasero have you also tried |
@gyzerok yes I am seeing the same result with either function convert(conv, input, context) {
if (!Buffer.isBuffer(input) && input !== FLUSH) {
throw new Error('Bad argument.'); // Not a buffer or a string.
} |
The object that is checked, when using |
@bpasero I see. No worries. I've decided to take a small break. Was using most of my free time before to make everything work 😄 But I am confident we can fix everything for July release. I will get back to it this weekend then. |
Sounds good, thanks. |
@ashtuchkin if there are no objections, I wonder if we should simply copy the tests folder from |
No objections from me, I think that might be the best we can do until I
support UMD natively.
--
Alexander Shtuchkin
…On Wed, Jul 8, 2020 at 11:25 AM Benjamin Pasero ***@***.***> wrote:
@ashtuchkin <https://github.com/ashtuchkin> if there are no objections, I
wonder if we should simply copy the tests folder from iconv-lite over
into this repo to be able to run them? Let me know if you have a better
idea...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#7 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEZKHPDLWD6DGA6UI2PMOTR2SFVDANCNFSM4OUHVAQA>
.
|
I pushed the tests to this repo so that they can be run via
|
Hello @bpasero! I've looked into this as promised.
It's not exactly like that. In With most errors you are seeing the problem is not with the library itself or with our webpack build, but with the fact that tests are written without any expectation that they could be run against So the library creates and returns buffers using it's shimmed After reading this you might start wondering if it means same problem for VSCode when running in Electron. And according to my understanding it is not the case, because we don't expect Now the only error here which concerns me personally is
I will look into it. And here is my suggestion: I don't think VSCode nor |
I have identified the source of the last error.
Will see what I can do about it. |
Sounds good, thanks. And agree, ideally tests would remain in |
I did an experiment where I let all tests from
iconv-lite
run against this webpacked version. Here are the steps:test
folder oficonv-lite
into the root of this projectdevDependencies
oficonv-lite
into thepackage.json
of this project"test": "mocha --reporter spec --grep ."
over into thescripts
section of thepackage.json
of this projectwebpack.config.js
target: "node"
but the default (web)yarn test
The result is a couple of test failures:
@gyzerok @ashtuchkin this worries me a bit. Some notes:
target: "node"
(not to any surprise)[email protected]
I would appreciate some help in fixing these issues as they would probably block the July release where I would like to go back to the webpacked version that does not target node. Thanks.
The text was updated successfully, but these errors were encountered: