Question: Could not load source 'Fastfile': not found, while debugging a Fastlane lane from VSCODE
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- ruby, vscode
- Domain
- developer-experience, devtools
Research direction
Reproduce the issue in the linked debug-fastlane example using the terminal command and the rdbg --open=vscode command, after running bundle install. Compare how each mode resolves the Fastfile source, then verify that the VS Code session can open and debug custom_lane as the terminal session does.
Written by the indexing model from the issue text.
Description
Your environment
ruby -v:ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [arm64-darwin23]rdbg -v:rdbg 1.9.1
Describe the bug
I'm not an expert here (so I'm probably missing something) but I was recently trying to debug a custom Fastlane lane with rdbg using vscode with the following terminal command:
rdbg --open=vscode -c -- bundle exec fastlane custom_lane
But it seems that the editor cannot load the source file: the Fastfile (see attached screenshot). I would guess that some context information are not correctly passed to the editor (am I missing some parameters?).
If I debug from the terminal, using the following command:
rdbg -c -- bundle exec fastlane custom_lane
Everything seems to work correctly (see attached screenshot).
I prepared an example repo to easily reproduce the issue.
Thanks in advance for your support, and sorry if it's a stupid question 😅
To Reproduce
- Checkout the example repo
- Install the required gems with
bundle install - Debug from terminal with:
rdbg -c -- bundle exec fastlane custom_lane - Debug from
vscodewith:rdbg --open=vscode -c -- bundle exec fastlane custom_lane
Expected behavior
I would expect to debug the custom_lane similarly from both terminal and vscode.
- Dominant language
- Ruby
- Stars
- 1.3k
- Forks
- 146
- PR merge metrics
- No merged PRs in 30d
Contributor 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 ruby/debug
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Support exceptionOptions in setExceptionBreakpoints to catch arbitrary exception classes via DAP Open
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
notch8/utk_knapsack#148 ·
-
feature
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
betagouv/acces-cible#722 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
foobara/empty-ruby-project-generator#10 · 2 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100