unrecognized format: dag-cbor

[christroutner]

• Version: ipfs-http-client v56.0.1

• Platform: Linux trout-dev 5.13.0-30-generic 33~20.04.1-Ubuntu SMP Mon Feb 7 14:25:10 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Node: v16.14.0
npm: v8.5.2

• Subsystem: ipfs-http-client

Severity: Low

Description:

My app uses ipfs-http-client v56.0.1 to control an external go-ipfs node running v0.11.0. I'm running a very simple example app for my ipfs-coord library.

I started noticing high CPU usage. When running glances, I notice the app uses about 100% of a single core. When running the app with DEBUG=* I see a lot of these message:

  ipfs-http-client:lib:error-handler { Message: 'unrecognized format: dag-cbor', Code: 0, Type: 'error' } +3s
  ipfs-http-client:lib:error-handler { Message: 'unrecognized format: dag-cbor', Code: 0, Type: 'error' } +933ms
  ipfs-http-client:lib:error-handler { Message: 'unrecognized format: dag-cbor', Code: 0, Type: 'error' } +1ms
  ipfs-http-client:lib:error-handler { Message: 'unrecognized format: dag-cbor', Code: 0, Type: 'error' } +379ms
  ipfs-http-client:lib:error-handler { Message: 'unrecognized format: dag-cbor', Code: 0, Type: 'error' } +3ms

I'm thinking that these error messages are related to the high CPU usage.

I'm trying to figure out where they are originating from. I scanned the js-ipfs repository, but couldn't find any instance of 'unrecognized format'.

Does anyone know what is causing these errors? Can anyone post a link to the source code where the error message is generated?

Steps to reproduce the error:

There is a process to setting up the example app, bug roughly: Install dependencies, fire up a go-ipfs node, and then execute [this example script](example app) with this command:

• DEBUG=* node start-external.js

Also, my IPFS nodes run on a private IPFS network. The swarm key for joining the network is here

[christroutner]

Through a process of elimination, I was able to isolate the issue to orbit-db. I filed this issue in their repository.