edf2csv 0.8.64 → 0.8.66

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/cli.js CHANGED
@@ -283,8 +283,25 @@ export async function main(argv) {
283
283
  }
284
284
  // Reported before anything is converted, so it cannot be lost among the summaries, and
285
285
  // counted against the run so the exit code does not call a partial sweep a success.
286
+ /*
287
+ What the walk actually knows, which is the sentence the summary below already uses.
288
+
289
+ This list holds two different things: a directory whose `readdir` failed, and any entry
290
+ whose `stat` failed — a broken link, whatever it pointed at. The walk cannot tell them
291
+ apart, which is the reason the comment in `walk` gives for reporting all of them: "The
292
+ walk cannot know what was behind a link it cannot follow."
293
+
294
+ So "any recordings inside it" is an assertion about a container, made about a list that
295
+ may hold none. It reads wrong on a broken `night-02.edf`, and cli-reference printed the
296
+ two sentences two lines apart, about the same path:
297
+
298
+ error: /data/locked: could not be read, so any recordings inside it were skipped.
299
+ error: Nothing could be converted.
300
+ That path could not be read, so whether it holds recordings is unknown.
301
+ */
286
302
  for (const entry of unreadable) {
287
- process.stderr.write(`error: ${printable(entry)}: could not be read, so any recordings inside it were skipped.\n`);
303
+ process.stderr.write(`error: ${printable(entry)}: could not be read, so whether it holds recordings is ` +
304
+ `unknown. It was skipped.\n`);
288
305
  }
289
306
  if (expanded.length === 0) {
290
307
  /*