c327f622f3
A websocket dial may hand for an unreasonably long time and a nostr client has no control over this when trying to connect to a relay. Go started introducing context in networking since 2014 - see https://go.dev/blog/context - and by now many net functions have XxxContext equivalent, such as DialContext. Example usage of the change introduced by this commit: ctx, cancel := context.WithTimeout(context.Background(), 3*time.Second) defer cancel() r, err := nostr.RelayConnectContext(ctx, "ws://relay.example.org") The code above makes RelayConnectContext last at most 3 sec, returning an error if a connection cannot be established in the given time. This helps whenever a tight control over connection latency is required, such as distributed systems. The change is backwards-compatible except the case where RelayPool.Add sent an error over the returned channel without actually closing said channel. I believe it was a bug.
25 lines
900 B
Modula-2
25 lines
900 B
Modula-2
module github.com/nbd-wtf/go-nostr
|
|
|
|
go 1.18
|
|
|
|
require (
|
|
github.com/SaveTheRbtz/generic-sync-map-go v0.0.0-20220414055132-a37292614db8
|
|
github.com/btcsuite/btcd v0.22.1
|
|
github.com/btcsuite/btcd/btcec/v2 v2.2.0
|
|
github.com/gorilla/websocket v1.4.2
|
|
github.com/tyler-smith/go-bip32 v1.0.0
|
|
github.com/tyler-smith/go-bip39 v1.1.0
|
|
github.com/valyala/fastjson v1.6.3
|
|
golang.org/x/exp v0.0.0-20221106115401-f9659909a136
|
|
golang.org/x/net v0.0.0-20190404232315-eb5bcb51f2a3
|
|
)
|
|
|
|
require (
|
|
github.com/FactomProject/basen v0.0.0-20150613233007-fe3947df716e // indirect
|
|
github.com/FactomProject/btcutilecc v0.0.0-20130527213604-d3a63a5752ec // indirect
|
|
github.com/btcsuite/btcd/chaincfg/chainhash v1.0.1 // indirect
|
|
github.com/decred/dcrd/crypto/blake256 v1.0.0 // indirect
|
|
github.com/decred/dcrd/dcrec/secp256k1/v4 v4.0.1 // indirect
|
|
golang.org/x/crypto v0.0.0-20200622213623-75b288015ac9 // indirect
|
|
)
|