labofsahil/github-event-dataset-2012 huggingface dataset:
I think we're talking at cross-purposes, I have no problem with returning HTML Form representations as part of larger representations from Spring MVC RESTful web services.

What I don't understand is:

a) What how exactly the FormBuilderAspect works (i.e. your intention) from your code and because of your lack of unit tests.

b) Why this is a Aspect instead of something like a ViewResolver, built with the ContentNegotiatingViewResolver.

c) That supporting HTML as a representation format like JSON or XML isn't a much larger piece of work and is out-of-scope for this pull request. For example, if we support HTML for Forms we should also support it for Link and Resource instances and any object returned from a Controller as a @RequestBody as well.

Lastly, I think we should get rid of the LinkTemplate object and have a separate, Form object instead to represent URIs that have request parameters.

I hope that makes things clearer.
this locator should be in a @FindBy at the top of the page.
create a data provider for the times and locations so that it tests all of them.
@raydavis  Hrmm, instead of checking for a null here, is it possible to wrap the original selected field from the database with an nvl?
Yes, this was enclosing code that breaks runtime in mono.
It should be randomized
This should be handled higher up in the code to ensure these domains are never passed in this way. You can easily account for that elsewhere.
What happens if I am not using readline?
I assume so too, because I haven't found a reference implementation of this method.
I'm sorry, I still don't understand.  Are you talking about the downscale factor?
It just looks like an exception in development but in production it will display 404.
I know this is from the original patch, but can you add (the usual) newlines between all the ``if`` blocks to make it match the rest of Tastypie's style please?
$fieldIdx => $fieldId ?
version**n**
@mrmattf Ideas?
I already fixed this yesterday with 2c59852 which is also posted above.
I passed over this too quickly and thought this behavior was applied for all types.  I see what you mean.  That said, this brings up the question of why only support this type of lazy unloading for String types only.  I know the academic answer of Strings being objects thus allowing null but from a API standpoint I think we should have some consistency here.  

IE:  allow setting null for all types to remove them or disable the behavior solely for String type.  Can you check with iOS and MW to see what parity behavior is in this regard?  This change may be beyond the scope of this PR but it's worth at least looking into and possibly addressing while this PR is open.
As stated before, windows or any other non OSX support is outside the scope of this PR.  Changes made to support windows will be decided upon once I perform testing on the window environment and look at the various obstacles that need to be addressed (not just pathing).  

Our internal that takes place during development is not to the level that I personally will consider a project left dead for several months production grade (it might be but I have seen nothing to indicate that).  It may be but I will have to evaluate it first in the scope of this specific project.

Aside from all of this, the hub runs in a hosted linux environment.  I don't intent to push a change in that regard and based on my discussions with IT, neither do they.  If I choose to use wrench.js for the driver, it is possible I would use the same on the hub for consistency but at the very least, there is zero time pressure or pending need to worry about it now.
We may want to call requestLayout() when setting the shadow layer as well.
Just had a thought... can we change this to be like the following for good measure?

    "ti-instrumentation": function(g) {
        return ${has_instrumentation | jsQuoteEscapeFilter} && g.instrumentation;
    }
It will if things are set up correctly, but more checks for safety are
probably a good idea here.
move the i declaration to the list of vars above. Also, use i++ not i += 1
Perhaps a name like onComplete would be more descriptive than callback
http://code.google.com/p/dart/issues/detail?id=5502
Furthermore, this is only for list fields, so this method should be updated to say so, and probably be named better.
it's been a while since i wrote this, but i remember i hit some problems with piping to tar.
Right, my bad, I should break.
yes seems insignificant
Are you talking about any of the changes below?

(a)
```diff
@@ -288,20 +287,20 @@
 		$( "#dialog" ).dialog({
 			autoOpen: false,
 			width: 600,
-			buttons: {
+			buttons: [{
 				"Ok": function() {
 					$( this ).dialog( "close" );
 				},
 				"Cancel": function() {
 					$( this ).dialog( "close" );
 				}
-			}
+			}]
 		});
```

(b)
```diff
@@ -288,20 +287,21 @@
 		$( "#dialog" ).dialog({
 			autoOpen: false,
 			width: 600,
-			buttons: {
+			buttons: [{
 				"Ok": function() {
 					$( this ).dialog( "close" );
 				},
+			},{
 				"Cancel": function() {
 					$( this ).dialog( "close" );
 				}
-			}
+			}]
```

(c) None of the above?
session[:current_filter] =  params[:filter] ||  session[:current_filter]
???? http://cl.ly/image/2b0r1h0e3339
this will be checked in the future pull requests, after a region for the sort_by is created.(which is mostly done, and is waiting for this pull to get merged)
I'd put your vars at the top
I already implemented these, so you're duplicating a functions.
What is this cheeze stuff?
No. Delegate type qualifier cannot test directly. You should extract function type from it, then test `const`.

```d
void main() {
  alias void delegate() const DG;
  alias const(void delegate() const) CDG;
  static assert(!is( DG == const));
  static assert( is(CDG == const));

  static if (is(DG F == delegate))  // extract function type from DG
  {
    // F is a "const function type"
    pragma(msg, F);  // const void()
    static assert(is(F == const));  // pass
  }
}
```
assert should suffice here
In a previous comment here: https://github.com/mozilla-services/android-sync/commit/db2de0f8434be941663bbf5857bfbe7467200499#src/main/java/org/mozilla/gecko/sync/stage/SyncClientsEngineStage.java-P41

You say API 1.1 expects the header to be in seconds. I'm confused, what changed here?
This can share implementation with the other `post` version.
Ah, ok. Then maybe there should be a comment in the file that the ".txt" 
was only added because of the itest structure? I think that there are 
users which orientate on the integration test for their implementations 
and they may be wondering why their own files are not recognized

Am 2012-10-23 08:39, schrieb Christoph Gritschenberger:
>> @@ -20,8 +20,8 @@
>>   
> I did not want the BundleTracker to pick up the .transformation-file in the pax-exam-probe
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/openengsb/openengsb-framework/pull/786/files#r1912701
>
I still think that ProjectChoice component should be an own component. Don't you like the idea?
could you format the ofVideoPlayer entries like the other class entries with multiple items ? e.g. [here](https://github.com/obviousjim/openFrameworks/blob/e135cd729e7e43f816904a3a5e371b41b3e0d14a/changes.txt#L205)
Method declaration parameters, uncheck align when multiline
Are you sure you want to use GWT.log, it leaks memory
Nit: I'd think this date would match the original release date. I'm good with the rest
this is LoggingEvent responsibilities - it is base log class in log4javascript - it has multiple benifits, we can use it as a better base for subsiquent jlog relieses
* day にcomponents.dayを代入しているため、当日の日付しか入りません。indexPathのrowをうまく利用して、すべての日を表示させてみましょう。
DB Felder immer privat machen!! 
Eine anforderung von Doctrine... 
(haben wir auch schon diskutiert... solltest das Vergessen haben, einfach fragen...)
не. Это без меня.
Пересиль.
`QString ()`!
Can you pull this theme out of this pull request?
This is part of https://jira.sakaiproject.org/browse/SAKIII-5058 that should be reviewed separately.
The line length is 129!
However, an arbitrary increase in the poll time is still fragile; better to have an 'alreadyFailed' flag in the Service and don't add the retry (as well as increasing the poll timer, perhaps).
in should be named as inputStream
Having trouble understanding this block...what is the significance of property values starting with digits? Also, what's the purpose of the Map.Entry instances?
blind rescues like this aren't super awesome.

Do you have specific exceptions in mind, if so, catching those only will reduce likeliness of bugs later.
Why should this module care about making this attribute accessible?  Shouldn't that be the responsibility of the app to do?
When you add the field in the initializer you shouldn't need to map it here as well.
The form must be serialized before it is disabled.
I think any node is fine for linux, easier for people to install it with their distro
same here if the instance exists the used volume show be available
Yeah we need this fix in asap.
You're right, but I don't see how it's a problem, nor do I see a better way.
Here, I wanted just to delete from Array the previously removed menuitem element. 
I found this method [here](http://wolfram.kriesing.de/blog/index.php/2008/javascript-remove-element-from-array "JavaScript: Remove element from Array").
Could you show a preferred method for this?
Why to check if the type is "be_simple_i18n"?
You want seperate your I18n routes and the original symfony yaml routes?

I am not agree with this commit because the modification is useless. You can name your yaml files route with a prefix or suffix to differentiate the original Symfony routes and the BeSimpleI18nRoutingBundle routes.

In the master of this bundle the be_simple_i18n is necessary because the Yaml file loaders of BeSimpleI18nRoutingBundle and Symfony are not same.
The exports are new, the blobservice thing was a quick hack to get it working. Will fix that as a separate issue.
> The interceptor ordering will be salient based (number based) and method interceptor will have a high but predefined number.

I assume you are talking CDI here, but there might be other technologies.
zepto yad gerefti digeeeeeeeeeeeeeeeeeeee!!!!!
new_translation.locale_id = Locale.where(:name => :en).first.id

Locale.find_by_name(:en).id
It's more complicated, but more generic. The same line of code can be used for updateSettingsFields and updateCMSFields functions. I guess it might be more illustrative to just show two examples.
You are correct it was a file eof character that created the SHA to change. Probably shouldn't have been check in, but alas it was.
This can be done on one line.
`return toBeIgnored.indexOf(file) === -1`
Should we hardcode the version? Doesn't that defeat the purpose?
it doesn't take or return an array when running in unit tests, it returns it from native
I think I just used:
`expect(JNEXT.invoke).toHaveBeenCalled()`

and it works fine
Ahhh retun as in new line. Will do.
i wasnt sure either .. but since it has to be used in different places it seemed like it would then need to be a twig extension and then it seemed like more trouble than it is worth
this replaces your get method
De par leur