labofsahil/github-event-dataset-2012 huggingface dataset:
It is NOT product that you are iterating on.

for asset in self.browse(ids):
    res[asset.id] = asset.product.code
Это тоже проблема прототипа. Мне нужны дополнительные данные о том как лучше делать.
Yes you are right. That would be cleaner.

Another option would be add `sample_weight` to the interface of `Classifier/RegressorMixin`.

I don't have any strong opinion regarding what's best though.
Do you mean current or cursor? Be less terse, please :)
I think you should rename here, too, to be consistent.
where does this admin class come from? i think we already had an admin for static content somewhere...
Small coding standard issue: all comments start with a capital letter, so the comment above should be:
```php
 // Trigger pre-"setBody" behaviour
```
a database call per shared_form seems unnecessary, should be doable with a single database call
This call means that if no `rewrite_module` is defined in `Options`, then `rewrite_module` app env var is defined as `undefined`.  This is a problem for the case statement at the top of `webmachine:new_request`, as `application:get_env(webmachine, rewrite_module)` returns `{ok, undefined}`, not just `undefined`.
How about making the output string the return value of execute instead of having two functions.
I'll be happy to do so, I didn't know the policy on removing commented out code.
On Sun, Mar 18, 2012 at 08:01:23PM -0700, Walter Bright wrote:
> I have no idea what this comment means.

I think I was talking to myself...

The idea is to do the special character encoding right
before macro expansion.

This way, everything the user typed in their doc comment
gets encoded properly*, but the macros can still be used
to output raw HTML.

* if you type

/// A < B

The proper output for html is

A &lt; B


So the user sees in their browser the same text you typed here.
As discussed, this is added in a later patch.
Done, based on state
May want to check for `setProgress:withRequest:` before `setProgress:` so that in the case of the target having a property named `progress` and it will have the expected behavior of having `setProgress:withRequest:` called.
There is no additional security benefits of using string concatination to sprintf.  If anything, it's the opposite, since you can preserve the variable type with sprintf
I think of using `to_python` as a way to cast to a python type.  Here is some irregular processing ocurring before the `super()` call which will pass in the "ready to be cast" stripped comma value.  If there was something like a `prep_input` method that occurs in clean and before `to_python`, I would say it would go there.  But there isn't, so I feel like this is fine.  It all depends on if you consider the comma stripping to be part of the type casting / coercion
I don't see any require for this file, how does this work ?
Ok, finally I understand the braces direction was no mistake. But .. 
1) why is one dimension normalized to 90 and the other to 180 ?
2) why don't we just use radiants?
3) why is the second dimension - using 180 - excluding the -180 from the range, but the dimension using the 90s not excluding the first range?
should be in cpp ?
>>
 don't have to rename it... tbh, I couldn't come up with a better name.

I'm open to suggestions...
<<
Well it isn't analysing, so it should be renamed.
It is outputting an expression along with its dependencies.  So something to suggest that.  analyse suggests it is looking at the expression, but not actually doing anything.
Is this related to HPCC-3154?
If the auperfile != NULL, but, numtoadd > 0, the 'if' statement returns true.
The reason is that contains() is O(num-fields) and this will be called O(num-field) times.  I don't want to add an O(fields^2) term.
What effect does removing the cluster name from the tab order have on the screen readers experience? What does the screen reader say when it gets to the 'learn more' link? If it's just "learn more", we should see if adding a title would override that. If not, maybe keep the cluster name and remove "learn more" ?
It recurses to handle this rather than keeping an ordered stack of filedata.  This keeps the code clean, but at the expense of wasting time scanning the directory and stating all the files.  It would be better to stat the file we're unlinking and to only recurse if we're still over logfile_max_*.

I'll add that as the normal case where there's only one file to remove will result in stating everything once (plus an extra stat at the end) rather than stating everything twice.
...and change this to:

```python
for version in current_versions:
```

This gets rid of the interdependency on the models in the forms.
whoops. added a commit
Nope, parenthesis in JavaScript is only used for precedence and control statements. Try it yourself in the console.
Added this example.
I am out of the office until 20/08/2012.

I'm off on holidays for 2 weeks.
For UI questions regarding the AirportIT SEPL application, please contact
Nicolas Abric.


Note: This is an automated response to your message  "Re: [ariatemplates]
Set the default sorting as Descending (#116)" sent on 16/08/2012 15:45:55.

This is the only notification you will receive while this person is away.
Right now we don't need to expose this but we might do this later.
This function also helps us to avoid duplication.
Wowww cool.
This would be a lot less painful with destructuring and `contains-point?`:

~~~clojure
(defn contains-rectangle? [outer [bottom-left top-right]]
  (and (contains-point? outer bottom-left)
       (contains-point? outer top-right)))
~~~
Yes I would much rather we be writing integration tests rather then functional tests and try to be as consistent as possible with our testing strategies.
oh, I have fix this...
No worries, I can remove that ;-).
Are you sure that 2008 will not work? 2008 and Windows 7 share the same kernel. The Windows 8 like Server product would be Server 2012
I don't think it is a good idea to make kwarg_name optional, because this breaks the function if the user does `func(image=arr)`.
@stefanv fixed in subsequent commit.
> Should the user be required to create a Transformation object and then call warp? Maybe there should just be functions that
> warp images, e.g. similarity(image, src, dst), similar to swirl and homography.

We could add a `warp` method to the `Transformation` class which wraps the normal `wrap` function?

>maybe make_tform -> estimate_transform.
>could make_tform be incorporated into the __init__ method of Transformation?

Either of these sound good. I'd prefer to incorporate the `__init__` method.
I don't think so. At least the security is not necessary.
Nice job on the enablement - so it will only enable when they have selected a layer!
"Less is more" -- @pjcozzi
is the c:\ normal ?
Same re "Type"
Seems we don't need import Log here.
Should be Titanium.UI.ActivityIndicatorStyle.*
Are you certain that the term, "page", sounds correct? Web pages come to mind, when I think of a page. I am happy to change it but to me it sounds quite out of place, and does not seem relevant to mobile apps. 
 
As it stands, all the references to "page" have been replaced with "child view", except for argument names.
That's interesting, because it should *not* work on iOS based on the source; means there might be something wrong with how our function routing tables work, which is dangerous.

Closing the results when the database is closed is in fact the intended behavior for iOS, although that might be considered a bug. The source is unclear if this is required because the database resources are no longer available, but that is likely the reason why.
Apparently not, though it used to work in my testing, and now doesn't, and I am not quite clear why. :(

Still, I checked, and the Ruby code is definitely not doing that, so maybe some strangeness in my build testing process made it look like this was working when it really wasn't.
Missing a space before `found`
я не знаю js, как надо?
This should be in the header region
I'd say that it's a bit much to deprecate `xformat` and `xsformat` at the same time. There are bound to be folks using `xformat` and `xsformat` because of the problems with the current `format`. Deprecating them now will break their code with no warning. Scheduling them for deprecation is good, but I don't think that they should be deprecated yet, not as long as deprecation results in an error by default rather than a warning.
This is a problem. You see, getTestCass actually tries to _resolve_ the class using Class.forName and in the presence of multiple class loaders it may resolve to a different class than the original. Not likely scenario, but possible. This is also the reason I liked the previous design better because it was giving you an explicit target object.

I'll think about it a bit.
it's because it's looping over directories. i moved it out of the loop.
`debug`.
is provided really required (all deps)
Getting services for `FactoryInterface` & `EventDispatcherInterface` IMO should be after `if` that user exists.
have a look at the old MediaMenuAdaptor, there we make the show and edit are breadcrumb items so you can use the breadcrumb to go back
I was thinking about this one and IMHO not.

Because the method is called only when a field annotated with {{@Page}} is of generic type. Therefore, somewhere in the hierarchy has to be the parametrized type before the recursion goes to the {{Object}} class.

Am I right ?

However, I do feel that this is probably not good programming practice to rely on that, therefore I am going to rework it. Thanks.
Typen-Sicher machen
public function getOffers(Document $document){
...
}
Can we implement the CSS Guidelines here?
Do we need to return false here, or do you always just want to `preventDefault`?
Ahh, got it. No need to make that change now -- could you create a JIRA for 1.3 to clean that up?
On Sep 13, 2012, at 12:43 PM, Iain Buclaw <notifications@github.com> wrote:
> 
> @alexrp - from a quick scan, first thing that pops out is core/thread.d: import core.sys.posix.sys.mman; // munmap
> 
> That publicly imports posix.sys.types. :-)

Nearly every posix header imports posix.sys.types.  That one's pretty much unavoidable.
MINOR: Personal preference - the use of { } brackets, even for single line statements.
Why remove the order? Although it doesn't have much meaning on startup, they might want to control the shutdown order.
That commit is not on the branch; do you mean https://github.com/ghillert/spring-integration/commit/5794c228e409ae6f9e73d8ae1db52504b1d709a9  ??
Then an equivalent runtime check needs to be added. That behavior was here due to an issue. Simply deleting it creates a regression.
That's my fault - there is an (admittedly) small chance that destroy() will crash if a new thread happens to send a message at the same time destroy() is called. Even if not possible, we figured the churn is low.
I see what you mean; you probably need to reject my other PR, adding the view-expression to the inbound endpoint because that, too, was based on the existing code in that class.
Missed in the initial version, but we need to have emphasis around the attribute names and for the Optional in the end
Huh? It's not moot at all. I don't get your argument - all you added was assertions that the group ID doesn't contain the prefixes and the second is useless because it would NEVER contain MESSAGE_KEY_PREFIX.

The 

     assertEquals(3, counter);

was always there (see line 280/285 below) - master __does__ return 3 groups, but they are empty.
Oh, Perl::Tidy went over this apparently, sorry ;)
hmm maybe it just an deadcode. will recheck
Please use escapeshellarg() here instead of adding quotes by hand in the string below.
It was in e5ad44c6b81c675f216dc11109fd36b5fe8485ae I think. Moving along! =)
This line should still be a key/value pair to ensure that when merged, it doesn't get removed.
그렇사옵니다... ㅎㅎ 심심하시면 한번 테스트도 해보세요 ㅋㅋㅋㅋㅋ 재밌네요. 산낚지 닉도 바꾸고... 헛소리도 하게하고 ㅋㅋ
add a blank line here for readability ... CTRL-ALT-F should fix it for you.
Almost certainly won't work under Mono.  Maybe we don't care?
click "view full changes" to see this entire text file and all discussions on it.
isnt this more `white_box` than `reddwarf_can_have_volume `?
i think we should add a todo there as well as open a ticket to look at the concurrency issues, but merge this PR.
Because of these lines in the spec_helper:

```ruby
 # Requires supporting files with custom matchers and macros, etc,
  # in ./support/ and its subdirectories including factories.
  ([Rails.root.to_s] | ::Refinery::Plugins.registered.pathnames).map{|p|
    Dir[File.join(p, 'spec', 'support', '**', '*.rb').to_s]
  }.flatten.sort.each do |support_file|
    require support_file
  end
```
the factories.rb file will be loaded again (Refinery::Testing loads it first). Previously the Refinery::Testing didn't find the factories.rb file since the path was wrang and hence didn't load it, only the spec_helper did.

But maybe there is a better solution used in some other engine?
`span10` plutôt, non? La colonne "content" d'un post est sur 10 colonnes, le layout général gardant 1 colonnes à gauche et une à droite pour des espacements. J'sais pas s'il est visuellement plus joli d'aligner le bloc de commentaires sur la largeur du texte ou sur toute la largeur du contenu blanc.

C'est aussi un peu bizarre d'enchainer deux colonnes de 8 sur une largeur de 10.
Peut-être vaudrait-il mieux un truc genre :
```html
<div class="row">
  <div class="span10">
    <div class="pagination">
      ...
    </div>
    <hr/>
  </div>
</div>
<div class="row">
  <div class="span10">
    {% include JB/comments %}
  </div>
</div>
```
Mais bon, ça marche très bien comme ça, la seconde colonne ne tenant pas en largeur s'affiche à la ligne.
I think we omitted the import statements from most listings (only some exceptions).
This and the next example flow over in pdf
inja az span estefade kardi bara opacity
chera az khode opacity estefade nakardi?
This will allow to run test without installing vendors, of course now all tests will be skipped but maybe someday there will be such tests.
Or that's not worth it and I should remove the code above?
custom exception removed
Yes, I have a test for that: https://github.com/RiotGames/knife_cookbook_dependencies/pull/42/files#L51L-1
I believe we traditionally would document this as Object[] and not Array<Object>
Indeed, shame it's broken though :)
Hmmm, I _think_ we might have to add something to the TranslatorServiceFactory to do his cleanly.
Actually that won't quite work...should be like this.

this._xhr.setRequestHeader("UserAgent", this.userAgent || Ti.userAgent);
this._xhr.withCredentials = (!!this.withCredentials).toString();
You want to increase the version number for this. It's a significant (but good) change.
I agree. That's something I didn't think about. I've been poking around the `pg_locks` table trying to see if there was a clever way we could include both the locked object's id and the user's id, but unfortunately that doesn't seem to be an option :disappointed: 

The big appeal for using Postgres's locks was that they automatically got cleaned up once a session disconnected. If we need to create another record to store the user's information, then you are correct this is defeating the purpose. 

Just a small note: Your current implementation doesn't take into account which table the lock should be placed on. Right now it is just locking a record with the same id as the lock row. That works because we are only using advisory locks within the context of the lock table, but to do this the "right" way you'd want to pass in the `Owner#id` and owner's table oid like so:

```SQL
SELECT pg_advisory_lock('#{owner.class.table_name}'::regclass::oid::integer, #{owner.id});
```
Actually, the AS7 formatter has been even more broadly adopted now.

https://github.com/jboss/ide-config

Although the choice for a common formatting appears on the surface like the type of arbitrary rule we hate :), the thinking here is that it makes it a lot easier for contributors (both new and old) to avoid getting tripped up over a formatting glitch. If we can make contributing more pleasant, I'm all for it.
Some "." missing round here.
var uid = $sn.getAttr($text, 'uid');
This code is for creating an argument if none were passed in. As arguments is an almost array, but not quite an array, I couldn't do arguments.push(options). Line 199 was taken from this article on JavaScript and arguments: http://javascriptweblog.wordpress.com/2011/01/18/javascripts-arguments-object-and-beyond/.

If only options were passed to Backbone.View instead of arguments, the code would be cleaner, but it doesn't look like that was possible with Backbone.View.
> ajaxGetPosts(null, brd, Posts[0].Num, null, doPostformChanges);

Та функция должна быть с агрументом (возвращается ошибка, если есть), иначе компилятор жалуется.
Why the round trip via the SPI file ? as appose to a simple all(TransactionEnabler.class).then(Collection<TransactionEnabler>) ?
is the folder key always going to exist? it's risky to use map like this unless you are 100% sure, it creates a new element if it doesn't exist
I normally add `msg="sanity check"` added to this style of test so it's abundantly obvious that they're just a precondition test.
去掉這行