-
Notifications
You must be signed in to change notification settings - Fork 26
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
Show wk user in vx workflow list #7794
Conversation
conf/application.conf
Outdated
jobsEnabled = false | ||
voxelyticsEnabled = false |
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.
as always ;) dont forget to remove!
@@ -77,14 +77,16 @@ object ChunkCounts { | |||
|
|||
case class WorkflowListingRunEntry(id: ObjectId, | |||
name: String, | |||
username: String, | |||
hostusername: String, | |||
hostname: String, | |||
voxelyticsVersion: String, |
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.
upon first sight it seems to me that the naming convention is mixed here (snake case vs. camel case vs. all small letters). Would this be an opportunity to unify the properties or is it on purpose?
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.
Yes, feel free to camelCase this stuff!
Also, hostusername can probably be thrown out, as the frontend does not display it anymore?
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.
alright, I'll do that! actually the user name on the host is displayed if the wk user couldnt be found, so it is still used. is it okay if I keep it in?
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.
Ah now I see the left join. Ok fair, if we want to support the rare case of a deleted user. However, in this case the type in scala needs to be Option[String]. And please test locally once that the query still behaves correctly if the user is missing/deleted.
But yes, then let’s keep the hostusername in as a fallback.
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.
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.
Backend LGTM. I’d suggest to remove hostusername from the case class and query, as it is no longer displayed.
@fm3 I renamed the scala class members as discussed in the other thread. This lead to a few changes, can you have another look? I tested it locally and everything seems to work like before. |
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.
front-end looks good to me 🎉 only left one remark about proper sorting. will leave the final approval to @fm3.
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.
Backend LGTM and re-testing looked good :) Feel free to merge after addressing Philipp’s latest comment
This reverts commit 21e08f8.
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 only found one small thing that might have an effect on the correctness of these changes, but I am not sure 🥴
filterSearch: true, | ||
}, | ||
{ | ||
title: "Hostname", | ||
title: "Host", | ||
dataIndex: "hostname", |
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.
The prop hostname
was renamed to hostName
right? But not here? is this maybe something?
Steps to test:
TODOs:
Issues:
(Please delete unneeded items, merge only when none are left open)