labofsahil/github-event-dataset-2012 huggingface dataset:
Adding org.owasp.csrfguard.Protect

The default behavior of CSRFGuard is to protect all pages. Pages marked as unprotected will not be protected. If the Protect property is enabled, this behavior is reversed. Pages must be marked as protected to be protected (org.owasp.csrfguard.protected.SecurePage=/SecurePage.do). All other pages will not be protected. This is useful when the CsrfGuardFilter is aggressively mapped (ex: /*), but you only want to protect a few pages.
Validate the 'Show source in catalog' action so it's only available for objects actually in the catalog

A nice bug for you all here:

* Enable the 'Show source in catalog' action
* type any text in the 1st pane "hello123" (or browse to a file you know isn't in your catalog)
* Tab to the 2nd pane and note that 'show source in catalog' is a possible action
* Perform the action, and watch QS open the catalog prefs then crash :)


This change:

* Adds a 'validatesObjects:YES' bool to the action in the Info.plist (sorry for it looking like everything got changed)
* checks whether the dObject is in the catalog in the `validActionsForDirectObject` method and enables the action depending on the result
HoloToast

Toast in Holo style
Network Architecture based on Game Philosophy

My talk proposal as a pull request.
[ParamConverters] Object ParamConverter

Allows to convert user input into object graphs. Use-case could be criteria/query objects or other lightweight objects that are not persistent.

See the documentation update for details on how this converter works and the security implications.

Open question: one way to avoid potential security problems might be only allowing this from $request->query - never from $request->request. Currently its adapting to the request method (which might not be that a good idea given POST requests with query parameters).
[ParamConverter][Doctrine] allow to find by single-valued associations.

Fixes GH-95

I initially thought this could lead to clashes when the following
conversions are defined:

    /**
     * @Route("/page/{user}/{group}")
     * @ParamConverter("user", {"id": "user"})
     * @ParamConverter("group", {"id": "group"})
     */
    public function showAction(User $user, Group $group) {}

    class User
    {
        /** @ManyToOne(targetEntity="Group") */
        private $group;
    }

However through the renaming via `id` its a find by primary key anyways.
There is a slim chance before GH-141 to find two objects through 
`findOneBy()` which would break because of this patch, when an association was not found before and now is included in the `$criteria`.

Should I add a UPGRADE notice?
fixed issue #666

#666
Enables more functional keys

The following keys were ignored previously.  Since they are functional keys, not characters, there's no reason for them to be disabled.  This pull request is for enabling them.

shift	 16
ctrl	 17
alt	 18
pause/break	 19
caps lock	 20
escape	 27
page up	 33
page down	 34
end	 35
home	 36
up arrow	 38
down arrow	 40
print screen   44
insert	 45

Keycode map reference: http://www.cambiaresearch.com/articles/15/javascript-char-codes-key-codes
Introduce :if, :unless, and :value options to attribute

I'd like to introduce `:if`, `:unless` and `:value` options to `attribute`. These options will enable the following capabilities, as described in the changes to the README:

***

Use an `:if` or `:unless` option to conditionally include a particular attribute:

	class PostSerializer < ApplicationSerializer
		attributes :id, :body
		attribute :admin_note, :if => :admin?   # will be evaluated by the serializer (see below)
		attribute :hidden,     :if => :hidden?  # will be evaluated on the serialized object
		attribute :synopsis,   :unless => lambda { |serializer| serializer.object.content.size < 100 }

		has_many :comments

		def admin?
			scope.admin?
		end
	end

Use the `:value` option to define a value other than the attribute on the serialized object:

	class UserSerializer < ApplicationSerializer
		attribute :first_name
		attribute :last_name,  :value => lambda { |serializer| serializer.object.last_name.upcase }
		attribute :full_name,  :value => :full_name  # will be evaluated by the serializer (see below)
		attribute :code_name,  :value => :code       # will be evaluated on the serialized object
		attribute :admin,      :value => true, :if => :show_admin? # value is static

		def full_name do
			"#{object.first_name} #{object.last_name}"
		end

		def show_admin?
			scope.admin? && object.admin?
		end
	end

The `:value` option can optionally be combined with `:if` or `:unless`.

All of these options can be either procs (see the `lambda` examples above), methods on the serializer, methods on the serialized object, or simply static values. Arguments are evaluated in that order.

***


This is similar to #36, and is somewhat based off @wycats' suggestion to use a `:value` option instead of a block. However, it differs from that suggestion because it keeps the attribute definition at the class (not instance) level, which I think is important for consistency and ordering purposes.
Single string and multiple string translation implemented

Need some testing so!
pull-request-274
Level mainloop simplification
Proposed: Add RSS link to nav bar

Do you think this is how this should be handled? This will add the feed to the `navigation` group and it will be shown with the other items in the nav bar.

On my blog, I just include the RSS link in a sidebar that is in the default layout - but I think doing that won't work with themes.

You could also argue that by adding the `site.rss_path` that maybe we should just defer this decision to theme authors - each theme can choose how and where to show the RSS link (in a sidebar, with an icon, in the footer, etc)
updated getItemsBySections and getItemsByAudiencesAndSections to

At the Cioppino sprint there was talk to have knowledge base documentation sort by version number.  I've updated the getItemsBySections and getItemsByAudiencesAndSections methods to sort the generated dictionary values for 'items' by version number.
Animation

Added a nice portal animation before teleporting. If you don't like it, I have other ideas. As suggest via PM.
Implementing @AfterInject for @Enhanced components

@AfterInject allows methods to be called after dependency injection in @Enhanced components (the dependency injection happens after the constructor returns).

See issue #6.

@matboniface could you please review and merge that (green button)?
Fix on the polling for mercurial 1.4

fix the polling for Mercurial 1.4

sorry, i don't have mutch time to do more than send the fix that work for me
Logging improvements

This branch changes the log event a bit. Instead of `message` argument sometimes being a string and sometimes an object it changes `message` to always be a string and adds another argument which is an optional object with extra log details.

The new interface now looks like this:

`(log, level, message, obj)`

- `log` - event name
- `level`- log level
- `message` - log message which is always present and is a string
- `obj` - optional object which contains extra attributes about the error

This branch changes the log interface which means we also need to bump the package minor version when this change is included in a release.
Update and Feature Additions

I updated to a newer build of spring-security-saml SpringSource/spring-security-saml@51a4952ebdd6aabcac6d80f51e43b25caefe1fd2  That includes an update to Open SAML 2.5.3 . 

Added the following:
* Configurable Response Skew
* Allow pulling of Roles from the DB instead of SAML and added configuration to do toggle this.
* Passed user from DB if it is doing the autocreate
* Travis config 
* SSO Binding configuration in the metadata controller
* Force failed saves in the user details service to throw an error.
* Added ability to turn off discovery in metadata controller when generating xml
* A few tests.
Erklärung auf den neusten Stand gebracht

Erklärung auf den neusten Stand gebracht
siehe:
http://www.informatik.uni-stuttgart.de/studierende/pruefungen/pruefungsausschuss-informatik-und-softwaretechnik/abschlussarbeiten-in-der-informatik/formvorschriften-fuer-abschlussarbeiten.html
README update and has_evaluation? and has_scoped_evaluation? methods

Added examples, fixed install instructions typo, added has_evaluation? methods
Allow use of UnixAddress in std.socket on Unix-like platforms

In current state static if check fails even if platform is
Linux, FreeBSD etc. As we noticed with CyberShadow the check for
struct existance should have form of is(StructName).
My solution

Submitting my solution to the Software Engineer Challenge.
logging in takes you to home page

Resolves Karaage-Cluster/karaage#126.
q

bgrb bs :P
LPS-25385
Use relative path for looking up the module
added collective.z3cform.widgets repo
OAEWDGT-78 Update the 'create the unexpected' tab of the carousel

https://jira.sakaiproject.org/browse/OAEWDGT-78
Use parameters instead of hardcoded class references (relates to #37)

*Adding @IamPersistent, @merk, @stof*

I've been using ``Sonata*Bundles`` for only a day and a half now, and I've run into some problems regarding namespaces:

1. My project uses different architecture than Symfony default, application files are stored in ``/src/App/`` as opposed to ``/Application/``. After easy-extending the core bundles everything was dandy, I just had to move files around and change some namespaces. But I ran into troubles, as the namespaces are hardcoded in XML files (which this PR fixes, for this bundle, for now).

2. Now ``SonataPageBundle``. While making things more configurable for ``MediaBundle``, matters are a lot worse for ``SonataPageBundle``. Apart from the hardcoded class locations in configuration files (which can be similarly fixed), there are also use statement references from code (ie take a look at ``SnapshotManager.php``)

I am not sure the current solution to reference application entities from the core ``Sonata`` namespace is a good idea. Perhaps a  Sonata core service should be introduced which allows the application to register it's overrides. This way every extending bundle could have any namespace.

Another idea (in case the previous gets shot down) is to define a parameter (``sonata.app.ns``?) which defaults to ``Application\Sonata``. Then you could address your specific namespace needs by overriding only one parameter (instead of dozens of classes, as mentioned by @rande in the original issue)

Thoughts?
Implemented mootools 1.3 compatibility, a bug fixed, z-index implemetation added

Upgrade to mootools 1.3.
The wrong year selection of a day of the prevoius/next year in months January an December fixed.
Z-index of calendar container is setted as the highest in the document.
Thanks for this awesome datepicker class.
Bye
Fix author name.

Author name was set incorrectly. Fixed it.
fix reference to missing method in super class
I'm leaning towards calling this kind of function getByAssoc rather than getByAssocId. You need to specify both assoc type and assoc ID and this name implies that only the ID is required. (Not a big deal.)
Why "Item"? Isn't it just row?
I think this is clearer: 95c620a300608577e05b460b3f993d8d34fca118
ActiveRecord::Base 的验证机制
validates_presence_of :item_title 这个的意思是 item_title 字段不允许为空
比如 voteItem 的 item_title 为空时
运行 voteItem.save 会保存失败并返回 false，voteItem.errors 里会有未通过验证的详细信息
Yeah, go ahead and call him a troll and then proceed to add commits to fix the reported security issue.  Stay classy @jonleighton
Since when Ruby has method visibility? o.O
Ok, I will change the formatter to not force "*" characters on each line.
the problem with when you always "explicitly freeze the gem dependencies" is that you prevent spree users from upgrading a certain gem in case there is an important bugfix - they'd have to wait for a new release of spree just to (hopefully) allow bundler to grab the new version. This is what the `~>` operator is for -- although I admit you are then victimized when gem authors break back-compat on point-releases, which happens as we see here. But, in that case, that's exactly the kind of thing that CI is there to catch and should be treated as a special case.

the reason I have an opinion, in fact, was because I just found an issue in paperclip that means I need 2.5.0, but can't get it because I am on spree 1.0.0.rc2 which required `paperclip '=2.4.1'`. Fortunately I am not in production yet so can go to edge to get this commit, but in the case of a production app which was a couple versions behind, I'd be SOL.
more than likely the `GET` data will be invalid. but that's okay. [we do stuff](https://github.com/cvan/zamboni/blob/f02f89/apps/search/forms.py#L287) to force the `appver`, `sort`, `cat`, etc. to be wellformed things that we can easily pass to ES without validation checks everywhere.
yes, you are right.

should pass a callback to call find. then the logic should be much more solid. but anyway, I think this won't happened often, it should works well for us. ;)
Sure, would be happy to see it cleaned up. I reality all we need to do is serialize basic primitive types plus CGRect, CGPoints, and CGSizes. Anything else is very unlikely to be helpful inside of Symbiote.

Great to hear of someone getting paid to work on Frank, btw :)
On a page with a couple hundred links, the total hint-generation time went from ~45ms to ~35ms.
I didn't say it's ok to add bugs, you've just turned my opinion into something terrible. I told ya that just being a bit more polite against another developers would bring you more friendlier replies from them and also may bring attantion to people, who could be interested in helping developing it.
1) Concatenating the files was making debugging a real nightmare (line number didn't have any meaning anymore).
2) For the lazy loading script test, you'll need a special test page, correct? So why not use the dist file there? Do we really have to complicate things ad nauseum for a single test page?
Good catch :D .. Long time no see, how you been?
https://github.com/Pylons/deform/blob/master/CHANGES.txt#L20
There are a bunch of PEP8 conventions not respected. Most common one: 
[0,1] should be [0, 1]
Riunire gli italiani...
Ahahah...
regression ;)
This is where we work. 
The python file should appear here soon.
@fixxolas: Interesting. I've tested with several FLAC files in my collection and I can't reproduce this. Furthermore, this particular change could not have introduced problems with header parsing (only with subsequent attribute accesses), so this must be related to a different change. Can you send me one of these files that's causing problems so I can run some tests? My email address is on [the beets homepage](http://beets.radbox.org/).
Had the same wallpaper error when tried to build for Nexus S 4G. Adding the same lines below gets it right. Thanks @andreasgal for the fix.
Added types to these, don't know why I didn't add them to the rest.
Any idea if this works on anything other than linux?
Shouldn't this entire method be removed? Because the boolean is now completely ignored and the method is only used in a unit test anyway.
So also remove CommandFactory.newSetGlobal(String, Object, boolean) and adjust accordingly:
  org.drools.integrationtests.StatelessSessionTest#testSetGlobal()
Feel free to merge any change(s) you want from my tree. I'm currently trying to think through how to do this without having to renumber objects frequently.
Hi Joseph
There is no special reason to choose ```call_user_func_array```

Also this patch not solves our problem. I closed. 

```$reflClass->getName()``` still points to parent class and it fails.
Add:

`if (!this.headers.hasOwnProperty(name)) clobber = true`

Otherwise setHeader('foo', 'bar', false) will actually set to 'undefined, bar'
Yeah I stopped calling it because JaguarSpeed doesn't know the correct tolerance.  It didn't make sense for JaguarSpeed, which should represent anything that uses Jags for speed control, to know the RPM tolerance.  The tolerance is something that depends on the particular use of that component, so I made it happen in Shooter instead of JaguarSpeed.

Now that I think about it, JaguarSpeed could have an argument for tolerance value and Shooter could pass it in.  Then JaguarSpeed.isAtSetPoint() could check against that parameter.  I'll do that now.
my GIT is broken, please help :D won't let me commit anything or checkout branches or do anything really, how do I just reset my repo ?

to fix this more appropriately use this rather :

        $viewable_types = array('.png','.jpg','.jpeg','.png','.bmp'); // image ext supported by fancybox viewer
        if ( in_array(strtolower($extension),$viewable_types) ) { // extention matches list
Just want to make sure that "live" is necessary here; 

Does the "settings-toggle" element show up spontaneously?
If not, and it's there at page-load always, we should use "bind" instead.

Are we unsure where in the DOM it might appear?
If we know, we should use "delegate" instead on a parent element to narrow down where JQuery is monitoring for it's appearance

If, however, the answers are "Yes" to both questions, then we're good.
Stable, to master.
:) Congratulations. Almost good, at least must be usable.
考虑到以后可能会有 Start All Tasks ，可能显示太长，所以在无歧义的情况下，可以参照 Yaner 直接称为“Start”，其他以此类推， New Task 暂时不用变，防止表意不清。
rails自带，将字符串的换行符\n\r等换为＜br＞

发自我的 iPhone

在 2012-2-12，1:48，董劭田 DONG Shaotian<reply@reply.github.com> 写道：

> `simple_format`这个函数哪儿来的？
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/PKUIRSA/pkuzone/commit/0552227e118727a19de9d7c2094e230a64090689#commitcomment-956787
с личными разборками и наездами - все в сад.
Same, { } delimiter effect of lock.
here you have 2mb of log :D

http://fbe.am/1Iu
Yeah, I noticed that. The string stored in the JSON file is never seen by the user so having %xx syntax seems fine. I would be afraid of adding backquotes because the corresponding "unescape" operation is more complex and therefore more subject to error, and we are hoping to ship immediately.
it looks better. I can't believe I wasted two minutes on this.
eugh, bPerms
Resultado xD no compila, bueno ya tienes la causa, al dia de mañana pasado el medio dia o noche lo incluimos en thalassa con los cambios necesarios :)
reindex() calls refresh(). Somehow refresh() alone was not updating the addon types.
Yes, `propagate_key_file_error()` is the only place in the code where we touch the contents of a `GError` supplied by an API user directly, so I've just added some additional checks there.
I've made this into an issue and CCed you. We should probably try to keep design discussions like this in some publicly viewable place. Your suggestions are good, keep 'em, comin'.
Here is the proper thread with a better patch from Shauren but needs to be tested: http://getmangos.com/community/topic/16928/fix-actionbar-problems-with-shapeshifting/
Is the hamcrest bug occurring right now, or is it only when adding hamcrest-all.jar?
I did have a slightly different test in here at one point and just compressed it down. Agreed, it's not really worth the extra lines of code.
keys is defined above, period had an assertion which i removed for some reason, will add back in.
I wonder if we should make this more explicit like ``storedata = 'id=123'``? Or a json blob. In other words, would we ever need to add to it? Don't want to overcomplicate things but it came to mind.
I'd prefer if the it removes up to and including user, but not the cell and certainly not the prefix :)
Doncha mean if get_macosx_version_major <= '10.7'?
that's sad ... what is the sense of new APIs, if we still need to look at backwards compatibility?

why not patching it with some `classList` polyfill?
the current screen should be updated also! it is still visible and active!
Yeah, I tested it a few times.. So im sure thats the ip blocking.
I also did test the ::lostcon command, same thing happend.
There should be a note that parameter is available since 1.1.11.
I never use git-flow or / prefixed branches so I don' really run into that problem :)  But good to know :)
Waitwhat? It just set it equal to zero!
do you have a 100% way to repreduce the crash? cause from what i hear its very random
http://nodejs.org/docs/v0.6.0/api/zlib.html
camelcase in function name is ugly. :D
aw crap, yea that can be removed, I was trying to figure out how markup attributes worked in jekyll. I eventually found the default template and updated that.
So, this is one way to do it. Obviously in foo.coffee I'd want to be smart about what I made 'yow' be, since it pollutes the global namespace when run in a browser. I don't think this is the current recommended RequireJS approach, though, so let's explore that.
50% failure rate on repo sync on our build cluster across 7-8 different machines. Fixed as soon as we switched to http.

http://jenkins.cyanogenmod.com

I have a fix so people can continue using git. Gimme a bit.
我感觉展开回复的按钮背景色不是很合适，太浅了有点
Yep. Had the same idea but the assets pipeline is not really connected to the rails app life cycle.
Since most of the changes are color based, I figured it wouldn't affect usability.
not sure what you mean exactly .. i just tried my best to fix the issue .. but i might not have been sufficiently aware of the entire code base to do things right in the grand scheme of things ..
I which is not the best way.

Visually it is not good.

The best way is to create a right menu, as in the header of the conversation, to copy nick, email, message.
Could you setup your editor to trim trailing spaces?
OK, I think I may have broken the handling of group-specific dependencies. It's probably not hard to fix but I'll have to take a look at it tomorrow.
I have merged this, sorry it took so long. Thanks!
Haha, yeah I think ultimately it's nicatron's choice :p
This doesn't look right to me, but maybe it's a matter of expected use...

If the child process exits with an error, but there is no error using the stdin or stdout streams, then `err` will be null.  Is it your intent that the callback passed to `data` only gets an error is emitted by the streams represented by stderr and stdout?

I understand the reason why you separated the "data" from the "exited with error" event, but I'm still thinking that it's more convenient to be able to access stderr from the same function that is notified that a child prcoess exited with an error.  I'll leave one more comment on what I think could be done about that...
variable name not good
Metto  un commento di test a questo commit di test
Isn't there a chance (it's a lower probability, sure) that things would have to be reconsidered again?
On Fri, Feb 24, 2012 at 3:19 AM, Keshav Kini
<reply@reply.github.com>
wrote:
> Thanks to 5.0.beta5 coming out, what I predicted has happened - there are now weird commits on your branch :) The commands I listed will have to be modified a bit now - just use your local branches, i.e.
>
> ```
> $ git checkout lfun
> $ git rebase github-master --onto master
> $ git push -f

You keep sending me stuff to try that appears to not even be valid input to git:

deep:sage wstein$ git rebase github-master --onto master
Usage: git rebase [--interactive | -i] [-v] [--force-rebase | -f]
[--no-ff] [--onto <newbase>] (<upstream>|--root) [<branch>] [--quiet |
-q]

Maybe I'm using the wrong version:

deep:sage wstein$ git --version
git version 1.7.4.4

> ```
>
> Thanks! I decided to just get rid of the `github-master` branch and put the github-specific README on the [github project wiki](http://github.com/sagemath/sagelib/wiki/) so that this doesn't happen to other people in the future.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/williamstein/sagelib/commit/f4104efd87cb421923f884f8ea5c571fa52d583b#commitcomment-1007022



-- 
William Stein
Professor of Mathematics
University of Washington
http://wstein.org
I think it probably should be in .gitignore really.
Then I can add source links to stuff in home directory etc.

I'm happy for you to add it to gitignore if you like.
Maybe could be usefull to set a tag for the previous commit? :)
ţȽϺ~

 201224 12:56Juanito <
reply@reply.github.com
>д

> -  ոµĲҺ͸˼ʽķ
> + µāKҸĳʽ˼
>
> @Σ
>
> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/fengdidi/acl-chinese/commit/25710b02f6cc957f92915629d0d3a6aa2f097699#commitcomment-932926
>
dont know if intended, but this is the only rule which is now longer than before. all other changes reduced duration time..
As far as I can see, `st->port` is `NULL` when no *Port* configuration option is given by the user. This will lead to a segfault in *strlen(3)*. Please either change to `if (port == NULL)` or `if ((port == NULL) || (strlen (port) == 0))`. If you chose the latter, be consistent and do the same with *host* above.
Interesting refactoring.

When moving the messages, wouldn't it be more Maven-like to move all message properties files to somewhere inside the resources directory (like, say, "src/main/resources/i8n/")?
I saw that the other day when we were going over something.

On Sat, Mar 3, 2012 at 3:30 PM, Michael J. Giarlo <
reply@reply.github.com
> wrote:

> Best commit message so far.
>
> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/psu-stewardship/gamma/commit/bc42c3f0b272b9429e99fa66c1328bddf0b89755#commitcomment-1039237
>
Most work flows will input the vitals tight after they are taken, so I am guessing the auto-timestamping was not much of an issue, considering it has been like that since the end as 2010 (as I remember). By changing it to the encounter date, you are now making the date/time inconsistent with the widget and the graphing module. Will leave this up to you, but if add this then should consider also doing it to other parts of the code that use the vitals.
Is it a problem? Just create a simple wrapper around sendfile, with internally different per OS system sendfile invocation using #ifdef ... #endif.
oh no, my Focus Energy code :(
That's why the original pull #689 included a comment ;)
hero of the day!! :)
thx man.
interesting fix... ;)
Can the compare return < 0 ? Should you assert ?
here just use your name, the other data is not required.
There's a race condition on _needToNotifyWaiters_ .. this code might fail to notify the wait_for_locking threads as it's reading the volatile before entering the exclusive lock with the other potential thread. At this point it might take the optimal branch of skipping the notifyAll, and at that same point in time the other thread might already have checked for _txComplete_ , it fails to return and enters in the deadly embrace of an eternal wait().

Sending soon an alternative proposal..
Thank you for this. Saved me some time banging my head on my keyboard.
Hai provato ad andare su IRC a chiedere?
Afaik we have a modvar for anonymous users = guest configured in the Users module.
Why is theFont marked as __block? I can't see any cycle there.
Шаблонные параметры обычно указываются с заглавной буквы.
sAreaStore.LookupEntry(4713) is last in 15050, isn't it?
Notice the method now takes two closures as arguments the happy path and the sad path.
I think this is pretty self explanatory. We don't need the if it's unnecessary.
The array key should aways exist because the option is auto-loaded on install.
It was too wordy. The information was included elsewhere.
{ 1, 787200, ACPU_PLL_2, 2, 0, 393600, 1, 7, 393600 },

to

{ 1, 1036800, ACPU_PLL_2, 2, 0, 518400, 1, 7, 518400 },

they all need to be changed, except the 806 one.

If it causes crashes, after you fixed that, maybe it's a bit too optimistic & then you should try diving by 3, change the ahb divider value to 2 too

{ 1, 787200, ACPU_PLL_2, 2, 0, 262400, 2, 7, 262400 },

etc. you need to divide the cpu speed for the ahb bus speed & it probably makes some sense to run axi at the same speed too if possible.
Change max length text without links or without text as links to asks
write /sys/devices/system/cpu/cpu1/cpufreq/screen_off_max_freq 1200000 is probably not a good idea battery wise and there are no reasons why the cpus should be allowed to go that high with screen off. It could even be a good idea to put 350000.

the mounts are somewhat not secure enough

the net buffer sizes won't improve anything in most of the cases

the idea is to not do things that would degrade experience by losing data or consuming more battery than stock
yes, it should be "dojox.app.controller"
There is still a problem with this line: "} else if ($options['sort'] instanceof Zend_Db_Expr) {". If options 'sort' is not set, this line raises PHP warning about non-existing array index. There should be a call to 'isset()' function before attempting to use $options['sort'].
hello, tom, sorry for disturbing you,
can i ask about this line?

i trying to compile kernel for my own blade, but got undefined reference for pm_modem_sleep_time_get

do i miss somethings?
thanks :)
`networking_basics` drags in a ton of stuff that Elastic Search (and most production systems) do not need. At least it used to. Plus, if this is the networking basics cookbook I am thinking about, it has "please do not redistribute" OSS "license". We had to quickly abandon it and rewrite our own for travis-ci.org.
Kan niet vertaald, wordt gebruikt in arrays.xml ;)

Op 24 februari 2012 10:42 schreef Gideon van Melle <
reply@reply.github.com
> het volgende:

> ALTIJD
>
> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/MIUI-Dutch/Translations-Dutch/commit/75e8c325e9b19bb0b0067e89240e630dc4e488e2#commitcomment-1006659
>
to support Michigan's Minority VAP stat.
Encoding for getBytes.
all these static methods is a good argument for migrating big chunks of OF to namespaces.
Thanks for the fixes. Always good to have a good disclaimer :)
Well, every other $this->logical_operator besides "OR" would work as "AND". I guess we'll fix that later
@brownan, I'm either misunderstanding what the `imgx, imgy` parameters to `chunk_render` mean, or this tileset doesn't yet set them correctly. Either way I made this change to get the image to come out reasonable.

The very bottom of the map is cut off though so this is *not* the best way to fix this, so I'm putting this comment here to remember to bug you about it in IRC later.
Hi, this is weird. I don't recall to change these line at all, even adding the indentation.
Is it just me or Github is just not good at differing the file?
Instead of separate `:compile_open` and `:compile_close` options, what do you think about a `:source_wrapper_proc` that defaults to `proc { |source|  "Ember.Handlebars.compile(#{source});"}`?
`It's important to understand that`, this is superfluous in a spec.
@joshmoore @chris-allan @cneves and @will-moore  above changes give the new style of formatting the log file including vertical reading
Basically it will look like: ```2010-01-01 00:00:00,000 INFO  [omeroweb.webadmin.webadmin_utils        ] (proc.1308 ) getGuestConnection:20 Open connection is not available```. Is everyone ok with that?
I included in text file.
I: Bus=0000 Vendor=0001 Product=0001 Version=0001
N: Name="7k_headset"
P: Phys=
S: Sysfs=/devices/virtual/input/input0
U: Uniq=
H: Handlers=event0 cpufreq 
B: EV=21
B: SW=4

I: Bus=0019 Vendor=0001 Product=0002 Version=0100
N: Name="msm_touchscreen"
P: Phys=msm_touch/input0
S: Sysfs=/devices/platform/msm_touchscreen.0/input/input1
U: Uniq=
H: Handlers=kbd event1 cpufreq 
B: EV=b
B: KEY=400 0 0 0 0 0 40000800 0 0 0 0
B: ABS=100 1000003

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="swift_keypad"
P: Phys=
S: Sysfs=/devices/virtual/input/input2
U: Uniq=
H: Handlers=kbd event2 cpufreq 
B: EV=3
B: KEY=40098 2100000 ffff 0 c0040 0 7f07f c3ff0ffc

I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="compass"
P: Phys=
S: Sysfs=/devices/virtual/input/input3
U: Uniq=
H: Handlers=event3 cpufreq 
B: EV=9
B: ABS=305ff

I: Bus=0000 Vendor=0001 Product=0001 Version=0001
N: Name="7k_handset"
P: Phys=
S: Sysfs=/devices/virtual/input/input4
U: Uniq=
H: Handlers=kbd event4 cpufreq 
B: EV=3
B: KEY=4 80000 0 0 100800 0 0 0
Personaly i would have split the route in different files :
hello.php, hellos.php for template and hellodb.php for db query.
Why ? 
because with one file, all application are impacted by the twig configuration, even if you don't use twig in one route (which is the case for the main route).
You should also add a test with doctrine because Silex allow Doctrine Dbal and it would be a fair benchmark compared to other framework.

But that's a nice work, i didnt' have the time to pull my request ;-)
Doesn't having 1 here for the APLL divider actually make 600 run at 300?  Everyone's kernels seem to be done like this, but I changed it to 0 in mine and it seems to work better.
Do you think it would be worth checking for a value at openstack_identity_service_name and warning/erroring? Otherwise it will silently be ignored currently I think, which seems like it might be confusing to debug. I don't have strong feelings since I lack context, but thought I would ask.
Thank you for your comments , john . I'll amend these.
I think this is redundant: in every code path `src` and `kernel` are set. You could change the if to `if src is None or kernel is None` just to make sure.
you could also just return the handle from here and store it in a `val handleB`
Yes, all the logs come first, and the test results afterwards, making it kind of hard to read. (For me at least ;)
The Chicago Manual of Style says that title-casing shall be done according to importance of each word, and "level" is one of the more important ones in this title.
Great, this is exactly the type of feedback I want (i.e. why I used different techniques in the PR)
I'd prefer my solution over using a seed-approach (sine the seed approach doesn't solve the problem of similarly named threads)
The queue size should also be bounded, otherwise we’re looking at OOM quite easily.
Yes, but it is only called on each node when it joins or leaves the cluster.
I think the best compromise would be to directly have the ActorDSL on it and otherwise expose the rest via a `val system: ActorSystem`.
I think they should be the other way around. It's the `consistentHash` that should be in the atomic since you don't want to overwrite it with a stale `consistentHash`. Overwriting the `consistentHashRoutees` with stale values will just trigger a new update.

I would just make it a Tuple. Cleaner I think.
maybe assert that no connection was there before the send
I think I was just being knee-jerky.  I cleaned it up a bit and moved it to Session.
this is going to be a painful merge with new_forms...
Overload is not an elegant by design..
Why are you marking this as side_effect_free?
The html tag must be kept?!
The generated link is a bit strange because it just reads "See the Introduction section of this guide", and of course we are reading a section by that name now. Maybe insert the word "Consumer" before the link so there is at least some context about which Introduction section it is.
Gotcha. I changed it to use `rb_enc_asciicompat` instead.
Not US/Pacific??
Not sure how this went missing.
YCbCr is not a mathematical concept
I think we should finally rename the fields in a migration, but again we already have too much here.  We can do that soon after this, and we only have to remove this and fix up where it sets it to nil in set_names (change the db-field name.  This seems to be the only read_attribute and we only explicitly write the attributes in set_name as I said.
If these were declared in the super class it is better to make them protected there than to redeclare them here.
Due to changes in the way curl handles plugins in the dev branch, you'll need to specify the module id like this:

```js
define(/*=='curl/plugin/worker',==*/ function () {
```
this is wrong according to ES5 spec => http://es5.github.com/#x9.2
I'm not too sure, Loren added that note for `.selected`, and I just prettied up that comment. I would think it's fine, having finally dug up the entire mess that is `TUITableView` and `TUITableViewCell`. I'll remove this bit of the comment if you'd like me to.
@galaxas0 And it does. If you remove this synthesize line, `setCursorColor:` will still be called. You'll need to set the underlying instance variable like this:

    - (void)setCursorColor:(NSColor *)c {
        _cursorColor = c;
        _cursor.backgroundColor = c;
        [_cursor setNeedsDisplay];
    }
This is a big nit, but in the rest of the custom vars, we always end the first sentence in the docstring with a period...
I included the daorecord selector in this file and not in the jelix init file, because of some macros (#ifnot ENABLE_PHP_JELIX, #if ENABLE_OPTIMIZED_SOURCE, ... ).
infomation?
I'm not a fan of the name of that face, since it makes it hard to search for in this file.  And I'd prefer to use or inherit `magit-log-sha1` as the face of the commit hash.

It's definitely a great feature to have.
small doctest + pep8 :)
I understand that. That's why I'm offering some suggestions for highlights. It's not easy to find good ones for this release unfortunately. Mostly lots of small things, refactoring, bug fixes, etc.
Noticed that several of these methods are named ```*_referenence_*``` and should be ```*_reference_*```. I realize you didn't introduce this in your changes, but would you mind fixing this as part of the pull request?
отступ в 2 таба
и лучше, видимо, через else if это все оформить
EdgeId const &e mb
@rafaelfranca can you work on this, I'm no having much luck with this and @spastorino won't have time to check it on the next weeks
No need for extra empty line.
Maybe a `respond_to?(:to_sym)` check is better here.
@pixeltrix lol! No, I don't hate flatten.  I just want to make sure we're not opening the API *too* wide without good reason.  Backwards compat seems a great reason to use it.  BTW, `flatten` will take a depth param:

```
irb(main):003:0> [:a, :b, :c].flatten(1)
=> [:a, :b, :c]
irb(main):004:0> [[:a, :b, :c]].flatten(1)
=> [:a, :b, :c]
irb(main):005:0> [[[:a, :b, :c]]].flatten(1)
=> [[:a, :b, :c]]
irb(main):006:0> 
```
(PR already marked as reviewed, these are just "clean-up" related questions we might want to consider before 2.10-FINAL)

(I know this line is not the best one to drop this comment on, but...) What do you think about hiding the group/section on shadowed or ambiguous implicits? I was thinking that maybe it'd be best even under a flag than even hidden under the toggle menu.
As I understand, all this is correct, but unrelated to the possibility to replace "sym == NoSymbol || sym.name == name" with "sym.name == name". In cases where sym is NoSymbol, we want to do just reifyProduct(tree), there are no observable problems with name here (there would be with sym.name, if we go to second branch); in cases where sym is not NoSymbol, we want to check if sym.name isn't the same as name, which would mean, that we are dealing with renamed import, and, in this case, to reify the whole Select with original name, which is sym.name, so we do reifyProduct(Select(qual, sym.name)). The need for "sym == NoSymbol" actually doesn't come from some bad things which should be impossible by construction, and Selects with NO_NAME as target are another, unrelated problem. Well, the check for NoSymbol could be replaced with "sym.name == nme.NO_NAME", and that would have desired semantics too.
If it does need special treatment, let's expose this in some way that lets scala-virtualized treat it specially, not hardcode filenames from another project into our source, which is wrong on many levels.
What do you think about renaming `isNamed` to `isNamedArg` for consistency?
I think I misunderstood. I don't understand the parameterization for negative skew.
This is also true if ``finish`` is left to its default value.
why are these imported seperatly?
PEP 8 no parentheses.
Basically, what I have said in the last comment: checking that hashes and equalities are consistent even after side effects.
Sure.  Wanted to say both "still" and "as yet", perhaps :-D
You are right, I added Pow. Anything else?
I'll change this if you think it's a good idea. I'm a little bit against it though. My reasons  are below. 

The `is_Matrix` check is very easy to satisfy. You don't need to be a MatExpr or a MutableMatrix object, you just need to claim to be a matrix by setting is_Matrix = True. In your class definition. I.e. you have to intentionally choose to opt into the Matrix world. 

I think that a little bit of type safety is a good thing. For example I can image someone calling Trace on a geometric object thinking that Trace is a word for drawing. I think it would be very strange at that point to return a `Trace(Circle(...))` object. I think this is a situation where SymPy should raise an exception.  The is_Matrix check is what gives us this error in this situation. 

At the moment the Quantum objects are the only matrix-like objects that don't use is_Matrix (a positive example are the gaussian optics objects which do use is_Matrix)  In the quantum case this Trace isn't appropriate anyway - the interfaces are not the same. They use a separate Tr object in core just like how they use a separate Add object in core. I think that we don't gain anything by making this more permissive. 

If in the future we choose to merge quantum and matrices then we should definitely think about what needs to change on both sides. My solution in that case would be to just add an `is_Matrix = True` line in the QExpr definition. 

In short. I usually like close-mindedness when it comes to types. I think it serves a useful purpose. Additionally in this particular case I don't think we gain anything by being open-minded.
looks weird but enabled needs to be false before to ensure event handler get attached. I could only do `setEnabled(true)` but then someone can use setEnabled before attaching and so event handlers do not get attached.
Isn't it possible to avoid the special case here?
Agree, `encodePassword` would be better.
((handle)->io_watcher.fd) - i.e. parentheses around the expression.
ok then; should I make it userdata or lightuserdata?
I completely agree. This is something I am embarrassed about.
You should not generate invalid xml. To do this you need to reject input that will result in invalid xml being generated.

array('<'=>'<') is a valid array. What will your function transform it to?
forum_id can not be 0 anymore
Also, "determinate" is not a word. Just "determine".
Dots go on the end of the line I think.
Missing `@var`
If I block a user that wants to read a topic in forum A because the f_read_other failed. I may not say that he may not read posts in that forum because he may be able to view other topics in that same forum.
Why are all these lines commented out? If they shouldn't be tested the lines should be removed all together.
This seems to be an avatar template's name rather than an avatar's template name.
I don't see why not, it is there for this kind of things.
Put this method into phpbb test case instead of phpbb database test case?
+1. I like this solution. We need to document it though.
Fair enough. Not knowing how heavy-weight an instance of UUID is, I had opted for the class variable, but if there's a different library built-in that obviates the problem, hooray!
A nit, admittedly, but the function of this routine and the name don't mesh for me. parseYUIModule implies we're going to read, but this routine does a lot more, it fully initializes a range of data structures as well.
Ah, I didn't know. Because of the location, I thought it would work with non-steam as well.
These blank lines within the methods should be removed.
Sneaky sneaky. I have a simple cartopy example of how to do this somewhere - is it worth doing it here & now?
Fixed in gh-1136
I see, you are right. Can you remove this line, please?
Is there no failure response to be handled from SnapshotRestore?
Fetch added data
kill は「中断」って訳した方が自然だ。なるほど。
We could test both scenarios.
Does this work on windows too?
Ohh, I didn't realise this. Sorry my bad - I will amend now.
Hm do we need the ++ here?
This comment does not add more information than the docstring of _create_gmf_cache. I would delete it.
Derp. I didn't see the references to oldName.
Oops. It was a bug fixing the bug.
Any benefit in something roughly like...

```js
var op = "push";

while ( (dataType = dataTypes[i++]) ) {
  // Prepend if requested
  if ( dataType[0] === "+" ) {
    dataType = dataType.slice( 1 ) || "*";
    op = "unshift";
  }

  (structure[ dataType ] = structure[ dataType ] || [])[ op ]( func );
}
```
also here... @gnarf37 was only talking about spacing
No, this should be "This is you."
We don't use int.
Can you point me to the file?  FunctionHandle?
This language could be misleading. You and I know why search being unavailable is a problem, but it isn't clear to not-us why search would break the home page with the pretty graphs, especially because there isn't even a search box yet.
Please adhere to convention and just use

```rb
depends_on :autoconf
depends_on :automake
depends_on :libtool
```
https://github.com/mxcl/homebrew/pull/13561
https://github.com/mxcl/homebrew/pull/14357
No need to alter the indentation here.
results { say "Ending port forward" }

No ....
Why the `none`? Why not have the message be `{unprepare, Name}`?
wouldn't it be easier to just always call normalizePath on $target
Совершенно верно.
Я бы ещё перефразировал «некоторые приятные удобные возможности» – во-первых, по-русски так не говорят (просвечивает дословный перевод с английского), а во-вторых, речь идёт о вполне конкретных возможностях (подсказки, как отменить изменения). В оригинале: “get some of these nicer usability features”.

Предлагаю такой вариант:
> Здесь довольно ясно сказано, как отменить сделанные изменения (по крайней мере новые версии Git'а, начиная с 1.6.1, делают это; если у вас версия старее, мы настоятельно рекомендуем обновиться, чтобы получать такие подсказки). Давайте сделаем то, что написано:
I don't really like this call to '_makeResult', but could not find a better way
I think we should avoid `root` because it isn't necessarily the root. You can extend an extension! It really sucks we can't use `extends`. Hmmm. . . . .
I use `AssertionError` to indicate problems that I believe are impossible. If I could write a (reasonable) test case for it, then it wouldn't be an `AssertionError`, but something weaker like an `IllegalStateException`.
The static help() method is not supported anymore. Please create .txt files in `src/docs/` for each subcommand.
我有点好奇，Mac的图形设备不是Aqua吗？跟X11什么关系？

另外这几行修改我已经手工加进来了，所以这个pull request就关了哈。
I am not native speaker.
Pls have your eyes on the text.
Thx.
In general, it's best to minimize what you put in a try block, so I think the call to .remove() should be moved outside the try block.
Checking for this explicit attribute name to be the first may be fragile over time, but I'm not sure of a more reliable way to do it.

FYI, tag name "a" (test above) seems pretty safe :)
Although I just spotted a bug in PopUpManager.removePopUp() that I think causes it to always leak memory anyway :-P  It doesn't distinguish between explicit calls to that method from outside, vs. automatic calls from its internal Esc key handler. Net result: unless you created the popup with autoAddRemove == true (which code hints don't), it will _never_ get removed from the _popUps array.

Do you want to tackle that problem here or in #1381?
Param docs are wrong.  Also, should probably document the format of the Array items.
No need for this check - it will always be true
It is only best even for the simplest textual completer to show up some smartness differentiating functions from variables.
That's what I do with the icon - showing difference between `PHP` default functions and default variables
However, the same doesn't strictly apply to `CSS` --> So, I'm following up with a commit that removes icons from CSS results
Same as before. If you didn't change the other one, leave it be. If you did, please change this as well.
What is the license of this code?
This code is repeated, can you put it in a method?
drawing individual labels with `geom_text`
Finished opacity of what? Nodes? Everything? If only nodes please add "node_" to the front of the variable. If everything it's fine it leave it.
I am not sure I understand what exactly to do here... Is this ok?
Import only modules. Use absolute or relative imports. Not import just "forms". You never know what you get (maybe there is some Python package in Python path with this name).