Skip to content

Conversation

@diegosoriarios
Copy link

@diegosoriarios diegosoriarios commented Nov 14, 2025

Trying to install Valdi on my machine I got some problems trying to build, looking at the code I realized it was because I am using Fedora and the config was built to work with debian based distros.
This pull request add Linux distribution support in the CLI setup process, providing tailored installation commands and setup logic for both Ubuntu and Fedora systems. The changes improve the user experience by detecting the user's Linux distribution and running the appropriate dependency installation steps, rather than assuming all users are on Ubuntu. Additionally, the doctor command now gives more accurate instructions for resolving missing dependencies based on the detected distribution.

Linux distribution detection and setup:

  • Added detection for Ubuntu and Fedora distributions in linuxSetup.ts, and refactored the main setup logic to delegate to new, distro-specific setup functions (ubuntuSetup and fedoraSetup). If an unsupported distro is detected, a clear error message is shown.
  • Implemented ubuntuSetup.ts and fedoraSetup.ts to encapsulate the installation steps for each distribution, including dependency installation and Java runtime checks.

Improved dependency installation instructions:

  • Updated the ValdiDoctor class to provide more accurate fix commands for missing dependencies, using sudo apt-get for Ubuntu, sudo dnf for Fedora, and a generic message for other distributions.
  • Imported the new distro detection helpers (isFedora, isUbuntu) into the doctor command for use in generating these instructions.

If anyone have any other changes feel free to change.

@diegosoriarios diegosoriarios changed the title Add fedora-setup option depending of which distro you are in Add Fedora setup option depending of which distro you are in Nov 14, 2025
jfuginay added a commit to jfuginay/omni-BASE that referenced this pull request Dec 31, 2025
* Fix CoT message handling and add debug logging for teammate display issue

- Add comprehensive debug logging throughout the CoT message pipeline to
  diagnose why teammates may not appear on map
- Fix cotEvents array deduplication by UID to prevent memory growth
- Add stale event cleanup (removes events older than 1 hour every 5 min)
- Improve CoT point parsing to handle different XML formats
- Add detailed logging at network receive, parsing, and event handling stages
- Log warnings when takService reference is nil (would prevent map updates)

This helps diagnose issues where users connect to TAK servers but don't
see their teammates on the map.

* Fix unit filtering to show all affiliations by default

- Changed showUnknown default from false to true (show unknown units)
- Added showNeutral toggle for neutral units (a-n-*)
- Updated filter logic to handle ALL MIL-STD-2525 affiliations:
  - Friendly group: a-f (friendly), a-k (faker), a-a (assumed friendly)
  - Hostile group: a-h (hostile), a-j (joker), a-s (suspect)
  - Neutral: a-n
  - Unknown: a-u and any other unrecognized 'a-' types
- Non-affiliation CoT types (waypoints, markers) are ALWAYS shown
- Added Neutral toggle button to Layers panel
- Philosophy: Default to showing MORE rather than potentially missing units

This ensures teammates from OpenTAKServer are displayed regardless of
what affiliation their CoT messages report.

---------

Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant