microsoft / microsoft/qlib

unexpected mlruns/filelock path

Open
#2,129 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
48.7k
Forks
7.7k
PR merge metrics
No merged PRs in 30d

Description

🐛 Bug Description

  • project root: /home/user/develop/test/test_qlib
  • mlruns root: /home/user/develop/test/test_qlib/mlrun
  • mlruns/filelock: /home/user/develop/test/test_qlib/home/user/develop/test/test_qlib/mlruns/filelock

mlruns/filelock path is not expected, it should be /home/user/develop/test/test_qlib/mlruns/filelock

To Reproduce

Steps to reproduce the behavior:

  1. Run with R
  2. mlruns/filelock path is /home/user/develop/test/test_qlib/home/user/develop/test/test_qlib/mlruns/filelock

Expected Behavior

mlruns/filelock path is /home/user/develop/test/test_qlib/mlruns/filelock

Environment

  • linux
  • python 3.12.9
  • pyqlib 0.9.8.dev27

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.

Research direction

Start by reproducing the mlruns/filelock path issue on Linux with Python 3.12.9 and pyqlib 0.9.8.dev27, following the reported project and mlruns roots. Trace where the duplicated path is constructed; done means the resulting path is exactly /home/user/develop/test/test_qlib/mlruns/filelock.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
machine-learning
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.