You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The store request with hash now takes a few minutes, waku api should return an error if reached timeout, the timeout should be a few seconds, how about 10s?
Describe the bug The store request with hash now takes a few minutes, waku api should return an error if reached timeout, the timeout should be a few seconds, how about 10s?
sounds like a good idea, but i don't think this should be addressed in go-waku. The caller (status-go) can just create a context with timeout and pass it to store request which would then get handled automatically.
The context is already there so that caller will have a choice to decide timeout in such scenarios.
Describe the bug
The store request with hash now takes a few minutes, waku api should return an error if reached timeout, the timeout should be a few seconds, how about 10s?
Related to issue: status-im/status-go#5449
cc @richard-ramos @chaitanyaprem @plopezlpz
The text was updated successfully, but these errors were encountered: