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

Implement handle_spec_setup_completed and handle_spec_playing. Release v1.1.0-rc1. #801

Open
wants to merge 8 commits into
base: master
Choose a base branch
from

Conversation

FelonEkonom
Copy link
Member

@FelonEkonom FelonEkonom commented May 13, 2024

Closes #796
Relates to #786

@FelonEkonom FelonEkonom self-assigned this May 13, 2024
@FelonEkonom FelonEkonom requested a review from mat-hek as a code owner May 13, 2024 09:24
@FelonEkonom FelonEkonom added no-changelog This label has to be added if changes from the PR are not meant to be placed in the CHANGELOG.md and removed no-changelog This label has to be added if changes from the PR are not meant to be placed in the CHANGELOG.md labels May 13, 2024
@FelonEkonom FelonEkonom changed the title Implement handle_spec_setup_completed and handle_spec_playing Implement handle_spec_setup_completed and handle_spec_playing. Release v1.1.0-rc0. May 13, 2024
@FelonEkonom FelonEkonom changed the title Implement handle_spec_setup_completed and handle_spec_playing. Release v1.1.0-rc0. Implement handle_spec_setup_completed and handle_spec_playing. Release v1.1.0-rc1. May 13, 2024
Comment on lines 324 to 325
MapSet.to_list(spec_data.children_names)
|> StartupUtils.exec_handle_spec_setup_completed(state)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem here is that the children_names can be empty, and we call handle_spec_started with an empty list. This makes me lean towards having handle_child_setup and handle_child_playing instead.

@FelonEkonom FelonEkonom requested a review from mat-hek May 22, 2024 11:23
@@ -38,6 +41,7 @@ defmodule Membrane.ChildEntry do
:group,
initialized?: false,
ready?: false,
terminating?: false
terminating?: false,
playback: :stopped
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why exactly do we need that?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Before my changes we have been sending :play to each child between 1 and 2 times. This field allows me distinct, if I have already done it, because I don't want to execute callback handle_child_playing more than once for a single child

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we never send play two times. If we do, it seems like a bug.

@FelonEkonom FelonEkonom requested a review from mat-hek May 28, 2024 08:40
@@ -38,6 +41,7 @@ defmodule Membrane.ChildEntry do
:group,
initialized?: false,
ready?: false,
terminating?: false
terminating?: false,
playback: :stopped
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we never send play two times. If we do, it seems like a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Review
Development

Successfully merging this pull request may close these issues.

Add handle_spec_playing
2 participants