labofsahil/github-event-dataset-2012 huggingface dataset:
It would be better to make it "smarter", i.e. with `{% if page.tagline %} <small>{{ page.tagline }}</small>{% endif %}` to get rid of the `<small>` tag...
I started initially with playing dtype bool might break stuff in scikit learn. For instance you cannot call `.toarray()` on the output directly:

```
>>> CountVectorizer(dtype=np.bool).fit_transform(['aa ab ac', 'aa ad']).toarray()
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
/home/ogrisel/coding/scikit-learn/<ipython-input-12-098d15b0686c> in <module>()
----> 1 CountVectorizer(dtype=np.bool).fit_transform(['aa ab ac', 'aa ad']).toarray()

/usr/lib/python2.7/dist-packages/scipy/sparse/coo.pyc in toarray(self)
    219         B = np.zeros(self.shape, dtype=self.dtype)
    220         M,N = self.shape
--> 221         coo_todense(M, N, self.nnz, self.row, self.col, self.data, B.ravel())
    222         return B
    223 

/usr/lib/python2.7/dist-packages/scipy/sparse/sparsetools/coo.pyc in coo_todense(*args)
    170         npy_clongdouble_wrapper Bx)
    171     """
--> 172   return _coo.coo_todense(*args)
    173 
    174 def coo_matvec(*args):

TypeError: Array of type 'byte' required.  Array of type 'bool' given

```

Furthermore it breaks  tf-idf transformation (even if combining binary occurrences with TF-IDF transform might seems weird, I don't see a reason why we should prevent it).

```
>>> Vectorizer(dtype=np.bool).fit_transform(['aa ab ac', 'aa ad']).toarray()
array([[-1.,  0.,  0.,  0.],
       [-1.,  0.,  0.,  0.]])
```

This particular breakage can probably be fixed in the `TfidfTransformer` class though.
chera `!important` gozashti?
If you think it makes more sense to put it there. I'll go do that now.
//cnamespace psd
You probably don't, but it's Android's native logging behavior that we wrap (and he is documenting here)
but we don't have one. :/
This is actually correct. We can do a suffix check and then `-[NSString floatValue]` actually parses the string up to the first point where it can't reasonably establish a floating point number via lookahead, i.e. spaces are removed and it would stop before the units. Probably also faster than manually removing whitespace and then doing a check.
```
    if (this.deleted) {
      rec.payload.put("deleted", true);
    } else {
      …
```
--> getBaseUrl
I decide to use instance variables here because it depends on puzzle and submission to build url, so I don't want to pass those when we call render partial. Is it bad to use instance variables in view partial?
The one thing I considered (but haven't thought all the way through) is that we could simply let the FactoryBean always return the channel from getObject(). It either looks it up or creates it. Clearly, I must be missing something though, because that would be very simple.
Убрал проверку при каждом обновлении страницы. -10мс (на моём компе) при загрузке + плюс меньше нагрузка на сервера гитхаба.
These two methods should be one.  They should return a generic object which is a QueryResult<T> where T = VersionInfo.  Pattern this object off of EntityHeaderQueryResult (and replace that object with QueryResult<EntityHeader>).  Then, have the manager do user access checking.
Dunno, I just went with consistency (see the sidebar on the site). I have no problem with leaving it as changelog if you prefer (ironically, Chrome's spell checker flagged that ;).