[Bug]: Working Custom Widget Started Failing After Latest Release.
Issue Summary
After the latest release, our custom widget started failing, resulting in a blank widget. We investigated the issue and discovered that it was caused by the Layout
component from Ant Design. Replacing it with a simple div
element resolved the issue, but introduced a new error.
Description
The error occurred when rendering the custom widget, resulting in a blank widget. We investigated further and discovered that the issue was caused by the Layout
component from Ant Design. Replacing it with a simple div
element resolved the issue, but introduced a new error.
Steps to Reproduce
- Create a custom widget using the latest release.
- Render the widget in the application.
- Observe the blank widget.
Code Snippet
import React from 'https://cdn.jsdelivr.net/npm/react@18.2.0/+esm'
import reactDom from 'https://cdn.jsdelivr.net/npm/react-dom@18.2.0/+esm'
import Markdown from 'https://cdn.jsdelivr.net/npm/react-markdown@9.0.1/+esm';
import { Button, Input, Card, Tooltip } from 'https://cdn.jsdelivr.net/npm/antd@5.11.1/+esm'
// ...
const App = () => {
// ...
return (
<div className="h-screen relative">
<Navbar ticketId={ticketId} licenses={licenses} />
<div className="flex-grow overflow-y-auto p-2 bg-white">
<Messages messages={messages} loading={loading} />
</div>
<MessageForm value={currentMessage} onChange={setCurrentMessage} onSend={sendMessage} loading={loading} />
</div>
);
}
Model
{
"ticketId": ""
}
Environment
Production
Severity
High (Blocker to building or releasing)
Issue Video Log
No response
Version
1.64-snapshot
Debugging Steps
- Investigate the issue by reviewing the code and logs.
- Replace the
Layout
component with a simplediv
element. - Observe the new error and investigate its cause.
Resolution
Replacing the Layout
component with a simple div
element resolved the issue, but introduced a new error. Further investigation is required to resolve the new error.
Additional Information
- The issue occurred after the latest release.
- The custom widget was created using the latest release.
- The issue was caused by the
Layout
component from Ant Design. - Replacing the
Layout
component with a simplediv
element resolved the issue, but introduced a new error.
Q&A: Bug Report - Custom Widget Failing After Latest Release ===========================================================
Q: What is the issue with the custom widget?
A: The custom widget is failing to render, resulting in a blank widget. This issue occurred after the latest release.
Q: What is the cause of the issue?
A: The issue is caused by the Layout
component from Ant Design. Replacing it with a simple div
element resolves the issue, but introduces a new error.
Q: What is the new error that was introduced?
A: The new error is related to the rendering of the custom widget. Further investigation is required to resolve this error.
Q: What are the steps to reproduce the issue?
A: To reproduce the issue, follow these steps:
- Create a custom widget using the latest release.
- Render the widget in the application.
- Observe the blank widget.
Q: What is the environment in which the issue occurs?
A: The issue occurs in the production environment.
Q: What is the severity of the issue?
A: The issue is classified as high severity, as it is a blocker to building or releasing the application.
Q: Is there a video log of the issue?
A: No, there is no video log of the issue.
Q: What is the version of the application in which the issue occurs?
A: The issue occurs in version 1.64-snapshot.
Q: What are the debugging steps to resolve the issue?
A: To resolve the issue, follow these debugging steps:
- Investigate the issue by reviewing the code and logs.
- Replace the
Layout
component with a simplediv
element. - Observe the new error and investigate its cause.
Q: What is the resolution to the issue?
A: The resolution to the issue is to replace the Layout
component with a simple div
element. However, this introduces a new error that requires further investigation to resolve.
Q: Are there any additional information or resources that can help resolve the issue?
A: Yes, there are additional information and resources that can help resolve the issue. These include:
- The code snippet of the custom widget.
- The model used in the application.
- The environment in which the issue occurs.
- The severity of the issue.
- The version of the application in which the issue occurs.
By following these Q&A, you should be able to understand the issue, its cause, and the steps to resolve it.