labofsahil/github-event-dataset-2012 huggingface dataset:
You're right, I don't really know anything about wavelets (unfortunately, the discussion on wikipedia didn't help much). If the concept is too complex to explain succinctly, there must at least be some practical significance that is easy to explain. The reason I ask is that you change levels in the haar vs harris example. What's the rationale? Larger features, less sensitive to noise, some sort of morphological structure to the feature (I'm just making stuff  up here)?
yeah. also i just realized that i need this to be dynamic because i intend to change the fallback dynamic too. then again maybe at this point we just dont have a generic solution and i am better doing a one shot solution for this specific project.
啊，这个还是plugin扫出来的。正则我不太熟，我也不确定是不是所有的/都需要做一个转义。如果结果一样，貌似统一写成转义是不是更好，因为这个正则中有一个/是加了转义符的
I hope this set of cascade targets is complete, but I'll trust you on that one.

I'm wondering if we can wrap this in an M4DBI transaction.
They are, but the parsing can get a bit wonky since it has different css sometimes. Thing is though, the seeds here are like 90% 100mbit+ servers, so the number doesn't really matter here. That's why I always give them a fairly high number of seeds since 10 of these seeds are comparable to, say, 100 public tracker seeds.
insert newline before override
group vars to save bytes
The len can be initialized at the top where the other variables are declared. You can also initialize i = 0 too.
move this hasattr check into the `key_in_fields` assignment.
should be cob_marker
since it is part of the API @Deprecated keeping the wrong value is the unfortunate best solution. Make sure its clearly stated in the @Deprecate comment.
can  you hold off on this change for a moment.
There should be no space before the colon: "Exception catched by Spring MVC: "
redundant control flow. Use

```d
if (lessI >= greaterI)
{
    break;
}
swapAt(r, lessI, greaterI);
```
I would point out that all of std.range and pretty much any range based code is using asserts.
The reason is that it's only guaranteed that c.front, c.popFront, c.back, c.popBack are defined if assert(!c.empty) holds otherwise it's a logic error on behalf of programmer.
Same reasoning should be applied to containers.
Also note that e.g. built-in array's RangeError is an *Error* thus equal in severity & meaning to AssertError.
for now, you could try to copy the original key list. Or take a shot at fixing #146? :)
Fix the module docstring, should be:

```
 EasyBuild support for installing Java, implemented as an easyblock
```
But both were required?
`tag` is final, so compute `tag + " :: "` inside the constructor.
Why the begin/end block?
how about do a range validation for the statusCode here and throw OutOfRange exception if the statusCode is out of range?
same thing regarding po files
no need to use ``else`` as the ``if`` returns.
Есть же `<suffix value="min" />`. Ну или типа того. И я бы по дефолту побольше поставил.
Пробел лишний, если объекта нет.
we don't need to use `-compass-space-list` anymore. Sass provides `()` to construct an empty space-delimited list.
you should add some phpdoc
How about this:

    self.assertEqual(
        [(s.number, s.instruction, s.expected) for s in cv.steps.order_by("number")],
        [(i, s["instruction"], s["expected"]) for i, s in enumerate(new_steps)],
        )

Mostly that's just using list comprehensions instead of a loop, and `enumerate` because its handy. The main functional change is that it's ordering the queried steps by number, as that's actually what determines correctness (they should be ordered in the order they were provided in the source data) - the instruction ordering is just an accident of the specific data you provided (well, I know it wasn't an accident, you did it on purpose, but there's no reason to rely on that).
That's fine and it is related to the later comment you made for which I already replied (had discussion with Mark about that)
Thread-1 sets it to null

Thread-3 establishes a new 

Thread-2 nulls it again

Meanwhile Thread-3 continues with the replyTo reference returned by determineReplyDestination method.
The bottom line is that this.replyDestination is never referenced in JOG aside  from clean up logic and determineReplyDestination method
Don't think so, because its not causing any harm and we have plenty of cases like this in other modules.
The bottom line there is no sideffect and therefore its a warning.
I think having a required `PointField` on a `Place` is a fair requirement.
this.el.hidden = true;

no?
> Darn, I just removed unused arguments in all datastream.js functions. PyCharm colored them gray, it was ugly. :)

Please put them back. The problem is that in JavaScript it is really hard to do introspection. In Python you can find fast which all arguments are possible to the function. In JavaScript, this is hard. So I found it much easier to always write them out, so that later on when I go and want to add something, I am not reinventing wheel when I think that something is not available, but it is. Especially when using functions which you do not know much about. (But the writer of original/initial code hopefully does.)
Why do we need to make a string copy here?
@apex13 done
Can you remove the extra white space
the way you write it is confusing. It looks like a function signature whereas it is an event name
I think yo can use `form_for [:oauth, application]` instead or not really?
You may want to wait and confirm the instance is truly gone before proceeding to another test.
Do you have to register it?
Very good remarks. I think I understand now. Yes, in fact EmbeddedListField and EmbeddedSortedListField are something else than mongoengine's SortedListField. For both of those it seems you could use SortedListField, or ListField. Depending on what you would want.

My question is then: why would you ever use EmbeddedListField instead of EmbeddedIndexedListField (or however we name it)? First if you want to access list elements by _id, second if you want to access it by index? I think I agree we have to rename this (I would not bother with backwards compatibility as this is still in very early development). And much improve documentation.

For other things: could you make another pull request with tests for all errors you find? It can be pull request with just tests which fail. You do not need to fix all. :-)
This way the example and sentence itself is placed much better :-)
this is broken as the CLI cannot know the base url (you are not reaching it through the webserver) and so it will always be empty
I'm gonna pull this. I like the logic and the configurability.

But I wouldn't ignore another pull request that fixed the spacing to be a bit more consistent :D :D :D
Why didn't you use `Array#inject`?
SyncKeys in ActiveSync are temporary. It seems that the way the server works is that it has a cache of N syncKeys per folder (and per device?), where N is pretty small. Older sync keys get expired, and if you try to use them, you have to resync the entire folder from scratch.

We also can't (easily) use the FilterType option, since that really means "filter". It will notify you of soft-deletion of messages over time as they pass out of range of your filter. That's probably not the right thing in general.

We can, however, restrict the number of results we get from a sync command. The specs recommend 100 at a time, but we could change that.

The thing that concerns me in particular is that we may sync an entire folder, and then the user might delete an old email via another client, and then we'll be notified of it next time. If we haven't loaded the block containing that message, things will be harder for us. (I think?)
This is true only on IOS. On Android it is probably fired when the button is clicked.
add a reference to the figure please
makes sense .. @dbu what version label do we want to give the transport interface?
more more question .. do we want to make it sort of a standard to postfix such virtual packages for interfaces with ``-implementation`` or something shorter?
Is this value always required?
If yes, the block is fine, otherwise, you can use isset in the condition.
Tämä ei toimi, jos lyhyin sekvenssi ei olekkaan ensimmäinen. Loppuehdon tulisi olla:
~~~clojure
(if (some empty? tails-seq)
  mapped-seq
  ...)
~~~
you cannot make the assumption that the key value exist. each filter can generated its own elements. Can you make it abstract ?

Of course child classes need to implements the ``isActive`` method
Aaaaaarrrrr noooooooo !!!!!!!
you should add the newline at the end of file. This makes the diff nicer and is part of the Sf2 CS (the ``check_cs`` script adds them)
too desperate to get this merged :P
BB10 C++ guidelines say that we are not allowed to have inline functions in the headers, need to move the implementation to the CPP file
You should actually be checking for this at the beginning shouldn't you? Like return value of 0.

Also shouldn't you be checking for local:// or does that not need translating?
remove this in favor of above
Ympäröivä `if` on tarpeeton. Lausekkeella `(== (mod n divisor) 0)` on jo haluttu arvo.