Pr lthall/20251006 callisto 4.5.7 11 fixes#18
Open
peterbarker wants to merge 13 commits intolthall:20251006_Callisto_4.5.7-11from
Open
Pr lthall/20251006 callisto 4.5.7 11 fixes#18peterbarker wants to merge 13 commits intolthall:20251006_Callisto_4.5.7-11from
peterbarker wants to merge 13 commits intolthall:20251006_Callisto_4.5.7-11from
Conversation
... to avoid the monitor thread's wrath when the main thread has not run for 1.9 seconds
Avoids trying to set parameters when we're popping the context which sets PARAM_SET_ENABLE to its default value of enabled. This can cause permission problems. We need the script to be actuve when we pop the context so we can set the parameter at all, so we can't disable scripting or remove the script and restart. During the infrastructure context pop: 2025-09-30T12:12:45.8005072Z AT-0151.7: PARAM_SET_ENABLE want=1.000000 autopilot=1.0 (attempt=4/40) 2025-09-30T12:12:45.8005691Z AT-0151.7: PARAM_SET_ENABLE is now 1.000000 2025-09-30T12:12:45.8006179Z AT-0151.7: DISARM_DELAY want=10.000000 autopilot=111.0 (attempt=4/40) 2025-09-30T12:12:45.8006714Z AT-0151.7: Sending set (DISARM_DELAY) to (10.000000) (old=111.000000) 2025-09-30T12:12:45.8007217Z AT-0151.7: Received wanted PARAM_VALUE DISARM_DELAY=111.000000 2025-09-30T12:12:45.8007737Z AT-0151.7: DISARM_DELAY want=10.000000 autopilot=111.0 (attempt=5/40) 2025-09-30T12:12:45.8008269Z AT-0151.7: Sending set (DISARM_DELAY) to (10.000000) (old=111.000000) 2025-09-30T12:12:45.8008937Z AT-0151.7: Received wanted PARAM_VALUE DISARM_DELAY=111.000000
Let's fix the GitHub Action workflow macos_build that is failing consistently. * https://github.com/ArduPilot/ardupilot/actions/workflows/macos_build.yml Upgrade pyenv and Python 3.10 in Tools/environment_install/install-prereqs-mac.sh Questions: * Why install and configure pyenv by hand instead of doing `brew install pyenv`? * Why specify the micro version Python 3.10.4 instead of 3.10? * Why not use `brew install uv && uv python install 3.10` instead of pyenv?
several of these environments will no longer work. They are also not relevant to the development of FreeSpace firmware.
the infrastructure in these is broken and they're not relevant to freespace development
lthall
force-pushed
the
20251006_Callisto_4.5.7-11
branch
2 times, most recently
from
b5b99dd to
5d28401
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.