Open Arcanemagus opened 8 years ago
I think next week i'll have some time for investigating. Until then i suggest using atom stable.
Confirmed that this only shows when opening a project that uses SVN as its VCS btw.
Since v1.7 atom introduces and requires a new async repository class which has to be implemented by this package. ref #2 See https://github.com/atom/atom/blob/39592599b1f577a0d395a088ecea3293d159097d/src/git-repository-async.js
Since today, I'm also having this issue with the stable Atom release. svn does not show changes in my source code any more, only in the treeview. Maybe this is related to the latest release of the statusbar package?
Ok, found out that this is related to Atom automatically updating to release 1.7 which has been released today. What can I do to fix this?
Same here... svn worked well until atom 1.6.2. Now broken in 1.7.0
Is there any way to revert Atom to 1.6.2 until this is fixed? Not having code diff highlights is a huge drawback.
the 1.6.2 package is here https://github.com/atom/atom/releases/tag/v1.6.2 . However I do not know how to disable the autoupdate feature...
Arf found it... in the core settings :-)
Yup, I also found out how to downgrade and prevent auto-updates now. But it would be great if the svn package could be adapted to 1.7 soon. Still, I don't understand why the Atom team introduces such breaking changes in a minor release. Obviously, they're not using semver.
This is the commit that broke the svn package: https://github.com/atom/status-bar/pull/114/commits/aa4c4fe3e9444d14973bbb69e41ca593895e507a. It is part of the move to async git: https://github.com/atom/atom/pull/9213.
The status bar is looking for an async
field on the SvnRepository
object. For the GitRepository
class, that object is an instance of GitRepositoryAsync
To keep up with the new "API," it seems like each of the functions in the SvnRepository
class will have to be replicated on a new class, SvnRepositoryAsync
. Each of the getter functions (or maybe all functions) in SvnRepositoryAsync
will have to return a promise that resolves to the requested value.
Should be fixed in v0.0.10. Many Thanks to @awestroke
Great to hear! Thanks a lot for fixing this. Now I can finally update my Atom :-)
Same happening here, running version 1.8 Was it supposed to be fixed already?
Linux mint 18, based on Ubuntu 16.04
Happening to me also - running Ubuntu 14.04 and Atom 1.8.
Yeah. Me too. It started after I did a Ctrl-Alt+R reload.
@andischerer I would suggest you to open it again then...
Anyone still experiencing this problem?
[Enter steps to reproduce below:]
Atom Version: 1.7.0-beta0 System: Microsoft Windows 10 Enterprise Thrown From: svn package, v0.0.9
Stack Trace
Failed to activate the svn package
Commands
Config
Installed Packages