The soopyv2 from soopyboo32

Minecraft Keeps Freezing When I Use Soopy

Minecraft freezes when I move around in hypixle skyblock, I tried disabling soopy and it stopped freezing. I would like to continue using soopy but can't play with it right now. My RAM and cpu say that they are fine and my ping to hypixle is really good.

HTTP request withou TLS cert

Why do you use a GET function on your website which has a tls certifcate and u dont use it in yyour code.

Chat getting spammed by soopy messages.

I am getting spammed in chat by soopy messages
"[SOOPY V2] Successfully reset powder data."

Didn't change any settings, few hours ago, this wasn't happening at all.

I keep getting these random green lines and have gone through every mod and find that the problem is soopy i can send screen shot of the random lines if need be but think this is a bug with this version cause no one else sees it on their screen.

GitHub actions build fail and warnings

Although updating in game via soopy changelog works so I wonder if that does something different?

Here are all the warnings and errors (copied from actions of last commit but i get the same warnings and error when cloning the repo and trying locally, except the check_compiles node 12 warning):

Actions output

Check_Compiles
Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: actions/checkout@v2

npm WARN deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

2 critical severity vulnerabilities

TypeError: /home/runner/work/SoopyV2/SoopyV2/src/featureClass/class.js: Cannot read properties of undefined (reading 'split')
    at PluginPass.ImportDeclaration (file:///home/runner/work/SoopyV2/SoopyV2/babel-import-promise/babel-import-promise.mjs:6:57)
    at newFn (/home/runner/work/SoopyV2/SoopyV2/node_modules/@babel/traverse/lib/visitors.js:181:21)
    at NodePath._call (/home/runner/work/SoopyV2/SoopyV2/node_modules/@babel/traverse/lib/path/context.js:53:20)
    at NodePath.call (/home/runner/work/SoopyV2/SoopyV2/node_modules/@babel/traverse/lib/path/context.js:40:17)
    at NodePath.visit (/home/runner/work/SoopyV2/SoopyV2/node_modules/@babel/traverse/lib/path/context.js:100:31)
    at TraversalContext.visitQueue (/home/runner/work/SoopyV2/SoopyV2/node_modules/@babel/traverse/lib/context.js:105:16)
    at TraversalContext.visitMultiple (/home/runner/work/SoopyV2/SoopyV2/node_modules/@babel/traverse/lib/context.js:74:17)
    at TraversalContext.visit (/home/runner/work/SoopyV2/SoopyV2/node_modules/@babel/traverse/lib/context.js:131:19)
    at traverseNode (/home/runner/work/SoopyV2/SoopyV2/node_modules/@babel/traverse/lib/traverse-node.js:24:17)
    at NodePath.visit (/home/runner/work/SoopyV2/SoopyV2/node_modules/@babel/traverse/lib/path/context.js:107:52) {
  code: 'BABEL_TRANSFORM_ERROR'
}
Error: Process completed with exit code 1.

npm auidit result:

npm audit result

$ npm audit
# npm audit report

js-extend  *
Severity: critical
Prototype pollution vulnerability in js-extend - https://github.com/advisories/GHSA-mh82-55cm-6gfh
No fix available
node_modules/js-extend
  babel-plugin-async-to-promises  *
  Depends on vulnerable versions of js-extend
  node_modules/babel-plugin-async-to-promises

2 critical severity vulnerabilities

Some issues need review, and may require choosing
a different dependency.

tried running npm update to see if it fixes any audit issues although it didn't (Maybe add package-lock.json file to gitignore or run npm update before building to update dependencies, or pin specific versions, because otherwise it will keep using the version in package-lock.json and never update unless you run npm update as far as I can see):

npm outdated & npm update result

$ npm outdated
Package      Current  Wanted  Latest  Location                  Depended by
@babel/cli   7.18.10  7.19.3  7.19.3  node_modules/@babel/cli   SoopyV2
@babel/core   7.19.1  7.20.2  7.20.2  node_modules/@babel/core  SoopyV2
$ npm update

removed 1 package, changed 17 packages, and audited 114 packages in 9s

7 packages are looking for funding
  run `npm fund` for details

2 critical severity vulnerabilities

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.

I don't really know how to fix any of this except the first one, which can be easily fixed by updating actions/checkout@v2 to actions/checkout@v3.

After searching the core-js warning I found the command to find where a transitive dependency comes from (I'm mainly a java dev so know nothing about npm/node not gonna lie):

source of audit warnings

$ npm ls core-js@2
SoopyV2@ /home/<redacted>/SoopyV2
└─┬ [email protected]
  └─┬ [email protected]
    └─┬ [email protected]
      └── [email protected]

$ npm ls js-extend
SoopyV2@ /home/<redacted>/SoopyV2
└─┬ [email protected]
  └── [email protected]

So the culprit for the warnings looks like the babel-plugin-async-to-promises. After looking it up on NPM I saw it last updated 7 years ago. Searching for an alternative, the first result was https://www.npmjs.com/package/babel-plugin-transform-async-to-promises , which seems to be updated 1 year ago and has 0 dependencies (if you don't have any dependencies you can't have vulnerable dependencies duh), maybe it can be switched into without much hassle?

And yes I know those warnings don't have anything to do with the actual build failure, i.e, the last line where it fails to find split function (maybe since toString probably returns a java.lang.String and babel thinks its a js string or something?) but warnings are still important and something last updated 7 years ago shouldn't be used anymore IMO

By the way I ran into those because I was gonna make a PR to contribute a fix, I don't know if it would have any errors since I can't build it, but I tested it in-game by changing the source in ./minecraft/config/ChatTriggers/modules/SoopyV2

I will start making PRs to fix any of the issues I mentioned that I know the fixes of after opening this issue, however the PRs will show red mark (build failure) until the actual failure gets fixed.

Terminals

Whenever I try to click into terminals, I cannot click the panes. I did not have this problem before downloading chat triggers and soopyv2. To be clear I do have other chat triggers mods which I have linked an image to. I have tried with the improved skyblock clicks both on and off. I have searched for a setting besides that which would change clicking but I have not found anything else. https://cdn.discordapp.com/attachments/1040497901606010892/1049503999704969276/image.png

soopyboo32 / soopyv2 Goto Github PK

soopyv2's People

Contributors

Stargazers

Watchers

Forkers

soopyv2's Issues

Minecraft Keeps Freezing When I Use Soopy

HTTP request withou TLS cert

Chat getting spammed by soopy messages.

I keep getting these random green lines and have gone through every mod and find that the problem is soopy i can send screen shot of the random lines if need be but think this is a bug with this version cause no one else sees it on their screen.

GitHub actions build fail and warnings

Terminals

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent