Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Find in file failing - UnicodeDecodeError: 'utf8' codec can't decode byte #1602
Find in files is always failing in my directory tree (quite large, mounted over NFS from a linux server to my Mac, handled via filesystem within Komodo).
Steps to Reproduce
Search for any phrase in all files.
List of files containing matching phrase!
A small number of files (100+) are scanned correctly, then one is clearly causing it to fail
Error: UnicodeDecodeError: 'utf8' codec can't decode byte 0xfd in position 3: invalid start byte
IMPORTANT: Despite Error the Log file is useless in that it doesn't pinpoint which file has the problem. So if the problem is due to one of my files having a corrupt UTF8 BOM (quite possible) then it isn't telling me which file. With 600+ files in root (don't ask) of project this is not easy to track down otherwise.
[2016-05-25 01:25:44,055] [INFO] Startup: Welcome to Komodo IDE 10.0.0 build 89159 (platform macosx, running on Darwin 15.4.0 version Darwin Kernel Version 15.4.0: Fri Feb 26 22:08:05 PST 2016; root:xnu-3248.40.184~3/RELEASE_X86_64)
[2016-05-25 01:25:45,061] [WARNING] root: ko.logging has been converted to a CommonJS module; use require("ko/logging") instead (since Komodo 9.0.0a1).
[2016-05-25 01:25:45,283] [ERROR] console-logger: TypeError: redeclaration of variable val (2) in chrome://analytics/content/analytics.js:204
[2016-05-25 01:25:46,697] [INFO] koInitService: Adding pre startup service for 'koFileStatusService': '@activestate.com/koFileStatusService;1'
[2016-05-25 01:25:47,765] [ERROR] console-logger: object Object in resource://gre/modules/addons/XPIProvider.jsm -> file:///Applications/Komodo%20IDE%2010.app/Contents/Resourcesfirstname.lastname@example.org/bootstrap.js:12
[2016-05-25 01:25:48,809] [WARNING] console-logger: Unknown property '-moz-border-radius'. Declaration dropped. (1) in chrome://docksearch/skin/styles.css:6
Is there any way to figure out how to find the culprit on my system now?
On 25 May 2016 at 15:11, mitchell email@example.com wrote:
Also, would it not be better for find in file to report that a file
On 25 May 2016 at 15:22, Jolyon Ralph firstname.lastname@example.org wrote: