labofsahil/github-event-dataset-2012 huggingface dataset:
Shall I rephrase the sentence?  I've never heard of pacman being used anywhere else than on Arch Linux, and I think that Arch is the only major user of pacman. After all, there are much better package management systems like yum or aptitude :)

And in either case, `yaourt` is a client for the Arch user repository which provides packages for Arch linux only.
Inside test_l1_compatability_logit (and mnlogit) I put t_tests.  

The f_tests are tricky since they require the inverse of cov_params.   e.g. invcov = np.linalg.inv(self.cov_params).

I got f_test "working" by subclassing f_test in L1BinaryResults (and later L1MultinomialResults if we like this).  The results are not correct yet since we need to adjust the degrees of freedom, which brings us back to the earlier question (I can't figure out out to change df_model, df_resid).
It is. Lines 1663-1664 for removed. This is under loglike. A case where github revision interface gives confusing results.
vaaaaaalue, quite a few typos with spelling mistakes in docstrings
默认值 -> 默认文件名
http://pastie.org/3492055 
Is this faster? It's using a different method :P
The `main` app introduces the concept of semesters; I wonder if you could use those, instead of defining an additional representation of time here?
Formatter.
TODO still in code.
If this is for 3.3, then the 3.1 should be changed to 3.3
There's really no need for the switch statement here as you're always returning the same builder.  Also, line 53 shouldn't be a log warning.
Gotcha, thanks.  Did you want to do any more on the other stuff (formatting headers etc.?).  I'm running out of steam, and I don't think it will be very effective for me to play around then check with you if you think it's better.  I'm happy to wait on merging if you want to play with it directly...
Some paragraph breaks in this humongous beast might help readability...?
What a massive steaming pile of XML.
thanks for doing this for me @dcadams
We don't need a manual-additions catalog most places.

I think the sync model is fine without volatile as load() only returns, and
manAdds var only set, when fully initialized and it crosses a method (and
sync) boundary if manAdd isn't set at first. And val never changes after.

Apart from this I agree with your comments -- thanks! -- and have preq
ready once I get decent internet.

Best,
Alex
On Nov 26, 2012 10:30 AM, "Aled Sage" <notifications@github.com> wrote:

> In core/src/main/java/brooklyn/catalog/internal/BasicBrooklynCatalog.java:
>
> > +import brooklyn.util.javalang.LoadedClassLoader;
> > +
> > +import com.google.common.base.Function;
> > +import com.google.common.base.Preconditions;
> > +import com.google.common.base.Predicate;
> > +import com.google.common.base.Predicates;
> > +import com.google.common.collect.Iterables;
> > +import com.thoughtworks.xstream.core.util.CompositeClassLoader;
> > +
> > +public class BasicBrooklynCatalog implements BrooklynCatalog {
> > +
> > +    private static final Logger log = LoggerFactory.getLogger(BasicBrooklynCatalog.class);
> > +
> > +    private final ManagementContext mgmt;
> > +    private CatalogDo catalog;
> > +    private CatalogDo manualAdditionsCatalog;
>
> What is the threading model here? You synchronize on
> loadManualAdditionsCatalog but you access the field without any synchronize
> or volatile, so usages of the field could see half-initialized objects etc.
> Should this be volatile?
>
> I presume it's too expensive to just create an empty
> manualAdditionsCatalog in the constructor rather than doing the more
> complex lazy creation?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/brooklyncentral/brooklyn/pull/396/files#r2220148>.
>
>
Watch out for ConcurrentModificationException - this thread doesn't hold the lock so another thread could call invokeStopOnShutdown(e) to add another entity while we're iterating.
Yes. But we are going to convert it to Java.
Replace `boolean` with `bool`.
Oops, I remembered why.
`internal_accessibilityActioregionToRectsnNames` is not found. Since I couldn't find it from the original SWT code, moreover since it was not used from anywhere, I removed it.
please update to new structure with arg instead of env, see ipa320 version
Heh. I didn't try plain zip(), but I could see it being slower due to allocations.
Puppet will already do this check for you. It fails with a pretty clear error message when you try to reference a non-existant class.
These should be inside a --INI-- section, not set manually in the test case
Some sanitization would be in order, not to redirect to a third-party site.
Thanks very much for taking the time to do this. Could you please update these links too?
Re: `createDelegate`. Yes, probably, I didn't realise that Ext monkeypatched the core Javascript classes.
the dir parameter requires a JSDoc. Something like,

@param {string} dir A path to a directory that holds templates.
There are spaces at the end of the following 4 lines.
This is utterly wrong. You should not pass 'target' at all as it is not needed.

By this point the engine redetected the game, since it was initialised, and thus you should have access to ADGameDescription instance which defines all required things, including _gameDescription->gameid.

Please change as described other engines too.
I agree, but that can wait for another PR.
We are TDD addicts and thus as a rule - we can't put into production code, which contains ignored tests.
what is with the log output here?
Since the numbers you're dealing with will always be positive, you could just use fmt_uint. If you really must convert signed integers to ASCII, copy from fmt_uint to add a signed prefix.
I think this is all fine (and hopefully not required), but if this breaks, I suggest using the fact that NetUtil.newURI can take a base URI, and node's url.resolve can do similar stuff.
@ruian using a deprecated method ? I don't think so
- Steven Silvester, Karel Zuiderveld
  Adaptive Histogram Equalization

I will hold off on pushing this until I have made more changes.
yes, it should. And I looked it up, there is no prior processing so this is the right place to do this, I think.
It just state that this is computing the same OvR based proba estimate as done in liblinear.
I don't think that there is a t at the end of classifier :)
We usually prefer ``(...)`` to ``\`` line continuation.
[pytype_to_ctype[...]]
чому так?
git + netbeans = :(
Actual, lets just get movements working. It's more important.
erm.... what?
We can't hard code localhost.
Is there really 32 items ?
What's the require: false do?
For minialism... Change line 15..17 to

```python
for line in view.substr(sel):
    selected.append(line)
```
in the plugin definition for promoteSuperFiles, delsub , is 'deltail'.
Which has a slightly clearer meaning of what's going on here with this option.
Yes, this is just to yield to other threads.  It's probably a good a idea to let other threads run before trying read again since the last read did not succeed reading all the data.
please fix the CS
```if get_map_by_attrs(mapAttrs):``` is cleaner.
I do not think this was meant to be an assignment:
$tableName = $this->getTableName()
it does not seem to be fixed
This is actually incorrect, as `(= false false) ;=> true`. What you want is an `(and blo tro)` and then you don't need the `if`, because `and` returns a boolean.
for now, for safety, when to call save=True is not finalised for the API
I assume this has to do with the EXTENSION option?
The indentation of this rescue should be fixed
Exploits are REQUIRED to pop a shell.
Ok, so we'll merge and we'll look for other solution when we'll have some more time.
I'm a fool.
Removed enablement for both layersView contribution and legendView contribution
need to change this back before we merge
Is it really ok if the data property is not immutable?  In Components at least (and here too, I assume), adjacent intervals with the same data get combined.  Let's say you create two adjacent intervals with different data and add them to a TimeIntervalCollection.  Then you change the second one to have the same data as the first.  You've now violated an invariant of TimeIntervalCollection, no?
This is not a question; it is a statement.
Is this wrong?  The geocentricSurfaceNormal doesn't use any of the information about the Ellipsoid?
`Event` at the end of the class name too much!?
If we have defaultErrorRoute() method, maybe this variable doesn't need to be final. Maybe refactor it to:

private Route defaultErrorRoute;
Redirects to an online dating site. 

N.B. that the internet domain example.com is explicitly reserved for documentation purposes.
_search
Yes. Android emulators return 'unknown' for manufacturer.
In that case the parenthetical is confusing (especially given `pagingControlOnTop`). It should be removed and a better summary of the property should be written, probably along with a `description:` section.
usage is already displayed if the platform argument is not displayed or if the platform is unrecognized (fails to load module).  The error though is a general fail to load error and I have updated to provide more focused logging and error handling.
If not attached, does this mean we're releasing annotationsToAdd without balancing it with a retain?
Don't forget Titanium.UI.MobileWeb.NavigationGroup :)
android has this constant as well
can you confirm me the role of verifier, and how we can get it.
Use rimraf module instead?
This is a pattern. See journal template_description.jsp.
Sorry, instance_methods returns an array of string in 1.8.
Please check both version.
А будет ок?
5.3+?
idem.

if they need to be freed, do it from the caller.
call result seed and move this line to after the if/else
I appreciate your quick responses, but I'm busy enough of late that you being a bit slower doesn't slow the process down much.
This has trouble with qualifiers. Replace with is(typeof(r1 == r2)).
NotExcludedBean
According to my testing, it does: uploaded records now correctly fall into the window between last fetch and last store, and are thus skipped on the next sync.
On desktop, this wipes, at least I think it does.  Worth checking with rnewman.
This rolls us back to BF 4.4.4. It will need to be reverted.
I searched for everything I could find that hit that endpoint exactly, but the chain of passing wasn't always easy to follow to be sure...

On Feb 21, 2012, at 9:52 AM, Simon Murtha-Smith<reply@reply.github.com> wrote:

>> -                // not all connectors need auth keys!
>> -                if((regIndex[key].repository.keys === false || regIndex[key].repository.keys == "false") && !regIndex[key].repository.hidden) connectors[key] = regIndex[key];
>> -                // require keys now
>> -                if(apiKeys[key]) connectors[key] = regIndex[key];
>> -            }
>> -        });
>> -        // annoyingly, some might be local only
>> -        Object.keys(serviceManager.map()).forEach(function(key) {
>> -            var svc = serviceManager.map(key);
>> -            if(svc.type != "connector") return;
>> -            if(connectors[key]) return;
>> -            if(apiKeys[key]) {
>> -                // spoof a repository field to be consistent
>> -                connectors[key] = lutil.extend(true, {}, svc);
>> -                connectors[key].repository = lutil.extend(true, {}, svc);
>> +// TODO make sure callers understand response format!
> 
> This needs to be checked before we can merge. There are lots places that use this and none of them can break.
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/LockerProject/Locker/pull/849/files#r472001
reminds me that I noticed the other day that some of the same constants are defined in fiff/write.py and fiff/constants.py, it would be cleaner to only use the ones in constants.
i am not a frontend guy .. but yeah thinking about it .. the trouble is mostly on the frontend side having to trust the remote provider. i did a quick google and found a blog post describing similar intentions to what i have done here and people in the comments pointing out that it might not really be necessary:
http://tav.espians.com/sanitising-jsonp-callback-identifiers-for-security.html
this one is in the User class, which has a constraint
@ogail already checked in a fix for this; can you integrate those changes and refresh your request?
Sure. I had to add this because I was getting a few issues while trying to get the bundle working. Will be removed on next push.
@jspahrsummers Oh, alright, I did indeed misunderstand the extensiveness of this guide... thanks! :+1:
See https://github.com/hpcugent/easybuild-easyblocks/pull/53/files#r2357138 for a description on how to do it without specifying Velvet as build dep.

However, as you've pasted from the Oases documentation: you just need to have Velvet installed, you don't need access to it's sources.

Oases probably just needs header files that are provided by Velvet. In that caqse, Velvet is actually just a build dependency, and you should:

* not specify the Velvet tarball in `sources` in the Oases easyconfig
* do specify Velvet as a build dependency (as you're doing now)
* simple use `VELVET_DIR = %s' % get_software_root('Velvet')` in the Oases easyblock, as opposed to what's suggested in the comment I referred to above

Is that clear? I'll also mention it in the easyblock pull request.
Ok, changed to set() and .add().
Should remove this.
If this format is only used is a single service, maybe we should start with putting it where it's going to be used.
agree, will work on that
Sorry, it was suppoused to be "\n", like in the original file.
Хм. Эффективнее получится.
This struct, when initialized without any particular work, should have all fields invalid.
> SymInitialize does only take a c-string. 

Like any other ASCII function. I don't understand your point here. Yes, `SymInitializeW` isn't available in old `DBGHELP.DLL`, but it doesn't mean we have to use it when *Unicode* version is available.
This is invalid use of pytest-mozwebqa. Please check the README.
persist "true" serializes the logging resource to disk, so you can reopen it between recipe runs.  Since the resource is already persisted using this flag in the default recipe, you do not need to specify again here.  Please remove this from each "do_*" recipe
you might want to mention BCMath here. this is used for long integer that could be bigger als PHP_INT_MAX
I think this logic belongs in the thread object itself. @asm89, @stof ?
Are we sure this works?
So, the corresponding functions in the app would be something like:

    (defn get-oauth2-response [request] 
      (:oauth (:session request)))

    (defn set-oauth2-response [request response oauth2-response]
      (if-let [rsp-session (:session response)]
    				  ;; Handler has put data in the session
        (if-let [new-oauth (find response :oauth2)]
            ;; Handler has set oauth - merge it all together
            (assoc response :session (merge rsp-session new-oauth))
            ;; Add our oauth data to the session
            (assoc response :session (merge rsp-session {:oauth2 oauth2-response})))
    					;; Handler has not modified session
        (if-let [new-oauth (find response :oauth2)]
            ;; Handler has set oauth - merge the new oauth data
            ;; into the session from the request
            (assoc response :session (merge (:session request) {:oauth2 (:oauth2 response)}))
            ;; No change to session - our oauth data will
            ;; be fine. If we were to set it here, we would 
            ;; wipe out the existing session state!
            response)))

Given the complexity of the latter function, would it make sense to define default versions of these in the `clj-oauth2.ring` namespace, so that the app can reference them in the parameter map if desired?
interesting! i was expecting a select with options, but i think this is fine. we will have to add classes to the li items, and event listeners that call the relevant functions. similar to what i showed you on thursday @hisakonog do you want to do this, or do you want me to take over?
In the other wrappers the `amount` param is optional, in this one is required.
Good idea, if time permits, I'll do it friday morning when everything else has settled.
@mandrews how about this?
you should fix the indentation. Seems like you mixed tabs and spaces
waited -> waiting
This sentence seems a little vague to me. Maybe we should explicitly mention that orientation of windows and of the system are always the same because of this sentence?
Hopefully we should be able to take this nonsense and concatenate it into "layout" now, since we found the offending code that was causing submission issues (apparently we had a legacy `@selector(layout)` call somewhere).
You're right, multiple events can end up attached to the same memory imprint and therefore linked even when it doesn't make sense.  Builds for a comment-added event should not be grouped with builds for a change-merged event that just happened to occur around the same time.

I was looking into implementing your suggestion for multiple BuildMemories, but after digging into the code a bit, I started thinking why not just have the BuildMemory use the GerritTriggeredEvent itself as a key?  That will allow us to keep one BuildMemory (which keeps the code simple and generic so it doesn't have to care about different event types) and groups the builds together in a way that makes sense.

In the current release, every event is a PatchsetUploaded event, so there should be no change in current behavior.

As for handling ChangeAbandoned in the way you described, we would still need to layer something on top of this in order for a ChangeAbandoned event to find the builds triggered by events emitted by that change that it wants to cancel.  But I don't think that's too difficult -- either a secondary index or iteration of all the events to find the ones it's interested in.  I'm not proposing implementing that now, just indicating that I think it's possible in the future.
Shouldn't this be a forEach?
you want to point me to the expected syntax here?
Just wondering what the signature of webview.addOriginAccessWhitelistEntry is?
Unit test has been added.
Would you mind removing the closing tag. It's better to take it off and not have to worry about newline at the end.
explicitly set to null
oops, a console log :)
Yes.

You remember correct that in my first approach the opening was `|{` and closing with just `}`, but that's changed in the final commit.

Parameter bag starts with `|{ ` and ends with ` }|`