Error: Column start (16) greater than line length (15)
See original GitHub issueError: Column start (16) greater than line length (15)
at Object.rangeFromLineNumber (/Users/miketheman/.atom/packages/linter-flake8/node_modules/atom-linter/lib/index.js:179:11)
at extractRange (/Users/miketheman/.atom/packages/linter-flake8/lib/main.js:49:18)
at Object.<anonymous> (/Users/miketheman/.atom/packages/linter-flake8/lib/main.js:194:25)
at undefined.next (native)
at step (/Users/miketheman/.atom/packages/linter-flake8/lib/main.js:9:273)
at process._tickCallback (internal/process/next_tick.js:103:7)
Using linter-flake8 2.0.0
Issue Analytics
- State:
- Created 7 years ago
- Reactions:54
- Comments:23 (11 by maintainers)
Top Results From Across the Web
PostgreSQL "Column does not exist" but it actually does
This problem occurs in postgres because the table name is not tablename instead it is "tablename". for eg. If it shows user as...
Read more >20.8. Error Reporting and Logging - PostgreSQL
When logging_collector is enabled, this parameter will cause PostgreSQL to truncate (overwrite), rather than append to, any existing log file of the same...
Read more >nchar and nvarchar (Transact-SQL) - Microsoft Learn
This large row size can cause errors (such as error 512) that users may not anticipate during some normal operations. Two examples of...
Read more >2 Server Error Message Reference - MySQL :: Developer Zone
Message: Column length too big for column '%s' (max = %lu); use BLOB or TEXT instead ... Message: Result string is longer than...
Read more >Data Types
If you try to insert a value that is too long for the column, then Oracle returns an error. Note that if the...
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 FreeTop 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
Top GitHub Comments
I have found a decent workaround that will suppress the error and allow linter-flake8 to function without any negative side effects.
Open file: .atom\packages\linter-flake8\node_modules\atom-linter\lib\index.js and scroll down to line # 178
Replace:
With:
Before applying this workaround I was constantly being spammed with the error message discussed in the first post and linter-flake8 would not function at all. However, after applying the aforementioned changes to index.js, I am now using linter-flake8 without any issues.
Disclaimer: This is, at best, a cheap hack to keep things glued together until the project developers are able to update the plugin with a proper fix.
Error still happening for me with 2.0.2.