René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Test ops.yaml files can be merged incorrectly","articleBody":"With 5da81736cce48d7525e69762d51165c5e74735df, I removed the progress reporting from the `DefaultOpEnvironment`'s op discovery, because it was failing the `OpRegressionTest` on one of my systems. Investigation shone light onto three distinct issues, the first of which is #228, which I believe is a cascading failure triggered by the second and third issues, described here. First, snakeyaml rejects a mangled `scijava-ops-image/target/test-classes/ops.yaml` file:\r\n\r\n```    \r\nCaused by: java.lang.ExceptionInInitializerError: Exception\r\norg.yaml.snakeyaml.scanner.ScannerException: while scanning for the\r\nnext token; found character '@' that cannot start any token.\r\n(Do not use @ for indentation);  in 'reader', line 26008, column 2:\r\n  {@code \u003cC\u003e}\r\n   ^ [in thread \"main\"]\r\n    at org.yaml.snakeyaml@2.0/org.yaml.snakeyaml.scanner.ScannerImpl.fetchMoreTokens(ScannerImpl.java:445)\r\n    ...\r\n    at org.yaml.snakeyaml@2.0/org.yaml.snakeyaml.Yaml.load(Yaml.java:434)\r\n    at org.scijava.ops.engine@0-SNAPSHOT/org.scijava.ops.engine.yaml.impl.YAMLOpInfoDiscoverer.parse(YAMLOpInfoDiscoverer.java:104)\r\n    at org.scijava.ops.engine@0-SNAPSHOT/org.scijava.ops.engine.yaml.impl.YAMLOpInfoDiscoverer.lambda$discover$0(YAMLOpInfoDiscoverer.java:78)\r\n```\r\n\r\nThe mangling takes the form of a rogue string `{@code \u003cC\u003e}` on its own line with no indentation, which appears to have overwritten some number of other lines of YAML, leading to improper indentation. (I tried diffing against a properly merged `ops.yaml` on an unaffected system, but the scijava-ops-indexer does not sort the op blocks, leading to ordering inconsistency, which makes diffing ineffective.)\r\n\r\nI suspect the mangling is rooted in a third issue: there is a Ruby script present in the Maven build infrastructure that gets executed using `script-maven-plugin`, which might be the culprit. But further investigation is needed: it is suspicious that with the removal of progress reporting from `DefaultOpEnvironment` construction (5da81736cce48d7525e69762d51165c5e74735df, which works around #228), the YAML parsing issue seems to disappear—but it is hard to believe that these two things could actually be related...\r\n","author":{"url":"https://github.com/ctrueden","@type":"Person","name":"ctrueden"},"datePublished":"2024-05-30T16:10:56.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/229/scijava/issues/229"}