labofsahil/github-event-dataset-2012 huggingface dataset:
Este es un punto de debate, para este TP si usan mmap haces que el bitarray sea una dirección al archivo. Entonces cualquier modificación ya se ve reflejada y no tendrías problemas de sincronización.
Si lo duplicas, tendrias que estar recreando el bitarray a cada rato o al menos haciendo memcpy de lo que esta en el disco al array.
dialog = widget.dialog()
    dialog.open()
    dialog.close()
If you put "```" before and after your code, it looks like code. (Fixed it for you.)
Yeah, we should have it so you only have to put in one `<div>`; it's not only easier/neater, but also future-proof (we can inject new stuff into it when we want things to change).

Also, is there a reason for the TitleCase stuff? ids and classes tend to be lowercase with hyphen/underscore separators in most of our stuff -- and most html/css I've seen in the wild as well.
I don't really care which you pick, but I'm just saying that `can not` is very outdated grammar and `cannot` or `can't` should be preferred. (http://www.dailywritingtips.com/cannot-or-can-not/)
i'm far from being a lawyer but I don't think it's that easy. While it looks fine for an app. But not for a standard lib - it should be included alongside with boost in all stuff based on Phobos:
Copyright © 2001-2012 Python Software Foundation; All Rights Reserved
I'm not sure everybody is okay with that. Also note that there is no distinction between source form and binary both should include notice.

@andralex  We gotta enlist somebody fluent with copyrights and licenses to look into this.

> P.S. - To be safe, you could rename the function to something else, e.g. calcMinRun.

What that supposed to mean? Of course it's not the question of names, it's a question of being a derivative work that you yourself admitted.

To be honest I personally don't give a damn about license issues (and hate 'em with passion) but it is important to clear this up for the commercial use of D.
Yes, exactly. XXE likes to reformat the file as it seems.
I assume this line is too long for our checkstyle checker
I think it's not so hard to update the test to work properly; in addition I would rather prefer to delay it another 2 days before merging something with broken/no tests...
don't you think that this can become a problem?
I created class "inline" that we can apply to all the labels in this situation.  Seems to work fine.
Yes, I am familiar with content classes from System.Net.Http namespace, but I have decided not to use them. I wanted full control on the buffer or stream, and I did not want extra functionality provided by HttpContent class.
I see... but I actually think it'd be just more consistent... This sort of comment for attributes seems weird / harder to read, wouldn't you agree ? If we're not using standard, might as well not include any at all... (but i'd still prefer the standard format :))
________________________________________
From: Aliaksei Baturytski [reply@reply.github.com]
Sent: Tuesday, March 27, 2012 9:36
To: André Rodrigues
Subject: Re: [azure-sdk-for-net] Public HttpResponse class (#28)

> +using System.Collections.Generic;
> +using System.Linq;
> +using System.Net.Http;
> +using System.Text;
> +using System.Threading.Tasks;
> +using NetHttpMethod = System.Net.Http.HttpMethod;
> +using NetHttpRequestMessage = System.Net.Http.HttpRequestMessage;
> +
> +namespace Microsoft.WindowsAzure.ServiceLayer.Http
> +{
> +    /// <summary>
> +    /// Represents an HTTP request.
> +    /// </summary>
> +    public sealed class HttpRequest
> +    {
> +        private NetHttpMethod _method;                      // HTTP method verb.

Got it. This is a private member visible only to the class members; it won't be included into any autogenerated documentation. Adding a standard header here would be an overkill.

---
Reply to this email directly or view it on GitHub:
https://github.com/WindowsAzure/azure-sdk-for-net/pull/28/files#r610008
Same here (don't change existing migration).
Right so you need the flag in order to differentiate in the CommandAwareRpcDispatcher between the commands you need to sed with total order flag set to tru and the ones you don't beed to. It sould be cleare if you add a flag to the the CommandAwareRpcDispatcher.invokeRemoteCommands method (there's a comment below on that).
It is being set in the initialization function, I'll leave it here to avoid confusion throughout the widget.
Should be on
check line 488.

I have:

if(prepareCommand.isOnePhaseCommit()) {
  markTxCompleted();
}

actually, I can change to set the condition to: if (isOnePhase() || exception). What do you think is better?
But this function has no params?
I'm not a fan of long dox with "*" prefix on every line. Emacs can handle that stuff well (and from what I can tell you're using it), but it's just not as friendly as plain text. Will merge this in though.
Artem, Gunnar - I can do the minor refactoring during the merge (description to a variable etc).

Artem, Can you point me to the "recommendations on your previous commit" - I looked at the canceled PR and only see something about using XOR for mutually exclusive atts.

While I agree consistency is best, I would tend to avoid a change like that this close to a release (we want to get RC1 out today).
Just looked at it again, I don't think its the right name (even though its internal). Spring already has a Resource strategy and quite a few implementations of it so this one may mislead somebody. Also looking at the code it really should be called something along the lines of  FileMessageHolder
Hi,

yes, sorry it would just be a pull.
Ok, please let me know about it.
Doesn't work; is() requires a selector.

On 29. 09. 12, at 12:33, Mitar <notifications@github.com> wrote:

> In tests/test_project/test_app/static/test_app/js/datastream.js:
> 
> > +        var add_metric = undefined;
> > +
> > +        if (options && options.metrics) {
> > +            options = $.extend(options, { 'datastream': {'metrics': options.metrics }});
> > +            delete options.metrics;
> > +        }
> > +
> > +        if (options && options.add_metric) {
> > +            add_metric = options.add_metric;
> > +            delete options.add_metric;
> > +        }
> > +
> > +        this.options = $.extend({}, $.datastream.defaults, options);
> > +        this.placeholder = placeholder;
> > +
> > +        if (placeholder.children('canvas').length > 0 && add_metric) {
> Or placeholder.children('canvas').is().
> 
> —
> Reply to this email directly or view it on GitHub.
> 
>
Good for wrap the rest of fields to fix a reasonable line length!
Can you pin the version? Thx
Did you mean `read-only-1` instead of `read-annotate-1` in the #comment and $command, to match up with the preceding `joingroup` command?
Implement `IEnumerable<T>`, not `IEnumerable`.
Maybe we move the retrieval of this out to a function which you could override?

I'm 85% ready to go on instance based javascript refactoring which is probably a better target for such a use case because it should allow you to replace certain functionality easier.
I'd just reuse the same secret.
I swear I ran this quite a few times. I'm not sure how it worked... I'm confused. Changing it anyway.
Yeah I was conflicted about leaving the named param; I had taken it out since the post_create_instnace method by default creates 2 instances (json and xml).

I just added back the named param.
You might want to consider using a transient SchedulerProtocolet in here, this will eliminate the need to do a lg(n) lookup everytime we want to reply to a message.
public SchedulerMessage(String method, SchedulerProtcolet handle) {
    super("scheduler", method);
    id = handle.getId();
    this.handle = handle;
}
I thought about that. I thought would be sufficient since Set and Array both implement the same interface. I can add tests if you like. One is probably enough. The ArraySerializer itself has enough tests (right above this one in the code).
the docstring with the Attributes might also need to be updated to specify the shapes
I'm down for the last option as it will be more efficient if you're right about the call to values being expensive, although I'd rather use parens over curly braces if it's all going to be kept on one line.
Not sure. The original idea was that any only the user who created the redaction would be able to assign redactables to it, but I'm now not so sure whether that's an unnecessary restriction. What do you think?
null checks shouldnt be required anymore
Oops - I'll write this code in a minute...
The later versions' artifacts aren't yet uploaded to the nexus repo
It's not a parent class of anything.  "Used for representing a file on the device's true file system.  This differentiates it from TiResourceFile, which represents a file inside the application's resource bundle."
Another option might actually be to check and see if the size is below a certain threshold, and then have a fixed value (10?) for handling that.
yes. fixed it. Thanks for reporting it.
I personally agree though it *might* cause confusion down the road. Using common over blog doesn't (IMO) add anything besides a naming conflict and potential problems. I think that files should properly be namespaced. So I'd rather keep `blog` or change it to `blog_common` if we expect more panguage files. Using "common" also doesn't make sense if there is only a single language file for the whole blog.
It's worth trying. I don't run `mvn clean` for the same reason. I'll 
push any changes once I get it working.

On 12-03-2012 14:43, Aslak Knutsen wrote:
>> +<scope>test</scope>
>> +</dependency>
>> +
>> +</dependencies>
>> +
>> +<build>
>> +<plugins>
>> +<plugin>
>> +<artifactId>maven-antrun-plugin</artifactId>
>> +<executions>
>> +<execution>
>> +<id>setup-glassfish</id>
>> +<phase>process-test-classes</phase>
>> +<configuration>
>> +<target>
>> +<get src="http://download.java.net/glassfish/${version.glassfish}/release/glassfish-${version.glassfish}.zip" dest="${project.build.directory}" usetimestamp="true"/>
> Could we use a Maven Artifact here instead, to avoid having to re-download for each mvn clean ? e.g. http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.glassfish.main.distributions%22
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/arquillian/arquillian-container-glassfish/pull/17/files#r544454
You're right. I actually like starting on a new line better; I thought PEPs said otherwise. Instead, it says, "The summary line may be on the same line as the opening quotes or on the next line."
No abbreviations for names
We need it to complete fully before the other code executes, since the parent is queried in task Complete and a null return value is unacceptable.