console error: 'Assertion failed: yarn out should always be exactly yarn in.'

[gabrielle-ohlson]

Though this doesn't seem to be impacting the performance of the visualizer, I keep getting the following console error and am not sure why:

CellMachine.js:503 Assertion failed: yarn out should always be exactly yarn in.

  | (anonymous) | @ | CellMachine.js:503
-- | -- | -- | --
  | CellMachine_addCells | @ | CellMachine.js:458
  | CellMachine_bringCarriers | @ | CellMachine.js:842
  | CellMachine_knitTuck | @ | CellMachine.js:1128
  | CellMachine_knit | @ | CellMachine.js:1162
  | (anonymous) | @ | parseKnitout.js:152
  | parseKnitout | @ | parseKnitout.js:12
  | ShowKnitout_parse | @ | show-knitout.js:425
  | updateVisualizer | @ | (index):339
  | setSource | @ | (index):456
  | reader.onload | @ | (index):476
  | load (async) |   |  
  | readFile | @ | (index):475
  | (anonymous) | @ | (index):574

It is always preceded by the following log (with variation in the carrier numbers):

CellMachine.js:468 Adding ["3","4","5","2"] | [] over ["2","3","4","5"] | []

NOTE: the above console error is copied from an instance of using the knitout visualizer site, but the error appears when using the local clone version (as well as the earlier version mentioned in #15)

[ixchow]

I think this looks like an error in ordering yarns during carrier motion.

If you have a moment, it would be useful to attach the file that causes the error when visualized.

[gabrielle-ohlson]

sure thing, here's one example file where it comes up (but seems to be coming up with most files I load in the visualizer that use more than one carrier)