Alexander Städing
Alexander Städing
> Can I recommend the new version catalogues feature introduced in Gradle 7.0 over declaring versions in gradle.properties? You can declare all of your dependencies in a TOML file and...
> @alexstaeding Are you able to update this pull request again? I pushed a few changes that break this a bit. Yeah, I'll have a look at it in the...
Fixed by #64
Naturally, immediately after submitting the issue, I discovered my blunder: The `singleOf` utility method assumes all constructor parameters are to be initialized with `get()` and does not use `getAll()` as...
I believe nucleus also registers the aliases /nanvil and /nucleus:anvil which you should be able to use for now. I'm still deciding on the best way to implement this fix...
Anvil no longer comes with any commands, so I will close this
I agree with your point that these callback-style futures are extremely prone to exception swallowing. This is one of the reasons I have been planning for a while to switch...
I imagine this is fixed now by #64. There shouldn't be any java futures anymore - and all coroutines should be joined to some main thread now.
I had a look at the Dockerfile, I'm pretty sure this command is causing the problem: https://github.com/itzg/docker-bungeecord/blob/04df9fedbe3c23bfa9597ce525e465049e7b7099/Dockerfile#L18-L19 Setting the home directory to `/server` will cause a `chown` on the whole...
I see two possible solutions: 1. Leave the image as-is. Modify the persisted `velocity.toml` to point to a `forwarding.secret` mounted outside of the `/server` directory. This is unclean as it...