labofsahil/github-event-dataset-2012 huggingface dataset:
See comment in roxierowbuff.hpp
I moved the call to useINotify out of the loop entirely.  The logic will now fall back to using old method if <code>inotify_init()</code>fails.
This is related, but not exclusive for the unit tests. It tries to load with "lib*.so" around if the load fails, and is here because the unit tests (which supposedly was working on Windows), did the load by library name, rather than file.

Also, I can't tell the unittests to load "libfoo.so", or it'd stop working on Windows.

This happens only on failure, so it shouldn't affect anything else.
please add the trailing comma so that next updates of the array don't need to edit the previous line to add a comma (see the difference between the diff here and in the Yaml driver where the comma was there)
Can we not use hash instead? E.g. `if (location.hash === '#advanced')` or something?
細かいけど、因果関係が逆だよね。ディレクトリはそれ自体にサイズは持っていないので、属性としては不要。
サイズを求められた場合には、配下のファイルを合計して算出する。っていう向きだと思う。
Added in 6a0d1dc36860f0c39d54aa2ca4b75acf68a366df.
Can you store `element.ownerDocument.defaultView.getComputedStyle(element, null)` in a local variable so that we don't need to repeat that?

Also, you could use an `if` with `||` so that you don't need to repeat the `return false`.
hmm so this is how hogan partials work? or for "real" hogan are they html fragments?

Express has no notion of partials so if they were to be relative to ./views (or the "views" setting etc) 
the user would have to be explicit
Sorry, missed that last time, but `SystemExit` is not thrown anymore. We can simply make it an `except` and handle any other failure which occurs here. Or does the outer method is already doing that?
is this related to the bugfix?  the publisher is so wonky that I am actually sorta nervous about this change...
define HD44780_BL in pinning as output so DDR macro is obsolete here
Change this to "ArrayUtils::iteratorToArray()" (see #880 for more details)
Same as https://github.com/zendframework/zf2/pull/804/files#r472262
The `Zend\View\Model` interface states that an `ArrayAccess` (not `ArrayObject`!) or an array is returned... Not sure if it is safe to cast directly here...
Odd, that blank line 196 isn't in my source.
prepareLoggedMessage used to support both string and array for msgArgs.
And we have a couple of places where we use a string instead of an array.

Either we change other classes or we allow strings in prepareLoggedMessage
would love to know where it is specified that the header cannot be empty. I know in practice it is rare, but reading the standard doesn't give me the reference. (http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html ), thoughts?
You can use self.where(...).first_or_initialize and save yourself the next line where you conditionally assign entry again. See handle_callback in the CanvasOauth2Controller.
Perhaps compiled CSS doesn't belong in our repository anymore. We may want to just have the LESS, then compile it to CSS in our local clients. We can add a Paver command to make it easier.
`(contains? author :death-year)` might be a better check. You could also do `(not (:death-year author))`.
Gotcha. I should've checked.
nothing major, something to do with ipv4 and ipv6 support. Feel free to ignore.
add curly brackets please
80980 : Dolibarr ERP/CRM admin/tools/export.php Remote Command Execution
I think, once the new "rop version" of the exploit is approved, it can (should) be deleted.
Good catch, fixed this even though in the discussion it still shows as being there.
Really nice having test cases - but still need that header :-)
I kind of hate to say it, but this should have a test even if it's just a trivial test that checks constructing with the default values.
There are a bunch of allocations here and below that I'm sure @mramato will be thrilled with.
Shouldn't we throw is `extent` is not defined?
I'll offer one rebuttal.  If these functions are hot-spots, then they should always be passing in a result parameter and not creating a new instance each time.  Since not passing in a result parameter results in the "slower case" then it's okay to initialize the properties twice.

That's just me playing Devil's advocate.. just say peep and I'll make the changes.
this class has a lot of whitespace formatting problems.  Please convert the spaces to tabs.
We run our code through minification which reliably strips out white space, but doesn't reliably group var statements.
Just a suggestion -- it isn't strictly necessary to use Iterator<String> here, you can also use for-each style:
```
for (String key : legacyLocationProviders.keySet()) {
    //..
}}
```
This is not really a change in the API. Local paths have never worked for these cards. Should I still use an ```@apiNotice``` tag?
Sorry, I didn't clearly describe my use case. What I need to override is the factory NOT the RepositoryFactory. The line you highlighted is the one that creates the RepositoryFactory factory service (which could be RepositoryFactoryJackrabbit or the doctrinedbal option). The pull request I submitted overrides the "factory" that the RepositoryFactory uses to build the transport.

If you open the Jackalope\RepositoryFactoryJackrabbit class then navigate to the getRepository method, it takes the following parameters:
- jackalope.factory
- jackalope.default_header
- jackalope.jackrabbit_expect
- jackalope.check_login_on_server
- jackalope.disable_stream_wrapper

The DI extension of the bundle has support for some of the parameters, but the "jackalope.factory" is not there.
would you ever get a HerokuServiceException.NOT_ACCEPTABLE and have the app actually created? i.e. is destroying actually needed?
What are you setting it to if the key doesn't exist? This description could be improved. 

Also, this test doesn't seem to check that the value for a non-existent key is 1. Perhaps this could be broken into 2 specs: one spec should test that a key that exists has a value that's incremented by 1, the other spec should test that a nonexistent key has a value of 1 post-incr.
this has already been implemented using signals
JavaScript seems good, even though y'all know I'm not a fan of the capital S :)
I have horrible visions of ruby 2.8 10 years from now. Can this check for '1.8' explicitly instead of 'X.8'?
Yeah, I decided to go with "baby steps" approach and fix issues one at a time and while at it also fix all the style and bad practices issues.
Never mind. Comment was already there :). Sorry.
What is p?
Даже так?
nit: you could use `randRangeExclude( roundTo( 0, MEAN - STDDEV * 3 ), min( roundTo( 0, MEAN + STDDEV * 3 ), 100 ), [ MEAN ] )`
можно не делать. он и так вызовет
seeded is fine as long as it's a property
Would be nice to merge it with analogous exception in std.variant but that probably can't  happen.
prolly not, so it's better to use a straight for loop and use ror.front.length
Hm, I found a good explanation about that.

A `@property` attribute just affects to the function *name*, not affects to the function declaration *itself*.
And, if the name annotated with `@property` is used like a variable, it is allowed. If the name is used like a function, it is disallowed.

Practically we might need some additional rules, but it is a principle explanation, in my opinion.
How about we change these to something more like

> format's current implementation is scheduled for replacement in January 2013. It will then be replaced xformat's implementation. This will be seemless for most code, but it will make it so that the only argument that can be a format string is the first one, so any code which uses multiple format strings will break. Please change your calls to format accordingly.
I expected such a redundant implemented code, too. When you accept my claim, it will be difficult to avoid it. Thank you for your work!
@andralex, as you see people again mixing `ElementType` with template programming. It was a major mistake to reject my pull #776.
And, as always, I don't see any mistakes in my opinion and it is opposite to all other *phobos* devs opinions...
Probably true.  I haven't encountered anything in Mystcraft, and this is what Mystcraft does (returns null here on no world).
If this is going to be used like this, setting widget to be null, the widget has to be removed from parent to I think.
It's because the oparser handler is set to resolve, and by adding this to params, the beginning of main overrides the standing store_true behavior, and we don't want that.
Again, null check.
why put this class under quotation marks
no comma
unit tests for thos methods would be fine!
How about
```
task test: [:spec, :features]
```
Oops, `11.10` typo :)

My commits from yesterday cover this (and there's a second entry that's required): https://github.com/benhoskings/babushka/commit/d55c259d93b303b1f2024d9519de7d8cd50dba00
"patient F" exists in registration table but not in patients table. Add it to patients table?
You are wrong. The listener you are lining is using the COMPLETED event, not the SUCCESS event
We should throw some logging in here so we can tell what's picking up as non-compliant.
I don't understand this change. It was declared as `unsigned int`, and you changed it to `int` and cast it back to `unsigned int` ?
$this-> validationFailed();
// So werden die Daten nicht gespeichert;
// Und der Controller kann das Formular noch einmal anzeigen... mit der Fehlermeldung;
// Den Fehler "nur" auf dem Params zu setzen reicht leider nicht aus; Auch der Service selber muss informiert weren, dass etwas schief gelaufen ist.
->max kann an dieser Stelle nicht funktionierten.

Verwende:
->OrderBy("c.version", "DESC")->setMaxResults(1)
if (      $var == 'crazy'        &&                             $foo != 'bar'                               )

works fine :)

However: Oh ... I thought its only about "no whitespace" against "one whitespace". But it's not completely clear to me: whats about

    $array = array(
      'slightly long string',
      'Heeeelllooo (here aroud 40 characters more) world',
    );

(I feel quite fussy right now ...)
Should use `$.each()`
What errors are you seeing that necessitates  the `try...catch` block? If an error happens, do we need to `return false`? Does the return get used anywhere?
and if it were, the second line should be indented another four spaces, and the paren that closes the surrounding `.create(...)` call should be on its own line
nah, never mind, it's all `@system`. Damn variadics.
I think you're a little too focused on `@safe` code. Keep in mind that this is a systems language; SafeD is just a subset.

Consider:

    ubyte* ptr = func(); // returns null due to some silly bug
    ubyte val = *(ptr + 0x10);

This is effectively the same as my first example, but shows a case where it's more likely to happen. You don't have to forge an invalid address intentionally for this to happen.

I'm willing to compromise: Make an `InvalidPointerError` class and a `NullPointerError` class. Throw the latter when you *know* that the pointer was null (and *nothing* else); otherwise, the former.
No; I'll do it; I am just having a little fun with you :+1:
Leaving it as is; I don't want to change the scope of the outer try/catch, which currenyly guards the code you put inside the inner try.
No, in fact that was the old value if you remember, but just so you understand the only attributes that would have affected messages stored by previous versions are the once used in query methods.
We need to deletes log files within pg_xlog directory.  Resource "file" doesnt allow multiple file selection and Resource "Directory" would delete directory itself and its contents.
@gordonslondon http://sonata-project.org/bundles/doctrine-orm-admin/2-0/doc/reference/audit.html

``
CREATE TABLE `page__bloc_audit` (
  `id` int(11) NOT NULL,
  `rev` int(11) NOT NULL,
  `parent_id` int(11) DEFAULT NULL,
  `page_id` int(11) DEFAULT NULL,
  `type` varchar(64) DEFAULT NULL,
  `settings` longtext COMMENT '(DC2Type:array)',
  `enabled` tinyint(1) DEFAULT NULL,
  `position` int(11) DEFAULT NULL,
  `created_at` datetime DEFAULT NULL,
  `updated_at` datetime DEFAULT NULL,
  `revtype` varchar(4) NOT NULL,
  PRIMARY KEY (`id`,`rev`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
``
Why is this one better?
Ehm, why inspect? `__file__` does not work?
I suggest: "For this tutorial it is good, but not necessary, [...]"
Yes, it does. But the requests for US regions my not be valid because of these differences in other regions.
Everywhere else the limit is 3 to 63 chartacters.
This class is trying to be immutable, but it's not because users can get these double[] properties and then modify the contents of the arrays.  Why not expose MinimumZ and MaximumZ as separate properties, the same way they're given to the constructor?  For Measures, consider using ReadOnlyCollection<double>.
Remove profiles.views from patterns
This regex comes from an old code... So then should it remove all whitespaces or just strip() ?
Why do you not simply use `*args` and `**kwargs` and just pass them on?
You can remove a commit: http://christoph.ruegg.name/blog/2010/5/5/git-howto-revert-a-commit-already-pushed-to-a-remote-reposit.html
Shouldn't this be `self.authentications = authentications or None`?
Same goes for parsers.
Capture is actually the one calling twice on an error (one for process.exit and the second for the exception thrown from cli.parse).
I've addressed this in my fixes.
In theory we don't need to whitelist hash, since they implement the as_json API, right?
Yes, this is fine.  We're never guaranteed a locale other than /en-US/, off the bat, so the test will fail until we have other localized versions trickle in (which we might never have).  The point is to test that the baseURL redirects, with its locale code, in place, like so:

--
[15:42:37.598] GET http://www.mozilla.org/firefoxlive/ [HTTP/1.1 301 Moved Permanently 52ms]
[15:42:37.712] GET http://www.mozilla.org/en-US/firefoxlive/ [HTTP/1.1 200 OK 20ms]
Instead of writing your own buffer, you probably just wrap a MemoryStream.
i_alpha is unused and use an array for this_rmses as you know the length in advance
Newlines are so 2011 :trollface:
This is used in tests that seem to make a point of "long texts". Wouldn't this "destroy" the test?
hayq ue cambiar los estados... hablá con Lucho para ver cuales son los que planteamos y el diagrama de estados.
Hayq ue agregar un método "set_estado(estado)"  que resiva el estado y devuelva True/False si lo pudo setear, y que verifique el estado actual y los estados posibles para ver si se puede pasar de uno a otro.

Hay que hacer algo similar para la Solicitud de Reserva, aunque los estados no van a ser los mismos.
Ah - just found [this](https://github.com/blog/985-git-io-github-url-shortener). Nice!
Implementers should _not_ use this to modify an existing property, but to be notified when an existing property is modified
Just tried moving this to setAlpha(). It seems that paint.setColor() resets the alpha value, so we would need to set the alpha here.
It's worth noting that this document will need to contain a link to the public information of the Composite spec (note that we shouldn't publish the full document, only portions of it describing parameters, precedence, and "auto" behavior). We may also need documentation about pinning, implicit calculations, and how absolute measurements vs. % works.
Why don't you just:

```
$container->setParameter('fsc_hateoas.json_options', $config['json']);
```

?
Shouldn't be agnostic?
"JSON-encoded"
Sure, I could do that.
`@rating.update_attribute(:rate, params[:rating][:rate])`, that is good. It updates only what we need.
A, you got me :) Corecting this right away :)
I was originally trying to set it up so I could require the file using jeffs custom require, but it kept dying on me at runtime. I may have been setting something wrong.

----- Original Message -----
From: Nukul Bhasin [mailto:reply@reply.github.com]
Sent: Thursday, June 07, 2012 05:34 AM
To: James Keshavarzi
Subject: Re: [BB10-WebWorks-Framework] Implemented webworks.js client/framework compatiblity mechanism [hash] (#63)

> @@ -19,8 +19,31 @@ var Whitelist = require("../policy/whitelist").Whitelist,
>  
>  module.exports = {
>      get: function (request, succ, fail) {
> -        var featureIds = whitelist.getFeaturesForUrl(request.origin);
> -        succ(featureIds);
> +        var webworksJsHash,
> +            frameworkHash,
> +            featureIds,
> +            xhr,
> +            errorMsg = "The webworks.js javascript library being used is incompatible with the WebWorks runtime." + 
> +                    "Please upgrade your webworks.js file.";
> +        
> +        //Extract webworksVersion from client webworks.js
> +        if (request.params["ext"]) {
> +            webworksJsHash = request.params["ext"].split("=")[1];
> +        }
> +        
> +        //read framework webworks.js version

this looks a a little weird for sure -
so the webworks.js creates XHR to framework and then framework back to client files.

Could you require this file instead in the framework? we basically use a custom version of require that @jeffheifetz wrote so I am sure if you have a special case you can handle it in the custom require.

I would like to move away from an explicit XHR from the framework to the client.


---
Reply to this email directly or view it on GitHub:
https://github.com/blackberry-webworks/BB10-WebWorks-Framework/pull/63/files#r942362

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
Yea
Also rotates even if you are locked



From: Jeffrey Heifetz
To: blackberry-webworks/BB10-WebWorks-Framework
To: Nukul Bhasin
Reply To: blackberry-webworks/BB10-WebWorks-Framework
Re: [BB10-WebWorks-Framework] Adds orientation API to the blackberry.app (#246)
2012-11-07 8:48:46 AM



In ext/app/client.js:

> @@ -50,6 +50,23 @@ defineReadOnlyField("name");
>
>  defineReadOnlyField("version");
>
> +function lockOrientation(orientation, receiveRotateEvents) {
> +    if (typeof receiveRotateEvents === "boolean") {
> +        return window.webworks.execSync(ID, "lockOrientation", {orientation: orientation, receiveRotateEvents: receiveRotateEvents});
> +    } else {
> +        return window.webworks.execSync(ID, "lockOrientation", {orientation: orientation, receiveRotateEvents: false});
> +    }
> +}
> +
> +function unlockOrientation() {
> +    window.webworks.execSync(ID, "unlockOrientation");
> +}
> +


I assume it would rotate without locking?

\u2014
Reply to this email directly or view it on GitHub<https://github.com/blackberry-webworks/BB10-WebWorks-Framework/pull/246/files#r2055144>.



---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
"using mustache", how can requiring  lib/events use mustache?
Try to remove the whole class.
You are right - we don't need to send notifications on each panning step. Changed the code.
I don't think the cacheing works the way you expect it to here.  The @Cacheable annotation is implemented as a Proxy-based interceptor, which means only callers who are working with an injected RouteBeanService interface instance will have caching applied. When you call getStopTreeForRoute(...) from within the implementation class, I believe it just calls the method directly without the caching interceptor.