the war against macOS firewall popups when running tests
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 248
- Forks
- 72
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 15
Description
Even though MPI process are forking and talking amongst themselves, they still trigger firewall popups during development.
Here is an example of what these look like:
These windows appear then disappear, and while doing so disrupt using the computer while testing.
I found that NodeJS folks have a script that adds firewall rules to smooth things over:
https://github.com/nodejs/node/blob/main/tools/macos-firewall.sh
We could autogen a similar script with cmake, or explore creating a script with generic rules that work for our test exes (t_zzz)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the NodeJS macOS firewall script linked in the issue and how this repository builds its test executables, including the t_zzz naming pattern. Determine whether a CMake-generated or generic script can cover the test executables without disrupting macOS development; done means the popups no longer appear while running tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp, macos
- Domain
- build-system, operating-systems, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100