labofsahil/github-event-dataset-2012 huggingface dataset:
I'm not really comfortable with this change as I figure that line was put in there for a reason originally, the potential for this to break something else is pretty high. Any chance you ran all the s3 tests after making this change?
Ditto.   But anyway, I have a pull request in that makes this moot.
This is your problem: `tomdoc` will never contain two consecutive newlines, as those are stripped.
Please also add this change to r5
According to this my implementation should be wrong. What I haven't figured out is why I didn't get a test failure. My impression is that this is covered by the test cases, which has both large and small values.
I installed everything with the procedure described on the github front page.
The fact that `yesod version` gives me 0.10.1 does not imply that I have the latest executable?

I'll take a look.
Thanks for the prompt answer.
Hi Terence,

I'm the maintainer of norbert, the library that sensei uses for distribution. I'd prefer to move forward with this changeset, and to instead improve the way sensei uses norbert. Sensei doesn't take advantage of newer norbert features to do request customization and routing. By doing so, it bypasses a lot of norbert's infrastructure to protect itself and it's degrader. This is really, really bad. If it just fixes the way it uses norbert, it will receive this implementation for free. This has been a task on my plate for a long time, but I never got around to it when I was on cloud in SNA since it wasn't prioritized. The initial step was taking in January, when we migrated to the latest norbert release.

Norbert already has a class almost exactly like this. See https://github.com/linkedin-sna/norbert/blob/master/network/src/main/scala/com/linkedin/norbert/network/partitioned/loadbalancer/PartitionedConsistentHashedLoadBalancerFactory.scala.  This class builds a consistent hash wheel per partition, unlike your approach. The store space required, however, is the same. It's numPartitions * numBuckets in both cases.

I also believe I see a problem with your approach. You're mapping all the rings onto a single ring. Usually, you look up a position in the ring and "roll" until you find a spot. What happens when a machine goes down? Now a different machine that can't handle the partition will be the next in the slot. So do you intend to iterate until you find the next one?

Let's work together to use norbert's infrastructure properly.
А тут в лог никак нельзя вывести на какой именно карте затык? Было бы ясно тогда точно какие карты поломаны...
removed, not sure what the problem was, thanks @robhudson
Didn't know that handy. Maybe some day you can tell it to #fix nnn :-)

Sent from my iPhone

On 24 feb. 2012, at 10:02, Andreas Stenius <reply@reply.github.com> wrote:

> If you write "Fixes #nnn" in the commit message, the issue is closed automagically by github... :)
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/zotonic/zotonic/commit/af60deb6143412e18afda811cbb6dabc12bea801#commitcomment-1006486
hacky way. The opcode is false =) but it's the better way for the moment =)
Lazy Dev is Bad Dev :)))
also ich krieg teilweise jetzt manchmal extrem wenig, manchmal auch 0. Aber leider auch öfter noch 10:
/home/rbs/projects/Empire/src/tests/RepositoryTests.cpp(51): fatal error in "testRepositoryCreation": Cannot create testing repo dir!
/home/rbs/projects/Empire/src/tests/RepositoryTests.cpp(51): fatal error in "CreatePropertyFromTypeStringTest": Cannot create testing repo dir!
/home/rbs/projects/Empire/src/tests/RepositoryTests.cpp(51): fatal error in "testRepoCreateProperty": Cannot create testing repo dir!
/home/rbs/projects/Empire/src/tests/RepositoryTests.cpp(51): fatal error in "ReadMetaDataFromFile": Cannot create testing repo dir!
/home/rbs/projects/Empire/src/tests/RepositoryTests.cpp(51): fatal error in "testRepoPropDataIO": Cannot create testing repo dir!
/home/rbs/projects/Empire/src/tests/RepositoryTests.cpp(51): fatal error in "testRepoLoad": Cannot create testing repo dir!
/home/rbs/projects/Empire/src/tests/RepositoryTests.cpp(51): fatal error in "testRepoRemovePropertyClass": Cannot create testing repo dir!
/home/rbs/projects/Empire/src/tests/RepositoryTests.cpp(51): fatal error in "testRegexMatch": Cannot create testing repo dir!
/home/rbs/projects/Empire/src/tests/RepositoryTests.cpp(51): fatal error in "AddPropertyTest": Cannot create testing repo dir!
/home/rbs/projects/Empire/src/tests/RepositoryTests.cpp(51): fatal error in "GetFirstDefinedValueRecTest": Cannot create testing repo dir!

das mit dem testRemoveFilesInDirRec krieg ich aber nie...
hmm *"ganze Unternehmen"* vllt etwas zu hoch gegriffen?
I learn something new today "Imbecil" also a English word :P
So, maybe it's better to put it after `.namego` in command table?
http://www.youtube.com/watch?v=F8zIlQGNL_c&feature=youtu.be&hd=1

for the warrior spell work ok, but the priest mass dispel are bug :(
thank rsa :)
tho as i see in comments, both permanent and temporary should be in spellbook.
looks like false alarm, toc shouldnt have shared CD. Maybe only at icc
just couldnt decide if I should set deadly_z to some very low amount, so people cant reach it with swimming neither, or do http://pastebin.com/t7Vw6aPr
Так и есть.
One of your dependencies (possibly clj-stacktrace) seems to be [dragging Clojure 1.2 in](http://travis-ci.org/#!/trptcolin/reply/builds/570838). You can  [exclude org.clojure/clojure for them](https://github.com/michaelklishin/monger/commit/c8fe274329d47c1181da1d1a1e3dfe665143cc3e). This is a known problem with certain github.com/clojure libraries being republished to Maven repositories. Since all dependency installations on travis-ci.org are from scratch, this issue becomes visible.
That is the better way to discover it. :-)

I noticed it when I wanted to use trigger id in an existing event, but
discovered that I had consistently swapped the trigger and target fields
in event functions.

Maas



> +1 :)
> I was going through some zotonic stuff with a co-worker yesterday, and
> noticed that the postback event wasn't made into a record, as the
> notification events have.
> Nice work Maas.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/zotonic/zotonic/commit/9bf749d24c93fb0c35c07c8f912e02693b1d8572#commitcomment-883795
>
It was just a naming suggestion to avoid "lang" as a package or jar
name, like we have now :)

On 7 March 2012 19:10, Andrey Breslav
<reply@reply.github.com>
wrote:
> What difference does this make for the users today (I can see one for later, but now…)?
>
> On Mar 7, 2012, at 23:08 , James Strachan wrote:
>
>> I was thinking we'd include the runtime stuff in the
>> kotlin-library.jar - so folks would either use kotlin-runtime.jar (the
>> minimal stuff) or more likely, kotlin-library (which has everything
>> you need inside and still only about 200K)
>>
>> On 7 March 2012 19:05, Andrey Breslav
>> <reply@reply.github.com>
>> wrote:
>>> I'll have to talk to Max about it. There were some arguments for having fewer jars for now.
>>>
>>> On Mar 7, 2012, at 23:02 , James Strachan wrote:
>>>
>>>> How about kotlin-runtime.jar & "runtime" for the package for the core
>>>> runtime stuff (the stuff you can't avoid) and kotlin-library for the
>>>> core library stuff (thats optional but I'd expect many kotlin folks to
>>>> use it as its so kool)
>>>>
>>>> On 7 March 2012 18:52, Andrey Breslav
>>>> <reply@reply.github.com>
>>>> wrote:
>>>>> I was talking about the first one, not the second, but your suggestion looks good, too.
>>>>>
>>>>> ---
>>>>> Reply to this email directly or view it on GitHub:
>>>>> https://github.com/JetBrains/kotlin/commit/522083bf5a067bf42fb56ce0a6244a3d2b49290f#commitcomment-1054997
>>>>
>>>>
>>>>
>>>> --
>>>> James
>>>> -------
>>>> FuseSource
>>>> Email: james@fusesource.com
>>>> Web: http://fusesource.com
>>>> Twitter: jstrachan
>>>> Blog: http://macstrac.blogspot.com/
>>>>
>>>> Open Source Integration
>>>>
>>>> ---
>>>> Reply to this email directly or view it on GitHub:
>>>> https://github.com/JetBrains/kotlin/commit/522083bf5a067bf42fb56ce0a6244a3d2b49290f#commitcomment-1055042
>>>
>>> --
>>> Andrey Breslav
>>> http://jetbrains.com
>>> Develop with pleasure!
>>>
>>> ---
>>> Reply to this email directly or view it on GitHub:
>>> https://github.com/JetBrains/kotlin/commit/522083bf5a067bf42fb56ce0a6244a3d2b49290f#commitcomment-1055049
>>
>>
>>
>> --
>> James
>> -------
>> FuseSource
>> Email: james@fusesource.com
>> Web: http://fusesource.com
>> Twitter: jstrachan
>> Blog: http://macstrac.blogspot.com/
>>
>> Open Source Integration
>>
>> ---
>> Reply to this email directly or view it on GitHub:
>> https://github.com/JetBrains/kotlin/commit/522083bf5a067bf42fb56ce0a6244a3d2b49290f#commitcomment-1055055
>
> --
> Andrey Breslav
> http://jetbrains.com
> Develop with pleasure!
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/JetBrains/kotlin/commit/522083bf5a067bf42fb56ce0a6244a3d2b49290f#commitcomment-1055065



-- 
James
-------
FuseSource
Email: james@fusesource.com
Web: http://fusesource.com
Twitter: jstrachan
Blog: http://macstrac.blogspot.com/

Open Source Integration
Damn, sure.  Let me fix it




Am 22.02.2012 um 18:01 schrieb mikevalenty <reply@reply.github.com>:

> Would `$project_name.pdb` work here?
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/ccellar/tamarack/commit/6c196204bfdb6bcf73f9dd3078b04911ea596d48#commitcomment-996856
variable _ could be x or something normal. But it is not important.
BSTNode already has attribute "size" = size of the subtree
This is currently on silent, I think everything works
These should be device colors too for consistency
@woxxy, @oohnoitz
You guys should notify me when shit changes.
oiuyiouoiup
:thumbsup: was thinking about the same thing!
not all cultures have first and last name, so presumably paypal is using both to hedge its bets. paypal returns it, i'm storing all of the information
CCCallFunc:actionWithScriptFuncName had been removed, so use which function to instead it ???
Did you figure these out or are they from MacPorts or...?
"If this is failing, then when we initially created the user, it didn't set the smf_member_id in their options. We force/retain the smf_member_id on all options updates by making it a hidden forced setting."

Could you please elaborate on that? I am far from expert, and in my case that was the only way to make it work (see http://www.simplemachines.org/community/index.php?topic=467594.0 )
moving controllers out of constructor
moving mongoose to server.db.mongoose instead of server.mongoose
few renamings
At a really high level, why don't we use this pattern:

    app.configuration("development", function () {
       app.get(/^\/test\/?(?:index.html)?$/, function (req, res) {
          res.render('test.ejs', {title: 'BrowserID QUnit Test', layout: false});
        });
    });

Isn't ``app.configuration`` for these development only type of middleware and routes?
@mrpoodlepants : The client sends an Integer for the card, per the Comm Data Structures / Gameplay example. Right now, I'm just passing that integer from the router to the Game, and the game can match it up with an actual card.
and yes, LGTM. Please push to develop branch after the fix.
What would be the benefit of using it?
that's already in there - line 580/1 - 'running lite' as the comment calls it
This looks yucky. Can we reengineer the above code so that `mobj.group(1)` is always set?
Okay, then my guess was wrong I think...
thanks for the clarification!

Am 15.01.2012 12:08, schrieb Flex B.:
> Sending a ß with newest build:
> 12:07:04 [INFORMATION]<drantor>  ▀
>> version
> 12:07:13 [INFORMATION] This server is running Craftbukkit version git-Bukkit-1.0
> .1-R1-73-g8fee20a-b1763jnks (MC: 1.1) (Implementing API version 1.1-R1-SNAPSHOT)
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/Bukkit/CraftBukkit/commit/44b59dd7e560fe434c374a12f2224fedf1ea7e46#commitcomment-868452
Setting extractionpath lets the rest of the code think it's already in the child process.
<string key = "abc">YES</strin>
my typing/grammar is atrocious :)
If you wrap all code of a method inside a block (begin / end), you leave the begin / end.
@Vasago code carefully
We might remove this implicit "magic", but I don't think that clicking in all links makes more sense. That's not even possible in some cases. Like when there are 20 links in the current page: when you click the first, the current page may change, and the other 19 links may not exist in the new current page.
The method will go away.
A general comments:
* The normal convention in Erlang for atoms, function names and fields in records is to use lowercase and separate words with _ .
This looks good. One thing, the statements need to be closed. Possibly just after the prepare with a 'defer'. Also, you can pass in nil for params. That's equal to an empty slice. I can do this or you can. No bigge.
I don't known `owner.connection.schema_cache` usage. great !
@nfedyashev Could you submit a pull request with this change?
* NOTE: SQLite doesn't support RANK() ON or other windowing constructs.

On Wed, Jan 18, 2012 at 12:39 AM, Ronald Chan <ronalchn@gmail.com> wrote:

> Fixed for SQLite now. Views are not a problem. Almost all SQL databases
> support them. Just that SQLite doesn't support the DateTime datatype nor
> the DISTINCT ON (fields) construct. Also used RANK() ON (PARTITION ...)
> which is available in postgreSQL to automatically rank scores.
>
> Latest commits working around them, either with a slightly weird query, or
> some ruby calculations. Note db:migrate has different queries depending on
> if SQLite or other SQL database.
>
> If you ran db:migrate on SQLite run before, you might want to run "rake
> db:migrate:redo STEP=5" to re-do a query change I made to cast
> string-formatted pseudo-date datatypes into integers before performing
> arithmetic on them.
>
> If you haven't pulled changes for about a day and you're on postgreSQL,
> please run "rake db:migrate" when you git pull.
>
> Ronald
>
>
>
>
> On Tue, Jan 17, 2012 at 11:17 PM, Kitten <
> reply@reply.github.com
> > wrote:
>
>> also fuck yes to boris' comment
>>
>> On Tue, Jan 17, 2012 at 9:08 PM, Boris Pfahringer <
>> reply@reply.github.com
>> > wrote:
>>
>> > Jamie,
>> > keeping it generic is useful for local development. Setting up Postgres
>> is
>> > a pain.
>> >
>> > Boris
>> >
>> > On 17/01/2012, at 22:55, xrymbos<reply@reply.github.com> wrote:
>> >
>> > > We've already moved to postgres, SQLite was slow as balls. Is it worth
>> > the effort keeping this general in case we want to move away from
>> postgres?
>> > >
>> > > ---
>> > > Reply to this email directly or view it on GitHub:
>> > >
>> >
>> https://github.com/xrymbos/nztrain-v2/commit/fde356ae57afdb6b8e746bd5a95bfaec04b2f224#commitcomment-873649
>> >
>> > ---
>> > Reply to this email directly or view it on GitHub:
>> >
>> >
>> https://github.com/xrymbos/nztrain-v2/commit/fde356ae57afdb6b8e746bd5a95bfaec04b2f224#commitcomment-873671
>> >
>>
>> ---
>> Reply to this email directly or view it on GitHub:
>>
>> https://github.com/xrymbos/nztrain-v2/commit/fde356ae57afdb6b8e746bd5a95bfaec04b2f224#commitcomment-873711
>>
>
>
I'm not following why we are testing that adding an entity, will invalidate the query cache.  If this test fails, what does that mean?
No need to do this. ````getNode(int)``` throws ```IndexOutOfBoundsException``` if the argument is out of bounds. ```removeNode(int)``` should do the same thing.
Looks great! Nice job indeed.
Ooooooops !
Buy means Bye :D
Style -- this should all be on one line
This commit changed dependency on qt from 4.6+ version to 4.7+.
@hendrens thank you for your contribution.  Do you plan on submitting a GMLWriter as well?  

Also, note that there is a "hidden" test suite that needs to be implemented...here's the one for GraphMLReader:

https://github.com/tinkerpop/blueprints/blob/master/blueprints-test/src/main/java/com/tinkerpop/blueprints/pgm/util/io/graphml/GraphMLReaderTestSuite.java

It's easy to implement and ensures a consistent set of tests across all the "Readers".  Could you please add that to your pull request?
I have commited new changes. I agree with you. I had no time to check if toolbar condition could be deleted, this simplied things a lot. thx!
Crap. I so thought this would be useful as a first commit.

What about the change to other pen? Is that at least.. less useless? I can close this and reopen a fixed version.
@wangkx which is better to use? align="left" or style="text-align:left"
В этом месте проверка any(оf class), конечно тоже может быть, но она недостаточно сильная. Попробуй добавить проверку с ипользованием refEq(), то есть равенство объектов с т.з. прохода по полям через reflection.
**Note**: setting CC, CXX and FC as environment variables is *supported but discouraged* in CMake.
The preferred way is setting the CMAKE_xxx_COMPILER variables.
On my amd64 with 8Gb of RAM it dies with abort trap, but setting ulimit -d 6000000 makes it playable. Also it increases speed of loading objects on start.
P.S. This game has the craziest controls I've ever seen!
Both the two solutions work, but not always work.

When combined, the probability of failure will be 1 - P(failure_a)*
P(failure_b), and it's improved.

It's better that we can find a solution that works all the time, but
currently I can't find any for the moment.

2012/1/19 Ari Maniatis <
reply@reply.github.com
>

> Dubious about that logic:
>
> One thing that doesn't work + one other thing that doesn't work = ?
>
> :-)
>
> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/liufengyun/jobsworth/commit/3ba7728123314582219cb5ee665596c54dd227e2#commitcomment-881317
>
It's better than none till Opera implement native notifications.
Quite right

On 07/03/2012 14:20, Dent Earl wrote:
> Shouldn't this initialization be
> <code>i = (None, None, None)</code>
> Since you're now expecting this function to return a triple? See the call made by<code>getUpdatedJobs()</code>.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/benedictpaten/jobTree/commit/0580ca24d6c8915964edf711f60729f10dacfb9a#commitcomment-1055948
Makes sense to me; thanks!
Yes, I did try that out to see how far I could push the Distributor. The problem is that the publishing code needs to know too much. Its not so bad if you only have one group to worry about, but what happens when you have a second group (or more) to distribute to? That group will need its own distributor and the publishers will have to know to send the right messages to the right distributor. At that point you've lost all that nice decoupling.
traingular => triangular
@blafoo: Please follow the rule of first creating an issue, and only after some time implementing it (or provide a pull request, if you want to hack the code immediately). We've seen several times in the past already that just introducing a new feature via commit leads to heavy discussions which should have occured _before_ writing the code. Otherwise the other developers are pissed because they don't agree with that implementation and the implementer is pissed because he can maybe throw away half his code.
If there defaults are already in AWSM then I can remove them here.

In subsequent commits I've made the API more permissive and allowing the server to handle errors (it does a better job).
Signs have a 15 character limit per line. So infinitearrows, and arrowknockback barely fits when appended with ":5". This applies to some other enchantments.
Are all of these strings still used?
I attach it to the window and set it to a var so I can get a reference (an ID) to this later if needed. For example, maybe you want a button that stop auto save you could then do `saveTimer.clearInterval()`. 

https://developer.mozilla.org/en/DOM/window.setInterval
I've just added a `config.tinymce.base` option: bb4fec39ee943aea3fa9d1a44895aebdc2ada1ff

To override the autodetection, add `config.tinymce.base = "/assets/tinymce"` to your `application.rb`.
The problem is that those issues are not SMALL and it almost month past with no comments from developers.
p.s. I'm talking about arkcore, not arkcore2.
not sure how grep is used to parse tree structure. If you want to have a way to do that, I'd highly recommend proposing another text output mode. What is it you're trying to achieve?
Changing Dialect to implement ConversionContext simplifies some code...
kliver because 0 errors are a must.
looks like soon we will have more unstable core :))
strange name for a flag.... what does the 'new' signify?
:D funny  now uve added it xD
y not implemented yet but theres a implement for that outside anywhere
Надо очень внимательно почитать про cancan и использовать данный функционал по полной.

Конкретно здесь:
 - в REST action-ах уже определены @album or @albums (в зависимости от того что надо). Соответственно строчка @album = Album.new лишняя, точно также как и @album = Album.find(params[:id]) (этот запрос уже выполнен cancan-ом). Убедиться в этом легко: поставь сразу после def new; raise @album.inspect и ты увидишь что это новый (id = nil) объект Album (при чем возможно там уже будет проставлен user_id). То же самое относится и к методу show, edit (там тоже лишний код)
This is actually not required any more (it was there because loading the flash file could fail). We can probably simplify this.
`Movie.find_all_by_rating(selected_ratings, :order => ...` (ks. http://blog.hasmanythrough.com/2006/8/13/how-dynamic-finders-work)
Implicite flushes are something very horrible to me:
Unneccessary flushings often creates serious implications when working with long-time transactions.
On long-time transactions the time-window between flush and final commit become big enough 
to cause lock-timeouts on concurrent transactions.

In my opion, like on all Hibernate Query-Apis, the user should have the possibility to choose between variuos FlushModes.
Example solution:

SimpleNaturalIdLoadAccess naturalIdAccess = session.bySimpleNaturalId(MyEntity.class);
naturalIdAccess.setFlushMode(FlushMode.AUTO); // flush if required
naturalIdAccess.setFlushMode(FlushMode.COMMIT); // don't flush until commit time
Object obj = naturalIdAccess.load(id);
Edwin speaks in third person!
riposte = {:haters => "gonna hate"}
riposte.to_json
 => "{\"haters\":\"gonna hate\"}"
Don't work with Xcode 4.3 where the developer directory is gone.
uhum? /system partition, please change it into /data xD
line [1992](https://github.com/toastdriven/django-tastypie/commit/09919753c0649023a7f247fba9e9f1c95ccc3542#L0R1992) returns unauthorized on resources with ReadOnlyAuthorization
This implementation is supposed to be model-based, thus controller should not be an option. I strongly request that we remove this.
My rule is NEVER put state in mixins. If you're doing that, you are building classes but in a more awkward way. It's better to depend on an interface than an implementation.
> It's a bit counter intuitive and will lead to bugs when overriding get_renderers without awareness of that detail.

Totally agree. I didn't think enough when writing that. I just wanted to cache the renderers, but that's not really necessary.

I think :

```python 
def get_renderers(self):
    return [cls(self) for cls in self.renderers]
```

... will do, I'll keep it simple, no need for private methods here.
`readThreadVisib();` всегда вызывается посмотри чуть ниже - 594 строка.
@Subv What did you expect  ? AlterEgo iq is under 50, don't blame his stupidity.
"default".
When deleting a column, Cassandra leaves the row key behind.
This is expected when using Cassandra and we can't actually delete that row key as well. 
Since it deletes by writing tombstones the data is still there until the next compaction. Eventually it will go away completely, but the application code must be aware that an empty row is the same as a deleted row.
Das ist nicht inkonsistent, die muss UHMapLoader.py heißen, weil die Plugin-Klasse so heißt. Gleichzeitig enthält die Datei aber auch die Klasse MapLoader, die das laden übernimmt. UHMapLoader registriert nur MapLoader als loader im FIFE Framework. Ich finde wir sollten uns hier an die Tatsachen halten und nicht einfach die Namen anders machen als im Code. Das gleiche gilt für die Saver weiter unten.

Ich hab das jetzt erstmal so geändert, dass es zumindest konsistent ist (vgl. Z. 185ff). Wenn du das weiterhin lieber ändern möchtest sollten wir da denke ich drüber reden.
This looks useful, thanks.
So what does command-I do in eclipse? Does it see that I use tabs and then
make it consistent? If I used spaces would comd-I convert everything to
tabs?

In article 1 it says that the key is just to be consistent so what is the
point in changing to spaces. This particular piece of code was mostly
copied from a GWT example and therefore inconsistent.
On Jan 7, 2012 5:21 PM, "Steve Loeppky" <
reply@reply.github.com>
wrote:

> Pros:
>        It enables someone to have more control on how their code is
> displayed. You may like tabs 4 spaces wide, and I may like it 3. By using
> tabs for the initial indent, we get an abstraction to be able to configure
> this.
>
>    Cons:
>        A programmer has to be more conscious of what they're doing to
> determine whether they should be tabbing, or spacing. Jeff Atwood believes
> it combines all the complexity and pitfalls of both approaches.
>        In practice, haven't found the necessary attentiveness for this
> being present by default.
>
>    Relevant articles:
>
> http://www.codinghorror.com/blog/2009/04/death-to-the-space-infidels.html
>        http://blogs.msdn.com/b/cyrusn/archive/2004/09/14/229474.aspx
>
> ---
> Reply to this email directly or view it on GitHub:
>
> https://github.com/BigLep/ChuckanutBayFoodsInternal/commit/076fd524cba98ddfd73928c5a265d9ed1bd4ebee#commitcomment-846963
>
That would be a bit simpler to maintain. +1 from my side. Maybe @mojavelinux and @alrubinger some comments on that ? :)
Personally I would say -1 for email addresses in the docs. I find they are just bloating things as the authors are listed anyways, so you can be reached either way. You don't get more reachable by repeating your email 5 times on a page.

I think when we did the first cut of the spec we basically just cut&paste the whole code the API. Personally I think we should remove the email addresses.
Some general comments:

* I imagine this will be very slow when the wiki is large (some thousands pages). Maybe it would make sense to save the result somewhere and update it on every save of a page once it has been built so it would only need to be built once. Building it once could be done in the indexer or with a special admin plugin in the admin backend.
* What about page caching? Currently the calculation is expensive so it makes sense to cache it but once it is cheaper, maybe it makes sense to either add a custom cache handling that checks for the modification time of the file "purgefile" in the cache which is updated whenever a page is changed.
This stuff shouldn't be in here.
have you had this successfully build? i still error on -l${LIBCAMERA_BUILD} not found.
Si quelqu'un a quelque chose à redire sur quel fichier que ce soit ou sur n'importe quel élément, qu'il me fasse parvenir ses quelques réflexions quelconques.
J'espère que j'ai pas niqué tout ce que t'a fait Cédric :D. Au pire j'ai un backup de Solution sur mon ordi
Perhaps we can keep the $ argument for now but mark it as deprecated in the docs so we don't break backwards compatibility for people currently using Bean stand-alone? Then remove it later?

The Ender bridge will need some work too now to rework the delegate handling.
Yeah, I know, my first version of the code had no duplication, but then I decided that following the existing approach (i.e. the _parse_fn_map) was worth a couple of duplicated lines.
This is not necessary for the Shown/Hidden events.
I double checked. The exception is just a shortcut to be caught a few lines down in order to set the status code and the error description as part of the AJAX call.
Your right it is almost a duplicate of the EncryptedMapDecoratorTests tests. However, that test uses the size() operator which Memcached doesn't support so we couldn't use it without removing that part of the test.
This doesn't quite work because $raw is not available to the closure. Fixed in a subsequent patch.
why this had different value than name?
This should be private[akka] and be documented as internal api.
don't return null, it's broken, throw exceptions
`isEmpty`
This seems to only work on ZMQ >= 3.0
Doesn't that do a copy of the original collection?
Would it be preferable to have a "foreachChild"-method instead?
The convention for makefiles is that DESTDIR is used as an alternate root, for packagers. This should actually be PREFIX. It should be like this:
```
PREFIX=/usr/local
DESTDIR=
```
(let DESTDIR default to blank)
I'm not 100% sure on the name hidden_list makes it sound like it is a hidden list rather than multiple hidden fields.

maybe hidden_fields is a little better can you think of anything really clear?
extra space after "="
Fixed (no idea how those got so out of whack, moved the Config one up a space too)
Last run will be updated by the main task in the group, and *only* the main task :)
Not thread safe but this is not really new, the entire method is not thread safe. I suggest to add a doc comment to syncModel() saying the method is not thread safe and MUST be invoked before start(). If you are in the mood, you could validate that the storage is not started...
length instead of range?
is this what got printed as None? 

Should it have gotten printed as None?
Cool... one last thing, do you want me to collapse all of these commits?
Note that this doesn't quite do what you'd expect if `s` is already bytes; I don't know if that's a problem:

```
In [2]: s
Out[2]: b'abc'

In [3]: bytes(str(s), 'ascii')
Out[3]: b"b'abc'"
```

Something like this would handle that case:

```
if isinstance(s, str):
    return s.encode('ascii')
return s
```
Does this not need to be reversed anymore?
Should be getIsElitist?
I suppose this is strange to me. You say 

I could throw an exception, but it seems overkill since the message should rarely (if ever) actually be killed when someone tries to send it.

I recognize it probably shouldn't be "killed" (though I'm not sure I know what you mean), but it's also not being sent in the case in which it's direction is neither set to up or down. In order for it to get to this sendOn function, someone has tried to send it. However, it quietly fails to be sent on if it's malformed and there's no warning or exception to alert the user that it's not being sent. Should it not at least be validated for send so that exceptions can be thrown when it doesn't validate?
you're right.  that's not being handled correctly.  another commit coming to handle things better.  keying off of the class isn't ideal (or probably particularly performant) so trying a different approach.
Current system font doesn't match the font as it was there though. See [a](http://cl.ly/image/1a0D383g2a21) vs [b](http://cl.ly/image/37162j2D0K3f).
Multi-line `if` statements should always have braces.

This logic should be factored out into a common method that can be invoked for `selected`, `highlighted`, and `floating`.
ok, i'll wait for it
needs a space in between `function()` and `{}`
This might confuse people.... I don't understand why should this option be exposed in APIs? For compatibility only? If so, probably it would better to display some warning on setting it twice..?
wouldn't it be better to throw an UnsupportedOperationException ?
rename: SmoothTesselation
I don't feel much sympathy for many things we unfortunately have to support. Point not taken.
аа, понятно. а можно тогда этот треугольничек рисовать не как сейчас прямо поверх элемента, а немного отступив? вверх или вбок, скажем
If you guys are OK with it, I can make a separate pull request
I am not sure why it's there in the first place
Can this be handle by Hash#invert?

```ruby
# before
Hash[args.zip(keys).map { |v, k| [k, v] }]
# after
Hash[args.zip(keys)].invert
```

Wdyt?
Also the second argument is not a `type` it is a message, so it can be a string.
One last thing. This method is mutating the options hash. I think this test will breaking now:

```ruby
def test_truncate_should_not_mutate_the_options_hash
  options = { :length => 27 }
  truncate("Here's a long test and I need a continue to read link", options) { link_to 'Continue', '#' }
  assert_equal { :length => 27 }, options
end
```
Apps rely on `config.assets.digests` so changing it in our stable branch won't fly. How about keeping the existing manifest and introducing a new one alongside it?
I'm not sure why this won't kick up a NameError. DEBUG doesn't exist in the namespace, yet. Do you mean ``'DEBUG'``?
Unfortunately getOrElseUpdate is very slow compared to writing the same logic by hand.
s/Symbol/Symbols
When possible, it's best to avoid this sort of ``x == x`` test. If you want to check that something hasn't evaluated, you can use something like ``.is_Function`` to ensure the expressions are valid and they return a symbolic Expr.
To display this result, you'll either need to split the cell here or use ``display()`` from ``IPython.core.display``
or maybe to show that you have to extract the data somehow,

```
converter[OtherList] = lambda other: Matrix(1, len(other), other[:])
```
... and same comment about shortcuts again.

Here a very clear case can be made: I would naively expect most of these to be about objects, not morphisms.
Stopping here for today.
On Wed, Apr 11, 2012 at 11:14 PM, Tom Bachmann
<reply@reply.github.com>
wrote:
>> -                bs = bs.removeO()
>> -            if bs.is_Add:
>> +            terms = bs.removeO()
>> +            if terms.is_Add:
>> +                bs = terms
>> +                # if as_leading_terms should only handle results from series then
>> +                # use this:
>> +                # lt = b.compute_leading_term(x, logx=logx) # arg = sin(x); lt = x
>> +                # instead of this:
>> +                lt = terms.as_leading_term(x)
>> +                if logx is None:
>> +                    pass
>> +                elif logx.is_Symbol:
>> +                    lt = lt.subs(log(x), logx)
>> +                elif logx.args[0] == -1 and logx.args[1].is_Symbol:
>> +                    lt = lt.subs(log(1/x), logx.args[1])
>
> Do these lines ever do anything? Because _eval_nseries should not return log(x) terms if logx is passed.
>
yes: None, p (for log(x)), and for -p (for log(1/x)) are passed.
Heh, it never occured to me that `$_SERVER['SERVER_PROTOCOL']` could be empty. I'm not sure if `HTTP/1.0` is a good default: `Last-Modified`/`If-Modified-Since` are 1.0 headers while `ETag`/`If-None-Match` were introduced in 1.1
removed in 1f653c5
Why do you say before :all is evil?  It's easy to misuse, but in this case, it's used to set up a number of variables that don't change at all over the course of the tests.  (In fact, because the RealtimeUpdates object itself doesn't store any state or change over the course of the tests, it should probably be moved into the before :all filter, because it executes an expensive call to Facebook to get the app_access_token each time it's initiated.)
As we discussed, I still think the object should either a) not implement an __eq__ function, or b) conform to the same comparison as Python floats. I really just can't see the use case for asking if two Angle objects are equivalent without caring if they are the same object (e.g. use 'is'), or if they are exactly equal (e.g. both zero, angle1.degrees == angle2.degrees).
Bug: uv__stream_try_select() returns either 0 or -1 and it's in fact returning -1 on my system.
print_all_project_parameters => print_all_parameters
This is not all project parameters, but only part because some files are not included/required by all executables.
Also, I think some Javadoc about what the interface does would be good :-)
This release note should be in the next.md and the new feature should be denoted against the id of this very pull request.
@scotthernandez suggests MB not Mb.
/currently/d
I don't think this is true.  connPoolStats can be useful on a mongod as well.
Would prefer to see this do equality testing, since relying on identity here may not be future-proof.
Why do you pass `request` to the template?
Reversed arguments make the test confusing, as above.
Right. And what if no time has elapsed between #68 and #76?
Please put comments on their own line.
That's fine - as I say I want a consistent decision on this. I've re-added them, then removed them again, I don't wish to re-add them only to get a comment saying they should be dropped once more :D

Personally I would disagree with third party use of phpBB functions as a reason to retain BC. They aren't released as standalone libraries and thus peeps should be mindful and watchful of any changes made to core functionality. Otherwise you could end up littering the codebase with all kinds of unused code. I remember having this discussion many years ago now, and that was our decision then. I guess it's changed and again, that's fine - but I'd like to see agreement in comments :P
I went ahead and just made a phpbb_controller_exception class and replaced all uses of RuntimeException with it.
No it's not compatible and the old one was named timezone, so I guess that was the reason why it was changed to `tz`
Can `forum_id = 0` on develop?
Instead of sprintf(), use the $user->lang() method like so:
`$user->lang('POWERED_BY', '<a href=...');`
Color should either be made conditional as done in commit-msg hook or taken out entirely as in the rest of this hook. It will probably cause problems when a git gui is used in windows.
de unde vine HttpResponsemessage ?
Right, obvi... this is the part that fails otherwise for some reason...
Camelcase properties
unwanted code formatting?
naming consistency. ```addIssue```?
I find int64 is more explicit and clearer than 'word'
They make the doc say *CoordSystem* rather than *iris.coord_systems.CoordSystem*
I've removed the commit that put tags as an input. Tags should now be back as required to create an Op.
Done.

thanks
Wrong answer: For IndexScan, "return true" means return with no rows found.  For IndexCount, the correct response is to set the count row to 0 and put it into the output table.
It's only used once, during initialization.  I can remove it...
No need to use opener here, you can just do urllib2.urlopen directly
Добавить второй опциональный параметр с суфиксами
I don't think we need a more explicit guide. ``reverse()`` is documented and ``get_absolute_url()`` is documented, I think it should be fairly obvious what to do.
nitpick, but if all you want to do is check a value exists that matches the criteria, you can use '#any?` which is a little more intention revealing imo.
I think that it's not very important if we implement do-notation, so left this braces in the code
Grouping parens?
oh sorry, didn't see this. I just did `$(container.firstChild).offset()`, that's still fine, right?
Please change all of the single quotes to double quotes.
I was in the middle of this. This can be reduced even further by combining with the return value on the next line.
I assume this catches `window.setTimeout` and stuff? Could you add a comment describing this behavior?
This is still to be made sense to me :( If you are firing a JIRA for this I would place it in the code.
This is a good point, and we have replaced that code with a more concise matrix multiplication.
I would rather call it categorical attributes (we do accept floating point attributes).
Same things goes for the input taking single objects and lists.
I can't find any ITP bug in Debian or similar in Ubuntu. I'll package it for apt.mopidy.com with time. Maybe even push it to Debian if I get inspired to find a mentor.
Options are then to (a) ask upstream to provide a versioned download or (b) this can go in an external repo; we can't accept non-versioned downloads into core.
Homebrew feels like a permanent code sprint :-)
I've tried and I confirm: gegl does *not* compile on Mac OS X Snow Leopard. I have a "clean" and recent SL install without any addition, except for homebrew and Xcode of course.
I don't currently have the exact error messages, but I've already dug into the errors and it was due to OpenCL not being at version 1.1 or later.
We can't because of the way the Commander code is structured. They allow a --trace to be passed in to get stack traces printed out otherwise they handle it themselves.  Unfortunately the code that does this is in  run_active_command and not run!.  I suppose we could pass in --trace for everything but I am pretty sure that could cause issues down the line and doing so without setting the flags would be just as invasive as overriding run_active_command.
If requesting /alias/dir/index.php/pathinfo
$pathInfo == '/pathinfo'
Celui là aussi peut être regrouper.
I'm a little confused about the difference between the access token stored as part of the Reddit object and the one as part of the config. I don't see the need for both. Unless there is a use-case for storing access tokens or refresh-tokens in the config file (how long is a refresh token valid for?), I think both of these settings need only be contained within the Reddit instance. However, it does seem that the url fetching part of the config depends on whether there is an access token or not so in that case maybe these attributes should just be part of the Config.
Are these yet to be implemented? Pending specs might be better
I don't consider dagger.internal to be a user-accessible plugin API.
The README is what users see when they first navigate to the site.

I'd like to leave the links to external resources (in particular Trello and JabbR) in addition to a brief introduction to the repository (like above).
annotation is a better name for the variable.
Some environments (I'm looking at you jsdom) take case insensitivity to the next level by downcasing all the attributes such that they are only accessible via lowercase. We rely on both jsdom's and the browsers' to have this behaviour in the `parseNode` step as well, but there it's done by regular expression and the baked in expectation that the thing comes out lowercase.
We could make this more bulletproof by also checking that `collection.respond_to?(:each)` so we are sure it can be converted to an array.

We also might have to do this before line 26. The way it currently looks is if I use a limit parameter with a `collection_collection_drop` it would not work as expected.

A regression test would be good to ensure it's solid.
Shouldn't be. We will only have 3 apps right now, with custom freqs. I want to observe it and spot check them for a while. If it is too noisy, I'll turn it off.
The button isn't hiding and showing, the playlist is. `playlist-visible` toggles the color of the button, so that it's inverted when the drawer is open.
The way this iterates over lines means you won't catch cases split across more than one line.  I think that's an edge case though, so maybe just put a TODO mentioning that?
Added test and filed #2384
Calling `_onError(..., { message: "" })` would be valid, though, since it's using the excepted format. However, calling `_onError(..., "foo")` would not, and that's what I want to detect.
Same here, need translation.
This states "... only works for edits to CSS code ...".

This only works for edits to *external* (i.e. not embedded or inline) CSS. Is taht worth mentioning?
In these three lines, it seems like we're using some specific knowledge about how the sidebar's children work, which breaks encapsulation. It would be better to create explicit methods on appropriate objects (WorkingSetView and ProjectManager, maybe?) called something like "notifyResize()" that localize these bits of logic into those objects--or, conversely, have the sidebar be an object that sends an event that the children listen to. Ditto for the sidebar selection.

As an aside, ProjectManager right now isn't really properly factored--it both contains the project model and the controller for the file tree; we should split those apart eventually...
Also, what do "show" and "hide" mean for MenuItems?
Yes, it's certainly ok. For example, after the user types ``h1 {``,  we are already in property name context but no property name yet.
Much safer. Done.
Ah, nice touch!
maybe reuse `'ace/mode/css/csslint'`?
I sometimes use them (more often, lately) to indicate "grouping" rather than "separating" with ';'-- especially when written on one line as here. The intent is to show visually that the three operations always go together. It's easily argued that the function itself already does that and should be three lines of semicolon-separated code, but that's the reason.
Is this coming from something like ```Shop.find_by_sql "SHOW SLAVE STATUS""``` if tat is the case it will return ```[]``` instead of nil
Can you put the brace on the same line as the function declaration please?
Correct. In fact, you'll see that I wrote an auto_test demonstrating it.
Probably doesn't matter, but when I looked into it, you can avoid the overhead of creating these functions for every case/form that doesn't match the `if` condition if you use the `var typeOf = function (...` notation, and put the `// !code util.js` inside the if.

Also probably has ~no affect on anything.
No, null or empty only tests null or "", not null or "<arbitrary number of blanks>".
Get rid of the code and remove the comment block.
OK. to go one step at the time. I created new field language to be saved to user profile which value is current language code. When user registers current language is saved as his preferred language *(currently user can't select prefer language, except if he changes language in footer)* and language stays as it is when user is logged in. When user logs out display language changes back to default browser settings language (what i think is OK), but if i log back in whit that user language doesn't change to user preferred language, but stays the same.

I will update the code and then you can see the behaviour for your self.
Using local variables now.
Contenttypes are using relation database.
Shouldn't you also do _popcorn.off in the close function?
I chose to go this route because of the difference in the query string, the options and the paramater names the API uses.
Much more misleading if document was signed and then appears as having no signatures made. Nevertheless, all traditional pdf viewers show annotations, with or without digital signature.

As I said, signature validation relies on regional standards, so the way user will be informed about present signatures and its validity be different in partcular applications. 

As of fillXXXXAnnotationOperatorList — yes, these functions have to be joined. I'll commit fix on Monday.
What about something like this to cover both?

```ruby

def javascript_confirm(result = true)
  raise ArgumentError, "Block required" unless block_given?
  result = !! result

  page.evaluate_script("window.original_confirm = window.confirm; window.confirm = function() { return #{result.inspect}; }")
  yield
  page.evaluate_script("window.confirm = window.original_confirm;")
end
It seems the not-centering for non-static navbars is a regression introduced in bootstrap 2.0.2: https://github.com/twitter/bootstrap/issues/2548

I'm hesitant to add a work-around for that, it's probably best to just wait for the new bootstrap release. That's not going to fix the rounded-borders, but these weren't my biggest concern with this anyway. :)
> However, since we disable the API by default, it means that travis won't run any of the API tests. That sucks, too.

We do have a `settings_test.py`, so we could choose to run the API tests on Travis.

Okay, so lets keep it this way. We agree that it's not the optimal solution, so I might look into that later and see if we can come up with a fix.
- copyright header missing
is this actually used somewhere?
Yeah. Good catch.
This looks like a strange syntax to me, but if you say it works... :-)
Does this need to be a template? No variables there.
As stated in commit description - it does not build on Fedora 17 as ruby 1.9.1 has problems with this syntax.
And in build time,this is executed to generate API documentation.
Given that #switchContainer is an ID and can only exist once, do we need the `$(switcher.target).parents` part?