11–20 of 216 posts
I'm gonna argue that the bug is not in "file". The bug is that the workflow uses file, which by it's very nature must be based on heuristics and will get things wrong occasionally. EDIT: Well file really had a bug in this case, where they didn't detect what they thought they were, but the point stands.
https://plus.google.com/113181962167438638669/posts/QF5pDB4X...
I love bugs like this. As a developer or Sysadmin you'd think the users are crazy again but then you dig deeper until you lose all hope and already book flights to become a farmer in the midwest and then you find something like thís
http://web.mit.edu/jemorris/humor/500-miles
Edit: And the FAQ: https://www.ibiblio.org/harris/500milemail-faq.html
I'm gonna argue that the bug is not in "file". The bug is that the workflow uses file, which by it's very nature must be based on heuristics and will get things wrong occasionally. EDIT: Well file really had a bug in this case, where they didn't detect what they thought they were, but the point stands.
I'm not sure to agree: if/as *nix systems do not use the extension to know the filetype, then `file`-like heuristics is the only other way to know the file nature, or do I miss someting?
But your point arguably stands: if a user says "print file X", and you want different files printed using different logic (e.g. PDFs and PostScript files should be printed differently than text files), what other option is there other than using something like "file" to try and guess the file type? It would be very annoying for the user to have to specify each time from a massive list of possible optins.
Reminds me of a bug in PostSharp.. After making some changes our app would throw a NullReferenceException Mondays. It turned out to be a bug in some optimisation, but it only occurred on Monday because they skipped licence checks unlocking "full functionality" on a Monday (Happy Monday!) which enabled the optimisation. https://plus.google.com/113181962167438638669/posts/QF5pDB4X...
I'm gonna argue that the bug is not in "file". The bug is that the workflow uses file, which by it's very nature must be based on heuristics and will get things wrong occasionally. EDIT: Well file really had a bug in this case, where they didn't detect what they thought they were, but the point stands.
I'm not sure to agree: if/as *nix systems do not use the extension to know the filetype, then `file`-like heuristics is the only other way to know the file nature, or do I miss someting?
Reminds me of a bug in PostSharp.. After making some changes our app would throw a NullReferenceException Mondays. It turned out to be a bug in some optimisation, but it only occurred on Monday because they skipped licence checks unlocking "full functionality" on a Monday (Happy Monday!) which enabled the optimisation. https://plus.google.com/113181962167438638669/posts/QF5pDB4X...
i can't remember exactly now, but webpack had a monday-only bug as wellat some point last year.
Reminds me of a bug in PostSharp.. After making some changes our app would throw a NullReferenceException Mondays. It turned out to be a bug in some optimisation, but it only occurred on Monday because they skipped licence checks unlocking "full functionality" on a Monday (Happy Monday!) which enabled the optimisation. https://plus.google.com/113181962167438638669/posts/QF5pDB4X...
i can't remember exactly now, but webpack had a monday-only bug as wellat some point last year.
I'm not sure why that would affect something like webpack though (unless the problem was specific to a date manipulation library).
Edit: spotted the post that arrived as I typed the above. Looks like an advertising related function that only ran once per week using something not available on all sorted OS builds for that code, so not a locale related problem. Advertising causing unexpected problems yet again!