mayhem: i took a look in the listens in spark but couldn't find listens with this mbid or even any having `a forest` in the track name. its possible the mapper matched this to some other mbid causing your submitted mbid to be overidden.
regarding dupes in recommendations, that is a known issue no? and we have filters in daily jams to tackle this.
i'll have to check to confirm but i don't think spark has any specification against recommending the same thing multiple times. could do a distinct items query in post processing but at least for daily jams purposes troi handles it already i thik.
vibhoo_24: best to ask monkey when he is around later today.
mayhem: oh i found the entries now all are `|2022-12-23 10:14:56|1 |A Forest - 2006 Remaster|null |`, so mapping issue i think.
vibhoo_24 joined the channel
jivte joined the channel
Thuraabtech joined the channel
jivte has quit
jasje has quit
jivte joined the channel
jivte
lucifer: Hey can u tell what to do when a module doesn't contain ts module declaration file
lucifer
jivte: module as in some external library?
jivte
yeah i installed a third party module for datetime
as soon I start using it the deadly white component appears
:(
lucifer
first option would be to check if there is a corresponding types module for it. what's the library you want to use?
(I'd still suggest dropping remaster more generally if you don't already, but that's I guess a different issue then)
reosarevok plays https://www.youtube.com/watch?v=JRtFHNen20M
jivte
lucifer: thanks for the help i found out my bugs :)
mayhem
lucifer: moin!
I think it would be good to remove the dups from the recs -- this will become a problem for other things and I would very much like to remove them just to be sure. please do that.
lucifer
morning!
mayhem
and maybe next week or so, I think you and I should tackle the mapping and move a couple of things forward.
Freso
alastairp: Pong
mayhem
namely, improving our detunings, so that that case above and lots of other cases are improved.
vibhoo_24 has quit
and releases in mapper -- a couple of days of concerted hacking could be good.
lucifer
mayhem: fix for dupes already deployed currently generating new recs to confirm it.
monkey, alastairp ^ so I put the basics into the codebase.
monkey: how did you set up the actual docs page for the BB API?
Would be nice to do that for MB so that as I work on this people can actually try it and give suggestions
monkey
Using two neat packages: one takes JSDocs and transforms them into swagger definition, the other serves the Swagger live docs website using expressJS (the web server framework we use)
Maxr1998_ joined the channel
So it integrates automagically into it
Maxr1998 has quit
alastairp
morning
reosarevok: amazing! thanks
reosarevok: lucifer was looking into compiling swagger to html and serving it as static files, he might be able to help
I split them into separate files because it would be ridiculous otherwise, but maybe the process to turn them into a static file needs to combine them, dunno
lucifer
monkey, reosarevok, alastairp: its possible to embed swagger docs in the readthedocs if wanted. (pending some issues with theme)
reosarevok: yup, i mean you can embed in a html page. just serve the openapi json schema file from some publicly available url.
alastairp
reosarevok: I think that multiple files is a good idea, especially if there are entities which are 90% the same but with just a different entity name. it could be possible to automatically generate these included files from a template
reosarevok
I expect descriptions and whatnot are going to be different for every entity (one of the best things about this is literally that you can customize the descriptions very nicely and show them as appropriate for every entity, so we can document how each include plays with each specific entity type for example)
akshaaatt: facing this issue thats described here : debugImplementation("androidx.fragment:fragment-testing-manifest:1.6.0-alpha04") androidTestImplementation("androidx.fragment:fragment-testing:1.6.0-alpha04")
I still don't understand what the issue is jivte. What is the result you see? VSCode warnings? Compilation failure with webpack? Something else?
A single index.d.ts file for typings of a library is the most common pattern.
jivte
yeah but like in date-picker library nostyles.d.ts file exists it is not there
but no worries by declaring it in utils we got it covered.
monkey
By declaring it in utils you're declaring a dummy typing, which means no typing help in your editor or at compile time, so definitely not the ideal result :)
I'm happy to try to help you resolve the typing issue properly, but you haven't given me enough information to do that at the moment. What's the actual error or warning you're getting?
Thanks jivte that's helpful. And so you get the same message after installing the @types/react-datetime-picker library? I think the issue could be simpler and have to do with webpack not being aware of the new package. Can you try rebuilding the docker image for the static_builder container and trying again?
vibhoo_24 has quit
jivte
monkey: already tried rebuilding
monkey
The command would be `./develop.sh up --build static_builder`