Validation discrepancy between classpath model and imported model

When using the smithy-gradle-plugin to build/validate a model, if that model is pulled in via the classpath by existing in a model/ directory, then the validation errors for that model are different than if that model is explicitly imported via the smithy-build.json file.

Here’s an example minimal model that should produce a DANGER error (it doesn’t like teapots, unless something changes due to #1386):

$version: "1.0"
namespace aws.protocoltests.misc

use aws.protocols#restJson1
use smithy.test#httpRequestTests
use smithy.test#httpResponseTests

@restJson1
service MiscService {
    operations: [ResponseCodeRequiredOperation],
}

@http(method: "GET", uri: "/responseCodeRequiredOperation", code: 418)
operation ResponseCodeRequiredOperation {
    input: EmptyStructure,
    output: ResponseCodeRequiredOutput,
}

structure EmptyStructure {}

@output
structure ResponseCodeRequiredOutput {
    @required
    @httpResponseCode
    responseCode: Integer,
}

This model, if pulled in by existing in the models/ directory, emits a WARN due to the IDL version being 1, but does not emit the DANGER message. If instead, it is placed outside the models/ directory and referenced directly from the imports section of smithy-build.json, then the DANGER message is emitted and the build fails.

[mtdowling]

Ok thanks for checking. One thing that I did see when trying to repro this is that the output was weird and interleaving text across threads (due to the use of PrintStream instead of PrintWriter). This PR will fix that https://github.com/awslabs/smithy/pull/1525. I’ll go ahead and resolve this, but let me know if you ever see it again.

[jdisanti]

I’m not able to repro this anymore in smithy-rs with Smithy 1.26.2.