-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[ipfs-core] - Exception is raised when attempting to releaseLock #3520
Comments
Do you have a small example project I can use to reproduce this problem? |
@achingbrain I will be very happy to provide an example however : |
Linking to the minified code in your project is fine, I can always swap it out locally to see if the error still occurs. |
Chrome Version 88.0.4324.150 (Official Build) (64-bit) https://dweb.link/ipfs/bafybeiguy3u45vc2i5ojlhmqfffpvxpfrcs4nq7ov6ez7kj7vbzmfuvx4m Load IPFS with TiddlyWiki with the previous link. At the very top:
You are going to save over ipfs.infura.io:5001 and load the new wiki from dweb.link. While saving the exception is raised multiple times. Thanks |
This exception is raised and catched as infura do not allow files.stat. The
program flow should not be disturbed. No authentication is required. Did
you get the exception I detailed? Thanks
…On Wed, 24 Feb 2021, 19:49 Alex Potsides, ***@***.***> wrote:
Do I need to be authenticated at all? I've followed your instructions but
get a 403 when it tries to do an ipfs.files.stat:
[image: image]
<https://user-images.githubusercontent.com/665810/109013590-41c75600-76ab-11eb-8132-9db76764a054.png>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3520 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE47PBCEX6VYU2W6WP4ZRV3TAUDIBANCNFSM4XAJ2ACA>
.
|
It looks like the application is invoking this here: https://github.com/xmaysonnave/tiddlywiki-ipfs/blob/73038b5b41d1675848a978207f4b53c3f1c2a316/core/modules/library/ipfs-bundle/ipfs-library.js#L372 called from here: https://github.com/xmaysonnave/tiddlywiki-ipfs/blob/73038b5b41d1675848a978207f4b53c3f1c2a316/core/modules/library/ipfs-bundle.js#L426 You may need to refactor your application to only use APIs that infura allow.
No, only what I pasted above. |
The exception remains in the latest however with Chrome Developer Tools the 'Pause on Exceptions' should be selected (the 'Pause on caught exception' should be unchecked) This exception is handled by Chrome though and do not seem to cause any trouble if Pause on Exceptions is unchecked. Here is an updated link of IPFS with TiddlyWiki Thanks |
js-ipfs is being deprecated in favor of Helia. You can #4336 and read the migration guide. Please feel to reopen with any comments by 2023-06-02. We will do a final pass on reopened issues afterward (see #4336). This issue won't be fixed in js-ipfs but there is replacement functionality available in kubo-rpc-client that should work much better. |
Environment
Severity:
Medium, while debugging Chrome always complain even the 'Pause on caught exceptions' is unchecked
Description:
ipfs-http-client dynamically downloaded from jsdelivr
https://cdn.jsdelivr.net/npm/ipfs-http-client@49.0.1/dist/index.min.js
Component
ipfs-core/src/runtime/preload-brower.js
Chrome Developper tools is open.
The following exception is triggered in the finally close while attempting to release the reader lock (line 32)
TypeError: This readable stream reader has been released and cannot be used to monitor the stream's state
Thanks
The text was updated successfully, but these errors were encountered: