Mafia support for SVN

[fronobulax]

This is more of a request for information and discussion than a request for features.

I had autoupdate on and it got to WHAM and errored with connection refused. This was repeatable. I then updated WHAM only and it checked and properly updated. Is there some kind of connection throttling imposed by SourceForge that might might cause the update attempt to fail? If so, should we consider introducing a delay? Is this an alternative explanation for some of the SVN error states (which effect the local repository) for which DropBox is the current explanation?

Would it be useful to have the repository as part of the script metadata? I'm thinking of the issues with Guide which is hosted on github. Since the best solution is to delete and reload Guide, this would help me identify candidate scripts for that action.

Would anyone else like a right click option in the Script Manager to ReInstall?

Is Script Manager (it's a thing now) retaining any error status messages? Sh/Could it? How about a visual cue for installed scripts if there was an error at the last update?

Finally, what did we decide is the method by which an author updates the Description and Long Description of a script that is managed by Script Manager? How does a new script get added? I feel the answer to both is "PM Bale" but I don't wish to annoy him unnecessarily or more than I already do.

Thanks.

 

[Fluxxdog]

Would it be useful to have the repository as part of the script metadata?

More information couldn't hurt.

Would anyone else like a right click option in the Script Manager to ReInstall?

That would be useful. If it's easier to do, it'll be easier to have people troubleshoot.

Is Script Manager (it's a thing now) retaining any error status messages? Sh/Could it? How about a visual cue for installed scripts if there was an error at the last update?

Again, more information couldn't hurt.

Finally, what did we decide is the method by which an author updates the Description and Long Description of a script that is managed by Script Manager? How does a new script get added? I feel the answer to both is "PM Bale" but I don't wish to annoy him unnecessarily or more than I already do.

What, you mean the author can't update it dynamically? I guess I missed that part of the convo. I would have thought there'd be a desc.txt file for the manager to parse when downloading to identify it.

 

[fronobulax]

What, you mean the author can't update it dynamically? I guess I missed that part of the convo. I would have thought there'd be a desc.txt file for the manager to parse when downloading to identify it.

What I remember is that authors asked Bale and between them they edited the table here. Magic happens and that table got parsed into the datafile that gets updated and drives Script Manager. But my scripts were in that post before Script Manager so I really don't know what the procedure is and I do recall valid concerns about letting just anyone update the file.

 

[lostcalpolydude]

Would it be useful to have the repository as part of the script metadata?

> ash svn_info( "Guide" ).url

Returned: https://github.com/Ezandora/Guide/branches/Release

 

[fronobulax]

Thanks. I'll rephrase my question to be whether Script Manager should use that info in its display. That said, it is of less importance than when I asked the question since I now know that I can write a script that, for example, forces a reload of everything from github so long as I don't care about server hits.

 

[roippi]

I'd rather people figure out how to reproduce the bug with Guide that causes mafia to (silently?) fail updates.

A reinstall context-menu item is fine.

 

[Bale]

I like the idea to add a reinstall context-menu item. The feature I really think should really be added is to add the checkbox for the "Update installed SVN projects on login" prefence to the same page as the installed SVN projects. (It wouldn't hurt anyone for it to be listed in both places...) All other preferences can be buried in the Preferences dialog since they are for more advanced users, but every beginning user who finds the Script Manager should be faced with the information that he can chose for them to be automatically updated.

What I remember is that authors asked Bale and between them they edited the table here. Magic happens and that table got parsed into the datafile that gets updated and drives Script Manager. But my scripts were in that post before Script Manager so I really don't know what the procedure is and I do recall valid concerns about letting just anyone update the file.

The current procedure is the same as the old procedure. Either post in that thread to ask for it to be added to the Script Manager or else I might add it to the Script Manager on my own if I happen to notice that there is something to add. The later happens more often than the former.

 

[xKiv]

I'd rather people figure out how to reproduce the bug with Guide that causes mafia to (silently?) fail updates..

https://github.com/Ezandora/Guide/branches/Release/

Without looking at it, I would suspect it's something like Ezandora sometimes somehow effectively *creating* a new Release branch [1] instead of merging changes into the existing branch. Then our checked-out copies point to HEAD of a dead branch (no longer even accessible), and have no direct relationship with whatever currently lives at branches/Release.

[1] this might also be artefact of github's git-to-svn support.


After looking at it a bit ... I don't know. I checked out the git version, and that looks alright (the "Release" branch has a simple linear topology, no merging, every version is a child commit of the previous version, going back to 1.0.1, 1.0, and a2).
Doing "svn log" in the Release branch shows commits all the wat back to r3 in 2014-01-18.
Doing "svn log" in svn root (checking out just https://github.com/Ezandora/Guide) goes only to r132, and trying to look at logs of anything from r131 up returns error E175002. "svn log -r130:1" returns logs all the way back to r1. Something's definitely broken *there*.

Then I wanted to look at graph of revisions in eclipse, but subclipse refuses to be helpful, because of the aforementioned error.

 

[roippi]

Hum. Have people been having Guide updating break on them multiple times, or is it perhaps limited to that one singular hiccup in the repo (that everyone who then had it installed experienced)?

(I have to say that I'm increasingly aware of how fragile a technology svn is. Between various sourceforge/github issues and new versions not being backwards-compatable... ah well. We're married to it now.)