cncf_slack_channel deprecation warning cites an internal darnit spec version
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 88/100
Research direction
Read the warning at packages/darnit/src/darnit/context/dot_project.py lines 671–680 and the assertion in tests/darnit/context/test_dot_project_deprecations.py. Remove the misleading internal version reference while keeping the migration guidance ASCII-only. Run uv run pytest tests/darnit/context -q and uv run ruff check .; done when the warning no longer cites the internal version and the deprecation test passes.
Written by the indexing model from the issue text.
Description
Summary
The deprecation warning for the .project/ field cncf_slack_channel says the alias "is accepted by darnit spec version 1.2.0". That number was one of darnit's internal reconcile counters, not an upstream CNCF dot-project version, and #502 pins darnit to the upstream schema version (1.0.0). The message should not cite an internal counter users cannot look up.
Where
Getting started
- Reword the message to drop the version number, for example: "This alias is still accepted by darnit and will be removed in a future release. Migrate to the
slack_channelslist form defined in the CNCF spec: ". - Update the test that asserts the message text:
tests/darnit/context/test_dot_project_deprecations.py(it currently checks for "spec version 1.2.0"). - Run
uv run pytest tests/darnit/context -qanduv run ruff check .. - Keep the text ASCII-only and sign off your commit (
git commit -s).
Acceptance: the warning no longer mentions an internal version number, and the deprecation test passes.
- Dominant language
- Python
- Stars
- 22
- Forks
- 27
- Avg merge
- 2d 28m
- Merged PRs (30d)
- 40
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 darnitdevorg/darnit
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
darnitdevorg/darnit#589 ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
darnitdevorg/darnit#587 ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
darnitdevorg/darnit#585 ·
Maintainers usually reply within 1 day
-
quality
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
darnitdevorg/darnit#523 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
darnitdevorg/darnit#516 ·
Maintainers usually reply within 1 day
All issues in darnitdevorg/darnit
Similar issues
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
openwisp/openwisp-utils#777 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
google-research/weatherbenchX#310 ·
Maintainers usually reply within 3 days
-
`unload()` returns the trained `modules_to_save` copy instead of the original modulePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
huggingface/peft#3955 ·
Maintainers usually reply within 1 day
-
author-page correction
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
acl-org/acl-anthology#10313 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
AOSSIE-Org/Gitcord-GithubDiscordBot#147 · 1 comment ·
Maintainers usually reply within 1 day