Mr_Monkey: So I was looking into that issue of relationship editor in which the search suggestions are not shown properly. But the problem is I cant see the console log statements since it is rendered on the server side. Now for that I thought to use the debug-watch-server script (hoping it would help in debugging this issue), but it doesn't seem to start elasticsearch on its own. So I am stuck here for a while now. Any help would be
2019-11-09 31302, 2019
abhishekpanwar
appreciated.
2019-11-09 31331, 2019
abhishekpanwar
It might be a noob issue
2019-11-09 31358, 2019
abhishekpanwar
Just tell me if I am going in the right direction?
we have a query named "all_stats_all_users" and it doesn't need any params
2019-11-09 31311, 2019
iliekcomputers
so we send {"query": "all_stats_all_users"} to rmq
2019-11-09 31312, 2019
ruaok
good thinking, we should preserve params. 🤣
2019-11-09 31318, 2019
iliekcomputers
:P
2019-11-09 31338, 2019
iliekcomputers
then we have a query "all_stats_for_user" and it needs a user
2019-11-09 31359, 2019
iliekcomputers
so we send {"query": "all_stats_for_user", params: {"user_name": "blah"}}
2019-11-09 31328, 2019
ruaok
ok, I see where you're going and I think I like it.
2019-11-09 31347, 2019
iliekcomputers
here each query just seems like a function call to me and we don't have to do any specific logic.
2019-11-09 31353, 2019
ruaok
I kinda dislike how both our approaches have a special case for "all".
2019-11-09 31348, 2019
ruaok
ah, but when there is a 1:1 binding from request types to functions, then it comes together nicely.
2019-11-09 31355, 2019
iliekcomputers
yes!
2019-11-09 31322, 2019
ruaok
ok, let's do that.
2019-11-09 31327, 2019
ruaok
let's talk about naming stats.
2019-11-09 31346, 2019
ruaok
I think each stat should have a clear and unambiguous name.
2019-11-09 31352, 2019
ruaok
artist_stats -> shitty.
2019-11-09 31302, 2019
iliekcomputers
I agree.
2019-11-09 31308, 2019
ruaok
top_artists_per_user -> good.
2019-11-09 31314, 2019
iliekcomputers
I'd also like to have a description for each stat anyways.
2019-11-09 31336, 2019
ruaok
does that get stored at lemmy or spark?
2019-11-09 31339, 2019
ruaok
I'd say lemmy.
2019-11-09 31358, 2019
iliekcomputers
hmm. not sure.
2019-11-09 31317, 2019
ruaok
it is user facing metadata. that belong to lemmy, IMHO.
2019-11-09 31327, 2019
ruaok
spark should be the dark magic voodoo stuff.
2019-11-09 31352, 2019
iliekcomputers
hmm, i don't think i have an opinion either way. if we enforce a 1-1 mapping, lemmy works for me.
2019-11-09 31307, 2019
ruaok
ok, bake it so.
2019-11-09 31351, 2019
iliekcomputers
+1
2019-11-09 31334, 2019
ruaok
how do I indent that line?
2019-11-09 31343, 2019
ruaok
I want to make a sub-list.
2019-11-09 31314, 2019
iliekcomputers
tab works for me?
2019-11-09 31327, 2019
ruaok
ah. the obvious thing. lol.
2019-11-09 31341, 2019
iliekcomputers
listing all the stats is a good idea!
2019-11-09 31319, 2019
ruaok
I just wanted to capture some examples on how the requests should be formatted.
2019-11-09 31338, 2019
ruaok
but, lets make a list of stats too.
2019-11-09 31332, 2019
ruaok
chhavi arrives in BCN tomorrow. I hope I can rope her into some graphics work for us. :)
2019-11-09 31351, 2019
iliekcomputers
that'd be amazing.
2019-11-09 31326, 2019
iliekcomputers
LB already has react so it'll hopefully be easier to add graphs this time around.
2019-11-09 31335, 2019
iliekcomputers
😅
2019-11-09 31349, 2019
ruaok
yes.
2019-11-09 31312, 2019
D4RK-PH0ENiX has quit
2019-11-09 31313, 2019
ruaok
ok, I think the spark consumer is well enough defined for my taste now. what do you think?
2019-11-09 31331, 2019
iliekcomputers
i agree.
2019-11-09 31336, 2019
ruaok
ok, onward.
2019-11-09 31352, 2019
ruaok
and yes, for staring the container on the spark side of things we should define and run a new servicem similar to how the master service is defined.
2019-11-09 31305, 2019
iliekcomputers
do we need a different service?
2019-11-09 31328, 2019
ruaok
I don't recall the specifics right this second.
2019-11-09 31348, 2019
ruaok
might just be a singleton container and not a service. I'll have to dig a little more.
2019-11-09 31310, 2019
ruaok
but for now I am comfortable saying that we'll start the service according to how services are started now, extending things as needed.
2019-11-09 31314, 2019
ruaok
and not bringing in consul.
2019-11-09 31337, 2019
iliekcomputers
hmm. sounds good.
2019-11-09 31353, 2019
iliekcomputers
do we have any sensitive data in the configs right now anyways?
2019-11-09 31305, 2019
ruaok
ok, I see things breaking down into two larger groups: write the consumer and all the admin BS around running and connecting both ends of the consumer.
2019-11-09 31318, 2019
ruaok
not on leader, we don't.
2019-11-09 31319, 2019
iliekcomputers
yes, totally agree
2019-11-09 31328, 2019
iliekcomputers
with the breaking into two groups.
2019-11-09 31356, 2019
ruaok
so, wanna take care of whipping the consumer into shape while I take care of the other tasks?
2019-11-09 31312, 2019
iliekcomputers
definitely what I was hoping for :P
2019-11-09 31331, 2019
iliekcomputers
this sync was really helpful!
2019-11-09 31332, 2019
ruaok
right. what else needs discussing before we dive in?
2019-11-09 31344, 2019
ruaok
yes, I feel like I understand the task to hand now.
