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

Rubberduck doesn't find anything when it's scanning #6227

Closed
Rovo1211 opened this issue Nov 14, 2024 · 6 comments
Closed

Rubberduck doesn't find anything when it's scanning #6227

Rovo1211 opened this issue Nov 14, 2024 · 6 comments
Labels
bug Identifies work items for known bugs status-bydesign "It's not a bug, it's a feature!" status-norepro The issue could not be reproduced. If there is a stable repro, please add that as a new comment.

Comments

@Rovo1211
Copy link

Rubberduck version information
The info below can be copy-paste-completed from the first lines of Rubberduck's log or the About box:

Rubberduck version 2.5.9.6316
Operating System: Windows 11 Home 23H2
Host Product: Excel VBE 7.1
Host Version:  Excel 365
Host Executable: [...]

Description
When I refresh the window of the Code Explorer, it doesn't find anything. I've tried many things to solve it, but so far no result. Sometimes it finds FUNCRES.XLAM, but no other things although there are more files open.

To Reproduce
Steps to reproduce the behavior:

  1. Go to menu Rubberduck
  2. Click on 'Refresh'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise overview of all MY objects in the Excel file
Rubberduck, Code Inspector
Rubberduck, Code Explorer
RubberduckLog.txt
.

Screenshots
If applicable, add screenshots to help explain your problem.

Logfile
Rubberduck generates extensive logging in TRACE-Level. If no log was created at %APPDATA%\Rubberduck\Logs, check your settings. Include this log for bug reports about the behavior of Rubberduck.

Additional context
Add any other context about the problem here.

@Rovo1211 Rovo1211 added the bug Identifies work items for known bugs label Nov 14, 2024
@Rovo1211
Copy link
Author

Only one time Rubberduck has worked PERFECTLY. After that time it didn't find anything to show although there was a file open with at least 20 macros, forms, etc.
Why it doesn't display the third level as in "@folder("Aandelen/Update/Declaraties")?

@Vogel612
Copy link
Member

Are you certain that the file fully parses as is? The Logs suggest there is a syntax error in "Aandelen_Update". If that is the case, Rubberduck basically disables most of its features to not accidentally break anything ...

@Rovo1211
Copy link
Author

That is what Rubberduck is for: to find errors in your code and correct it. If Rubberduck already falls about syntax-errors...

@retailcoder
Copy link
Member

That is what Rubberduck is for.

No. Rubberduck has always assumed the code it's looking at is legal code that VBA can compile and run. We strive to ensure any legal VBA code can be correctly processed, but it's the compiler's job to produce the executable P-Code and report any errors that might occur while doing so; Rubberduck (or any other tool) literally cannot do the compiler's job without being a compiler itself.

@Vogel612 Vogel612 added status-bydesign "It's not a bug, it's a feature!" status-norepro The issue could not be reproduced. If there is a stable repro, please add that as a new comment. labels Dec 6, 2024
@Vogel612
Copy link
Member

Vogel612 commented Dec 6, 2024

Judging by the follow-up issues you opened that both expect rubberduck to work off code that does not compile, that was the underlying issue here as well. Closing for the same reason. The underlying paradigm for Rubberduck is that we need code that parses correctly, otherwise we could irrecoverably break user code, which is unacceptable. To prevent that, we instead severely limit Rubberduck's functionality until the code we are supposed to analyze parses.

@Vogel612 Vogel612 closed this as completed Dec 6, 2024
@Rovo1211
Copy link
Author

Rovo1211 commented Dec 8, 2024 via email

@rubberduck-vba rubberduck-vba locked and limited conversation to collaborators Dec 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Identifies work items for known bugs status-bydesign "It's not a bug, it's a feature!" status-norepro The issue could not be reproduced. If there is a stable repro, please add that as a new comment.
Projects
None yet
Development

No branches or pull requests

3 participants