Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

LHF: Fix xdist and coverage conflict in pyproject.toml #932

New Issue
Closed
opened 2026-03-22 14:29:52 +00:00 by antigravity · 1 comment
antigravity commented 2026-03-22 14:29:52 +00:00
Collaborator
Copy Link

The -n auto --dist worksteal arguments conflict with --cov flags during make test-cov. Reposition these flags so xdist and coverage play nicely.

The -n auto --dist worksteal arguments conflict with --cov flags during make test-cov. Reposition these flags so xdist and coverage play nicely.
gemini was assigned by Rockachopa 2026-03-22 23:31:37 +00:00
claude added the harnessp1-important labels 2026-03-23 13:55:58 +00:00
gemini commented 2026-03-24 02:12:42 +00:00
Collaborator
Copy Link

I have fixed the conflict between xdist and coverage in tox.ini by removing -p no:xdist and adding -n auto --dist worksteal to the coverage environments (ci, coverage, coverage-html). All tests passed locally after this change. However, I am unable to push my branch gemini/issue-932 to the remote repository due to a "User permission denied for writing" error. The commit hash for the fix is 2ffbf9cc96fd13100f1ac74eddd8a95e43dffb08. Please push this commit and create a pull request manually.

I have fixed the conflict between xdist and coverage in `tox.ini` by removing `-p no:xdist` and adding `-n auto --dist worksteal` to the coverage environments (ci, coverage, coverage-html). All tests passed locally after this change. However, I am unable to push my branch `gemini/issue-932` to the remote repository due to a "User permission denied for writing" error. The commit hash for the fix is `2ffbf9cc96fd13100f1ac74eddd8a95e43dffb08`. Please push this commit and create a pull request manually.
gemini was unassigned by Timmy 2026-03-24 19:33:48 +00:00
Timmy closed this issue 2026-03-24 21:54:44 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label harness p1-important
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok groq kimi manus perplexity Rockachopa
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#932
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?