zas: Hi, Can I please have a login on trille (critiquebrainz) and gaga (LB timescale)?
iliekcomputers
shivam-kapila: i'm hesitant to do too much with very basic components like loaders and pills
it leads to stuff getting flashy for flashiness sake
but i'll leave it up to you
shivam-kapila
I also dont want it to be too funky
Butr the current loader doesnt look so good
iliekcomputers
also, the less code we have to maintain over time, the better
shivam-kapila
or we may wait for BS4 migration and use the inbuilt one once we are there
iliekcomputers
if a BS4 migration takes more than a day or two's worth of work, i don't see it happening anytime soon
shivam-kapila
I guess it will be
Actually the thing which makes me feel to change the loader is that:
1. The current loader is a little ugly icon
2. There are 5 loaders currently on report page itself so I aim to replace it with a simple decent loader that covers the page and when the components are ready show them
iliekcomputers
yes.
i'd prefer a simple circle
shivam-kapila
shall I go with the npm package I pointed and use its simple circle animation?
iliekcomputers
sgtm.
thansk
shivam-kapila
thanks
Mr_Monkey
+1 for simple circle
iliekcomputers: Are the websockets irremediably broken then, for suggesting we do polling?
iliekcomputers
i'm not sure. i don't remember if we made it work with the listens page.
did we?
Mr_Monkey
It was definitely working at some point, and updating the page.
iliekcomputers
i see
Mr_Monkey
Not sure exactly how that would work now if we navigate to another page (probably would just add it to the top of that page)
iliekcomputers
we should open a ticket if it's broken.
Mr_Monkey
OK, I'll do that
iliekcomputers
thanks!
Mr_Monkey
Here it is: LB-679. I also created LB-680 and assigned it to myself, to integrate working solution into the current navigation mechanism.
that image will need to be pushed to docker hub some time, too
white_shadow joined the channel
yvanzo
alastairp: we usually have two approvals before merging but this one is such a small pr :)
alastairp
that's OK, I approved it too ;)
white_snack has quit
white_shadow has quit
zas
alastairp: try to log in trille & gaga
alastairp
zas: login key and sudo works. thanks
Mr_Monkey
ruaok: Do you agree with mine and shivam-kapila's conclusion that we should implement the automatically-search-in-bigger-time-range mechanism (if listens count < requested count) in the `/user/XXXXX/listens` API endpoint?
ruaok
Yes, I do.
Mr_Monkey
Currently, PR #992 removes the mechanism from the front-end (the "Search Larger Time Range" button), and there is no existing way to request a larger time-range from the API (using for example a time_range param). It also makes sense to do it automatically on the API endpoint rather than do another API call…
OK
ruaok
But,what is the logic behind expanding the range?
Mr_Monkey
I'm not convinced I'll be able to implement that in python without setting the whole thing on fire, but I'll give it a try. I might need help with special cases (such as "no, really, you only have 10 listens, no need to look for more")
ruaok
If fewer are returned, search the whole range?
gr0uch0mars
ruaok: evaluations sent! I had it in mind for today, but could’t do it this morning