kworkflow / kworkflow/patch-hub

`Path doesn't exist` when trying to open a patchset

Open
#69 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug waiting-stable
Dominant language
Rust
Stars
36
Forks
17
PR merge metrics
No merged PRs in 30d

Description

Description:

For when trying to see details of a given patchset, the program crashes saying:

Error: 
   0: /home/ojarrisonn_/.cache/patch_hub/patchsets/accel-config.20220607025834.1740551-1-li4.zhang@intel.com.mbx: Path doesn't exist

Location:
   src/app.rs:151
How to reproduce:
  1. Open accel-config list
  2. Open 025. V01 | #14 | [Accel-config] Add Zcompress32, Zdecompress32, Compress and Decompres | Li Zhang
  3. It crashes
Expected behavior:

The details for the given patchset should be shown

Screenshots
[INFO] [2024-10-25 18:53:57] patch-hub started
[ERROR] [2024-10-25 18:56:02] Error executing "lore_session::split_patchset(&patchset_path)": /home/ojarrisonn_/.cache/patch_hub/patchsets/accel-config.20220607025834.1740551-1-li4.zhang@intel.com.mbx: Path doesn't exist
Setup:
  • Project branch: unstable
  • Project commit hash: 9f14c2da9297d3806a0b2f1c4c58ff87df8bafa1
  • rustc version: rustc 1.82.0 (f6e511eec 2024-10-15)
  • cargo version: cargo 1.82.0 (8f40fc59f 2024-08-21)

Contributor guide

Open the contributing guide

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.

Research direction

Start at src/app.rs:151 and inspect the lore_session::split_patchset call involved when opening the listed accel-config patchset. Reproduce the failure using the provided steps and patchset path, then verify that opening its details shows the patchset instead of crashing when the path is unavailable.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.