Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Providers will probably not respond to tasks which expire sooner than 5 min or later than 30 min #109

Closed
cryptobench opened this issue May 25, 2021 · 2 comments · Fixed by golemfactory/yapapi#416

Comments

@cryptobench
Copy link
Member

Yapapi still prints out:
WARNING yapapi.summary] Expiration time for your tasks is set to 119 min 59 sec from now. Providers will probably not respond to tasks which expire sooner than 5 min or later than 30 min, counting from the moment they get your demand. Use the timeoutparameter toExecutor()to adjust the timeout.
when requesting a task on the network. AFAIK the limit has been raised from 30 minutes to 3 hours.

@jiivan
Copy link

jiivan commented May 27, 2021

https://github.com/golemfactory/yagna/blob/830288196bff943f8819a633041acf55fe78fbf5/agent/provider/src/market/negotiator/factory.rs#L18-L29

Current values in master, 0.6.7-beta.1 and pre-rel-0.7.0 are: 5 minutes to 3 hours. (unless modified by env)

@tworec
Copy link

tworec commented May 27, 2021

Using debit note keep alive feature is needed. If one does not use it, the upper bound is 30mins.

https://github.com/golemfactory/yagna/blob/830288196bff943f8819a633041acf55fe78fbf5/agent/provider/src/market/negotiator/factory.rs#L25-L26

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants