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

use MetaStorage.get where null allowed #3630

Merged
merged 5 commits into from
Dec 4, 2024

Conversation

awildturtok
Copy link
Collaborator

No description provided.

…ectColumnValuesJob (#3618)

* adds soft pool cleaner, configuration and allocation limiter for CollectColumnValuesJob
* use 4 kibibytes as default chunk size for NetworkSession
* Reduce queue size of NetworkSession and make configurable.

---------

Co-authored-by: awildturtok <[email protected]>
@awildturtok awildturtok requested a review from thoniTUB December 3, 2024 10:38
@awildturtok awildturtok force-pushed the fix/use-get-where-failure-allowed branch from e9d3b4d to 5f2553c Compare December 3, 2024 11:23
It is a potentially excepting operation which may cause the entire stack to crash. Instead use *Storage.get which will produce null. Handling is then at the discretion of the caller.
@awildturtok awildturtok force-pushed the fix/use-get-where-failure-allowed branch from 5f2553c to c1dad12 Compare December 3, 2024 14:06
Copy link
Collaborator

@thoniTUB thoniTUB left a comment

Choose a reason for hiding this comment

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

Sehr cool, dass du noch einige abkürzungen gefunden hast!

@@ -57,6 +57,7 @@ public CDateRange getValidityDate(int event, Bucket bucket) {
// JsonCreator was not happy, and I could not figure out why. This is probably the most performant implementation that's not two classes.

if (getColumn() != null) {
// TODO resolve in hot loop
Copy link
Collaborator

Choose a reason for hiding this comment

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

Vielleicht im Konstruktor schon zu transient resolven, dann passiert das resolven nur einmal beim laden des Concepts

Comment on lines +315 to +316
status.setOwner(user.getId());
status.setOwnerName(user.getLabel());
Copy link
Collaborator

Choose a reason for hiding this comment

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

Sollten wir noch checken: Was macht das Frontend, wenn die null sind

@awildturtok
Copy link
Collaborator Author

@thoniTUB ich hatte gehofft die initaliisierung über initializer zu machen, aber da läuft es in Probleme, weil wir im LoadingUtil Konzepte mit FailingProviders laden und dann knallt es im resolven. Das ist erstmal eine zwischen Lösung.

(Ich werde vermutlich einmal in die Ids eingreifen müssen, jetzt wo ich mehr gesehen habe wie es funktioniert und wo es hakt)

@awildturtok awildturtok requested a review from thoniTUB December 3, 2024 16:27
@thoniTUB thoniTUB changed the base branch from develop to release December 4, 2024 07:03
Comment on lines +60 to +62
if (extractor == null){
//TODO this is just a workaround: We should actually be using Initializing, which sadly gives us issues with LoadingUtil
init();
Copy link
Collaborator

Choose a reason for hiding this comment

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

Ja das mit der Abhängigkeit hatte ich in den Tests nicht beachtet. Sehe aber auch keine besser Lösung

@thoniTUB thoniTUB merged commit 7ddc6cf into release Dec 4, 2024
6 checks passed
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.

2 participants