Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / neume-network/extraction-worker issues and pull requests

#60 - allow extraction-worker to be used without worker_thread

Issue - State: closed - Opened by il3ven about 2 years ago - 2 comments

#59 - debug doesn't show logs for validation with DEBUG=* in /core

Issue - State: open - Opened by TimDaub about 2 years ago

#57 - update @neume-network/[email protected]

Issue - State: open - Opened by TimDaub about 2 years ago

#56 - extraction worker still uses message-schema, but it has been deprecated

Issue - State: closed - Opened by TimDaub about 2 years ago - 2 comments

#55 - feat/add-arweave-api

Pull Request - State: closed - Opened by Kunkka0822 about 2 years ago - 5 comments

#54 - try to parse all requests as json

Pull Request - State: closed - Opened by il3ven about 2 years ago - 1 comment

#53 - test cases for result json parsing

Issue - State: closed - Opened by TimDaub about 2 years ago

#52 - Implement Arweave support

Issue - State: closed - Opened by TimDaub about 2 years ago - 4 comments

#51 - Implement content negotiation using `Accept` and `Content-Type` header for worker

Issue - State: closed - Opened by TimDaub about 2 years ago - 1 comment

#50 - parse response as json only if content-type includes json

Pull Request - State: closed - Opened by il3ven about 2 years ago

#49 - extraction-worker shouldn't try to `JSON.parse` all responses

Issue - State: closed - Opened by il3ven about 2 years ago
Labels: bug

#48 - Use weiroll to batch process multiple eth_call requests in a single RPC call

Issue - State: closed - Opened by TimDaub about 2 years ago - 1 comment

#47 - feat: handle ipfs messages

Pull Request - State: closed - Opened by il3ven about 2 years ago - 5 comments

#46 - Basing extraction-worker on nodejs disallows usage in the browser

Issue - State: open - Opened by TimDaub about 2 years ago - 1 comment

#44 - validate config before running

Pull Request - State: closed - Opened by il3ven about 2 years ago - 3 comments

#43 - fastq implementation

Pull Request - State: closed - Opened by TimDaub over 2 years ago - 1 comment

#40 - call-block-logs makes worker run out of heap memory

Issue - State: open - Opened by TimDaub over 2 years ago
Labels: bug

#39 - `workerData.endpoints` should use neume-network/schema

Issue - State: closed - Opened by TimDaub over 2 years ago - 3 comments

#38 - add rate limiter

Pull Request - State: closed - Opened by il3ven over 2 years ago - 1 comment

#37 - Return message object from panic function

Pull Request - State: closed - Opened by il3ven over 2 years ago

#36 - Rate limits should be definable by extraction-worker pool

Issue - State: closed - Opened by TimDaub over 2 years ago - 1 comment

#35 - Tests fails because setTimeout cannot be set in expressively-mocked-fetch

Issue - State: closed - Opened by TimDaub over 2 years ago
Labels: bug

#34 - panic returns context free error in false message object

Issue - State: closed - Opened by TimDaub over 2 years ago - 2 comments
Labels: bug

#33 - some blatantly wrong IPFS CIDs aren't immediately purged from the worker

Issue - State: closed - Opened by TimDaub over 2 years ago - 1 comment
Labels: bug

#31 - extraction-worker implements `setTimeout` falsely

Issue - State: closed - Opened by TimDaub over 2 years ago
Labels: bug

#30 - STATUS 429 has a Retry-After

Issue - State: open - Opened by TimDaub over 2 years ago - 2 comments

#28 - current queue usage doesn't batch tasks

Issue - State: closed - Opened by TimDaub over 2 years ago - 2 comments
Labels: bug

#27 - there are cases in extraction-worker where only a string can be returned as the result of a message object

Issue - State: closed - Opened by TimDaub over 2 years ago - 1 comment
Labels: bug, enhancement, help wanted, question

#26 - log to signal eth_call is not useful and leads to the debug log being spammed

Issue - State: closed - Opened by TimDaub over 2 years ago
Labels: bug

#25 - We must allow a user to pass better-queue options from outside

Issue - State: closed - Opened by TimDaub over 2 years ago
Labels: bug, enhancement, help wanted

#24 - function panic to handle better-queue errors is assuming false callback structure

Issue - State: closed - Opened by TimDaub over 2 years ago
Labels: bug

#23 - It's difficult to understand if a very long timeout in `fetch` could stall the extraction worker's progress

Issue - State: closed - Opened by TimDaub over 2 years ago - 5 comments
Labels: bug, help wanted, question

#22 - It's hard to debug how many requests per second extraction worker does

Issue - State: closed - Opened by TimDaub over 2 years ago - 1 comment
Labels: bug, good first issue, help wanted

#21 - some requests to soundxyz's API fail, are we rate limited?

Issue - State: open - Opened by TimDaub over 2 years ago - 3 comments
Labels: bug

#20 - error message for failing HTTPS request isn't useful for debugging

Issue - State: closed - Opened by TimDaub over 2 years ago
Labels: bug

#19 - extraction-worker should parallelize different root domains

Issue - State: open - Opened by TimDaub over 2 years ago - 7 comments
Labels: enhancement

#18 - Implement getLogs

Issue - State: closed - Opened by TimDaub over 2 years ago

#17 - if a string blockNumber "arbitrary" is passed to "eth_call" it can be that simply no results are returned. `results: undefined`. It should throw

Issue - State: closed - Opened by TimDaub over 2 years ago - 6 comments
Labels: bug, good first issue, help wanted

#16 - must define [email protected] as peerDependency

Issue - State: closed - Opened by TimDaub over 2 years ago
Labels: bug

#15 - make `concurrency` option in queue configurable with env vars

Issue - State: closed - Opened by TimDaub over 2 years ago - 1 comment

#14 - allow downloading data from ipfs://

Issue - State: closed - Opened by TimDaub over 2 years ago
Labels: bug

#13 - upgrade [email protected]

Issue - State: closed - Opened by TimDaub over 2 years ago - 1 comment
Labels: enhancement, good first issue, help wanted

#12 - update message-schema version, fix unit tests and fix prettier CI

Pull Request - State: closed - Opened by il3ven over 2 years ago - 2 comments

#11 - on npm, release extraction worker under new organization scope

Issue - State: closed - Opened by TimDaub over 2 years ago

#10 - %s/music-os/neume-network/g

Issue - State: closed - Opened by TimDaub over 2 years ago
Labels: enhancement, good first issue, help wanted

#8 - NEW: add CODE_OF_CONDUCT

Pull Request - State: closed - Opened by phadkesharan over 2 years ago

#7 - add coc

Issue - State: closed - Opened by TimDaub over 2 years ago - 2 comments
Labels: documentation, enhancement, good first issue, help wanted

#6 - separate message object schema definition from rest of code

Issue - State: closed - Opened by TimDaub over 2 years ago

#3 - get api's version specifier from package.json

Issue - State: open - Opened by TimDaub over 2 years ago

#2 - For tests calling services on the internet, sandbox them with fetch-mock

Issue - State: open - Opened by TimDaub over 2 years ago
Labels: enhancement, good first issue, help wanted

#1 - implement special graphql job message

Issue - State: closed - Opened by TimDaub over 2 years ago