Open jboilesen opened 4 months ago
Thanks for the report. Can you tell me what sort of file this was? It looks like this was an “injection” scenario — one language embedded in another — so I'm curious to know which language might have the bug here.
It happened in a pure .php
file with only PHP code (but the project also has HTML, CSS and JS files).
Strangely, that counts because of the way that the PHP grammar is architected.
I see the bug here (assuming something that may return null
is an array without checking it), but I don't yet understand why it happens. Still, I should at least make it so that it doesn't throw an exception.
I'm glad that it's sporadic instead of something that happens all the time. Still, if you figure out reliable reproduction steps, please let me know. Thanks!
Thanks in advance for your bug report!
What happened?
I was simply writing code when autocomplete throw this error.
Pulsar version
1.119.2024071703 x64
Which OS does this happen on?
🐧 Debian based (Linux Mint, Ubuntu, etc.)
OS details
Debian Bookworm
Which CPU architecture are you running this on?
x86_64/AMD64
What steps are needed to reproduce this?
Sincerely, I am not sure how to reproduce this issue.
I was typing in a big file (4000+ lines) in a big project (3000+ files) and autocomplete thrown this error.
Additional Information:
Versions
Pulsar: 1.119.2024071703 x64 Electron: 12.2.3 OS: Debian GNU/Linux Thrown From: Pulsar Core
Stack Trace
Uncaught TypeError: Cannot read property 'map' of null
Commands
Non-Core Packages