parser crashes with comment at beginning of file
See original GitHub issueUsing latest version from master
test.sql
-- comment at beginning of file
select * from my_table
Last part of traceback
File "...\.venv\src\sqlfluff\src\sqlfluff\rules\std.py", line 1760, in _eval
if last_seg.type == 'comma':
AttributeError: 'NoneType' object has no attribute 'type'
Problem persists even with block /**/
comment
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
INI Parser crashes with `segmentation fault` after opening ...
I am making an INI parser that will save all sections in an array for later use. The problem I am running into...
Read more >Clangd repeatedly crashing on a single file after ...
After restarting, the file it crashed on originally will continue to crash clangd, whereas other files will be fine.
Read more >VS 2017 RC crashes while parsing included files
You are able to get the files with the following steps: 1. Start Visual Studio. 2. Start another instance of VS. 3. Select...
Read more >Attacking the batch file parser - The Old New Thing
Another scenario is that an attacker convinces a naïve user to type the specific malformed command line and cause their command prompt to...
Read more >Papa Parse - Powerful CSV Parser for JavaScript
The world's first multi-threaded CSV parser for the browser. Papa can handle files gigabytes in size without crashing. Use Papa when performance, privacy, ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Interesting! Would you mind trying with the pre release version?
pip install sqlfluff --pre
Tried with the pre, different error, and it happens twice for the same rule in the same code-path: