Quote from: bible_pay on August 10, 2018, 01:50:31 PM

Quote from: cryptocadxyz on August 09, 2018, 10:43:58 PM

Quote from: bible_pay on August 09, 2018, 10:05:24 PM

Quote from: rastiks on August 09, 2018, 08:46:49 PM

Quote from: cryptocadxyz on August 09, 2018, 05:12:24 PM

Rob, I tried migrating completely to WCG to test this last week and noticed my wallet stopped sending PODC updates after a week. I read through my log and discovered that after suspending Rosetta on each machine, the first number in my PODC Updates steadily decreased. It went from "PODCUpdate Processed (7) over 1 CPID(s) successfully" down to "PODCUpdate Processed (1) over 1 CPID(s) successfully." and then finally PODCUpdate Processed 0 tasks for CPID. At this point, my wallet transaction list no longer showed PODC updates. I tried manually running "exec podcupdate true" but it would fail and say Processed (0). Only until I took one of my machines and started crunching Rosetta again, was I able to get it to run PODC updates once again automatically.

Do you think you could explain this? Thanks!

I'm experiencing the same issue right now. Few days after I solved my last Rosetta task, I stopped receiving rewards - the wallet is not sending PODC updates.
"exec podcupdate true" it would fail and say Processed (0) tasks.

I think you guys do have a point here. The wallet does have a spork (a network config setting) that dictates if it should be counting task weight per project, but I dont believe its honoring that setting from the PODC Update perspective. So for now you can get around this by typing:
exec podcupdate true (that means force=true) if you are wcg only, do this once per day, but yes, I need to take a look at this as this is exactly the kind of thing new users hate.

Hi Rob, I tried PODC update true, but it refuses to work when no Rosetta hosts are crunching.

I had a quick look at the rpcblockchain.cpp. I notice that PODCUpdate function will return false if iInserted == 0. iInserted seems to only be incremented in a loop that iterates through all the BOINC hosts that a user has extracted from GetBoincHostsByUser. Given that GetBoincHostsByUser is passed the argument "project1", does that mean only hosts crunching Rosetta are counted? Because if so, that would explain why an individual with WCG only hosts would be unable to send PODC updates.

Sorry my coding skills are a bit rusty, and I'm not very familiar with the BBP source. Please correct if I'm wrong.

I'll take a look at this today, maybe we need a leisure to fix this; and we can roll out the fast boot feature at the same time.

This will be fixed in a few hours as a leisure.

In this way WCGs or Rosetta PODC updates should go through automatically starting in version 1.1.4.4.