gus-asf commented on PR #2284: URL: https://github.com/apache/solr/pull/2284#issuecomment-1953997986
The above tidy/spotless check does not reproduce locally for me. Neither running `gradlew spotlessApply` nor running `gradlew tidy` tasks produce changes. The offending file is not changed in this change list and does not have this flaw on my local machine or in the branch I am merging? https://github.com/gus-asf/solr/blob/SOLR-17140_9x/solr/core/src/test/org/apache/solr/cloud/SolrCloudExampleTest.java#L44 ... seems to be seeing this: https://github.com/apache/solr/commit/9b9f56970b695f64769fd5dc277d3ca66819c034 which apparently broke things. *sigh* Would be nice if this PR interface identified that commits had happened, even if they don't interfere with the merge. Also @epugh maybe following a PR process when back-porting would have caught this without breaking others? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
