Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Multiple instances are created from a ConfigSource #5175

Closed
kjuhasz opened this issue Nov 4, 2019 · 2 comments
Closed

Multiple instances are created from a ConfigSource #5175

kjuhasz opened this issue Nov 4, 2019 · 2 comments
Labels
triage/out-of-date This issue/PR is no longer valid or relevant

Comments

@kjuhasz
Copy link

kjuhasz commented Nov 4, 2019 •
edited
Loading

Language: Kotlin (AWS Lambda)

Environment: When running a @QuarkusTest annotated test

Setup: A class implements org.eclipse.microprofile.config.spi.ConfigSource and is added to the list of entries in org.eclipse.microprofile.config.spi.ConfigSource under META-INF/services

Scenario: When running a test annotated with @QuarkusTest (Currently I can not test it any other way because of this issue) multiple instances are created from the class defined in the services file.
@jmartisk
Copy link
Contributor

jmartisk commented Nov 4, 2019

Looks like yet another manifestation of #4512

dmlloyd added a commit to dmlloyd/quarkus that referenced this issue Nov 22, 2019
@dmlloyd
Disable failing test (see quarkusio#5175)
c57d90c
Simulant87 pushed a commit to Simulant87/quarkus that referenced this issue Nov 23, 2019
@dmlloyd @Simulant87
Disable failing test (see quarkusio#5175)
e95b9d8
Simulant87 pushed a commit to Simulant87/quarkus that referenced this issue Nov 23, 2019
@dmlloyd @Simulant87
Disable failing test (see quarkusio#5175)
167ad7e
mmusgrov pushed a commit to mmusgrov/quarkus that referenced this issue Dec 13, 2019
@dmlloyd @mmusgrov
Disable failing test (see quarkusio#5175)
1042f98
@emmanuelbernard
Copy link
Member

can you check again on Quarkus 1.3+ Lots has happened since then. Please reopen as needed

@emmanuelbernard emmanuelbernard added the triage/out-of-date This issue/PR is no longer valid or relevant label Apr 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
triage/out-of-date This issue/PR is no longer valid or relevant
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@emmanuelbernard @jmartisk @kjuhasz