Reenable environment override tests on macos
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
Research direction
Locate the disabled macOS tests matching test_x_when_env_is_set_overrides... and inspect how set_env(...) and work() are implemented. Reproduce the failure on macOS, then re-enable the environment-override tests and verify that the relevant tests pass there.
Written by the indexing model from the issue text.
Description
They were disabled because unlike Linux on Macos tests of the following nature were failing:
test_x_when_env_is_set_overrides...
set_env(...)
work() // set_env was not getting picked up
- Dominant language
- Rust
- Stars
- 29
- Forks
- 7
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 12
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.
More from Screenly/cli
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
bug rules
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
app bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
IronCoreLabs/ironcore-alloy#346 ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100