Skip to content
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

Failed to modify player's pipeline. (NoSuchElementException/packet_handler) #219

Open
2 tasks done
andrewkm opened this issue Jun 19, 2024 · 4 comments
Open
2 tasks done
Labels
bug Something isn't working

Comments

@andrewkm
Copy link

andrewkm commented Jun 19, 2024

Just making sure

  • I made sure, this bug is not already known or reported.
  • I believe, that this bug is fixable.

Reproduction

Looks to happen immediately after the player's login,
Unknown reproduction.

[17:36:00] [Netty Server IO #1/WARN]: [DecentHolograms] Failed to modify player's pipeline. (AusRoona)
java.util.NoSuchElementException: packet_handler
	at io.netty.channel.DefaultChannelPipeline.getContextOrDie(DefaultChannelPipeline.java:1073) ~[netty-transport-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.channel.DefaultChannelPipeline.addBefore(DefaultChannelPipeline.java:248) ~[netty-transport-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.channel.DefaultChannelPipeline.addBefore(DefaultChannelPipeline.java:237) ~[netty-transport-4.1.97.Final.jar:4.1.97.Final]
	at DecentHolograms-2.8.9.jar/eu.decentsoftware.holograms.api.nms.PacketListener.lambda$hook$0(PacketListener.java:30) ~[DecentHolograms-2.8.9.jar:?]
	at DecentHolograms-2.8.9.jar/eu.decentsoftware.holograms.api.nms.PacketListener.executeOnPipeline(PacketListener.java:52) ~[DecentHolograms-2.8.9.jar:?]
	at DecentHolograms-2.8.9.jar/eu.decentsoftware.holograms.api.nms.PacketListener.lambda$executeOnPipeline$2(PacketListener.java:54) ~[DecentHolograms-2.8.9.jar:?]
	at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174) ~[netty-common-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167) ~[netty-common-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470) ~[netty-common-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569) ~[netty-transport-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[netty-common-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.97.Final.jar:4.1.97.Final]
	at java.base/java.lang.Thread.run(Thread.java:1570) ~[?:?]

Solution

No response

Server Version

Paper version 1.20.6-147-ver/1.20.6@e41d44f

Client Version

Cannot detect the player's client version nor are they available to ask.

Plugin Version

2.8.9 - Compiled against (24af340)

Log

https://pastebin.com/raw/bC0MWxUV

@andrewkm andrewkm added the bug Something isn't working label Jun 19, 2024
@d0by1
Copy link
Member

d0by1 commented Aug 23, 2024

Hi, I've added additional details to the log message associated with this error in DH 2.8.10. Could you please test the issue in this new version and share the updated log message with me? Thanks!

@IAISI
Copy link

IAISI commented Oct 30, 2024

Still an issue on

> ver DecentHolograms
[22:34:48 INFO]: DecentHolograms version 2.8.11
[22:34:48 INFO]: A lightweight yet very powerful hologram plugin with many features and configuration options.
[22:34:48 INFO]: Author: d0by

and latest Paper 1.21.1

[22:24:32] [Netty Epoll Server IO #2/WARN]: [DecentHolograms] Failed to modify player's pipeline. player: PlayerName, availableElements: [DefaultChannelPipeline$TailContext#0]
java.util.NoSuchElementException: packet_handler
	at io.netty.channel.DefaultChannelPipeline.getContextOrDie(DefaultChannelPipeline.java:1073) ~[netty-transport-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.channel.DefaultChannelPipeline.addBefore(DefaultChannelPipeline.java:248) ~[netty-transport-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.channel.DefaultChannelPipeline.addBefore(DefaultChannelPipeline.java:237) ~[netty-transport-4.1.97.Final.jar:4.1.97.Final]
	at DecentHolograms.jar/eu.decentsoftware.holograms.api.nms.PacketListener.lambda$hook$0(PacketListener.java:32) ~[DecentHolograms.jar:?]
	at DecentHolograms.jar/eu.decentsoftware.holograms.api.nms.PacketListener.executeOnPipeline(PacketListener.java:54) ~[DecentHolograms.jar:?]
	at DecentHolograms.jar/eu.decentsoftware.holograms.api.nms.PacketListener.lambda$executeOnPipeline$2(PacketListener.java:56) ~[DecentHolograms.jar:?]
	at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174) ~[netty-common-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167) ~[netty-common-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470) ~[netty-common-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:413) ~[netty-transport-classes-epoll-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[netty-common-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.97.Final.jar:4.1.97.Final]
	at java.base/java.lang.Thread.run(Thread.java:1583) ~[?:?]
[22:24:32] [Server thread/INFO]: PlayerName lost connection: Disconnected

Also using ViaVersion, ViaBackwards and ViaRewind

@andrewkm
Copy link
Author

Still an issue here on our end via Paper 1.21.3 Build 50.

[11:14:15] [Server thread/INFO]: playername[/redacted-IP] logged in with entity id 12769168 at ([rising]2669.5, 74.0, -9596.5)
[11:14:16] [Netty Server IO #0/WARN]: [DecentHolograms] Failed to modify player's pipeline. player: playername, availableElements: [DefaultChannelPipeline$TailContext#0]
java.util.NoSuchElementException: packet_handler
	at io.netty.channel.DefaultChannelPipeline.getContextOrDie(DefaultChannelPipeline.java:1073) ~[netty-transport-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.channel.DefaultChannelPipeline.addBefore(DefaultChannelPipeline.java:248) ~[netty-transport-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.channel.DefaultChannelPipeline.addBefore(DefaultChannelPipeline.java:237) ~[netty-transport-4.1.97.Final.jar:4.1.97.Final]
	at DecentHolograms-2.8.12.jar/eu.decentsoftware.holograms.api.nms.PacketListener.lambda$hook$0(PacketListener.java:32) ~[DecentHolograms-2.8.12.jar:?]
	at DecentHolograms-2.8.12.jar/eu.decentsoftware.holograms.api.nms.PacketListener.executeOnPipeline(PacketListener.java:54) ~[DecentHolograms-2.8.12.jar:?]
	at DecentHolograms-2.8.12.jar/eu.decentsoftware.holograms.api.nms.PacketListener.lambda$executeOnPipeline$2(PacketListener.java:56) ~[DecentHolograms-2.8.12.jar:?]
	at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:174) ~[netty-common-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:167) ~[netty-common-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470) ~[netty-common-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569) ~[netty-transport-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) ~[netty-common-4.1.97.Final.jar:4.1.97.Final]
	at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.97.Final.jar:4.1.97.Final]
	at java.base/java.lang.Thread.run(Thread.java:1575) ~[?:?]
[11:14:16] [Server thread/INFO]: playername lost connection: Kicked for exceeding packet rate limit

@d0by1

@Andre601
Copy link
Contributor

The last line seems to be interesting:
playername lost connection: Kicked for exceeding packet rate limit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants