AI Prompts for Extract Full Error Stack Trace

Please provide the complete error message from the last build attempt, including the specific error type and the line number it references. This information is crucial for diagnosing the issue accurately. After quoting the error message, summarize what was expected versus what was actually produced based on the error details.

Please analyze the following build error output: [BUILD ERROR OUTPUT]. Ensure that you include all lines of the stack trace, as this will provide the complete context needed to identify the root cause of the issue. After your analysis, summarize the key points and suggest potential solutions or next steps to resolve the error.

Please provide a detailed explanation of your understanding of the last instruction executed in relation to the error encountered during the build process. Include any specific details about the error message, what you believe went wrong, and any relevant context that may help clarify the situation. This will assist in diagnosing the issue more effectively.

Please provide a structured comparison of the expected error message versus the actual output received for the error scenario titled 'bolt-not-reading-full-error-stack'. Include details on what the correct error handling should look like in this case. Format your response with clear headings for 'Expected Behavior', 'Actual Output', and 'Recommended Error Handling', and provide specific examples for each section.

Please analyze the last operation and identify the specific rule or constraint that was violated. Quote the exact clause that was not adhered to during the execution, and provide a brief explanation of how this violation occurred. Format your response by clearly stating the violated rule, followed by the quoted clause and the explanation.

Please modify the error logging function in [FILE] at line [LINE] to ensure it captures the full stack trace of errors. The current implementation only logs the first line of the error message. Update the function to log the entire error object, including the stack trace, and provide a brief explanation of how this change improves error tracking and debugging.

Rewrite the error handling logic in the file [FILE] at line [LINE]. Include a catch-all mechanism for unhandled exceptions that logs the complete error stack. Additionally, provide a brief explanation of how this change improves diagnostics and suggest any best practices for error handling in this context.

Change the error reporting mechanism in [FILE]:[LINE] to utilize a more verbose logging level. Ensure that the updated logging captures all relevant details during failures, including error messages, stack traces, and any contextual information that may help in diagnosing the issue. Provide a summary of the changes made and the expected impact on error reporting in the system.

Please implement a format enforcement rule in the error handling system that ensures the full stack trace is included in all error messages. The stack trace should be formatted to include the file name and line number, specifically in the format [FILE]:[LINE]. Additionally, provide a brief explanation of how this change will improve error tracking and debugging processes.

Please verify the dependency listed in [FILE] at [LINE] that is responsible for error handling. Confirm that it is up to date and functioning correctly to capture full stack traces as intended. Provide a summary of your findings, including any necessary updates or changes needed to ensure proper error handling.

Please execute a test build for the issue related to [USE-CASE] and capture the full error output. Ensure that the stack trace is complete and includes all relevant lines. After capturing the output, summarize the findings and indicate whether the resolution has been verified or if further investigation is needed.

Display the differences in the error handling logic changes made in the codebase. Specifically, highlight the modifications that ensure the full stack trace is logged. Present the output in a clear format that shows both the original and modified lines of code, along with a brief explanation of why these changes were necessary to meet the requirements.

Replay the original scenario that triggered the error related to [ERROR TYPE] in [APPLICATION NAME]. Carefully observe whether the full stack trace is now being captured and displayed correctly. Provide a detailed report on any discrepancies or improvements noted compared to the previous behavior, including specific examples of the stack trace output.

Please test an edge case related to error reporting in the system. Specifically, verify that when an error occurs, the full stack trace is logged correctly. After conducting the test, provide a detailed report that includes the output generated, any discrepancies from the expected results, and suggestions for improvements if the output does not meet the expectations.

Please verify the state of the error handling file located at [FILE]. Check that it accurately reflects the modifications made and confirm that it is functioning correctly without any issues. Provide a summary of your findings, including any discrepancies or areas that may require further attention.

Before any build, ensure that error logging captures the full stack trace. If the stack trace is truncated, stop the build and alert the developer. Provide a detailed explanation of why capturing the full stack trace is essential for debugging, and outline best practices for implementing effective error logging in the development process. Include examples of common pitfalls to avoid and how to set up alerts for developers.

Create a conversation-starter template for error handling in builds. Include the following points: always log the full stack trace when handling errors, and if only the first line of the stack trace is logged, alert the developer immediately. Format this template as a checklist with clear instructions for each point, ensuring it is easy to follow and implement.

Draft a project specification message for the error reporting system that clearly states the requirement for error handling. The message should include: "All error handling must include full stack traces in logs. This is mandatory for debugging purposes." Additionally, explain the importance of this requirement in ensuring efficient debugging and maintaining system reliability. Format the message in a professional tone suitable for a project documentation.

Please create a naming convention for error handling functions that clearly indicates they capture complete error information. All error handlers should be prefixed with 'LOGFULLSTACK_' to maintain consistency. Provide examples of how this naming convention can be applied in different scenarios, and explain the importance of using this format for clarity and maintainability in code.

Please create a self-check request for the agent that ensures proper error handling. The request should state: 'Before executing any build, verify that all error handling functions are logging the full stack trace. If not, stop the build.' Ensure the text is clear and concise, and provide any additional context or instructions that may help the agent understand the importance of this check.