10000 fix: javadoc blocking snapshot release by csviri · Pull Request #904 · operator-framework/java-operator-sdk · GitHub
[go: up one dir, main page]

Skip to content

fix: javadoc blocking snapshot release #904

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

Merged
merged 1 commit into from
Feb 2, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@

/**
* <p>
* Pols resource (on contrary to {@link PerResourcePollingEventSource}) not per resource bases but
* Polls resource (on contrary to {@link PerResourcePollingEventSource}) not per resource bases but
* instead to calls supplier periodically and independently of the number of state of custom
* resources managed by the operator. It is called on start (synced). This means that when the
* reconciler first time executed on startup a poll already happened before. So if the cache does
Expand All @@ -24,7 +24,7 @@
* Another caveat with this is if the cached object is checked in the reconciler and created since
* not in the cache it should be manually added to the cache, since it can happen that the
* reconciler is triggered before the cache is propagated with the new resource from a scheduled
* execution. See {@link PollingEventSource##put(ResourceID, Object)}.
* execution. See {@link #put(ResourceID, Object)} method.
* </p>
* So the generic workflow in reconciler should be:
*
Expand Down
0