labofsahil/github-event-dataset-2012 huggingface dataset:
Nope :)

Sent from my iPhone

On Dec 20, 2012, at 9:33, rsturgell <notifications@github.com> wrote:

In injector/wtf-injector-chrome/popup.js:

> +document.addEventListener('DOMContentLoaded', function() {
> +  document.querySelector('.buttonToggleInjector').onclick =
> +      toggleInjectorClicked;
> +  document.querySelector('.buttonResetSettings').onclick =
> +      resetSettingsClicked;
> +  document.querySelector('.buttonShowUi').onclick =
> +      showUiClicked;
> +});
> +
> +
> +/**
> + * Updates the popup with the given page information.
> + * @param {!Object} info Page information.
> + */
> +function updateWithInfo(info) {
> +  console.log('info');

did you intend to leave this in?

—
Reply to this email directly or view it on
GitHub<https://github.com/google/tracing-framework/pull/148/files#r2479735>.
This format is new in Graphite 0.9.9, but if you're using an older version you could set older defaults.
Little cleaner, but would start at 0 rather than 1.
Same here. why would the string "123" or the float "123.0" be ignored?
Could you explain why this was needed please?
Yeah, I'm not familiar with this `use_decimal` option. It seems to exist in simplejson but not in json. And simplejson refuses to install on Python 3. So I removed it without understanding the ramifications. I thought you guys could determine if it is still necessary perhaps.
But for the dummystream it is a waste of time to generate extra points (points that overlap). It can take several minutes to generate points for 2 days. So last_timestamp feature is really needed for this kind of metric generation. Another possibility is to embed the generation code in the mongodb backend.

On 03. 10. 12, at 11:26, Mitar <notifications@github.com> wrote:

> In datastream/api.py:
> 
> > @@ -272,6 +317,18 @@ def get_data(self, metric_id, granularity, start, end=None, value_downsamplers=N
> >  
> >          return self.backend.get_data(metric_id, granularity, start, end, value_downsamplers, time_downsamplers)
> >  
> > +    def remove_data(self):
> > +        """
> > +        Removes datastream data from the database.
> > +        """
> > +        self.backend.remove_data()
> > +
> > +    def last_timestamp(self):
> I would create "import" API call which imports datapoints and makes sure there is no overlap with existing datapoints.
> 
> —
> Reply to this email directly or view it on GitHub.
> 
>
Per discussion on b2g-dev, the detection method would be `if (window.MozSmsFilter)` , not `('SmsFilter' in window)`, coz SmsFilter could be exist but `null`.
Done. I did the same for the Comments controller
Commented out lines 86-100, for /strangerock/acid_act

As above, kept this commented out because melty and explained issue in comment
Oh... Thanks... I couldn't understand, where my error :D
Add update_values() calls to filtered and breath, kindly.
Next time I'll remember to check those references, thanks for the info!  On that topic, I see that the relevant lines in the aforementioned util.rb and compatibility.rb are
```ruby
def snow_leopard_64?
  MacOS.prefer_64_bit?
end
```
and
```ruby
def prefer_64_bit?
    Hardware.is_64_bit? and not leopard?
end
```
Since I'm guessing homebrew has no Tiger support (or very few Tiger users), `not leopard? == snow_leopard?` and this makes `snow_leopard_64?` mean `MacOS.prefer_64_bit? and MACOS_VERSION >= 10.6`," correct?
I would suggest you combine these two with the block below that parses the config.  Set it to this if no config or if there is something wrong with that value, something like
```
ActiveResource::Base.logger = Logger.new(logging_defaults_method)
```
and then in that method have something like
```
return STDOUT unless @config[:logging}
@config[:logging][:logfile].include?('\') ? @config[:logging][:logfile] : @config[:logging][:logfile].upcase
```
To be honest I'd rather like to have this with the me interpolation for "normal" fields in sql_for_field. We could even add the `:format => "user"` (or similar) to the normal fields so as not to have a list of fields for the me interpolation but a "proper" tag/key/thing.
Can you wrap text to 120 chars?
В stack уже хранится Character. Чтобы сравнение такое сделать, надо вызывать метод charValue()
Надо использовать мой класс, а не делать copy-paste в свой package.
To be generic and correct, this should be:
```c++
  typedef typename Eigen::Matrix<Scalar,A,B,C,D,E>::Index index_t;
  index_t rows, cols;
```
Can you update?
What's the relation between `\u0005` and `&#5`?
Corrected on 81db25 Commit
I'll give it a try. The radial ones might not be the same, but they at least would be still be symmetric (:
We should <code>Assert.contains</code> here.
There is a bug related to this section: https://bugzilla.mozilla.org/show_bug.cgi?id=776882
Please mark the test with xfail until that bug is resolved:

@pytest.mark.xfail(reason="bug 776882")
Optional: You should be able to create a base class for ProjectMediaPaneView and ProjectMediaButtonView to avoid some duplicate code? What do you think?
PEP 8 or checker tools would tell you to add spaces after these commas. Would you mind doing that?
some comment are now added

    # allocate memory with malloc
    cdef int max_se = srows*scols

    # number of element in each attack border
    cdef int n_se_n, n_se_s, n_se_e, n_se_w

    # the current local histogram distribution
    cdef int* histo = <int*>malloc(256 * sizeof(int))

    # these lists contain the relative pixel row and column for each of the 4 attack borders
    # east, west, north and south
    # e.g. se_e_r lists the rows of the east structuring element border

    cdef int* se_e_r = <int*>malloc(max_se * sizeof(int))
    cdef int* se_e_c = <int*>malloc(max_se * sizeof(int))
    ...
No, it's ok. When I commit they should fold away.
Yes, `clone` clones the parameters of the Estimator object. Tree results from the fit of a DecisionTree -- it is not copied. Also DecisionTree has a Tree and is an Estimator, but a Tree is not an estimator (it inherits directly from object).

If someone knows a copying function, I will gladly use it.
Left over artefact of development.
I think that you should use `Type::resolve` to detect whether `targ` actually specifies a symbol or not.
Otherwise, we cannot support some complex cases, e.g. `is(Temp!int == template)`, `is(Overloads[n] == template)`, and so on.
Some BB specific like orientation for example.
No, I suspect the reasoning was to avoid cascading sequence of errors when dali is shutting down, but not convinced shouldn't just throw and leave it up to the handler(s)
Why did you remove this?

Looks like it was intended to run the jhtree unit tests from this framework too. I don't recall why it was loaded dynamically rather than linked though... Probably because the linker is liable to optimize it away otherwise.
silly doubly semi-colon, not worthy an update, I think.
Not gone, but using the retry mechanism from transaction (essentially the same thing).
Yes, it could be a counter, I'm guessing it's like this because intention was to make it parallel..
(Again, just a ignorable nit more-of-a-tip)

Since it's "bad form" for purists to reuse the same variable name for a different purpose, it might have been more appropriate to use the variable `date_attributes` if you'd change that you'd have to change the indentation for all the entries in the list. 

A possible improvement would be:
```python
date_attributes = [
    'date_created',
    'date_recently_completed',
    'date_oldest_job_queued',
]
other_attributes = [
    'avg_process_sec',
    'avg_wait_sec',
    'waiting_job_count',
    'processors_count',
]

for attribute in date_attributes + other_attributes:
    plucked = ...
...
for stat in stats:
    for attribute in date_attributes:
        stat[attribute] = parse(stat[attribute])
```
Can you write them like this instead:

```python
parameters = [
    'terms', 
    'products', 
    'versions',
    ...
```

That way it's easier to read and easier to comment things out. 
Also, diffs on future patches will be easier to read.
What if transportPort() is called before transportHost()? Is there a compelling reason to expose these properties on JettyHttpServerTransport? They are not really JettyHttpServerTransport's properties after all.
This would be better to add `__DIR__` as second argument to the Process so it runs that in the composer dir at least. Then the error message can say `or you must ensure you run compile from a composer clone`?
I simplified the isset check, but kept the rest as it is, because my change was only meant to be a bugfix to avoid the notices, I didn't want to introduce potential problems by doing a concrete refactoring - in my opinion, this should be done in a separate process.
Ok you can discard my previous comment as I don't think there is a way to break in forms listed above.
Ohhh good catch, I completly missed that big bug!
We agreed on the fact that using .apply instead of .call should be configurable
Missing empty line after the header.
It would be good to have test coverage of this method -- either in its own test or in the generate() test of EnrollmentCSVGeneratorTest. Not a blocker for merge though.
This should be the only line in the `try` block.
Doing this give me access to the instance within the context (see example below).
indent seems a bit funky on these
Great idea. I knew this was bad, but was debating on the right way to do it.
Would you mind adding a comment about what levels is in a practical sense? I don't know anything about this: does it have something to do with the wavelength of features?
This example is on the right track, but I think we need something more complex to show that the algorithm is adaptive.  Perhaps the hand data that I used at EuroSciPy would suffice? (It's in intro_notes.tar.gz. here: http://mentat.za.net/euroscipy2011/)
That doesn't matter.  Estimating a similarity, affine transformation, homography... those all follow the same procedure (or should).  The only difference is where the coefficients are that you allow to vary.
This method, as well as the one in `OnlyIntegerMatcher` , can probably be private (unless it makes the tests horrendously harder to write).
Short descriptions are in the apps management portal, not the app package.
Fixed.  

Also, I just realized I had `cs'<q` instead of `cs"<q`, also fixed.
Presumably you can delete this
This function doesn't throw this exception any more.
When replacing `DOC_TBA`, please fully replace them.  This particular doc should also include a '@returns` tag including the datatype.  Try not to be redundant in the doc.

All non-trivial functions should include an `@example`.  This function is, of course, trivial.
Fabric is externally scriptable.  We guarantee the default texture and cube map.  If we allowed it to change, third-party Fabric authors could not rely on it.  I wouldn't add this functionality until we need it.
I'm pretty sure we do one variable per `var` to make the Eclipse formatter happy.
As simple as this class is, it should still have a `Spec` file with tests.
We probably want to refer to this as 'android bug 2373' to make it clear
We are adding support for a new key here, "notes:" Please use it to refer to the alternative API.

```
deprecated: 
    since: "2.2.0"
    notes: Use the [applyProperties](Titanium.Proxy.applyProperties) method to batch-update layout properties.
```
No, you are missing the root cause.  The TabGroup is only exiting because a check to activity.isTaskRoot() is returning true (meaning the parent of the tab group is root).  Our task root is ALWAYS our root activity but what this behavior indicates is that this is the root activity from the users perspective (they dont know about our root activity).  The tab group is seen as being a parent of the root activity versus the window because when the proxy is create, it has a reference to the activity that the proxy belongs to.  The proxy in this case is a child of the root activity (the window is basically a parallel operation in terms of what the parent child relationship is).

If an activity is the task root from a user perspective (which would be a normal dashboard activity) then it should exit the application on close as default (normal use case).  The flow you describe is not how it appears to be working (tab group layer over the window) as isTaskRoot() would not return true.

This change would break any app that:
- uses a tab group as the root of the application
- assumes that exiting that root tab group will exit the app (how it works now)

In a valid test case, the tab group check you are removing will only pass the isTaskRoot() if the tab group is root from the users perspective (in which the app should close).  If the Tab Group is supposed to open over the window and be treated as such then it should be created and opened after the window is opened (via event listener).

Before merge, please update the YML to add the exitOnClose property on the TabGroup along with the default behavior.
It's already marked as iphone, ipad only--I didn't change that, so it's not highlighted.
Using a class here seems like overkill, but I'm OK keeping it.
do you have ticket numbers associated with these issues?
Any reason why we can't run this in the browser?
This is needed because the struct is meant to be a bidirectional range, and bidirectional ranges need save. Previously, with just input range "needed", this was never checked.
But that one line will end up in every single range which needs to have `opDollar` return something other than `size_t`. Sure, that code duplication isn't long or complicated, but it adds up. I don't see why it's a problem to simply declare one that everyone can use if they want to and avoid all such ranges having to declare their own. It also helps make it more immediately obvious what's going on with `opSlice` when it's using a familiar type rather than one that was created for that specific range type with whatever name the creator of that range happened to pick.
I've already added support for enum.

Just need to clean up code and apply @jmdavis suggestions and gonna update pull.

Thanks for feedback! :)
Changed in all of the graphs in this lab and the Rieman Sphere lab.
also - please add a simple unittest in test/emitter_test.dart (e.g. basically a new test just like the one named "inserted for attribute")
typoでした。修正いたします。
I did add it as I thought it would be helpful and can be somewhat useful when trying to debug (if needed). However if you guys want it removed then it doesn't bother me.
maybe all those comments would be better readable if you use some kind of DSL here (builder pattern). Like 

theOperation(operationName).does("is used to support other fields types than)
.ct("only string....")
.ct("for the construction.").toString();

Something like that would make the comments definitely more readable
once you stop learning you're growing old :-)
I think we've somewhere to state that any id need to contain a overwritten toString method.
Please put spaces around the `!` symbols, and continue that if statement, beginning with `OR`, on a new line, per the styleguide.

Personally, I would also never use single-line if statements like that, but always use braces.
without params, just for dev by default
I was wondering. We can remove that since its getting deployed to sonatype.
No need for this definition. Why not make it more general with a regex? If we followed this style, we'd have one step definition for every possible button
translates ????
Although the addEventListener method is supported by Internet Explorer from version 9, but it does not work for the propertychange event. If we want to register a listener for the onpropertychange event, use the attachEvent method instead.
When would this be a function?
So, it seems that calling .click() manually from jQuery doesn't follow the link, which is the problem.
if i am not totally wrong, there can be arbitrary defaults for a route. we would need a way to add named fields in the frontend or at least in the configuration
reperition with prev sentence here, I haven't noticed that before
After taking a brief glance they should run fine on the server. All that would need to change is removing Console.Write.
The validator should still be assigned, right? It is needed for serverside validation.
I guess you're removing this because we can't evaluate the expression yet, but that means we're losing this check and the WARN log message (which was added at one point as an issue itself addressing the fact that there was no such warning).
Additional test-case:
`GatewayWithPayloadExpressionTests$GatewayWithMapThatIsNotHeaders` method
````xml
<int:method name="sendMapMapWithMapPayloadExpression"
			payload-expression="#args[0]">
	    </int:method>
````
````java
public void sendMapMapWithMapPayloadExpression(Map<Integer, Object> map1, Map<Integer, Object> map2);
````
There are first Map is payload from 'payload-expression' 
And that's all: everything else will be ignored.
So, remove `&& this.payloadExpression == null` or add some additional `else` should remedy the situation: throws some other Exception.
WDYT?
this file is not necessary.
ちょっと考える。
I'm not quite understanding this bit of code. Can you tell me the reasoning behind firing a reference event for each child property?
align => characters
These I would put under a "Search" section.
Ah, okay ... you should probably add a service method like MohCoreService.hasLocationPermission(sysUser, userLoc)
I have found bug here. We should not pass ignore value via params because it's cached. UniqueEntity isn't considered to be work till i fix it.
+1

Do we have these rules for HV as well? I think at least {@code} vs. \<code\> is not handled consistently. If you don't have objections I'll add this to the [wiki](https://community.jboss.org/wiki/ContributingToHibernateValidator) and create a Jira issue to clean this up one day.
Do we need two of those... it's one auth url... we use the same auth service
Sorry that the formatting got a bit screwed up in MojamComponent...
can you add an sdk convenience option for max miles?
This doesn't "marshal objects" and it does manipulate the view and it does encapsulate conditional display logic.

No piece of code outside of this helper has to know this class exists. Moving it to lib would only make sense if it were going to be used elsewhere. As it is now it is just a private child class of PostsHelper.
Excellent! Peut être dire un mot rapide sur le fait que le site de NinjaSquad et ce blog sont complétement responsives ? (La navbar bootstrap est aussi vachement bien).
a little brain dump:

* I am wondering whether the Path object does not get too heavy weight in this case? We are adding a lot of information with all these descriptors on each node
* Especially we make the standard bean validation more heavy weight where this type of meta information is not needed (and in the end bean validation is still the main concern of BV). Maybe a differentiated MethodConstraintViolation (as we have now) is in this case better?
* What about the string representation? Do we have a string representation for these paths? Is it even possible to have a non ambiguous one? From my experience from the forum it seems that most people work with the string form of the path which is not even specified. I hardly had a case dealing with the API. Given that there is such an assumption on the string representation shouldn't we specify it?
yani dar in had mikhan ba joziat cide ha ro check konid???? :scream:
zaim should answer this .
Snafu :p

Basing our naming on DOM4 sounds like a good idea.
Also we need more red in that method name.
As I mentioned, this should not be required. Please check out notification builder's methods for something that clears the notification automatically as soon as it is clicked. ( As a general rule, anything that is regular behaviour will most probably be present in the api, and should be usable without much hassle, please look for such methods always before implementing something custom)
99% sure template is proprietary as well.
It's interesting that we're choosing to rename some of these parameters.  Should we also rename things like Max -> Maximum or add Duration to the end of all our TimeSpan names for consistency?
these child files have the kind of anonymous data i would expect in a participant..
I would leave it *xqDataSource*. I know that PMD complains that names are too long sometimes...
unnecessary comment :), I think the code is standard to read, no comment necessary for this line.
Do we need to open an issue for this?
Ok, I'll try, but I can't test it
what about the integer type ?