Drops not being claimed in the intended way, causing some to be missed and no notifications #85
Labels
Bug
Something isn't working
Comments
|
Is it claimed on reload? I think this might be similar to #63, where I also experienced a drop not being claimed at first, because the miner thought it was mining another drop. |
|
Yes, a reload always claims (this is in fact, how I have temporarily bypassed the issue in my fork Valentin-Metz@07047a4). |
|
I also don't know how I'd debug it, because trying something and then running the miner would immediately fix it. I also haven't even experienced this myself. |
|
The solution to this is probably adding a lot more logging statements (and maybe upgrading to / introducing a proper logging framework). |
This was referenced May 31, 2024
|
Hi, I released v15.6.0, can I get a confirmation that this is still an issue? I'm always running the latest in-dev to try and find bugs before releasing and have never experienced this. |
|
I was able to complete and claim with your new release. I'll keep an eye and update you. Edit: I am out of open campaigns, but it seemed to have done the job and completed 3 drops |
edit: after restarting the app multiple times its now working |
|
@dogodogowoof @rothexD I'll leave it open. Again, I don't think much should've changed regarding this. I didn't specifically do anything to fix it, as I don't know what's wrong because I never had this issue. |
|
You'll probably only start running into it if a long, multistage campaign shows up. I'd assume it to still be there. |
I had no issues with the whole last ow2 campaign. |
|
So, I just happened to witness the end of a drop, and it did get stuck for a bit, but pretty quickly refetched and claimed without logging. I guess there was some logic to claim when a drop is done and the thing fetching and thus claiming it for me might be a built-in fail-safe sort of thing. edit: unfortunately running the exe and not vs code tho |
|
So I ran it in |
|
Interesting traces. When I was running into the issue, it seemed to claim the previous drop when achieving a new drop at least. |
|
Never triggered.This is a video of it happening, it weirdly does the last minute twice, and again, reloads out of nowhere (Maintanance task was supposed to be triggered at Untitled.video.15.mp4Logs |
Windows200000
changed the title
This was referenced Jun 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This has been an ongoing issue for a few weeks:
Drop progress is full, but no claim is triggered:
Full log output:
The text was updated successfully, but these errors were encountered: