Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

check_dir_authority error: C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/debug-1.6.2/lib/debug/config.rb:415:in `check_dir_authority'

Offen
#762 2 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
25/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Veraltet
Tech-Stack
ruby, vscode
Bereich
devtools

Rechercherichtung

Start with the reported Windows failure in debug-1.6.2 at lib/debug/config.rb:415 and compare it with the rdbg launch configuration in launch.json. Reproduce the VS Code run-and-debug invocation and inspect the reported temporary directory mode. Done means the supplied rdbg configuration starts the Ruby program without the check_dir_authority error.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

I'm running the launch.json in vs 1.71.2 from within vs in the run and debug area. rspec - 3.11 ffi - 1.15 debug 1.6 rdbg 1.6.2

  • ruby -v:
  • rdbg -v:

Describe the bug
Error output:
C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/debug-1.6.2/lib/debug/config.rb:415:in check_dir_authority': C:/Users/tculbert/AppData/Local/Temp/ruby-debug-sock-0's mode is 40755 (should be 040700) (RuntimeError) from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/debug-1.6.2/lib/debug/config.rb:432:in unix_domain_socket_tmpdir'
from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/debug-1.6.2/lib/debug/config.rb:452:in unix_domain_socket_dir' from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/debug-1.6.2/lib/debug/config.rb:466:in create_unix_domain_socket_name'
from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/debug-1.6.2/lib/debug/client.rb:20:in util' from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/debug-1.6.2/lib/debug/config.rb:368:in block (2 levels) in parse_argv'

from C:/Ruby31-x64/lib/ruby/3.1.0/optparse.rb:1576:in `block in parse_in_order'
from C:/Ruby31-x64/lib/ruby/3.1.0/optparse.rb:1559:in `catch'
from C:/Ruby31-x64/lib/ruby/3.1.0/optparse.rb:1559:in `parse_in_order'
from C:/Ruby31-x64/lib/ruby/3.1.0/optparse.rb:1553:in `order!'
from C:/Ruby31-x64/lib/ruby/3.1.0/optparse.rb:1659:in `permute!'
from C:/Ruby31-x64/lib/ruby/3.1.0/optparse.rb:1684:in `parse!'
from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/debug-1.6.2/lib/debug/config.rb:382:in `parse_argv'
from C:/Ruby31-x64/lib/ruby/gems/3.1.0/gems/debug-1.6.2/exe/rdbg:4:in `<top (required)>'
from C:/Ruby31-x64/bin/rdbg:32:in `load'
from C:/Ruby31-x64/bin/rdbg:32:in `<main>'

Error: exit code is 1
Make sure to install rdbg command (gem install debug).
If you are using bundler, write gem 'debug' in your Gemfile.
[Start session]
{"_debugServiceProxy":{},"_id":"549c291c-e660-4a33-b942-da6e53d04476","_type":"rdbg","_name":"Debug current file with rdbg","_workspaceFolder":{"uri":{"$mid":1,"fsPath":"c:\Users\tculbert\Documents\Selenium Class\Ex_Files_Learning_Selenium\Exercise Files","_sep":1,"external":"file:///c%3A/Users/tculbert/Documents/Selenium%20Class/Ex_Files_Learning_Selenium/Exercise%20Files","path":"/C:/Users/tculbert/Documents/Selenium Class/Ex_Files_Learning_Selenium/Exercise Files","scheme":"file"},"name":"Exercise Files","index":0},"_configuration":{"type":"rdbg","name":"Debug current file with rdbg","request":"launch","command":"rspec","script":"blog-test.rb","args":[],"askParameters":true,"__configurationTarget":6}}
my launch file:
{
// Use IntelliSense to learn about possible attributes.
// Hover to view descriptions of existing attributes.
// For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
"version": "0.2.0",
"configurations": [
{
"name": "RSpec - all",
"type": "Ruby",
"request": "launch",
"program": "${workspaceRoot}/bin/rspec",
"args": [
"-I",
"${workspaceRoot}"
]
},

    {
        "type": "rdbg",
        "name": "Debug current file with rdbg",
        "request": "launch",
        "command": "rspec",
        "script": "blog-test.rb",
        "args": [],
        "askParameters": true
    },
    {
        "type": "rdbg",
        "name": "Attach with rdbg",
        "request": "attach",
        "debugPort": "12345"
    
    }
]

}
To Reproduce

Expected behavior
I'm expecting not to get the error and have my code run

Additional context
I've looked at the other 2 related bugs and have added the debugport, but that hasn't fixed the issue.

Vorherrschende Sprache
Ruby
Sterne
1.3k
Forks
146
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus ruby/debug

Alle Issues in ruby/debug

Ähnliche Issues

Weitere Issues zu Ruby

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.