Estás usando algo de bootstrap? Si no lo estás usando ni lo importes.


Esto es para ver como se organiza html con las divisiones. En el futuro no voy a dejar código comentado, pero me puedo quedar con esto?


Btw la ruta esa es RARISIMA


El theme tampoco lo estas usando


FFFF


shouldn't  rpmtest be added as well?


Todo lo que sea javascript, cargalo antes de cerrar el tag <body>


Never mind. PHP was too low of a version.


The `-d` flag allows an install, even if it is a lower version. This is very, very valuable, and should be the default.

This does not work on devices that are running an older version of Android, regardless of what version of the Android tools you have installed. We had a script to try and check the device version, but this is brittle, and lately does not work on my devices.

Although forcing this flag means that old Android devices will not work properly from the tools, this is a better compromise in my mind than not installing applications on (perhaps?) all the devices people realistically use


is this needed? seems to have no impact


En el laburo si mandas código comentado te comes una cagada a pedos. En proyectos grandes te olvidas de esto, y queda re perdido y ensuciando. Guardate un file vos si lo necesitas.


FixDaylightingTableZone (mjwitte) - i386-Windows-7-VisualStudio-12: OK (2347 of 2347 tests passed, 573 test warnings)

 * 573 tests had: AUD diffs.

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


@Jhair2015 Actually I just found a but :/. If you turn ERTP controls it disables Q controls so Slither can't work


imma try to fix it


How about rpmtest depends on rpmbuild target which builds the rpm
and then only executes find as the verification step?


El media query es preferible usarlo dentro de la hoja de css.
`main.css`
```
@media screen and (max-width: 980px) {
  * {
    color: red;
  }
}
```
Cuantos menos archivos cargues mejor. Dos archivos de 50k tardan menos que 1 de 100k.
Ah y no dejes el espacio entre el = y la "


yes, try to call `Js_unsafe` as less as you can in case I make some changes in the future


@pwojnowski  May be its bit late to comment on this commit.  However DEFAULT_ERROR_HANDLER  bit aggressive when it comes to ```MongoSocketException`` i think. Below is what happened in our production.

Due to I/O operation mongo master decided release leadership as explained in https://jira.mongodb.org/browse/SERVER-23471,  (neverthless MongoDb re-election is inevitable)

The current exception handler will encounter this mongo exception and just exits the JVM.  Since all nodes in Quartz cluster will encounter same problem and bring the entire cluster down.  My question is it not safe to ignore  MongoSocketException and log  warning and carry-on, assuming cluster will recover from network error.? Or is there any otherway around this cascading failure?


El `h5` es para titulares de baja importancia, en este caso no son titulares, son una lista de items. Lo que tendrías que usar son `<ul>` y `<li>`


Guarda que esto está mal, cerraste primero el h1 y despues el a y es al revés.


Tratá de no dejar espacios vacíos.


Tratá de usar espacios en vez de tabs, la conveción más común dice 2 espacios


closes #7


Hmm, very good question. This one isn't in the ROS repo and it doesn't use
Travis (to my knowledge?) So it seems like it can still merge ? But Dirk
knows way more about this.

On Jan 3, 2017 5:14 PM, "Mikael Arguedas" <notifications@github.com> wrote:

> @codebot <https://github.com/codebot> is this one also discarded ? should
> we delete the branch or create a PR for this?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/ament/ament_index/commit/6ac431e25e6c0ff463695c05c91670f736cd8fad#commitcomment-20353821>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AFBR2q1JtxhAQMpZhFbOj1jIznFGBQzQks5rOvJcgaJpZM4LaMw_>
> .
>


Which comes from https://github.com/jbenet/node-subcomandante/blob/master/survivor


建议阅读放在那儿挺好的，多谢多谢


a.pgm is my test file ?

On Tue, Jan 3, 2017 at 5:03 PM, gewirtz <notifications@github.com> wrote:

> What?
>
> Sent from my iPhone
>
> On Jan 3, 2017, at 5:43 PM, ninagnedin <notifications@github.com<mailto:
> notifications@github.com>> wrote:
>
>
> Runs on a.pgm
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub<https://github.com/
> gewirtz/APC_FinalProject/commit/623e10eb91e91ba7b3a9da6a691aa9
> 49ad52da0a#commitcomment-20352685>, or mute the thread<https://github.com/
> notifications/unsubscribe-auth/APG-Pnzh1iwKOPntD9PW1GRpAR-
> iw4ADks5rOs74gaJpZM4LaG_9>.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/gewirtz/APC_FinalProject/commit/623e10eb91e91ba7b3a9da6a691aa949ad52da0a#commitcomment-20352904>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AV88liWnNS0YLhjjls6KhYhO6zdfjtdMks5rOtPTgaJpZM4LaG_9>
> .
>

--
Nina Gnedin
Masters of Finance | Class of 2017
Princeton University | 26 Prospect Ave Princeton, NJ 08544


a


DOA-TO-UnitVent (Nigusse) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2383 of 2383 tests passed, 0 test warnings)

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


Shouldn't TL3 links still get noopener?


DOA-TO-UnitVent (Nigusse) - 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.png)


Nice change, will implement this if you guys don't mind.


Hm... there is no rpmbuild target or do you mean: add a new rpmbuild target which builds the rpms and the test just verifies their existense?


ここについては、Pylint で下記の警告が出てますが、確認いただけますか？
```
ryu/lib/packet/dhcp.py:184: [R0204(redefined-variable-type), dhcp.parser] Redefinition of parse_opt type from list to ryu.lib.packet.dhcp.options

```


I've made a small followup change: https://github.com/google/oss-fuzz/commit/e4cfaf79361acdef2565b720a04302ae17fae280#diff-b4fb04eed1eae086922862af3c1227fd


That is correct. The way I see it, there  are 2 things that the target does, 1. build the rpm, 2. verify it (hack)

IMHO, it is best to separate these into different targets


Oh yeah, sorry if I wasn't clear, I wasn't suggesting going back to compile all of them, but the previous binaries should be available.

@rmackay9 Are you OK with changing the quad to matrix? I think that would be easier for GCSs too, they can detect if that binary is available or not.


Yep!


I felt adding it to reset the CWD. In script I change into the docker directory again to run the container with docker-compose. Arguably could be a makefile target as well, but I don't want to spend time on that now ...


Hmm, did you mean to remove the line break?


Dang! I did not expect that at all (please reconsider).
Actually, out of the many articles I read about CSS architectures and methodologies yours is the one I liked the most because of its *honesty*.
Your *disclaimer* and *invitation to comment* is actually what I'd expect to see in any article comparing libraries/frameworks. In my opinion, that approach helps people understand that they have some home work to do and that they should not blindly trust the conclusions that some authors reach even though they often lack the expertise in some of the very libraries/frameworks they "grade".

For the record, what inspired (triggered) [https://twitter.com/thierrykoblentz/status/816379165653880836](https://twitter.com/thierrykoblentz/status/816379165653880836) was this particular post: [ACSS (Atomic CSS) CSS Methodologies Part 4 and conclusion](http://tech.buyapowa.com/blog/css/frontend/scss/sass/2015/10/14/css-methodologies-part-4.html).


add proper README.md


Very clever! Is this PR ready to go now, as far as you can tell?


151行目(ちょっとコメント位置がずれてますが)
`boot_file` だけ、バイナリ型になっているようです。
簡単な修正で終わりそうなので、
- [このコミット](https://github.com/shinpeimuraoka/ryu/commit/ed5b3edd27243d52b69693768e0865ff694ef836)に似せて１つ切る
- コミットに混ぜ込む

で対応可能でしょうか？


Orientation = 100?


Ah, thanks!


this is  a   test   git


Just go from 2000 to 3000, problem solved.


I'm curious about what went wrong. I think that other modules should also have linking issues for the same reason. Unless this is the only one that brings in JSON and not any Foundation includes. But it could still happen again, so I was wondering why the 64 bit libs where being picked up, and what I could do to fix that perhaps in the cmakelists. Like the library search path, etc


Restore the 'Sunflower' Portable Lightbox


注意：配置文件不能重复 更不能出错


DOA-TO-UnitVent (Nigusse) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1201 of 1201 tests passed, 0 test warnings)

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


配列最後は,いらなくない？


@daaaaaaaaaaaaaisuke これは・・・？


@daaaaaaaaaaaaaisuke 細かいところですが大切ですね！


Updated RGBMood library which simply incorporates the RGB to HSV function in FastLED


Andreas, your script for master automation works, and performs slave .dyn graphs on DETACHED or LOCAL copies. I'd like to push further and to convert a batch of central files ( 86 on my project) into local files.
In your experience, could Python take care of the conversion process from within Dynamo ?
I found this blog spot by David Kingham
https://www.blogger.com/profile/05482407609356395147

http://bimmanager.blogspot.ca/2010/12/revit-launcher.html

on his blog he explains and posts Revit Launcher, that has functionality to create local files from central files, and therefore, convert central files to a state that master graph will be able to work. Unfortunately, David stopped updating his app and his blog in 2012, so Revit Launcher is of no use for 2015-2017 Revit.

Please, let me know if the functionality of that app could be picked by Dynamo through Python


![Január 4. - Szerda](http://ujlipot.vakvarju.com/data/napimenu/22.jpg?v=1483344630)
Tárkonyos pulykaraguleves
Resztelt csirkemáj petrezselymes burgonyával
Feketeerdő szelet


<!DOCTYPE html>
<html>
<head>
<meta name="viewport" content="width=device-width, initial-scale=1.0"/>
<style>
canvas {
 border:1px solid #000000;
 background-color: #00FFFF;
}
</style>
</head>
<body onload="startGame()">
<script>

var myGamePiece;

function startGame() {
 myGamePiece = new component(30, 30, "smiley.gif", 10, 120, "image");
 myGameArea.start();
}

var myGameArea = {
 canvas : document.createElement("<wbr />canvas"),
 start : function() {
 this.canvas.width = 480;
 this.canvas.height = 270;
 this.context = this.canvas.getContext("2d");
 document.body.insertBefore(<wbr />this.canvas, document.body.childNodes[0]);
 this.frameNo = 0;
 this.interval = setInterval(updateGameArea, 20);
 },
 clear : function() {
 this.context.clearRect(0, 0, this.canvas.width, this.canvas.height);
 },
 stop : function() {
 clearInterval(this.interval);
 }
}

function component(width, height, color, x, y, type) {
 this.type = type;
 if (type == "image") {
 this.image = new Image();
 this.image.src = color;
 }
 this.width = width;
 this.height = height;
 this.speedX = 0;
 this.speedY = 0;
 this.x = x;
 this.y = y;
 this.update = function() {
 ctx = myGameArea.context;
 if (type == "image") {
 ctx.drawImage(this.image,
 this.x,
 this.y,
 this.width, this.height);
 } else {
 ctx.fillStyle = color;
 ctx.fillRect(this.x, this.y, this.width, this.height);
 }
 }
 this.newPos = function() {
 this.x += this.speedX;
 this.y += this.speedY;
 }
}

function updateGameArea() {
 myGameArea.clear();
 myGamePiece.newPos();
 myGamePiece.update();
}

function move(dir) {
 myGamePiece.image.src = "angry.gif";
 if (dir == "up") {myGamePiece.speedY = -1; }
 if (dir == "down") {myGamePiece.speedY = 1; }
 if (dir == "left") {myGamePiece.speedX = -1; }
 if (dir == "right") {myGamePiece.speedX = 1; }
}

function clearmove() {
 myGamePiece.image.src = "smiley.gif";
 myGamePiece.speedX = 0;
 myGamePiece.speedY = 0;
}
</script>
<div style="text-align:center;<wbr />width:480px;">
 <button onmousedown="move('up')" onmouseup="clearmove()" ontouchstart="move('up')">UP</<wbr />button><br><br>
 <button onmousedown="move('left')" onmouseup="clearmove()" ontouchstart="move('left')"><wbr />LEFT</button>
 <button onmousedown="move('right')" onmouseup="clearmove()" ontouchstart="move('right')"><wbr />RIGHT</button><br><br>
 <button onmousedown="move('down')" onmouseup="clearmove()" ontouchstart="move('down')"><wbr />DOWN</button>
</div>

<p>&copy widowskenya 2016 &trade;</p>
</body>
</html>


![](https://github.trello.services/images/mini-trello-icon.png) [Fix: Taxonomy aggregation doesn't work without taxonomy](https://trello.com/c/sjcqSPBI/22-fix-taxonomy-aggregation-doesn-t-work-without-taxonomy)


develop (kbenne) - i386-Windows-7-VisualStudio-12: Tests Failed (0 of 0 tests passed, 0 test warnings)

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


We have 3 standing bugs in the Debian BTS: https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=scanmem
This upload of course fixes all 3.

Are you still in time to add the relevant "Closes #NNNNNN" to the relevant changelog lines, so the bugs autoclose?


👍  This looks really good, this should finally solve #9


some small changes...
UserLogin:: missing in some places.
activate_user() should query id = $user_id not username = $username.


HI jay..
Is test_bios_update.robot scripting is working after make changes? I see a failure in teardown as ''cat: can't open '/tmp/obmc-console.log': No such file or directory' should be empty.'


should it be:
	lm75@49{
		compatible = "lm75";
		reg = <0x49>;
	};


When you are planning to publish it? I mean update nuget package


Only this code newly added others are package changes and proper naming.


i think `remove-v` is not exists in git, maybe here need change to `git remote -v upstream`?


LGTM :+1:


打发打发


THIS PROJECT WILL CONTINUE DO NOT WORRY!


Added some initial notes.


Now, anybody with skills in HTML, JS and CSS,  like Tony Partner, will be able to create custom question rendering with custom attributes in an easy way. I took on my side the complexity of the logic, letting to the 3rd party coders only the easy part.

Before, with the plugin system, only people with high skills in PHP, who understand the plugin system logic, were able to do that.


Suggestion: use the rune alias instead of uint8


This number should ideally be 64 or 32. (See http://www.rossbencina.com/code/real-time-audio-programming-101-time-waits-for-nothing)

Starting at 64 we can more easily see all the overhead of communication.


Not thread-safe.


Immediate changes in gain cause clicking. Most of the time you would want to smooth it out. At 0.1 increments, it's probably not that noticeable.


I'm not sure whether waiting here for completion is a good idea or would it be better to do the buffer swapping yourself. I have to lookup how should this be done in PortAudio.

The concern: when you start waiting here, you are wasting time that could be spent on calculating the next buffer. This means that you could be more likely to miss the deadline for that next buffer.


just `git remote -v`, because use `git remote -v origin` will get a error response from git:

```
Seans-MacBook-Pro:Laravel Sean$ git remote -v origin
error: Unknown subcommand: origin
usage: git remote [-v | --verbose]
   or: git remote add [-t <branch>] [-m <master>] [-f] [--tags | --no-tags] [--mirror=<fetch|push>] <name> <url>
   or: git remote rename <old> <new>
   or: git remote remove <name>
   or: git remote set-head <name> (-a | --auto | -d | --delete | <branch>)
   or: git remote [-v | --verbose] show [-n] <name>
   or: git remote prune [-n | --dry-run] <name>
   or: git remote [-v | --verbose] update [-p | --prune] [(<group> | <remote>)...]
   or: git remote set-branches [--add] <name> <branch>...
   or: git remote get-url [--push] [--all] <name>
   or: git remote set-url [--push] <name> <newurl> [<oldurl>]
   or: git remote set-url --add <name> <newurl>
   or: git remote set-url --delete <name> <url>

    -v, --verbose         be verbose; must be placed before a subcommand
```


:tada:


@oberon2007 nice switch :+1:


Suggestion: use rune alias instead of uint8


First: it's not really needed for now (it's for the admin part).
Second: it's absolutely possible to add a localization system.


empd_bugfix_rcoating (nmerket) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1197 of 1197 tests passed, 0 test warnings)

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


![image](https://cloud.githubusercontent.com/assets/19995663/21639063/35ba2b96-d27f-11e6-88b8-abe67e566e51.png)
![image](https://cloud.githubusercontent.com/assets/19995663/21639145/9b501d4e-d27f-11e6-864e-2ed48dc731c3.png)
Where should I insert the password in the game? In a chat? If in chat, then how?


:smile:


yes


To be fair, this is more an issue of not using C++ *right* than an issue of C++; if that code used a RAII-based approach (in this case, std::string would go over well, so I may swap to it at some point), this would not have been an issue. I have been thinking of using RAII approaches for ages now, such as shared_ptr, weak_ptr, and unique_ptr; but my vote for it was beaten on the mailing list due to performance concerns.


@jaroel Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.api/19/violations
```
src/plone/api/content.py:269:1: C901 'delete' is too complex (15)
src/plone/api/content.py:361:1: C901 '_wf_transitions_for' is too complex (13)
src/plone/api/content.py:426:1: C901 'transition' is too complex (13)
src/plone/api/portal.py:284:13: Q000 Remove bad quotes.
src/plone/api/portal.py:285:13: Q000 Remove bad quotes.
src/plone/api/portal.py:326:13: Q000 Remove bad quotes.
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


first yii 2 project


tpartner: we still have to choose what variables will be available from the pstpl file. But:
1. A good guess is: oSurvey, oQuestionGroup, and oQuestion
2. While moving the logic from the helpers to the pstpl file, we'll find all the needed variables to pass.


That makes some sense to me... I'll accept a PR on this. This is the right time to make the change - 3.2's beta is about to be released.


Test, Hey Helke I am trying out Pull Requests. This was my first entry for the CVS file. Can you let me know if you can see this? Since you still weren't able to see my code maybe this is the solution


Этот коммит можно удалить, случайно после pull отправил не то...


Nie mogę skompilować tego programu. Proszę o zamieszczenie skompilowanego, ale czas 15s może być zabójczy dla napędu, proszę mi wprowadzić 1-2s


you can add custom attributes in the admin part, like width and height, with CSS on frontend?
no.  It makes it extremely easy for anybody knowing HTML, CSS, JS and XML to create new question rendering.


I'll try and crate a better fix for the command current one is very hacky, I just needed it working asap.


`boolean`???


Какое  интересное имя для переменной


练习多进程抓取汽车之家图片


Ну поправь и снова залей


eidt


Not for what I've seen. Can you confirm?


But : we already have a plugin functionnality for this : 2 think for the same purpose : I think there are an error.

If existing functionnality don't cover this part : improve it/fix it. But adding a specific system don't seems the good solution for me.

And here :

1. What is the DB columns ?
2. How manage multiple columns (subquestions | subquestions X/Y | etc .... tri dimensionnal arry etc ...)
3. How manage global attribute (CSS class for example )
4. How another dev can add an attribute for THIS new question type

Have a better system for Question attribute/settings are a good idea , then improve https://github.com/LimeSurvey/LimeSurvey/blob/develop/application/helpers/questionHelper.php#L1591 seems a better idea. For example a xml reader to get new attribute here, why not.


PS: "FinalStatGameState" und "RoundStatGamesSate" erstellt und bearbeitet.


@Fasse this is a big security issue. A fallback to an unsecure pseudo random generator is MUST NOT in security


#19 fixed by this commit.


Python matplotlib plot of the functions

[alsamixer-linear.pdf](https://github.com/TermeHansen/MPD/files/684372/alsamixer-linear.pdf)


I have the following error

$ make
make: *** No rule to make target `../mono/mcs/class/System.Drawing/System.Drawing.Drawing2D/Blend.cs', needed by `bin/ios/System.Drawing.dll'.  Stop.


You don't see them ? I did them as a review in #368. Is That why ?

Yes, `docker exec -it --user root bash` works and does the same thing as --user=0. But I don't see why you would need to log as root since the jhipster docker image has sudo.


欣喜地发现1.0.0没有这个问题。。。


See: https://github.com/roots/sage/pull/1741


@jerri123 what is the problem?


@rascarlo for german it is correct!


TIL you need to submit the review or else nothing is shown...


lol I say : show any li.radio-item like a button it's max 10 lines of css , and this 10 lines of css can easily be added with a plugin with less than 50 lines of PHP (with comment).

> you can add custom attributes in the admin part

Yes

> like width and height, with CSS on frontend

Yes

See : https://framagit.org/SondagePro-LimeSurvey-plugin/radioToStarRating/blob/master/radioToStarRating.php for example. When made it : no [newQuestionAttributes](https://github.com/LimeSurvey/LimeSurvey/blob/develop/application/helpers/questionHelper.php#L1590) but really more easy ..... (see [here](https://framagit.org/SondagePro-LimeSurvey-plugin/moveSomeAnswers/blob/master/moveSomeAnswers.php#L94) for a new attribute in admin part)


haha :stuck_out_tongue:


update Chinese translation


Something like this would probably be good for exult. I haven't used C++ in
a very long time now. Only been using language with garbage collection. It
certainly makes this a lot easier. First class array types so nice compared
to just using raw pointers.

Really don't see what sort of system would experience any sort of
substantial slowdown using RAII. The slowest parts of the engine are likely
to be shape rendering, the interpreter and pathfinding. Using the _ptr
classes shouldn't affect those in any major way. Just a lot of work going
through the code base fixing things up.

The file handling code could really use it. I remember not too long
ago trying to track down how it worked and it was getting extremely
confusing trying to work how what owned what pointer and where, when or if
things got deleted.

On 4 January 2017 at 21:15, Marzo Sette Torres Junior <
notifications@github.com> wrote:

> To be fair, this is more an issue of not using C++ *right* than an issue
> of C++; if that code used a RAII-based approach (in this case, std::string
> would go over well, so I may swap to it at some point), this would not have
> been an issue. I have been thinking of using RAII approaches for ages now,
> such as shared_ptr, weak_ptr, and unique_ptr; but my vote for it was beaten
> on the mailing list due to performance concerns.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/exult/exult/commit/88c4a227ef30fd535bced9aeabdafbabf8091536#commitcomment-20356724>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AA-DB_aLtPtXlmg0hnOmOIfZReuXYnFQks5rO3FDgaJpZM4LaMsJ>
> .
>


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


Do you have a working built with lp integration?


 1）将汉字翻译为拼音，其中每一个字的首字母大写；
 pinyin.getFullChars(this.value);

 2）将每一个字的拼音的首字母提取出来，是大写的形式：
 pinyin.getCamelChars(this.value);


**About event plugins for everything:**
The plugin system is based on events, and made to manage anything related to events. Using events to manage all the rendering modularisation is a bad idea. It makes it harder for third party coder. Someone who just wants to change some HTML, or to add some CSS and some JS should not be obligated to go into complex PHP developments. Also it brings conception errors, like adding the events inside the helpers to manage attribute, instead of adding a method in the question attribute model. This kind of conception errors have consequences: it make the code more procedural, and will make it harder to centralize when we'll move to question object (for exemple, that what happened to the Drupal code who was entirely based on hooks and events, making it extremely hard to update). Using a MVC approach, putting the data logic inside the models, is already a first little step to the big move to question object.

**About different tools to add modularity:**
In any web application, web framework, you have different kind of bricks to manage modularity:

Plugins for events (eg: plugins in Joomla), widgets for recurring views appearing in different controller contexts ("widget" in Yii, "modules" in Joomla), MVC components to add entire new functionalities (components in Joomla, YiiModules, etc), and templates with positions.

This is just very normal. You can add to your system plugins, modules, components.

So, now, if Tony Partener or any body with a low level in PHP but a good skill in HTML, CSS and JS wants to create a new question rendering: he can do it without difficulty. If he wants to share it or to sold it: it will be very easy.


Ha-ha, in one projects we put `fixtures` script and data in there


估计是sama的事吧


@ToporBigBots  И ты тут...


красивое решение с передачей аргумента)


Das Löschen führt dazu, dass keine Gruppen mehr erstellt werden können!


started with practising


started practising


But ..... you don't answer to the original question

I never say adding an xml system for new question attribute is a bad solution, i say it's a good idea. I never say have a clean way to replace views in new Question attribute is a bad idea (currently : i think slider in mulmtiple numeric can be a plugin).

Foix/correct actual concept is a OK for me, but adding (again and again and again) a new concept .... a new system and the 2 systems are incompatible ....


WARNING!!! This version of phinx breaks when running seeds like this: $this->dispatchShell('migrations seed --seed PermissionsSeed');


But what Admidio is Not usable in some cases without that fix!


This:
https://framagit.org/SondagePro-LimeSurvey-plugin/radioToStarRating/blob/master/radioToStarRating.php

Is typically something hard to do for someone with no PHP skill, but good HTML, CSS and JS skills. Someone like Tony Partner could not use it, whereas he created a lot of workaround for LimeSurvey.

Now, he will have an easy system to update the rendering of a question type, and to share it, or to sell it.


Note: Sorry, this was meant to be on another repository, but this'll also be helpful with the high scores and other stuff.


comment


2017-01-03 19:32:13 Warning: Warning (2): trim() expects parameter 1 to be string, array given in [/dados/www/sige.qa.dotgroup.com.br/vendor/robmorgan/phinx/src/Phinx/Console/Command/SeedRun.php, line 114]
Trace:
Cake\Error\BaseErrorHandler::handleError() - CORE/src/Error/BaseErrorHandler.php, line 146
trim - [internal], line ??
Phinx\Console\Command\SeedRun::execute() - ROOT/vendor/robmorgan/phinx/src/Phinx/Console/Command/SeedRun.php, line 114
Migrations\Command\Seed::parentExecute() - ROOT/vendor/cakephp/migrations/src/ConfigurationTrait.php, line 165
Migrations\Command\Seed::execute() - ROOT/vendor/cakephp/migrations/src/Command/Seed.php, line 71
Symfony\Component\Console\Command\Command::run() - ROOT/vendor/symfony/console/Command/Command.php, line 255
Symfony\Component\Console\Application::doRunCommand() - ROOT/vendor/symfony/console/Application.php, line 830
Symfony\Component\Console\Application::doRun() - ROOT/vendor/symfony/console/Application.php, line 191
Symfony\Component\Console\Application::run() - ROOT/vendor/symfony/console/Application.php, line 122
Migrations\Shell\MigrationsShell::main() - ROOT/vendor/cakephp/migrations/src/Shell/MigrationsShell.php, line 101
Cake\Console\Shell::runCommand() - CORE/src/Console/Shell.php, line 456
Migrations\Shell\MigrationsShell::runCommand() - ROOT/vendor/cakephp/migrations/src/Shell/MigrationsShell.php, line 156
Cake\Console\ShellDispatcher::_dispatch() - CORE/src/Console/ShellDispatcher.php, line 217
Cake\Console\ShellDispatcher::dispatch() - CORE/src/Console/ShellDispatcher.php, line 181
Cake\Console\Shell::dispatchShell() - CORE/src/Console/Shell.php, line 345
App\Shell\PermissionShell::main() - APP/Shell/PermissionShell.php, line 24
Cake\Console\Shell::runCommand() - CORE/src/Console/Shell.php, line 456
Cake\Console\ShellDispatcher::_dispatch() - CORE/src/Console/ShellDispatcher.php, line 217
Cake\Console\ShellDispatcher::dispatch() - CORE/src/Console/ShellDispatcher.php, line 181
Cake\Console\ShellDispatcher::run() - CORE/src/Console/ShellDispatcher.php, line 127
[main] - ROOT/bin/cake.php, line 33


they are not the same system.
Plugin system is to manage events.
Question Template is to manage question rendering.


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


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


done


My two cents...

I think that most LS "power users" seldom need to modify the LS core but very often need custom question views or functionality, typically rendered on top of an existing question type. This feature definitely makes that easier for PHP luddites like me.


This will cause an issue to re-appear. The parsing of computeStyle has to end if you reach the default case. If you let the style compute, the parsing of a certain style will only end with the end of the line

@emanuelschuetze described the issue inside #2576 as:

> create motion pdf without line numbers
> => Failure 1: the full paragraph is filled with background color


Hi!

I'm trying to use your addon here in  Spain, but so far I completely incapable of make it work. I've installed the addon available on the repository, it initially was logging in to the UK or German site, I was capable of login in, and browse the contents (the german or UK contents), but I couldn't play any of the videos.

In most of them it said "This video is not available in your country" (which is something I already expected).
But, in others (I looked for movies and tv shows I know are available in Spain) it said "Due to changes in Amazon DRM this files are not playable".

Now, I see here that you're working to adapt the addon to the global "primevideo.com" site, which hopefully will fix the first of the errors I mentioned (I will only access those movies and tv shows from Spain).

However, I think I might be still facing the second error (changes in the DRM), any idea?

However, if you need to any test, please let me know I'm very interested on this to work :)

Thanks and regards!


Won't this removal create an activity for removing a rating again?


А удалить его с сайта полностью можно? Он же ничего полезного не несет))


![](https://github.trello.services/images/mini-trello-icon.png) [HTML utils form is ignoring the method attribute on generation](https://trello.com/c/npioyOCX/15-html-utils-form-is-ignoring-the-method-attribute-on-generation)


I really hope this turns out!


Thanks


Any reason for making this conditional? I understand that SWELL doesn't have the constant, but the constant should resolve to the same string anyway, so we can just use the same code for Windows and comment as to why we're using a literal. An alternative would be to define the constant in resource.h for Mac only.


1. Render is an event : http://www.yiiframework.com/doc/api/1.1/CViewAction#onBeforeRender-detail + http://www.yiiframework.com/doc/api/1.1/CController#beforeRender-detail
2. [Plugin](https://en.wikipedia.org/wiki/Plug-in_(computing))  == "addon" : where did you see it manage event and only event. It's an addon , and add an xml to add an attribute are done in a plugin.


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1922](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=21528&buildTypeId=ota_plus_RviSotaServer_Ci) is now running


great idea !!! ;)


> Is typically something hard to do for someone with no PHP skill, but good HTML, CSS and JS skills.

It's why i say update actual solution to have an xml file (for example) are a good solution ....

You think it's an easy way ... i'm really unsure of that ....


sad


time for 7.3.0? thanks.


Any specific reason for the WDL update; i.e. does it fix some bug with the resource generator? No harm in updating it, just want to be explicit as to whether that's necessary for this particular patch to work.


done


> Why, if the only difference between OTA and non-OTA is linking procedure (different link address)?

As I said, it's currently messy needing to delete the intermediate files.  And, doing "make" after "make ota" (after editing some source file) is also not currently working.

512k target uses different build options so should go in build-512k.


Good)


Yeah just like the one 8 lines above it. Thanks for noticing this. :-)


missed PrefixHeader.prch


Thx, i already fixed stack corruption problem with another way. Don't need to write a camera wrapper, there is exists a simpy way with hack in libc ;) Open libc/Android.mk and add -fno-stack-protector to libc_common_cflags, after that there is no crash at ImgSensorDrv::getResolution() without any wrappers.


error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 1 0 0
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
Initialized empty Git repository in C:/git-sdk-64/usr/src/git/wip2/t/trash directory.t1504-ceiling-dirs/.git/
error: isatty: 1 0 0
expecting success: test '' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test '' = ''
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 1 - no_ceil

expecting success: test '' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test '' = ''
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 2 - ceil_empty

expecting success: test '' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test '' = ''
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 3 - ceil_at_parent

expecting success: test '' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test '' = ''
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 4 - ceil_at_parent_slash

expecting success: test '' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test '' = ''
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 5 - ceil_at_trash

expecting success: test '' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test '' = ''
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 6 - ceil_at_trash_slash

expecting success: test '' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test '' = ''
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 7 - ceil_at_sub

expecting success: test '' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test '' = ''
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 8 - ceil_at_sub_slash

checking prerequisite: SYMLINKS

mkdir -p "$TRASH_DIRECTORY/prereq-test-dir" &&
(
	cd "$TRASH_DIRECTORY/prereq-test-dir" &&
	# test whether the filesystem supports symbolic links
	ln -s x y && test -h y

)
++ mkdir -p '/usr/src/git/wip2/t/trash directory.t1504-ceiling-dirs/prereq-test-dir'
++ cd '/usr/src/git/wip2/t/trash directory.t1504-ceiling-dirs/prereq-test-dir'
++ ln -s x y
ln: failed to create symbolic link 'y': No such file or directory
+ test_eval_ret_=1
+ want_trace
+ test t = t
+ test t = t
+ set +x
error: last command exited with $?=1
prerequisite SYMLINKS not satisfied
expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 9 - subdir_no_ceil

expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 10 - subdir_ceil_empty

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 11 - subdir_ceil_at_trash: prefix

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 12 - subdir_ceil_at_trash_slash: prefix

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 13 - subdir_ceil_at_sub: prefix

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 14 - subdir_ceil_at_sub_slash: prefix

expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 15 - subdir_ceil_at_subdir

expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 16 - subdir_ceil_at_subdir_slash

expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 17 - subdir_ceil_at_su

expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 18 - subdir_ceil_at_su_slash

expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 19 - subdir_ceil_at_sub_di

expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 20 - subdir_ceil_at_sub_di_slash

expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 21 - subdir_ceil_at_subdi

expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 22 - subdir_ceil_at_subdi_slash

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 23 - second_of_two: prefix

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 24 - first_of_two: prefix

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 25 - second_of_three: prefix

expecting success: test '' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test '' = ''
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 26 - git_dir_specified

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 27 - sd_no_ceil

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 28 - sd_ceil_empty

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 29 - sd_ceil_at_trash: prefix

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 30 - sd_ceil_at_trash_slash: prefix

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 31 - sd_ceil_at_s: prefix

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 32 - sd_ceil_at_s_slash: prefix

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 33 - sd_ceil_at_sd

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 34 - sd_ceil_at_sd_slash

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 35 - sd_ceil_at_su

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 36 - sd_ceil_at_su_slash

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 37 - sd_ceil_at_s_di

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 38 - sd_ceil_at_s_di_slash

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 39 - sd_ceil_at_sdi

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 40 - sd_ceil_at_sdi_slash

# passed all 40 test(s)
1..40


Looking at `<Poco/JSON/Object.h>` again, I now see it pulls in `<Poco/Foundation.h>` via `<Poco/JSON/JSON.h>`. And I added `-DPOCO_NO_AUTOMATIC_LIBS` to my `CFLAGS`. Hence no need.


I just realized that this method needs YARP 2.3.69 (devel) but at the VVV17 (as long as I remember) we agreed on using YARP 2.3.68 (master). Not a big problem, but something we should be aware of.


cc @pattacini


@gavinking I believe GuardedVariables are never "visible" in the editor, could you confirm this commit won't break other features please?


empd_bugfix_rcoating (nmerket) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1772 of 1772 tests passed, 0 test warnings)

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


```
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 1 0 0
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
Initialized empty Git repository in C:/git-sdk-64/usr/src/git/wip2/t/trash directory.t1504-ceiling-dirs/.git/
error: isatty: 1 0 0
expecting success: test '' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test '' = ''
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 1 - no_ceil

expecting success: test '' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test '' = ''
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 2 - ceil_empty

expecting success: test '' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test '' = ''
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 3 - ceil_at_parent

expecting success: test '' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test '' = ''
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 4 - ceil_at_parent_slash

expecting success: test '' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test '' = ''
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 5 - ceil_at_trash

expecting success: test '' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test '' = ''
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 6 - ceil_at_trash_slash

expecting success: test '' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test '' = ''
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 7 - ceil_at_sub

expecting success: test '' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test '' = ''
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 8 - ceil_at_sub_slash

checking prerequisite: SYMLINKS

mkdir -p "$TRASH_DIRECTORY/prereq-test-dir" &&
(
	cd "$TRASH_DIRECTORY/prereq-test-dir" &&
	# test whether the filesystem supports symbolic links
	ln -s x y && test -h y

)
++ mkdir -p '/usr/src/git/wip2/t/trash directory.t1504-ceiling-dirs/prereq-test-dir'
++ cd '/usr/src/git/wip2/t/trash directory.t1504-ceiling-dirs/prereq-test-dir'
++ ln -s x y
ln: failed to create symbolic link 'y': No such file or directory
+ test_eval_ret_=1
+ want_trace
+ test t = t
+ test t = t
+ set +x
error: last command exited with $?=1
prerequisite SYMLINKS not satisfied
expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 9 - subdir_no_ceil

expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 10 - subdir_ceil_empty

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 11 - subdir_ceil_at_trash: prefix

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 12 - subdir_ceil_at_trash_slash: prefix

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 13 - subdir_ceil_at_sub: prefix

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 14 - subdir_ceil_at_sub_slash: prefix

expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 15 - subdir_ceil_at_subdir

expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 16 - subdir_ceil_at_subdir_slash

expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 17 - subdir_ceil_at_su

expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 18 - subdir_ceil_at_su_slash

expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 19 - subdir_ceil_at_sub_di

expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 20 - subdir_ceil_at_sub_di_slash

expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 21 - subdir_ceil_at_subdi

expecting success: test 'sub/dir/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test sub/dir/ = sub/dir/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 22 - subdir_ceil_at_subdi_slash

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 23 - second_of_two: prefix

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 24 - first_of_two: prefix

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 25 - second_of_three: prefix

expecting success: test '' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test '' = ''
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 26 - git_dir_specified

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 27 - sd_no_ceil

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 28 - sd_ceil_empty

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 29 - sd_ceil_at_trash: prefix

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 30 - sd_ceil_at_trash_slash: prefix

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 31 - sd_ceil_at_s: prefix

expecting success:
		test_expect_code 128 git rev-parse --show-prefix

++ test_expect_code 128 git rev-parse --show-prefix
++ want_code=128
++ shift
++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
fatal: Not a git repository (or any of the parent directories): .git
++ exit_code=128
++ test 128 = 128
++ return 0
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 32 - sd_ceil_at_s_slash: prefix

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 33 - sd_ceil_at_sd

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 34 - sd_ceil_at_sd_slash

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 35 - sd_ceil_at_su

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 36 - sd_ceil_at_su_slash

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 37 - sd_ceil_at_s_di

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 38 - sd_ceil_at_s_di_slash

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 39 - sd_ceil_at_sdi

expecting success: test 's/d/' = "$(git rev-parse --show-prefix)"
+++ git rev-parse --show-prefix
error: isatty 2 (0000000000000000 0000000000000000)
error: isatty 1 (0000000000000000 0000000000000000)
error: isatty 0 (0000000000000000 0000000000000000)
error: isatty: 0 0 0
++ test s/d/ = s/d/
+ test_eval_ret_=0
+ want_trace
+ test t = t
+ test t = t
+ set +x
ok 40 - sd_ceil_at_sdi_slash

# passed all 40 test(s)
1..40
```


Love it


wind-dom 这个库好像没有用到了，忘记删除了


Arg, indeed 👍


empd_bugfix_rcoating (nmerket) - 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.png)


@estudiogenius Can you please open a ticket ? So we don't lose track of this.


Add PKGBREAK and PKGREP to all sub packages, pointing to `qemu-user-static<=currver` in which `currver` is the version currently available in the repository.


@wufeifei ??


a example of erlang gen_server


done


@lornat75 @pattacini  The reason why I did so is because I wanted a linear backoff in the polling policy of the module. If the resource is not available, then I want to wait more and more. But I understand that it feels a bit weird when this whole procedure has a time out. I agree with both that 0.001 is too small.
I will just remove the time out.


write


:lollipop:


add jihyun's information


This comment for first commit )


thanx, I just reverted the commit.


TaskCluster: @petemoore does not have permission to trigger tasks.


...many thanks


@stamparm Nothing, Very timely :)


data.GRACE doesn't give rendering hints
See: https://github.com/rism-ch/verovio/issues/403


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1922](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=21528&buildTypeId=ota_plus_RviSotaServer_Ci) outcome was **SUCCESS**
Summary: Tests passed: 306, ignored: 4 Build time: 00:17:02


What does CMake report?

```
Configuring LMMS
--------------------------
* Project version             : 1.2.0-rc2
*   Major version             : 1
*   Minor version             : 2
*   Release version           : 0
*   Stage version             : rc2
*   Build version             : 0
```


Hi Vincent,

It was just a quick fix for a Jekyll test app.

I changed the gems to fit my other project, as your gemspec replaced my defined later versioned gems.

I'm not sure how to rewrite the gem versions to allow for more recent ones, while still having a minimum defined version.


Why did you move the TextInputEditText to a different else if?


@lolmaxlik а почему нет? Я ж не собираюсь это говно отсылать куда-то на ревью. Мне с гитхаба удобнее было.


Note to self: naming convention


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


Its because since you don't have the lib you can't do TextInputEditText.class?


TaroEnterprise


Sorry, on my mobile, so premature send.

I think the latest Jekyll version is better than older ones, especially with the gem based themes.

As for Bundler, I just updated that one to the latest version out of habit.

Hope that answers your questions.


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


### Lipsum really?


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1923](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=21539&buildTypeId=ota_plus_RviSotaServer_Ci) is now running


### Lipsum Really?

Hahaha


o no


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1924](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=21541&buildTypeId=ota_plus_RviSotaServer_Ci) is now running


Hi Vondele,

This seems to be interesting patch, can you please elaborate it?

I can see the result is a type of a pattern somehow getting generated from SPSA tuning, finally, you will take the average of all values ?


@mdoering @MattBlissett
Could I please ask for your review of this change? The IPT uses CSVReader often but doesn't call .close(). I believe it could be the root cause of issue #1311, hence the reader's BufferedReader isn't being closed. As part of your review, I'd also be interested in finding out
1. whether the CSVReader instances are being properly closed in other places/projects?
2. whether the CSVReader.close() is sufficient - are there other streams being left open for example?

Thanks for your assistance


thanks to @wetliu 's initial implementation, the Parameters class is almost there.
the driver (test code) is located at tests/bfs/test_parameters.cu (compiled with ` nvcc test_parameters.cu ../../gunrock/util/error_utils.cu -o ./bin/test_parameters_8.0_x86_64 --std=c++11 -I"../.." -Xcompiler -Wall` under `tests/bfs`).


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1924](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=21541&buildTypeId=ota_plus_RviSotaServer_Ci) outcome was **FAILURE**
Summary: Compilation error: Scala compiler (new) Build time: 00:04:39


С чисто синтаксической точки зрения на диаграмме случаев использования неплохо бы (но не обязательно) границу системы (прямоугольник, внутри которого все use case-ы, а снаружи --- все акторы), на диаграмме активностей --- конечный узел, явно отмечающий окончание процесса. И ещё слияние потоков (горизонтальная черта) ожидает наличие токенов исполнения на ВСЕХ входных связях, что может не соответствовать твоим ожиданиям, проверь, пожалуйста.

И для диаграмм нужны исходные файлы, ссылки или что-то такое, не в графическом редакторе же их редактировать.


@absimaldata I don't think the SPSA tuning actually worked, results are just wandering around in the allowed interval. I assume some of the SPSA parameters need to have better settings.


Minor suggestion: try to stay away from inlining this kind of stuff, separate it out to a function or resolve it to a variable before you get to this point so that you can instead write:

```
return (
  <table className="grid-container">
    { tableRows }
  </table>
);
```


This makes sense! Nice!


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1925](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=21545&buildTypeId=ota_plus_RviSotaServer_Ci) is now running


I was about to ask the same, have you put the default values for ck and rk?


Typo: Should be 'than' instead of 'then'.


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1923](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=21539&buildTypeId=ota_plus_RviSotaServer_Ci) outcome was **FAILURE**
Summary: Tests passed: 57; compilation error: Scala compiler in Test (new) Build time: 00:10:25


@gorhill But the $websocket modifier works with just uBO no need of uBO extra.


I used a larger than default value for, I believe, ck .


We could provide some information here to the user about what's wrong.


And here, too.


1. This code seems to be useless, as those variables are not used anyhow:
```
IFS='-' read -ra ADDR <<< "$(hostname)"
CLUSTER_NAME="${ADDR[0]}"
```
I guess @foxish, original author of it, might add some light, but this should not affect you anyhow.

2. `while read -ra LINE; do` does expect script to have some input from /work-dir/peer-finder, if you are running with no input you would get stuck. Script is not started from shell, only on successful run of peer-finder. Try to run all init-containers by hand with all parameters and look at the output. This helped me to debug issues.

3. Do StorageClass and PVC work for you the way you want in general? I've no experience with aws-ebs provisioner, so I would advise you to address this issue in  main kubernetes repo


We do allow `null` here, but not if it's returned by a `Callable`. We should handle them the same way.


@TasneemBohra android studio just modified two files for me:
build.gradle
=>         classpath 'com.android.tools.build:gradle:2.2.3' instead of         classpath 'com.android.tools.build:gradle:1.0.0'

and

gradle-wrapper.properties
distributionUrl=https\://services.gradle.org/distributions/gradle-2.14.1-all.zip instead of distributionUrl=https\://services.gradle.org/distributions/gradle-2.2.1-all.zip

Maybe it helps you


These could both be final, no?


And they could both be simple `HashMap`s.


I guess you can add it to the linter for any specific project that needs it.


Thanks, Gergely, noted! I'm just using it as a starting point. We will probably shift things around substantially depending on how many talks we accept for the conference.

We were considering having 15 minute talking slots with 5 minutes for questions. This has worked rather well at a number of academic conferences that I have been to. 15 minutes seems to work well for audience attention span. We might go for 20 minute talking with 5 minute questions too. Don't want to go longer than that though.

We might also drop the final session (17:55 to 19:10) since by then I imagine that most people will have a serious case of conference fatigue.

Would you advise on longer coffee breaks? 30 minutes seems to be about right to me. And an hour for lunch should be ample.


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1925](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=21545&buildTypeId=ota_plus_RviSotaServer_Ci) outcome was **FAILURE**
Summary: Tests passed: 57; compilation error: Scala compiler in Test (new) Build time: 00:10:39


> As I said, it's currently messy needing to delete the intermediate files. And, doing "make" after "make ota" (after editing some source file) is also not currently working.

Then probably something else should be changed, instead of just making copy of the build dir to contain the very same content.

> 512k target uses different build options so should go in build-512k.

Yes, 512k is at all interesting, because there were questions if it's possible to support it still, and it was shown that yes, it's possible. But actually supporting it along would require someone who really needs it to maintain it further, in particular to make this and other changes.


@ToporBigBots Use the chat command `/login [password]`


heatingcoil_propane_bugfix (nmerket) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2382 of 2382 tests passed, 0 test warnings)

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


Oops ... :) I appreciate how many ways you got in touch with me to let me know. I was asleep :) Fixed in 6a68b95


Never go full retard


Let me look at this today.  /Thank you for the catch


heatingcoil_propane_bugfix (nmerket) - 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.png)


Dear All;

Thank you for explanation and quick answer. But I have no experience with Visual Studio or Sharpdevelop. Do you have any windows based software tool to install STF-Exporter 2017 version.

If exist, could you send me software tool or web page link.

Thanks you,

Best Regards,

İsmet HIZYOLU

Electrical-Electronics Engineer

Beytepe 1815. Street

No:46 Çankaya/ANKARA

Ph    :+90 312 440 87 13

Fax   :+90 312 440 87 38

Gsm :+90 530 110 82 20

web : www.se-naz.com <http://www.se-naz.com/>

From: Kyle Morin [mailto:notifications@github.com]
Sent: Tuesday, January 3, 2017 6:58 PM
To: kmorin/STF-Exporter <STF-Exporter@noreply.github.com>
Cc: ismethi <ihizyolu@se-naz.com>; Mention <mention@noreply.github.com>
Subject: Re: [kmorin/STF-Exporter] add wix installer for 2016 and 2017 (8dea105)

@ismethi <https://github.com/ismethi>  you have to compile the source code using a tool of your choice. Either Visual Studio or Sharpdevelop

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <https://github.com/kmorin/STF-Exporter/commit/8dea105740c5765b50c651828927fc9d351c0ad3#commitcomment-20348188> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AXhwbBGlpYJ7oQGo1UnqrVj2XP2lKUU6ks5rOnAfgaJpZM4JpDQ6> .  <https://github.com/notifications/beacon/AXhwbGgR-PZQcMoBFroKs4a2hiTVfzUpks5rOnAfgaJpZM4JpDQ6.gif>


Corrects "shortcode" usage.

Fixes #2889.


This won't support the commit you mention as written. .


@kmorin Thank you for explanation and quick answer. But I have no experience with Visual Studio or Sharpdevelop. Do you have any windows based software tool to install STF-Exporter 2017 version.

If exist, could you send me software tool or web page link.


https://www.pivotaltracker.com/story/show/137011895

Testing for Pivotal Tracker


> We were considering having 15 minute talking slots with 5 minutes for questions. This has worked rather well at a number of academic conferences that I have been to. 15 minutes seems to work well for audience attention span. We might go for 20 minute talking with 5 minute questions too. Don't want to go longer than that though.

We planned to have 18 min talk + 2 min QA like at the useR! conferences, but had to stick with 15 min talks and no questions at all due to delays and the tight schedule :( Anyway, 15+5 seems to be right -- as if some sessions do not receive questions, you have the flexibility to allow others go a bit longer etc.

> We might also drop the final session (17:55 to 19:10) since by then I imagine that most people will have a serious case of conference fatigue.

Yeah, that makes sense. At Budapest, we really needed that as we not only have the conf talks, but also the workshops and a dataviz contest on the same day -- but attendants were extremely tired by the end of the day, although they did not seem to be much worried about this fact :) And even stayed for a few drinks after the conference. But as you moved the workshops to the previous day(s), there's no need to have such a long conf day, I agree.

> Would you advise on longer coffee breaks? 30 minutes seems to be about right to me. And an hour for lunch should be ample.

30 mins is OK for coffee, but a longer break would allow you more flexibility with delays in the schedule. If the schedule is not too tight, that should be totally OK, just like an hour for lunch. The only problem we had with the latter was that serving was slow, so some folks received the food like 15 mins before the end of the lunch break :(


@jaroel Jenkins CI reporting about code analysis
See the full report here: http://jenkins.plone.org/job/package-plone.api/20/violations
```
src/plone/api/content.py:269:1: C901 'delete' is too complex (15)
src/plone/api/content.py:361:1: C901 '_wf_transitions_for' is too complex (13)
src/plone/api/content.py:426:1: C901 'transition' is too complex (13)
src/plone/api/portal.py:284:13: Q000 Remove bad quotes.
src/plone/api/portal.py:285:13: Q000 Remove bad quotes.
src/plone/api/portal.py:326:13: Q000 Remove bad quotes.
```
Follow [these instructions](https://github.com/plone/jenkins.plone.org/blob/master/docs/source/run-qa-on-package.rst) to reproduce it locally.


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1926](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=21550&buildTypeId=ota_plus_RviSotaServer_Ci) is now running


Broken link: https://docs.getexponent.com/versions/unversioned/guides/changing-native-code.html
I guess the next version from v12.0.0 is not on the website yet.


![](https://github.trello.services/images/mini-trello-icon.png) [testing commits](https://trello.com/c/gSBfv97v/761-testing-commits)


This probably never gets called in a situation where the component wouldn't normally update anyway, for the record. (I'm assuming the goal of this was to force the component to update at some point)

Leftover from early experimentation?


why not
```
if r < 1 {
    return 1
}
```


just to add a desc


Do you know what you are running when the core dump occurs.


You no-good scum


Won't this be a problem (being an uninitialized variable) when the ``if (do_signal) {}``` is run?


addition of three numbers


Does this work for you?


ok thanks, will reverse argument order.

> On 03/01/2017, at 24:56 , jamshark70 <notifications@github.com> wrote:
>
> I use ContiguousBlockAllocator in at least one of my quark classes. Just confirming Julian's suspicion that it isn't really safe to assume it's an internal-only class.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or mute the thread.
>


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


LGTM


Thanks, I included your nickname! How to use?


This commit looks good. I have one remark, though. Bootstrap (or any other version) shouldn't be a part of our version control code since we might change its version. Otherwise, we simply hard-code a library version (example jQuery 2.0.0) and never use package managers at all. Instead we could:
a) access lib assets from their vendor folder (if possible)
b) write a simple build script which will transfer required files in specific directories


Do this commit and the previous one need to be mentioned in NEWS?
Not, if we think these classes and flags are private.
(though without documentation, there's no clear distinction between private/public anyway..)


Try using the default ones, I believe they will converge to a specific value, as it is a one variable.

If this doesnt work, another option left is CLOP.


orientation 100 means - that creature will use his current orientation ... not one set by us. (we've been told this long time ago- and it works fine).


TeamCity OTA+ :: rvi_sota_server :: migrations container [Build 119](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=21554&buildTypeId=ota_plus_RviSotaServer_MigrationsContainer) is now running


Imagine we have a screen sharing stream, in this situation we pass "config.video = true" but "that.hasVidedo()" returns false although we have video in screen sharing, so this line sets config.video to false and it prevents our screen sharing to subscribe, this is a major issue in playing shared screen.
sorry for bad english


Testing comment


fjghhgghhgkgggkkg
![screenshot](https://cloud.githubusercontent.com/assets/23654886/21641754/e46f0f98-d2a3-11e6-8ae2-0130afd6a5c7.gif)


TeamCity OTA+ :: rvi_sota_server :: migrations container [Build 119](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=21554&buildTypeId=ota_plus_RviSotaServer_MigrationsContainer) outcome was **SUCCESS**
Summary: Running Build time: 00:01:14


Hier wurden die Pfade der Bibliotheken mit geändert. Da es bei mir sonst nicht funktioniert hat musste ich die ändern. Das führt zu nervigen Fehlern.


hhjjhhg


I realized that since I’ve been in Canada for so long, I would be able to come with that conclusion which is some people who are privileged of having more than the necessities of life, its more likely to act carelessly about environment that surrounded them.


Fixes issue #41 by making sure that if the `fixedDate` is blank, the database recieves a `DBNull.Value`.
The problem with the previous code was that, to keep DateTime formatting consistent, it passed the `fixedDate` value `.ToString()` to the database, causing the intended null value to become `DBNull.Value.ToString()` and not a valid null.


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1926](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=21550&buildTypeId=ota_plus_RviSotaServer_Ci) outcome was **SUCCESS**
Summary: Tests passed: 305, ignored: 4 Build time: 00:15:47


more lover


Eh, it was meant to fix the odd view transition that we had on Metastruct, but it's only for when going down. Not sure if it would work for you, because it looks like Metastruct has some incompatibilities issues with your version of prone mod


Это перевод каретки же. Я после мержа постоянно меняю концы строк с линукс-стиля на виндосовский, дабы гит не считал это изменением.


Good Stuff.


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1927](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=21560&buildTypeId=ota_plus_RviSotaServer_Ci) is now running


heatingcoil_propane_bugfix (nmerket) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1200 of 1200 tests passed, 0 test warnings)

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


@montkiara コミットメッセージは、なんの作業をしたのかをちゃんと記載しましょう！
>first commit


@montkiara コミットメッセージは意味のあることを記載してください。
>13commit
http://postd.cc/how-to-write-a-git-commit-message/


fuck you


<!DOCTYPE html>

<title>TICKET RAISE</title>

<<link href="sample.css" rel="stylesheet" type="text/css">

<form name="frm1" onsubmit="return validate()">

ENTER TICKET DETAILS

	EMPLOYEE ID

	<input type="text"  name="uname" placeholder="ENTER NUMBERS ONLY"required pattern="[0-9]{6}" title="it should be of 6 digits"  />

	   EMPLOYEE NAME

	  <input type="text" size="20" placeholder="ENTER ALPHABETS ONLY" name="pass"required pattern="[A-Zz-a]{5,25}"  title="min 5 character"/>

	 select function:
     <select name="function1"   onchange="populatecity()">
       <option value="none">select...</option>
       <option value="IT">IT Infrastructure Mgmt</option>
       <option value="ADMIN">Admin</option>
      <option value ="TRAVEL">Travel and Transport</option>
      </select>

	 category:
     <select name="category" required  >
         <option value="none">select...</option>
     </select>

	    PRIORITY :
	  <input type="radio" name="priority" value="HIGH">High
	  <input type="radio" name="priority" value="MEDIUM">Medium
	  <input type="radio" name="priority" value="LOW">Low

	  Description:
	  <textarea  placeholder="TYPE REASON HERE" rows="2" cols="20">

		</textarea>

	   Raise date:
	   <input REQUIRED class="main" name="raisedate" type="Date"/>

	  ENTER YOUR MOBILE NUMBER:

	  <input type="text"  name="MOBILE NUMBER" required pattern="[0-9]{10}"
	  title="pls enter 10 digit mobile number" />

		multiple users/system impacted
		 <input type="checkbox" id="cbox1" value="first_checkbox">

	   <INPUT  TYPE= "SUBMIT" VALUE = "Raise Ticket" align="center"/>
	   <INPUT  TYPE= "reset" VALUE = "Clear" align="center" />

</form>


@montkiara  コミットメッセージは、何をしたのかをきちんと記載してください。日本語でも構いません。
http://postd.cc/how-to-write-a-git-commit-message/


@montkiara 空行は不要です。


@montkiara デフォルトコメントは削除してOKです！実務では削除しましょう。


- Make separate points for separate things
- Do not do comparisons with unrelated things unnecessarily
- Lists do have order, "dictionaries" don't. Pay attention to what the lecturer says, and use your common sense.


@montkiara  100万件レコードがあったらこのままだとまずいですね。。


@montkiara JSONは通常使わないので、削除してください。


@montkiara コーディング規約は目立った修正点はないのですが、コミットメッセージは気をつけてください。
http://postd.cc/how-to-write-a-git-commit-message/


Nice


This patch will hardly make it. **There can be many such cases in which depth is higher but not the best path to proceed.**


Did you test bskyb ?


TeamCity OTA+ :: rvi_sota_server :: ci [Build 1928](http://teamcity.prod01.internal.advancedtelematic.com:8111/viewLog.html?buildId=21563&buildTypeId=ota_plus_RviSotaServer_Ci) is now running


A better regexp perhaps is \\`[^.].*\\.org\\'\\|[0-9]+\\' so that backups like 20170101~ do not match.


fuck ytou


![](https://github.trello.services/images/mini-trello-icon.png) [add loading indicator](https://trello.com/c/6gvKbZ0j/93-add-loading-indicator)


> постоянно меняю концы строк

@alfacom, Это можно настроить в гите.


Points 519-523 don't make any sense. They were an example in the lecture. Either put them under an example point, or remove them.


Very impressive patch !

Just for position test, I hope this enables SF to solve this position now.

8/4nk2/1p3p2/1r1p2pp/1P1R1N1P/6P1/3KPP2/8 w - - bm Nd3;


this commit is a lie


TaskCluster: @greenkeeper[bot] does not have permission to trigger tasks.


Hi Fabian, if it's not any trouble a small test case would be good so I can have a look at it. But this change should only have an impact if you are using partials which you probably don't if your apps having troubles are very old.


that's good! shall we close https://github.com/fonttools/fonttools/issues/141 ?


From another perspective - most confs I go to have hour long talks or half
hour. People seem to like those lengths also. Talks shorter than that work
ok for single track events I guess but I prefer talks that are 30mins+ both
as an attendee and a speaker.

On Wed, 4 Jan 2017 at 11:49 Gergely Daróczi <notifications@github.com>
wrote:

> We were considering having 15 minute talking slots with 5 minutes for
> questions. This has worked rather well at a number of academic conferences
> that I have been to. 15 minutes seems to work well for audience attention
> span. We might go for 20 minute talking with 5 minute questions too. Don't
> want to go longer than that though.
>
> We planned to have 18 min talk + 2 min QA like at the useR! conferences,
> but had to stick with 15 min talks and no questions at all due to delays
> and the tight schedule :( Anyway, 15+5 seems to be right -- as if some
> sessions do not receive questions, you have the flexibility to allow others
> go a bit longer etc.
>
> We might also drop the final session (17:55 to 19:10) since by then I
> imagine that most people will have a serious case of conference fatigue.
>
> Yeah, that makes sense. At Budapest, we really needed that as we not only
> have the conf talks, but also the workshops and a dataviz contest on the
> same day -- but attendants were extremely tired by the end of the day,
> although they did not seem to be much worried about this fact :) And even
> stayed for a few drinks after the conference. But as you moved the
> workshops to the previous day(s), there's no need to have such a long conf
> day, I agree.
>
> Would you advise on longer coffee breaks? 30 minutes seems to be about
> right to me. And an hour for lunch should be ample.
>
> 30 mins is OK for coffee, but a longer break would allow you more
> flexibility with delays in the schedule. If the schedule is not too tight,
> that should be totally OK, just like an hour for lunch. The only problem we
> had with the latter was that serving was slow, so some folks received the
> food like 15 mins before the end of the lunch break :(
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/satRdays/satRday-Cape-Town-schedule/commit/92f6205cb1a5d65bbfeee99967842c2e99d7036c#commitcomment-20357632>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AGJ1gnvw_cdhe-X0yfwDxl01oX-llJdIks5rO4dEgaJpZM4LaX6a>
> .
>
--

Steph Locke

@SteffLocke <https://twitter.com/stefflocke> | LinkedIn
<http://uk.linkedin.com/in/stephanielocke/> | itsalocke.com | 07951 787 022
SQL Cardiff <http://www.meetup.com/Cardiff-SQL-Server-User-Group> | CaRdiff
R <http://www.meetup.com/Cardiff-R-User-Group/> | diffNET
<http://www.meetup.com/diff-NET/> | SQL Relay <http://sqlrelay.co.uk/>
Microsoft Data Platform MVP