-
Notifications
You must be signed in to change notification settings - Fork 21
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
Rerendering cluster names #769
Changes from 3 commits
0f930c2
5b760c5
7547bb7
fe590ad
bbd92c3
97bc35b
27aa734
c8271d2
e0ac266
e34d7b4
7e3d585
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -106,7 +106,13 @@ const fetchWork = async ( | |
getState, | ||
optionals = {}, | ||
) => { | ||
const { extras = undefined, timeout = 180, broadcast = false } = optionals; | ||
const { | ||
extras = undefined, | ||
timeout = 180, | ||
broadcast = false, | ||
clusterNames = undefined, | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. why not using these There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. FetchWork function is used for fetching every work, clusterNames are something specific to just some of the fetchWork calls, then why would we want to introduce a new parameter for fetchWork that is relevant only to some work types? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is exactly Agi's point which I agree with. I put the cluster names in the dot plot's work body where they are relevant. I also didn't like how I did it initially but was not sure how to pass them otherwise. I think now it should be good |
||
} = optionals; | ||
|
||
const backendStatus = getBackendStatus(experimentId)(getState()).status; | ||
|
||
const { environment } = getState().networkResources; | ||
|
@@ -135,7 +141,12 @@ const fetchWork = async ( | |
} | ||
|
||
const ETag = createObjectHash({ | ||
experimentId, body, qcPipelineStartDate, extras, cacheUniquenessKey, | ||
experimentId, | ||
body, | ||
qcPipelineStartDate, | ||
extras, | ||
cacheUniquenessKey, | ||
clusterNames, | ||
}); | ||
|
||
// First, let's try to fetch this information from the local cache. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think you should get the values here
clusterNames
here. Implementing it here would add another parameter to be passed tofetchPlotDataWork
. I think it would be better to attachclusterNames
inside the body request body that's generated for this plot.