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

fixing #3001 #3186 over logging of websocket exceptions and closure #3197

Merged
merged 2 commits into from
Jun 9, 2021

Conversation

shawkins
Copy link
Contributor

@shawkins shawkins commented May 31, 2021

Description

this localizes the state of a websocket to the listener, rather than the runner, to have a clearer lifecycle.

it reduces the logging of websocket stacktraces that shouldn't be meaningful.

it also replaces the use of BlockingQueue with CompletableFuture and adds another version of the utility method waitUntilReady for callers you aren't checking the boolean value.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • Feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change
  • Chore (non-breaking change which doesn't affect codebase;
    test, version modification, documentation, etc.)

Checklist

  • Code contributed by me aligns with current project license: Apache 2.0
  • I Added CHANGELOG entry regarding this change
  • I have implemented unit tests to cover my changes
  • I have added/updated the javadocs and other documentation accordingly
  • No new bugs, code smells, etc. in SonarCloud report
  • I tested my code in Kubernetes
  • I tested my code in OpenShift

@centos-ci
Copy link

Can one of the admins verify this patch?

@shawkins shawkins force-pushed the watch_close branch 3 times, most recently from 22d7041 to 3ddf258 Compare June 2, 2021 02:58
@shawkins shawkins marked this pull request as ready for review June 2, 2021 03:00
@shawkins shawkins added the wip label Jun 3, 2021
@shawkins
Copy link
Contributor Author

shawkins commented Jun 3, 2021

This should wait until after #3185 - it looks like after that change a lot more logic can be pulled up into AbstractWatchManager. I have started down that path with this pr.

@shawkins shawkins force-pushed the watch_close branch 4 times, most recently from a635096 to 93da37b Compare June 8, 2021 13:54
@shawkins shawkins removed the wip label Jun 8, 2021
…ions and closure

this removes the runner abstraction

it also replaces the use of BlockingQueue with CompletableFuture.
@sonarcloud
Copy link

sonarcloud bot commented Jun 9, 2021

Copy link
Member

@manusa manusa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thx!

@manusa manusa merged commit fb5e638 into fabric8io:master Jun 9, 2021
@manusa manusa added this to the 5.5.0 milestone Jun 10, 2021
Vlatombe added a commit to Vlatombe/kubernetes-plugin that referenced this pull request Mar 31, 2022
InterruptedException is no longer thrown on websocket timeout, rather a
KubernetesClientException. Unfortunately there is no way to
differentiate between a timeout and an error.

* fabric8io/kubernetes-client#3274
* fabric8io/kubernetes-client#3197
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants