reosarevok sighs at an unexpected ISE http://tickets.musicbrainz.org/browse/MBS-9063 - I thought the dates would get dropped automatically here :/ I guess I can remove them with one edit then enter the other change, but I guess I'll leave it be for testing for now
2016-08-31 24445, 2016
Nyanko-sensei joined the channel
2016-08-31 24404, 2016
D4RK-PH0ENiX has quit
2016-08-31 24458, 2016
Mineo has quit
2016-08-31 24408, 2016
reosarevok
Also I wonder why suddenly almost 20 people decided to like our FB page, we normally get like one per day
(however, all of these are public, so that's back to the first point)
2016-08-31 24405, 2016
kartikgupta0909
but for private, only authors would know the job id right?
2016-08-31 24417, 2016
kartikgupta0909
in case we allow public datasets to have jobs?
2016-08-31 24421, 2016
kartikgupta0909
*private
2016-08-31 24436, 2016
alastairp
yeah. With UUIDs it's a bit less of a problem
2016-08-31 24453, 2016
alastairp
since the probability of generating the same uuid is almost 0
2016-08-31 24413, 2016
kartikgupta0909
yes
2016-08-31 24430, 2016
kartikgupta0909
so should I change something and add somekind of error handling or is it fine this way?
2016-08-31 24435, 2016
alastairp
for example, if we had integer ids for our job ids, we would want protection to make sure that no one iterated through the all ids
2016-08-31 24450, 2016
alastairp
the reason that I was thinking about private datasets is this:
2016-08-31 24452, 2016
kartikgupta0909
yes that would have been a problem
2016-08-31 24434, 2016
alastairp
for now it's not a problem, but if we ever change this decision, we have to remember all the parts of the code which access datasets, and add this check
2016-08-31 24453, 2016
alastairp
I can imagine that we perhaps forget all the places where this could happen, and so we end up with a bug
2016-08-31 24423, 2016
alastairp
however, if we do it now, it doesn't matter if we make the change in the future
2016-08-31 24449, 2016
alastairp
the downside is that we have additional complexity here, which will stay forever
2016-08-31 24452, 2016
alastairp
hmm.
2016-08-31 24459, 2016
alastairp
Gentlecat: got any thoughts on that?
2016-08-31 24419, 2016
Gentlecat
huh?
2016-08-31 24422, 2016
Gentlecat reads
2016-08-31 24433, 2016
ruaok
alastairp: got a sec?
2016-08-31 24435, 2016
kartikgupta0909
I dont see a problem even someone tries to access a job of a private dataset
2016-08-31 24448, 2016
kartikgupta0909
since this API end point doesnt demand the dataset to be private
2016-08-31 24402, 2016
kartikgupta0909
its simple retrieving the job from the dataset_eval_jobs table
2016-08-31 24406, 2016
Nyanko-sensei has quit
2016-08-31 24407, 2016
alastairp
right. I'm not talking about the case as it is at the moment
2016-08-31 24414, 2016
alastairp
ruaok: what's up?
2016-08-31 24420, 2016
kartikgupta0909
ah
2016-08-31 24430, 2016
alastairp
because in this case we know that all jobs are for public datasets
2016-08-31 24433, 2016
D4RK-PH0ENiX joined the channel
2016-08-31 24433, 2016
Gentlecat
alastairp: I think I made a change to allow submission of private datasets because of challenges
2016-08-31 24437, 2016
ruaok
I'm not ready to put up a PR for the big-query stuff yet, but I wanted to catch you up.
2016-08-31 24440, 2016
Gentlecat
that might be in my own branch though
2016-08-31 24444, 2016
ruaok
its been an interesting set of challenges.
2016-08-31 24446, 2016
alastairp
Gentlecat: ah, interesting!
2016-08-31 24401, 2016
alastairp
that makes my crazy ranting valid!
2016-08-31 24413, 2016
Gentlecat
so yeah, need to make sure that user owns the dataset before retrieving it