-
Notifications
You must be signed in to change notification settings - Fork 81
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
YAML comments duplication #480
Comments
Might be fixed by #361. I doubt it, but there's a chance. |
When might we a have a chance to test the proposition. There hasn't been a dev build for six months, unless I'm looking in the wrong place. |
Actually, I'm running a server right now and can confirm the issue. I'll also test whether the PR fixes it later today or tomorrow. |
This might actually be a |
Paper is fixing things that wouldn't be broken if folks used the new snakeyaml API correctly. But this issue occurs on both Spigot and Paper 1.18.1 presently. |
paper's bugfix is for files with 100+ lines of adjacent comments crashing the server, not comment duplication |
A quick patch version of mv-inv to disable comments for now (wont effect any functionality): |
Off topic: Yeah, it wouldn't hurt for known bug fixes to end up on Jenkins again with tested builds. On topic: I am using Paper and I can confirm this issue. I have a MVi yml file that's over a megabyte and it's full of duped comments, and I dont' use /reload or even touch mvc/mvi, it just runs there helping me have some worlds. Thanks ben for the temp zip i will clean up the yml files and start the server with that jar and see how it goes, also good to see spigot's fix upstream to paper. Another one that has 50 to 150 mb yml files is mcMMO, if ppl use mcMMO, go get the latest github compile from their jenkins or something to help mitigate it. |
The reason ben's build isn't on Jenkins is because it's just a stopgap. The actual fix is simple enough and shouldn't take too much work. I just tested #361, and as suspected, it doesn't help. It does however make it easier to implement the actual fix, so hopefully we can get it merged soon and then we can start working on this bug! |
I read this, then i wake up today to see a fix on jenkins, only to now learn it's the stopgap build and not the actual fix. How is this helping .. And the ticket is closed. Implying the issue is resolved. But i guess it's automated ~ just confusing. |
I see you're a bit confused on this. #361 is not a ticket. It's the code that ended up in that new Jenkins build that you mentioned. That Jenkins build is also different than the stopgap that ben posted. The build on Jenkins is just some general cleanup to the code that handles our config files. #483 is the actual fix I mentioned. |
Thanks for explaining. But before I go to bed I ask why it's not on jenkins, and it's explained why not. Next morning I see this closed and it's on Jenkins, so I assume it's fixed. Then I mention this to sliced who says it's not. So yes, it's confusing. I hope "what is useful for me as server owner to resolve this snake crap debacle" is released fully then soon. So I can focus on the next plugin that causes issues for servers for me. Best of luck everybody ~ thanks for the stopgap jar |
Issue still exists in Multiverse-Inventories 4.2.3-b521. |
Confirmed fixed in b522. Thanks. |
Information
/mv version -p
:Irrelevant
Details
I was
able
to reproduce my issue on a freshly setup and up-to-date server with the latest version of Multiverse plugins with no other plugins and with no kinds of other server or client mods.Description
Due to the new snakeyaml updates, coupled with the fact that MV rewrites configuration files on every server start-up, the comments in MV-Inventory config.yml and groups.yml are duplicated at each server start-up.
Steps to reproduce
Expected behavior
Static configuration files.
The text was updated successfully, but these errors were encountered: