-
Notifications
You must be signed in to change notification settings - Fork 1.2k
interface-ipfs-core tests failing on my machine #902
Comments
my system setup is a bit nonstandard |
It's hard for me to see what's going on without having a way to replicate the environment. The files API should not fail and since WebRTC is not injected by default anymore, there shouldn't be anything that could cause a lag on the network side of things that would trickle lagging to those tests. The first two tests seem like a Race condition to me (//cc @pgte) and the third one fails because the other two didn't finish correctly. |
@kumavis can't seam to reproduce this in any way... |
yeah consistent on re-runs
just pull down latest (after 0.25 release) and got a new error added to the set
these failures are all on 'test:karma-raw' so maybe some issue with browser comms? |
@kumavis closing this one. If you manage to replicate this issue for us, I'm happy to reopen and tackle it :) |
Allows users to access these additional types and utilities without having to create an instance of the client first. resolves ipfs#902 BREAKING CHANGE: `ipfs.util.isIPFS` has moved to a static export and should be accessed via `const { isIPFS } = require('ipfs-http-client')`. The modules available under `ipfs.types.*` have also become static exports. `ipfs.util.crypto` has been removed as it is not a dependency of `ipfs-http-client` so reduces the bundle size. If you need to use libp2p crypto primitives then please see the [js-libp2p-crypto](https://github.com/libp2p/js-libp2p-crypto) project for info on how to use it in your project. Finally `ipfs.util.getEndpointConfig` is now a direct instance method, `ipfs.getEndpointConfig` License: MIT Signed-off-by: Alan Shaw <alan.shaw@protocol.ai>
on a fresh clone of master
The text was updated successfully, but these errors were encountered: