desktop: Git LFS error reported after upgrading to latest Heroku CLI

Description

I get this error when opening up Github Desktop, bad netrc file /Users/username/.netrc: line 7: keyword expected; got method. I believe it is not liking the entry in my .netrc file that is put there by the heroku CLI.

image

Here is what my .netrc file looks like with fake data:

machine api.heroku.com
  login fake@email.party
  password fake-password
  method sso
  org fakeorg

It looks like the Github Desktop is not liking this method line.

Version

  • GitHub Desktop: 1.1.1
  • Operating system: MacOS 10.13.4

Steps to Reproduce

  1. Open desktop via the command line with github command
  2. Error is displayed

Expected Behavior

No error during startup

Actual Behavior

Error displayed

Additional Information

Logs

2018-05-21T15:48:17.702Z - info: [main] Processing protocol url
2018-05-21T15:48:18.099Z - info: [ui] [AppStore] loading 12 repositories from store
2018-05-21T15:48:18.100Z - info: [ui] [AppStore] found account: codebender (Matthew Bender)
2018-05-21T15:48:18.686Z - info: [ui] launching: 1.1.1 (Mac OS 10.13.4)
2018-05-21T15:48:18.686Z - info: [ui] execPath: '/Applications/GitHub Desktop.app/Contents/Frameworks/GitHub Desktop Helper.app/Contents/MacOS/GitHub Desktop Helper'
2018-05-21T15:48:18.727Z - error: [ui] `git lfs install --skip-repo` exited with an unexpected code: 2.
bad netrc file /Users/username/.netrc: line 7: keyword expected; got method

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 2
  • Comments: 15 (5 by maintainers)

Most upvoted comments

@shiftkey I am looking at cutting a release containing that (+ a few other patches) for v2.4.2 early next week. Will that work OK for you?

Git LFS v2.4.2 was released containing https://github.com/git-lfs/git-lfs/pull/3027, which should fix this issue!

@codebender the fix is going out to beta now, with it slated to be available to everyone Monday

@codebender thanks for the report! This is being raised by Git LFS due to the unexpected syntax in your .netrc file - I dealt with a similar issue to this over in https://github.com/desktop/desktop/issues/2858.

I’m not sure whether netrc files support any sort of flexibility with extra tags, and I can’t find any documentation about it from Heroku’s end indicating this is intended behaviour (best link i could find) so I’d recommend commenting out those lines by prefixing a # and seeing if anything Heroku-related is affected.