Confusing error message when the workspace directory of a junction is missing
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- build-system
Research direction
Reproduce the problem by moving a junction directory, reopening the workspace, and running bst source track for the junction shown in project.conf or its include file. Trace the error reported for the missing workspace directory and adjust the behavior so it no longer gives the misleading instruction to track a junction without a ref; verify both project.conf cases.
Written by the indexing model from the issue text.
Description
I had a workspace open on a junction, then moved the junction directory. Trying to track a source in the project later gave the current error
project.conf [line 12 column 2]: Subproject has no ref for junction: buildstream-plugins-community.bst
Try tracking the junction element with `bst source track buildstream-plugins-community.bst`
In this case, here is part of project.conf starting at line 12
- origin: junction
junction: buildstream-plugins-community.bst
sources:
@vixalien reported a similar error on matrix:
project.conf [line 33 column 2]: Subproject has no ref for junction: freedesktop-sdk.bst
Try tracking the junction element with `bst source track freedesktop-sdk.bst`
and in this case, it was an include file from the junction (project.conf starting line 32)
(@):
- freedesktop-sdk.bst:include/runtime.yml
It might be that it only happens if the junction is needed in project.conf
- Dominant language
- Python
- Stars
- 144
- Forks
- 45
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 6
Getting set up
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/buildstream
-
logging
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
apache/buildstream#2150 · 3 comments ·
-
question
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
apache/buildstream#2143 · 2 comments · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
apache/buildstream#2196 ·
-
Modification time of an element with an open workspace propagates into consumer element's sandboxOpenbug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
apache/buildstream#2186 · 2 comments · 2 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
apache/buildstream#2184 · 1 comment ·
All issues in apache/buildstream
Similar issues
-
customer-reported
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Azure/azure-cli#34150 · 1 comment ·
Maintainers usually reply within 1 day
-
community-request
Difficulty 1/5 Under an hour Newbie friendliness 95/100
NVIDIA-NeMo/Curator#2464 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
WeblateOrg/translation-finder#1099 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
trezor/trezor-firmware#7997 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day