Willian Galvani

> We should do something about the navigator model, 10MB looks insane. The advantage is that we can now replace the svgs with hardcoded red squares with component highlights, like...

> Nice! > > Per [my comment](https://github.com/bluerobotics/BlueOS/issues/2567#issuecomment-2079248064) in #2567, this fixes a bug but is only a partial fix for the observed behaviour, because we’re saying MS5611 is a water...

@patrickelectric @joaoantoniocardoso this is what I had in mind for making sure our install scripts match our blueos_startup_update. I am open for suggestions and/or better alternatives. One thing I'm worried...

[this](https://github.com/bluerobotics/BlueOS/pull/2537/files#diff-1b6f61dd35ba0a33383f81ee7443065b1d88729fba34996c986f41235dc8c70b) is the actual test part

@joaoantoniocardoso @JoaoMario109 @patrickelectric how do you guys feel about this? I personally don't like it but I think it is helpful...

on every boot? yes. each patch should be applied once. I do suspect the message is misleading and the issue is how lot it takes to verify each step. The...

we should consider installing tools to diagnose the issue in the image. As we won't be able to install them with malfunctioning dns...

another report, this time the failure is in ardupilot manager failing to get firmwares from the ardupilot manifest: [system_logs.zip](https://github.com/bluerobotics/BlueOS/files/15168298/system_logs_DanielG.zip)

Goal: don’t show ardupilot versions that haven’t been vetted by BR Idea: use default parameter repositories and only show firmware versions that have matching parameters DECISION: Warning dialog for untested...

can you check if the helper had MemoryError? IIRC it also manifests there as being unable to create new threads