./va/va_vpp.h file still has execute bit set
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 65/100
Research direction
Inspect the mode of va/va_vpp.h and the Travis check described in the issue. Correct the file's executable bit, then run the provided find command locally to confirm that no C or header source file is executable.
Written by the indexing model from the issue text.
Description
There is travis check added by #419 but currently on master there is ./va/va_vpp.h that has execute bit set
if I run script manually in my work tree error is raised:
$ if [[ -n "$(find -name '*.[ch]' -executable)" ]]; then echo "Error, a source code file(s) has the execute bit set:" >&2; find -name '*.[ch]' -executable; exit 1; fi
Error, a source code file(s) has the execute bit set:
./va/va_vpp.h
but on travis error is not triggered, dont know why maybe umask or exit handle, not sure
commit that introduce execute bit on ./va/va_vpp.h is https://github.com/intel/libva/commit/30c751f7b74c43021f33361c1baf2aa92acd0317 100644 → 100755
I will send PR with fix for mode on file ./va/va_vpp.h but don't know how to debug travis locally without spamming your build with adding ls -l va/va_vpp.h or stat va/va_vpp.h lines
- Dominant language
- C
- Stars
- 790
- Forks
- 316
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No 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 intel/libva
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
registry_packageOpen
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
OjaidiOpen
Difficulty 5/5 Over a week Newbie friendliness 1/100
Similar issues
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 92/100
github/copilot-sdk#2804 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Zenmap
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 5 days
-
hfile_s3: reading to EOF fails with EINVAL when object size is a multiple of the read part sizeOpen
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 3 days