#musicbrainz-devel

warp: bots aren't always auto-editors as well

nikki: yeah, I figured as much... but wasn't sure. thanks for confirming ):

:)

warp: sorry for the additional work due to the invalid bugs, but maybe you should update to update you documentation to state clear for which entities ratings are available

-update

well, releases don't have ratings. why would you think you can request something through the webservice which doesn't exist? :P

jensl: I've clarified it for lookup requests (browse requests already had "except for releases").

since releases have user-ratings, but indeed that is something else

no

and for labels, i thought that for consistency reasons the XML element rating would be 0

releases don't have any ratings nor tags.

jensl: in general, the webservice tries to omit information which is set to some kind of default, to save bandwidth.

ok

warp: whatever everything is clear for me now :)

I'm not always happy with that choice, but considering the amount of traffic we get, I can understand it.

ok

jensl: anyway, no problem with the bug reports.

jensl: is there anything new for me to checkout yet?

:)

jensl: we planned to meet before the meeting today, right? around 20:00?

maybe 20:30 if you think we don't have much to discuss.

included and pushed the paypal library but have to setup the sandbox environment to test it

20:30 is fine

ok

I'll do a checkout around 20:00 and have a look at things.

ok i will have the new artist and release details view almost finished then

cool

warp, hi

ijabz: hello

U stil having problem building annotation index (SEARCH-32)

yeah

is there something broken on my end?

Are you sure youve got the latest code are you using subversion or the git mirror thingy

subversion

Revision: 12795

Try mvn clean then do mvn package

but the last version I have is 12790 !

Oh i see 12791 -12795 are for other projects

Well just try out the mvn clean and let me know

ok, will do that.

did you get anywhere with http://jira.musicbrainz.org/browse/MBS-794

[INFO] There are test failures.

hello, I'm trying to set up search server according to http://bugs.musicbrainz.org/browser/search_serv...

when I do mvn install it says "Cannot execute mojo: resources. It requires a project with an existing pom.xml, but the build is not using one."

I'm not really familiar with whole java technology.

fixing it.

OS is gentoo, maven is 2.2.1

oh, sorry, cd to brainz-mmd2-jaxb fixes it :/

ruaok!

hi!

i iz bak!

happy belated birfday!

ohai

hi

ruaok: thanks :)

djce: I spent a bit of time hanging out with the postgres team in the last week.

can haz less vlc requests? :-D

awesome foks, really.

djce: I throttled those down even further when we were tweaking the DB.

I think I noticed that, a few days ago yes?

but VLC has already fixed how the use MB. We just need to wait for the next release.

ok

a week ago, yeah.

VLC released a new version a couple of days ago actually

navap: oh good.

navap: re the N1. can I ship the monitor there too?

it would be much easier even if only for customs.

hmm

navap: you flying or driving?

if flying its clear....

Across the border is by car, but I'm taking the amtrak from buffalo to NJ and back.

of screw that.

I'll ship the monitor.

It's probably a hell of a lot cheaper to ship that domesticaly though, isn't it?

yep

The thing is I usually end up going back with more stuff to carry then on the way there, the monitor will add to that :(

I know the feeling, trust me.

socks.

and müsli.

:)

navap: I'll just ship the monitor to ca.

you may need to cover the import taxes though.

Hmm. I'm trying to get a playable version of my work up, but now I'm having server issues again and don't have physical access. Curse you, technology!

but the N1 going to NJ is a good idea.

wow. test is still up. that colo install was supposed to be shut down over the weekend.

oh well.

Leftmost: if you have stuff on code review, we can just merge that into next and update test.musicbrainz.org.

djce: wrt our DB problems. its likely table on disk fragmentation that is our problem.

ok. need to read up on how to check/fix that then

we need to determine if the problem exists with a just a few tables or if it s a widespread problem.

if its just a few indexes (possible) that cause most of the fragementation, we can rebuild the indexes in place.

if its widespread, we need to dump/reload which will take 2-3 hours. :(

ttfn!

Hmm. What's in code review has some unresolved issues for discussion, and probably wider discussion.

Leftmost: you can update the review with a new diff.

Leftmost: anyway, if you point me or aCiD2 at a branch which resembles whatever you put up for review, we can merge that into next.

Right, but they're issues that at the least I need to talk to aCiD2 about.

he should be back by now, right? :)

srsly.

room for a slacker?

yay!

of course!

:)

I got the contract today btw ruaok, do you want that posted or faxed?

that'll be best for me, I don't have/know anyone with a faxmachine

Shlacker, as they might say in Cork.

jensl: ping

warp: ack

yay!

warp: only artist search might work for now, but you can click through until a release

warp: I refactored the artist and release detail pages and introduces the release groups in between

yikes, the rating starts are huge

:)

ruaok, if the 3g is supposed to work regardless of the network, what are we worried won't work on whichever network I go with?

aCiD2: post please/

jensl: the release groups still need 'album', 'single', etc... headings?

ruaok: ok, great

will be in the post tomorrow