-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MP Config TCK - Fix excluded tests #4516
Comments
microprofile/microprofile-config#446 covers the |
@dmlloyd @jmesnil I was taking a look at Basically the test iterates over system properties and verifies that the values from What's weird is that the value for Any thoughts? |
There's an actual property called |
I believe it's set by Maven. I'm just confused how accessing it directly through system properties, and through system properties in the config source, lead to one having a leading space and one not |
Is there a log output I could look at without having to build everything? |
Will run the test and capture it for you |
@dmlloyd here's the output from running the single test method: https://gist.github.com/kenfinnigan/ede49a21fd7f144f7d58c65e29b295cc |
Hmm that's pretty strange. I think we can rule out SmallRye Config though because that call path would just be |
Well I guess that's good, but I'm really confused as to how |
I think it's not Here's one hypothesis, which might be a little crazy but it's all I can think of that makes sense: Maven copies all the system and env properties into the Maven property map. They somehow munge the whitespace at that time. Or, at a later point, they set that property by hand for some reason. Then we haplessly copy the build system properties in as a configuration source (we have one for the build system's properties), somehow including that property despite it not being within our namespace. |
So you think we shouldn't be copying any property that doesn't begin |
The intent for that code was in fact to only copy build system properties that started with |
That's fine, I can dig in to see if I can discover why we're reading more than needed. Might be a key needs to be passed to SRye Config, maybe |
@dmlloyd so I figured out what's going on with the system properties.
Is it ok to add a no trim flag to the expression creation? |
Sure, that should be fine. |
Fix MP Config TCK tests as part of #4516
@dmlloyd Does it make sense to make it serializable in SmallRye Common and switch Quarkus to use that instead of WF common? Are the two "identical" enough to do that? |
It might be easier to make the |
- Ensures Config is serializable - Passes Config serialization TCK test
Currently, the below tests are excluded from execution when running the MP Config TCK. We need to either fix Quarkus so the test passes or challenge and fix the TCK if it's a problem there.
The text was updated successfully, but these errors were encountered: