Page MenuHomePhabricator

Do not run insecurely in Blubber until coverage reports work
Open, MediumPublic

Description

Description

runs: insecurely: true isn't needed for now; this is only relevant for coverage reports, and we currently can't generate those.

Desired behavior/Acceptance criteria (returned value, expected error, performance expectations, etc.)

  • eliminate runs: insecurely: ... from Blubber variants until we fix coverage

Completion checklist

Details

Related Changes in GitLab:
TitleReferenceAuthorSource BranchDest Branch
Draft: Remove runs: insecurely: true; this is not necessary until we fix the coverage reports.repos/abstract-wiki/wikifunctions/function-evaluator!289apineapine-so-insecuremain
Customize query in GitLab

Event Timeline

DSantamaria changed the task status from Open to In Progress.Feb 6 2025, 12:10 PM
DSantamaria changed the task status from In Progress to Open.Mar 3 2025, 8:19 AM

apine closed https://gitlab.wikimedia.org/repos/abstract-wiki/wikifunctions/function-evaluator/-/merge_requests/289

Draft: Remove runs: insecurely: true; this is not necessary until we fix the coverage reports.