durward2003

Still getting some sort of weird lighting issue, at least around water (my mob farm collection system).

Definitely contained in a chunk, similar as before.

Very minor, but still worth mentioning to see if it's related.

DETAILS:

Original World Generation Version: 1.14

-Upgraded to: 1.14.1 then 1.14.2-pre3 (used --forceUpgrade --eraseCache both times)-

Running As: 1.14.2-pre3 SERVER .jar

Server Render distance: 10

I can send a link to my world files PRE-update and POST-update (update to 1.14.2-pre3) upon request.

UPDATE: I haven't seen any more issues in my world besides this one spot, so it's possible this is just kind of a one-off fluke area. I would be more curious to see if anyone else has issues still. Overall, the update seems good. Thank you for your hard work on this issue!

UPDATE: Turns out this issue is actually unrelated to torch lighting bug (see MC-149518). Thank you ModVioline for pointing this out

I can confirm. On my server,  one of my player's iron farms just would not stop breeding villagers. Most villagers were farming profession. There were 160 beds in the area and eventually we got up to 650+ villager count because they wouldn't stop breeding. 

I just ran into this and I thought it would be significant. This is the first time I have seen the lighting glitch in the nether. Running 1.14.1 vanilla server:

Random side thought - Do chunks load differently in spectator mode? I tend to see the glitch happen more often when I load chunks in spectator mode, although it could just be coincidence.

I have done the following on my server (my server was generated in 1.14 vanilla release)

1. Pulled my servers world files
2. Ran the workaround mentioned above in the 1.14.1 launcher, single player world method (this also upgraded world from 1.14 to 1.14.1)
3. Pushed world files to server
4. Ran server with 1.14.1 jar in multicraft (Apex hosting)

My result is that we are still experiencing the lighting bug but it seems to be a on a much lesser scale than as before on 1.14, or at least the torches are going out at a slower pace.

Simultaneously, the amount of lag we experience now (after updating to 1.14.1) seems dramatically reduced on the server.

This leads me to believe that this issue is lag related on a server. I think people were correlating this bug to nether portals, because nether portals always produce a huge lag spike.

For dev, here is my plan of action on my server:

1. Pull my 1.14 server world files (world was generated in 1.14)

2. Run clear-cache work-around using 1.14.1 as single-player world

3. Re-upload world files to server, run with 1.14.1 server .jar

I will report back if I am still experiencing lighting issues.

Is anyone able to reproduce this bug from scratch in 1.14-pre3 or 1.14-pre4? I haven't been able to yet.

Looking at the comments it seems like nobody had issues during these snapshots. 

If this is the case, that pretty much narrows it down to 1.14-pre5 (most likely nether portal optimizations)

Willian that is very good to know. If I am not mistaken, it was said this bug was fixed in 1.14-pre4. Then, in 1.14pre5 Mojang added NEW nether portal logic, which keeps chunks loaded between nether/overworld for 14 seconds one a player enters/leaves. I wonder if this logic (keeping chunks loaded for 14 seconds) has something to do with the bug?

This also happens when you manually craft an Iron Golem against a wall. I have to break the blocks behind him so he doesn't suffocate.

Upgraded my 1.14 Vanilla Server World to a 1.14.1-pre-2 Single Player World.

Lighting issue still exists after upgrade:

Unfortunately, I have to agree with Gary Cousins. My players on my server are EXTREMELY unhappy with this glitch because they are having things like Iron Golems dying in their slime farms. 

I also think this is a showstopper bug.

I think this is the worst bug of 1.14 (even more than the chunk rendering bug). My vote would be to fix this before 1.14.1 release if possible.

I will do my best to continue to help with this issue as well.

From the above few comments, I can also confirm this happens on newly generated 1.14 vanilla server worlds, not just worlds upgraded from 1.13.2

That is extremely interesting regarding the slime chunks. I just made a slime farm on my 1.14 vanilla server and almost every torch light was bugged out when I restarted and logged back in.

I went back onto my server and did a survey of my slime chunks with regards to torches going out. Unfortunately, test inconclusive - there were chunks with torches out that were NOT slime chunks.

1.14 Vanilla

Georgii if it helps, this tends to trigger for me when I reboot my server. My server is hosted at Apex using multi-craft interface. Every time I reboot, the more torches go out each time. that's when I notice. It seems to be elongated over time thing.

Confirmed that this is currently breaking our vanilla 1.14 server as well. I need to apply work-around mentioned above every few days or so. Causes about 30 minutes of server downtime per instance (problem grows larger as our world gets explored more).

This is happening to me as well on my 1.14 vanilla server (NO SPIGOT). Whenever the server restarts, things like brewing stands disappear. We also have a name-tagged endermite in a minecart in The End. This endermite+the minecart has disappeared after certain reboots. Hope this is helpful. 

CORRECTION - I have made some edits to the original comment. This issue is kind of sporadic and unpredictable when these entities get reset. I wish I could be more helpful but I don't know what the cause of the problem is :/ . My player who experienced the issue with the endermite thinks it has something to do with a chunk loading while the server was reset (possible race condition thing?) I didn't do a hard-shutdown either, I let the server gracefully shutdown using the restart command in multicraft. 

I am also having this problem on my 1.14 server. The endermite disappears after server reboot.