labofsahil/github-event-dataset-2012 huggingface dataset:
"... accepts a block that accepts ..." somewhere, an editor has dubbed you :crown: :poop:
The same comment on the ports loop on enumerate_mysql applies here
I know. Read the other pull and you'll see why.
On 17/11/2012 4:12 AM, "sinn3r" <notifications@github.com> wrote:

> In tools/msftidy.rb:
>
> > @@ -25,7 +25,7 @@ def yellow
> >
> >  class Msftidy
> >
> > -	LONG_LINE_LENGTH = 200 # From 100 to 200 which is stupidly long
> > +	LONG_LINE_LENGTH = 100 # From 100 to 200 which is stupidly long
>
> 100 is impossible. Most modules cannot do 100. Give this setting a run
> against all existing modules and you'll see why.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/rapid7/metasploit-framework/pull/1074/files#r2154051>.
>
>
We couldn't find the password field for printers, although it is specified in the XML. That blog seems to confirm they cant be set for printers.
Stack-based buffer overflow in the UltraMJCam ActiveX Control in TRENDnet SecurView.....
If you can write and execute, which seems to be the case for you already because you're writing a PHP file to /enterprise/control/,  then you can probably still take advantage of the PhpEXE mixin.  There is a get_write_exec_payload() function that basically writes a payload to a directory based on your choosing, executes it, and then cleans it up.   You can see the code here:
https://github.com/rapid7/metasploit-framework/blob/master/lib/msf/core/exploit/php_exe.rb

And yes, exploits are still required to pop a shell.  If a shell is not possible, then this module will fall into the "auxiliary" category, where it simply extracts passwords.
Also, I'd change this description to be more descriptive - something like `it "has a failure message that indicates failure with instance methods"` or something.
Please make this one line as well. It's not *that* long.
Well, it's ``E225 missing whitespace around operator``. I can disable it in the checker.

The motivation of doing this is that I would like to add pep8 check into travis-ci; therefore, I fixed all the errors in pep8 checker. as far as I know, openstack strictly follows the pep8 rule. All the commit has to pass the checker of pep8 for openstack.
Trailing whitespaces should be removed
Yep, you're code is way simpler and better. (though I had to throw in an orientation.conjugate().  The only downside is that it will now create three new additional throw-away objects per sensor per update.  I'm not going to worry about that for now because it will be fixed with the other memory pressure stuff I plan on doing sometime soon.
It sounds useful, but I'm not sure that is actually is.  Fabric is a JSON schema like CZML, and the string `agi_defaultImage` is valid JSON, but `Uniforms.defaultImage` is not.  All this helps is our built-in materials, but not others.  Users of materials - as opposed to authors - will pretty much never use `agi_defaultImage`, so I'd back off this until there is a real need.

And, yes, we will rename `agi_` to `czm_` right after we get this into master (no rush).
So passing `undefined` causes this function to have no affect?  Shouldn't we at least default to true or throw on undefined?
Do this once in `_createMeshes` and pass it in.
Aligning with other projects
Missing newline at EOL.
We should include a link to the spec for people who haven't heard of it before.
failed validation on since tag.
It's probably better to look up the settings utility here instead:

1. It leads to strange errors when a browser view can't be initialized (like ``404`` instead of ``500``).
2. The view doesn't really need a state.

In fact, I think ``grid`` shouldn't be a method at all – but a function outside the browser view.
BTW, this was the only use of plexus-utils so I just inlined the method and nuked the dep.
А, там [по апи](https://developer.mozilla.org/en-US/docs/DragDrop/DataTransfer#getData%28%29) пустая строка возвращается. Ну всё равно лучше как выше.
Ты строкой, кажется, промахнулся. Но да, в этом и суть клона — чтобы сделать такой же инпут, но свежий без файла, а с файлом отправить во фрейм.
`$field`, not `$modelField`.
The whole block from 216 to here seems a little tangled, you seem to be abusing a little on comprehension lists at the cost of readability (and repeating code)
`Gets the rank (number of dimensions) of a static array type.`

This is an important distinction from the dimensions *themselves*.
Except that for zero-argument functions with `@property` also allows you to omit parenthesis, which is the principal reason _I_ use it. And since the name `popFront` clearly describes a function, from _my_ viewpoint, it is a clear cut case that it should be `@property`. BTW, technically, properties were intended to provide an upgrade path when a change to a class' private implementation necessitated a change to a public/protect field. So, the use of properties to omit parenthesis or for new classes to emulate variables was never intended. Of course, the original intent of a feature has little to do with its practical use (e.g. C++ templates). 

Getting back to the main point, looking at the implementation of `isBidirectionalRange`:

```D
template isBidirectionalRange(R)
{
    enum bool isBidirectionalRange = isForwardRange!R && is(typeof(
    (inout int _dummy=0)
    {
        R r = void;
        r.popBack();
        auto t = r.back;
        auto w = r.front;
        static assert(is(typeof(t) == typeof(w)));
    }));
}
```

I'm not really sure why `static assert(isBidirectionalRange!(typeof(app[])))` compiles or what may be done to enforce the intended behavior of `isBidirectionalRange`.
"stuffs" is not a noun. It's a verb (as in "she stuffs the turkey"). I think that you meant simply "stuff," as "stuff" is always plural. It's like dust. You can't have dusts. Both dust and stuff can have amounts (e.g. lots of stuff or 5 pounds of dust) but aren't countable (e.g. 7 stuffs or 12 dusts make no sense). There's probably a technical term for what they are, but I can't think of it at the moment. Regardless, you should remove the s.
That's cool. I kept it the same to keep a consistent API, but command certainly makes more sense.
notifyAllConnectorsRegisteredOnSameHostAboutDeregistration
Cool, that works. If a user wants to use their own repos, they can add their fork as a config option in the repos as discussed below, then. That's mainly what I was getting at.
That's because you're passing in the address of the local variables, that drop out of scope.
You need to declare explicit pointers, set the pointers to the addresses of the local variables, then pass the pointers to the block. Everything must have the `__block` specifier.
Then the block will capture the pointers, which will keep the local variables alive.
@stof yup
This block looks similar to the core one. What is the difference ?
Have we tested all these? I am not sure we currently pass XmlSerializer as the dataSerializer.
If you can mix btn-large into the media query for this windows size, that would be ideal.

If not, we should do this on resize as well.
> +# special compiler flags
> +list( APPEND CMAKE_CXX_FLAGS "-std=c++0x ${CMAKE_CXX_FLAGS} -g -ftest-coverage -fprofile-arcs")

 

This is for the use of c++11 to avoid compiler warnings. Copied from TYS.

 

Von: Florian Weißhardt [mailto:notifications@github.com] 
Gesendet: Dienstag, 11. September 2012 12:54
An: ipa320/schunk_modular_robotics
Cc: Fröhlich, Tim
Betreff: Re: [schunk_modular_robotics] Improvments on init and reference checking (#9)

 

In schunk_powercube_chain/CMakeLists.txt:

> @@ -32,6 +32,9 @@ set(LIBRARY_OUTPUT_PATH ${PROJECT_SOURCE_DIR}/ros/lib)
>  # add include search paths
>  INCLUDE_DIRECTORIES(${PROJECT_SOURCE_DIR}/common/include)
>  
> +# special compiler flags
> +list( APPEND CMAKE_CXX_FLAGS "-std=c++0x ${CMAKE_CXX_FLAGS} -g -ftest-coverage -fprofile-arcs")

for what do you need this?

—
Reply to this email directly or view it on GitHub <https://github.com/ipa320/schunk_modular_robotics/pull/9/files#r1575228> . 

 <https://github.com/notifications/beacon/1nuKxw1fnxrP5xgMiyVu8dklA0I5HH0oHRW7P_6IPgtL0_umRqD5tPOXQZBrXYll.gif>
Please make the => line up with the others--makes code much more readable.
Uh "$username" doesn't look right remove the quotes
Getter und Setter verwenden!
$order->setFinalDocument($document)
Can we please have `!` next to the expression that is negated without a space?  It's very strange otherwise.
I think you need an ifdef WIN32 in front of this and I would prefer not to have the whole cblas file in here but just what is needed from shogun.

what worries me again is that you might be able to compile libshogun but you won't be able to link against it because all these cblas_* functions are nowhere implemented?
Yes, that is correct, but we can update the test then. Just use a simple enough example where changes are unlikely to happen.
How about adding `version (D_InlineAsm_X86)` in front of the function?
This gp should have ORUR01 in the name somewhere
Hi,

For the purposes of this template, you will only be receiving one encounter. This happens because we wanted to have multiple PID + PV1 segments per message. 
The ORUR01 template (your parent template) will call your template inside a for loop for encounters, passing in one encounter at a time.
Do you want me to open another JIRA or you already have one?
Seems odd to have a store package that doesn't have all the stores in it; OTOH, it would be inconvenient for users to move the other message store here.

Maybe just remove package ??
Maybe like this:
`logger.error("No MBeans found matching ObjectName pattern(s): " + Arrays.asList(this.objectNames))`
?
Also we should add a note into XSD on 'object-name' attribute description how it can be configured...
Why is there a new Import?
Nice update on the test cases here and below.
Sorry, I was mistaken. Forget that comment. Here comes the full explanation of the problem.

The problem is that the styles set in text.css are overridden by compass/reset. It may seem hard to believe: in CSS the later rule always overrides the former, and as you can see, text.css is @imported after compass/reset.

However, compass/reset is SCSS (or SASS), while text.css is CSS. Therefore compass/reset is compiled right into application.css, but SASS passes the @import "text.css" into application.css, unchanged. In addition, in CSS all @import statements must be in the beginning of the file, before anything else. Therefore the browser ends up reading the content of CSS files first. As a result, the content of **all** CSS files has a very low precedence: SCSS and SASS will **always** override CSS.

The proper fix is to rename text.css into text.css.scss (and adjust the @import line below).
Never heard of such a table ! Where is the code ? :)
I think I mean that you'd have

``
class Player
end

class Dealer < Player
end
```

And the Dealer would override the status method that has "XX" showing

--------------------

As far as which way I'd like you to go: That's the beauty of software development; all ways are valid --- there's no one right way. I think of it more like an english/writing paper. It's interesting to see where you go and what you do: I teach the theory and fundamentals.
So for example here is right side.
NSString *jsString
Can we break this into multiple lines? I prefer a column width of 120 personally.
Private was added to :set_escaped_name and to :set_name methods, now!!!
There's an assumption here that the session class has to be named by adding `MfaSession` to the model name, but this is not documented anywhere.
So you would prefer Fody.*.dll  over  *.Fody.dll ?
if this registry is unused, do we need this method? This has change has many ripple changes.
Do all these functions need to be public?  Or are some public just for testing?  There could be a .NET way to provide better scope, and still test them. CC @kring
Oh yes, I love list comprehensions and generators!  The main reason I did it the other way (although your syntax is much nicer) is that, as I noted in the comments, there's a lot of other stuff in the "Received" header besides the date and time the email was received. I'm going to have to write a little function to extract what information is needed before inserting in the db, but at the time I wasn't sure what of that information (other than the datetime) would be useful to keep.

As for the rest... I will experiment with Flask and see. I'm not sure how Jinja2 templates handle tuples, I think they sort of expect dictionaries...
I dont like that this data object is hardcoded in this fashion. Can we move to something that can be manipulated by the event above the get call?
i think we would end up with reference problems again since form_state is passed by reference. it would be nice to have this section be clearer though, it took me awhile to figure out what was up.
But yes, this is a bit cryptic. It also [gave me](https://github.com/mitar/django-tastypie-mongoengine/pull/1#r659744) some problems.
Apologies.  Should be this:

    self.headers = headers and headers.copy() or {}
Maybe I'm wrong, but this grabs dates for the archive. It doesn't output them; it just grabs them. That is marshalling objects. (Marshalling in the sense of gathering a group, rather than [Marshalling](http://en.wikipedia.org/wiki/Marshalling_(computer_science)).
Good idea, I'll open a bug to change it later.
Also, when returning an error, do ```callback(new Error(message))``` - return the exception as an actual exception message. That way you've got a stack trace.
Thanks @gunnarmorling I have applied these for BVAL-208
This is a bad idea. a file containing a cached json should not be named ``fosJsRouting.json.fr``.
and if you create a bunch of cache files, a subfolder should be used instead of creating many files in the root of the cache dir.
Old compiled code could (maybe?) return zero under some conditions before curRow equals numRows, and that will mean EOF for this function.

I was not sure that could ever happen, but didn't want to break stuff. If you're saying that it will never happen because it was never on the design of the temp tables, than, fair enough, we should remove it and leave only the row check.
just letting you know that the workflow structure has been reorganized in the last couple of days.
We should do a instanceof check here to make sure the property is actually a TiViewProxy
Should not be documented/public, as it is only used internally and intended to be controlled entirely by `Ti.UI.backgroundImage`.
Ork = Orc
The name makes me think this class does something different.  Perhaps HttpQueryStringParameters would be more descriptive.
we have to take this out of the version control. I would keep this info in a separate experiment design file (which are gitignored), and keep only anonymous behavior in the session files
Opened blackberry/BB10-WebWorks-Framework#233 to track this
Woops this should comment should have been removed.