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.

Sign up for GitHub

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

Jump to bottom

No-offers warning message mentions 30 instead of 180 minutes #581

Closed
azawlocki opened this issue Aug 6, 2021 · 0 comments · Fixed by #582
Closed

No-offers warning message mentions 30 instead of 180 minutes #581

azawlocki opened this issue Aug 6, 2021 · 0 comments · Fixed by #582
Assignees
@azawlocki
Labels
beta.2.patch.3

Comments

@azawlocki
Copy link
Contributor

Yapapi currently prints this warning:

[2021-08-06T16:01:08.819+0200 WARNING yapapi.summary] Expiration time for your tasks is set to 1 min from now. Providers may not be willing to take up tasks which expire sooner than 5 min or later than 180 min, counting from the moment they get your demand.
[2021-08-06T16:01:28.820+0200 WARNING yapapi.summary] 2 offers have been collected from the market, but no provider has responded for 20s. Make sure you're using the latest released versions of yagna and yapapi, and the correct subnet. Also make sure that the timeout for computing all tasks is within the 5 min to 30 min range.

The last 30 min should be 180 min.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@azawlocki azawlocki

Labels
beta.2.patch.3
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix upper bound for expiration time in no-offers warning golemfactory/yapapi
1 participant
@azawlocki