When process killed, we should use $ --status to detect fail (in this case telegram bot was alive, and it not reported fail).
Even if telegram bot killed, we should detect restart. And if after bot start we have commands in $, we should try to resume them, if they started before bot start time.
We need to make sure we have in all places start and end time, or start time without end time if everything is killed. All our logs, should write time, so we will be able to catch exact moment of such total failure.
We also need to make sure we don't destroy our previous log, so we can find out last time the telegram bot was active, so we only try to restore and resume /solve commands, that were executing when last telegram bot statement were written. We also need to have backup of all previous logs of telegram bot, so no overrides (no data should be destroyed).
We need to download all logs and data related about the issue to this repository, make sure we compile that data to ./docs/case-studies/issue-{id} folder, and use it to do deep case study analysis (also make sure to search online for additional facts and data), in which we will reconstruct timeline/sequence of events, list of each and all requirements from the issue, find root causes of the each problem, and propose possible solutions and solution plans for each requirement (we should also check known existing components/libraries, that solve similar problem or can help in solutions).
If there is not enough data to find actual root cause, add debug output and verbose mode if not present, that will allow us to find root cause on next iteration.
If issue related to any other repository/project, where we can report issues on GitHub, please do so. Each issue must contain reproducible examples, workarounds and suggestions for fix the issue in code. Also double check to fully apply requirements to entire codebase, so if we have issue in multiple places, it should be fixed in all them.
Please plan and execute everything in this single pull request, you have unlimited time and context, as context auto-compacts and you can continue indefinitely, until it is each and every requirement fully addressed, and everything is totally done.
When process killed, we should use
$ --statusto detect fail (in this case telegram bot was alive, and it not reported fail).Even if telegram bot killed, we should detect restart. And if after bot start we have commands in $, we should try to resume them, if they started before bot start time.
We need to make sure we have in all places start and end time, or start time without end time if everything is killed. All our logs, should write time, so we will be able to catch exact moment of such total failure.
We also need to make sure we don't destroy our previous log, so we can find out last time the telegram bot was active, so we only try to restore and resume /solve commands, that were executing when last telegram bot statement were written. We also need to have backup of all previous logs of telegram bot, so no overrides (no data should be destroyed).
We need to download all logs and data related about the issue to this repository, make sure we compile that data to
./docs/case-studies/issue-{id}folder, and use it to do deep case study analysis (also make sure to search online for additional facts and data), in which we will reconstruct timeline/sequence of events, list of each and all requirements from the issue, find root causes of the each problem, and propose possible solutions and solution plans for each requirement (we should also check known existing components/libraries, that solve similar problem or can help in solutions).If there is not enough data to find actual root cause, add debug output and verbose mode if not present, that will allow us to find root cause on next iteration.
If issue related to any other repository/project, where we can report issues on GitHub, please do so. Each issue must contain reproducible examples, workarounds and suggestions for fix the issue in code. Also double check to fully apply requirements to entire codebase, so if we have issue in multiple places, it should be fixed in all them.
Please plan and execute everything in this single pull request, you have unlimited time and context, as context auto-compacts and you can continue indefinitely, until it is each and every requirement fully addressed, and everything is totally done.