IQSS logo

IRC log for #dataverse, 2017-12-19

Connect via chat.dataverse.org to discuss Dataverse (dataverse.org, an open source web application for sharing, citing, analyzing, and preserving research data) with users and developers.

| Channels | #dataverse index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

All times shown according to UTC.

Time S Nick Message
08:09 jri joined #dataverse
08:13 jri joined #dataverse
11:23 jri joined #dataverse
12:29 jri joined #dataverse
12:37 jri joined #dataverse
15:20 pameyer joined #dataverse
15:37 jri joined #dataverse
18:34 jri joined #dataverse
18:39 pdurbin pameyer: I see you made some commits on https://github.com/IQSS/dataverse/pull/4370
19:02 pameyer pdurbin: yup
19:09 pdurbin pameyer: you don't patch grizzly?
19:09 pdurbin I'm looking at https://github.com/IQSS/dataverse/commit/06c5767
19:10 pameyer it's not bulletproof; but it works
19:11 pdurbin cool
19:11 pdurbin I think I'm going to clone fresh to make sure the deps are really built on the fly for me.
19:12 pameyer that should work
19:12 pameyer deleting `dv/dep` should work too
19:12 pdurbin sure, but I'm paranoid
19:12 pdurbin :)
19:18 pdurbin hmm
19:18 pdurbin docker: Error response from daemon: Conflict. The container name "/dv" is already in use by container "adb505218f64092190c6786818214f113​f89a9daa8aeb328bb5f182be445aa18". You have to remove (or rename) that container to be able to reuse that name.
19:18 pameyer `docker rm -f dv`
19:19 pdurbin pameyer: thanks! After running that, this worked: docker run -d -p 8083:8080 --name dv dv0
19:20 pameyer one possibly non-intuitive thing with docker is that stopping a container doesn't remove it; with all of the talk about containers being disposable it's sometimes easy to forget
19:21 pdurbin I'm not even clear on the terminology. Stop, remove, kill, shutdown, terminate. Who knows what anything is called. :)
19:22 pameyer just wait until you discover the joy of dangling images / dangling volumes
19:23 pdurbin I wouldn't be in this business if I didn't enjoy learning new things.
19:24 pdurbin tests running
19:24 pdurbin BUILD SUCCESS
19:24 pameyer :)
19:25 pameyer I'd be curious how your timing worked
19:25 pdurbin Total time: 01:32 min
19:25 pameyer for running the tests, or the whole build image -> setupIT -> run tests?
19:30 pdurbin oh, oh, that was in the output of `mvn test`
19:31 pdurbin I didn't time the various steps. How long have we been talking? :)
19:31 pdurbin Maybe it took me 10 minutes or so.
19:32 pameyer on my system, ~5m for building the image, and 1-2 minutes for each of the other steps (prep, setup, mvn test)
19:32 pameyer but my dev system doesn't have the fastest IO
19:33 pameyer glad to hear it worked for you :)
19:33 pdurbin I already have all the maven artifacts cached, which I'm sure helps.
19:33 pdurbin yeah, I moved it to QA
19:33 pdurbin Thanks for automating the creation of the deps. That was the main thing.
19:35 pameyer I lost steam on combining that with how vagrant and your docker images do it; but maybe something to consider in the future
19:36 pdurbin I guess I'm still slightly confused about Solr... at what point you stick the schema file in place.
19:36 pdurbin I guess I'll go look.
19:36 pameyer yeah - that part is confusing
19:36 pdurbin (The thing about stuff being automated is that you no longer have to care much.) :)
19:36 pameyer part of using the non-stock solr zip was that I was putting a custom schema in there
19:37 pameyer then I realized/learned that it's one of the things I was frequently iterating on, so it should be separate
19:37 pdurbin It looks like you copy the schema over in 1prep.sh. That's fine.
19:42 jri joined #dataverse

| Channels | #dataverse index | Today | | Search | Google Search | Plain-Text | plain, newest first | summary

Connect via chat.dataverse.org to discuss Dataverse (dataverse.org, an open source web application for sharing, citing, analyzing, and preserving research data) with users and developers.