Jill Kitten
Assigned
Reported
REALMS-12699
Uploading any world in 1.21.5 Java fails with message “Upload failed! (-1)” after some small percentage of upload.
Duplicate
MC-137154
Structure blocks when loading pop off some comparators [1.13.1 java win7]
Duplicate
MC-136267
Shulker boxes loose custom name after broken and picked up [in java 1.13 as of 2018-08-20]
Cannot Reproduce
Comments
Similar issue in 1.21.5, trying to upload ANY world fails with message “Upload failed (-1)” after some small percentage of upload, even a world I literally just downloaded from the Realm with NO changes to it.
Similar issue in 1.21.5, trying to upload any world fails with message “Upload failed (1)” after some small percentage of upload, even a world I literally just downloaded from the Realm with NO changes to it.
Ok, so after reading the new changes made to the other issue referenced, I had a thought and suspected something and went to go check. The original solid quartz block that the comparitor popped off of that one time looks like a solid quartz block, however when I use the 'pick block' op on it I actually get a quartz slab instead of a solid block despite its appearance of being a solid quartz block. I think it is safe to assume I built it originally as a slab and added another slab to make it a solid block at some point after. So it may still be related to the slab, but I feel this makes the appearance of a solid block misleading in any context if in fact it remembers it as a slab but then has to still treat it as a solid,... This sounds to me like a bug just waiting to happen. This ambiguity of a solid remembering it is a slab may come to bite in the end.
Thank you for addressing this. I seem to remember the original poster stated they had windows 10, so I thought it was for win10, especially since it was set as resolved and I was on a different OS and it was clearly still happening. Again I am not so sure that it only happens on slabs as I did come across one since I originally posted [literally just 1 at one time] that popped off that was NOT on a slab, so I feel it puts into question the assertion of it happening ONLY on slabs. I tried to reproduce the same result from that one incident [repeating the load op in diff locations] and it did not repeat, so I cannot be sure of why it happened that one time or how it may or may not be related. This also should create concern that it may also have a relation to world position, orientation, and such where you may get different results [if even slightly] depending on position, rotation, chunk boundaries, or other position and orientation related effects [e.g. the order in which block updates happen].
I at least hope that this can help resolve this issue and help make the code that much more robust. Again, thank you for addressing this issue.
The issue appears to have went away for 1.13.1.
Similar issue in 1.21.5, trying to upload ANY world fails with message “Upload failed! (-1)” after some small percentage of upload, even a world I literally just downloaded from the Realm with NO changes to it.