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.

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

Added GraphQL service information to the response results of NetServices. #7580

Merged
merged 4 commits into from
Sep 16, 2024

Conversation

ITStarMan100
Copy link
Contributor

@ITStarMan100 ITStarMan100 commented Sep 5, 2024

PR description

Added GraphQL service information to the response results of NetServices.

Fixed Issue(s)

fixes #7513

This PR is in response to this #7513

@non-fungible-nelson please review when you have some time.

Signed-off-by: ITStarMan100 <danhopeman@outlook.com>
@ITStarMan100 ITStarMan100 changed the title Added GraphQL Service Information in responese result NetServices Added GraphQL Service Information in responese result of NetServices Sep 5, 2024
@ITStarMan100 ITStarMan100 changed the title Added GraphQL Service Information in responese result of NetServices Added GraphQL Service Information in response result of NetServices Sep 5, 2024
@ITStarMan100 ITStarMan100 changed the title Added GraphQL Service Information in response result of NetServices Added GraphQL service information to the response results of NetServices. Sep 6, 2024
@macfarla macfarla requested a review from jflo September 10, 2024 01:04
@macfarla
Copy link
Contributor

@jflo seems like another candidate for daggerization

@jflo jflo added techdebt maintenance, cleanup, refactoring, documentation dagger illustrates a need for IoC labels Sep 10, 2024
@ITStarMan100
Copy link
Contributor Author

I can update my code to use Dagger for dependency injection of the GraphQLConfiguration class.

I would like to ask @jflo if I can proceed by creating a GraphQLConfigurationModule.

@jflo
Copy link
Contributor

jflo commented Sep 11, 2024

I can update my code to use Dagger for dependency injection of the GraphQLConfiguration class.

I would like to ask @jflo if I can proceed by creating a GraphQLConfigurationModule.

Yes! the two most important questions to ask yourself when starting is 1) how is the thing created 2) what class ACTUALLY depends on it, directly. not transitively.

Once you know that, then you need to see if the other things it depends on during 1) can be provided via Dagger. This is often a stumbling block, but more things are added all the time. My current WIP is increasing what is available quite a bit.

@ITStarMan100
Copy link
Contributor Author

If the work is still in progress, I can start working on Dagger once it's finished.
If there are no additional reviews needed for the current code, it might be better to proceed with integration.

@jflo
Copy link
Contributor

jflo commented Sep 12, 2024

yes, it's totally appropriate to refactor toward dagger in a future pr.

@ITStarMan100
Copy link
Contributor Author

Will my PR be rejected?

@jflo
Copy link
Contributor

jflo commented Sep 12, 2024

Will my PR be rejected?

No it will not, just waiting on feedback/approval for this and we will merge it.

@ITStarMan100
Copy link
Contributor Author

When I first submitted the PR, the check for testing on my local PC passed.

However, after 5 days and merging with the latest changes from besu main branch, it seems that there is an error in TxPoolOptionsTest.
(txpoolForcePriceBumpToZeroWhenZeroBaseFeeMarket() FAILED
org.mockito.exceptions.verification.WantedButNotInvoked at TxPoolOptionsTest.java:104)

Should I resubmit the PR with the latest changes from besu main branch?
Or is there a way to fix the issue in TxPoolOptionsTest since @jflo reviewed and approved my PR?

Can @jflo help me to fix this issue?

@ITStarMan100
Copy link
Contributor Author

I'm getting the same check pass error as my PR (#7580) in "Moved maintainers to emeritus #7611".

What could be the reason?

@macfarla
Copy link
Contributor

When I first submitted the PR, the check for testing on my local PC passed.

However, after 5 days and merging with the latest changes from besu main branch, it seems that there is an error in TxPoolOptionsTest. (txpoolForcePriceBumpToZeroWhenZeroBaseFeeMarket() FAILED org.mockito.exceptions.verification.WantedButNotInvoked at TxPoolOptionsTest.java:104)

Should I resubmit the PR with the latest changes from besu main branch? Or is there a way to fix the issue in TxPoolOptionsTest since @jflo reviewed and approved my PR?

Can @jflo help me to fix this issue?

think that is a flaky test that has been disabled in the meantime. checks now running on your updated PR 🤞

@macfarla macfarla enabled auto-merge (squash) September 16, 2024 02:09
@macfarla macfarla merged commit 12caf7d into hyperledger:main Sep 16, 2024
41 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dagger illustrates a need for IoC techdebt maintenance, cleanup, refactoring, documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

net-service information reading error for GraphQL
3 participants