-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
references to "undefined" in webUI #47
Comments
I don't quite understand the situation you're describing. I suspect it might be that the UI is having difficulty displaying certain variables, which usually happens when the UI tries to display multimodal variables with extended Markdown syntax. It would be best to have logs for reference. |
fixed! just an error due to my lack of familiarity with js. You can get the fixed version on latest master branch. |
Can I assume therefore that the agent is assigning internal variables to some of these things? Presumably to track their values and standardize their usage? How are those used? Just curious. |
This error was simply caused by me using incorrect js syntax when rendering the codespan. However, what you're curious about also exists in AIlice: code blocks marked with triple backticks will be automatically defined as variables, allowing agents to quickly reference these codes without needing to copy them. This will become apparent when you let AIlice program and run the code. The coder-proxy usually has the coder write the code, and after the coder returns the code block, the coder-proxy directly references a randomly named variable to execute or save the code. In fact, the system automatically parses the code block returned by the coder and saves it as a randomly named variable. You can see the related code in core/AConversation.py:18-26. |
The agent appears to have assigned labels to various symbols correctly, since it references those symbols by name in the console log.
But in the web UI it will refer to those same symbols as "undefined".
I would post a screenshot but I assume you know what I mean already.
The text was updated successfully, but these errors were encountered: