Skip to content
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

Data Wrangler (often) doesn't get called when trying to open a DataFrame from other frames on the call stack #16026

Closed
danhje opened this issue Sep 9, 2024 · 0 comments · Fixed by #16057
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug triage-needed Issue needs to be triaged

Comments

@danhje
Copy link

danhje commented Sep 9, 2024

This bug was originally reported over at the DataWrangler repo (link), but they think the issue lies with the Jupyter extension.

Environment data

  • VS Code version: 1.92.2
  • Data Wrangler Extension version (available under the Extensions sidebar): v1.8.0
  • Jupyter Extension version (available under the Extensions sidebar): v2024.7.0
  • Python Extension version (available under the Extensions sidebar): v2024.14.0
  • OS (Windows | Mac | Linux distro) and version: Windows 11 with Ubuntu on WSL2
  • Pandas version: 2.2.2
  • Python and/or Anaconda version: 3.12
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): poetry venv

Expected behaviour

DataFrame opens in data view / Data Wrangler.

Actual behaviour

Nothing happens.

Steps to reproduce:

Put a breakpoint on the first return line of the following script, and run it in VS Code debugger.

import pandas as pd


def inner():
    inner_var = pd.DataFrame()
    return

def outer():
    outer_var = pd.DataFrame()
    inner()

outer()

The (empty) DF inner_var can be opened in DW. Now find the "CALL STACK" panel and click "outer". The "VARIABLES" panel now previews outer_var. But opening it in DW often fails, though not always.

@danhje danhje added the bug Issue identified by VS Code Team member as probable bug label Sep 9, 2024
@vs-code-engineering vs-code-engineering bot added the triage-needed Issue needs to be triaged label Sep 9, 2024
@DonJayamanne DonJayamanne assigned amunger and unassigned DonJayamanne Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug triage-needed Issue needs to be triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants