!ujrhtmeIGtusHvGHbp:ipfs.io

ip-js

1452 Members
Channel for those working on the JS side of the interplanetary stack (e.g, IPFS, libp2p, IPLD). Bridged to #ip-js in IPFS Discord and Filecoin Slack.3 Servers

Load older messages


SenderMessageTime
26 Feb 2024
@_discord_1126394030008320080:ipfs.iojoelclark6547 joined the room.12:26:49
@_discord_969104118142615582:ipfs.ioimmccn123 joined the room.14:13:08
@_discord_531813989966151690:ipfs.iofacepunch.com joined the room.14:39:28
@_discord_1024701829663182889:ipfs.iov.i.p_leader joined the room.14:49:46
@_slack_filecoinproject_U015951Q5GS:ipfs.ioachingbrain We have tests for the isPinned method here - https://github.com/ipfs/helia/blob/main/packages/utils/test/pins.spec.ts Could you open a PR with a test similar to the above that fails? 15:25:21
@_slack_filecoinproject_U015951Q5GS:ipfs.ioachingbrain The pseudo code above looks a bit off because:
// 'hello world' needs to be a Uint8Array
await helia.blockstore.put(block.cid, 'hello world')
// pins.add returns an async generator so needs to be consumed somehow - this is new as of early January - https://github.com/ipfs/helia/pull/231
await helia.pins.add(block.cid)
15:28:24
@_slack_filecoinproject_U061ZESM69L:ipfs.ioHayden Thanks. Iterating the add generator now pins the cid. Am I correct in assuming the actual pinning is done when iterating the generator? Also, what impact does this have on users using Helia pre-January? will we need to guard against this when we call helia.pins.add() against older versions of Helia? 18:17:01
@_discord_773016815466184704:ipfs.iorachelg.eth joined the room.19:14:08
@_discord_567803018775625753:ipfs.iomarstonc joined the room.20:30:38
27 Feb 2024
@_discord_737349785207701544:ipfs.ioshacqeal joined the room.00:19:52
@_discord_950706156295303189:ipfs.io_unknown_name_0 joined the room.07:21:02
@_slack_filecoinproject_U015951Q5GS:ipfs.ioachingbrain Aha, great. The API change is covered in the upgrade guide for Helia 2.x.x to 3.x.x, which is linked to from the release notes - that and the types changing should be enough? I would definitely encourage people to read the guides when migrating between majors! 09:32:19
@_discord_486488902840877057:ipfs.iocaliginoustenebrae joined the room.12:01:28
@_slack_filecoinproject_U061ZESM69L:ipfs.ioHayden Thanks for the confirmation. And when a peer replicates the block of another peer that is pinned, does it pin it on the replicating peer? Or do I need to explicitly pin it on the replicating peer? 12:49:46
@_discord_1014768299831197736:ipfs.iojerrylove0605 joined the room.12:54:30
@_slack_filecoinproject_U015951Q5GS:ipfs.ioachingbrain You would need to pin it, yes - this will also walk the dag beneath the pinned CID and ensure that all blocks are present on the pinning node 12:57:45
@_discord_819851334248431626:ipfs.io0hash joined the room.13:00:27
@_slack_filecoinproject_U061ZESM69L:ipfs.ioHayden Is there a way to automatically pin items on the replicating peer? I.e. can this be configured with createHelia()? 13:04:46
@_slack_filecoinproject_U015951Q5GS:ipfs.ioachingbrain Not by config, not - you would have to pin the items using the pinning API after starting a node 16:11:16
@_discord_1142753554575142968:ipfs.iookon0913_58308 joined the room.16:13:35
@_slack_filecoinproject_U061ZESM69L:ipfs.ioHayden Got it. What about a way to add an event listener to, say, blockstore.add/del to pin/unpin when the add/del event fires? What I'm trying to do is lean on Helia to handle the pinning when my replicating peer fetches a remote block. 16:36:40
@_discord_518921366184001557:ipfs.iovoxelqueen joined the room.16:45:37
@_discord_754819433037561926:ipfs.iocarlos.santos joined the room.16:48:52
@_discord_837805436371599421:ipfs.iovoyager_666. joined the room.21:40:51
28 Feb 2024
@_discord_1194846149702582282:ipfs.ioshwurz changed their display name from syberstein to shwurz#0.03:13:41
@_discord_1194846149702582282:ipfs.ioshwurz changed their display name from shwurz#0 to shwurz.03:13:46
@_discord_1212244213866168361:ipfs.iomobly_83662_69271 joined the room.03:54:30
@_discord_1133874426828570777:ipfs.ioakak1439 changed their display name from gogo1439 to akak1439#0.06:48:22
@_discord_1133874426828570777:ipfs.ioakak1439 changed their profile picture.06:48:28
@_discord_1133874426828570777:ipfs.ioakak1439 changed their display name from akak1439#0 to akak1439.06:48:31

There are no newer messages yet.


Back to Room ListRoom Version: 10