-
Notifications
You must be signed in to change notification settings - Fork 5
Issues: neume-network/extraction-worker
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Basing extraction-worker on nodejs disallows usage in the browser
#46
opened Sep 19, 2022 by
TimDaub
for any IPFS URI, we're currently not validating if the request's results are matching the hash
#45
opened Sep 16, 2022 by
TimDaub
call-block-logs makes worker run out of heap memory
bug
Something isn't working
#40
opened Aug 6, 2022 by
TimDaub
We're not distinguishing between permanent or temporary request failures (e.g. for permanently deleted IPFS CIDs)
bug
Something isn't working
help wanted
Extra attention is needed
#29
opened Jun 30, 2022 by
TimDaub
some requests to soundxyz's API fail, are we rate limited?
bug
Something isn't working
#21
opened Jun 28, 2022 by
TimDaub
extraction-worker should parallelize different root domains
enhancement
New feature or request
#19
opened Jun 27, 2022 by
TimDaub
To allow parallelizing neume strategy transformations, refactor extraction worker
#9
opened May 17, 2022 by
TimDaub
For tests calling services on the internet, sandbox them with fetch-mock
enhancement
New feature or request
good first issue
Good for newcomers
help wanted
Extra attention is needed
#2
opened Apr 4, 2022 by
TimDaub
ProTip!
Updated in the last three days: updated:>2024-11-13.