The problem is that the entry in the array needs to be a functional call. It could be a method (by reflection) or a sort of lambda expression via another class. All of these options are slower than the switch.


ha!


protected?


Intuitively it seems like it would be simpler (and probably faster) to tell the Sender directly to send just a header (e.g. by adding a Bool to OResponse, or a new OHead constructor, or maybe a new Head constructor in Aux), and avoid the TBQueue / waiter machinery entirely in this case.  Am I missing some reason that wouldn't work?


wouldn't it be awesome if you could extend Enums then you could just add extra cases to `UITableViewCellStyle`?


@recena I think this screws up any use of the agent in the build


This may or may not be useful to you, but all those bots (and a few others) are in the @guardian/bots GitHub team - so you might not need to configure this here.


`encodeId` and `encodePath` do not need to be public and I can keep all the methods to return `DatabaseURIHelper` to keep the build chain.  Are there any methods that need to be static utilities? If so, we can have another static class to call at these utilities i.e. if the encode path is needed by itself, make it static and move it to a Utils (maybe existing?) class.


Ok. My suggestion would be to leave implementation order to the text of the spec and favor naming the directories in a fashion that simply communicates which story is contained within. I agree it would be nice to have them them ordered when browsing, but having to rename directories when we re-order work (or insert a new story in-between several others), breaking links everywhere in the process seems like it's not worth the benefit.

I'd be happy to write something down in the flow wiki that says implementation order of stories is determined by their position relative to one another in the feature spec.


原文の指すものを僕が正確に理解してない可能性があるのでこれはなんとも言えないのですが（なのでissueで立てるべきだったのかも）、ではこれどう直すのが正しいのでしょうね。


Did you change your comment? In this case, yes, the array could be as efficient as the switch, I need to check the byte code.


Thx man. :)
I am sorry to be so nitpicky, but URI is an abbreviation and is always written in capital letters.


Might as well change this one too for consistency.


Кстати (в отрыве от всего остального): `return true if array.empty?` :)


Still fails if there is no match, `mobj` will be None.


What's the new jar?


В целом да, дух уловлен верно, можно продолжать (учитывая мои замечания).


(yes I had to edit the comment, after I read your `UNKNOWN` alert)

I'll submit a PR


We would like to avoid adding a dependency on Grunt. In another place we use `shelljs` together with `archiver` to create zip files.


Ooh, nice example of `FBSnapshotTest`. Super useful.


It will be approximately simultaneous with Yii 2.0.7 release, which is scheduled for the end of the month


The milliseconds issue was actually secondary, I noticed while working on the script that if you set a expiry timespan of less than a second it was being rounded down to zero.

The `and 1 or 0` returns 1 if the first part is true (i.e. the `redis.call('set', ...)` added a key) or 0 if it didn't (like the `?:` conditional operator in C#)


We already did it for some other public repos (SDK, github-api-client). In fact anonymous user has the View Status right and only this one.


Can val be nil at any point?


lgtm with comments


Hmmm. I wonder if we should use a new package name for the jvm-testing plugins, rather than adding more duplication between subprojects?


Remove two irrelevant conferences. I was hurried in adding them while at work without checking them in detail.


why do we have an instruction that is both `branch` & `indirect_branch` (with values 1, 1) at the same time?


http://www.innovationsintesting.org/index.aspx
Program: https://www.eiseverywhere.com/ehome/index.php?eventid=129906&tabid=346339


It's `gradle-testing-jvm.jar`, corresponding to a new subproject (`testing-jvm`).


Which names should renjin be using? does collected_data have a names attribute or a dimnames attribute or something else?


favicon now showing


hmm, so what should I do to init push if we don't use set here?


**[unitTests_php_branches run failed](http://qa-s2.wikia-prod:8080/job/unitTests_php_branches/23948/testReport/) for this commit**


https://events.bcs.org/book/1825/
Past conference topics: http://www.bcs.org/content/ConWebDoc/55437


Yes, we definitely will need to do this. Software model projects shouldn't depend on ':plugins'. It's a good chance to detangle the ':plugins' project a bit more.


i think the problem is in the video and not the method.
i can't play in the browser i get this message:`Acest fişier nu este disponibil momentan. Te rugăm să încerci mai târziu.`.


Great!! :)

This is a little bit shorter with less repetition:
```javascript
var route = "/state";
if (semver.valid(mesosVersion) &&
    semver.satisfies(mesosVersion,"<=0.25.0")) {
  route += ".json";
}
```


I'll remove all `NSColor.CurrentControlTint` calls everywhere, so we have only one color (for now). This is the start.


Do you really only want first and last name to be required when using this form? In theory someone could create the user specifying a first and last name and then if the user has the ability to update their information they could remove their first and last name since this form is for creation and it's the only thing that's forcing those fields to be required. If you removed blank=True from them in the model you can take L# 16-17 out of this file and first and last name will always be required.


the new homework


Thanks!


alignment


@sevoku: I think we'll have crossplatform black background soon, so there won't be any need for platform checks (reason: ~sel icons need that background anyway).


I just saw the byte code, I think the tableswitch opcode wins the boundary checks of the array access.


@acozine If we want to make this more permanent/generic
1) The key stuff, lines 7-22 could be moved to the vagrant_setup role and replace or augment [lines 5-11](https://github.com/curationexperts/ansible-hydra/blob/master/roles/vagrant_setup/tasks/main.yml#L5-L11) there.
2) The target repo could be replaced by a variable.
3) Consider whether to move the repo destination to /vagrant (shared with host) instead of /home/vagrant (have to ssh into the vm to edit)
4) Decide on a standard capistrano stage name - I used 'internal_vm' in newfia - and/or parameterize the cap stage as a variable
5) figure out if we really need both restarts - I think only the Tomcat restart is really needed and only on the very first deploy (where solr and fedora config files get updated), but I haven't had time to test in detail.


oh, so how could I set value for them? could you give me some advices about it? thank you!


@sevoku: This is not a formatting change, it's just syncing `LoadLightStyle()` and `LoadDarkStyle()` so it contains same things except values.


`URL::current()` perhaps?


@tpoisot,

It looks to me like `fuzzaldrin` sorts on the score of `.author` as part of `.filter()`. Do we need to tell it to sort again?

Thanks,
Andrew


Maybe use separate folder?


This logic might be better in `DocumentationRenderer` rather than `DocumentationController`


made these powers of 2 in case we ever want to do bitwise operations


Yes, skins.xml can be dropped. I put it there because I wanted to create a layer for the site links viewlet. Like suggested here: http://docs.plone.org/develop/plone/views/layers.html#creating-a-layer

But the layer isn't necessary at all.


If your parameter name is "variables" and your dictionary is ```{"variable1" : "value1", "variable2" : "value2"}```  it will look like:
```{ "variables" : { "variable1" : "value1", "variable2": "value2" }}```
This also fixes the problem with the encoded quotes. As I said in another message, Asterisk fails to deserialize messages like:
```{\"variables\" : {\"variable1\" : \"value1\", \"variable2\" : \"value2\" }}```

I don't know why but it ends with an error:
```
res_stasis.c:1856 stasis_app_user_event: unable to set eventname to blob
```

It tries to add the event name to the json and it fails. Apparently there is something that Jansson library doesn't handle well in his ```json_object_set_new``` method. I stopped my research there.

My asterisk version is 13.6.


in renjin the output from format(do.call(...)) had no colnames, as a consequence in db the timings were given non-informative names (eg V1, V2, etc).
in GNU R they are named user.self/sys.self/elapsed/user.child/sys.child.
now the naming is consistent in both GNU R and Renjin


we already use separate folder. And now we will use separate variables


Yep. Same is true for URL, but I've [seen it in mixed case](https://github.com/mesosphere/marathon-ui/blob/master/src/js/components/TaskMesosUrlComponent.jsx#L42), thus I sticked to that writing style. Would you like to adjust the writing style?


:) So fyi, I can't click any of the links yet, but I still love it!

Also, thoughts on making this generic so that we can get a view like it for JS, other langs?


On Fri, Dec 04, 2015 at 07:29:29AM -0800, Raniere Silva wrote:
> Fix suggested by @wking

No need for recording editorial changes in a separate commit.  Feel
free to squash into your original commit.


I'll probably take a look at it this weekend, see if there's anything I can help out with!


But where (in renjin) are the colnames being dropped? By sapply? By rbind? By format?


In doing #310 it pointed out that this is a duplicate definition of plugin:

In #310 I revert to using the original, longer, list of names.


The code already was a mess of tabs of spaces, so understandably it is hard to choose :) Would be nice if that got fixed to spaces, but we can also do that ourselves in a later commit.


And thanks for the commits, you just beat us starting at this widget :)


I think if possible the `build()` implementation should be in the `URIBaseMethods` then we can try to make sure we always build them the same way and in one place.


TeamCity Xbim :: Xbim Essentials :: XbimEssentials [Build 150](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=562&buildTypeId=XbimEssentials_XbimEssentials) is now running


protected?


Yeah, but it assumes that every invalid version is compatible with the new routes. I prefer to use the old/deprecated routes as default. What do you think?


@FadeMind  added 03299fa63c95bd2894ec616555e9c868f522c9d6


使用 sequelizejs 的 model hook 來進行處理如果
1. 使用者建立時 afterCreate 檢查有 email  則進行優惠碼送出
2. 使用者更新時 afterUpdate 若元 email 為空，更新後有值  則進行優惠碼送出


TeamCity Xbim :: Xbim Essentials :: XbimEssentials [Build 150](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=562&buildTypeId=XbimEssentials_XbimEssentials) outcome was **SUCCESS**
Summary: Running Build time: 00:01:09


We need to think if returning -1 for failure is ok here, since -1 is also getting used in 2 different, totally separate purposes in this namespace and related functions.


There is a lot of commented out old code that will need cleaning up too.


can this fix the problem:
```python
                mobj = re.search(r'(\d+)x(\d+)(?:_(\d+))?', key)
                if mobj:
                    width, height, bitrate = mobj.groups()
                formats.append({
                    'format_id': key,
                    'url': video_url,
                    'width': int_or_none(width),
                    'height': int_or_none(height),
                    'tbr': int_or_none(bitrate),
                })
```


enought -> enough


Hi @MisaelSalcido, can you add a new example for this but using the dropins option? This also can show to the user that we can publish with filesets to the dropins. Something like:
 <wlp:deploy ref="wlp.ant.test" >
     <fileset dir="${basedir}/resources/">
         <include name="**/*.war"/>
     </fileset>
 </wlp:deploy>


Got it!  So, is the 'get', 'set' or 'pexpire' command that (sometimes) returns 'OK'?


Last thing: did you need to change the renderer? Seems like whatever is chewing on these values needs to be updated too (unless you want to show the user true/false/null over Yes/No/-).


EconomizerIntegrationNew (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1441 of 1441 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg) ![Coverage Badge](http://img.shields.io/badge/coverage%20status-70.51%25-green.svg)


clean instead of refresh?


1.3.9.1 is not available on NuGet. 1.3 is too old and has breaking changes, and for some reason 1.4 does too, but the latest - 1.4.9 - does not.


Missing var declaration


nvm this is my mistake. It does need it.


@malirod, as far as I understand it doesn't hide the problem since on QNX it would work in a proper way


2.5.2.9222 is very old and has disappeared from NuGet. Used the latest 2.5 version (2.5.10) to ensure no breaking changes.


I'll make a test to see what's actually faster, the switch vs the array access.
I'm beting the array will be a hell of a lot faster.
I'm betting that there won't be any boundary checks, I think the runtime should be smart enough to eventually stop making those, in sort of a predictive manner, or it simply just breaks when the bounds are broken and you step out, but I might well be wrong.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8076](https://teamcity.mesosphere.io/viewLog.html?buildId=86473&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Execution timeout Build time: 01:00:58


ok, I didn't know about the anonymous access, why not then


I'm trying to compile latest parse code with Unity4, but I'm having problem with this call:

RegisterSubclass(typeof(ParseObject));

I don't really get why it should work, because ParseObject doesn't have public default constructor and RegisterSubclass requires types to have one (it throws this exception: "Cannot register a type that does not implement the default constructor!").

Could you explain why this should work?


what if i change it to:
```python
                key = video_file.attrib.get('bitrate')
                format_info = {
                    'format_id': key,
                    'url': video_url,
                }
                mobj = re.search(r'(\d+)x(\d+)(?:_(\d+))?', key)
                if mobj:
                    format_info.update({
                        'width': int_or_none(mobj.group(1)),
                        'height': int_or_none(mobj.group(2)),
                        'tbr': int_or_none(mobj.group(3)),
                    })
                formats.append(format_info)
```


This should be the exact one for the latest version


EconomizerIntegrationNew (Myoldmopar) - Win64-Windows-7-VisualStudio-12: OK (1977 of 1977 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


**[unitTests_php_branches run failed](http://qa-s2.wikia-prod:8080/job/unitTests_php_branches/23949/testReport/) for this commit**


` `, you forgot a semicolon.


I was looking into this more last night after I mentioned it in IRC.  I don't think we actually have to bump all the way to 0.9.2, it's just the test that relies on behavior introduced in that version.  We just need to rewrite the test to not use `naming_conventions`.  It would be nice to at least use 0.8, which includes `sqlalchemy.inspect`.


On my opinion usage of the ifdefs should be hidden as far as possible. If such fix is really required, then it can be moved to the ConvertPathForURL. Ifdefs in the business logic looks not good.


Good


I know you're smiling, he he he. I'm starting to doubt myself as I write it, damn it.


Hi @MisaelSalcido sounds a little bit more clear if the values to the `deployTo` are `dropins` and `configDropins`. Can you change it, please?


弄好了


Ok, got you. Agree


I'm pretty sure we don't want to expose `FileOperations` directly to rules-land. Would want to restrict the API, at the very least.


I would use `if (empty($data->returns_success))` here because it may be an empty string (I believe). The same applies for returns_failure.


develop (Myoldmopar) - i386-Windows-7-VisualStudio-12: OK (1442 of 1442 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


This is just a question: What was the motivation beind modifying the pod manifests to replication controllers? What is the difference between the two?


Hmm, true, didn't thought about that!
But thinking the other way around, why should an invalid version should work with the new route format?
Kannst Du halten wie ein Dachdecker. :)
I am fine with both, but personally prefer my variant.


Same as my previous comment. Can you change possible values of `deployTo` parameter, please?


These (I believe) are always set, but you might wish to do extra `empty()` verification with `$data->parameters` and `$data->returns_*` and display "This function has no parameters" and "nothing special is returned on success"


It was the set command that returns OK, the others all return integers.

I hadn't noticed it before as it's (in theory) a fairly rare situation - for that line of the script to execute the key needs to have expired from redis before the timer gets around to running the extend script, which would probably only happen if you're stepping through in the debugger, or maybe if the thread pool is very busy and you have a short expiry time set.


Probably shouldn't end in `.git`, right?


I'm not aware of anything needing to be static was just thinking that was potentially an option to avoid breaking the build chain.


@claudiopro Done


This linking part should not depend on whether we use the system boost or boost from CMSSW. This is why different paths are set above.


@andrewsmedina it's God's choice.


yep, see above: https://github.com/kaedroho/wagtail/commit/6918a9be2fb39bd0b8cee271ab2803a9172cdba0#diff-509186d17133395aafeb7c62930e9881R584


Yep, this was trigger by your comment on IRC (thanks!).

Agreed about removing the `naming_convention` test dep, I just wanted to get this to represent the actual state of affairs of the project. Happy for support back to `0.8`, although the last release for that (`0.8.7`) was well over a year ago.


This sounds a bit nitpicky, but this should be ClangFormatConfigFile, just `clang` is something much bigger than clang-format. And I will test this as soon I find some time. So at some point in time after Monday.  But before I  test this, how often is this evaluated? Once? Once per buffer? Once per format? And to what is it relative? The file or the location where I stared vim?


lgtm


Додав новий заголовок


`fs` is a core module, it does not need to (and should not) be installed via npm.


The idea is for a replication controller to restart the pod if it dies. I've heard recently, though, how a replication controller won't ensure that there's exactly N pods, just that there are at least N pods, and I suppose that can lead to issues...


This changes will use the $post->post_excerpt in its entirety, or when post_excerpt is not set it will only create an excerpt from the_content if a length is set in the short code.


Oh, good catch. We are inconsistent. I would suppose to stick with the capital letters, like in ```encodeURIComponent``` or ```apiURL```.

It's funny, in the config.template.js, we have both variants directly besides each other. :)


Nice solution!


Yo, glob isn't included in the package dependencies


`forEach` is already imported from `utils`.


Remind. Do not commit file as .exe, .o .  They can be recompiled
http://huan-lin.blogspot.com/2012/04/git-ignore-file.html


:+1:
![s](https://i.imgur.com/IEQc5Dn.png)


Is it ok?


Never use synchronous methods`!

Instead use async methods from `fs-promise`.


This is the initial brightness until Android kicks in and takes over. So it started bright then dimmed. This way it stays even through the boot process.


Good


Don't worry. 0eb4c3e


@lojack5: Would it harm if this were in modInfos.refresh() ? As far as I can see it would not matter as far as RefreshData is concerned cause  bosh.modInfos.refresh() is called anyway above: https://github.com/wrye-bash/wrye-bash/commit/6452bcb4b44d4b434e8636b35b69351cb6742869#diff-be6a3eed6c0edcc900fe0291f274970bL4008 - except if the mark mergeable depends (or must not precede) any of the operations in between which does not seem probable. On the other hand it may not be desirable to have it in modinfos refresh for some reason (not performance - but it would pop up a dialog in unexpected situations ?)

I need to fix this cause I need to revisit RefreshUIMods and RefreshData stands of course in my way - I need to simplify it - see #205. Every little bit helps...


you are accessing an undefined variable here, ``sortable_current_page `` has not yet been set, hence its part of the global namespace – ugly!

Why did you remove the statement ``var page = $.getQueryParam('p');``.


Also, vatesfr/xo-web#546 requires to also look in `${__dirname}/../node_modules`.


No callers to this method.  So removed it.


Whoot! :tada: thanks!


@stephenc I did not modify anything (important) in `SSHAgentBuildWrapper`. [Reference](https://github.com/jenkinsci/ssh-agent-plugin/pull/4/files#diff-de89c992e5ff4164168d5a4bba09aa5e).


Não veio o método


I think it would be better (more flexible and more efficient) to pass the plugin path directly.


Moved this to openedx/core/lib/courses.py.


Относительно исходного источника раскомментировал строки
```
*.ps
*.eps
*.pdf
```


Removed this in favor of the implementation in LMS, which is now moved to openedx/core/lib/courses.py.


Moved to openedx/core/lib/tests/test_courses.py.


As far as I can see, all of the above tests are on titles that are completely blank after stripping - I'm talking about a test to confirm that a title such as `<space><space>hello world<space><space>` is accepted and saved as `hello world`.

(Github doesn't let you write preformatted text with leading/trailing spaces? That's a bit rubbish...)


LGTM


lol, forgot that nginx.conf is not included. Well, this commit was made when SSL was enabled so yeah.


Why keep a `if` statement if it is always `true`?


If not assigned again, should be declared as `const`.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8077](https://teamcity.mesosphere.io/viewLog.html?buildId=86474&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Execution timeout (new) Build time: 01:00:57


$post->post_excerpt will be used as the excerpt if it exists.
An excerpt will only be created by truncating the_content if a string length is specified in the shortcode.


@vr2262 hmm, that's too bad.

I didn't realize that Flash wasn't supported by default on Android anymore... I agree that we probably don't want to go down the path of shimming with a Flash fallback in that case.


filesss


Moved to openedx/core/djangoapps/models/tests/test_course_details.py.


@jmwohl I asked the question on Stack Overflow: https://stackoverflow.com/questions/34070341/is-there-any-way-to-get-a-phones-camera-stream-in-the-aosp-browser

Hasn't gotten any attention though...


looks good, thx :boom:


I love this new feature you have added! Thanks so much!


Uniq


This is not a good idea. Ideally, atoms can be optimized out by the compiler, but not with such a `@TruffleBoundary`. Would it be sufficient to compute the hash lazily?


Работает отлично :+1:
Варнинги:
bash-3.2$ ./hoverboard
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
( 2 раза )


Moved from original `CourseDetailsViewTest` (seen below in the diff) to here.


Ideally, here only the most expensive case is a boundary. Ideally, you got a specialization that already takes care of the `==` comparison.


The bug was caused by the fact that when a merge failed, the working directory was left in a state where Git refused to do anything until the conflicts were resolved or the merge aborted. So checking out other commits and trying to merge them failed.

These lines of code abort failed merges, allowing future merges to run as expected.


FYI - this is now removed in commit #4.


1. The shape of the selected features are modified as the ones in Edit mode.
2. Popup is not displayed when the features are selected using 'Shift Key' and 'click'.
3. Buttons to select and delete features are placed close to each other.
4. Clearing the features selected is fixed using 'click' event of aoi_extents.
5. The capability of deleting Polyline (LineString) is added, but not tested.


I think, most comparison operations deserve a specialization of some sort, to avoid them being true function calls with @TruffleBoundary.


Hello,

The short array definitions is breaking code in PHP 5.3.3 which is shipped with CentOS 6.6
This feature is introduced in PHP 5.4 - http://php.net/manual/en/migration54.new-features.php
You might revert that part of patch for PHP backwards version compatibility.


Why not expose `FileResolver` instead?


Moved to openedx/core/djangoapps/models/course_details.py, but then completely removed in commit #4, since no longer needed.


i dunno why you removed this when it can be easily reseen


I suggest to pass a ValueBase instead of a SILInstruction, because we also want to get notifications for e.g. deleted block arguments.
Considering this, we might also pass the containing SILFunction as a parameter, because not all ValueBases have a parent. E.g. what happens if we delete a SILUndef?


Removed in favor of CourseDetails.update_about_item.  Both have same implementation.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8081](https://teamcity.mesosphere.io/viewLog.html?buildId=86483&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 205 Build time: 00:10:15


Only some experiments will tell...
My feeling is that threats in the endgames are very important.
You want to tie the opponent King and pieces to defensive duties.

The individual Threat parameters have all their mg quite smaller than their eg.

But this overall weight is currently working in the opposite way.
So it is a bit confusing, the end result is not clear....

Once this global threat weight will be stabilized,
I think it should be merged back into the individual threat parameters, to avoid this confusion,
with some retuning of the individual parameters.


твой кол говно :3


what the fuck code!!!


Thinking more about this, we should remove `COLOR` and `SHAPE` as well.
Mainly because you can assume that shape and color has lower carnality as thus muhc less likely to have occlusion.  Also, for COLOR, if you specify color, you would get annoy if you see it lighter than you want (esp when there are only 5-20 marks)


#itshappening :rocket:


@josephsavona do you know if browsers do any sort of interning for strings like this? Wonder if there might be any benefit to storing a ref instead...


we should include the landmark description as well


I think the code I have is very close. Unfortunately, after experimenting with this code for several hours, what I found was that all of the blobs generated by a merge were given stage 0, even when there are merge conflicts. I don't understand enough about GitPython to know where the stage numbers come from or what they mean exactly, and the [GitPython source code](https://github.com/gitpython-developers/GitPython/blob/master/git/index/base.py#L430) is written in a way that I found made it hard to track down where the stage numbers are assigned. (It looks like they're using some kind of complex pattern I didn't have time to understand.)


`test_basic` now covers these.


Looks good, but 32K on a stack is not good.  I would think that the majority be under 1K.

However, where is `buf` used?  It is only used for printing?  Otherwise, it looks like line 229 should be referencing `buf` instead of `fieldbuf`.


Verified with @ziafazal that `has_cert_config` is no longer needed.


I don't know what we should do or not do, but I miss the `project.files(...)` method to create an arbitrary file collection. I can remove the service, but I'm pretty sure people will miss it anyway. The methods in `FileResolver` are not so pretty.

For reference, this is used here: https://github.com/gradle/gradle/blob/067dd78495d12fd019d92067255cc7a338f63dd6/subprojects/testing-jvm/src/main/java/org/gradle/jvm/plugins/JUnitTestSuitePlugin.java#L125-L125


> Should this be in this PR?

It doesn't really belong here, but I'm fine with the little addition squeezed in. If you think I should move it out I can.


develop (Myoldmopar) - Win64-Windows-7-VisualStudio-12: OK (1442 of 1442 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


@vr2262 ok, we'll keep an eye on it. If there's not already, we should add a bug in PT.


How about introducing somethibg new to wrap `FileOperations` instead?


> What about just adding an extra line? This `\n` is a bit ugly, imo. What do you think?

Totally, done.


Moved from CMS, but added the following methods: `update_about_video`, `fetch_youtube_video_id`, `fetch_video_url`, and `fetch_effort`.


I would still recommend having two separate samples as the preserveOrder option is used to influence the execution order of multiple (independent) test classes while the groupByInstances option is used to influence the execution order of multiple test class instances created by a test class factory.

I have simplified the sample code by removing the unique resource (which caused the sample tests to fail if the according option is not set) and adding output for visualizing the test execution order. Unfortunately I had to add a testLogging configuration to the test task for showing the output (especially of the @BeforeClass and @AfterClass methods). In order to not have this configuration in the snippet for the documentation I split the configuration of the test task (looks a little bit unusual to me).


That's ok with me. :)


Lol, is this an anti-bug ? Why 1.62f ?


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8084](https://teamcity.mesosphere.io/viewLog.html?buildId=86488&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 205 Build time: 00:05:17


@MisaelSalcido there's a reference to the previous parameter here. Would you mind fixing it, please?


@jmwohl https://www.pivotaltracker.com/story/show/103518624


Sorry to be pedantic, but why is `server-can-flash-window` not `server_can_flash_window`


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (1442 of 1442 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg)


`exit(1)` will be called if we have an empty `pid_file` setting.


this should be `false` otherwise the tests fail when run and they just save reference images instead.


> Should this be in the heroku adapter?

It can safely stay here, but indeed it's clutter when not deploying to Heroku. It would be better to move it on to the adapter.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8078](https://teamcity.mesosphere.io/viewLog.html?buildId=86476&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Execution timeout Build time: 01:00:08


> what about moving all this lines to the heroku adapter?

Indeed!


thank you @SilverFire


This is the only available 4.0 version available on NuGet


Unfortunately, the Windows service fails miserably and screams about private IP failure if you don't explicitly specify the bind addy on the command line as an argument, config file contents be damned. I wish I knew why. :/


```
"failed to lock '"` << pid_file << "'. locked by another process?" << dendl;
```


Iannis -- this `if YARN` and the one below should now be ready to move to the launcher, right?   Would you mind moving those?  AFAICS, those are the last `if`s which remain in the non-YARN agent code.  Thanks!


...maybe I should comment that as a windows-only thing?


Thanks - I amended this commit.


@stuarteberg What's your rationale behind adding support for lzma compression in our libtiff builds? Is it so much better than the LZW compression libtiff already supports? I'm always a bit sceptical about new codecs in data formats because compatibility is so much more valuable than a bit of saved memory. New encoders only make sense if there is a reasonable chance that the receiving end has the corresponding decoder. Is this the case here? Or are we at the receiving end and are urged to catch up?


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg)


I'm currently updating this article with other changes and will take car of this one when I do, so I would like to reject it. Will be publishing the updates next week.


I curse you  @tkrokli


const


Thanks! I noticed the latest release in the web documentation is already corrected.


yeah i noticed and i like how it looks :)

i think the final code should look like this (just to ensure that the original `jsreport.config.js` object can't be modified in runtime):

```js
var main = require('./lib/phantom.js')
var config = require('jsreport.config.js');
// assuming you have a utility to copy objects like lodash
var assign = require('lodash.assign')

module.exports = function (options) {
  var newConfig = assign({}, config)
  newConfig .options = options
  newConfig .main = main
  return newConfig
}
```


Two thoughts

1. We'll have to put something like this in the rest of the commands. Might be worth refactoring into a support module.
2. It might be nice to catch the exception from `gituseremail()` and `gitusername()` here rather than returning `None`. We could see if the underlying package that provides the gitconfig scraping has a unique exception class.

These aren't blockers though --- just thoughts for the next iteration.


The duration might be a bit long.


Yep, readthedocs watches for commits and automatically rebuilds the docs. :-) When we tag a new release, stable will automatically be updated too.


This can not be accepted for the following reasons:

1) There is no x86intrin.h in MSVC or ICL.
2) f16c intrinsics are specified as being declared in immintrin.h by Intel.


32KiB is fine, we build with 1MiB stack. The majority strongly depends what you have. The picture changes drastically if Windows logs and certain firewalls get into the picture.

You are right with line 229, patch follows.


This commit actually fixes this issue: https://github.com/SonarSource/sonar-csharp/commit/9aef3403a47a9c94cc7fb8ac45c878e5856e7815


This commit fixes https://jira.sonarsource.com/browse/SONARCS-566


lets add these files to the deletion patterns in the `polymer_element_config.yaml`.


put `const` for params that does not change


MPL


This is great. The naming is now PC compliant.

PC NIU.


too many blanks


Maybe add this to the deletion_patterns as well, but not all `.md` files (its useful to keep around the readme and changelog)


What methods would you keep? The ones I can see in `org.gradle.api.internal.file.FileOperations` seem to be quite convenient. Maybe `copy`, `copySpec`, `sync` are not that useful, and `getResources` can definitely be hidden.


ah, you remembered


blank line


This actually does generate the correct report for the crossing you have most recently clicked. However, it also generates reports for all other crossings you have clicked on since you visited the index page (unless you hit refresh). Not sure how to fix still


Dang it, I'm cursed. (Have I got a duck on my head?)
SQLyog sort of complains if a comment is not completed with a semicolon.
I thought that was correct, but I was wrong. Sorry for not checking that in detail.


add blank


Here is the stack trace when I apply this commit (actually, I clone entire your repository) and launch galaxy.
```
Traceback (most recent call last):
  File "/galaxy/lib/galaxy/webapps/galaxy/buildapp.py", line 63, in paste_app_factory
    app = galaxy.app.UniverseApplication( global_conf=global_conf, **kwargs )
  File "/galaxy/lib/galaxy/app.py", line 54, in __init__
    self._configure_models( check_migrate_databases=True, check_migrate_tools=check_migrate_tools, config_file=config_file )
  File "/galaxy/lib/galaxy/config.py", line 852, in _configure_models
    verify_tools( self, install_db_url, config_file, install_database_options )
  File "/galaxy/lib/tool_shed/galaxy_install/migrate/check.py", line 66, in verify_tools
    raise Exception( "Error attempting to update the value of migrate_tools.version: %s" % output )
Exception: Error attempting to update the value of migrate_tools.version: Activating virtualenv at /galaxy/.venv
Galaxy config file does not exist (hint: use '-c config.ini' for non-standard locations): ./config..ini
```


@jlirochon Player's actual height. ;) Ask @Mojang for the reason. xD


`libtiff` can optionally be linked with `lzma`, `jpeg`, and `jbig`.  Anaconda's package linked with none of these, and the lack of `jpeg` was a problem for us.  I remedied this will a pull request to their `libtiff` recipe.  We only needed `jpeg`, but while I was at it I tossed in `lzma` and `jbig` support, thinking "more is better, right?".

Alas, perhaps adding `lzma` (a.k.a. `xz`) was a mistake.  We didn't need it in the first place, and now we're paying the price of having added it.

FWIW, python 3 depends on `xz` out-of-the-box, so this issue was bound to come up sooner or later.


I think you forgot to add the new files in this commit.


@arunasp PHP 5.4 was released 3 years ago, it's time for CentOS to keep up.


There is also a `package.json` file in the `interfaces/folder`.


So, while the size is okay, crossing page boundaries on the stack is not is not good for TLB references.  So if the other items are allocated on the stack after that buffer, then you'll always use those pages.  if you have many threads that call into mmfields, then page usage will go up.


patch: https://github.com/rgerhards/rsyslog/commit/027ff7f47b5a6de0feff0fe8c10ef84424eb81f6 (to be run through CI)


ok so apparently hexedit for windows is not very good i was able to mod libcamera but not seccamera, any chance you could mod the exhibit ones, and or give me a tutorial on how to do it in IDA? :)


I'd rather implement a resetTo() method in Message class instead of introducing functionality that is only there for debug/testing reasons. With both the "resetTo" and "addTo" methods you can do what you want and the behaviour is clear from the naming.


This seems incorrect. The C++ standard states that all definitions in stddef.h are mirrored in the global namespace.


Yeah, ack on the TLB ref. But on the other hand, for those cases with large messages, we would need to do malloc/free each time, which would be far more costly. So I think the current implementation is the best compromise.


Oops!
Thank you for your PR :+1:


k, didn't know it even existed a deletion pattern. good to know.


Well, we could keep the alloc'ed mem in instance storage, but I am not sure if it is worth spending time on such a seldomly used module. But I wouldn't object a PR either ;)


That's a good question. I guess it was too late at night when I wrote the code.
Feel free to change it :smile:


blank line


Hey. I've got a question. Can you use just random() function from Glibc
https://swift.org/getting-started/#using-the-repl

On Linux
1> import Glibc
2> random() % 10
$R0: Int32 = 4


Nit: Shall we have the import block at the top along with the others? Also, separate the declarations from the iterations? (for the sake of beauty! :P)


BasedOnStyle: WebKit


In my opinion the parameter naming could be misunderstood. I'd call it something like "debug_only_recepient" or something like that to make it clear that if you set it the only recipient will be this one.


TeamCity Jarvis Framework :: CI-GitFlow [Build 65](http://build.prxm.it:8811/viewLog.html?buildId=5109&buildTypeId=CqrsFramework_CiGitFlow) is now running


Remove this.


:) sure

Do you mind if I also implement integer checks (> 0) in the luadef?


remove turbo-link. also remove gem


TeamCity Jarvis Framework :: CI-GitFlow [Build 1.1.9](http://build.prxm.it:8811/viewLog.html?buildId=5109&buildTypeId=CqrsFramework_CiGitFlow) outcome was **FAILURE**
Summary: Error running GitVersion Build time: 00:01:14


TeamCity Jarvis Framework :: CI-GitFlow [Build 66](http://build.prxm.it:8811/viewLog.html?buildId=5110&buildTypeId=CqrsFramework_CiGitFlow) is now running


lol, we have a common phrase in France, which says literally "their are walking on their head". It means "it makes no sense". I think it quite appropriate here.


TeamCity Jarvis Framework :: CI-GitFlow [Build 1.2.0-unstable.2+2](http://build.prxm.it:8811/viewLog.html?buildId=5110&buildTypeId=CqrsFramework_CiGitFlow) outcome was **FAILURE**
Summary: Error running GitVersion Build time: 00:00:51


Please add a how-to.


Здесь :heavy_plus_sign:

Только:

1. Зачем `<h2>` обёрнут в `<b>`?
1. Отступ для `<ol>` определённо лишний
1. `&` ?

Исправляем.


Ya, actually while you are in there would you mind removing ` - bower\.json$`? Those files are really the only way of tracking the current version of the elements, so I think we should restore them.


OK


Good Work


Perfect!


why do you use join table. remove it. it should work without this option


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8086](https://teamcity.mesosphere.io/viewLog.html?buildId=86501&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 201 Build time: 00:04:58


@Xephi !!!!!


You shouldn't modify src.buf.* function pointers after buffered port is created; they are set at initialization and then stay untouched.


as this is only for debugging wouldn't it be right if we'd only consider deliveryAddress if the environment is "dev"?


TeamCity Jarvis Framework :: CI-GitFlow [Build 67](http://build.prxm.it:8811/viewLog.html?buildId=5112&buildTypeId=CqrsFramework_CiGitFlow) is now running


I noticed since that with the field corrected, it now tries to download the token images for Duel Deck Anthologies sets but can't find them, I guess because of our different set codes.


is that correct ?


This needs to be a complete URL (domains should’t use capitals either), this: `http://www.powtoon.com/`


new line


@mehdiovic1234 CoffeeScript


rename to `getUrn`


rename to `getName`


I had a quick look at the site too, and registered to see if there was a more permanent URL that can be linked too (‘No!’). Deeply buried in the Support Center, there’s an email address, it’s probably better to just add an email for this entry (support@powtoon.com from: https://powtoon.freshdesk.com/support/solutions/articles/5000009895-why-has-my-export-to-youtube-failed-).


Game


Форматирование уж совсем не айс, но выглядить будет верно.


TeamCity MonoGame :: Develop (Win) [Build 3.5.0.891](http://teamcity.monogame.net/viewLog.html?buildId=11949&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **FAILURE**
Summary: Snapshot dependency failed: MonoGame :: Develop (Mac) Build time: 00:00:00


I see what you're doing, but I'm not quite sure why.  Could you explain what behavior this change makes difference?


I think the easiest way to address #100 is to say that the value "normal" should not be used because there is no uniform implementation.

I wonder if the computed value for line-height because of

> 8.4.3.2 Computed Values
> When style properties are specified using relative value expressions, such as a named color, a relative unit (e.g., cell), or a percentage, then they need to be further resolved into absolute units, such as an RGB triple, pixels, etc.
(TTML 1)

You can classify "normal" as a relative unit.


TeamCity Jarvis Framework :: CI-GitFlow [Build 1.1.10](http://build.prxm.it:8811/viewLog.html?buildId=5112&buildTypeId=CqrsFramework_CiGitFlow) outcome was **SUCCESS**
Summary: Tests passed: 132 Build time: 00:03:34


TeamCity Jarvis Framework :: CI-GitFlow [Build 68](http://build.prxm.it:8811/viewLog.html?buildId=5113&buildTypeId=CqrsFramework_CiGitFlow) is now running


Oops. Thanks for the fix. I'll get a new release out momentarily.


Added support of csgo.tm API to confirm trades via HTTP request.


Wrong codestyle xD


Yeah, I think I did a pull with some unpushed changes on my local master so it added a merge commit.  I suppose it could have been avoided but no big deal either.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8087](https://teamcity.mesosphere.io/viewLog.html?buildId=86503&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 206 Build time: 00:05:13


This broke the back button, I just get an empty left toolbar with two empty elements
```<ons-back-button class="back-button" style="display: inline-block;">
        <span class="back-button__icon"></span>
        <span class="back-button__label"></span>
</ons-back-button>```


TeamCity LabKey :: Trunk :: Premium :: Git sqlserver 2014 [Build 80](https://teamcity.labkey.org/viewLog.html?buildId=289482&buildTypeId=LabkeyTrunk_GitSqlserver2014) outcome was **SUCCESS**
Summary: Running Build time: 00:02:14


Thanks for catching this. Completely missed it after the conversion from word.


looks good


No problem. Also test how pull request works. :)

--
Qu Tang

On December 4, 2015 at 12:13:03 PM, sbilly-qmedic (notifications@github.com) wrote:

Thanks for catching this. Completely missed it after the conversion from word.

—
Reply to this email directly or view it on GitHub.


TeamCity Jarvis Framework :: CI-GitFlow [Build 1.2.0-unstable.3+3](http://build.prxm.it:8811/viewLog.html?buildId=5113&buildTypeId=CqrsFramework_CiGitFlow) outcome was **FAILURE**
Summary: Tests passed: 132; exit code 1 (new) Build time: 00:03:27


Yup, the settings we have are good. Any glitches you're seeing are probably in OSD normally. Of course if you have any suggestions for fixes (or repros), please file an issue!

And thanks for fixing the mobile viewport! Much better :)


No : we may use it in staging and preprod environments too.
Config parameters (`config_dev.yml`, ...) are there to let each developer decide what value he wants depending on his environments.


TeamCity LabKey :: Trunk :: Premium :: Git sqlserver 2014 [Build 81](https://teamcity.labkey.org/viewLog.html?buildId=289486&buildTypeId=LabkeyTrunk_GitSqlserver2014) outcome was **SUCCESS**
Summary: Running Build time: 00:01:49


Hm. Is it possible to make the `build-script-impl`-only options go away in all the common cases? I'd rather keep all the logic up in `build-script` and leave `build-script-impl` as a low-level thing. (Which we eventually want to redo in Python, so that we're not crossing language boundaries for silly reasons.)


> I think the easiest way to address #100 is to say that the value "normal" should not be used because there is no uniform implementation.

Ok with the text above, right?


@ydubreuil I think this causes another bug. We should loop as long as selectable. breaking after the first wake is not the right thing to do here at all


@ProfessorWest I completely missed the comment that we needed to rework our documents. I've created a class diagram is it to late for this to be considered for regrade


What about where points = 1?


Good Work


where does it say they are deprecated?


Hmmm. weird error. Nothing in the commit would cause that...

```
[exec] System.InvalidOperationException: There is an error in XML document. ---> System.InvalidOperationException: <Module xmlns=''> was not expected
[11:09:01][NAnt output]      [exec]   at System.Xml.Serialization.XmlSerializationReaderInterpreter.ReadRoot (System.Xml.Serialization.XmlTypeMapping rootMap) [0x00000] in <filename unknown>:0
[11:09:01][NAnt output]      [exec]   at System.Xml.Serialization.XmlSerializationReaderInterpreter.ReadRoot () [0x00000] in <filename unknown>:0
[11:09:01][NAnt output]      [exec]   at System.Xml.Serialization.XmlSerializer.Deserialize (System.Xml.Serialization.XmlSerializationReader reader) [0x00000] in <filename unknown>:0
[11:09:01][NAnt output]      [exec]   --- End of inner exception stack trace ---
[11:09:01][NAnt output]      [exec]   at System.Xml.Serialization.XmlSerializer.Deserialize (System.Xml.Serialization.XmlSerializationReader reader) [0x00000] in <filename unknown>:0
[11:09:01][NAnt output]      [exec]   at System.Xml.Serialization.XmlSerializer.Deserialize (System.Xml.XmlReader xmlReader) [0x00000] in <filename unknown>:0
[11:09:01][NAnt output]      [exec]   at System.Xml.Serialization.XmlSerializer.Deserialize (System.IO.TextReader textReader) [0x00000] in <filename unknown>:0
[11:09:01][NAnt output]      [exec]   at Protobuild.ModuleInfo.Load (System.String xmlFile) [0x00000] in <filename unknown>:0
[11:09:01][NAnt output]      [exec]   at Protobuild.ModuleInfo.GetSubmodules (System.String platform) [0x00000] in <filename unknown>:0
[11:09:01][NAnt output]      [exec]   at Protobuild.Tasks.GenerateProjectsTask.Execute () [0x00000] in <filename unknown>:0
[11:09:01][NAnt output]      [exec]   at Protobuild.ActionDispatch.GenerateProjectsForPlatform (Protobuild.ModuleInfo module, System.String platform, System.String[] enabledServices, System.String[] disabledServices, System.String serviceSpecPath) [0x00000] in <filename unknown>:0
[11:09:01][NAnt output]      [exec]   at Protobuild.ActionDispatch.PerformAction (Protobuild.ModuleInfo module, System.String action, System.String platform, System.String[] enabledServices, System.String[] disabledServices, System.String serviceSpecPath) [0x00000] in <filename unknown>:0
[11:09:01][NAnt output]      [exec]   at Protobuild.GenerateCommand.Execute (Protobuild.Execution execution) [0x00000] in <filename unknown>:0
[11:09:01][NAnt output]      [exec]   at Protobuild.MainClass.Main (System.String[] args) [0x00000] in <filename unknown>:0
```


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8079](https://teamcity.mesosphere.io/viewLog.html?buildId=86478&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Execution timeout (new) Build time: 01:00:10


very useful and necessary. thank.


Good idea! Done here 272ffaa
ut it's hard to avoid this [if](https://github.com/cchampet/loudness_validator/blob/dev_MediaAnalyserProgressionInFile/app/mediaAnalyser/AvSoundFile.cpp#L14) statement since the seek does not work if we print on console.


I used the same parameter name as in [Swift Mailer](https://github.com/symfony/swiftmailer-bundle/blob/master/DependencyInjection/Configuration.php#L114).
But if you want to make it more clear. It's not a problem for me to set another name :)


Split WorldState Input Handling into its own file


No problem if it's just a matter of name :-)


Why does refreshing here fix this test?


Lowest available version in NuGet.


Add Grid Entities to collision data for pathfinding


Show a different text box depending on what verb you used on what thing.


Fixed in [b1d9ea7](https://github.com/bedatadriven/renjin/commit/b1d9ea7358c151ffdf873c9b366fd3745e7a4e4b)


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8080](https://teamcity.mesosphere.io/viewLog.html?buildId=86482&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Execution timeout Build time: 01:00:08


Create some wandering interactables


yay :)


Regularity helps a lot.  I've picked up and dropped Clojure with months in
between sometimes.  I found myself relearning the same stuff a lot the
longer the interval.

On Fri, Dec 4, 2015 at 10:35 PM, Mike Gehard <notifications@github.com>
wrote:

> Yeah.
>
> I grabbed that from another blog post on Elm so I understood it on the
> surface when I wrote that code.
>
> Going back after some time I realized that I didn't really understand it
> so I want to make sure I really grok what it is doing.
>
> I'm guessing this will be a thing for a while since I'm not using Elm 8
> hours a day and only have so much brain space for stuff that I don't use
> every day. :-)
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/mikegehard/elm-minesweeper/commit/ad1073ccfbdacf6e3c970cd52eead69a1422f845#commitcomment-14789847>
> .
>


Do we plan to evolve with this class as a base class? If not, maybe add `final`?


1. Downloading the md5sum from a remote host is fine when we want to detect corrupted archives. It does not guard us from compromised 3rd party servers, which is the main point of the pull request.
2. We use 2.1.11 ;-)


This is an important discussion, which I would like to move to the forum. I will reply there in a new thread.


Probably wee need to add a kind of mapping.


For better error handling you can do that, yeah (set the error using ``CScriptArgReader::SetCustomError`` then).


This can be moved a few lines below, after the early exit.


Good work


At the #lineHeight entry in the profile table:

*The value "normal" SHOULD not be specified as there is no uniform implementation of the "normal" value at the time of this writing.*


The most Linux servers in companies are still based on CentOS 6 which mean another 2-5 years before switch over to CentOS 7. Also due breaking things between PHP 5.3 and PHP 5.4+ it is very slow progress for all web based software to migrate.


Deleted MatlabFetchTest via MATLAB


looks good


great! I don't see why this shouldn't go in as is, will do a quick test tonight then merge.


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (904 of 904 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg) ![Coverage Badge](http://img.shields.io/badge/coverage%20status-25.57%25-green.svg)


Without adding the <version> tag to the AnalyzeSkeleton_ dependency I wouldn't get the latest version, which has the new package naming.


I am not sure if everyone wants this


I cannot reproduce. How do you launch Galaxy? `./run.sh` ?

When do you stop it? Before it reaches `serving on http://127.0.0.1:8080` ?


On Fri, Dec 4, 2015 at 10:10 AM, Andreas Tai <notifications@github.com>
wrote:

> I think the easiest way to address #100
> <https://github.com/w3c/imsc/issues/100> is to say that the value
> "normal" should not be used because there is no uniform implementation.
>
That is not sufficient, since 'normal' is the initial (default) value. So
one must explicitly specify a non 'normal' value somewhere, e.g., on body,
since it will be inherited to all paragraphs.

> I wonder if the computed value for line-height because of
>
> 8.4.3.2 Computed Values
> When style properties are specified using relative value expressions, such
> as a named color, a relative unit (e.g., cell), or a percentage, then they
> need to be further resolved into absolute units, such as an RGB triple,
> pixels, etc.
> (TTML 1)
>
> You can classify "normal" as a relative unit.
>
Inadvisable. 'auto' and 'none' and many other keywords would have to be
treated as the same.

> —
> Reply to this email directly or view it on GitHub
> <https://github.com/w3c/imsc/commit/60f5991ca7cd842b88dc8a2bd881462a7317efed#commitcomment-14792151>
> .
>


well, graphene is there, ... so should the opi widgets


--didn't find a way to contact you,  but I noticed you also know much of the hashcat,  I would like to discuss some issues currently with regards to Proxmark and cryptos.


Quality software development there.


On Fri, Dec 4, 2015 at 10:23 AM, Andreas Tai <notifications@github.com>
wrote:

> At the #lineHeight entry in the profile table:
>
> *The value "normal" SHOULD not be specified as there is no uniform
> implementation of the "normal" value at the time of this writing.*
>

Doesn't work.

> —
> Reply to this email directly or view it on GitHub
> <https://github.com/w3c/imsc/commit/60f5991ca7cd842b88dc8a2bd881462a7317efed#commitcomment-14792409>
> .
>


LOL!


* Did you make sure to pass --enable-c++11 to configure? Why exactly does C++11 support detection fail? Did you check config.log to see the error message produced by the compiler for the C++11 check?
In general I would advise against forcing C++11, this is really an optional feature. Our code base is supposed to work cleanly with C++98.
* I am not sure whether setting _sdlconfig to sdl2-config really forces SDL2 usage. I think what actually happens is that it prefers SDL2 over SDL1.2 in this case. At least AFAICT in your case `_backend` is `sdl`, which results in `find_sdlconfig` to be used. Also please note that SDL2 support is considered experimental so far.


This part of code for datee seems to be already present few line before


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8082](https://teamcity.mesosphere.io/viewLog.html?buildId=86484&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Execution timeout Build time: 01:00:41


What about covering all bases: _`tts:lineHeight` should not be set to "normal" and should be explicitly specified such that the specified style set of each p elements contains a tts:lineHeight property the value of which is not assigned by initial value fallback_


This migration will break for developers who haven't run this migration yet, but also have other new pending model migrations.

New models that have added to app/models/** expect that their tables exist. Loading those new models here, will throw exceptions.   (As happened to me)


Fine with me.


my bad, it's because i wasn't used PHPStorm for this :/


@josteinaj Please check if this still works for you.


OK, well this is the program I tested it on is below. It sounds a bit wobbly at times on the :saw synth. OK if you just run ONE loop not four. Running on a MAc with 2.8GHz intel Core i7 processor and 16Gb RAM so resources of machine should be OK. Sounds perfectly smooth using with_fx :reverb,room: 0.8 instead.

two line break to watch below in t = (ring......)

############################################################

#Frere Jaques 4 part round using live loops by Robin Newman, November 2015
#Syntax here needs SP2.8 Will work on 2.6 and alter if you replace
#,delay: xx*c from the live_loop calls
#and insert sleep 8*c before each of the live_loop :tune lines instead

s=0.2 #adjust the tempo here by varying s Try 0.1 to 0.4
q=1*s #define quaver (q) duration
c=2*q #define crotchet (c) duration
m=2*c #define minim (m) duration
#define rings for the tune notes and the note durations
#by using rings, we can access the contents with the tick and look functions
t = (ring :c4,:d4,:e4,:c4,:c4,:d4,:e4,:c4,:e4,:f4,:g4,:e4,:f4,:g4,:g4,:a4,:g4,:f4,:e4,:c4,:g4,:a4,:g4,:f4,:e4,:c4,:c4,:g3,:c4,:c4,:g3,:c4)
d= (ring c,c,c,c,c,c,c,c,c,c,m,c,c,m,q,q,q,q,c,c,q,q,q,q,c,c,c,c,m,c,c,m)

define :f do |syn|
  use_synth syn #set the current synth
  #now play the next note selected by tick and the duration selected by look
  play t.tick,sustain: d.look*0.9,release: d.look*0.1 #sustains note for 90% of duration
  #sleep for the duration of the note selected by d.look
  sleep d.look
  stop if look >= d.length*2 - 1 #stop after 2 cycles. Note look starts from 0, so subtract 1
end
with_fx :gverb do
  live_loop :tune do
    f(:tri)
  end
  live_loop :tune2,delay: 8*c do
    f(:saw)
  end
  live_loop :tune3,delay: 16*c do
    f(:fm)
  end
  live_loop :tune4,delay: 24*c do
    f(:prophet)
  end
end

##########################################################


Okay, so it's still referred to as the naughty list in some places, but that's a minor edit once the final functionality is complete


`
var helloMessage="你好,swift"
println(helloMessage)
`


change template


It's just the first push, to show something.
90% of this work is just pasted from awesome @Hywan's work


Thanks for adding this.


You mean moved to places where this array is actually used? How this would help with code duplication? Current state is a bit ugly, I agree but I don't see how removing it can make rest of our code better.


This commit did indeed fix the reported resizing issue for me, but introduced a different unwanted behavior on resize.  I don't have a demo, but a workaround for me was to uncomment BOTH of the following lines referenced in this commit:

```
sticked[i].reset(true);
sticked[i].self.computeWrapper();

With those two lines now uncommented, my sticked content is finally behaving as expected.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8083](https://teamcity.mesosphere.io/viewLog.html?buildId=86487&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Execution timeout Build time: 01:00:13


No need to put twice the license badge


Tested, LGTM


何書きたいですか？


Nitpicking: there is 2 spaces after `télécharger`


Actually this might be a good commit for you guys. If you don't use RocksDB, it won't break the compile and the overhead will be minimal. If you do use RocksDB, you'll get tons of useful info in the slow query log.

As I said, these counters helped us debug many performance issues with MongoRocks, especially since it prints out the number of tombstones that query had to process (under a cryptic name internal_delete_skipped_count)


こんにちは、**Swift**！


Created a JIRA ticket: https://jira.mongodb.org/browse/SERVER-21770, but I doubt that Mongo will add support for this before 3.4.


This is yet again a tactical issue.
The main problem here is that you're not using an http library (I think libcurl will do here)


Hi !
The problems here is that unfortunately in some build system or projects generator is very difficult to exclude files from sources. This is one of the reasons the make and cmake and biicode and backfile are too complicate. They need to write complicate code to exclude this *.cpp files.
In other words, these  platform preprocess check are a workaround to make possible simple automation, that in other case will be very difficult to mountain, inconsistent, and will be always outdated... and people ask then why it don't compile, etc.  But maybe we find another solution. This is just a workaround, not very elegant. But I think it works.
I want to explore automatic daily test build in the "cloud" with travis & Co. and this is important for that.


LGTM


Can be simplified to:
private boolean isTrue(Boolean b) {
    return b != null && b;
  }


Player actual height is a bit more that 1.6.2F, so you should probably add 1.63F instead.


altHtml


One last thought: We've found on `json_matchers` that it's useful to test the negative case because sometimes pointers aren't dereferenced as expected and we get false positives when we only test the "happy path". [This RSpec test](https://github.com/thoughtbot/json_matchers/blob/master/spec/json_matchers/match_response_schema_spec.rb#L97-L115) is a good example of what I'm suggesting.


Hi, One of the five messy things in software is naming, the other 4 are caching, off-by-one errors and bike-shedding.

Sure, we can rename Folders to match the resulting images. Having done that now we have inconsistent makefile target names. -- Personally the names of folders don't really bother me but I can see it may be a source of a cognitive stress we can avoid.

In that same spirit can you dive in and change the makefile targets and any other inconsistencies?


Да это для теста было. Потом переделаем


To remove as already on top


I can confirm @errror's comment - I get the same error message when trying to run the script. This happens if you use Python 2 instead of Python 3. If you want to make it work on Python 2, changing line 23 to `f.write(data.encode('utf-8'))` seems to solve the problem.

However, after fixing this problem, I get the following error message (on Python 2 and Python 3):

    Preparing index.html

    Preparing CHANNELS:

    Preparing GROUPS:
    Traceback (most recent call last):
      File "./json2html.py", line 207, in <module>
        exportClass(groups, users, 'group', 'groups')
      File "./json2html.py", line 155, in exportClass
        html = prepareChannelContent(item_content, users, type)
      File "./json2html.py", line 85, in prepareChannelContent
        content += formatMessage(message, users)
      File "./json2html.py", line 50, in formatMessage
        res += message['text']
    KeyError: 'text'


@SandPox It works with the proprietary one? I'll look into that.. On my phone Youtube videos work fine, but videos on Facebook crashes the same way.


I think this should have `parent=None` everywhere -- otherwise the `value` property would not work.


:syringe:


Are we sure about this one? There's a hiccup in some atom docs if so.


@tute `app_name` and `template` are methods of `app_builder`, I think.


hi @KLuka, could you please create a new tag as well? Thanks a lot.


pesimo


HI


ESTA PERFECTO


Interesting. But using libcurl would add a build dependency that is in my opinion not relevant given the small amount of HTTP done in this program.


completes #2


all this private code should be after the public methods
it's a pain to have to scroll pages down to find out what the interface of this class might be


@alexcjohnson better?


うむ
HTMLとの違いとかよくわからないけど、HTMLのコードになるのであればOK

そういえば、使う言語言ってなかったね

・Webサーバ: Node.js(JavaScript)
・データベース管理システム: MySQL
・フレームワーク: express
・クライアントサイド: HTML, CSS, JavaScript

まりはちと決めたんだけど、意見ありますか？


Not needed (checked in Builder - and other checks in builder [e.g. schema] are not checked here).


Okay


Fixed. Thanks!


Possibly.  That was my original thought, but I didn’t want to make the logic overly complex.

That route basically says “compute everything you’re going to send to build-script-impl, and right before doing it, do the check on those arguments.”

That will work, but only as long as there isn’t yet another path to get to build-script-impl.

The logic is a bit more cumbersome but shouldn’t be bad.

-Todd

> On Dec 4, 2015, at 9:15 AM, Jordan Rose <notifications@github.com> wrote:
>
> Hm. Is it possible to make the build-script-impl-only options go away in all the common cases? I'd rather keep all the logic up in build-script and leave build-script-impl as a low-level thing. (Which we eventually want to redo in Python, so that we're not crossing language boundaries for silly reasons.)
>
> —
> Reply to this email directly or view it on GitHub <https://github.com/apple/swift/commit/02a493b8380bbcb5c4bf2e123db0b6d79c95dc8f#commitcomment-14792238>.
>


Killing time on the train, so pushed 8c89a761b52151c154d16e8f73903f3b6cd6d28a which takes support back down to `0.8.0` and improves the `MetaData` tests.


Thank you!


you can choose to merge this pull request or not


it's not the same. different generators.


それでいいと思う


(I should note that this was really meant to be a stop-gap before I added ReleaseDebInfo build support to the Swift LLDB build).

-Todd

> On Dec 4, 2015, at 9:44 AM, Todd Fiala <tfiala@apple.com> wrote:
>
> Possibly.  That was my original thought, but I didn’t want to make the logic overly complex.
>
> That route basically says “compute everything you’re going to send to build-script-impl, and right before doing it, do the check on those arguments.”
>
> That will work, but only as long as there isn’t yet another path to get to build-script-impl.
>
> The logic is a bit more cumbersome but shouldn’t be bad.
>
> -Todd
>
>> On Dec 4, 2015, at 9:15 AM, Jordan Rose <notifications@github.com <mailto:notifications@github.com>> wrote:
>>
>> Hm. Is it possible to make the build-script-impl-only options go away in all the common cases? I'd rather keep all the logic up in build-script and leave build-script-impl as a low-level thing. (Which we eventually want to redo in Python, so that we're not crossing language boundaries for silly reasons.)
>>
>> —
>> Reply to this email directly or view it on GitHub <https://github.com/apple/swift/commit/02a493b8380bbcb5c4bf2e123db0b6d79c95dc8f#commitcomment-14792238>.
>>
>


No need for `space_guid` as the URI contains the guid of the space you're searching.  Yet another doc failure.


ここのヌルポで死んだことがある気がするが、再現コードは思い出せない。


[this is not about this code, it's a metacomment] @mhvk I think you commented on this on my fork?  I'm kind of confused.  I wonder if you got notified of this after I rebased & pushed this branch?  Otherwise, maybe I'm doing something wrong here


Ainda falta mudar a classe gerenciador de conexões!!!


so 0xffffffff is overflowing on x86. Why not just use -1 here? Or am I reading this wrong?


I believe browsers intern most short strings - definitely worth exploring!


Nit, do you think this class belongs here or in TableInfo?


As I see it, what you're suggesting here implies:
1. keep maintainer's life easy, and user's life hard
2. keep ~~wasting time~~ "maintaining this code" each time fortigate IOS increases cookie size....


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8085](https://teamcity.mesosphere.io/viewLog.html?buildId=86491&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Execution timeout Build time: 01:00:07


いまクライアント側のメインページのデザイン考えてる
出来たら載せるよん


This commit requires a regenerate_and_update.sh run


Yes i will, lets just wait for Marc to update the debian/changelog file,
like I mentioned in #355 ;)
On 4 Dec 2015 18:42, "monsieurp" <notifications@github.com> wrote:

> hi @KLuka <https://github.com/KLuka>, could you please create a new tag
> as well? Thanks a lot.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/shellinabox/shellinabox/commit/8a68194da2fba5b0931ab3bbd37f94c91b42fde0#commitcomment-14792807>
> .
>


Should be a `List<RuleEntity>`.


I didn't see that commit until today…
That's a shame, really.

My company is the original author of the code and we worked with @marcosgdf  to get it integrated upstream: #2538
You seem confused by this feature and I was also confused by the units fields in Dolibarr when doing it, so I can relate to that.

But, at the end of the day, the use cases are very different.
The existing informations on the product card are mere properties. They tell the weight, size or shape of the item. Very useful for packaging and shipping except they don't tell the quantity unit used to sell/store them.
This feature does.

The implementation relies on a unit dictionary to be extremely flexible and handle edge cases in a nice fashion.

The information can then be issued in commercial documents such as proposals, invoices and used for the storage of the products.

Let me take an example to try and get my point accross:
- A bucket might be 5 liters but is sold as a single item.
  - I'd put 5 L in the volume field of the product card and say this selling unit is item.
  - When I sell 10 buckets, this amounts to 50 L but this information is irrelevant.
  - The relevant quantity printed on the document is 10 items.
- I sell cable, this is sold by the meter, but it's a huge submarine cable that weights 100 Kg per meter
  - I'd put 100 Kg in the weight field of the product and say the selling and storing unit is "linear meter".
  - When I sell 100 meters of the cable, this amounts to 10 tons bug, again, this information is irrelevant for the sale process (It's obviously useful for packaging and shipping though…).
  - What the printed document would state is a quantity of 100 linear meters which is the information salesman and customers alike need.

As we saw, the two features may look like  they have a bit of overlapping but are not mutually exclusive.
The use cases are really relevant and this was sorely missing from Dolibarr.

Please re enable the feature or at least hide it behind the experimental flag.
Completely commenting it was very rude of you and makes me sad :(


Fejlen ser ud til at ligge i en manglende .jar, hvori driverens kode ligger. Denne skal bare tilføjes til projektet og så burde det virke :+1:


I mean move neighbouring tile iteration to int3, (except pathfinder).


What difference does that change make? Didn't the deferred closure trigger?


@dpgeorge Actually the high speed stuff wasn't for rshell, it was for talking to bioloid servos: http://forum.micropython.org/viewtopic.php?f=5&t=1189

rshell over a UART talking to an sdcard was also an issue (but the testing I was doing for that was at a more sedate 115200 baud).

I don't see any way around the reentrancy problem given that we're using synchronous I/O.

There is still the potential for issues (like we uncovered with @blmorris and doing file I/O from a DMA callback).  I think your patch is a reasonable short term fix.


Isn't it better to move make it like this:

 ret = pb_write_one(img_from_set(imgset, CR_FD_MM), &mme, PB_MM);
+if (!ret)
+    ret = task_reset_dirty_track(pid);
 xfree(mme.mm_saved_auxv);

Additional label complicates error handling path.


Is there any reason that applying this change to 2.4.10 shouldn't work? I tried and saving the price on the edit screen still isn't working.


How often will this happen? If this isn't some kind of error path, we probably shouldn't be logging.


No longer supported in bootstrap 3

Steve
--
Als ik kan

> On Dec 4, 2015, at 12:16 PM, Jared Dillard <notifications@github.com> wrote:
>
> where does it say they are deprecated?
>
> —
> Reply to this email directly or view it on GitHub.
>


Same question as above.


Maybe your issue is unrelated...


@jlirochon Why? No one can be exact 2meters height, right? And 1.62 height can let player jump a little bit in 2block-height mines and it won't scare claustrophobia people. lol


Nit, should this be abstract and maybe protected?
If so, I would make `public T build()` abstract.

Also, should `BaseTableInfo` be abstract (and `toBuilder`)?


Is a super hack but as long as is isolated, clear for the users, easy to remove, and most important fixes a error that is causes by wrong emulation, I don't see why it cannot be added.


@chriseidhof  When we make changes to the internals of the standard library we need to consider the impact of the change on the performance of Swift programs.  In many cases the swift optimizer can handle some patterns but not others.

Before you commit any changes like this you need to measure the performance of the generated code. If you think that this is a good change then please write a test program and benchmark your change and show that this is a performance win.


"OTICE" instead of  "NOTICE" ?


This commit and next one (Remove `SplashActivitiy`) can be squashed.


мы так не делаем. все договорённости описаны здесь:
https://github.com/ngc696/PromProg_Race_CardRedactor/issues/1


Oh, didn’t think that could be misunderstood. Yes I ment that we exceed it. And yes the limit is 200. I just stated that we use 250. Okey, I’ll rephrase it so it can’t be misunderstood.


I've remembered why I did this, to ensure that "private type in public interface" is indeed a warning and not a breaking error.


This can be squashed with c1e463b7d4d69a35834fbb59fe0c3cd5ba56a20c.


Thanks @dhacker29 , but please, can you fix Browser on downloads ?  When you try to download something, the browser is crash quickly !
Best regards !


Doc failure again.


:). In fact in the old system the RecvStream closed the socket, so the defer here was useless. Now that WebsocketMirror sends a TextMessage when it's done instead of closing the socket itself, we need to close it explicitly. (We need this because we mix and max WebsocketRecvStream with WebsocketMirror in lxc/lxd.) We could do this in WebsocketRecvStream as soon as we get the TextMessage to keep it self contained if you want, but then you could only ever use WebsocketRecvStream to receive one stream.


Oh, I see that `StreamingBuffer` is also relevant to `External`..? If so, ignore my comment above.


Use the daemon from the storage struct please.


Not an error path, just means the end of stream. It's essentially like CloseMessage.


I put it here because it's also used by ExternalTableInfo


This is how we mark streams as being done so we can reset and send another stream over the same websocket.


Ok, I'll dig deeper. I'm not sure what the server is running but the symptoms are the same as the issue this fixed. Saving in QuickEdit works, but not on Edit.


**[unitTests_php_branches run failed](http://qa-s2.wikia-prod:8080/job/unitTests_php_branches/23951/testReport/) for this commit**


Drop the empty line :)


Then why is it in bootstrap.min.css which is v3.3.4?


Now i See!


Use container.Path()


xz doesn't compile on Windows out of the box, because there is a mismatch between the 64-bit compiler (MinGW) and some hand-tuned 32-bit assembler sources.


I think Google's material design guide lines for icons makes simple icons look the best.

https://www.google.com/design/spec/style/icons.html

Maybe you an find someone with photoshop that can update the icon to match the spec?


Please drop this


I think the parent's equals will work for all (because of the `toPb`), however if you think that is not the case then we should probably only have the hashCode/equals in the children.


We can't. The type here is `container`, so we can only get an abstract `Storage`, which doesn't export the daemon.


В файле ещё много ошибок, но выкладываю для того, чтобы понимать как всё будет работать, к тому же этот файл ещё нужно будет объединить с остальными.


**[unitTests_php_branches run failed](http://qa-s2.wikia-prod:8080/job/unitTests_php_branches/23952/testReport/) for this commit**


Please drop this function.


Use `isPresent(namespacePrefix(lcName))` instead of checking against svg and math...


Nit, here (and above). I don't think overriding is necessary.


Remove `(they can nt have content)`


`bunyan-logentries` should be in optional dependencies


Not sure: this error is not supposed to be handled in runtime, one would have to fix their environment.


It turns out, it's both: https://github.com/nodejs/node-gyp/blob/2ac7de02c42654e4e80e346e5d560f7cc01d4553/lib/process-release.js#L15


Nit, see my other comments about the double-checking.


lgtm


Also added a collision box to the UfoMesh


This server was replaced by de-ns1.de, http://79.133.37.92/dnscrypt/


LGTM.


Why?


As this affects a normative requirement I'm reluctant to apply it as editorial. Please bring it up separately on the mailing list.


All the tests run after my change but this one, I'm looking at fixing it now, any guidance would be appreciated.


The spec says svg and math


@suryasev don't forget to handle errors in `receive`


Gotcha. Let's remove it, then.


also it's spelled wrong "uswgi" :)


I believe the "any" is intentional.


This is to address #53


I did not make them abstract to use them in `listTables` that returns partial information on tables, not enough to say whether they are simple tables, views or external tables. I accept ideas.


Wait... it's had already been removed :)


This is intentional.


:+1: Thanks for reverting this shit.


pass params[:user_role]. Remove :student and :admin from form.
and add here like
```
@user.add_role params[:user_role]
```


Maybe we could rather read a version from the `package.json` using something like `cat package.json | json version`.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8097](https://teamcity.mesosphere.io/viewLog.html?buildId=86547&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 205 Build time: 00:05:04


Hmm, fine then, let's do it like that for now and I'll send a branch which makes daemon a global variable and then rip it out of everywhere because that's just getting ridiculous :)


what error message?, I think that we need know the text  of error message for the doing assert.


My comment was just an information to the server users.


Fixed #39


Also your commit title and message are not accurate.

mem: reset SOFT_DIRTY bits after dumping of all vmas in the process

Currently CRIU resets SOFT_DIRTY bits immediately after dumping of anonymous private memory. Anonymous shared memory dumping is performed later. So SOFT_DIRTY bits are all zeroed at the time of anon shared mem dumping. This is invalid behavior if we want to track changes in anonymous shared memory.

This patch changes SOFT_DIRTY bits reset moment. Now SOFT_DIRTY bits reset is performed after dumping of all  VMAs in the process.


Because it's pretty much the only place in the whole code base that a function begins with an empty line :)


Please fix both issues and send me the link.


shouldn't this be in else? since checkPrefix won't start with java or javax


On Fri, Dec 04, 2015 at 10:04:38AM -0800, Stéphane Graber wrote:
> Hmm, fine then, let's do it like that for now and I'll send a branch which makes daemon a global variable and then rip it out of everywhere because that's just getting ridiculous :)

Yeah, I agree. Abstraction for the sake of abstraction in some places
here.

> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/tych0/lxd/commit/5de5bd6df9ea05b7def878a620f9c17d115eed89#commitcomment-14793300


Or the player could spawn in the air, at optimal height, so than when he falls he doesn't die immediately, but he'll be soon killed by a random mob. But for this to happen, we need mobs first :cow:


add here `:user_role`


I love it, you churlish, weather-bitten mumble-news!


Nah, that's fine, it's just annoying because we're using defer on all the other websockets in Exec.


Didn't check if it is working or not.


what is it ? `fffff`?


out of curiosity, why do you kneed to do this?  It seems like we should use all relative imports within flopy.  Otherwise, we may end up importing an installed flopy module, instead of the one in this set of flopy files.


On Fri, Dec 04, 2015 at 10:05:18AM -0800, Stéphane Graber wrote:
> Because it's pretty much the only place in the whole code base that a function begins with an empty line :)

Yes, I know that you've removed them in a lot of your other patches. I
don't like it that way, which is why I do it the other way. In general
I don't like whitespace discussions, so I've been avoiding commenting
on them in other patches. However, I dislike making whitespace changes
in reviews even more. If we're going to start having a policy about
stuff like this, can we please talk about it and write it down
somewhere as opposed to just whatever one person feels looks the best?
I'd like to avoid stuff like this in the future.


What I've discovered is that DFU goes and initializes a bunch of the hardware, but doesn't restore things when it quits. So entering the code from a hard reset has the hardware completely uninitialized, while entering the code after a DFU session has some of the hardware already initialized.

One of the issues I ran into was related to the UART on the M7. DFU initialized some bits which affected the baud rate, but the HAL code didn't use those bits and assumed they were in their HW reset state, which caused an incorrect baud rate to be used.


nnhj


mm


After the update has been broken one of my scripts. He began canceling ability when cast,


It looks like preferred practice in this project to remove old feature and leave tons of unused trash in project.  I don't like that style.

Here is remove of outdated AI code: https://github.com/freeorion/freeorion/pull/414


Looks like we've been logging in similar cases in the websocket code, so fine for now. I've got a massive logging rework planned soon where this may change a bit (or at least get a bunch of context added to make it useful).


Yeah, let me think about it over lunch. There may be a way to make this a bit nicer if we are a little clever about how we close things on the server side. That said, being clever here has gotten us in trouble before, so maybe it's best just to be dumb and ugly. Anyway, I'll give it some thought.


This is what actually fixed the issue. The other changes were just normalization intended to root out the issue.


What did you study after all? I alway thought it's easy to get a job after graduating...


Yeah, I find this is useful for debugging such things, though. Perhaps we can rework things to not all be at the same info level? :)

Another option would be to turn on debug mode for certain parts of the code.


@JungMinu ... you've been doing amazing work so far. It's definitely very appreciated.


Only a partial close as code is messy


If for perf reasons, I think this is OK since `buildQuery` on mutations is not a very hot codepath. If for ‘not blowing up in production’ reasons, I'd still like to leave it this way since it's probably better to fail loudly rather than to just-not-work.

OTOH I'm hoping we can get rid of this whole thing soon: https://github.com/facebook/relay/issues/615


This work is licensed under a
<a rel="license"

To the extent possible under law,

https://www.youtube.com

has waived all copyright and related or neighboring rights to

copyright all
.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8099](https://teamcity.mesosphere.io/viewLog.html?buildId=86559&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 2 (new) Build time: 00:02:07


Then don't waste brainpower on it. You already added jpeg, which is all we need. Sorry for the confusion.


Why add the xor function? Pretty sure haxe allows a ^ b. I'll look at the rest in a sec.


nit: s/<replace>/${WORKER_IP}

This was my own bad example, but since we talk about WORKER_IP already, may as well describe it in the command.


Hi , I am very interested in your work.
Did you intend to share this module source code soon, or do you work on it yet ?


Here are my commands:
```
git clone https://github.com/nsoranzo/galaxy.git
cd galaxy/config
cp galaxy.ini.sample galaxy.ini
cd ..
sh run.sh
CTRL-C (after server started)
sh run.sh
```


We should keep this sample file in as an example for people cloning the repo fresh


This is rasterized.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8088](https://teamcity.mesosphere.io/viewLog.html?buildId=86507&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Execution timeout Build time: 01:00:09


it's ok


You should also run
```
git checkout dev_verify_tools
```
after cloning and moving inside the git repo.


Would prefer this to be `false` by default.


@blair1618 https://github.com/tangrams/tangram-es/blob/master/core/src/scene/styleParam.cpp#L151-L157 should have taken care of family name being all lower case.


Why not `===` for the comparison to `"object"`?


My general thoughts about your implementation:
1. make `private let ...` a `private static let` and begin with capital letters
2. make instance methods a class methods (add `class func`)
3. change `func getImageFromDisk` to `func cachedImage(..) -> UIImage` - user should generally don't care where those image are from, so `getImage*FromDisk*` tells user that it is from disk (obviously), and I absolutely shouldn't care about it. It's so called *implementation detail*
4. Because of point 3, I would also suggest to hide `func getImageFromDisk` and `func saveImageToDisk` by making them `private`. The question is will you ever care to check cache before asking API? I think we just want our image and that's it :)
5. change `func getImageFromUrl` to `class func imageForURL` - the difference is that user will have to know that this image will `GET` *from* url. Also URL is abbreviation so it should be capitalized imo. I would love to not reveal how we will get the image (cache or API) for the user, so that we will provide the image for a given URL by executing the callback
6. You can go further with point 4 and make a `private` nested type, something like `private class FileCache`, and put everything related to the cache there.

Don't get me the wrong way, it's not criticism, but suggestion. Your implementation is fine, but it can be improved


Just curious.
Why is it important that pvp is enabled by default for saving a player to list?


Nice that you check data length, but instead of optional value you can use `downloadedData.length > 0` :+1:


Indentation is wrong


@pattacini: There were some calls to ARE with `shouldWait=false` ..
@AnneLaureM @gregoire-pointeau: Please check whether this change gives you any trouble. Now, by default `ARE` always is called with `shouldWait=true`. From the code, I don't think this will be a big deal.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8089](https://teamcity.mesosphere.io/viewLog.html?buildId=86510&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Execution timeout Build time: 01:00:18


@AnneLaureM @gregoire-pointeau @pattacini: See 7d0a394


I think you missed completion call in case nothing was downloaded. No chance for the use to recover from this situation


If you would follow my advices, you wouldn't need an instance here


You're looking at an outdated commit. Use the files page for the latest.


I think this should be `self.__relationship_types = self.__client.relationship_types()`


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8091](https://teamcity.mesosphere.io/viewLog.html?buildId=86512&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Execution timeout Build time: 01:00:09


About the relativeness, I suppose its the current working directory, but that should be the current file's directory.
It is evaluated once per format. Generally speaking I prefer things to be as dynamic as possible. In this case the upsides aren't that big, but still, config files can move or be created/removed. It shouldn't have any performance impact, as its a simple check compared to executing the formatter. If you can show that it does have significant impact, then this may have to be changed.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8100](https://teamcity.mesosphere.io/viewLog.html?buildId=86564&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 205 Build time: 00:08:49


Thanks @Tobias-Fischer for spotting this.
Actually, compilation of `lrh` doesn't get enabled by default on my machine.


I see, thanks.

Quite a large commit.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8103](https://teamcity.mesosphere.io/viewLog.html?buildId=86576&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:02:27


Thanks. This is a vestige from some previous work. I'll push over it.


Maybe the following will be enough:
make[1]: Entering directory '/build/zimg-git'
make[1]: *** No rule to make target 'vszimg.c', needed by 'vszimg.lo'.  Stop.
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory '/build/zimg-git'
Makefile:2708: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1
make[1]: Entering directory '/build/zimg-git'
  CXX      src/zimg/api/libzimg_la-zimg.lo
  CXX      src/zimg/colorspace/libzimg_la-colorspace.lo
  CXX      src/zimg/colorspace/libzimg_la-colorspace_param.lo
  CXX      src/zimg/colorspace/libzimg_la-graph.lo
  CXX      src/zimg/colorspace/libzimg_la-matrix3.lo
  CXX      src/zimg/colorspace/libzimg_la-operation.lo
  CXX      src/zimg/colorspace/libzimg_la-operation_impl.lo
  CXX      src/zimg/common/libzimg_la-cpuinfo.lo
  CXX      src/zimg/common/libzimg_la-libm_wrapper.lo
  CXX      src/zimg/common/libzimg_la-matrix.lo
  CXX      src/zimg/depth/libzimg_la-depth_convert.lo
  CXX      src/zimg/depth/libzimg_la-depth.lo
  CXX      src/zimg/depth/libzimg_la-dither.lo
  CXX      src/zimg/graph/libzimg_la-basic_filter.lo
  CXX      src/zimg/graph/libzimg_la-filtergraph.lo
  CXX      src/zimg/graph/libzimg_la-graphbuilder.lo
  CXX      src/zimg/resize/libzimg_la-filter.lo
  CXX      src/zimg/resize/libzimg_la-resize.lo
  CXX      src/zimg/resize/libzimg_la-resize_impl.lo
  CXX      src/zimg/unresize/libzimg_la-bilinear.lo
  CXX      src/zimg/unresize/libzimg_la-unresize.lo
  CXX      src/zimg/unresize/libzimg_la-unresize_impl.lo
  CXXLD    libzimg.la
make[1]: *** No rule to make target 'vszimg.c', needed by 'vszimg.lo'.  Stop.
make[1]: Leaving directory '/build/zimg-git'
Makefile:2708: recipe for target 'install-recursive' failed
make: *** [install-recursive] Error 1
-------------------------------------------------
Building of zimg-git failed...
Delete the source folder under '/build' and start again.
If you're sure there are no dependencies <Enter> to continue building.
Close this window if you wish to stop building.


Was just about to submit a PR for this (with a test :wink:) - can we get this tagged so it can be installed as I'm currently experiencing an issue with this :)


Yes, this is a bug I introduced with the last commit where I replaced `grep` with `diff` which I believe have inverted return code logic.


TeamCity LabKey :: Trunk :: Premium :: Git sqlserver 2014 [Build 82](https://teamcity.labkey.org/viewLog.html?buildId=289494&buildTypeId=LabkeyTrunk_GitSqlserver2014) outcome was **SUCCESS**
Summary: Running Build time: 00:01:51


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8101](https://teamcity.mesosphere.io/viewLog.html?buildId=86565&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 1, ignored: 205 Build time: 00:11:05


I know that it might seem bogus, but in order to keep uniformity in the code, the right thing would be to revert e3c299db7b564b and leave the rest the same.


Mark deprecation please


> Yes, this is a bug I introduced with the last commit where I
> replaced `grep` with `diff` which I believe have inverted return
> code logic.

Cool, that would nicely explain it.


That said, unit tests are failing after this, because I suspect that rsync error handling is wrong.


Ah, new bash tricks, proudly presented by @haguenau .


TeamCity LabKey :: Trunk :: Premium :: Git sqlserver 2014 [Build 83](https://teamcity.labkey.org/viewLog.html?buildId=289498&buildTypeId=LabkeyTrunk_GitSqlserver2014) outcome was **SUCCESS**
Summary: Running Build time: 00:01:54


Should we leave readUltrasonic() in this file or move it to its own? It is used in findCandle(), driveStraight() (this one), and I think that's it. I think we can just leave it here.


#44 has been merged! :)


It's not really important, it's just a way to avoid saving every single player and end up with a file with hundreds of players. This way if the player has PvP equal to the default, i don't save his data since... well it's already default, no need to save it.


Whatever is in loop needs to be put into its own function so that this file can be imported by the main file, findCandle.


Looks like this like is not needed here.


develop (Myoldmopar) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1442 of 1442 tests passed)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.svg) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.svg) ![Coverage Badge](http://img.shields.io/badge/coverage%20status-70.51%25-green.svg)


TeamCity pull requests :: netty [Build 789](https://garage.netty.io/teamcity/viewLog.html?buildId=3795&buildTypeId=pulls_netty&guest=1) is now running


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8092](https://teamcity.mesosphere.io/viewLog.html?buildId=86520&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Execution timeout Build time: 01:00:08


Even though this doesn't hurt we may get rid of U-Boot in that configuration because we don't use U-Boot in that particular testing.


Ej ale gównianie to zamieniłeś z tym żartem. Teraz to nie ma sensu w ogóle. Przecież grecki znak zapytania to średnik i to nawiązywało do "średniki Ci nie straszne". a teraz ni w kij takie coś. Tak samo w komentarzach w kodzie było "kod jest dobrze okomentowany" to zmieniłeś na dokumentowany, co w ogole traci sens w takim kontekscie.... spoko literówki, spoko interpunkcja itp. ale sens zdania zostawiaj...


@pcbro Line 69 still contains a use of .Master so this test no longer builds successfully.


Correction: should be "head.ejs", not "head.ejd"


the summery is now xml passed through xsl into the index.html guys *


> Ah, new bash tricks, proudly presented by @haguenau.

That's really much the same as quoting `$@`: should be safe.

    $ (HARRY=(cray\ on show$'\n'stopper goo); for f in "${HARRY[@]}"; do printf "f = \`%s'\n" "$f"; done)

    f = `cray on'
    f = `show
    stopper'
    f = `goo'


Are we tracking visible layers [twice] (https://github.com/geomoose/geomoose-js/blob/master/geomoose/geomoose.js#L515)?  Are the HashTrack extension and getBookmarkUrl two similar ways to do the same or similar thing?


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8104](https://teamcity.mesosphere.io/viewLog.html?buildId=86578&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 2 (new) Build time: 00:00:48


Yes, seems so. Adding this step got a bundled font file to load correctly last night, but I'll check and see; maybe it was just a coincidence. If the bundled font works without this step then I'll remove it.


Wir haben dein Hoare Kalkül geprüft und sind mit deiner Lösung einverstanden, sieht gut aus!
Weiss allerdings nicht wofür das roc jeweils am Anfang und Ende auf dem Pfeil steht..


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8105](https://teamcity.mesosphere.io/viewLog.html?buildId=86579&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Exit code 2 Build time: 00:00:46


I believe "local" is a bash extension. That's okay but please change change the shebang header to #!/bin/bash.


TeamCity OSS :: Kubernetes Mesos :: 4 - Smoke Tests [Build 8093](https://teamcity.mesosphere.io/viewLog.html?buildId=86521&buildTypeId=Oss_KubernetesMesos_5SmokeTestsDockerMesos&guest=1) outcome was **FAILURE**
Summary: Execution timeout (new) Build time: 01:00:09


Has this been done manually/on purpuse? I've had issues with this specific attribute while building on Windows.


My degree is in Business Tech Administration, an analogue of Information Systems. There simply aren't enough good jobs to go around for every person.


Looks clever.


Sieht gut aus. Hatte bei den Überprüfungen der boolean-Werte an ein paar Sachen nicht gedacht. Hast du noch irgendeine Idee für d?


This isn't available in the version of arcutils specified in setup.py. Should I change setup.py and install the latest version?


LOL los CName es del DNS