[Account Manager RPC] <suspend><dont_request_more_work><update> behavior [7.6.9 (x64)]

[Kati3e]

<update>1</update>
<suspend>1</suspend>
<dont_request_more_work>1</dont_request_more_work>

I would expect this to attach a project as "Suspended" and "Won't get new tasks", and then update the project, getting the Project Name, Account, Team.. etc. But no tasks.

What happens instead is the project starts downloading new tasks right away. And the project is no longer set to suspended. "Won't get new tasks" is still set, but is not enforced.

---

Also this isn't really a bug I guess but I noticed it is not possible to remove projects that were added via an account manager. You must stop using the account manager, then remove them. Is there a reason for that? I'd think the client should never restrict the user from removing a project under any circumstance.

[davidpanderson]

I checked in changes to the client that (I think) fix this. These are in trunk, and will appear in an upcoming release.

The inability to remove projects sent by the account manager is intentional; a project removed in this was would quickly be added back by the account manager.

[Kati3e]

"The inability to remove projects sent by the account manager is intentional; a project removed in this was would quickly be added back by the account manager."

Shouldn't it be the account managers responsibility to update the settings on their own servers? Aka, if a project was removed from BOINC, set it as removed on the account manager. Just like you would if the user had suspended it in the client or set it to not request more work; instead of locking these projects down from a user being able to remove them? I've seen lots of people asking why they can't remove projects in the client and resort to deleting the files themselves.. There is not even an indication as to why the "Remove" button is greyed out when this happens, just causing even more confusion for the user. Please reconsider this. There is no reason why account managers wouldn't be able to handle projects being removed, correctly.

Every time a request is made to the account manager, a list of all attached projects are sent along with it, meaning the account manager just needs to scan them for any missing projects, if any are found to be missing, assume the user removed it and set the project to detached, server side. Just as you would for Suspended tasks.

[davidpanderson]

The idea is that when using an account manager,
the account manager becomes the interface for adding/removing projects.

Typically an AM is used to manage multiple hosts;
the semantics you suggest wouldn't make sense in this situation.

In any case, the AM protocol is pretty much set in stone at this point;
BAM! and Gridrepublic aren't going to change the way they work.

[grctest]

In any case, the AM protocol is pretty much set in stone at this point;
BAM! and Gridrepublic aren't going to change the way they work.

Can we get input from BAM! and Gridrepubic so see if they'd be open to changes?

Gridcoin community is looking into making a fully open source Gridcoin pool kit which is effectively an account manager: https://cryptocointalk.com/topic/49262-open-source-project-gridcoin-pool-boinc-account-manager/

If we're successful in creating this kit then this issue will be a repeating issue not just for @Kati3e but for multiple users who create pools.

Since both Gridrepublic (Matt Blumberg) and Boincstats (Willy de Zutter) are on the Boinc Project Governance Model, I'd appreciate open discourse on this matter. I'll be emailing the boinc_stats mailing list http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_stats.

Best regards,
CM.