i am getting http error on adding collaborator, i'll delete my cache and test again
2021-02-10 04107, 2021
ruaok
`Error HTTP Error Forbidden` while trying to add a track to that playlist, Mr_Monkey
2021-02-10 04135, 2021
Mr_Monkey
Hm. Maybe something not working with collaborating, rather than WS
2021-02-10 04138, 2021
CatQuest
it's working beta?
2021-02-10 04142, 2021
CatQuest
:D
2021-02-10 04157, 2021
_lucifer
websockets working for me now :D
2021-02-10 04117, 2021
shivam-kapila
ruaok: anything in browser console?
2021-02-10 04120, 2021
_lucifer
adding track working as well
2021-02-10 04127, 2021
Mr_Monkey
As collaborator?
2021-02-10 04138, 2021
_lucifer
no as owner
2021-02-10 04149, 2021
ruaok
shivam-kapila: the 403, nothing else.
2021-02-10 04102, 2021
Mr_Monkey
I can't seem to add remove or move tracks as collaborator
2021-02-10 04118, 2021
Mr_Monkey
So that's an issue confirmed.
2021-02-10 04124, 2021
shivam-kapila
_lucifer: can you add me as colab to your playlist you listed above
2021-02-10 04127, 2021
Mr_Monkey
Let me test on prod, see if that's a tregressions
2021-02-10 04103, 2021
_lucifer
shivam-kapila: done
2021-02-10 04149, 2021
shivam-kapila
Mr_Monkey: collab adding didnt work for me on prod
2021-02-10 04152, 2021
Mr_Monkey
I'm getting the same 403s on prod, doesn't seem to be a regression. New WS update feature works for my own playlists, but as collaborator I don't see the changes reflected.
2021-02-10 04153, 2021
Mr_Monkey
I'll debug this collaborator issue locally, but there's no regression I can see on beta ruaok
2021-02-10 04123, 2021
ruaok
should I wait or proceed with the release, knowing that we're likely going to do another one soon?
2021-02-10 04124, 2021
Mr_Monkey
You can proceed I think. Ill get on debugging that today
ERROR: Service 'test' failed to build: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit
No mention of collaborators in the playlist item add/move/delete API endpoints
2021-02-10 04110, 2021
atj
At least it's a helpful error message
2021-02-10 04126, 2021
ruaok
lol, at least we now reminded ourselves.
2021-02-10 04132, 2021
Mr_Monkey
If only the helpful error message made it back all the way to the front-end to be displayed to the user… :)
2021-02-10 04148, 2021
Mr_Monkey
But that's another bug for another time !
2021-02-10 04133, 2021
zas
alastairp: can you re-run jenkins container with --cpus="6" on cage?
2021-02-10 04155, 2021
alastairp
sure
2021-02-10 04159, 2021
ruaok
what was it before? 4, right?
2021-02-10 04112, 2021
alastairp
we configure jenkins to have only 4 workers
2021-02-10 04122, 2021
alastairp
but there's no docker-level resource restrictions
2021-02-10 04112, 2021
ruaok
zas: did you remove the lb dump private files?
2021-02-10 04117, 2021
zas
nope
2021-02-10 04117, 2021
_lucifer
what's the JDK its using?
2021-02-10 04143, 2021
_lucifer
before 8u192, Java didn't play with docker
2021-02-10 04150, 2021
_lucifer
*play nice
2021-02-10 04153, 2021
ruaok
zas: oh, I found them. totally not what I expected.
2021-02-10 04132, 2021
alastairp
_lucifer: 11, I think
2021-02-10 04119, 2021
_lucifer
that's good!
2021-02-10 04119, 2021
_lucifer
i tested locally the python 2 change, adding the header works. thanks!
2021-02-10 04128, 2021
ruaok
zas: on the LB dumps issue: if an old dump fails for whatever reason, we stop the dump process BUT we don't clean up the dirty files. then for the next run, we sync the whole dir and that copies out the failed dump.
