Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

build: Added configurations to apply constraints to dependenciesresolves #134#159

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Closed

Conversation

Thedrogon
Copy link

Added configurations to apply constraints to thebuild.gradle dependencies to preventgestalt pulling in dependencies with known CVEs, directly or transitively through things like Reflections. Added some suppressions in various files and as well removed some unnecessary imports

…ent `gestalt` pulling in dependencies with known CVEs, directly or transitively through things like Reflections. Added some suppressions in various files and as well removed some unnecessary imports
@ThedrogonThedrogon changed the titlebuild: Added configurations to apply constraints to dependenciesbuild: Added configurations to apply constraints to dependenciesJan 26, 2025
@ThedrogonThedrogon changed the titlebuild: Added configurations to apply constraints to dependenciesbuild: Added configurations to apply constraints to dependenciesresolves #134Jan 26, 2025
Copy link
Contributor

@BenjaminAmosBenjaminAmos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Thanks for this!

Constraining the dependencies is a useful adjustment but I would rather it was not bundled with other wide-sweeping changes. Suppressing warnings is a last resort as well, since usually we want to see warnings.

… to prevent `gestalt` pulling in dependencies with known CVEs, directly or transitively through things like Reflections. Added some suppressions in various files and as well removed some unnecessary imports"This reverts commit43923eb.
Copy link
Author

@ThedrogonThedrogon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

reverted the changes .

@soloturn
Copy link
Contributor

@BenjaminAmos does this look good to you now? apart from commented stuff which imo should be better removed ...

Copy link
Contributor

@BenjaminAmosBenjaminAmos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I appreciate you trying to make changes for the better but not all warnings are actionable here for reasons that I have tried to explain.

If you could constrain the changes to that tiny but beneficial gradle constraint improvement then this would be much easier to take in. Removing logic in the code without understanding why it is there (this library is quite a central piece of our games) just makes this pull request unviable as-is, I'm afraid.

@@ -328,16 +330,16 @@ Optional<T> createInstance(Asset<U> asset) {
Optional<? extends Asset<U>> result = asset.createCopy(asset.getUrn().getInstanceUrn());
if (!result.isPresent()) {
try {
return AccessController.doPrivileged((PrivilegedExceptionAction<Optional<T>>) () -> {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Despite being deprecated, I'm afraid that for the time being we do still need to use theAccessController APIs. Gestalt sandboxes modules usingSecurityManager as an additional precaution and until it's completely unusable I'd rather have that safety net than not. TheAccessController.doPrivileged calls are needed when running with aSecurityManager active.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Then for the requirement I will revert them in the PR.

@@ -131,7 +133,7 @@ public synchronized void close() {
/**
* Disposes any assets queued for disposal. This occurs if an asset is no longer referenced by anything.
*/
@SuppressWarnings("unchecked")
//@SuppressWarnings("unchecked")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

You can either remove those suppressions or leave them be but commenting them out like that in committed code is rather messy.

@soloturn
Copy link
Contributor

@BenjaminAmos what you think now of this?

@BenjaminAmos
Copy link
Contributor

My comments from before are still valid, I think? The changes remove code needed for gestalt to work withSecurityManager, as well as other unrelated changes. I could probably accept removing unused code but theAccessController.doPrivileged blocks are still needed.

@BenjaminAmos
Copy link
Contributor

This also has merge conflicts now, so it would have to be updated regardless.

@ThedrogonThedrogon closed this by deleting the head repositoryMay 24, 2025
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@soloturnsoloturnsoloturn left review comments

@BenjaminAmosBenjaminAmosBenjaminAmos requested changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@Thedrogon@soloturn@BenjaminAmos

[8]ページ先頭

©2009-2025 Movatter.jp