neume-network / data

On-chain music NFT data.

neume-network/data Issues

Sound Protocol is not being properly crawled.
Updated 2 years ago4
sound-protocol crawl includes multiple editions
Updated 2 years ago
All downstream strategy results from call-block-logs-transformation aren't including the newly added transactionHash metadata
Updated 2 years ago
for music-os-accumulator check if all list entries comply with track schema from /schema in a test
Updated 2 years ago
For all call-block-logs-transformation mint events, do a getTransactionReceipt to get a minter (from) and the original transaction hash
Updated 2 years ago
for sound-protocol artist name doesn't show up in neume music-os-accumulator schema
Closed 2 years ago
logs-to-subgraph test file can be deleted
Updated 2 years ago
In 71fbeea3ac0363b653abe786b33b62d95c2a6dee, noizd tracks don't seem to be included in music-os-accumulator file
Updated 2 years ago1
3.mjs is buggy as call-tokenuri must include an argument about the extractor file path
Closed 2 years ago
2.mjs seems unnecessary now
Updated 2 years ago
sound protocol integration checklist
Closed 2 years ago
Integrate missing call-tokenuri platforms into crawlpath at steps/3.mjs
Updated 2 years ago
data quality assurance pipeline is not working
Closed 2 years ago1
add indie artist sound of fractures
Updated 2 years ago
in update neume-network/data file step, some files don't seem to be present; is this a problem?
Updated 2 years ago
we should only update `lastBlockNumber` file with valid block numbers
Closed 2 years ago1
integrate zora drops
Updated 2 years ago2
integrate newly added noizd strategies into continuous crawl
Closed 2 years ago
some newly released songs on soundxyz aren't showing up in the music os data feed
Closed 2 years ago1
green ring NFT on catalog has a duplicate
Updated 2 years ago4
add green ring indie artist
Updated 2 years ago
data quality assurance should run on every new push on main branch but it doesn't
Updated 2 years ago
it is not easy to find logs for a given commit
Closed 2 years ago1
the `lastBlockNumber` script doesn't work
Closed 2 years ago2
For platforms like soundxyz that implement custom editions, attempt to filter by unique audio manifestations and see if editions get reduced to unique works
Updated 2 years ago
In yet another case, the continuous crawl produced a duplicate
Updated 2 years ago
duplicate songs in music-os-accumulator
Closed 2 years ago3
Some partial crawls end up running very long and its unclear why they do
Closed 2 years ago6
We often don't comply to our own schema in this repository and we are unaware of it
Updated 2 years ago
Since we now don't have steps in Github actions we can use a single crawl path
Closed 2 years ago2
Since the crawl is continuous, music-os-accumulator is appended with new data but our users expect one big JSON array with all tracks and no line separation
Closed 2 years ago1
at the time of invoking the step 0.mjs file, soundxyz-filter-contracts-transformation file won't exist yet
Closed 2 years ago
we can technically switch back to cpina/github-action-push-to-another-repository as we stopped using the ignore file option for now
Closed 2 years ago
when the new NFT IDs get appended to the old NFT IDs in logs-to-subgraph, and then a downstream strategy like soundxyz-call-tokenuri gets called: It sees the entire huge file and recrawls everything and not just the delta
Closed 2 years ago3
instead of manually renaming call-block-logs-transformation into logs-to-subgraph-extraction, we should define transformer.args[0]
Closed 2 years ago
block-logs crawl is failing because I have remove authorization for the time being to run some jobs manually
Closed 2 years ago
Crontab of block-logs.yml is currently crawling every 10th minute of the hour, but we want every ten minutes
Closed 2 years ago
If 10min call-block-logs crawl runs regularly, we may not need to execute it on a powerful machine
Closed 2 years ago1
there can potentially be duplicate data in call-block-logs-transformation because we're not adding to the latest crawled block
Closed 2 years ago1
After call-block-logs-transformation, GitHub Action Worker never stops
Closed 2 years ago1
given `scripts/lastBlockNumber` and a network call to an Ethereum node, determine start and end parameters of call-block-logs-extraction step
Closed 2 years ago2
checkout step for neume-network/core wrongfully assumes that if neume-network/data@branchname is run, that branch is available on neume-network/core@branchname too
Updated 2 years ago2
script to efficiently extract the last block number from results/call-block-logs-transformation is missing
Closed 2 years ago
GitHub Action that commits to the `results` repository isn't additive, it deletes all content of the repository and re-adds the crawl results
Closed 2 years ago1
using ssh-agent, a GitHub Actions step should log into node.rugpullindex.com, trigger a crawl that downloads the lastest blocks and append them to call-block-logs-transformation
Closed 2 years ago1
job 1 - job x are non-descriptive names for what is actually going on
Closed 2 years ago
github action indicate that a job had been running for 6 hours, but that doesn't seem right
Closed 2 years ago
To crawlpath, add NFT owner information
Updated 2 years ago8
For files over 100MB, they cannot be pushed to GitHub with regular git
Updated 2 years ago4
soundxyz makes crawl fail
Closed 2 years ago