labofsahil/github-event-dataset-2012 huggingface dataset:
Yes. This will be fixed in next iteration. Together with new command features.

On 29. 09. 12, at 12:21, Mitar <notifications@github.com> wrote:

> In tests/test_project/test_app/templates/demo.html:
> 
> > +                <tr>
> > +                    <td>Metric</td>
> > +                    <td>Granularity</td>
> > +                    <td>From</td>
> > +                    <td>To</td>
> > +                    <td>Elements</td>
> > +                </tr>
> > +            </table>
> > +        </div>
> > +        {% endif %}
> > +    </div>
> > +    <script type="text/javascript">
> > +        $(document).ready(function () {
> > +
> > +            var to = new Date(2012,8,19,12,0,0,0),
> > +                from = new Date(2012,8,13,12,0,0,0);
> Hmm. This is hard-coded? Is this why it does not display anything to me when I start with fresh database one?
> 
> —
> Reply to this email directly or view it on GitHub.
> 
>
Beware here, the name of the file and the public class are different. This is not the java way :D
No there wasn't, I didn't mean to include this in the pull request. I didn't know it would automatically add commits I make after the pull request. I'll remove this. I needed it because some of the rc files were not valid ASCII or UTF-8, thus had to be read as binary in order to work at all, which is a separate issue
the most important part here is that this is an immutable POJO
Ok, as long as we are aware that these properties are case sensitive. @kwallis .
@jeffheifetz and i were actually discussing this the other day. There seems to be some properties that are case sensitive and some that aren't.
Seems weird to suggest 0.6.20 here when we are telling them to install 0.6.10 above. We suggest 0.6.10 above because that's the version that works on Windows. I suggest we leave it as 0.6.10 for now. When i do my 0.8.14 support pull request we can reference that version.

I will add the period.
I think we may be a little overdoing the niceness of having these various commands. I don't think this is required here.
this is a bug - datasources.tex doesn't exist and from the context it's apparent that you meant appendix.tex
Get rid of this constructor, we shouldn't be able to construct a scheduler message without tagging it with the id of the controller.
Any chance you can format all of these so that SIGNAL and SLOT are aligned? 

Like:

blah, SIGNAL,
blah, SLOT
That is correct, but why do we need the script on the repo?
I agree on the text.erb files, the a.sh is the one I don't see the purpose.
A controller may hold multiple blocks, check to make sure that b is smaller than nextAvailable before replacing.
we want question to be immutable, ie you can't edit it once it is created. Maybe one way to do this is to check to see if self.id is not None (ie there is already an object in the db) and if so create a new object, rather than update the existing one.
If we don't do this, when we are outputting a persons answer to a question, the question could have changed, and the answer will no longer be relevant.
Any idea what errors?
I thought users could write that src= part whenever they needed. I didn't changed src= argument processing
@bryanhiggins Yes

@haahmad []'s denote an optional property, this is a bizarre situation where they are both optional and necessary
избавляемся..
I don't see the test :-) It should be: reject package version if not subsequent when incremental version is true
> This should probably say: the base trait <tt>OverridesEquals</tt>, correct?
right. We changed the name from Base to OverridesEquals, but I did that change not consistently.
Created https://jira.springsource.org/browse/INT-2590
This line should be part of the line above. You cannot divide one html tag into 2 lines according to coding guidelines.
that's not how we log exceptions
and this again should be a namedtuple instead of a dictionary
En nog een keer!