Compute Deploy.full_name with IPMeta.variant_name
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- python
- Domain
- build-system
Research direction
Start with deploy.py and the linked discussion about Deploy.full_name and IPMeta.variant_name. Trace how full_name is currently assembled and identify the repeated code mentioned in the issue; done means Deploy.full_name uses IPMeta.variant_name and the repeated deployment logic is removed.
Written by the indexing model from the issue text.
Description
This was an idea from @AlexJones0 here and should allow us to get rid of quite a bit of repeated code in deploy.py.
- Dominant language
- Python
- Stars
- 14
- Forks
- 21
- Avg merge
- 3d 11m
- Merged PRs (30d)
- 5
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 lowRISC/dvsim
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Better log visibility on the license type usage profilePossibly taken @AlexJones0 claimed this 5 days ago. Open
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 75/100