labofsahil/github-event-dataset-2012 huggingface dataset:
On Mobile Web, the current implementation does not wrap children, and if the children take up more space than the parent, then the children are clipped. This is about to change, however. PR https://github.com/appcelerator/titanium_mobile/pull/2067 includes a new horizontal layout algorithm that matches (in theory) iOS.
Why is this disabled ? The class is here, ain't it ?
mark as pending, then.
no, the constants are never directly used as per your example (you could, but what you are interested in is in self.variables), but they are supposed to stay constant (but i'm sure that is not really completely valid throughout all code).

i thought about using the self.compiler_cc instead of COMPILER_CC. however, using constant like this allows for clean code when using multiple inheritance. it's far easier to overwrite the constants than to change the __init__ and guaranteeing MRO-safe code (it's also a lot cleaner looking and imho more clear to understand) 

if you want constants that never change across classes, just define them in the module instead of the class.
just add note for that in readme
what about making it more user-friendly by exploding on the comma and trimming the values ? Currently, you force the end-user to separate the names by a comma followed by a single space
Gah. I missed this because I tested against the case with a DocBlock containing @package before a define statement which currently doesn't get documentation due to another bug!
Not sure why this is commented out, but it's normally better to just delete code instead of committing it as commented out.
I can see why this has been added to an existing test, but would prefer it to be separated into its own test.  Litmus 15128 is a pretty big testcase and putting all of it in one test will make it more difficult to debug later.  We had to do the same thing with either the homepage tests or the layout tests for desktop IIRC.  

Otherwise, looks good.
Why was this indentation changed?
Probably, but not applying it kills Rails 3 support. The problem we ran into here was that `content_type` is a `Mime::Type` object in Rails 3, which means you can't just compare it with a regex the way you're doing. This always returns `true` in Rails 3, since `false != nil`:

```ruby
((content_type =~ %r{^text/html}) != nil)  || content_type == nil
```

...which means that everything — images, CSS files, etc — will get run against the HTML validator. The moral of the story is that while this pull request might not be a silver bullet, doing nothing means we're pointing Rails 3 projects at a fork until there's a fix.
I don't think that works if sep is not an array. The unittests tests check a lot of different RoR cases, but sep is always an array, never an inputRange.

I think the test case:
```D
join(filteredWords, filteredWord1);
```
Would fail. I may be mistaken, but I'd be very surprised if this was not the case. Either way, I'd want to see it tested.

It seems like a call to `sep.array`, or some (static) variation thereof (depending on RoR/sep) may be better suited.
Not used in CTFE? This function appears to be used in a string mixin. How is that not CTFE? `Format` itself is template metaprogramming, but what's going on here definitely looks like CTFE to me.
This code along with it's helpers like makeRangeTuple better get removed given how well it is replaced by appender. 
Still Q about *InPlace and reuse the array holds.
Hey, stop. Already marked it `package` so I see no problems here.
Couldn't just the `sumRight` in `join` be changed to `foldLeft` to avoid recursion?
this one makes it 3.x only; doesn't it?
np, will do
In this case, `<label for="tlc_assigned_to">` is more appropriate than `<span/>`, imo.  If this change was a matter of styling, CSS it up!
That's a pretty meaningless instruction ;) Can you research what <meta title> actually does, and rewrite? For example: "Replaces the page title in the results of most search engines"
I'm curious why those assumes? Those tests won't pass with HtmlUnit?
This concerns http://forums.zotero.org/discussion/10671/new-american-meteorological-society-style/?Focus=120289#Comment_120289
remove this hack please :)
`%1's` (и далее много где аналогично).
“the size is force” ? Au-delà des sous-entendus pervers, je comprends pas tout…  ;)
We should remove this in favor of `overflow:auto` on the parent container
Link to said doc?
HPPA64
This indentation is a little confusing.
Ok cool, makes sense.  Thanks!

Can you fix the spacing to be like the rest of the file.  Also $actual_userid should be $actual_user_id to follow the same formatting.

Thanks!
функциональность - это характеристика, не подойдет.
What's the point of this class if there are no methods or members defined? Wouldn't an interface make more sense anyways?
What? Oh, user is a userprofile.

We should be doing this at the top:

```python
if request.user.id == user_id:
    user = request.user
    page_type = 'profile secondary user-details'
else:
    user = get_object_or_404(User, id=user_id)
    page_type = 'secondary user-details'
```

And then pass both `user` and `profile` to the template and stop bothering with `user.userprofile`.
there may or may not be some OpenSubdiv Android goodness ready in a not too distant future...
I only like to use `return` for early returns. Not a huge deal, obviously, but I think it s a decent enough convention
Can we use 4 spaces before the remove the spaces between `:` and `auto`?

so this instead:

```css
.widget_name {
    overflow: auto;
    width: 350px;
}
.widget_name .main_container {
    height: 400px;
    overflow: auto;
    padding: 10px 5px;
}
```
since we are now using this method in more than one test class, we may as well extract it into a static utility class ... maybe `MohTestUtils.createQuestion()`?
is empty string to represent blank subject okay?
this disables the test for all plattforms, we should not merge like this. if we can't fix it, we should put something into our implementation loader to only skip this if we are on sqlite. but lets first see if we can fix the problem.
Makes sense.  No opt in here.
Gaaah! what's with all this commented out code :-)?
no entiendo porqué agregar las propiedades. Si las necesito, se las pido, sino, con agregar al chabón alcanza xD
Looks like I need to fix code here. From Client.js I call "return window.webworks.execSync(_ID, "purchase", args);"

SO, that probably looks for 

purchase: function (success, fail, args) {

in index.js

I will fix the function signature and fix the code with

			try {
				paymentJNext.purchase(purchase_arguments_t);
				success();
			} catch (e) {
				paymentJNext.stopEvents();
				//throw "Purchase Failed with error: " + e;
				fail(-1, e);
			}
zepto plz
I'm glad you brought this up, that would be cleaner except what I meant to go for here was to bring in all organizations in one query and avoid having a second COUNT query. I must have changed it from using len(actee.user.organizations.all()) to count without thinking about why it was I had it that way initially.
Okay, will add tomorrow.
Хорошо бы иметь перед глазами список всех глобальных костылей, а не искать макароны по всему тексту.
Зойчем оно вообще?
This is described in gh-19. Copy-paste:

It seems that certain MBeans from EDG become available not before EDG actually starts. These are typically server module's MBeans like HotRod and Memcached. Furthermore, this happens only sometimes.

We should IMHO wait for an MBean (with certain timeout - let's say 30 seconds) when it is not available the first time it is accessed.
Hmm, there is still a problem with MBeanObjectsProvider. This class has methods that look up MBeans based on a pattern so it can happen that some MBeans according to the pattern were found but not the one that we're actually looking for - this check happens after a group of MBeans was retrieved. I will look at it.

This whole problem is related to JBossAS7's service being loaded lazily, so it can happen that MBeans are available later than AS starts. We could, of course, wait directly in the test but IMHO it is convenient to do this change directly in the ispn-arq framework.
Should be a static class
Type is not part of the version info.
you should add the use statement so that copy-pasting the example results in a working code
@nacmartin I think we should get this chance to overcome all of our past dependency problems