Improper shading used within node #1244
Labels
p: high
This issue or pull request has a high priority.
s: confirmed
The described bug was reported multiple times and/or is reproduceable
t: bug
Something isn't working as intended
v: 4.X
This pull should be included in the 4.0 release
Stacktrace
No response
Actions to reproduce
CloudNet version
[03.06 23:12:54.195] INFO:
[03.06 23:12:54.195] INFO: CloudNet Blizzard 4.0.0-RC9-SNAPSHOT 1619e68
[03.06 23:12:54.195] INFO: Discord: https://discord.cloudnetservice.eu/
[03.06 23:12:54.195] INFO:
[03.06 23:12:54.195] INFO: ClusterId: 2e8f442a--41f4--861d5dfef0a4
[03.06 23:12:54.195] INFO: NodeId: Node-1
[03.06 23:12:54.195] INFO: Head-NodeId: Node-1
[03.06 23:12:54.195] INFO: CPU usage: (P/S) .16/20.16/100%
[03.06 23:12:54.195] INFO: Node services memory allocation (U/R/M): 11776/11776/63803 MB
[03.06 23:12:54.195] INFO: Threads: 100
[03.06 23:12:54.195] INFO: Heap usage: 62/256MB
[03.06 23:12:54.195] INFO: JVM: Private Build 17 (OpenJDK 64-Bit Server VM 17.0.7+7-Ubuntu-0ubuntu120.04)
[03.06 23:12:54.195] INFO: Update Repo: CloudNetService/launchermeta, Update Branch: nightly
[03.06 23:12:54.195] INFO:
Other
When we use the node dependency
When we don't use it
A potential solution would be to relocate the dependencies instead of directly shading it with the shadow plugin, to avoid conflicts like this
Issue uniqueness
The text was updated successfully, but these errors were encountered: