Provider Agent - issues

[nieznanysprawiciel]

• Should retrieve confirmed agreements from market API on start.
• Consider how should we handle lost connection with yagna daemon (activity, payments)
• Provider should return early with when app key is wrong
• Provider should display warning on ctrl-c about breaking agreement(s).
• Consider communication between ya-provider and external apps (GUI, CLI...) https://github.com/golemfactory/yagna/wiki/Provider-Agent-issues
• Use datadir for yagna provider, preserving .env functionality in comfortable way.
• Provider does not validate agreement contents before approval:
  • Provider shall not approve the agreement for which expire date is already passed
• Configure debit note issuance interval
• Provider says: Can't create activity for not my agreement [CreateActivity { activity_id: "56f25eb147854a97b39604dd458ab518", agreement_id: "ad483e42-5285-4a8b-a031-b08e21fc4f5e" }] after Agreement expired before start.
  `

Side kicks:

• activity service seems to have bug on CreateActivity -- expired agreement results in 500 on ya-requestor on exec
• ya-requestor does not check agreement expiration. Consider if it should or it is ok...
• exe-unit results with 0 exit-code after being SIGTERM'ed during ExeScript processing...