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

DID object not able to be propageted to IPFS API #1

Open
k-solutions opened this issue Jan 9, 2023 · 1 comment
Open

DID object not able to be propageted to IPFS API #1

k-solutions opened this issue Jan 9, 2023 · 1 comment

Comments

@k-solutions
Copy link

k-solutions commented Jan 9, 2023

I was tring to run examples/create.js, but could not submit the file to IPFS.
My test environment is against "preview" network.

IPFS daemon log:
'
ipfs0 | ipfs version 0.17.0
ipfs0 | Found IPFS fs-repo at /data/ipfs
ipfs0 | Initializing daemon...
ipfs0 | Kubo version: 0.17.0-4485d6b
ipfs0 | Repo version: 12
ipfs0 | System version: amd64/linux
ipfs0 | Golang version: go1.19.1
ipfs0 | 2023/01/09 15:16:32 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/lucas-clemente/quic-go/wiki/UDP-Receive-Buffer-Size for details.
ipfs0 | Swarm listening on /ip4/127.0.0.1/tcp/4001
ipfs0 | Swarm listening on /ip4/127.0.0.1/udp/4001/quic
ipfs0 | Swarm listening on /ip4/172.21.0.3/tcp/4001
ipfs0 | Swarm listening on /ip4/172.21.0.3/udp/4001/quic
ipfs0 | Swarm listening on /p2p-circuit
ipfs0 | Swarm announcing /ip4/127.0.0.1/tcp/4001
ipfs0 | Swarm announcing /ip4/127.0.0.1/udp/4001/quic
ipfs0 | Swarm announcing /ip4/172.21.0.3/tcp/4001
ipfs0 | Swarm announcing /ip4/172.21.0.3/udp/4001/quic
ipfs0 | API server listening on /ip4/0.0.0.0/tcp/5001
ipfs0 | WebUI: http://0.0.0.0:5001/webui
ipfs0 | Gateway (readonly) server listening on /ip4/0.0.0.0/tcp/8080
ipfs0 | Daemon is ready
'

The log from Sidetree-cardano node is:
`
Event emitted: cardano_observing_loop_success
Got latest blockchain time: {"time":8248530,"hash":"c24ccb57b3d2f12b97abe6ba38dd2ac987ff3bafbc28458d8e17a9f3b7c0e6c6"}
Event emitted: sidetree_blockchain_time_changed: {"time":8248530}
Core cachedApproximateTime updated to: 8248530
Start operation batch writing...
Getting blockchain time...
Getting time
Got latest blockchain time: {"time":8248530,"hash":"c24ccb57b3d2f12b97abe6ba38dd2ac987ff3bafbc28458d8e17a9f3b7c0e6c6"}
Getting blockchain time...
Getting time
Got latest blockchain time: {"time":8248530,"hash":"c24ccb57b3d2f12b97abe6ba38dd2ac987ff3bafbc28458d8e17a9f3b7c0e6c6"}
IPFS write error response status: 500
IPFS write error body: {"Message":"expected a file argument","Code":0,"Type":"error"}

Event emitted: sidetree_batch_writer_loop_failure: {"code":"ipfs_failed_writing_content"}
End batch writing. Duration: 543 ms.
Waiting for 60 seconds before writing another batch.
Fetching Sidetree transactions from blockchain service...
Fetching URI 'http://127.0.0.1:3002/transactions?since=16959601786224640&transaction-time-hash=826a606c86825e5e9f4f33bdd22cc4a63b89bac3543c58a4a685b5c6bc5864f8'...
Transactions request: since transaction number 16959601786224640, block hash '826a606c86825e5e9f4f33bdd22cc4a63b89bac3543c58a4a685b5c6bc5864f8'...
Fetch response: 200'.
Fetched 0 Sidetree transactions from blockchain service in 4 ms.
Successfully kicked off downloading/processing of all new Sidetree transactions.
Processing previously unresolvable transactions if any...
Fetched 0 unresolvable transactions to retry in 1 ms.
Event emitted: sidetree_observer_loop_success
Waiting for 60 seconds before fetching and processing transactions again.
Starting processTransaction at: 1673280074387
Getting blockchain time...
Getting time
Processing 0 new transactions
Finished processing 0 transactions
Event emitted: cardano_observing_loop_success
Got latest blockchain time: {"time":8248533,"hash":"50b1226f957b6eb4ad66a286077c9e04147eb057fc190c2244ad7640b8ee9417"}
'

@k-solutions k-solutions changed the title IPFS not able to be propageted to IPFS API DID object not able to be propageted to IPFS API Jan 9, 2023
@rodolfomiranda
Copy link
Owner

This problem start happening with version of IPFS greater that 0.11. Seems that ipfs implemented something that breaks in the sidetree reference implementation. My workaround at that time was just to revert IPFS to 0.11 (see this issue )

I just noticed now that the problem was fix in newer sidetree version based on that issue. However the code in sidetree repo is ahead of the fork I used for this project. That needs to be updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants