Fix secondary sensor deletion and algorithm stability#1
Fix secondary sensor deletion and algorithm stability#1ctqwa wants to merge 2 commits intodev-latestfrom
Conversation
- SensorViewModel: Added forceDeleteSensorDirectory to ensure corrupted sensor files are removed from disk. - sensoren.hpp: Modified addsensor to only set 'current' sensor if none is selected, preventing secondary sensors from hijacking the algorithm state. Co-authored-by: ctqwa <3178592+ctqwa@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
- SensorViewModel: Added forceDeleteSensorDirectory to ensure corrupted sensor files are removed from disk. - sensoren.hpp: Modified addsensor to only set 'current' sensor if none is selected, preventing secondary sensors from hijacking the algorithm state. Co-authored-by: ctqwa <3178592+ctqwa@users.noreply.github.com>
1 participant
SensorViewModel.ktto robustly delete sensor directories when "Wipe Data" is selected, even if native calls fail or the sensor state is corrupted.Common/src/main/cpp/sensoren.hppto prevent the algorithm from automatically switching to a newly added sensor if a valid sensor is already active ("tied to its first sensor").PR created automatically by Jules for task 6507488236282328971 started by @ctqwa