find_composes prints traceback if compose directory cannot be read

Open
#74 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

Start at find_latest.py in find_composes(), where productmd.compose.Compose is called, and reproduce the case with an unreadable compose directory. Verify that this condition no longer produces the shown traceback while normal compose discovery continues to work; no test file is named in the issue.

Written by the indexing model from the issue text.

Description

    ci_list = find_composes()", 
  File \"/usr/lib/python2.6/site-packages/distill3_utils/find_latest.py\", line 58, in find_composes", 
    compose = productmd.compose.Compose(compose_path)", 
  File \"/usr/lib/python2.6/site-packages/productmd/compose.py\", line 70, in __init__", 
    for i in os.listdir(compose_path):", 
        "OSError: [Errno 13] Permission denied: '.../released/F-20/20-Beta-RC1'"

where .../released/F-20/20-Beta-RC1 is unreadable by the user.

Dominant language
Python
Stars
11
Forks
34
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 release-engineering/productmd

All issues in release-engineering/productmd

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.