.
├── src/
│ ├── classes
│ └── module
├── main
└── shared events
main starts a thread with main logic…
module starts a which is audio playing…
in module, after let’s say 5 seconds.
self.logger.debug(f"Setting audio_finished_event.")
audio_finished_event.set()
main:
def wait_for_audio_play():
logger.info(f"Stopping to wait for audio to play)
audio_finished_event.wait() <<<<<<<< DOES NOT CARE AT ALL
audio_started_event.clear()
logger.info(f"Finished waiting") <<<<<<<<< GOES STRAIGHT TO
…. we reach:
if audio_started_event.is_set():
wait_for_audio_play()
NOT ONLY does the waiting never happens, the MODULE SETS the event WITHOUT LOGGING.
There is LITERALLY ONE PLACE in the code where the event is set and it’s this one…
IS this some classic noob trap I don’t get ?????????? Spent almost 20hours on this.
I’m only hoping there’s some known issue with that cause I’ve tried way too much for way too long to describe it.
I’m ready to get flamed I can’t handle the pain anymore I don’t care
Lvl 1 Coder is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
1