AI Prompts for Resolving Infinite Loading States

Quote the exact output produced by the async function located in [FILE] at [LINE]. Then, compare this output to the expected result based on the function's intended behavior, and highlight any discrepancies that could explain why the function is not resolving as expected.

Paste the code for the async function located in [FILE]:[LINE]. Analyze the function's structure and identify any missing resolve or reject statements that could cause an infinite loading state. Additionally, provide suggestions for correcting these issues to ensure proper functionality.

Interpret the original instruction for the async code related to the use-case of BOLT-INFINITE-LOADING-STATE. Clearly outline your understanding of the expected behavior for this function, including any specific requirements or outcomes that were intended.

Compare the expected behavior of the async function with the actual behavior observed. Detail what the function was supposed to return, including specific values or outcomes, and contrast this with what it is currently returning. Include any discrepancies and potential reasons for these differences.

Identify and name the specific rule or constraint that was violated in the async function related to the bolt-infinite-loading-state. Quote the exact clause from the documentation that outlines the expected behavior for resolving promises, and explain how the violation impacts the overall functionality.

In the async function located at [FILE]:[LINE], add a resolve statement at the end to ensure the function completes successfully. Additionally, verify that the resolve is called only when the correct conditions are met, and provide a brief explanation of those conditions.

Rewrite the async function located in [FILE] at line [LINE] to incorporate explicit error handling. Ensure that the function rejects the promise with a specific error message that clearly explains the reason for the failure, and provide examples of potential errors that should be caught.

Modify the async function in [FILE]:[LINE] to improve the promise resolution logic. Ensure that the function correctly resolves or rejects the promise based on the specific execution path taken, and provide a brief explanation of the changes made and their impact on the overall functionality.

Check the async function in [FILE] at line [LINE] to ensure it adheres to the correct format for promises. Verify that both the resolve and reject functions are properly defined and invoked within the function, and provide suggestions for any necessary corrections.

Review the dependencies used in the async function located at [FILE]:[LINE]. Confirm that all necessary imports are included, check their compatibility with the async logic, and identify any potential issues that could affect performance or functionality. Provide suggestions for correcting any identified problems.

Execute the async function located in [FILE] at line [LINE]. Verify that it resolves successfully by checking the console for any errors, and confirm that the user interface updates as expected after the function completes.

Display the diff of the changes made to the async function in [FILE] at line [LINE]. Highlight the additions of the resolve and reject statements, and confirm that they are correctly implemented by providing a brief explanation of their purpose in the context of the function.

Recreate the scenario that previously caused the infinite loading state. Verify that the async function resolves correctly this time, and observe whether the UI behaves as expected without any loading issues.

Test the async function in [FILE]:[LINE] for edge cases to ensure it handles all potential inputs correctly. Specifically, verify that the function does not enter an infinite loading state when provided with edge case inputs, and document any scenarios where it fails to perform as expected.

Check the output of the async function located in [FILE] at [LINE] after implementing the fix. Verify that it returns the expected result and confirm that the user interface accurately reflects this change.

Write the exact session-opening constraint for this project using the following format: 'Before executing any async function, verify that all promises have a defined resolve and reject. If any promise is not resolved or rejected within [TIMEOUT], log an error and halt execution.' Provide the response in a format that is ready for direct pasting.

Create a conversation-starter template for handling errors in async functions. The template should include the following elements: a clear structure for capturing and logging exceptions, guidelines for ensuring all promises are resolved or rejected appropriately, and examples of common error scenarios that may arise. Provide the exact text of this template.

Draft a project specification message that outlines the requirements for async functions. Ensure the message states that "All async functions must include both resolve and reject statements. Any function that does not adhere to this will be flagged during code reviews." Include a brief introduction explaining the importance of these requirements in maintaining code quality.

Establish a naming convention for async functions in your codebase. All async functions must be prefixed with 'async_' to clearly indicate their behavior. Any function that does not follow this convention will be considered non-compliant. Please provide the exact text of this naming convention for documentation purposes.

Create a self-check request for the agent to ensure that before executing any async function, it verifies that all promises have a defined resolve and reject. If any promises do not meet this requirement, the agent should alert the developer immediately with a clear message indicating the issue. Provide the exact text for this self-check request.