Way to handle doom loop coding
I've been running into an issue repeatedly letting Firebase Studio AI try to fix an error that it keeps re-detecting. It acknowledges that it's a persistent issue, but none of the fixes seem to work. I'm not sure how to fix it either. Maybe it would be good to have a way for the AI at some point engage human support on the Google side? Or maybe open up for a request to identify and investigate problems the AI seems to be struggling with?
Here's the particular error in this instance:
"Runtime Error
Error: ./nodemodules/@opentelemetry/sdk-trace-node/nodemodules/@opentelemetry/context-async-hooks/build/src/AsyncHooksContextManager.js:20:20
Module not found: Can't resolve 'asynchooks'
18 | exports.AsyncHooksContextManager = void 0;
19 | const api1 = require("@opentelemetry/api");
20 | const asyncHooks = require("asynchooks");
| ^^^^^^^^^^^^^^^^^^^^^^
21 | const AbstractAsyncHooksContextManager1 = require("./AbstractAsyncHooksContextManager");
22 | class AsyncHooksContextManager extends AbstractAsyncHooksContextManager_1.AbstractAsyncHooksContextManager {
23 | constructor() {..."
Daniel James
shared this idea
Thank you so much for taking the time to share your idea with us and for participating in our community.
Because we have officially announced the sunsetting of Firebase Studio and are currently focusing on the migration process, we are no longer accepting or implementing new feature requests for this product.
We appreciate your support and understanding as we transition to our next chapter.