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

Race condition for ScheduleDestroy events when reseting the environment #114

Open
Kakadus opened this issue Apr 9, 2024 · 0 comments · May be fixed by #115
Open

Race condition for ScheduleDestroy events when reseting the environment #114

Kakadus opened this issue Apr 9, 2024 · 0 comments · May be fixed by #115

Comments

@Kakadus
Copy link
Contributor

Kakadus commented Apr 9, 2024

Resetting a running environment sends a close_command to the simulation. Then, the ns3 simulator is destroyed, and all ScheduleDestroy events should be handled:

Simulator::Stop();
Simulator::Destroy();

In parallel, the experiment is runned again, which kills the old environment and interrupts the ScheduleDestroy events.

def run(self, setting=None, show_output=False):
self.kill()

Instead, I expected that all events scheduled with ScheduleDestroy are executed when I reset the environment. It would be a nice feature to execute these events, when I close the environment.

@Kakadus Kakadus linked a pull request Apr 10, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant