profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/Stebalien/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

filecoin-project/venus 1874

Filecoin Full Node Implementation in Go

filecoin-project/FIPs 108

The Filecoin Improvement Proposal repository

filecoin-project/go-fil-markets 46

Shared Implementation of Storage and Retrieval Markets for Filecoin Node Implementations

benweissmann/zephyr-mobile 6

Zephyr Mobile Application for Android

filecoin-project/fvm-project 5

⚙️ home of the FVM (Filecoin Virtual Machine) project

gxed/ansi 0

Small, fast library to create ANSI colored strings and codes. [go, golang]

gxed/aws-sdk-go 0

AWS SDK for the Go programming language.

gxed/backoff 0

The exponential backoff algorithm in Go (Golang).

issue commentipfs/go-ipfs

Multipart reader regression in go 1.17

Uh, yes, you're right. And it might be a bug, or they might be getting more strict.

Stebalien

comment created time in 6 hours

issue commentipfs/go-ipfs

Multipart reader regression in go 1.17

Confirm this only manifests with go 1.17 and if so release with 1.16.

The CI passes with 1.17 but not with 1.16, so I believe we can consider this confirmed. But yeah, we can just not use 1.17 when we release.

Stebalien

comment created time in 7 hours

PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent

issue commentipfs/go-ipfs

Partial pinning progress is not preserved well.

The two pin operations take different paths through the graph. For performance, we don't bother making it deterministic.

skliarie

comment created time in 16 hours

issue commentlibp2p/go-libp2p

flaky mDNS test: TestOtherDiscovery

@cbegin please file a new bug.

marten-seemann

comment created time in 16 hours

issue commentipfs/in-web-browsers

WebDAV (HTTP Extensions for Distributed Authoring)

Note: it should be pretty easy to implement: https://pkg.go.dev/golang.org/x/net/webdav

lidel

comment created time in 16 hours

PullRequestReviewEvent

issue closedipfs/ipfs-webui

Add option for `--nocopy` flag for importing files in the web UI if it detects `filestore` is enabled in the config

Is your feature request related to a problem? Please describe. I cannot import files using the --nocopy from flag from the web UI.

Describe the solution you'd like If Experimental.FilestoreEnabled is set to true in the go-ipfs config, there should be a check mark when importing files that uses the --nocopy flag to ensure the file is not duplicated.

Describe alternatives you've considered The alternative solution has been using the command line; ipfs files cp /ipfs/$(ipfs add -Q --nocopy <local-file>) "/<dest-name>"

closed time in 16 hours

AccessViolation95

issue commentipfs/ipfs-webui

Add option for `--nocopy` flag for importing files in the web UI if it detects `filestore` is enabled in the config

Unfortunately, this isn't possible. For security reasons, the browser won't tell the WebUI where the files live on-disk.

If you need the Filestore, you'll need to use the CLI.

AccessViolation95

comment created time in 16 hours

issue openedipfs/go-ipfs

Multipart reader regression in go 1.17

Checklist

Installation method

built from source

Version

No response

Config

No response

Description

See the test failure in https://github.com/ipfs/go-ipfs-files/pull/40:

--- FAIL: TestMultipartFiles (0.00s)
    helpers_test.go:122: [2] found end of directory, expected files.Event{kind:0, name:"nested", value:"some content"}
FAIL
FAIL	github.com/ipfs/go-ipfs-files	0.007s
FAIL

This isn't a flake so something is going wrong. I'm not sure if this affects production, but we should figure it out before releasing.

created time in 16 hours

issue closedipfs/go-ds-s3

Sharding?

By default, go-ipfs provides a sharding option for the datastore. When using this plugin the datastore is not being sharded.

As described in previous issues, the serialization in the datastore_spec is not 1:1 because when I try to add shardFunc this results in an error.

Is there a way to achieve sharding for the data stored in S3?

closed time in 16 hours

v-stickykeys
PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent

pull request commentipfs/go-ipfs

Make variadic false for `ipfs files rm`

This should definitely support multiple. Mind changing it to loop over the Arguments instead of just picking off the first one?

AyumuKasuga

comment created time in 16 hours

issue closedipfs/ipget

ipget automatically saving and exiting session upon opening program, unable to input any commands

<!-- I have installed ipget on a Mac. As soon as I open ipget, the terminal automatically exits the session and freezes command inputs. See image. How do I bypass this or prevent it?

Screen Shot 2021-09-16 at 10 00 13 AM

Thanks in advance! -->

closed time in 16 hours

YeOldGit

issue commentipfs/ipget

ipget automatically saving and exiting session upon opening program, unable to input any commands

ipget is a command line tool. You need to execute it from a terminal, not by double clicking on the executable. You probably want https://docs.ipfs.io/install/ipfs-desktop/.

YeOldGit

comment created time in 16 hours

PullRequestReviewEvent
PullRequestReviewEvent

issue commentipfs/go-ds-s3

Sharding?

Specifically, the flatfs (flat-file backed datastore) provides a sharding option because some filesystems don't handle large directories very well. None of the other datastores provide such an option.

Honestly, sharding just doesn't make sense in S3 and would massively complicate the query logic.

v-stickykeys

comment created time in a day

PullRequestReviewEvent
PullRequestReviewEvent

Pull request review commentlibp2p/go-libp2p

fix flaky TestEndToEndSimConnect holepunching test

 func TestEndToEndSimConnect(t *testing.T) { 	ensureDirectConn(t, h1, h2) 	// ensure no hole-punching streams are open on either side 	ensureNoHolePunchingStream(t, h1, h2)-	events := tr.getEvents()-	require.Len(t, events, 3)+	var events []*holepunch.Event+	require.Eventually(t, func() bool { events = tr.getEvents(); return len(events) == 3 }, time.Second, 10*time.Millisecond)

This line is getting a bit long...

marten-seemann

comment created time in 2 days

PullRequestReviewEvent
PullRequestReviewEvent

pull request commentlibp2p/go-libp2p

remove legacy mDNS implementation

Is there any reason not to leave this around for a while?

marten-seemann

comment created time in 2 days

PullRequestReviewEvent

Pull request review commentlibp2p/go-libp2p-nat

stop using goprocess for shutdown

 func (nat *NAT) NewMapping(protocol string, port int) (Mapping, error) { 	}  	m := &mapping{-		intport: port,-		nat:     nat,-		proto:   protocol,+		intport:  port,+		nat:      nat,+		proto:    protocol,+		teardown: nat.removeMapping, 	} -	m.proc = goprocess.WithTeardown(func() error {-		nat.rmMapping(m)-		nat.natmu.Lock()-		defer nat.natmu.Unlock()-		nat.nat.DeletePortMapping(m.Protocol(), m.InternalPort())-		return nil-	})--	nat.addMapping(m)--	m.proc.AddChild(periodic.Every(MappingDuration/3, func(worker goprocess.Process) {-		nat.establishMapping(m)-	}))+	nat.mappingmu.Lock()+	if nat.closed {+		nat.mappingmu.Unlock()+		return nil, errors.New("closed")+	}+	nat.mappings[m] = struct{}{}+	nat.refCount.Add(1)+	nat.mappingmu.Unlock()+	go nat.refreshMappings(m)

If it's not too difficult, it would be nice to have a single worker loop to handle refreshing mappings.

marten-seemann

comment created time in 2 days