labofsahil/github-event-dataset-2012 huggingface dataset:
Wanted the title to be more obvious that it is two letters in the lesson, and not the lesson "oh".
Нууу
Once we start making Evolve-specific assumptions in cloudfiles, is it still appropriate to distribute it to the world at large? Or should we move this fork in-house and submit more sanitized versions of changes upstream?
Interesting. I *never* knew that method was there :smile:. I've typically used ```.should_not_receive```
FYI, Ruby objects have a method for doing this `is_a?` (also aliased as `kind_of?`) Idiomatically you'd see this as `if config_file.is_a? Hash`.
Concatenating the developer comments with the description is not a bad idea. Unfortunately, when I tested this against a details page without developer comments, the test failed.  You'll need to include an "if dev_comments_message" for the condition that there is only a description and no developer comments.  

I tested this using the search "worldcooler"
that's a good question, i'm not sure. i guess to make it usable out of the box. /cc @joemoore
I think you meant to have `randRange(3, 200)` inside the `parseFloat()`. This is currently just giving me $3.00 for every question.
Uppercase `i`, lowercase `L` and the number `1` can look very similar or identical with certain fonts. In this case, the problem isn't with the number `1`, but I and l.
wonder whether this should be rejected during compilation
Line up these declarations or remove the extra spaces.
Minor point of note: this should be double-quoted for consistency.
change equal sign position
missing a trailing ;
We also should complete the docs for _ConstraintLocation_ and use _@Override_ at the sub classes.
Nope :)  I originally intended to make it a web app, but keeping web out keeps it much clearer.
explain what else happens to the ID (if you dont set one)
This file has been reviewed.
not a huge deal, but I believe in general the case statement should be on its own line, so that the clause is all much more readable. I usually even see a newline between a return or break statement when in a switch block.
`ReflectionClass` can take the object directly.
`dev-master`, correct?
are you sure this regexp is working properly? `-` inside a group (around `[]`) means range, but I'm not whats happens if I put it between these special chars...
I am a little confused about where this , comes from.
Same comment here, both re `set` vs `sorted` and applying it to both sides at the point of the assertion.
Can you remove the wrapper function here?
Can you implement the new CSS style guidelines?
I think you can eliminate this if entirely, and just do `callback(contentResults`
Also, new-style string formatting.
Otherwise it doesn't show up in docs. So it's really just a silly, generic comment to make it show up, if nothing else.
Sorry, that I forgot to mention it in the commit message.
In the `chain``<poller>` isn't handler, so it is logical it that one should be defined as close as possible to the channelю
In the current state of XSD it can be in the any position inside the `<chain>`...
I've found it a bit confusing.
I can make a note about this change in the Migration Guide.
By the way: we have an issue about similar changes: https://jira.springsource.org/browse/INT-2218
I can steal it from Gunnar, if you let, and go ahead as I do it here ;-)
And some little question.
How do you think: is there any reason to document SmartLifecycle support for 'chain' in the Reference? If it's OK, of course...
comma after Support.

also I don't think it should be capitalized

... XML namespace support, ...
But, isn't that the purpose of propagation=REQUIRED? If there's already a tx, we'll use it; otherwise we'll start one and commit for this call.

Of course, it does mean that someone who is using the MS, will now need a txManager bean, but that's probably a good thing.

OTOH, if having the group metadata out of sync with the messages is immaterial, and we have defensive coding for a situation where there's a GROUP_TO_MESSAGE row but no MESSAGE, or vice versa, then I suppose it's ok to be transaction-less.

Seems to me that all the defensive coding, testing, data correction code etc that would be needed can be eliminated with a transaction.
They show up correctly on the github front page but not in this diff.
I don't think this should actually be a semi-colon. The second statement isn't a complete sentence. A comma?
Bit hard to read.
Missed it before. I've changed it since.
isn't that 1.0
Drop the token field - I wouldn't use the AuthTokenSerializer for the response, just for validating the input
For now should I move it back into `_utils.py.TestCase`?
Good point, I also wanted to mention this :)

I'd be fine with either term but I think we should align on one and use this consistently throughout the spec. Could you maybe create a BVAL issue to agree on one term and to streamline the spec accordingly?
I suggest renaming ``create_html`` to something like ``create_index_html`` to be more specific about what is being generated.
Rozliczeniony -> Rozliczeniowy
I am using get_validation_error(array $response) to determine both if there is an error that makes the response ungradable and if there is some feedback that should be given to the student in interactive with multiple tries mode. I will refactor this code as I agree it is messy and difficult to follow. Sorry.
this has been addressed by having you specify a constraint to specify which version to download. A best match will be found between the constraint and all versions available on the site. The best solution will be chosen.

If no version_constraint is specified then the latest_version will be downloaded.
I believe the correct way to document this is ````String|Blob````
This cannot be combine with SOFT_INPUT_ADJUST_RESIZE. If neither is set, the system will automatically pick one depending on content of window
Forgot to remove it...originally it did have some code because it handles the PICKER_TYPE_PLAIN type, but that code was removed.
The actual transformation is handled by the EKB.

When you describe something as future matter. It is better to link to an unfinished manual-chapter.
When we finish the EKB it would be a pain to find all references in the manual that assume it is not finished.
Should we simply use ForceApp.SDK_VERSION?
I do not like it does not use language file. Or it is not able to be used here?
maybe there is a way to handle these exceptions in a more code compact way?
``@return void`` should be removed
Math.random() has 0 arguments ;)
`/var/logs/instagram/instagram.txt`
throw a runtime
needs a check for Ti.version > = 2.1.3 && iOS 6 and do stuff accordingly
Is symfony 2 comming with tests or constants for `GET` and `POST`
checking if the type passed is number or string, will be the solution.