Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Multiworld Watcher Multiworld Watcher
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 27
    • Issues 27
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Terraform modules
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Q4SG
  • Multiworld WatcherMultiworld Watcher
  • Issues
  • #91
Closed
Open
Issue created Mar 08, 2023 by Adam "MrBond" Ziegler@MrBondOwner

Duplicate threads created from rapid log processing

watcher module: when threaded output is enabled, processing multiple messages with the same channel/world combination in rapid succession may create multiple threads. The last thread created is saved to the world's output, leaving previous threads as orphans, and any messages within will not be reachable for future reactions.

Example scenarios:

  • Forfeit / release sends all remaining items
  • Rapid hint sends e.g. for Hollow Knight worlds

Two possible resolutions:

  1. Queue messages internally such that they are processed serially; or
  2. Set up all initial threads on module start, such that all channel/world thread IDs are populated before being used
Assignee
Assign to
Time tracking