Please add ability to change from pause to finish

[calxalot]

Muz, please link to your github issue. Thanks.

[muziqaz]

Muz, please link to your github issue. Thanks.

Yeah, I'm trying to find it, but failing miserably. I'll end up just creating a new ticket and be done with it. I'm at work like now, so my attention is limited

[muziqaz]

https://github.com/FoldingAtHome/fah-we ... issues/240
I created a new ticket, but as I'm writing that ticket, think it is a bad idea, since people who want to just resume folding, would need to click fold twice.
It has been established long ago, that we don't want to clutter the UI with Fold, Pause, Finish buttons on the main page.

I think this boils down to the personal preferences and is not universal request

Edit: I was presented with the real world case where this request makes sense.

However, I would say if user wants to use FAH in such a tricky circumstances, enabling Advanced Options within fahclient settings would solve this, if one creates separate resource groups to each device which they want to fold on

[Peter_Hucker]

I used to report every single bug in everything, but nowadays everyone's a beta tester. Well I'm tired of it.

[arisu]

Remember the v8 client is developed by one overworked guy. It's not a big team who just have their priorities backwards like Activision.

Although if it was up to me, I would just rewrite the client completely at this point. The client is basically a dumb wrapper around the cores with some bells and whistles added on, and rewriting it in a language other than C++ would probably be useful. Even Python would be fitting.

I'd write a minimal client myself, but I'm not allowed to.

[muziqaz]

V8 is a complete rewrite
I hope dev does not get a whiff of this thread

One should understand the clear fact of programming:
It is easy to criticise someone else's work until you do it yourself V8 is a vision of that dev, if that vision does not meet your specific personal agenda, that is your specific problem. There is never a perfect app for your needs or a code someone else wrote

Fahclient is open source, you can submit your suggestions or a complete rewrite without any issues.
Wether Dev accepts the changes or the rewrite is another matter

[arisu]

Anyone can suggest or show a complete rewrite, but the EULA prevents us from using it unless it's accepted.

[muziqaz]

So suggest, and see

[arisu]

What might be better is requesting a change to the EULA to allow 3rd party clients, perhaps with some minimal vetting or a minimum number of mandatory features. There isn't much that a client can do to cheat or damage the science as long as the cores are not tampered with. But I know that's not going to fly.

[muziqaz]

As I said, GitHub is your friend. Dev is there to read and deny your suggestions

[calxalot]

Where is the EULA for v8? I don’t see it distributed with the client.

[muziqaz]

calxalot, wouldn't your lufah utility be considered an alternative to the client? Oh, no, it is alternative to web ui. isn't it?

[calxalot]

Sorta. It sends commands to clients using the undocumented api that web control uses. It doesn’t login to an account or use the node system.

[arisu]

Where is the EULA for v8? I don’t see it distributed with the client.

I don't think it has an EULA itself (though it does have a license), but using FAH servers do, and it says you can only contact the servers using the official client. So making a custom, lighter client would break the current EULA, even if its behavior is identical to and indistinguishable from the v8 client.

It's silly imo because all the important safety checks are done by the cores, and the client's job is really quite simple: Send hardware info to the server, download the assigned WU, execute the core, return wuresults_01.dat if the core terminates successfully, otherwise send dump/failure report. An absolutely minimum client could probably be written in a 100 line Python script using the json and requests modules.

Literally the worst a custom client could do if it was buggy is download WUs and unnecessarily dump them. What the v8 client tends to do anyway because it can't distinguish between a 127 exit status caused by WU_STALLED and caused by the dynamic linker missing a library.

[TheMikeyDK]

Sorta. It sends commands to clients using the undocumented api that web control uses. It doesn’t login to an account or use the node system.

How undocumented is it? Is it possible to somehow find some information about that?