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

MacOS/Windows bug with Daemon/Coordinator on 0.3.5rc0 #575

Closed
Hennzau opened this issue Jul 2, 2024 · 6 comments · Fixed by #583
Closed

MacOS/Windows bug with Daemon/Coordinator on 0.3.5rc0 #575

Hennzau opened this issue Jul 2, 2024 · 6 comments · Fixed by #583
Labels

Comments

@Hennzau
Copy link
Collaborator

Hennzau commented Jul 2, 2024

Describe the bug

When I launch a dataflow where a node is dynamic, I can't stop it; no crash of coordinator or daemon (CTRL+C if attached, dora stop if detached).

To Reproduce
Steps to reproduce the behavior:

  1. Dora start daemon: dora up
  2. Start a new dataflow: dora start dataflow.yaml (optional: --detach)
  3. Stop dataflow: dora stop / CTRL+C
    At this step it blocks until I do:
  4. Destroy dataflow: dora destroy

On windows, i can only tell that when i want to do dora stop it blocks. Because CTRL+C in attached mode always make the coordinator crash

Environments (please complete the following information):

  • System info: MacOS
  • Dora version: 0.3.5rc0
@github-actions github-actions bot added bug Something isn't working coordinator daemon labels Jul 2, 2024
@Hennzau Hennzau changed the title MacOS bug on 0.3.5rc0 MacOS bug with Daemon/Coordinator on 0.3.5rc0 Jul 2, 2024
@Hennzau Hennzau changed the title MacOS bug with Daemon/Coordinator on 0.3.5rc0 MacOS/Windows bug with Daemon/Coordinator on 0.3.5rc0 Jul 2, 2024
@Hennzau
Copy link
Collaborator Author

Hennzau commented Jul 2, 2024

on windows I have this error in dora-coordinator output file:

2024-07-01T19:56:46.554799Z ERROR dora_coordinator::control: failed to send reply
2024-07-01T19:56:46.554844Z ERROR dora_coordinator::control: failed to send reply

@haixuanTao
Copy link
Collaborator

haixuanTao commented Jul 3, 2024

I'm unable to reproduce. I get the following behaviour:

2024-07-03.08-35-07.mp4

Are you saying that the dynamic node is not stopping? Or that the dataflow is not stopping?

P.S: Sorry the screen recording only recorded half of the screen.

@Hennzau
Copy link
Collaborator Author

Hennzau commented Jul 3, 2024

Hi, it's the dataflow that is not stopping. Even if I don't run the dynamic node, i'm unable to stop the dataflow. Here is a record:

Enregistrement.de.l.ecran.2024-07-03.a.08.48.19.mov

@haixuanTao
Copy link
Collaborator

So I think that you might need to start the dynamic node first before stopping the dataflow. I think not starting the dataflow is going to make it impossible to stop a not started dataflow.

I think we should fix this but this might be your error.

@phil-opp
Copy link
Collaborator

I opened #583 with a potential fix. Perhaps you could give it a try if you have time, @Hennzau?

@Hennzau
Copy link
Collaborator Author

Hennzau commented Jul 11, 2024

I opened #583 with a potential fix. Perhaps you could give it a try if you have time, @Hennzau?

Hi! It works now! Thanks

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

Successfully merging a pull request may close this issue.

3 participants