Runnning betaMAM tasks from WCG I know my tasks have had their deadlines extended. (This needed on a Ryzen9 with only two tasks running and little else.) Is there a way for the project to communicate this to the client or is the displayed deadline fixed once the tasks have ? A project update does not achieve this. It would be nice to see this in the manager rather than have to go to the task pages to see it.

PG does (did?) this by making server to wait for otherwise timeouted WU to complete (thus extra WUs are not issued). But *only* if client routinely reports progress. AFAIK clients won't abort timeouted WU, except if operator does it by themself. I have zero knowledge of server telling client to increase ETA.

---

I'm counting for science,
points just make me sick.

Dave, I don't think anyone has requested this option so... why don't you create a new ticket on the BOINC git repository?

Not sure i'd consider this an issue.

If the deadline has been extended, but not updated on the system, then the only way it would be a problem (as such), is for those that micromanage their systems; they see the deadline has been reached or passed, and manually delete the Task.
For everyone else- it's not an issue. If the deadline's been extended but not updated on the system, then it will still get done according to the existing deadline, returned, Validated & Credit awarded. It may or may not get bumped up to a being processed as a High priority Task if it starts later/runs much longer than the BOINC Manager expected. But it will still get done & returned in time for Credit.

And if the Project reduces the deadline for Tasks already issued?
The Tasks will get re-issued if the earlier longer deadline issued ones haven't been returned by the new shorter deadline date. If those re-issued Tasks get returned & Validated before the initially issued longer deadline Tasks, then those earlier issued longer deadline Tasks will be cancelled by the server if they haven't already been started. If they have already been started, then they should continue to completion & if Validated upon return, Credit still awarded.



I can actually see updating deadlines for already issued Tasks causing all sort of problems.

People get mighty worked up when they have large caches, lots of projects, and Tasks with all sorts of different deadlines and all sorts of ideas about what their Resource Share settings actually are (i'm forever telling people that they're a ratio, not a percentage. And that what is run and when, is based on work actually done, not the amount of time spent processing / the amount of Credit for that Project).
Changing the deadlines on already issued Tasks is going to cause the Manager to stop and start multiple other Tasks across multiple projects- causing meltdowns from those that have spent months getting BOINC to process a certain number of Tasks for certain projects at any given time.

Not changing the deadline for already issued Tasks doesn't cause any issues of significance IMHO. But changing them will cause issues, that will significant those that would consider it to be an issue IMHO.

---

Grant
Darwin NT.

And if the Project reduces the deadline for Tasks already issued?

I admit I had not thought of the consequences of projects reducing deadlines. For those who micromanage and might delete the tasks an alternative might be for the projects to push a notice. (Might be a pain for some if they can't restrict that to those running the tasks though.) This has so far only been an issue on MAM beta tasks on WCG. I certainly won't be requesting git-hub add it as a feature unless I see it happening a lot more often. On CPDN all the development tasks are only sent to a small group of crunchers who know the results are wanted ASAP irrespective of what the deadline is. I don't know if the issue ever crops up on other projects.