labofsahil/github-event-dataset-2012 huggingface dataset:
`ax.imshow(label_image, cmap='jet')` ? Or do you want it with another colormap?

When I execute the script within Ipython, the jet colormap is used by default, but I built the doc it showed with the gray colormap, which is not as nice for this example. Don't know where the difference comes from, but the safest is probably to fix the colormap.
You could also use the plt.cm.spectral colormap, which is handy for this type of thing.
What are the Doctrine coding guidelines on `use` statements? I did this to keep in line with the rest of the file. Related: I've seen other parts of Doctrine use a single multiline `use` statement instead of separate statements like this.
One downside here is that if intermediate directories need to be created, they won't have permissions applied to them. Is that OK with you?
This function should take an optional `result` parameter.
I would think `var p = ray.getPoint();` would return the origin, but I agree with you so this is OK with me.
Should it throw an exception in 2D instead of ignoring the method call?
What is the longest value you can use?  If people need to define these ids externally as part of Fabric, then it should really be a GUID in order to enfore uniquess; of course we can internally map the GUID to a counter variable at runtime so that we have instance based uniqueness across runs.  I still need to read up on exactly how Fabric works and probably have design review comments rather than just code comments.
I'm actually OK with keeping them if we can rationalize it.  It is so much cleaner, and how often do we access frozen objects?  In the grand scheme of things, will freezing affect performance?  The safety it provides is pretty important.  Maybe we can leave them in for now and for the other Cartesian and Matrix updates, and then benchmark some higher-level functions like triangulation, ray intersections, etc. and see if we need to remove the freezes.
Maybe I didn't get your question yesterday, sorry. `bus = bus || EventBus()` looks more consistent to me
I wonder if we should remove an existing section and always add a new one to ensure its shape is exactly as we need it?
Why are we not calling this condenseMessage like in the java implementation?  Small thing but figured using the same function naming in the case of mirror implementations makes sense unless there is a reason not to for the sake of clarity.
Define "attached." ;)
I think this line is superfluous in terms of Android and iOS. However, I will need to speak with you about what you mean for MW. Would you mind pinging me when you are on IRC?
Thanks
Nope, was not necessary, has been removed
Start comments with an uppercase letter. If the comment forms a complete sentence, use a period.
This is a really good example of magic numbers. I have no clue what those numbers are.
The folder should probably better be created in a tmp directory and not in the source directory.
this says keystone service. I guess that answers the question of how you got started :)
@classifiedadventures: It was pseudo code, so yeah I probably got the logic wrong. ;)

@parndt, @radar: WDYT?
It's just fine with CTFE as it is. I even added CTFE tests after the initial version (which lacked the `__ctfe` branch above) didn't work with std.format, because slicing the `ptr` wasn't valid in CTFE. I don't know why `strideImpl` doesn't just assume that `core.bitop.bsr` exists, but based on what Alex said, all of the compilers have it, and it works just fine with CTFE, so I think that we can just use `bsr` and not worry about it.
why is this defined here? could be defined at initialization.
Then subtly introducing bugs (from what I read)? Of course. 
As someone firsthand introducing a bugprone usage pattern into std.regex.
Now I'm seeing that getting "foreach over all matches" is bound to fail on the first try.
(however it was forced mistake because of trying to get full backwards compatibility)

I encourage you to go to great lengths to reduce the surprize rate of users. 
That could mean anything of (from the top of my head):
a) make both equivalent
b) disallow one form as in "static assert/@disable/private", keeping backwards compatibility 
c) or something else, maybe analyzing how users work with Appender as of now.
@klickverbot, yes template are great!
Probably you will be happy then with [unstd.templates](http://denis-sh.github.com/phobos-additions/unstd.templates.html) and [unstd.generictuple](http://denis-sh.github.com/phobos-additions/unstd.generictuple.html) just like I do as `unstd.generictuple` eliminates a need to learn different function sets for dealing with ranges and generic tuples.
I'm not quite sure how that works... Sorry, could you enlighten me?
An entity is (very simply put) an object representing a line in the database; in this case the entity is a node which represents a page. An entity should not be left in charge of routing duties as it has nothing to do with it, it should be handling data from a database entry and try to not incorporate too much business logic. From my point of view, if you need to do routing it's best to add a new router service (see chainrouter.md) with a priority that's higher than the slug router.
I actually tested it in dart2js + chrome and it works!

 It fails in FF though. It fails really early (matchesSelector is not implemented correctly there, which is used by the polyfill script)
Can you add a new line here?
I don't think you're even doing this.  As written, you can't assume that the argument to `onRecordStoreSucceeded` has *any* data attached to it.
nit: it's not an interface.  For forms and tabs, this is an inner class -- I would prefer it be inner to your PasswordsRepositorySession.
OK, got it now :-)
it is, i added this for the one day it took it to get to central and forgot to remove it.
Yeah... laziness.  fixed.
I think that's right, but I think we still also want to bind the weasel id to a thread local. we don't want to need to pass this data hash to every function that might conceivably want to log...
not part of this patch, but we should change AbstractCliCommand to not use the "aliases=[]" and in
the init just set it to [] if not specified
Hmm, not sure where XML got in there but that brings up a good point.  Why not XML support?  OpenStack tried to cease XML API support and was quickly attacked by the portion of the community that is heavily invested in XML web services.
change to

```
sources = ['mcl-%s.tar.gz' % '-'.join(version.split('.')]
```
i think you need to add that method to the interface too
Are the extra line breaks here intentional?
Why take this version out?
This appears in master as commented out.  Any reason for that?
maybe wrapping with <emphasis>Spring Integration 2.2</emphasis>
Went ahead with 'store-payload-as-single-value' for now
Unfortunately the library is a little frankenstein-like in terms of spaces and tabs. It was originally written in tabs, but I'd prefer to migrate towards spaces. The idea would be that as soon as a method gets a non-trivial rewrite, convert to spaces. I'd rather not do a wholesale conversion in a single commit.
Do we really want to change this to just download?
Need to update the comment - should be reload
> Yes. This will be fixed in next iteration. Together with new command features.

OK, but it is still strange to have to tell specific start and end dates. For example, for wlan slovenija, we will probably want to define graphs like "display last one week of data" and leave to library/API to figure what this is out.

But maybe you are right that this is something user of the library should figure out automatically, maybe not library itself. Think about it, what is the most common use case. So in our case, it is "1 week old", and not "from there to there". We will probably never initialize graphs like that. So library could be helpful here.
look into eliminating the callback URL in favor of a relative URL.
The idea was to use the same message object to send emails with different contexts. This is why render() method was called from send(). There probably should be optional context paramter in send() method to reflect this.
You removed such ability by moving the template rendering part to template property setter. If you want to avoid the repeating rendering for static context, it would be better to check for context change on send().
That makes more sense.  I'm doing that now.
Do we need this? A TCP shutdown will implicitly cause the shutdown routine to be run in the protocolet. We can override the shutdownCallable to send an internal message to the scheduler thread.
its fine its a not a big deal, lets move on to more important things :)
be akharin span ke ro div e akhr hastesh hatman padding-right bede
We should probably change this to `showData` or something given that it clearly no longer toggles anything ;-)
what happens if you don't do all this? Does it not use the defaults on its own?
the knife command assumes you have a UI. Since this is library code I would prefer library functions. The knife command was written pretty shitty, it should have library code that we could tie into and then the knife command should wrap around that.

Using the knife command wouldn't prevent our code from breaking when it's in the users hands because we lock to a specific version of Chef. Opscode also versions their API and wouldn't want to break compatibility with other version of Knife - so I don't think this is a real problem.
What does this mean? Does it mean that this proxy can not be created programmatically?

The user can always do `var cdata= doc.createCDATASection(String data)` where doc is a Document and data is the data you want to store in the CDATA section
don't specify commons version (simply remove it)
Suggest a brief sentence to introduce the second diagram.

For outbound endpoints, the second thing to consider is timing while interacting with the remote server.


You would then drop 'Secondly," from the para below.
No. This is against the point of events (also, the module is not aware of the events that exist in the codebase).
Степан, а зачем скрипт сначала изменяет, а затем удаляет этот `input`?
I can do that, the impact isn't to big but if you want it, i'll do it, just for you
remove lock from name