Open yangxin325 opened 2 years ago
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm WARN deprecated debug@4.2.0: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm ERR! code 1
npm ERR! path C:\Users\HUAWEI\Downloads\unredacter-main\node_modules\electron
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node install.js
npm ERR! RequestError: read ECONNRESET
npm ERR! at ClientRequest.
npm ERR! A complete log of this run can be found in: npm ERR! D:\Program Files\nodejs\node_cache_logs\2022-02-26T09_17_13_337Z-debug-0.log
Subsequent installation errors occur in Windows PowerShell
No idea what's up with those warnings.
But in terms of speed, just how slow is "like a snail"? That's rather subjective. Can you try to guesstimate how many iterations per second you're getting?
There is an error, and the cracking speed is very slow,like a snail.
npm start
(node:8300) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. (node:20660) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Steps to Reproduce
First npm install, second npm start
Additional context
Win10 , Desktop, Browser:Google Chrome vision 98.0.4758.102 , 2022.2.22
Relevant screenshots