labofsahil/github-event-dataset-2012 huggingface dataset:
window.parent.postMessage will not work in the current version of Gaia run on top of B2G (The rest of the codebase needs to be updated to reflect that). And this is also use mostly for tests so you don't really need that :)
I think you forgot to update this comment?
I fixed this to rex/tundra2. This is what I tried to use before https://github.com/realXtend/naali/blob/tundra2/src/Application/DebugStatsModule/TimeProfilerWindow.cpp#L1007 but i didnt want to link to DebugStatsModule just for that function, hence i copied it. I didnt know knet had that, but now I do.
Removes friend requests correctly now, fixed the & issue.
Using form in create_message.html which calls upon this method.  Tested this to make sure it can send a self message and a message between users.
`$world` should be used only in interactive code. Better `morph.world()` or `lively.morphic.World.current()`
Whoa.  Good catch.
Ditto below comment about Q_ASSERT that this is 1
Sorry, I should have added to the README file. This comes from a package, which is available either on Debian as on Ubuntu.

`apt-get install shunit2`
I don't know if it makes much sense to me. Maybe, "Rest implementation of HttpProvider"
Пробел до {
Во входном файле допускаются пустые строки. Они тоже должны сортироваться.
I don't think we need `product_details` at all, do we?
I did int() here so it always rounds it to lower integer. Makes more sense to do that in presentation layer though. So ok for now, but shouldn't forget this. Now it causes trouble because if a project is at 90,6 and needs 100 and it shows up rounded up to  91 and someone donates 9 to complete it then it's at 99,6 and still nog full. So keep in mind while templating!
Can you run this test on your box with like 100 seeds?
Would that be to long for a non-regression test?
This function along with many of the ones below seem internal, I don't see how someone applying an RBM would use them.  Am I missing a possible utility or should they be underscored? Apart from `free_energy` and `pseudo_likelihood` I mean.
If you find it, it should probably be a utility function :)
Yep, that was something I was going to do after this.

On 10/04/2012, at 12:58 PM, Sven Fuchs wrote:

>> require 'webmock/rspec'
>> 
>> require 'travis/listener'
>> -require 'travis/testing/webmock'
>> +require 'support/webmock'
> 
> so, maybe we should move travis/testing to travis/support?
> 
> --- 
> Reply to this email directly or view it on GitHub:
> https://github.com/travis-ci/travis-listener/pull/4/files#r664735
Ah, that was just a GitHub issue - in raw file, the indentation is correct. Probably mix of tabs and spaces.
I agree with Rado on this one. Changing the xml format to include those elements all in one line doesn't look good and infact makes it more difficult to understand, IMO. Why is this being treated different from any other xml like standalone.xml for example?
please, try to not make this dummy changed especially when you lot of real changes... There could be a separate commit that just handles formatting, but having both in one commit is very hard to read and review....
No parentheses
Should this be given the loc passed into the function?
Surely this should still be document and getDocument() in the MongoDB listener and likewise for the other changes to this class?
Rename to correspond to file name.
Parameter probably should be const ref.
A deplacer dans models/DocEtude
it should be outside of client options ( client options are those that are going directly to adapter )
Flag names should use dashes:

mkflag("check-missing-deps") etc.

even though the dest variable naturally uses underscores.
You left this getDebugValue usage in..

You should use getLogs here too.
If you look at the getLogs() impl. you'll notice it gets returns thorlog*
So it covers the functionality you're doing in this loop.
Actually I don't think this code works.  Why are you adding matchLen to cur?  You've just removed matchLen from the buffer.
Which is why `masterTransfer` must be given a name distinguished by the name of the slave node, as you did. That is not true for `localTransfer`, which is what I commented on. I.e.:

    FilePath masterTransfer = masterCache.child("xfer-" + node.getName() + ".hg");
    FilePath localTransfer = localCache.child("xfer.hg"); // this line can be unchanged in diff if you fix indentation
Yes, but ...
We look at the result of the application.
{{ field|field_type }} -> charfield # this realy type field 
{{ field|widget_type }} -> textinput # this really type of widget that need for render

What would you call these filters?
This was actually a bad idea. DEFAULT_ALIGN means we do not know and are to lazy to investigate so we play safe (align 8) and we will want to revisit every DEFAULT_ALIGN sooner or later to replace them with correct figures. The correct figures are the actual alignment requirement of binary_hash() and cmp_*() so I believe 4 and 1 was correct.
What's missing here is a comment that explains the why.  E.g.:

```
# for the Date Range = "Build Date" report, we only want to 
# include versions that had data. 
```
I would just do a single get and iterate over the result, and not generate a new request for each version... I don't think it'll save anything, I guarantee the full set is cached by the time you get here :)
Agreed. :-)
If you want to use the <xi:include> syntax you have to specify the namespace xmlns:zf="http://framework.zend.com/xml/zend-config-xml/1.0/" and  xmlns:xi="http://www.w3.org/2001/XInclude". So we still need the namespace for this specific feature.
The inclusion of these lines break the builder tests and non builder tests as:

* the should dependency results in the wrong should.js library being used (ie. the one in node_modules and not the one in the support directory)
* I think the inclusion of the socket.io-client dependency results in the non builder tests using the wrong verion of the library - we would want it to load the version in lib and not from node-modules - otherwise it does not test your changes
Ah, cool to know. Had to use div.clearfix not br.clearfix, but that works nicely. Instructors layout know works equally well for single-instructor and multi-instructor views.
Why you make this changes in GitExtensions.csproj?
This approach fails is we later want to add new fields to the book representation. It should be done as in `add-author` using assoc.
Legacy left over from when I wrote it as a post module to begin with.
I suggest using ``r, c`` (row-column) instead of ``x, y`` to avoid confusion.
Perhaps a check to ensure the image is an integer subtype?
This is correct! But in the Rails world, we would prefer the shortcut, which in this case does the same thing:

<code>return reading && reading.toread?</code>
Or even
<code>reading && reading.toread?</code>

This is because we are at the end of the method, so it will return (exit) anyway. In ruby, if the returned value of a method is not explicitly specified in a <code>return "bla"</code> statement, the method will return the value of the last evaluated statement, in this case true or false, just as we need.

We could also do
<code>return unless current_user</code>
instead of the if block, and then just get the reading and if it's marked to read.

This is because a simple return will just give nil, which is equivalent to false in logical tests.

So the entire method could be expressed as:

<code>return unless current_user
reading = Reading.find_by_work_id_and_user_id(work.id, current_user.id)
reading && reading.toread?</code>

This tends to be the beloved Rails way of trying to get as many one-liners as possible. *g* You don't _have_ to do it though, the code is otherwise correct.
Can you remove this test?
Did you see this comment:

> It would be better for this to be at file-level scope like getExtentPosition, then it will really be private.
Do you mind changing this to `undefined` as well as for `_positions` above.  This is older code.  Now we allows assign `undefined`.
When will the camera not have a frustum?
I'm pretty sure that making `commandList` a separate argument here is the right move since it's kind of like the return value.  We could also put it in `frameState`, which would simplify the function signature, but right now `frameState` is basically read-only from the perspective of the primitive.  Did you have any other thoughts?
Thanks, fixed.  I plan on doing another round of doc clean-up as soon as @kristiancalhoun doc fixes are in.
Think these two lines could be condensed to:

if attr_platform_name in class_platforms:
While I understand the point of this is to avoid having the line in two places, I think we should avoid hitting the getParentView() call every single time that propertyChange is called.  Please move this inside the if and else if blocks so we only hit it when we need it.
This change is not part of this PR. It is in the PR for 7109, which this PR is dependent on.
I am torn about even mentioning this.  The idea of simple mode is that we control it end of story.  I don't want the developers making any assumptions about the behavior of simple mode beyond what we strictly define in the API docs.
Shouldn't this be 'switch' instead of 'imageview'?
ah, I mean: all the var blocks in DB are sorted whenever it's possible, like:

```javascript
var a, b, c;
```
Sync has moved to a single membase server, but you're right we should do something better here.  I guess we could also re-implement the bucketing algo from libmemcached inside this code, IIRC it's not very complicated.
Is 1 second realistic here? We should ensure that we pass here nearly all the time.

Also, is there any way from the index to see if it is marked for deletion? That way we can verify that the API call went through, even if the index deletion didn't (which to me would be a test pass).
This should be fixed now, I think.
yep, for now we're not sure about having people enter `x^2` terms by hand. That and it was easier to just copy the multiplying_expressions_1 stuff.
</p> at end of line?
I do not believe that it is standard to place a parenthesis around the function being integrated.
I see. But there are several places in druntime in particular where the array copy syntax is used to initialize objects manually like that, and they don't seem to have a problem with that. So what gives?
This is necessary from 2.061.

If a struct has a nested struct member, it must be *directly* initialized in its constructor to avoid leaving undefined state.
If you change `setItem` to a function, the initialization of `_current` field is wrapped into private member function, then compiler could not detect that is correctly initialized while constructing.

To avoid the compiler error check, string mixin is used.
You're right, I somehow always manage to pick the most confusing variable names! I'll use `Command` and `CommandRunner` as you suggested
all of this should come from `application.conf`
All of the methods prefixed with an underscore should be protected, unless you know that they'd be directly called by DB forge and/or DB utility as with the current implementation they won't be accessible from there.
the ``->end()`` call should be at the end of the previous line
I looked in Java, and found this:

    private final Map<String, ActiveToken> activeTokens;

The WrapTokenManager is associated with one instance of a ServiceBusRestProxy; the tokens should be shared across invocations of  the same proxy, but not shared between different proxy instances. Consider two SB proxies, each for a different service. Their tokens should not be shared.
`url` is not needed
Do you have a case where the runner wouldn't be the chef runner? You can remove `run_start` if you want to, it's just extra sugar.
Why writing **exactly** the same method 3 times ? you should keep the code DRY
`<<` же.
No, what should we do to show the optional ones in the usage?
Sure, but `.get(0)` returns the DOMElement, not a jQuery object, and I think you just want that jQuery object, right?
Should combine these into one `margin:` declaration
I don't think you need to wrap `$(this).parents('.contentauthoring_row_handle_container')` in `$()` as it should be returning a jQuery object that you can run `.addClass` on
As discussed in other pull request.
У тебя, похоже, в этом файле форматирование поехало. Проверь. что юзаются табы.
http://docs.jboss.org/process-guide/en/html/logging.html
very true.  OK.  I took a different approach that I'm hoping is better.  I'm changing the flat list of suite names and making them dicts in the same shape as what we have in the top-level list of suites.  that way this function always knows how to process it.
@alexrp : The Tango port for D2 works alongside Phobos *does not mean* the Phobos must exist when Tango is installed.
Make message consistent with what we typically do
```
Assert.notNull(factory, "'factory' must not be null");
```
As a general comment, I think all these conditionals are going to be very confusing.

E.g. if it's a zset and it's a map and the map has a score as the key, and parsePayload is set, do one thing, else ... , else ... , else ... Ugh..

Maybe it would be better to to have a zset adapter, a list adapter etc, with a separate subclass for each. 

Or, at least separate out adapters that store a single value Vs. parse the payload.

I need to take a fresh look in the morning.
Zend FRamework.
Rendy, can you change this to `pageNeedsUpdate`?  It reads a little easier.
I think you can get away with using a plain class here instead of BaseModuleContextSensitiveTest ... it will be a lot faster.  The only time you need that is if you are writing something that will reference the Context.
Can you simply use instanceof?
For some reasons, IIS (the Web server) may deny to serve a request that doesn’t specify the user-agent property in the request header. So, although it’s not really obvious, this can be solved pretty easily by specifying the particular user-agent property. You can set it to anything, it doesn’t matter as long as it exists.
Reason for dead code?
Exciting new features.
I would rather rename variable in `base_urls`.
I think my editor broke the Makefile, but this is the key line.
I see, that is similar behavior with `.prompt()`.
So we'll have choice, that is, it's up to us to merge or not to merge filled options into `program` in a callback.

As with camelCase, or hyphenated-words, I aimed to be in "generous on input, strict on output" way. But if you don't like it, I agree with you.
public methods start with capital letters, should be Purchase
Yes of course - that looks like it got removed by accident - I agree it adds value :)
This field should be read-only? People can't change this to point to something else.
How about the BBM Platform events. However if you would like a different look or a different way to document it we can discuss that as well.
The test should have a defined fail or success criteria. Just running without an exception is not suffiecient.
Self is shorter...it can be minified to 1 character, versus 4 for this :). Also, "lang.hitch(this," is a lot of characters. Lang.hitch also has the nasty habit of not propagating this properly (i.e. if you call a function within the hitched function, you also have to hitch that function). Self is usually more space efficient than lang.hitch
addSystemConceptMap used a different GP (metadatasharing.systemConceptSource) for local mappings which could be set from the module configuration page. See ConfigureController. We will resign from setting that GP in MDS and add a configuration page to the ConceptPubSub module.
I will fix that. Comes from the previous version where my class extended an App which was executed.

-----Original Message-----
From: nermin [mailto:reply@reply.github.com] 
Sent: Freitag, 1. Juni 2012 04:28
To: Gruntz Dominik
Subject: Re: [scalapuzzlers.github.com] Puzzler 011 (#17)

> +    <tr>
> +      <td><strong>Contributed by</strong></td>
> +      <td>Dominik Gruntz</td>
> +    </tr>
> +    <tr>
> +      <td><strong>Source</strong></td>
> +      <td>N/A</td>
> +    </tr>
> +    <tr>
> +      <td><strong>Tested with Scala version</strong></td>
> +      <td>2.9.2</td>
> +    </tr>
> +  </tbody>
> +</table>
> +<div class="code-snippet">
> +<h3>What does the following program print upon execution?</h3>

We typically just ask: "What does the following code print?". Therefore, "upon execution" is a bit unnecessary, in my opinion. I would also change word program into code, for the same reason.

---
Reply to this email directly or view it on GitHub:
https://github.com/scalapuzzlers/scalapuzzlers.github.com/pull/17/files#r912654
I think we should have a test that checks that the actual splashScreen property was set correctly during parsing.
Something like expect(configObj.splashScreen).toEqual("test.JPG")
Why are you updating the framework?
Hmm, we use it for more then testing. This seems like a pointless function. But should probably be removed another time.