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
When running the command: tibanna log --job-id=JOBIDHERE, I get the message: log/postrunjson file is not ready yet.Wait a few seconds/minutes and try again. which I understand is expected behavior. However, I get this message on log files I have already viewed previously. I am not sure if this is a client-side error or not, but I did not expect to see this message for log files I have previously viewed. Thank you!
The text was updated successfully, but these errors were encountered:
It should work on previously viewed files. I can think of a couple of possible scenarios.
the log/postrunjson file on s3 has been deleted manually (Tibanna does not delete them). This can be checked by either awscli (aws s3 ls s3://<logbucket>/<jobid>.log) or checking the S3 bucket on the browser.
multiple step functions are being used and the job was run on a step function different from the currently set TIBANNA_DEFAULT_STEP_FUNCTION_NAME. In this case, tibanna log --job-id=<jobid> --sfn=<stepfunctionname> should work.
When running the command:
tibanna log --job-id=JOBIDHERE
, I get the message:log/postrunjson file is not ready yet.Wait a few seconds/minutes and try again.
which I understand is expected behavior. However, I get this message on log files I have already viewed previously. I am not sure if this is a client-side error or not, but I did not expect to see this message for log files I have previously viewed. Thank you!The text was updated successfully, but these errors were encountered: