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

Profiler pane not showing results #21590

Open
dalthviz opened this issue Dec 5, 2023 · 1 comment · May be fixed by #21713
Open

Profiler pane not showing results #21590

dalthviz opened this issue Dec 5, 2023 · 1 comment · May be fixed by #21713

Comments

@dalthviz
Copy link
Member

dalthviz commented Dec 5, 2023

Problem Description

Unable to see code profiling results. Also seems like there some sort of widget under the Profiler pane file combobox selector.

What steps reproduce the problem?

  1. Try to profile a file via the menu (Run > Run profiler)

What is the expected output? What do you see instead?

Expected to see the profiler result as a tree instead the empty pane message persists

Behavior preview:

profiler

Versions

  • Spyder version: 6.0.0.dev0 0d4f204 (conda)
  • Python version: 3.9.17 64-bit
  • Qt version: 5.15.2
  • PyQt5 version: 5.15.7
  • Operating System: Windows-10-10.0.19045-SP0
@dalthviz
Copy link
Member Author

dalthviz commented Dec 6, 2023

Note: Seems like PR #21555 fixed the UI issue releated with the combobox

@ccordoba12 ccordoba12 modified the milestones: v6.0alpha3, v6.0beta1 Dec 14, 2023
rear1019 added a commit to procitec/spyder that referenced this issue Jan 16, 2024
@rear1019 rear1019 linked a pull request Jan 16, 2024 that will close this issue
@ccordoba12 ccordoba12 modified the milestones: v6.0alpha4, v6.0beta1 Feb 6, 2024
@ccordoba12 ccordoba12 modified the milestones: v6.0alpha5, v6.0beta1 Mar 12, 2024
@ccordoba12 ccordoba12 modified the milestones: v6.0beta1, v6.1.0 May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants