Remove PacketPipelineSetup to fix application startup crash
The PacketPipelineSetup was attempting to subscribe to a single PacketConsumer process that doesn't exist. The application uses PacketConsumerPool which automatically handles subscriptions for multiple consumer processes, making PacketPipelineSetup redundant and causing startup failures. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
parent
ad2d9c14cf
commit
e41118a243
1 changed files with 1 additions and 3 deletions
|
|
@ -55,9 +55,7 @@ defmodule Aprsme.Application do
|
||||||
Aprsme.Presence,
|
Aprsme.Presence,
|
||||||
Aprsme.PostgresNotifier,
|
Aprsme.PostgresNotifier,
|
||||||
# Start the packet processing pipeline
|
# Start the packet processing pipeline
|
||||||
Aprsme.PacketPipelineSupervisor,
|
Aprsme.PacketPipelineSupervisor
|
||||||
# Start the packet pipeline setup
|
|
||||||
Aprsme.PacketPipelineSetup
|
|
||||||
]
|
]
|
||||||
|
|
||||||
children = maybe_add_is_supervisor(children, Application.get_env(:aprsme, :env))
|
children = maybe_add_is_supervisor(children, Application.get_env(:aprsme, :env))
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue