-
Notifications
You must be signed in to change notification settings - Fork 392
Can't stage files after Stage All
with project on D: drive
#1801
Comments
Thanks for the report! I was unable to reproduce on macOS 10.12.6 with Atom 1.32.2. Do you see this behavior with any project or just the one you're working on? And can you reproduce with any file for the "right click a file -> Stage" step? Also for this step, are there any special characters in the filename or path of the file that you right-click to stage?
I think you'll get that error if you run |
Yes, this behavior happens on every project.
Yes, this behavior also happens when I right click a file and click stage.
That is interesting, there are no special characters in the filename or path but I created a folder on the root of my C: drive and stage/unstage worked. It seems like when a folder is on D: this behavior happens, but when I move them to C: they seem to work. What can be the cause of this? |
Ohh sorry, I just realized that I misinterpreted your repro steps. I thought this was a series of steps:
But I think you meant that none of those functions work for you? I played around with things more so I'll leave some notes here, tested on Windows 10 with Atom 1.32.2.
At this point I found that if I open the Git panel I see the "Unsupported directory" + "Atom does not support managing Git repositories in your home or root directories" message, so you can't initialize a repo from the Git panel. But then if I do a
After reloading Atom, the Git panel shows up normally. If I make and save a change, it shows up in But where it seems to break is if I click The "Atom does not support managing Git repositories in your home or root directories" doesn't seem right since I've created a subdirectory under |
Stage All
with project on D: drive
Hi, I also have the same issue as OP I've included a video of the same thing happening (also on D:\ which also happens to be a thumb-drive). Please let me know what other information I need to supply. video link : https://streamable.com/c8edh EDIT: To add to above, moving the project to C: makes it all work fine. Repeatable every time |
That behavior is a separate issue, see and atom/tree-view#856 (comment) in particular for more details. |
Looks like this is still open. Was there ever a solution @adriangzz ? I get the same error. |
I ended up moving my working folder to the C: drive. |
Edit by @rsese to add my notes from #1801 (comment)
I played around with things more so I'll leave some notes here, tested on Windows 10 with Atom 1.32.2.
mkdir test-gh; cd test-gh
echo "Hello World" >> README.md
atom .
At this point I found that if I open the Git panel I see the "Unsupported directory" + "Atom does not support managing Git repositories in your home or root directories" message, so you can't initialize a repo from the Git panel.
But then if I do a
git init
and an initial commit in Git Bash:git init
git add README.md
git commit -m "Initial commit"
After reloading Atom, the Git panel shows up normally. If I make and save a change, it shows up in
Unstaged Changes
and at this point, if I right-click andStage
the file, that works ok and I can commit that change.But where it seems to break is if I click
Stage All
, I see a "Uncaught (in promise) Error: EINVAL: invalid argument, read` message in devtools console. At this point I can no longer right-click to stage a change unless I reload/restart Atom.The "Atom does not support managing Git repositories in your home or root directories" doesn't seem right since I've created a subdirectory under
D:
? Then the other issue seems to be the error fromStage All
which then prevents things from working while right-clicking to stage a single file works.Prerequisites
Description
When I click on Stage All, Unstage All, right click a file and click stage, nothing happens.
In console I get this error:
VM22 <embedded>:14 Uncaught (in promise) Error: EINVAL: invalid argument,
Steps to Reproduce
Expected behavior: [What you expect to happen]
For my files to move to Staged Changes or Unstaged changes
Actual behavior: [What actually happens]
Files don't move.
Reproduces how often: [What percentage of the time does it reproduce?]
100%
Versions
You can get this information from copy and pasting the output of
atom --version
andapm --version
from the command line. Also, please include the OS and what version of the OS you're running.Atom : 1.32.2
Electron: 2.0.9
Chrome : 61.0.3163.100
Node : 8.9.3
Windows: 10
Additional Information
When I do apm --version I get this:
internal/child_process.js:323
throw errnoException(err, 'spawn');
^
Error: spawn UNKNOWN
at _errnoException (util.js:1024:11)
at ChildProcess.spawn (internal/child_process.js:323:11)
at exports.spawn (child_process.js:502:9)
at EventEmitter.<anonymous> (C:\Users\Adrian\AppData\Local\atom\app-1.32.2\resources\app\apm\lib\apm-cli.js:169:17)
at _combinedTickCallback (internal/process/next_tick.js:131:7)
at process._tickCallback (internal/process/next_tick.js:180:9)
The text was updated successfully, but these errors were encountered: