Please rerun `pre-commit run -a`
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- c
- Domain
- build-system
Research direction
The whitespace hook is configured in .pre-commit-config.yaml at the repository root, so start there to see which hooks are enabled. Install pre-commit, run pre-commit run -a locally, and let it rewrite the affected C sources and other files. Done means the command exits cleanly on a fresh checkout and the resulting diff contains only whitespace or formatting changes. Check with maintainers first, since the change touches many files and could conflict with in-flight work.
Written by the indexing model from the issue text.
Description
Description / Steps to reproduce the issue
This repo has .pre-commit-config.yaml that enabled whitespace fixing (good idea). But the sources are not formatted with. pre-commit fails right now, and it is difficult to use it locally.
Please rerun pre-commit run -a so all the existing error are fixed.
On which OS does this issue occur?
[OS: Linux]
What is the version of your OS?
Arch Linux
NuttX Version
master
Issue Architecture
[Arch: arm], [Arch: all]
Issue Area
[Area: Build System]
Host information
No response
Verification
- I have verified before submitting the report.
- Dominant language
- C
- Stars
- 4.1k
- Forks
- 1.8k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 833
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 apache/nuttx
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/nuttx#19435 · 9 comments ·
Maintainers usually reply within 1 day
-
Arch: all OS: Linux Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
apache/nuttx#16249 · 7 comments ·
Maintainers usually reply within 1 day
-
Arch: all Area: Networking OS: Linux
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Type: Enhancement
Difficulty 4/5 3-5 days Newbie friendliness 22/100
apache/nuttx#21581 · 1 comment ·
Maintainers usually reply within 1 day
-
Arch: simulator Arch: xtensa Area: Kernel OS: Mac Type: Bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
apache/nuttx#21499 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
SPIDevice selects an active-high device as soon as it is createdPossibly taken @mikeysklar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
adafruit/circuitpython#11869 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
gnif/LookingGlass#1352 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
kovidgoyal/kitty#10862 ·
Maintainers usually reply within 1 day