Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Duplicate key value violates unique constraint (Despite Fix) #361

Open
2 tasks done
ToasterUwU opened this issue Dec 19, 2024 · 1 comment
Open
2 tasks done

Duplicate key value violates unique constraint (Despite Fix) #361

ToasterUwU opened this issue Dec 19, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@ToasterUwU
Copy link

  • I have checked the existing issues to avoid duplicates
  • I have redacted any info hashes and content metadata from any logs or screenshots attached to this issue

Describe the bug

Im on the newest version and still regulary have the issue described in #285 that should have been fixed by #319

Something is stuck in the retry queue, doesnt get processed correctly and than locks bitmagnet in an endless loop of failing to run properly.

To Reproduce

Steps to reproduce the behavior:

  1. Have a lot of things in the database already
  2. Restart the Container or Host
  3. Be unlucky enough to have the issue

Expected behavior

I expect some kind of error handling for this. Like "Duplicate Key error, deleting item from queue" and be done with it.

Environment Information (Required)

  • Bitmagnet version: v0.9.5
  • OS and version: NixOS 24.11 Docker
  • Please specify any config values for which you have overridden the defaults: Prcessor Concurrency = 3, DHT Crawler Scaling Factor = 15

Additional context

I changed the concurrency to 1, in hopes of it being fixed by that. But i honestly dont know, just throwing things at the wall here.

@ToasterUwU ToasterUwU added the bug Something isn't working label Dec 19, 2024
@ToasterUwU ToasterUwU changed the title Short description of bug Duplicate key value violates unique constraint (Despite Fix) Dec 19, 2024
@ToasterUwU
Copy link
Author

To be extra clear, this comment has the same error message and the same by hand one time fix that also work for me. This seems to be exactly the same issue as here: #285 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant