You're missing some values in drinkorder:
    time_complete timestamp with time zone,
    bar_id integer references bar(id),
    comments text

Also, in mock.sql I noticed you're missing the categories table which is referenced in the ingredient table.
Not sure if that helps.


Shouldn't the P in Skillproficiency.php be capitalized?


cool thanks


The test which broke was about embedded admin. It did not match the regex when you commited your changes, but it does now.


This is supposed to be *the* configuration of the frontend. The fact that the configuration is generated from buildout in development is not relevant at this point.


MakeDegreeDaysConsistWithASH901 (JasonGlazer) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed, 0 test warnings)

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


kkk


Are we only interested in statistics at the first backup?


Shouldn't the C in VacancyCategory be capitalized?


Added to http://contrib.xwiki.org/xwiki/bin/view/Main/#HForxwiki-contribGitHubAdmins


Comparing of old epb and a new one can be done in this thread. It can (and, IMHO, should) be done internally, so callback is called only for really happened events. Requeue also can be done automatically in client library without further actions from user application. That's why I said that not only there is no point to backport this commit to 3.0, but crap from 3.0 should be deprecated and replaced with new calls. May be with something similar to Oracle's publisher-subscriber API.


@mosic as per api's end public/cameras end point [Line](https://github.com/evercam/evercam-api/blob/master/app/api/v1/routes/public_routes.rb#L107) we are getting public cameras as PUBLIC and DISCOVERABLE= true. are these relevent?


^^    #tropSpeed


This code was a highly experimental branch, which I only pushed, so people can have a look at it. I would neither recommend merging it into your work, nor would I want to merge it into the master.


Именно так


I would combine the two rsync commands into one, where the --link-dest part is injected into the OPTS variable.


Hi

First of all, congrats for the work you did on Axis. It is really good!

Actually, I did not know about the wiki. My contract is over now but may be in the future I might need the wiki again. Thanks.

Chrislain


代码评价注释


My master is a little out of sync.  Although the .sql file had to be added, my version.php says I have 4.3.1-dev and $v_database=159, so I increased it to 160.  Hope that is correct.
Committed:
https://github.com/ophthal/openEMR_2/commit/251d508c9515c774e5c9859a7b56dff6edb1807c


hahaha lol :D


The only purpose of this experiment was to see, how *fast* one could calculate these numbers. But speed is not at all our main goal. Readability is much much more important.

So the code should be easy, and short where possible.

At least this is my opinion.


eeeeee( @vasylhoban


That commit


може краще var result = {};
щоб якщо спрацює кетч повернувся пустий обєкт а не андефайнед @vasylhoban


On 03/29/2016 03:04 PM, Dimitry Sibiryakov wrote:
> Comparing of old epb and a new one can be done in this thread. It can (and, IMHO, should) be done internally, so callback is called only for really happened events. Requeue also can be done automatically in client library without further actions from user application.

 From what place?

> That's why I said that not only there is no point to backport this commit to 3.0, but crap from 3.0 should be deprecated and replaced with new calls. May be with something similar to Oracle's publisher-subscriber API.

Ok, please suggest them and we will take a look how can it be
implemented in our case.


why no initial / ?


TeamCity Glyssen :: Glyssen-master Continuous [Build 0.100.7.0a485c9f81731a801d4292a7797c5fca69a54a60](http://build.palaso.org/viewLog.html?buildId=70800&buildTypeId=bt431) outcome was **SUCCESS**
Summary: Tests passed: 1063, ignored: 13 Build time: 00:11:49


Are you still using the same .vimrc ? Can you please update it ?


@ijunaidfarooq In general yes, but for the thumbnails it doesn't matter if the camera is discoverable or not. The only important information there is if it's a public camera - if it is, the thumbnail works without api credentials, if it's not you need to provide valid api credentials.


My guess would be that the tvos target of that project doesn't work with Carthage. I don't think that it used to have tvos support so maybe it's just a setting problem in their project.


«mew» release? )))


My helloworld is used to show "helloworld" in the computer languages I have learned!


Unfortunately, I have only implemented a basic access to VOT database
(frames data and GT info). If you are interested in tracker algorithms
scoring and metrics, I would recommend you to see:
http://cvlab.hanyang.ac.kr/tracker_benchmark/index.html

On Tue, Mar 29, 2016 at 1:06 AM, Eric Zavesky <notifications@github.com>
wrote:

> @Auron-X <https://github.com/Auron-X> This is a great way to evaluate
> performance on VOT. Did you have corresponding scoring and/or other test
> harnesses in mind? I'm wondering about automated scoring both for VOT and
> other internal datasets that I have.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub
> <https://github.com/Itseez/opencv_contrib/commit/1e7d9e0548ec8fd2e6109bf7ab351124c5f2ea91#commitcomment-16864339>
>


is this finished?


Main script starts here


> From what place?

From background thread, of course. It is safe as long as it can acquire connection mutex. To avoid deadlocks, waiting for the mutex can be done with timeout or be joined with waiting for packets.

>  please suggest them

  Will do that in devel list.


Maybe defining `ZMQ_NULL` such as it resolves to `NULL` on old compiler and `nullptr` to compiler supporting C++ is the way to go.


Windows Changing File mode? I don't know. I think my OS X did that. Sorry.


**[unitTests_php_contractual_responsibilities run failed](http://jenkins.wikia-prod:8080/job/unitTests_php_contractual_responsibilities/1863/testReport/) for this commit**


**[unitTests_php_contractual_responsibilities run failed](http://jenkins.wikia-prod:8080/job/unitTests_php_contractual_responsibilities/1864/testReport/) for this commit**


hello


Thanks for poking me about this. Recorded in https://github.com/luismbo/cl-travis/issues/17


in the beginning BooleanOperations did:

* check / match complete contours
* check / match segments
* check / match remaining parts

the middle part, matching segments, didnt work as expected. This could be improved. But this is more complex then the first draft Tal and I wrote. The direction can change, start and end points can be different (even for the same input segment)

The last check already doest those checks, rather fast.

gr Frederik
www.typemytype.com

> On 28 Mar 2016, at 01:08, Cosimo Lupo <notifications@github.com> wrote:
>
> this function is 310 lines long... I just can't hold it in my mind all at once. Maybe I'm just tired...
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub <https://github.com/typemytype/booleanOperations/commit/d699af0e2e0af276088d49e5122aada49cdd4506#commitcomment-16859129>


Guess this should be done also for the categories/tags metabox. Will handle it in the branch for #4053
and #4149 if no objections.


ой


should this really be static?


Are you spying on me ? :D I was testing something with branches and merge.


Looks good. One comment: The Whetstone bridge is for the magnetic counter/sensor (not level sensor).


Added: Header section of the site


cout<<"hello"<<endl;


On 03/29/2016 03:15 PM, Dimitry Sibiryakov wrote:
>>  From what place?
> >From background thread, of course. It is safe as long as it can acquire connection mutex.

AST should never wait on mutexes.

> To avoid deadlocks, waiting for the mutex can be done with timeout or be joined with waiting for packets.

And as soon as we start to talk about timeout to avoid deadlocks....
sorry, I do not like this suggestion.
Always comes old question - what should it do if timeout happened?


yes, I was a bit excited since It works in first try. I forgot to remove this line.


Invalid URL in what way. Do you have an example?


Sure! thx


Yes, something like that.


@frs69wq Could you, please, help with this issue when I run TracingTest.java of tracing package.
```
# Problematic frame:
# C  [libsimgrid.so+0xb2366]
#
# Core dump written.
```


Modification du ReadMe


What does it look like???


Not me bro, my github :cry:

![capture du 2016-03-29 14 22 27](https://cloud.githubusercontent.com/assets/3015402/14107845/9ad44108-f5ba-11e5-8074-cda7814db763.png)


Why you don't use results of TryParse? If you don't use it, maybe it is unnecessary,


then it still should be fine - it must only be the same as if the admin would have been defined in xml / yaml


this is the first change made in readme file by aman gupta


Très bien lol


An alternative way of converting seconds to a human-readable format:
```
date -u -d @${RUNSEC} +"%T"
```


my first comment


hehehe c++


The reality is that we'll always have users in older environments, and we can't just abandon them. There's an issue open right now from a user that needs libzmq on SunOS 5.10, released 11 years ago!

The problem with defining our own ZMQ_NULL that depends on the environment is that nullptr is actually useful in templates definitions, overloaded function prototypes and so on. So you can't just arbitrarily change the signatures, as that will break the ABI depending on the build environment, which is unmanageable.


this looks interesting :D


When you had that crash when braking a barrel the other day, the item you had inside it, was it a barrel ?


> AST should never wait on mutexes.

   May be, but it is not a real AST, it is just another background thread that do
something. It can do anything that application's background thread can do. Including FB
API calls that will wait for attachment mutex.

> Always comes old question - what should it do if timeout happened?

   Check for new event has arrived if not something like WaitForMultipleEvents() is used.
Then wait some more. That's how waiting for several things at once used to work, no?..


Comment your code!


MakeDegreeDaysConsistWithASH901 (JasonGlazer) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1063 of 1063 tests passed, 0 test warnings)

![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-32.55%25-green.svg)


You made everything a comment. Comment your code.


@ins0m Please try `1.3.9_1` and let me know if that works for you


MakeDegreeDaysConsistWithASH901 (JasonGlazer) - x86_64-MacOS-10.9-clang: Tests Failed (1618 of 2171 tests passed, 0 test warnings)

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


You need to be more specific about what you tested and how. And by the way, commenting an unrelated commit is not the right way to go. Please open an issue to discuss about issues ;)


You might want to call it something like "ATXFrontPanelGPIO" or maybe just "FrontPanelGPIO" and have a link to "http://www.intel.com/content/www/us/en/support/boards-and-kits/000005643.html"?

Took me a while you didn't mean case as in "switch / case statement" but as in the metal box you put the board in :).


The categories table is okay to be missing. The way this works is create.sql is ran first. In create.sql the categories are added because we are keeping a static number of them. mock.sql is used for unit testing only.


USE THE ITEMCUSTOMSWORD AND MAKE OVERLORD SWORD EXTEND IT


fixed in be7e02fc83bb289b945c6ed099498f502812fcc5


switches


MakeDegreeDaysConsistWithASH901 (JasonGlazer) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: Tests Failed (1637 of 2209 tests passed, 0 test warnings)

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


MakeDegreeDaysConsistWithASH901 (JasonGlazer) - x86_64-Linux-Ubuntu-14.04-custom_check: OK (0 of 0 tests passed, 0 test warnings)

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


!important kullanmamaya dikkat et


ayni sekilde important'a gerek yok


why freeze?


Okay, I've seen some examples using the --delete flag, but maybe they were mistaken. You know this from experience?


Why private?


@a0viedo what is the actual need to have a `description` property instead of a `message` property as the standard Error object?


Just some small string changes.


thank you for reporting the bug and thank you for taking the time to offer a solution!


```
for(MenuItem mi : this.menuItems) {
    menuText.append(String.format("%1$-" + 10 + "s", mi.getKey().getKey()) + mi.getKey().getText());
    menuText.append("\n");
}
```


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


I know this is not really part of your change, but I don't want to change this now as there will end up being merge conflicts.

We should only send to CP when the settings is enabled. if it's not enabled we should still approve the movie.


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


Согласен. ОК


First line - need to change to heading


@mosic I needed it because if a camera is public and discoverable ,it gives a different thumbnail_url than a camera is just public.

But right now I tested it again and it seems this is useless,So I'm removing it now.


Awesome ))) Really easy to read. uri from initializer and url from method params.


Removed some legacy copyright information, no longer valid.


Only 1 method call of this object. Why not in the initializer?


I just verified this on the test machine.


Наверно просто с объектом. Прсто кидать его не на все а только на первый неверный параметр


u wot m9?


Results are used actually. They're passed to ViewModel via CanExecuteRoutedEventArgs.


Thanks.


It is a couple of new optional fields in the API but not a new feature. We used to do it by sending an initial message on the control socket but that was racy. So now we alternatively allow you to send it as part of the REST request.

So that's not breaking any existing client, it just allows newer clients to be slightly more reliable.


method to complex. You are doing 4 actions in 1 method:
1. create dir
2. init queue
3. loop thhrough product
4. add jobs to queue


OK I will change that. Also I'm actually using PMOD pins from the low speed TOFE board. I'll change that to use the pins of the Opsis board.


It would be nice if in future you can separate out the code reviews for different issues. That way it's easier for the reviewers and also you get better quality reviews. Will review this one soon.


Great, travis work!!


we need to call

Sdl.GL.SwapWindow

here I think


"it is" (instead of is is).  Or "the recommendation is to" (what I probably would have written were I avoiding we=)).


Holy hardcodings, Batman!


aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa


excess loop


harikaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa @

- [1. ](

`url`

)


you could also use the `@override_settings` test decorator


merged


Yeah, I saw that and assume you would fix it later :)


스플래쉬 액티비티가 실행 되지 않음...


to protect from access outside of this class


to prevent modification of this variable


I'm not actually sure why it did this.


This is the critical bit !


Doing it that way disallows for lazy init. I'm using the widget dynamically (the rendered output is inserted into the document via ajax), so i had to change the js_template (successfully ;) - might be a nice feature to handle this special case, too - but i am already happy with the template change.


why don't you collect all data while looping thought a html? This actually do a mess to a code.


Could turn this into a partial... code to generate the avatar and compile the collection of posts & comments.


To do more edits when https://github.com/dastgir/Hercules/tree/r1-meteor is merged to Hercules


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


@jimis lets switch it back then, I only changed it because @estenberg asked.


第3-7章改成第3-8章


@mquinson I do it. https://github.com/mquinson/simgrid/issues/70


@frankyw  Please see the solution posted in the following reply.

https://colorlib.com/wp/forums/topic/more-link-not-visible/#post-49547


:joy:


Oops, should be meow release...


You were not aware of the thread: http://forums.bethsoft.com/topic/1599816-wrye-bash-thread-108/page-2#entry25113512 ? That's where the action is - Supierce saebel and co are my main testers

I fetched your commits in upstream and will gradually review them.

General remark: You need to split work up a bit differently - I can do it for you and add constructive criticism ;) I will post messages to the upstream fetch as I go: https://github.com/wrye-bash/wrye-bash/compare/iaz3-mod-import

Have a look in my wip branch would be a nice way to contribute at the moment - you may catch a bug I have not caught and most importantly you can see how I work with the commits - more on that later


I forgot..


i just changed it because i wanted to, not really needed, i was just used to that


Katarina? what happened to leblanc ?


Hehe +1:


TeamCity jonas-requests :: WindowsBuild [Build 46](https://build.neohq.net/viewLog.html?buildId=613665&buildTypeId=JonasHaRequests_WindowsBuild) outcome was **UNKNOWN**
Summary: Canceled (Tests failed: 1 (1 new), passed: 32358, ignored: 122) Build time: 1:31:27
### Failed tests
```
org.neo4j.server.ServerCommandLineArgsTest.shouldPickUpSpecifiedConfigFile: <no details avaliable>

```


The constructor should be called __construct and not __constructor


@teraJumper98193 good good. thank you for ding the work.


This has been disabled for years, and is in the process of being rebuilt from the ground up-
See the PackageInstaller branch.


Yes!


Why stop PC port and use Chrome app ?


@lws-team you discussed this in #279 but keeping it installed is a good idea.
Thanks for re-introducing the file in `INSTALL` in https://github.com/warmcat/libwebsockets/commit/88d118d6705f0cb5bb8f5e6c817cb051ee87dbf6 :sparkles:


Sorry Monday was holiday here, so I did not saw your messages until now.
I just submitted the changes for Xcode7 and iOS 9.x. Please try and let me know if you still got a problem.
I am closing this this thread here - please use the other commit and or open an issue to continue the discussion.


Hey Doga, this line was screwing everything up lol. ng-controller needs to be HomeController, or else things break.


I forget what the situation is.  I'll re-investigate this.


@SarahSchoonmaker when you are building/debugging your app you'll benefit massively by using the non-minified versions of scripts. Just drop the `.min` resulting in > `<script src="https://code.jquery.com/jquery-2.1.3.js"></script>`


fokhooo


p.s.: you might want to check if your `cpack` scripts (rpm) are still working :)


Hi world.


this needs to be changed to shouldUpdateCommTar


Add foundation devCoin to getblocktemplate output


В самом jssc уже есть поле для определения закрыт или открыт порт. Проще было использовать его
https://github.com/scream3r/java-simple-serial-connector/blob/2.8.0/src/java/jssc/SerialPort.java#L137


+1 @kyook caltech don't need to worry about this issue.


It works well,but there is no source code to modify to revise current version.


Tireless Tracker 2nd ability still bugged.

Wolf of Devil Breach attack ability is forcing discard even if you select not to use the ability or pay the 1R.


TeamCity Glyssen :: Glyssen-master Continuous [Build 0.100.8.ef8ba4d54f7250a2feda8a5754659caea841080b](http://build.palaso.org/viewLog.html?buildId=70801&buildTypeId=bt431) outcome was **SUCCESS**
Summary: Tests passed: 1083, ignored: 13 Build time: 00:08:13


Since the task args are added after the task name on the command line. So the constructed command line looks like this command args taskname task.args. In your example the command would be npm compile run instead of npm run compile.


@jhgundersen you are right. It's fixed in the new release: https://github.com/easybook/geshi/releases/tag/v1.0.8.17


В самом jssc уже есть метод для определения состояния порта (открыт/закрыт).
https://github.com/scream3r/java-simple-serial-connector/blob/2.8.0/src/java/jssc/SerialPort.java#L137

В таких ситуациях можно использовать его


:+1: :+1: :+1:


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


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


This edit is slightly inaccurate. The *compiler* won't complain because Python is interpreted.  So, technically you get a runtime warning from the interpreter, not the compiler.  The code will compile without any issues.


These files are there so that it is easy for other cmake projects to find the lib. That the RPM does not build with them I would blame hte RPM part of everything... It is just some text files, it should be able to deal with installing those.


Can you make it so that it works for nay number? so instead of `x = 10` you have something like
```python
x = input("Give me a number")
```


@mckll Good work here. Thank you! Ship code.


It may not be easy to identify, but do you know what version you were using
previously or when you downloaded it?

Most of the recent changes addressed identified issues, but also added a
5th child to the master, which is only fully supported if you update
RF24Mesh and RF24Network on the nodes (or at least the ones close to
master). Otherwise, for testing purposes, try setting #define
MESH_MAX_CHILDREN 3 in RF24Mesh_config.h (on master only) and
recompiling/uploading the master node to revert to scheme more similar to
prior behaviour. (The master will support 4 nodes, while children support
only 3)

Not sure what else it would be, it seems to work much like before for me,
just more reliable.

On Tue, Mar 29, 2016 at 1:10 AM, robertiko07 <notifications@github.com>
wrote:

> Really is working? i update mesh 1.0.5 and Network 1.0.5, but the master
> static is hard to detected nodes.
> i have 7 nodes id-1,id-197,id-89,id-32,id4-0,id-251,id99 y id-15
> just 1 time detected 3 nodes.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly or view it on GitHub
> <https://github.com/TMRh20/RF24Mesh/commit/b420fbc0d43536f534779030cd5ad1872eb2ce40#commitcomment-16873534>
>


Using `1` instead of `0` here because `iron-list` usually scrolls to `scrollTop` `1` when using `scrollToIndex(0)`


Generalmente node_modules se agrega a gitignore para no subir todos los paquetes que npm instala.
Cada integrante del grupo cuando obtiene cambios del repositorio antes de correr la aplicacion puede hacer un "npm install" para instalar lo que packages.json diga que hay que instalar.


why enable apc when from the build logs I see that php 5.5-7.0 comes with opcache by default?

"with Zend OPcache v7.0.4-dev, Copyright (c) 1999-2014, by Zend Technologies"

maybe against <apcu> should be tested


Yep, is are the indices of the respective eigenvectors.


u too :)


This should be a ```const```


This too should be a ```const```


改了以后的版本：两张图片、一个表格、锚点、格式、等


> how does this all look?

And let the review begin: this should be squashed with its child commit - as it is `self._import` calls will blow with undefined attributes - you understand why ?

General note: commits that break even temporarily a feature must absolutely not hit dev and I avoid them like the devil on personal branches too - when it happens to commit something that breaks stuff and I become aware I push the fix ASAP (so it is the closest possible in the regression) clearly marked as regression - search for regression to see what I talk about:

![kkk](https://cloud.githubusercontent.com/assets/1365079/14109212/ab9db1d6-f5c9-11e5-857d-a25ffe193c52.jpg)

Being very careful to separate work on _self-contained_ commits not only makes for better code overall (cause you code more carefully) but also permits debugging commands like bisect to work - that is a very real concern.


lol stfu mat


ah ok, didnt know that. I only ever use tasks.json for npm scripts, not install or update.


*and


not sure about the parameters, esp favorite.


Good. A slight correction:  I said before "There should always be space after a note/chord", but of course I meant "There should always be space after a note/chord/ligature".


@levinotik oops, sorry for incredibly late reply. May not be useful any more, but i wrote a library for this called robots-txt. it's on hackage and abstracts away the horrible details.


@coffeeking , please check my other commits! These settings aswell as the update Desktop entry I moved to desktop-settings. That's where they should be. Please make the changes there!
See
https://github.com/manjaro/manjaro-tools-iso-profiles/commit/de3ea458d0bf8476d53dd4493c80f7045db56331
and
https://github.com/manjaro/manjaro-tools-iso-profiles/commit/7065047a5f08aaa2bc8ce7ece2377dd8679121d7


> It looks like it does an update every frame (render call) when it's the shadow's camera's 'fov' that only needs to be change when a SpotLights 'angle' property is changed.

> Please explain how this is a wrong interpretation of what's happening, and otherwise an argument that supports updating the camera FOV per frame, instead of when angle is changed?

Not sure what you mean...

> I also posted 2 new spot light examples but I guess those should go to another separate PR.

Yes please.


Collaborator:
A review for this commit was created. [Link to review](http://localhost:8080/ui#review:id=161)


Collaborator:
A review for this commit was created. [Link to review](http://localhost:8080/ui#review:id=162)


hi
I'm so sorry. I'll remove them. I already found out that you'd added the
software updates desktop icon, so I'll remove them. It's late and I'm
tired, so that might explain why my brain's not working properly lol.
Thanks
Kendell Clark

Bernhard Landauer wrote:
>
> @coffeeking <https://github.com/coffeeking> , please check my other
> commits! These settings aswell as the update Desktop entry I moved to
> desktop-settings. That's where they should be. Please make the changes
> there!
> See
> de3ea45
> <https://github.com/manjaro/manjaro-tools-iso-profiles/commit/de3ea458d0bf8476d53dd4493c80f7045db56331>
> and
> 7065047
> <https://github.com/manjaro/manjaro-tools-iso-profiles/commit/7065047a5f08aaa2bc8ce7ece2377dd8679121d7>
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub
> <https://github.com/manjaro/manjaro-tools-iso-profiles/commit/b62ee401c4df0e137e7bf5306d4264bf61bb4d8e#commitcomment-16877700>
>


Collaborator:
A review for this commit was created. [Link to review](http://localhost:8080/ui#review:id=163)


tu peux un jour venir sur hangout ou pas ?


No problem at all! :)


wtf where is my project upgrade


sorry (


Yes it is not complicated. They are just missing in the packaging scripts in the `.spec` file and need to be added :) Otherwise the packing scripts are confused and report the mismatch between installed and to-be-packed files.


`feel_options` should not be necessary, it is added by default


anyway thanks for fixing that !


On 03/29/2016 03:34 PM, Dimitry Sibiryakov wrote:
>> AST should never wait on mutexes.
>     May be, but it is not a real AST, it is just another background thread that do
> something.

Not sure what do you call real. Unix signal handler or HW interrupt?
In that case since 2.5 there are no real AST in firebird - on all
platforms blocking thread is used to deliver AST. Certainly, it's
somewhat simpler to write them in this case. For example, one can
allocate memory in AST. But the rule of thumb remains - no wait
operations in AST (even if it's not real).

> It can do anything that application's background thread can do. Including FB
> API calls that will wait for attachment mutex.
>
>> Always comes old question - what should it do if timeout happened?
>     Check for new event has arrived if not something like WaitForMultipleEvents() is used.
> Then wait some more. That's how waiting for several things at once used to work, no?..

With ability to wait for multiple objects I see no problems with your
suggestion. Unfortunately to be able to do it on non-windows platforms
we need to change remote to use events polling. And I'm not sure will it
be done in v.4 due to release timeframes. As soon as we have epoll I'll
be glad to agree with suggested interface.

>
> ---
> You are receiving this because you authored the thread.
> Reply to this email directly or view it on GitHub:
> https://github.com/FirebirdSQL/firebird/commit/f92f2a1b09d68ddb30c2928110d0ad432b636cf0#commitcomment-16877001


I.tesa


Added msdn style documentation to repository.


"J'imagine que nous serons épargnés de la vision des fourches et des torches hors de notre moulin" L'homme sourit de travers. "Du bon travail, d'avoir calmer cette querelle. Trumbel dormira sans aucun doute plus facilement."
d'avoir calmer -> d'avoir calmé
Et il ne manquerait pas un point entre moulin" et L'homme ?


Finally it is fixed.


Thought so. The reason I asked is because the build bots are clean.


MakeDegreeDaysConsistWithASH901 (JasonGlazer) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1621 of 1621 tests passed, 0 test warnings)

![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.91%25-green.svg)


I would do this differently - I would have kept working on the individual execute methods and when they became very similar I would replace them in one go. So I would first define a constant (you define later) for
`_(u'No relevant NPC levels to import.')` and similar and would replace the strings, rinse and repeat:

```
while execute not similar enough:
    refactor some more
replace execute with base class execute
```

This approach would permit me (among others) to verify more easily that the intermediate commits do not break anything - refer to my comments in https://github.com/wrye-bash/wrye-bash/commit/972bf2846680fcc5db03db9575773191c084c0c3 - and also would document the steps and rationale why I ended up with the design I ended for future devs. So your commit says: lets copy paste the Mod_ActorLevels_Import.Execute to base while my approach would say - hmm look here all (or nearly all, as you saw I left some too complicated executes there in the export case) use a string message, let's factor this out - so one sees how the common execute is built up and if a regression hits in is much more easily tracked

I don't know (yet) how your approach went but I recommend you doing it this way next time


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


Hi @travisneilson, I liked the new changes.
I took the liberty to add a parallax-effect to the header (in memory of the good old days of the _Parallax On The Web_ series). I have uploaded the code on [my domain](http://parallax-devtips.aldesign.it/) - please, I would like to know what you think.


allons y


I am not going to create a PR, I will just "_work_" on a [separate branch](https://github.com/andrealeone/DevTips-ShowWebsite/tree/style-experiments) of my [forked repo](https://github.com/andrealeone/DevTips-ShowWebsite/).


Welcome, have a sit


Hi all!

I have a problem. I can see the 'FOX-BRDG' device but I can't add the device. I have a message that it say me that the PIN-number is incorrect, but I don't use any PIN. How can I add the 'FOX-BRDG' device with my Smartphone or PC? Can you help me with a communication example between SME(cc2541) and Smartphone/PC?

Thank you!!


Yep, thanks for catching it !

I think it should have broken some of the deploy tests, let's give the builders some time to try again.


See now - we have something temporarily broken: `_(u'No relevant NPC levels to import.')` is displayed in `Import Relations` - refer to parent commit comment


Ajout d'une fonction pour gérer les états de la single page web.


You don't want to do this. The docker client will only sent the Dockerfile directory and children directories to the docker daemon, so it doesn't include your source code.


I propose to remove that page and document service in the source code with Swagger (eg. http://apps.titellus.net/geonetwork/api-doc)


Hey


Sphinx complains about many errors in that file
```
[INFO] /data/dev/gn/develop/docs/manuals/en/api/the-geonetwork-api/index.rst:11: WARNING: Title underline too short.
[INFO]
[INFO] Group Services
[INFO] =============
```


dfbsehgbh


hi


How do to use it in CentOS 7?


I guess _log should be called in base execute ?


All right! Is the (re)loading problem fixed?

A remark about the indentation. I would *un*indent line 3 (the `li` is nested within its `ul` parent, but only one level deep, so a couple spaces is enough). And I would *un*indent lines 6-8, for the `ul` tag here really belongs at the root of the HTML hierarchy.


After this commit header became too big:
![image](https://cloud.githubusercontent.com/assets/4552250/14110019/7449da44-f5cd-11e5-9e7f-c5b0fe3d2bec.png)
may be revert?


O


> Unix signal handler or HW interrupt?

Yeah, something like that.

> Unfortunately to be able to do it on non-windows platforms we need to change remote to use events polling.

Not necessary. What do you think about following: put event requeue request to some kind of queue inside of attachment (in atomic manner) and try to acquire the attachment mutex. If success - send request (if it is still in queue), delete queue and release mutex. If failed - leave queue as is. In main thread before every mutex release check if there is something in queue and if yes - send it, delete queue and then release mutex.


@tobscure I hope that's okay - seemed to make sense, but I might have overlooked something.

In fact, it seems to break the live preview for unsaved items - was that the reason it was implemented like this? And if so, is there a way to bind the inputs to the properties of the unsaved model instead?


@bjkistad, I mean having a numeric ID as value of the options. This prevents arbitrary text to be used as the country. Displayed to the client would still be the actual name.


Previously the logo was too small, I think it looks better now, even if the lang switch is not in the center (vertically)


Never mind, I reverted it.


Yes, that's not a bad ideea. Better than this...


Google does not support this  font Noto Sans Meetei Mayek/TTF/NotoSansMeeteiMayek-Regular.ttf
is there any way to add this font in google fonts..


环境说明：windows 7，python27，jieba VERSION 0.38，pycharm2016.1
1.简介：

支持中文分词，关键字提取，词性标注,自己管理词库等
2.安装：
方法一：开始->搜索cmd->cd到pip.exe目录->输入命令pip install jieba
3.代码片段：
import jieba

seg = jieba.cut('有关青春萌动',True/False)#分词，True/False  全模式/精确模式
seg = jieba.cut_for_search('有关青春萌动',True)#分词，搜索引擎模式
#seg 是迭代器，可通过list(seg)将其转换为列表

#关键词提取(import jieba.analyse)(sentence,关键词数目)

import jieba.analyse

seg  = jieba.analyse.extract_tags('有关青春萌动',12)

print ' '.join(seg)

#词性标注
# import jieba.posseg as pseg
words = pseg.cut("我爱北京天安门")
for w in words:
   print w.word,w.flag


MakeDegreeDaysConsistWithASH901 (JasonGlazer) - i386-Windows-7-VisualStudio-12: Tests Failed (1621 of 2177 tests passed, 0 test warnings)

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


@mnzt A commit with no changes. Please. Beat that.


rule of the longest chain: implemented
mutual rollback: implemented
stable network: implemented


Force push is beautiful


Actually I used the web interface.
On 29 Mar 2016 14:49, "Toby Archer" <notifications@github.com> wrote:

> Force push is beautiful
>
> —
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub
> <https://github.com/libeclipse/starlight/commit/755811377a1e22dee01aed7bf033f4f54b37ea01#commitcomment-16878023>
>


I dont have my mac on me right now so I cant schedule it, but can we schedule a meeting so you can walk me through instillation


I guess to enlarge the logo is ok, but we need to provide better quality of the source image and align the lang switch.


Also I assume enemies will just always be coming at the person, not waiting at specific spots?


TeamCity Glyssen :: Glyssen-master Continuous [Build 0.100.9.7b1035d4fc8a884375dc7f0be9b6f69917a31d41](http://build.palaso.org/viewLog.html?buildId=70802&buildTypeId=bt431) outcome was **SUCCESS**
Summary: Tests passed: 1062, ignored: 13 Build time: 00:07:39


I do not know either :) This was just copying the deleted test in plugin/cfopsplugin/cfopsplugin_test.go to here when refactoring the call method. Maybe let us delete it?


Hd


Looks too huge for me, but maybe it's just the matter of taste..
Aligned lang switch element vertically.


Alright the patch is updated on master + v1.7-stable.  It is the specfile's "fault" it has to dispose of everything in DESTDIR somehow or the packaging action fails... anyway it should be sync'd with the reality of this file also being generated now.


Tt


You need to match to detinees belonging to 'active' movement orders, else someone who was previously in the estate would not be matched


Hi jocafli.

You do not have to add any PIN.

- Please read the library README.md and use one of the validated applications
  in the "Useful Links" section.
- The Examples provided with the SME library should be enough to start.

Ciao


this will return `undefined`, I'm guessing you meant to return `prebooking`


> Finally it is fixed.

If you really wanted it so badly, you should have done something about it.


DepricatedFields (mitchute) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed, 0 test warnings)

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


The scan failed.
Included commits

Commit ID	Owner

14398c1fc35655a03bab11ce5c8b427e0b4040da	@cxehud


BOOOOOOOO


Just a pointless comment. Thanks!


commit


pom项目名


Until [Set](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Set) is more widely supported, I would use an object as opposed to array to avoid duplicates. You could then return `Object.keys()` at the end

```javascript
for (var i = 0; i < tests.length; i++) {
  var name = tests[i].getAttribute('data-test-name')
  names[name] = true;
}
return Object.keys(names);
```


Changes:
- moved color settings for whole app from translation to settings (config)
- one form for editing all values
- call own helper class :smile:
- some code cleaning (need some more :cry:)


General remark: fixups should be squashed with relevant commit in the spirit of correct, self-contained commits

Re: Attribute error - not sure I like it - I would prefer we use the common execute in classes that do have those attributes and have the yellow unresolved attr warning (as I mostly do) - in classes that do not have these attributes we must of course override the execute. Reason: this way I am kind of aware that the refactoring is not perfect yet - once perfect one finally defines a class attribute and marvels at one's design.

Have a look at the 306 commit message where I explain the refactoring performed for 306 - many links in there to example commits: https://github.com/wrye-bash/wrye-bash/commit/1cd839fadbf4b7338b1c12457f601066b39d1929


/*
    ========================================
        Table of Contents
    ========================================

    ::Assumed Markup
    ::Base Styles

    ::Global Width

    ::4 Columns
    ::6 Columns
    ::8 Columns
    ::9 Columns
	::10 Columns //new with Clarke
    ::12 Columns
	::14 Columns //new with Clarke
    ::16 Columns

    ::Clearfix

    ========================================
        ::Assumed Markup
    ========================================

    NOTES:
    ========================================
    .page
    Contains any overflow / offscreen elements

    .container
    Defines large
's

    .container > .inner
    Non-padded, centered fluid width block with clearfix

    .content
    A left floating element

    .content > .inner
    Padded block with clearfix

    ========================================
        ::Base Styles
    ========================================
*/
    *, *:before, *:after {
        box-sizing: inherit;
    }
    .page  {
        position: relative;
        overflow: hidden;
    }

    .container {
        position: relative;
    }
    .container > .inner {
        max-width: 1280px;
        min-width: 240px;
        padding: 0 10px;
        margin: auto;
    }

/*
    .container > .inner {
        max-width: 1280px;
        min-width: 240px;
        margin: auto;
    }
*/

    .content {
        float:left;
    }

/*  Removed in Clarke (box model)
    .content > .inner {
        padding: 0 10px;
    }
*/

    .content > .inner *:first-child {
        /*margin-top: 0;*/
    }

/*
    ========================================
        ::Global Width
    ========================================
*/
    .size1of1 { width: 100%; }

/*
    ========================================
        ::4 Columns
    ========================================
*/
    .size1of4 { width: 25%; }
    .size2of4 { width: 50%; }
    .size3of4 { width: 75%; }
    .size4of4 { width: 100%; }

    .shift1of4 { margin-left: 25%; }
    .shift2of4 { margin-left: 50%; }
    .shift3of4 { margin-left: 75%; }
    .shift4of4 { margin-left: 100%; }

    .hide6,
    .hide8,
    .hide9,
    .hide12,
    .hide16 {
        display: block !important;
    }

    .hide4 {
        display: none !important;
    }

    .wrap4 { float: none; }
    .wrap6,
    .wrap8,
    .wrap9,
    .wrap12,
    .wrap16 { float: left; }

/*
    ========================================
        ::6 Columns
    ========================================
*/
    @media screen and (min-width: 321px) and (max-width: 480px) {

        .size1of6 { width: 16.66666%; }
        .size2of6 { width: 33.33333%; }
        .size3of6 { width: 50%; }
        .size4of6 { width: 66.66666%; }
        .size5of6 { width: 83.33333%; }
        .size6of6 { width: 100%; }

        .shift1of6 { margin-left: 16.66666%; }
        .shift2of6 { margin-left: 33.33333%; }
        .shift3of6 { margin-left: 50%; }
        .shift4of6 { margin-left: 66.66666%; }
        .shift5of6 { margin-left: 83.33333%; }
        .shift6of6 { margin-left: 100%; }

        .hide4,
        .hide8,
        .hide9,
        .hide12,
        .hide16 {
            display: block !important;
        }

        .hide6 {
            display: none !important;
        }

    .wrap6 { float: none; }
    .wrap4,
    .wrap8,
    .wrap9,
    .wrap12,
    .wrap16 { float: left; }

    }

/*
    ========================================
        ::8 Columns
        ::9 Columns
    ========================================
*/
    @media screen and (min-width: 481px) and (max-width: 720px) {
        /* ::8 Columns */
        .size1of8 { width: 12.5%; }
        .size2of8 { width: 25%; }
        .size3of8 { width: 37.5%; }
        .size4of8 { width: 50%; }
        .size5of8 { width: 62.5%; }
        .size6of8 { width: 75%; }
        .size7of8 { width: 87.5%; }
        .size8of8 { width: 100%; }

        .shift1of8 { margin-left: 12.5%; }
        .shift2of8 { margin-left: 25%; }
        .shift3of8 { margin-left: 37.5%; }
        .shift4of8 { margin-left: 50%; }
        .shift5of8 { margin-left: 62.5%; }
        .shift6of8 { margin-left: 75%; }
        .shift7of8 { margin-left: 87.5%; }
        .shift8of8 { margin-left: 100%; }

        /* ::9 Columns */
        .size1of9 { width: 11.1% }
        .size2of9 { width: 22.2% }
        .size3of9 { width: 33.3% }
        .size4of9 { width: 44.4% }
        .size5of9 { width: 55.5% }
        .size6of9 { width: 66.6% }
        .size7of9 { width: 77.7% }
        .size8of9 { width: 88.8% }
        .size9of9 { width: 100% }

        .shift1of9 { margin-left: 11.1% }
        .shift2of9 { margin-left: 22.2% }
        .shift3of9 { margin-left: 33.3% }
        .shift4of9 { margin-left: 44.4% }
        .shift5of9 { margin-left: 55.5% }
        .shift6of9 { margin-left: 66.6% }
        .shift7of9 { margin-left: 77.7% }
        .shift8of9 { margin-left: 88.8% }
        .shift9of9 { margin-left: 100% }

        .hide4,
        .hide6,
        .hide12,
        .hide16 {
            display: block !important;
        }

        .hide8,
        .hide9 {
            display: none !important;
        }

    .wrap8,
    .wrap9 { float: none; }
    .wrap4,
    .wrap6,
    .wrap12,
    .wrap16 { float: left; }

    }

/*
    ========================================
        ::12 Columns
    ========================================
*/
 /* @media screen and (min-width: 721px) and (max-width: 960px) { */
	@media screen and (min-width: 801px) and (max-width: 960px) {

        .size1of12 { width: 8.33333%; }
        .size2of12 { width: 16.66666%; }
        .size3of12 { width: 25%; }
        .size4of12 { width: 33.33333%; }
        .size5of12 { width: 41.66666%; }
        .size6of12 { width: 50%; }
        .size7of12 { width: 58.33333%; }
        .size8of12 { width: 66.66666%; }
        .size9of12 { width: 75%; }
        .size10of12 { width: 83.33333%; }
        .size11of12 { width: 91.66666%; }
        .size12of12 { width: 100%; }

        .shift1of12 { margin-left: 8.33333%; }
        .shift2of12 { margin-left: 16.66666%; }
        .shift3of12 { margin-left: 25%; }
        .shift4of12 { margin-left: 33.33333%; }
        .shift5of12 { margin-left: 41.66666%; }
        .shift6of12 { margin-left: 50%; }
        .shift7of12 { margin-left: 58.33333%; }
        .shift8of12 { margin-left: 66.66666%; }
        .shift9of12 { margin-left: 75%; }
        .shift10of12 { margin-left: 83.33333%; }
        .shift11of12 { margin-left: 91.66666%; }
        .shift12of12 { margin-left: 100%; }

		.size1of8_12 { width: 12.5%; }
		.size2of8_12 { width: 25%; }
		.size3of8_12 { width: 37.5%; }
		.size4of8_12 { width: 50%; }
		.size5of8_12 { width: 62.5%; }
		.size6of8_12 { width: 75%; }
		.size7of8_12 { width: 87.5%; }
		.size8of8_12 { width: 100%; }

        .hide4,
        .hide6,
        .hide8,
        .hide9,
        .hide16 {
            display: block !important;
        }

        .hide12 {
            display: none !important;
        }

    .wrap12 { float: none; }
    .wrap4,
    .wrap6,
    .wrap8,
    .wrap9,
    .wrap16 { float: left; }

    }

/*
    ========================================
        ::16 Columns
    ========================================
*/
/*  @media screen and (min-width: 961px) {	*/
    @media screen and (min-width: 1121px) {
        .size1of16 { width: 6.25%; }
        .size2of16 { width: 12.5%; }
        .size3of16 { width: 18.75%; }
        .size4of16 { width: 25%; }
        .size5of16 { width: 31.25%; }
        .size6of16 { width: 37.5%; }
        .size7of16 { width: 43.75%; }
        .size8of16 { width: 50%; }
        .size9of16 { width: 56.25%; }
        .size10of16 { width: 62.25%; }
        .size11of16 { width: 68.75%; }
        .size12of16 { width: 75%; }
        .size13of16 { width: 81.25%; }
        .size14of16 { width: 87.5%; }
        .size15of16 { width: 93.75%; }
        .size16of16 { width: 100%; }

        .shift1of16 { margin-left: 6.25%; }
        .shift2of16 { margin-left: 12.5%; }
        .shift3of16 { margin-left: 18.75%; }
        .shift4of16 { margin-left: 25%; }
        .shift5of16 { margin-left: 31.25%; }
        .shift6of16 { margin-left: 37.5%; }
        .shift7of16 { margin-left: 43.75%; }
        .shift8of16 { margin-left: 50%; }
        .shift9of16 { margin-left: 56.25%; }
        .shift10of16 { margin-left: 62.25%; }
        .shift11of16 { margin-left: 68.75%; }
        .shift12of16 { margin-left: 75%; }
        .shift13of16 { margin-left: 81.25%; }
        .shift14of16 { margin-left: 87.5%; }
        .shift15of16 { margin-left: 93.75%; }
        .shift16of16 { margin-left: 100%; }

		.size1of10_16 { width: 10%; }
		.size2of10_16 { width: 20%; }
		.size3of10_16 { width: 30%; }
		.size4of10_16 { width: 40%; }
		.size5of10_16 { width: 50%; }
		.size6of10_16 { width: 60%; }
		.size7of10_16 { width: 70%; }
		.size8of10_16 { width: 80%; }
		.size9of10_16 { width: 90%; }
		.size10of10_16 { width: 100%; }

        .hide4,
        .hide6,
        .hide8,
        .hide9,
        .hide12 {
            display: block !important;
        }

        .hide16 {
            display: none !important;
        }

    .wrap16 { float: none; }
    .wrap4,
    .wrap6,
    .wrap8,
    .wrap9,
    .wrap12 { float: left; }

    }

/*
    ========================================
        ::Clearfix
    ========================================
*/
    .group,
    .container > .inner,
    .content > .inner {
        *zoom: 1;
    }
    .group:before,
    .group:after,
    .container > .inner:before,
    .container > .inner:after,
    .content > .inner:before,
    .content > .inner:after {
        display: table;
        content: " ";
    }
    .group:after,
    .container > .inner:after,
    .content > .inner:after {
        clear: both;
    }


Можно было сделать
```cpp
if (!isEmpty)
    return;
```
Было меньше изменений и можно было бы применить гипотетический патч, исправляющий оформление
```} else {```
и написанный до этого коммита.


Yeah that makes the most sense to me


Названия полей должны быть с префиксом m_.


@engbiruk can you figure out what's wrong with this commit? You are doing three separate things in a single branch new feature, bug fix and God knows what the other things are. **_Please avoid doing this kind of practice_** :boom:  :bomb: :disappointed:


Yup 165 -- looks like it got [added with this commit](https://github.com/mozillascience/site/commit/4dd895c8c4d863dbc7dddeb22b14c9c52493be35#diff-7b51e4470a529ea02b2eb6e7a29493d7R165) --  would rather not have this at the bottom of the page:
![screen shot 2016-03-29 at 10 02 40](https://cloud.githubusercontent.com/assets/617994/14110653/648fe7ac-f595-11e5-8576-0c6d32340569.png)

Could you remove?


On 03/29/2016 04:45 PM, Dimitry Sibiryakov wrote:

>> Unfortunately to be able to do it on non-windows platforms we need to change remote to use events polling.
> Not necessary. What do you think about following: put event requeue request to some kind of queue inside of attachment (in atomic manner) and try to acquire the attachment mutex. If success - send request (if it is still in queue), delete queue and release mutex.

Send and delete will happen automatically on release.

> If failed - leave queue as is. In main thread before every mutex release check if there is something in queue and if yes - send it, delete queue and then release mutex.
>

The only disadvantage I see is that sooner of all we will have to
cleanup this when moving to epoll (hope this will happen somewhen). But
compared to the rest of changes it's definitely not too much.

And tech detail - we must keep existing queEvents() at least in order to
emulate old API. New interface should be built on top of existing one.


Без c++11 не будет ```range-based for```.


Thanks--the best place to make this kind of comment is in Gerrit, in this case at https://golang.org/cl/21202 (see the change description).


Let me be the first one to congratulate you on this commit message!


Комментарий тоже убрать видать нужно.


Oops, unclosed string literal!


이메일 체크 관련 모듈 빠짐,
pip freeze로 추가 예정


Нет, комментарий как раз валидный, объясняет, почему мы читаем весь поток данных целиком, игнорируя Content-Length


fixed


[HZR] 2.3 AC-Web User views Hot Zone Report


not sure, just wanted to provide you with great examples how to use it ;)


Amazing....
sdcardfs...


@1ec5 Thanks for the :eyes: on this.  I am very curious if GitHub will respect those links however as it seems to want to only respect the current branch / git situation.  For example the current README.md plays out like this:

```
// URL Needed In Web browser
https://github.com/mapbox/mapbox-gl-native/blob/master/README.md

// Produces 404 Not Found
https://github.com/mapbox/mapbox-gl-native/README.md

// Possible Solution?
/mapbox/mapbox-gl-native/blob/master/README.md
```


nope, that is exactly the difference.

if you simulation is `simDim`, all fields (vector and scalar fields) are of dimension `simDim` but can still have `N` components:

- scalar field: simDim dimensions with N=1 components
- vector field: simDim dimensions with N=3 components
- tensor field: simDim dimensions with N components


Whoops. Forgot.


I think it makes sense to switch all the current `ara` sentences to `arb`.

I'm wondering if we can keep `ara` as a supported language. Technically, if someone searches a sentence in `ara`, we should return results in `arb`, `arq`, `arz`, `acm`, etc. But that's not something Tatoeba can do at the moment, so we technically can't support `ara`.

If we decide to keep it, to categorize sentences that don't fit into any of the other Arabic languages that we support, what should we do with the language name? If we leave it as "Arabic", I'm afraid it can lead to some confusion.

* Some contributors will be adding sentences into "Arabic" instead of "Arabic (Modern Standard)" because they won't know what's the difference or won't even notice there is a "Arabic (Modern Standard)" language.
* Some users will select "Arabic" instead of "Arabic (Modern Standard)" when searching sentences, for the same reasons, and they won't find anything because we will have almost no sentences in `ara`.


This commit contains unrelated indent ...


This is old version.
New version is this:
https://github.com/neobuddy89/shamu/commit/c28130f33e6388388f7d9f87384c737789d94a92


DepricatedFields (mitchute) - x86_64-MacOS-10.9-clang: OK (2128 of 2170 tests passed, 511 test warnings)

 * 511 tests had: AUD diffs.
 * 401 tests had: BND diffs.
 * 4 tests had: EIO diffs.
 * 4 tests had: ERR diffs.

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


> And tech detail - we must keep existing queEvents() at least in order to
> emulate old API. New interface should be built on top of existing one.

Not necessary. We can emulate old API on the top of new interface as well depending on
what will have smaller overhead.


@kevincox For some reason, this breaks terminfo in Bash (i.e. <TAB> and other special keys). I've spent some time but haven't figured out what happens at all. At this point I consider reverting given that `buildFHSEnv` adds Bash unconditionally now anyway, what do you think?


This is a good commit (aside from some formatting you were not aware of) - in the sense that it clearly factors out a specific thing and can be easily reviewed. Unfortunately I can't be sure the calls to super work - for instance what if an override does not define continueInfo  ? So this boils down again to refactoring in place till code is similar enough - in this case you could have defined a common _ask_import say method in an early stage and replaced common code and be able to clearly see which (if any) execute did not call that.

Pausing review here for now - I guess you get the spirit. If you can rewrite those commits trying to conform to my instructions so far and excluding intermediate steps that you reverted (like the formatter) let me know - otherwise I can do it for you so I try to illustrate my points.

Thanks!


This is not sufficient to run mochitests on my laptop. I need to add one python package.
adding any of pythonPackages.{pip,setuptools,pkgconfig}, or even pythonPackages.web, which is completely unrelated, fixes the build.
In fact, it seems that any pythonPackage will do as buildPythonPackages pulls setuptools.

I would go with pythonPackages.setuptools here.


Good catch! I was about to fix this.


Просто комментарий об условиях вычитки, а по факту никаких проверок не осталось читаем всё, что читается.


Here is an [example](https://github.com/ComputationalRadiationPhysics/picongpu/blob/6bc280eaf6bed7bb0b65a978d653fcee5e8180a5/src/picongpu/include/fields/FieldTmp.kernel#L96-L97) how you can use a `DataSpace<simDim>` object to shift inside the `operator()` instead of using the C-style bracket `[]` operator.


Indeed, `feel_options` is not necessary. This has been removed in commit cf47704e134c1bfd20658e1d5b7ceeddd1a60d00.


了承しました。


ИМХО комментария ниже на 167 строке достаточно вполне для понимания. Но это мелочь, пофиг.


@shoogle I'm still finalizing...but this si basically what my Docker file looks like


Result of TryParse is a boolean value that indicates is the parsing was successful or not.
In your case, according to your comment, if a user has entered an invalid value, then TryParse will return false and it will be a valid situation called trial trial period.


Ok. Muchas gracias.
El mar. 29, 2016 10:21 AM, "Diego van Haaster" <notifications@github.com>
escribió:

> Generalmente node_modules se agrega a gitignore para no subir todos los
> paquetes que npm instala.
> Cada integrante del grupo cuando obtiene cambios del repositorio antes de
> correr la aplicacion puede hacer un "npm install" para instalar lo que
> packages.json diga que hay que instalar.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly or view it on GitHub
> <https://github.com/LeandroLuque/AplicacionesWeb/commit/19e8023c0d60bbc9c2b63be41ca6c846468184e2#commitcomment-16877606>
>


omit the head and body tags If you require to add more stylesheets or javascripts, use global.html


yes, there is quite some temporal (and spatial) space in this code where `notifyPeriod` is first defined and set and then re-defined to an other meaning. this is bad style and obfuscates things.


Picked to release-16.03 in cc8278e ;-)


Thank you!


Fix IE issue for multiple records


Please don't use JSP tags like "c:if"i n JSF pages. Instead of them it's better to use "rendered" property and a4j "render".

There are many examples in other XHTML pages an in this page. Or you can use as reference: http://livedemo.exadel.com/richfaces-demo/


true! then maybe write `if( visualization->init() != 0 )` to avoid the implicit cast? :)


On 03/29/2016 05:10 PM, Dimitry Sibiryakov wrote:
>> And tech detail - we must keep existing queEvents() at least in order to
>> emulate old API. New interface should be built on top of existing one.
> Not necessary. We can emulate old API on the top of new interface as well depending on
> what will have smaller overhead.

We can't change it in fb3 (it's too many changes for post-RC2)! I.e.
existing call anyway should be present.


Pardon, missed the formatting errors. Will try and remove the extra line breaks


可以吗


TeamCity Glyssen :: Glyssen-master Continuous [Build 0.100.10.3151dd3939a706e316ff46ac93193bc393bf6210](http://build.palaso.org/viewLog.html?buildId=70807&buildTypeId=bt431) outcome was **SUCCESS**
Summary: Tests passed: 1062, ignored: 13 Build time: 00:10:15


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


Still wating for you to get this set correctly.
This is merged wrong in here, CM repo and everywhere else that kanged this incorrect commit.
Fix this already please.


It seems like it is validating that the backup or restore can throw
errors... I like the idea... It's more that the behaviors don't make sense
as called out....

Let's just log a chore to clean this up separately
On Mar 29, 2016 9:51 AM, "Shaozhen Ding" <notifications@github.com> wrote:

> I do not know either :) This was just copying the deleted test in
> plugin/cfopsplugin/cfopsplugin_test.go to here when refactoring the call
> method. Maybe let us delete it?
>
> —
> You are receiving this because you commented.
> Reply to this email directly or view it on GitHub
> <https://github.com/pivotalservices/cfops/commit/b9d8c834a5c42c1dc46ab6ae12718fd87fc9b509#commitcomment-16878063>
>


> We can't change it in fb3 (it's too many changes for post-RC2)! I.e.
> existing call anyway should be present.

May be (I told you many times that you rushed too much with publishing it). But internally
they can be implemented via new ones.


I have no idea, I don't use CentOS.


adding helloworld repository with demo-exp repository.


test


@christkv shouldn't this be "1.3.12"?


that's fantastic, thank you! :sparkles: (f632e449defa566aa79cc4b028e0a291ae0aa8ae)

(btw: did you just amend/rebase f632e449defa566aa79cc4b028e0a291ae0aa8ae on top of the previous 88d118d6705f0cb5bb8f5e6c817cb051ee87dbf6 in `master` ? :scream: )


Shouldn't draws have a 1/2, 1/2 result instead of 0, 0?


assembler?


@ljacqu That is not broken. Will propose a revert commit.


No, GitHub is smart enough to make working links. We’ve been using them all along in the READMEs. Try it!


THERE IS NO DRAWING, ONLY DEFEAT


[HZR] 2.2 AC provides HZR areas as .kmz files


you are right fixed and published in 2.1.13


I'd suggest to change the vendor name to your own and not use `clippings`. E.g. you can use `ezarkov` like your GitHub username or whatever else you prefer. Then you could sign up on https://packagist.org and submit it there under the new name.

You could (and probably should) change the PHP namespace as well from `CL` to either something to do with your Composer vendor name or directly using a namespace like `SwiftmailerTranslator` as a root namespace.


Added new function to check if ANY beer measurements exist (such as ABV, IBU, or OG)


DepricatedFields (mitchute) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2150 of 2208 tests passed, 514 test warnings)

 * 514 tests had: AUD diffs.
 * 401 tests had: BND diffs.
 * 4 tests had: EIO diffs.
 * 4 tests had: ERR diffs.

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


So in my code the Texture of the screenquad is upside down now. I fixed it manually by reverting this codechange, but this cannot be a persistent solution.


it makes sense to change menu from Apps into RLV ?


cannot recognise this


OK, I fixed this.

On Mon, Mar 28, 2016 at 11:55 AM, Jonah Gabry <notifications@github.com>
wrote:

> @bgoodri <https://github.com/bgoodri> If I update rstan I still get
> errors, although different errors depending on the model and whether I'm
> calling pp_check_validate or pp_check_validate0:
>
> With a simple glm pp_check_validate seems to run ok but when I try to run
> pp_check_validate0 I get:
>
> fit <- stan_glm(mpg ~ wt, data = mtcars)rstanarm:::pp_check_validate0(fit, n.reps = 2)Error in matrix(0, nrow = n.rep, ncol = (n.param + num.batches)) :
>   argument "nreps" is missing, with no defaultCalled from: matrix(0, nrow = n.rep, ncol = (n.param + num.batches))
>
> With a simple glmer model I can't get either of the functions to work and
> they give different errors:
>
> rstanarm:::pp_check_validate(example_model, n.reps = 2)Error in quantile.theta[reps, ] <- apply(theta.draws, 2, quant) :
>   number of items to replace is not a multiple of replacement length
> rstanarm:::pp_check_validate0(example_model, n.reps = 2)
> [1] "Error:  Lengths of parameter batches don't sum to length of parameter vector"NULL
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub
> <https://github.com/stan-dev/rstanarm/commit/ae177e8b113190f5dac0ae09d2657d7094c71a4e#commitcomment-16864212>
>


Author @Andrew


Hey, I accepted the contributor request on Steam. Unfortunately, it seems only the original author/contributor is allowed to upload new versions and edit title and description, so it seems I'll have to reupload a new release (and I'd have to do that for DST anyway).

By the way, the DST code also runs on DS. The only issue is that the hide log on close setting isn't being applied properly if you run the together branch under DS (though it does work on DST itself). I'll soon merge the master and together branches.


DepricatedFields (mitchute) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1062 of 1062 tests passed, 0 test warnings)

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


Website description and data dictionary


Formatting changes such as this must be squashed with commit that introduces them


@neobuddy89 We have video recording working with new blobs (https://github.com/TheMuppets/proprietary_vendor_yu/commit/eaf724df231edca7e2657e79c147a5e6f4fd0345)

You facing issues with those new blobs?


test/updated some code


DepricatedFields (mitchute) - x86_64-Linux-Ubuntu-14.04-custom_check: OK (0 of 0 tests passed, 0 test warnings)

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


Thats true


Typo here: `pyhton2`


I have thought about this - more on this later. I am glad you dropped extraExts Execute parameters later on though ;)


Yes. It's broken even with new blobs.


Amazing, thank you!


hi
Bernhard, would you mind doing to our gnome image what you've done to
mate? Making the panel the same background, fixing the custom
keybindings, etc?
Thanks
Kendell Clark

kendell clark wrote:
> hi
> I'm so sorry. I'll remove them. I already found out that you'd added the
> software updates desktop icon, so I'll remove them. It's late and I'm
> tired, so that might explain why my brain's not working properly lol.
> Thanks
> Kendell Clark
>
>
> Bernhard Landauer wrote:
>> @coffeeking <https://github.com/coffeeking> , please check my other
>> commits! These settings aswell as the update Desktop entry I moved to
>> desktop-settings. That's where they should be. Please make the changes
>> there!
>> See
>> de3ea45
>> <https://github.com/manjaro/manjaro-tools-iso-profiles/commit/de3ea458d0bf8476d53dd4493c80f7045db56331>
>> and
>> 7065047
>> <https://github.com/manjaro/manjaro-tools-iso-profiles/commit/7065047a5f08aaa2bc8ce7ece2377dd8679121d7>
>>
>> —
>> You are receiving this because you were mentioned.
>> Reply to this email directly or view it on GitHub
>> <https://github.com/manjaro/manjaro-tools-iso-profiles/commit/b62ee401c4df0e137e7bf5306d4264bf61bb4d8e#commitcomment-16877700>
>>


there is an error on this line,


delete


Thanks!


Umm.. It's working for me ATM. Tried with Snap as well as google cam. Can you explain if some action breaks it?


I created issue SECURITY-259: Can only connect one JNLP3 slave per IP address.  Sorry if that is the wrong category.


ok, then let us move it to the boost work-around section above and put a comment above it.


just decide on an official spelling, e.g., CMake vars are derived from it.


Yes, especially master recent patches are still open to getting amended, reordered or squashed as needed without respecting history.  Travis etc make that a fairly common occurrance by telling me about problems after it's pushed, there is no meaning to adding a spew of fix patches into the history.


In a later commit i change the way i wanted it to work, such that every subclass must define supportedExts, so the check for it not being there should probably be removed.

I added it because some classes, the only difference in execute was the extensions supported. And it just doesnt make sense to duplicate execute just allow a different extension in addition to .csv


From what i saw, every single import asks for continue, so they all define it. If for some reason we add one that doesnt, well i suppose it needs to be changed.

I'm not sure what you mean about super, though.

What it super does is just call the generic execute from the parent class.

Also, what formatting?


I don't use camera on daily basis, but I do have video recording working with those new blobs. I just now tried it :/


TeamCity Chorus :: chorus-win32-master Continuous [Build 2.6.198.e76bd46db6e48f13715fda3f64ac2df0280f17be](http://build.palaso.org/viewLog.html?buildId=70819&buildTypeId=bt2) outcome was **FAILURE**
Summary: Compilation error: src\LibChorus\LibChorus.csproj Build time: 00:03:44


That was definitely missing here ! Cool feature.


don't worry young padavan, people *do* find that out since the CMake is verbose during configure time and additionally the `ISAAC_` vars are still visible in `ccmake`.


Hi yared,
Yes I did it on purpose, because we are using the same branch(bugfix) to
push our any changes.

On Tuesday, 29 March 2016, Yared Ayalew <notifications@github.com> wrote:

> @engbiruk <https://github.com/engbiruk> can you figure out what's wrong
> with this commit? You are doing three separate things in a single branch
> new feature, bug fix and God knows what the other things are. *Please
> avoid doing this kind of practice* [image: :boom:] [image: :bomb:] [image:
> :disappointed:]
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly or view it on GitHub
> <https://github.com/ndrmc/cats/commit/e17e1ff4e0cda6708ad7b5739629343b7b57929b#commitcomment-16878231>
>


Open SNAP, switch to front cam video recording, start recording.
Without fix, it doesn't start recording for me.
Also exposure is pretty low.


It is


test review on commit


I dealt with that issue later on, for all of the classes.


This usage is obsolete in HTML5. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a#attr-name


shouldn't you set the flag to `false` above after the call to `masterProc`? Now, in other hosts that _don't_ call getParameter() inside `masterProc`, the flag won't get reset until some later time.

I'd also hold on to the parameter index (`frame->index`) as well, just for safety's sake. Who knows, maybe Ardour will decide to call `getParameterProc` for some other parameter at the same time. That might be realistig actually, since it could come in from a different thread.


@mikeNG Yes. Exposure is too low on front cam.

@neobuddy89 yes front cam video recording works for me. Do you have this: http://review.cyanogenmod.org/#/c/136450/


our namings are therefore in PIConGPU:
- `simDim` == dimension (array, matrix, 3D matrix)
- `numComponents` == scalar, vector, tensor

Example: [FieldE.hpp](https://github.com/ComputationalRadiationPhysics/picongpu/blob/6bc280eaf6bed7bb0b65a978d653fcee5e8180a5/src/picongpu/include/fields/FieldE.hpp#L55)


ok


Ouch, thats an issue. Next time i'll focus on doing a set task within one commit, and providing clear commit messages, and rebasing more(I actually did a few rebases and squashed stuff later on, so i'm getting better on that)


Do we need all of this?


And you know what that means....


It is a learning experience


sshinternnavy


Updated, thanks


Ага, вижу, спасибо.


Probably not. Looking at RFC5545, these should probably all be negative.

@languitar: is this intentional? Do you use negative numbers in those fields?


All right, just need to know when pulling new patches directly from `master` :)


Oh, Eclipse!


> Try it!

I did!  It failed.  :-)

I trust your experience though.  Let's go with your PR and wait for the all the cruft to get knocked out after the release branch is merged back into master.


Thanks!


TBH I'm not using this currently but it still seems like a good idea to use absolute paths where possible. However if something is breaking by all means fix it.


update：我最初想到的是，维护一个hashtable表，将出现1之前已经出现的存起来，这样如果检测到了ciycle就说明出现了loop；别人的想法是既然是检测cycle，那就可以用快慢指针来做，如上面答案。


I later managed to find it, but nowhere bash related has a link to the latest thread. I ended up following the "NEW THREAD" links from one of the old ones.

Why is there a 7 page limit or whatever on there?

Will do!


მარა რო დაუკვირდე ადვილი დასაწერია და ბევრი შეცდომაა ;დ


Hahahah the funiest commit message i've ever seen.


> General remark: You need to split work up a bit differently - I can do it for you and add constructive criticism ;)

yes please


Thanks for the explanation @borisbstyle .