Skip to content

Conversation

@dsilhavy
Copy link
Contributor

@dsilhavy dsilhavy commented Oct 9, 2025

This PR adds an option to specify an output directory for the files that are received in the FLUTE receiver example. That way we can avoid overwriting files that are sent from the same machine as the receiver is running on.

@jordijoangimenez
Copy link
Contributor

And Daniel did the magic in 5 mins. I can check but not sure when.... If it's urgent and you checked it works, go ahead.

@dsilhavy
Copy link
Contributor Author

dsilhavy commented Oct 9, 2025

Thanks @jordijoangimenez . Maybe @davidjwbbc can take a quick look if there are any flaws in the code.

Copy link
Contributor

@davidjwbbc davidjwbbc left a comment

Choose a reason for hiding this comment

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

I've done a test with the transmitter and receiver and there were no issues. I transmitted a file, got it to store in the output directory and diff'd the two to show there were no transmission/reception problems. Everything looks good to me.

@davidjwbbc davidjwbbc moved this to In Progress in MBMS: Support for FLUTE Oct 9, 2025
@davidjwbbc davidjwbbc added the enhancement New feature or request label Oct 9, 2025
@dsilhavy
Copy link
Contributor Author

Thanks, @davidjwbbc, I will include this in the upcoming release then

@dsilhavy dsilhavy merged commit 53b1188 into development Oct 10, 2025
1 check passed
@github-project-automation github-project-automation bot moved this from In Progress to Done in MBMS: Support for FLUTE Oct 10, 2025
@dsilhavy dsilhavy deleted the feature/flute-receiver-output-path branch October 10, 2025 05:58
@dsilhavy dsilhavy modified the milestones: 0.12.0, 0.11.0 Oct 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

Development

Successfully merging this pull request may close these issues.

4 participants