culinko: I'm looking at this and I'm confused, so I'll have to get bitmap involved :)
2019-03-20 07952, 2019
culinko
alright. did you manage to repro the bug with my repro steps?
2019-03-20 07915, 2019
Mr_Monkey
akhilesh: Quite the timing. I'll need to wait for some input from the MB API pros, but there are some aspects of the gist above that you could look at already
2019-03-20 07943, 2019
akhilesh
Mr_Monkey: thanks :
2019-03-20 07913, 2019
Mr_Monkey
akhilesh: Note that the API structure related stuff (lines 23 onwards) might change significantly
2019-03-20 07949, 2019
Mr_Monkey
But I hope this allows you to move forward. I'm here if you have more questions as well
2019-03-20 07923, 2019
iliekcomputers
/var/lib/docker takes up 67G
2019-03-20 07939, 2019
iliekcomputers
pristine--: can you paste the fulllogs
2019-03-20 07902, 2019
Mr_Monkey
iliekcomputers: I seem to remember something about Docker not getting rid of old logs by default, so log files keep growing until you run out of disk space :/
2019-03-20 07914, 2019
Mr_Monkey
Not sure it's related, but there.
2019-03-20 07930, 2019
alastairp
not just log files, but intermediate images too
2019-03-20 07921, 2019
alastairp
but it's unclear from pristine--'s error message exactly what moving part is breaking
2019-03-20 07940, 2019
reosarevok
culinko: yeah
2019-03-20 07910, 2019
alastairp
iliekcomputers: `docker system prune -a` is your friend
2019-03-20 07931, 2019
iliekcomputers
i did a docker system prune and cleaned up 6 GB
2019-03-20 07938, 2019
iliekcomputers
would the -a help?
2019-03-20 07940, 2019
alastairp
-a should clean up more
2019-03-20 07959, 2019
alastairp
you may need to pull/build some images again after that
2019-03-20 07929, 2019
alastairp
are there any stopped but not removed containers hanging around? they may also keep some images from being deleted
2019-03-20 07951, 2019
akhilesh
Mr_Monkey: In line 19, Did you mean that , We will implement search end point on elasticsearch for now?
2019-03-20 07919, 2019
culinko
reosarevok: so far i have found 3 places where the artist name is used instead of AC (all 3 are in the recordings tab) but there might be more, idk whether the same code is reused or such
2019-03-20 07933, 2019
Mr_Monkey
akhilesh: Yes. One GSOC proposal should notrely on another proposal
2019-03-20 07949, 2019
reosarevok
culinko: Pretty sure it's just there, because that's taken from the ws recording search
2019-03-20 07905, 2019
reosarevok
It's just weird in how it only happens in some specific cases
2019-03-20 07918, 2019
culinko
what do you mean by specific cases? i have seen it happen every time the artist has been credited with an AC that is different from the artist name
2019-03-20 07959, 2019
culinko
but only with recording AC (so no RG, release AC, etc.)
culinko: testing locally it seems to only happen sometimes, but maybe I'm missing something. Does it also happen if the artist is not the release artist?
2019-03-20 07924, 2019
iliekcomputers
when i ran this from inside the repo root dir via `./docker/push-master.sh` it errored out.
2019-03-20 07947, 2019
iliekcomputers
but when I added a `cd ..` and ran it from the docker dir (`./push-master.sh`) it worked.
2019-03-20 07948, 2019
culinko
reosarevok: i think so, because first time it happened on a VA release, let me try to reproduce
2019-03-20 07948, 2019
iliekcomputers
weird.
2019-03-20 07915, 2019
culinko
reosarevok: yeah i reproduced it on a VA release just now, re-used the same recording as in my ticket
2019-03-20 07934, 2019
reosarevok
Ok. I'm not sure why it doesn't always work (or well, break) locally
2019-03-20 07946, 2019
reosarevok
I'll talk to bitmap :)
2019-03-20 07958, 2019
pristine--
iliekcomputers: what did that cd .. from inside docker so that it worked out
2019-03-20 07907, 2019
culinko
reosarevok: thanks a lot!
2019-03-20 07922, 2019
iliekcomputers
pristine--: in the push-master.sh file, I added a `cd ..`
2019-03-20 07929, 2019
iliekcomputers
then from inside the docker dir
2019-03-20 07936, 2019
iliekcomputers
`./push-master.sh`
2019-03-20 07906, 2019
pristine--
How did it change things?
2019-03-20 07914, 2019
iliekcomputers
i have no idea.
2019-03-20 07916, 2019
pristine--
Why wasn't there an error after this change
2019-03-20 07919, 2019
pristine--
Okay
2019-03-20 07923, 2019
iliekcomputers
it made the docker image smaller for some reason.
2019-03-20 07947, 2019
pristine--
Let me know whenever you know the reason
2019-03-20 07949, 2019
iliekcomputers
ruaok: when you're back, let's talk about these docker images. :P
2019-03-20 07906, 2019
iliekcomputers
pristine--: workers and masters both have numpy now
2019-03-20 07911, 2019
pristine--
How
2019-03-20 07931, 2019
pristine--
I would like to understand the prob and sol
2019-03-20 07942, 2019
pristine--
If you could explain :)
2019-03-20 07955, 2019
pristine--
iliekcomputers: ^
2019-03-20 07901, 2019
iliekcomputers
i don't particularly understand it myself yet.
2019-03-20 07912, 2019
iliekcomputers
the basic idea is that the images being build were too big.
