yapapi
yapapi copied to clipboard
Password not found in yacat example
Name: kubam yagna version: yagna 0.8.0-rc5 (e9476c02 2021-09-08 build #170) OS+lang+version (if applicable): Linux, python 3.8.11 Title: Password not found on first run of the example
Task computed: Task(id=2, data=0), result:
[2021-09-16T12:48:13.706+0200 INFO yapapi.summary] [Job 2] Task finished by provider 'EBGolem-2', task data: 0
[2021-09-16T12:48:13.706+0200 INFO yapapi.summary] [Job 2] Task started on provider 'EBGolem-2', task data: 4096
Task computed: Task(id=3, data=4096), result:
[2021-09-16T12:48:14.195+0200 INFO yapapi.summary] [Job 2] Task finished by provider 'EBGolem-2', task data: 4096
[2021-09-16T12:48:14.196+0200 INFO yapapi.summary] [Job 2] Task started on provider 'EBGolem-2', task data: 8192
Task computed: Task(id=4, data=8192), result:
[2021-09-16T12:48:14.621+0200 INFO yapapi.summary] [Job 2] Task finished by provider 'EBGolem-2', task data: 8192
[2021-09-16T12:48:14.622+0200 INFO yapapi.summary] [Job 2] Computation finished in 7.0s
[2021-09-16T12:48:14.622+0200 INFO yapapi.summary] [Job 2] Negotiated 1 agreements with 1 provider
[2021-09-16T12:48:14.623+0200 INFO yapapi.summary] [Job 2] Provider 'EBGolem-2' computed 3 tasks
[2021-09-16T12:48:15.713+0200 INFO yapapi.executor] [Job 2] Waiting for Executor services to finish...
No password found
Total time: 0:00:25.954077
This happened also to other people during the testing session, and sometimes the password was found, we don't know any pattern when the password is found and when not. yapapi-2021.09.16_12.47.47.log yagna-log.zip
@shadeofblue are we investigating this for beta.3?
Might be connected -> https://www.notion.so/golemnetwork/beta-3-requestor-testing-session-4-e9f6c75cccdd45ce86f6d1cb33a981ec#3f0d6bf4c23548dc8c34c78e9eca4653
I will convert it to an issue at some point -> linking notion now
Is yajsapi
's yacat
example also tested? If it is tested and it always finds the password, you can compare both versions.
https://github.com/golemfactory/yajsapi/blob/b0.5/examples/yacat/yacat.ts
if the hashcat process fails with an error on provider's end, this error is not handled and yacat.py
just assumes correct execution that did not find the password -> thus, it doesn't re-schedule that task