Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

lsf.py using a variable project not available in WorkspaceConfig

Open
#239 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
tooling

Research direction

Start in lsf.py at line 56 and inspect how WorkspaceConfig is passed to Launcher.set_pyvenv. Then trace the job_rusage configuration and its handling of resource options. Done means the unavailable project reference is resolved and LSF resource options such as xcelium are no longer hardcoded.

Written by the indexing model from the issue text.

Description

All the issue in this ticket are with LSF.

  1. line 56 of lsf.py Launcher.set_pyvenv(cfg.project)
    There is no variable project in type WorkspaceConfig
  2. job_rusage = "'rusage[xcelium=1,xcelium_dynamic=1:duration=1]'"
    Need a way to provide the options in ruage. Hardcoded option like xcelium cause issues.
Dominant language
Python
Stars
14
Forks
21
Avg merge
3d 11m
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lowRISC/dvsim

All issues in lowRISC/dvsim

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.