The generated-files builder timeout cannot be changed

Open Beginner friendly
  • Is something wrong?
#1,306 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
tooling

Research direction

Start with scripts/check_generated_files_current.py, especially BUILD_TIMEOUT and the existing FAIRCODE_GH_TIMEOUT handling. Read the module docstring and relevant tests, then check how the builder applies its timeout. Done means a test confirms FAIRCODE_BUILD_TIMEOUT sets the limit and an invalid value falls back to 600 seconds.

Written by the indexing model from the issue text.

Description

enhancement good first issue tooling

Where: scripts/check_generated_files_current.py (BUILD_TIMEOUT).

Current gap: The 600 s limit for each regeneration step is a constant, so a slow CI runner or a very large explainer set needs a code change (the gh timeout got FAIRCODE_GH_TIMEOUT for this reason).

Suggested approach: Read an optional FAIRCODE_BUILD_TIMEOUT (seconds), ignore values that are not positive numbers and mention it in the module docstring.

Done when: a test sets the variable and sees the limit used, and an invalid value falls back to 600.

Dominant language
HTML
Stars
47
Forks
45
Avg merge
2h 47m
Merged PRs (30d)
92

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 yakew7/Fair-Code

All issues in yakew7/Fair-Code

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.