search

microsoft / vscode-data-wrangler

Other
442 stars 20 forks source link

Failed to load the data frame: TypeError: 'module' object is not callable #260

Open vidyutkapur opened 3 months ago

vidyutkapur commented 3 months ago

Type: Bug

Behaviour

Expected vs. Actual

When clicking on "Open in data wrangler, at the bottom of a code cell in a Jupyter notebook in VS Code, it opened the DW window and then showed the error "Failed to load the data frame: TypeError: 'module' object is not callable"

Steps to reproduce:

  1. XXX

Diagnostic data

N/A

Extension version: 1.6.0 VS Code version: Code 1.92.1 (eaa41d57266683296de7d118f574d0c2652e1fc4, 2024-08-07T20:16:39.455Z) OS version: Windows_NT x64 10.0.22631 Modes:

System Info |Item|Value| |---|---| |CPUs|11th Gen Intel(R) Core(TM) i5-11300H @ 3.10GHz (8 x 3110)| |GPU Status|2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off| |Load (avg)|undefined| |Memory (System)|15.79GB (5.32GB free)| |Process Argv|--crash-reporter-id 166e4d2e-2efd-44e1-a727-f852601d166a| |Screen Reader|no| |VM|0%|
A/B Experiments ``` vsliv368cf:30146710 vspor879:30202332 vspor708:30202333 vspor363:30204092 vswsl492cf:30256860 vscod805cf:30301675 binariesv615:30325510 vsaa593cf:30376535 py29gd2263:31024239 c4g48928:30535728 azure-dev_surveyone:30548225 vscrp:30673768 a9j8j154:30646983 962ge761:30959799 pythongtdpath:30769146 welcomedialog:30910333 pythonnoceb:30805159 asynctok:30898717 pythonregdiag2:30936856 pythonmypyd1:30879173 h48ei257:31000450 pythontbext0:30879054 accentitlementsc:30995553 dsvsc016:30899300 dsvsc017:30899301 dsvsc018:30899302 cppperfnew:31000557 dsvsc020:30976470 pythonait:31006305 dsvsc021:30996838 jg8ic977:31013176 pythoncenvpt:31062603 a69g1124:31058053 dvdeprecation:31068756 dwnewjupyter:31046869 impr_priority:31102340 refactort:31108082 pythonrstrctxt:31112756 wkspc-onlycs-t:31111718 wkspc-ranged-t:31111713 ```

image image

kycutler commented 3 months ago

Hi @vidyutkapur, thanks for opening this issue!

Does this error happen every time?

To narrow down the problem, please try the following:

  1. Restart VS Code, create an empty notebook with just a simple variable x = [1, 2, 3] and try to open x in Data Wrangler.
  2. Open a CSV file in Data Wrangler by right-clicking it in the file explorer and selecting "Open in Data Wrangler".

Please confirm if either of the above works.

vidyutkapur commented 2 months ago

Kyle,

I tried all of the suggestion in your email.

I tried once again opening the data frame which had originally given me the error. It still gives me the same error. (screenshot attached) [image: image.png]

Hope this helps.

Regards, Vidyut

On Wed, Aug 21, 2024 at 5:32 AM Kyle Cutler @.***> wrote:

Hi @vidyutkapur https://github.com/vidyutkapur, thanks for opening this issue!

Does this error happen every time?

To narrow down the problem, please try the following:

  1. Restart VS Code, create an empty notebook with just a simple variable x = [1, 2, 3] and try to open x in Data Wrangler.
  2. Open a CSV file in Data Wrangler by right-clicking it in the file explorer and selecting "Open in Data Wrangler".

Please confirm if either of the above works.

— Reply to this email directly, view it on GitHub https://github.com/microsoft/vscode-data-wrangler/issues/260#issuecomment-2299960125, or unsubscribe https://github.com/notifications/unsubscribe-auth/APSIBTAPYRMGD4CDKSQWGH3ZSPKIPAVCNFSM6AAAAABMVGLTB6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJZHE3DAMJSGU . You are receiving this because you were mentioned.Message ID: @.***>

kycutler commented 2 months ago

@vidyutkapur thank you for the information!

Given that an empty notebook with just x = [1, 2, 3] works, it is likely that there is some unexpected variable in the notebook you are trying to use that is causing Data Wrangler to fail (for example, if a Python built-in such as print / type / etc. were to be redefined in the notebook, it could potentially cause problems in Data Wrangler code).

We have made some changes in the latest pre-release version of Data Wrangler (v1.9.1) that may fix the issue. Can you try that version and let me know if the issue still occurs?

If so, would you be able to share a sample notebook here that reproduces the issue?