-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
manual import of hashes fails #10
Comments
Thanks, let me look into this and get back to you. I haven't tried the importer in a little while and it definitely needs more work anyway.... |
This should be fixed in the latest release, could you give it another try? |
Perfect, thanks for the quick fix. I had the same issue and works with the latest update.
|
Good to hear, thanks! Closing this now.... |
I am stupid, sorry. |
Hi @bonny1992 this is working for me using 0.1.0. If you could redact any copyrighted material and post a line of JSON here I'll see if anything looks obviously wrong - please do not post any complete info hashes, just remove 1 character is fine. |
No, I'm sorry, you're right. It's working fine. BTW, sorry to derail this issue, but is there any place where I can find what are the expected fields for an import? There's a very old csv I'd like to import (from an Italian tracker that closed some years ago) and for sure that doesn't have any imdb id :) |
@bonny1992 I still need to add a proper schema for the import. You can see the data structure here: https://github.com/bitmagnet-io/bitmagnet/blob/main/internal/importer/importer.go#L44 - at a minimum you'll need |
Thank's for creating this awesome tool.
I've tried to run your example script to import the bittorrent hashes from rarbg, but curl always fails with the following output:
bitmagnet shows the following logs, before restarting:
the Json data (with the hashes removed) generated before it get's piped into curl seems reasonable:
manually sending a request with a single json object returns a sucess message, but the data doesn't seem to get added (unavailible in the web dashboard and there are no logs showing that anything is happening)
The text was updated successfully, but these errors were encountered: