yeah, I saw that LB configures watch automatically if mode is development. I see now how that fits in with the builder container - you always want it running. I added a separate command for it so that we could run build:dev once off if you're doing other stuff, or build;watch if you're developing js
iliekcomputers
about the jenkins issue, right now the script `jenkins-test.sh` is in the jenkins config. Maybe we could change the config to just run the script off the git repository instead.
alastairp
if that script is only in jenkins, then I agree, probably a good idea
but you're also right that it raises an interesting question about where files generated during runtime should be kept - in the source tree, or in a separate working directory
I see the value for a working dir, then this could just be another volume somewhere + a config option
we have a setup at the uni where we can start a container as a user that exists on the host. we do it by creating a user in the Dockerfile and then passing in the user's UID and name as env vars. then the entrypoint runs usermod to change the user's name and uid so that permissions work properly on linux, and it looks like you're logged in as yourself
gabbo
yvanzo That's very helpful, thanks a million. I will keep you updated (:
yvanzo It tells me: `sir: error: unrecognized arguments: -e area`. Is this syntax correct?
LB-542: Expose the artist stats on an API endpoint
gabbo
yvanzo Thanks again
yvanzo
gabbo: 'recording' search index takes over 80% of the building time, you might want to skip it if you don't need to send recording search requests.
alastairp
iliekcomputers: btw, not sure if you saw that I removed the use of the manifest file in development, so now you don't have to restart the webserver when the asset hashes change
iliekcomputers
nice, i wasn't aware that that had to be done in AB :D
yvanzo Do live indexing and replication work in my case (not all indexes have been built) ?
v6lur has quit
sumedh has quit
v6lur joined the channel
yvanzo I'm experiencing the same problem when I try to import the artist. Same kind of exception, the procedure won't end .. Should I open an issue?
Zastai joined the channel
Zastai
yvanzo: ping
gabbo has quit
jmp_music has quit
yvanzo
Zastai: pong
gabbo joined the channel
gabbo: yes please, report this issue with as much relevant logs as possible.
live indexing cannot skip a particular search index
gabbo
Ok thank you. Are there other doable ways to access data from MusicBrainz directly offline?
yvanzo
Probably not, but it depends on the info you want to query.
shivam-kapila has quit
Zastai
I'm trying to get mb-solr op and running, and it's proving challenging. Most of my trouble seems to stem from Java 11 vs Java 8.
But also, for the tests: do I understand that foo.xml is the input document, and foo-list.xml/json are the expected outputs?
gabbo
yvanzo I need a way to retrieve the MBID for artists and release-groups. Once I have those, I can exploit the DB version without the search indices to access other information, granted that I have the IDs at my disposal
Zastai
gabbo: define offline. you can download the data dumps and load those into postgres, without setting up the full MB server, and just SQL queries for your data
and if you only want artists and rgs, you can _probably_ import only those dumps
gabbo
yvanzo Offline meaning that I'm currently using the XML WS 2 Apis to do everything I have described before (through the Python library), but that is too slow for my purposes. I need to do so without performing any HTTP calls in the internet
But querying instead a local dump
Zastai
no way to do that and have live data, but if local dump is fine, then you should be able to do as I said - create the postgres db and import the tables you want from the dumps. the you just access pg from python to do lookups there
download and import takes a while (last time I set up a dev vm I let it run overnight)
yvanzo: see above. and I take it foo.xml (area.xml etc) are supposed to be what sir produces? are they supposed to comply with mmd2-schema? (currently they don't; e.g. <lifespan><ended>false</ended></lifespan> is not valid because <ended> can only contain true)
yvanzo
Zastai: tests are not up-to-date indeed.
Zastai
I had to update some maven dependencies (com.sun.xml.bind -> javax.bind for brainz-mmd-schema, and jaxb 2.3.1 for mb-solr)
but the tests are still not running (as in: failing for non-functional reasons), in ways I can't really diagnose properly (for example, the json output seems to be "<0>.")
rather hard to implement fixes for the json output when there is no baseline to work from
and debian no longer ships a JDK8; guess I'll install a third-party one like Adopt, to rule out issues from that angle
gabbo
yvanzo What do you suggest?
Zastai
yvanzo: assuming I have time to work on it, would PRs be accepted to try and get things to the point where they run on Java 11 (brainz-mmd-schema and mb-solr)?
yvanzo
gabbo: I will look into this issue tomorrow, in the meantime mostly what Zastai suggested.
Zastai: It is based on adoptopenjdk you just mentioned.
gabbo
yvanzo Zastai I don't know if I get it right: you suggest to use the dumps with Postgres to retrieve the MBID of Artists and Release-Groups, and, for everything else, use the Offline Server without Search Indices (that I'm not able to build right now)?
yvanzo
gabbo: What do you use to retrieve MBID? Artist’s name? If so, there is no easy way for you to do it right now.
For example, if you had something like a barcode, it would be easy to directly query directly the database instead.
That seems simpler to fix tests staying with Java 8 at first, just follow the easiest path for you, assuming you have time, that would be awesome.
petaaaah joined the channel
petaaaah
Anyway, I could get late entry into GSoC?
gabbo has quit
petaaaah has quit
sampsyo has quit
sampsyo joined the channel
BestSteve has quit
BestSteve joined the channel
supersandro2000 has quit
supersandro2000 joined the channel
chaban
Too many broken links in the timeline graph :( I'll stop filing tickets for now.
prabal has quit
Zastai
yvanzo: not quite up on docker. as for the PRs, the first ones would just be bumped/changing mavend dependencies. for example, brainz-mmd-schema uses a comn.sun.xxx one for jaxb, but that one gets "illegal reflective access" warnings/errors on java 11. switching that to the javax.bind version 2.3.1 resolves that
and fits in better with mb-solr, whih already uses that (it just needs to go from 2.3.0 to 2.3.1)