decnet deploy spawns a standalone profiler daemon AND api.py was also starting attacker_profile_worker as an asyncio task inside the web server. Both instances shared the same attacker_worker_cursor key in the state table, causing a race where one instance could skip events already claimed by the other or overwrite the cursor mid-batch. Default is now OFF (embedded profiler disabled). The standalone daemon started by decnet deploy is the single authoritative instance. Set DECNET_EMBED_PROFILER=true only when running decnet api in isolation without a full deploy.
8.8 KiB
8.8 KiB