labofsahil/github-event-dataset-2012 huggingface dataset:
@zstone I'm not sure if it's obvious how to use JSON inside scikit-data in a natural way.   however, could you comment on the split scheme currently proposed in the code?   I just added support for non-standard splits. I put the split related data in the dataset init, because we might want to have the split data travel with the dataset instance.  The current code has the idea that to change splits, you have to re-instantiate a new instance (or I guess, monkey around inside the code; probably the various attributes should be private).   What do you think?
Almost all of these defines are no longer used.  When you update a file we need to be diligent about removing unused defines.  From my count, the following are not used: combine, destroyObject, Cartesian4, Matrix4, ComponentDatatype, IndexDatatype, PrimitiveType, PolylinePipeline, BufferUsage, BlendingState, StencilFunction, StencilFunction, SceneMode, PolylineVS, PolylineFS shallowEquals
Sounds like a plan.  At some point I'll switch gears back to the CZML spec side rather than the implementation side and we'll review things like this.
as long as this utility belongs to the spi or is inside the Router, I think it is ok. Maybe, instead of passing the view, we should pass the svg and the path to this utility object.
Method name misspelled
Cache children to a var
Eu acho a sintaxe do symbol melhor do que a de string. Mas e so opiniao. ehheheh
Really?  I think that works fine in most ruby code...
actually Doctrine DBAL creates the default workspace automatically as well.
Yeah fair enough I guess. Requireing it in the interface just ensures that anything requiring the interface implicitly requires an actual implementation, because without it the interfaces are kinda useless, but I see your point too.
Wrong "it's." It's "its."
Static arrays have the syntax `type[in­te­ger]`. `int` does not follow that syntax at all. It's a completely different type. There is _nothing_ in the spec which supports the idea of zero-dimensional arrays. Rather, anything that you would consider to be a zero-dimensional array is explicitly talked about as having a completely different type (e.g. `int`, `float`, etc.). And _nothing_ in the standard library supports the idea of zero-dimensional arrays - precisely because they _wouldn't be arrays_. Try `__traits(isStaticArray, int)`. It's `false`. The language quite specifically does _not_ consider anything to be a zero-dimensional array - be it static or dynamic.

You're proposing something fundamentally different from how arrays are ever treated by the language or by Phobos.
I'll just remove those line-separators. I prefer to not use multiple unittest blocks because this unittest block basically jus tests the whole visit function.
is it possible to remove the container here, and pass the "multilanguage", "defaultlocale" en "request" parameters/objects
This could be expressed a little more clearly as:
    
    if video_summary and video_url
        "#{video_url}\n\n#{video_summary}"
    else
        video_url || video_summary
    end
s/it's required/you need to/
I think 'bundle' is unwanted here?
Is it worth including the comment with the ticket number so that the `grep` command I listed will return nothing?
Cool, indeed. I'll fix this now.
Remove this entirely
match at least one char.

1.9.2p290 :001 > ".png".match(/[^'"]*\.[a-zA-Z0-9]{3}/)
 => #&lt;MatchData ".png"&gt;

1.9.2p290 :002 > ".png".match(/[^'"]+?\.[a-zA-Z0-9]{3}/)
 => nil 

but you are right about the greedy match.
so [^'"]+ would be better as it would match foo.bar.png too
Yes, it does exist in 2.1-stable. Take a look: https://github.com/EllisLab/CodeIgniter/blob/2.1-stable/system/libraries/Upload.php#L1093
same here for the empty line
The left and right padding will give you some trouble once you add the tabs to the section. See localhost:5000/course for what I mean. You're better off putting it on the h2 instead of on the whole section.
what is the naming scheme here, 6 lines above, service bus management is called ServiceBusManagementService, here service bus is abbreviated as sb.
If this is only a problem on Linux platforms (with certain glibc libraries), should we do this substitution only on Linux?
What happens on OSX, for example?  Does the double one slow things down?
Drop the prefix.
@lsmith77 do you know if this is the right way to do things? simply setting this value in the app/config/config.yml parameters: section would result in the same. do we want to explicitly expose some but not all classes as configuration?
Pretty sure this breaks windows users because HOME there starts with `C:\` or something like that. I think a better approach is to rescue the `ArgumentError` that gets raised from `expand_path`.
I would even like it better if this check could go away from the main library, because moveTo looked much simpler before Renderer.NG. The ```redraw``` below could even go away entirely. e3d137754c4d2f0e77127cda715cdf10863f1928 was the change that added it.
I think that the rule should be something like "Project MUST NOT mix tabs and spaces for indetation". It would be compatible with almost all projects, I think.

And if you use PHPCodeSniffer to check your CS then there is no difference between using tabs or spaces. PHPCodeSniffer supports both.
Can we change this to `margin: 0;`
You can remove the `!== 0` here, as that is implied by it being in a conditional. 0 if false-y in javascript
Hmmm... when I originally created this utility class, I had this method and your comment was the method should take a BeanResolver, not a BeanFactory because, "while we currently only have 1 BeanResolver...."

I guess you had a change of mind :-)
why is this attribute still here?
I was not aware of that; thanks for noting.  Would it be sufficient to set `this.viewDate = new Date(date.getTime())`?
Didn't we decide we don't want to use authorization headers for sending keys? Is this just temporary?
Fair enough. I'm not very attached to either value :)
The above is awkward. I'll rephrase on merge. Considering I wrote the original, it's my bad. :)
Should this inherit from `object` rather than some test class?
Путь выделить при помощи ` ` `
yeah, we need something. Currently, it would simply break.

Btw, I would put show before edit in the order, as I find it more logical to display the item than to edit it again when you complete the edition
That's a long time ago! Has there been any change since such that these could be tested now?
This is new, created the polyline implementation for openlayers
Good, but RSpec and SimpleCov should be namespaced for "test".

Furthermore, all "require sdl" should be converted to bundler, and spec_helper must change too.
inexistent -> nonexistent
Instead of forcing users to call default_handle manually, instead we could use a Module.add_compile_callback to automatically add the `default_handle` before compiling the module.
If(x.y) will only evaluate to true, when y is truethy, so defined and neither null nor false. Therefore it should work the way i supposed
:mod:`numy.linalg`
This is just for logging purposes, no big deal
This specifically tells the doc generation system not to generate a *standard* static factory method (which in this case would be Ti.XML.createCDATASection).
I'll leave it up to the author's discretion on if this is feasible, but with values that are enumerations or virtual enumerations, (Text alignment, button type, etc) we might be able to make a meta-type like what we do with optional arguments. That is, type here is 'UITextAlignment', and the UITextAlignment type is defined elsewhere as one of three values, allowing us to dodge the exact nature of the constant while keeping the constants in close relationship to functions that use them.
why using ``number`` as parent ? Use ``date`` as parent and you will not need to add anything in ``buildForm`` as all will be inherited
can you explain the purpose of doing this? it seems like bad design that would cause a scenario where this is needed.
Please also provide an *INFO* level log message, informing the user whether the SAXON library is being used or not.

Not sure whether we really need to test for the Sedna libraries being present. SAXON is probably sufficient. Also, since Sedna is an external XML database, users will have to provide more detailed XQDataSource configuration parameters anyway (username, database name etc.). Thus, you can probably only try to discover SAXON.
No, the new callback will mean you don't have to handle the logic of removing the callback. You will still need to handle this since you need to trigger the correct callback.
The top two are constants, the bottom one changes depending on orientation.
I think its fine this way, I checked some other extensions (io, invoke, notification) and they have to JSON.parse on the index side as well.
only use select * if you will use 100% of the data returned.
CS Need blank line before return