question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ENOENT error when publishing new repository

See original GitHub issue

Description

When attempting to publish a new repository, I receive this error:

ENOENT: no such file or directory, mkdtemp 'C:\Users\[name]\AppData\Local\Temp;C:\MinGW\bin\GitHubDesktop-lfs-progress-XXXXXX'

The problem with this is that both of those directories exist and GitHub is running in administrator mode so it should be able to access those. I uninstalled GitHub and deleted all correlated files and registry keys to no avail.

Version

GitHub Desktop version: 1.0.12

OS version: Windows 6.3.9600

Steps to Reproduce

  1. I wrote the code and used GitHub Desktop to create a new repository in the folder containing all of my code files.

  2. I clicked the ‘Publish’ button and received this error.

  3. I tried “soft” reinstalling GitHub Desktop by using Programs and Features to remove it.

  4. Once this didn’t work, I reinstalled it and used Revo Uninstaller to locate all related files and registry entries, deleting every one.

  5. I tried again and it still didn’t work, so I deleted the content of C:/Users/[me]/AppData/Local/Temp and double-checked the permissions to make sure it could write to it.

  6. I rebooted my PC (this really should’ve been an earlier step). Still nothing.

Expected behavior: Publishing my repository without errors.

Actual behavior: Did not publish, received ENOENT instead.

Reproduces how often: 100% of the time

Logs

It appears that the log is mostly full of information about being unable to fetch my account picture (that’s happening as well), but that’s a much less important issue to me. I don’t know which pieces exactly are relevant. It can be found here for the sake of making this issue concise.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:6 (2 by maintainers)

github_iconTop GitHub Comments

4reactions
shiftkeycommented, Jan 9, 2018

This is a duplicate of #3072 - your TEMP or TMP environment variable contains multiple paths - you should update the environment variable so it only contains one path.

1reaction
shiftkeycommented, Apr 12, 2018

@piotrrybinski88 ensure you don’t have a trailing ; on the path for both environment variables, as that seems to have been the issue here.

Read more comments on GitHub >

github_iconTop Results From Across the Web

npm install errors with Error: ENOENT, chmod - Stack Overflow
I noticed that the error had to do with the file I am linking to the path, specifically when npm tried to do...
Read more >
File Copy Job in Build Process fails with "ENOENT
It's failing on the "Copy Files" task where I'm telling it to copy everything in "dist**". So it should not be doing anything...
Read more >
Error: ENOENT: no such file or directory, open '/opt/build/repo ...
Having trouble to pass my build. Not sure what it could be. I have tried a few things that I found on the...
Read more >
ENOENT Error while publishing - Mobirise Forums
Project-new -> direct Publish to local folder on Drive D! Sometimes I'm still really disappointed about Mobi. image.png 75.5K ...
Read more >
Spa - npm errors when publishing a demo to IIS
npm ERR! enoent This is related to npm not being able to find a file. npm ERR! enoent. npm ERR! A complete log...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found