Marcelo

Results 22 comments of Marcelo

Sure, here you go: ``` "Running: rdbg --command --open --stop-at-load -- bundle exec rspec /Users/marcper/my_project/my_spec.rb /Users/marcper/my_project/my_spec.rb:21" [Start session] {"d":{},"f":"87107d23-84d9-4499-8869-6cddada117c0","g":"rdbg","h":"RSpec current line with rdbg","i":{"uri":{"$mid":1,"fsPath":"/Users/marcper/my_project","external":"file:///Users/marcper/my_project","path":"/Users/marcper/my_project","scheme":"file"},"name":"my_project","index":0},"j":{"type":"rdbg","name":"RSpec current line with rdbg","useBundler":false,"command":"bundle exec rspec","request":"launch","script":"/Users/marcper/my_project/my_spec.rb","args":["/Users/marcper/my_project/my_spec.rb:21"],"__configurationTarget":6,"rdbgExtensions":["traceInspector"],"rdbgInitialScripts":[]}} ```...

> I can confirm this issue. Using just `rspec` works but `bundle exec rspec` does not Good point, I hadn't realized the issue is with RSpec+bundle generally, I thought it...

> Have you tried `"rdbgPath": "bundle exec rdbg",` in your config file? > > This is my current setup which works for me. That is odd, this fails for me...

> The config that works for me is then > > ``` > { > "type": "rdbg", > "name": "RSpec current line with rdbg", > "useBundler": true, > "request": "launch",...

> ``` > project > - `build.zig.zon` > - `raylib-zig` > - `raylib` > ``` @AtishaRibeiro I noticed in your message that you seem to be importing the submodule with...

I resolved the `error: expected type 'Target.Query', found 'Build.ResolvedTarget'` by updating `raylib-zig/build.zig` as follows: ```diff diff --git a/build.zig b/build.zig index 2170cf8..7eb96cc 100644 --- a/build.zig +++ b/build.zig @@ -89,11 +89,11 @@...

Great, I'll open a PR with proposed changes in the next days.

> Could you rebase on main? Our CI on master broken... and I've fixed it now. Thank you, I've rebase it now.

> Thanks. But sorry... The master CI was broken... I've fixed it. Could you rebase on master again? No problem, I rebased it now.

I'm assuming the test failures are related to https://bugs.ruby-lang.org/issues/20526, right?