e2b-dev / e2b-dev/code-interpreter

Inconsistent Elements Data in Charts When All Values Are Equal

Open
#104 1 comment 0 reactions 1 assignee View on GitHub

@mishushakov is already working on this.

Since May 19, 2025.

bug Code Interpreter
Dominant language
Python
Stars
2.4k
Forks
228
Avg merge
48m
Merged PRs (30d)
5

Description

I encountered an issue when generating a bar chart using the provided code. When all the values in the incident_counts list are equal, the elements data in the resulting chart object is incorrect. Specifically, the label and value attributes of the elements are not as expected. The value is always fixed at 0.8, which does not match the actual data.
Steps to Reproduce:
Run the following code to generate a bar chart:
Python
复制
import matplotlib.pyplot as plt

Data for the supplier locations and incident counts

supplier_locations = [
"aa",
"bb",
"cc",
"dd",
"ee",
"44"]

incident_counts = [2, 2, 2, 2,2,2]

Create a bar chart

plt.figure(figsize=(10, 6))
plt.plot(supplier_locations, incident_counts, color='blue')
plt.xlabel('Supplier Location ID')
plt.ylabel('Incident Count')
plt.title('Incident Counts by Supplier Location')
plt.xticks(rotation=45, ha="right")
plt.tight_layout()

Store the result for testing or further analysis

result = plt.gcf()
Inspect the elements data of the chart object. You will notice that the label and value attributes are incorrect. The value is always 0.8, regardless of the actual data.
Expected Behavior:
When all the values in the incident_counts list are equal, the elements data in the chart object should still accurately reflect the actual data. The label should correspond to the supplier locations, and the value should match the incident counts.
Actual Behavior:
The elements data is incorrect. The label and value attributes are not as expected. The value is always fixed at 0.8.
Additional Information:
This issue only occurs when all the values in the incident_counts list are equal.
When the values are not all equal, the elements data is correct.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.