| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Codecov Report
@@ Coverage Diff @@
## main #4733 +/- ##
==========================================
- Coverage 69.23% 69.18% -0.05%
==========================================
Files 29 29
Lines 1638 1652 +14
Branches 341 363 +22
==========================================
+ Hits 1134 1143 +9
- Misses 428 432 +4
- Partials 76 77 +1
Continue to review full report at Codecov.
|
Sorry, something went wrong.
|
✨ Coder.com for PR #4733 deployed! It will be updated on every commit.
|
Sorry, something went wrong.
|
@yisibl any ideas why the artifact failed? |
Sorry, something went wrong.
What is the actual glibc version in Docker? |
Sorry, something went wrong.
@node-rs/argon2 doesn't support GLIBC_2.17 for now. I'm implementing the support in napi-rs/napi-rs#1025 And I'll draft a patch release after NAPI-RS toolchain supported the lower GLIBC on the Linux platform. |
Sorry, something went wrong.
|
Yeah, I see GLIBC_2.17, let's wait for the next version. |
Sorry, something went wrong.
|
Actually, idk if I could test on Termux, since whenever I tried it it didn't work. But I will try 3.9.3 and try learning how to do that. |
Sorry, something went wrong.
|
Uh oh... My Termux isn't working. From the beginning, I haven't able to get the mirrors updated, there isn't a sources.list file in my /etc dir. Idk what happened to my phone, maybe it's because I have an older phone. |
Sorry, something went wrong.
|
Wait we are supposed to use @napi-rs/argon2 right? Why's it node-rs? |
Sorry, something went wrong.
|
Upgrade to @node-rs/argon2@1.0.5 to solve the GLIBC problem with centos:7 |
Sorry, something went wrong.
|
@Brooooooklyn will do - thank you for the quick patch! @yisibl - thank you for the review and feedback! @im-coder-lg no worries, I will test on Termux |
Sorry, something went wrong.
|
This should fix the audit/code scanning CI failing (I'll rebase once merged): #4742 |
Sorry, something went wrong.
|
Testing this now! |
Sorry, something went wrong.
😅 I wish I had a good answer for that... |
Sorry, something went wrong.
|
@code-asher brought up a good point. our e2e tests run on Linux so those are passing which means this is good on Linux. |
Sorry, something went wrong.
|
@im-coder-lg any updates? |
Sorry, something went wrong.
TermuxPreviously, installing the project would fail on Termux due to argon2 issues. From what I can tell, it seems as though those problems are resolved with this PR! I couldn't successfully downgrade Node to v14 on Termux so code-server wouldn't actually run. So assuming someone can downgrade, it should work. |
Sorry, something went wrong.
|
I'll just test again. Since I didn't install Node 14 before running, I got into errors. I will try again and hopefully succeed. |
Sorry, something went wrong.
No worries at all. What I did was upload the npm-package to Google Drive, then download directly on my device, unzip/untar and then yarn in that (yarn install --production) and was able to get it to work. |
Sorry, something went wrong.
|
Here's a link to the npm-package.zip if you want to download: https://drive.google.com/file/d/1VyB0i4GMf9yAo8n_DU-YkfPGRKnzb9Nf/view?usp=sharing |
Sorry, something went wrong.
|
Heads up: I'll be testing two architectures, the first one is AARCH64 aka. ARM64 and then ARMV7L which is integrated to Raspberry Pi OS Bullseye. |
Sorry, something went wrong.
|
LOLZ, all I needed to test was the package.tar.gz tarball? I couldn't unzip the ZIP file, maybe it's due to that. |
Sorry, something went wrong.
|
This absolutely works. I am testing this once again with the hashed password and maybe again on armv7l. |
Sorry, something went wrong.
|
I can say this works successfully, although 4.0.1 is still in development, some simple errors pop up. |
Sorry, something went wrong.
There was a problem hiding this comment.
We can merge! LGTM!
Sorry, something went wrong.
|
@im-coder-lg thanks so much for helping test!!! I will merge this once CI passes |
Sorry, something went wrong.
This reverts part of the changes introduced in refactor: migrate from argon2 -> @node-rs/argon2 (#4733) Switching to @node-rs/argon2 introduced bugs that we couldn't solve due to limitations in npm. see here #4804 (comment)
* revert: partial revert of 723469a This reverts part of the changes introduced in refactor: migrate from argon2 -> @node-rs/argon2 (#4733) Switching to @node-rs/argon2 introduced bugs that we couldn't solve due to limitations in npm. see here #4804 (comment)
* chore(deps): replace argon2 w/@node-rs/argon2 * refactor: clean up hashPassword functions * refactor(util): pass in process.platform * fix: use correct settings for test-extension Before, it was running into errors with an @types package. Now, we're correctly running `tsc` so it picks up our `tsconfig.json` and we're telling TypeScript to not typecheck our lib and exclude `node_modules`
* revert: partial revert of 723469a This reverts part of the changes introduced in refactor: migrate from argon2 -> @node-rs/argon2 (coder#4733) Switching to @node-rs/argon2 introduced bugs that we couldn't solve due to limitations in npm. see here coder#4804 (comment)
| Back | FazBrowse Home | New Git URL |
This migrates our hashing password implementation from using argon2 to @node-rs/argon2.
Fixes #4422
How to Test
Tested on
Notes
At first, I ran into some issues with tests because I was overriding process.platform and that caused issues with any test files that required @node-rs/argon2. @code-asher had a good idea to fix this: refactor getEnvPaths() to pass in process.platform. That fixed it.
Resources