For example we can just have links to issues like we have
▶️ uselessgoddess/ryzr#3 (processing, 2h 14m 16s)
▶️ link-foundation/box#99 (processing, 53m 52s)
▶️ link-assistant/hive-mind#1886 (processing, 51m 50s)
▶️ link-assistant/hive-mind#1885 (processing, 50m 30s)
But if we split processing and pending, that will help us make it more compact (with links as now):
• uselessgoddess/ryzr#3 (▶️ 2h 14m 16s)
• link-foundation/box#99 (▶️ 53m 52s)
• link-assistant/hive-mind#1886 (▶️ 51m 50s)
• link-assistant/hive-mind#1885 (▶️ 50m 30s)
For example list of processing/executing can be shown like this.
Waiting/pending does not need to show waiting reason, it usually all the same for all of them. And in the queue we need to have just a list, and emoji + time of wait to be short.
We should also try to fit more data (it will be fine if it does not fit in one message, we can split it by our universal message sending method, split should be done by lines, without breaking the markdown (expecially code blocks), so if we split code block it should be correctly at the end of one message and at the start of next, and language repeated if specified, add lots of tests for that).
And we don't need to show empty queues.
So please make the viewing experience and our sending messages experience across the codebase perfect.
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.
For example we can just have links to issues like we have
But if we split processing and pending, that will help us make it more compact (with links as now):
For example list of processing/executing can be shown like this.
Waiting/pending does not need to show waiting reason, it usually all the same for all of them. And in the queue we need to have just a list, and emoji + time of wait to be short.
We should also try to fit more data (it will be fine if it does not fit in one message, we can split it by our universal message sending method, split should be done by lines, without breaking the markdown (expecially code blocks), so if we split code block it should be correctly at the end of one message and at the start of next, and language repeated if specified, add lots of tests for that).
And we don't need to show empty queues.
So please make the viewing experience and our sending messages experience across the codebase perfect.
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.