THIRD PAGE (ADD ON)

1. USER CAN UPDATE THE NUMBER OF PERSON BOOKED
2 .USER CAN CHANGE TYPE OF CLASSES
3. USER CAN MODIFY THE NUMBER OF LUGGAGES
4. USER ARE ALLOWED TO CANCEL THEIR RESERVATION, OR UPDATE THEIR OWN PERSONAL DETAILS


:D


@nikorev Looks good. I am thinking bottom middle or bottom right as of position.


I don't have a machine with XInput 1.0.9 but no 1.4, but one of our users did. I can't explain it, but it's out there!

I also changed
mLoaded = mGetState != NULL && mSetState != NULL;

Made ensureLoaded, return mLoaded

And checked it before dereferencing it

DWORD XInputGamePadGetState(DWORD dwUserIndex, XINPUT_STATE* pState)
{
	if(gXInputLoader.ensureLoaded())
	{
		return gXInputLoader.mGetState(dwUserIndex, pState);
	}
	else
	{
		return 1167; //ERROR_DEVICE_NOT_CONNECTED
	}
}

So I don't crash now :-)


Still digging around....

Basically on Kltevzw the ril does not initialize it's self.  If you tap LTE it works great until restarted.  I'm sure it's something in the device tree.  But it alludes me.


FOURTH PAGE(SEAT)

1. CLIENT ARE PROVIDED THE LAYOUT OF THE FLIGHT SEAT (IF THE SEAT ARE ALREADY BOOKED BY OTHER CUSTOMERS, THEY ARE PROMPTED BY ALERT MESSAGES THAT PARTICULAR SEAT HAVE BEEN RESERVED, THEN THE LAYOUT WILL CHANGE THE COLOUR OF AVAILABILITY.)


LAST PAGE(SUMMARY)

1. USER ARE ABLE TO SEE THE DETAIL OF TICKET RESERVATION ON THAT DAY.
2. USER ARE ABLE TO PAY THE WHOLE PAYMENT NEEDED.


Using ecto as a git dep didn't work out?


This line doesn't make sense for pirates that refuse to accept a bribe.


HVACWaterToAirMultiSpeedHP_-#4093 (jasondegraw) - i386-Windows-7-VisualStudio-12: OK (1148 of 1148 tests passed)

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


Can you explain why do you stash here ?
That doesn't seems right


WinEquivalentLayer_#4625 (Nigusse) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: Tests Failed

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


Conferido e OK


Maybe from GetDoubleCanvasPointPix call GetDoubleCanvasPointPixVP rather than duplicate code?

What case did this fix?  Maybe skewed or polyconic charts or?  It seemed to work for me before this change.

We should use the Double variation here as:

void glChartCanvas::MultMatrixViewPort(ViewPort &vp)
{
    wxPoint2DDouble point;
    cc1->GetDoubleCanvasPointPixVP(vp, 0, 0, &point);
    glTranslatef(point.m_x, point.m_y, 0);

...


This will do 1_2_3_alpha instead of 123_alpha.


@andrewsmedina
Thanks!


Sweet


I wonder what happens if you try and name a new container the same as a completed container.


Nice!


back to v2


Você fez a internacionalização usando tradução direto na Xib, Existe outra forma de se fazer isso via código para os texto que não aparecem na Xib? Se sim, consegue fazer?


89976832-HPWH-fan-not-autosizing-#4693 (rraustad) - Win64-Windows-7-VisualStudio-12: OK (1649 of 1653 tests passed)

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


Criou um array para cada tipo, já pensou em Herança e/ou dicionário?


The unit testing doesn't cover the case, which Employee has a department which department contains an employee. In this case, the parser won't work.


precisa definir vários atributos media? Olha a documentação que tem uma forma mais simples.


delete commented-out part?


Caso um dos vetores estiver vazio você mostrará uma sessão em branco? E os outros tipos de mídias?


I removed the whitespace from the shader strings which yields this:
http://pastebin.com/zxuQcHEU


Oh, that's an easy trap to fall into.  I'll have to remember that. Good to go.


Conferido e OK


prolly


Bro @zakyalvan, i just copied it from your code on Employee entity, but think i make mistake on the import statetement because i took package from Bean Validation API, and there's no such annotation there. Actually, I just used it to notice that it should not blank. I think it should be @NotNull @Size(min=1) regarding the Bean Validation API.


This commit is "gone" -- I rebased and squashed see commit a6146334f92dfbbf74e067ef6f76cd46d74eb392


yay, you even updated the change log!


@ me why?


very LGTM


@sils1297 I think i did it :wink:


common use script to help work easily


Yeah, I was really surprised by this. I'm not sure if the AST_CHILDREN_CALL for CallExpr should be updated, but I certainly didn't want to do that at this point in the release.


Yes, you correct, i think should be @NotNull @Size(min=1) regarding Bean Validation API. I just copy-paste that code and not recheck it. I'm sorry...


should the other TextFields also have description, or remove this one?


Really? I can get MariaDB 10.0.17 source from http://mirror.jmu.edu/pub/mariadb/mariadb-10.0.17/source/mariadb-10.0.17.tar.gz .


@csware
Thanks for your information. I read it. :)


This bit of code is actually mine. I decided to add a description to this field and not the others because this one seemed less self-explanatory than the others.


This might be important in #53


rax retry tests


Where is the description of your progress?


Everything is set first in mobile networks... APN, CDMA Type, etc??? I'm sure of that. You aren't one of my build users... LOL.
But I did just do a quick scan for you (sometimes an outside look helps) and I was wondering if you have tried building without this revert: https://github.com/VanirAOSP/frameworks_opt_telephony/commit/ee9728f99f63fe91f873a9357861ac4e02dbd368

Sorry if it doesn't apply, I know jack-shit about any device specifics except the G2.


Tem outra forma de fazer? Que permita via código trabalhar com internacionalização? Desta forma que foi feita está bastante simples.


Forgot to give the README the .md extension


fixes #1 #2


Those lines are not the latest, [those](https://github.com/Narann/mupen64plus-video-rice/blob/master/src/OGLTexture.cpp#L73) are.

What branch are you pointing to?


Why has this been removed?


Muitos campos em comum entre os diversos tipos de mídia, que tal usar herança?


BTW, that device's overlay directory is useless now.


Well it should be possible and I managed to do it once in my own Mixin as well - don't know why it doesn't work for you...


1: M100 needs more reviewers
1: M101 signature is missing
1: M110 missing component name


1: D290 White spaces around docstring should be trimmed.
1: D400 First line should end with '.', not 's'
5: L102 copyright year is outdated, expected 2015 but got 2014
25:1: E402 module level import not at top of file
28:1: E402 module level import not at top of file
29:1: I101 Imported names are in the wrong order. Should be collect_user_info, get_email, get_user_info, isGuestUser
29:1: I100 Imports statements are in the wrong order. from invenio.legacy.webuser should be before from invenio.utils.url
29:1: E402 module level import not at top of file
30:1: E402 module level import not at top of file
31:1: E402 module level import not at top of file
32:1: I101 Imported names are in the wrong order. Should be CFG_BASE_URL, CFG_CERN_SITE, CFG_SITE_LANG, CFG_SITE_NAME, CFG_SITE_NAME_INTL, CFG_SITE_RECORD, CFG_SITE_SECURE_URL, CFG_SITE_SUPPORT_EMAIL, CFG_SITE_URL, CFG_WEBCOMMENT_ALLOW_COMMENTS, CFG_WEBCOMMENT_ALLOW_REVIEWS, CFG_WEBCOMMENT_AUTHOR_DELETE_COMMENT_OPTION, CFG_WEBCOMMENT_MAX_ATTACHED_FILES, CFG_WEBCOMMENT_MAX_ATTACHMENT_SIZE, CFG_WEBCOMMENT_NB_REPORTS_BEFORE_SEND_EMAIL_TO_ADMIN, CFG_WEBCOMMENT_USE_RICH_TEXT_EDITOR
32:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.utils.mail
32:1: E402 module level import not at top of file
33:28: E126 continuation line over-indented for hanging indent
48:1: I101 Imported names are in the wrong order. Should be create_html_select, get_html_text_editor
48:1: E402 module level import not at top of file
49:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.utils.html
49:1: E402 module level import not at top of file
50:1: E402 module level import not at top of file
51:1: I100 Imports statements are in the wrong order. from invenio.modules.access.engine should be before from invenio.modules.formatter
51:1: E402 module level import not at top of file
52:1: I101 Imported names are in the wrong order. Should be acc_get_role_id, acc_get_user_roles_from_user_info
52:1: I100 Imports statements are in the wrong order. from invenio.modules.access.control should be before from invenio.modules.access.engine
52:1: E402 module level import not at top of file
53:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from invenio.modules.access.control
53:1: E402 module level import not at top of file
55:1: E302 expected 2 blank lines, found 1
55: D203 Expected 1 blank line *before* class docstring, found 0
55: D400 First line should end with '.', not 'l'
58: D202 No blank lines allowed *after* method docstring, found 1
58: D400 First line should end with '.', not 'd'
58: D205 Blank line missing between one-line summary and description
93:13: F841 local variable 'last_comment_round_name' is assigned to but never used
99:139: E221 multiple spaces before operator
102:85: E231 missing whitespace after ','
102:87: E221 multiple spaces before operator
141:34: E127 continuation line over-indented for visual indent
153:13: E128 continuation line under-indented for visual indent
155:33: E203 whitespace before ':'
160:36: E225 missing whitespace around operator
161:168: E502 the backslash is redundant between brackets
161:57: E225 missing whitespace around operator
162:67: E127 continuation line over-indented for visual indent
165:13: E124 closing bracket does not match visual indentation
179:14: E127 continuation line over-indented for visual indent
181:14: E124 closing bracket does not match visual indentation
185: D401 First line should be imperative: 'Display', not 'Displays'
185: D205 Blank line missing between one-line summary and description
210: D400 First line should end with '.', not 'd'
210: D205 Blank line missing between one-line summary and description
245:26: E201 whitespace after '{'
245:45: E203 whitespace before ':'
245:22: E222 multiple spaces after operator
246:46: E203 whitespace before ':'
247:44: E203 whitespace before ':'
248:44: E203 whitespace before ':'
249:44: E203 whitespace before ':'
249:62: E261 at least two spaces before inline comment
249:63: E262 inline comment should start with '# '
250:44: E203 whitespace before ':'
250:62: E261 at least two spaces before inline comment
250:63: E262 inline comment should start with '# '
251:25: E124 closing bracket does not match visual indentation
261:13: F841 local variable 'last_comment_round_name' is assigned to but never used
295:106: E231 missing whitespace after ':'
295:143: E231 missing whitespace after ':'
296:32: E222 multiple spaces after operator
317:37: E225 missing whitespace around operator
337:13: E122 continuation line missing indentation or outdented
337:14: E201 whitespace after '{'
337:40: E203 whitespace before ':'
338:40: E203 whitespace before ':'
339:40: E203 whitespace before ':'
340:40: E203 whitespace before ':'
341:40: E203 whitespace before ':'
342:40: E203 whitespace before ':'
343:40: E203 whitespace before ':'
344:40: E203 whitespace before ':'
345:41: E203 whitespace before ':'
346:60: E225 missing whitespace around operator
347:40: E203 whitespace before ':'
348:13: E124 closing bracket does not match visual indentation
360:28: E128 continuation line under-indented for visual indent
361:28: E128 continuation line under-indented for visual indent
364: D400 First line should end with '.', not 'n'
364: D205 Blank line missing between one-line summary and description
403:35: E128 continuation line under-indented for visual indent
404:35: E126 continuation line over-indented for hanging indent
409:81: E225 missing whitespace around operator
409:100: E225 missing whitespace around operator
411:83: E225 missing whitespace around operator
434:105: E225 missing whitespace around operator
436:106: E225 missing whitespace around operator
442:110: E225 missing whitespace around operator
453:111: E271 multiple spaces after keyword
462:37: E126 continuation line over-indented for hanging indent
489:17: E127 continuation line over-indented for visual indent
489:33: E203 whitespace before ':'
490:33: E203 whitespace before ':'
491:33: E203 whitespace before ':'
501: D400 First line should end with '.', not 'n'
501: D205 Blank line missing between one-line summary and description
534:107: E231 missing whitespace after ':'
535:9: E266 too many leading '#' for block comment
569:94: E225 missing whitespace around operator
575:99: E225 missing whitespace around operator
590:31: E203 whitespace before ':'
591:16: E128 continuation line under-indented for visual indent
592:16: E128 continuation line under-indented for visual indent
592:31: E203 whitespace before ':'
593:16: E128 continuation line under-indented for visual indent
593:31: E203 whitespace before ':'
594:16: E128 continuation line under-indented for visual indent
595:16: E128 continuation line under-indented for visual indent
595:31: E203 whitespace before ':'
596:16: E128 continuation line under-indented for visual indent
596:31: E203 whitespace before ':'
597:16: E128 continuation line under-indented for visual indent
597:31: E203 whitespace before ':'
598:16: E124 closing bracket does not match visual indentation
601: D400 First line should end with '.', not 's'
601: D205 Blank line missing between one-line summary and description
610:55: E231 missing whitespace after ','
693:13: F841 local variable 'c_round_name' is assigned to but never used
694:13: F841 local variable 'c_restriction' is assigned to but never used
703:26: E201 whitespace after '{'
703:45: E203 whitespace before ':'
703:22: E222 multiple spaces after operator
704:46: E203 whitespace before ':'
705:44: E203 whitespace before ':'
706:44: E203 whitespace before ':'
707:44: E203 whitespace before ':'
708:44: E203 whitespace before ':'
709:44: E203 whitespace before ':'
710:44: E203 whitespace before ':'
711:44: E203 whitespace before ':'
712:44: E203 whitespace before ':'
713:25: E124 closing bracket does not match visual indentation
720:22: E201 whitespace after '{'
720:37: E203 whitespace before ':'
720:19: E222 multiple spaces after operator
721:42: E203 whitespace before ':'
722:36: E203 whitespace before ':'
723:36: E203 whitespace before ':'
725:36: E203 whitespace before ':'
726:36: E203 whitespace before ':'
727:36: E203 whitespace before ':'
728:36: E203 whitespace before ':'
732:9: E266 too many leading '#' for block comment
737:13: F841 local variable 'last_comment_round_name' is assigned to but never used
748:20: E127 continuation line over-indented for visual indent
755:35: E127 continuation line over-indented for visual indent
755:73: E221 multiple spaces before operator
764:132: E202 whitespace before ')'
765:33: E127 continuation line over-indented for visual indent
765:71: E221 multiple spaces before operator
766:140: E225 missing whitespace around operator
839:76: E261 at least two spaces before inline comment
847:275: E231 missing whitespace after ':'
848:163: E231 missing whitespace after ':'
881:38: E203 whitespace before ':'
881:62: E231 missing whitespace after ':'
883:38: E203 whitespace before ':'
883:61: E231 missing whitespace after ':'
884:38: E203 whitespace before ':'
884:63: E231 missing whitespace after ':'
886:35: E203 whitespace before ':'
893:9: E266 too many leading '#' for block comment
918:9: E266 too many leading '#' for block comment
1086:9: E122 continuation line missing indentation or outdented
1087:47: E203 whitespace before ','
1089:43: E225 missing whitespace around operator
1105: D401 First line should be imperative: 'print', not 'prints'
1105: D400 First line should end with '.', not 'm'
1113: D202 No blank lines allowed *after* method docstring, found 1
1113: D400 First line should end with '.', not 'n'
1113: D205 Blank line missing between one-line summary and description
1125:15: E221 multiple spaces before operator
1158: D400 First line should end with '.', not 'n'
1158: D205 Blank line missing between one-line summary and description
1176:15: E221 multiple spaces before operator
1178:9: E122 continuation line missing indentation or outdented
1179:9: E128 continuation line under-indented for visual indent
1180:9: E128 continuation line under-indented for visual indent
1197: D400 First line should end with '.', not 's'
1197: D205 Blank line missing between one-line summary and description
1217:22: E201 whitespace after '{'
1217:40: E203 whitespace before ':'
1218:40: E203 whitespace before ':'
1218:65: E202 whitespace before '}'
1223: D400 First line should end with '.', not 'r'
1223: D205 Blank line missing between one-line summary and description
1230:9: F841 local variable '_' is assigned to but never used
1239: D400 First line should end with '.', not 's'
1239: D205 Blank line missing between one-line summary and description
1258:22: E201 whitespace after '{'
1258:37: E203 whitespace before ':'
1258:19: E222 multiple spaces after operator
1259:42: E203 whitespace before ':'
1260:36: E203 whitespace before ':'
1261:36: E203 whitespace before ':'
1262:36: E203 whitespace before ':'
1263:36: E203 whitespace before ':'
1282:20: E222 multiple spaces after operator
1307:13: E122 continuation line missing indentation or outdented
1308:121: E502 the backslash is redundant between brackets
1309:28: E127 continuation line over-indented for visual indent
1310:100: E502 the backslash is redundant between brackets
1311:31: E127 continuation line over-indented for visual indent
1312:238: E271 multiple spaces after keyword
1321:50: E251 unexpected spaces around keyword / parameter equals
1321:52: E251 unexpected spaces around keyword / parameter equals
1356: D400 First line should end with '.', not 's'
1356: D205 Blank line missing between one-line summary and description
1374:22: E201 whitespace after '{'
1374:37: E203 whitespace before ':'
1374:19: E222 multiple spaces after operator
1375:42: E203 whitespace before ':'
1376:36: E203 whitespace before ':'
1377:36: E203 whitespace before ':'
1378:36: E203 whitespace before ':'
1379:36: E203 whitespace before ':'
1389:13: E128 continuation line under-indented for visual indent
1428:1: E128 continuation line under-indented for visual indent
1429:50: E251 unexpected spaces around keyword / parameter equals
1429:52: E251 unexpected spaces around keyword / parameter equals
1470:35: E203 whitespace before ':'
1470:42: E225 missing whitespace around operator
1471:35: E203 whitespace before ':'
1471:41: E225 missing whitespace around operator
1486: D400 First line should end with '.', not 'd'
1486: D205 Blank line missing between one-line summary and description
1493:22: E201 whitespace after '{'
1493:37: E203 whitespace before ':'
1493:19: E222 multiple spaces after operator
1494:42: E203 whitespace before ':'
1495:36: E203 whitespace before ':'
1496:36: E203 whitespace before ':'
1497:36: E203 whitespace before ':'
1498:36: E203 whitespace before ':'
1502:51: E221 multiple spaces before operator
1513:101: E222 multiple spaces after operator
1517: D401 First line should be imperative: 'Create', not 'Creates'
1517: D290 White spaces around docstring should be trimmed.
1517: D205 Blank line missing between one-line summary and description
1540:15: E221 multiple spaces before operator
1580: D400 First line should end with '.', not 'e'
1580: D200 One-line docstring should not occupy 3 lines
1606:19: E225 missing whitespace around operator
1610:36: E203 whitespace before ':'
1613:35: E203 whitespace before ':'
1614:35: E203 whitespace before ':'
1619:39: E225 missing whitespace around operator
1621: D400 First line should end with '.', not 'e'
1636:18: E225 missing whitespace around operator
1667: D400 First line should end with '.', not ')'
1667: D205 Blank line missing between one-line summary and description
1691:27: E127 continuation line over-indented for visual indent
1694:27: E127 continuation line over-indented for visual indent
1717:13: E201 whitespace after '{'
1717:25: E203 whitespace before ':'
1718:25: E203 whitespace before ':'
1719:25: E203 whitespace before ':'
1720:25: E203 whitespace before ':'
1722:26: E203 whitespace before ':'
1723:25: E203 whitespace before ':'
1724:25: E203 whitespace before ':'
1725:25: E203 whitespace before ':'
1755: D401 First line should be imperative: 'output', not 'outputs'
1755: D290 White spaces around docstring should be trimmed.
1755: D400 First line should end with '.', not 'd'
1759: D401 First line should be imperative: 'prepare', not 'prepares'
1759: D290 White spaces around docstring should be trimmed.
1759: D400 First line should end with '.', not 'r'
1774: D401 First line should be imperative: 'output', not 'outputs'
1774: D290 White spaces around docstring should be trimmed.
1774: D400 First line should end with '.', not 'w'
1789:34: E203 whitespace before ':'
1797: D400 First line should end with '.', not 't'
1797: D205 Blank line missing between one-line summary and description
1804:9: F841 local variable '_' is assigned to but never used
1843:17: E128 continuation line under-indented for visual indent
1843:50: E225 missing whitespace around operator
1843:69: E225 missing whitespace around operator
1844:17: E128 continuation line under-indented for visual indent
1844:36: E203 whitespace before ','
1844:23: E231 missing whitespace after ':'
1845:17: E128 continuation line under-indented for visual indent
1845:49: E203 whitespace before ','
1846:17: E128 continuation line under-indented for visual indent
1847:17: E128 continuation line under-indented for visual indent
1853:17: E128 continuation line under-indented for visual indent
1853:50: E225 missing whitespace around operator
1853:69: E225 missing whitespace around operator
1854:17: E128 continuation line under-indented for visual indent
1854:36: E203 whitespace before ','
1854:23: E231 missing whitespace after ':'
1855:17: E128 continuation line under-indented for visual indent
1856:17: E128 continuation line under-indented for visual indent
1861: D400 First line should end with '.', not 't'
1861: D205 Blank line missing between one-line summary and description
1867:9: F841 local variable '_' is assigned to but never used
1901:49: E225 missing whitespace around operator
1901:68: E225 missing whitespace around operator
1902:54: E272 multiple spaces before keyword
1904:49: E225 missing whitespace around operator
1904:68: E225 missing whitespace around operator
1905:54: E272 multiple spaces before keyword
1911:13: E128 continuation line under-indented for visual indent
1911:39: E203 whitespace before ','
1912:13: E128 continuation line under-indented for visual indent
1913:13: E128 continuation line under-indented for visual indent
1914:13: E128 continuation line under-indented for visual indent
1915:13: E128 continuation line under-indented for visual indent
1916:13: E128 continuation line under-indented for visual indent
1921: D400 First line should end with '.', not 't'
1921: D205 Blank line missing between one-line summary and description
1971:73: E261 at least two spaces before inline comment
1971:73: E262 inline comment should start with '# '
1973:81: E261 at least two spaces before inline comment
1973:81: E262 inline comment should start with '# '
1974:81: E261 at least two spaces before inline comment
1974:81: E262 inline comment should start with '# '
1975:81: E261 at least two spaces before inline comment
1975:81: E262 inline comment should start with '# '
1976:81: E261 at least two spaces before inline comment
1976:81: E262 inline comment should start with '# '
1977:81: E261 at least two spaces before inline comment
1977:81: E262 inline comment should start with '# '
1979:81: E261 at least two spaces before inline comment
1979:81: E262 inline comment should start with '# '
1980:81: E261 at least two spaces before inline comment
1980:81: E262 inline comment should start with '# '
1981:81: E261 at least two spaces before inline comment
1981:81: E262 inline comment should start with '# '
1982:81: E261 at least two spaces before inline comment
1982:81: E262 inline comment should start with '# '
1985:76: E261 at least two spaces before inline comment
1985:76: E262 inline comment should start with '# '
1987:84: E261 at least two spaces before inline comment
1987:84: E262 inline comment should start with '# '
1988:84: E261 at least two spaces before inline comment
1988:84: E262 inline comment should start with '# '
1989:84: E261 at least two spaces before inline comment
1989:84: E262 inline comment should start with '# '
1990:84: E261 at least two spaces before inline comment
1990:84: E262 inline comment should start with '# '
1991:84: E261 at least two spaces before inline comment
1991:84: E262 inline comment should start with '# '
1993:84: E262 inline comment should start with '# '
1994:84: E262 inline comment should start with '# '
1995:84: E262 inline comment should start with '# '
1996:84: E262 inline comment should start with '# '
1997:84: E262 inline comment should start with '# '
1999:84: E261 at least two spaces before inline comment
2002:65: E261 at least two spaces before inline comment
2002:66: E262 inline comment should start with '# '
2003:65: E261 at least two spaces before inline comment
2003:66: E262 inline comment should start with '# '
2004:66: E261 at least two spaces before inline comment
2004:66: E262 inline comment should start with '# '
2011:75: E261 at least two spaces before inline comment
2012:75: E261 at least two spaces before inline comment
2013:75: E261 at least two spaces before inline comment
2014:70: E261 at least two spaces before inline comment
2029:15: E128 continuation line under-indented for visual indent
2030:15: E128 continuation line under-indented for visual indent
2031:15: E128 continuation line under-indented for visual indent
2032:23: E211 whitespace before '('
2045:13: E122 continuation line missing indentation or outdented
2046:13: E122 continuation line missing indentation or outdented
2047:13: E122 continuation line missing indentation or outdented
2051:13: E122 continuation line missing indentation or outdented
2052:13: E122 continuation line missing indentation or outdented
2053:13: E122 continuation line missing indentation or outdented
2073:36: E225 missing whitespace around operator
2075:36: E225 missing whitespace around operator
2102: D400 First line should end with '.', not ','
2102: D205 Blank line missing between one-line summary and description
2114:37: E225 missing whitespace around operator
2114:86: E225 missing whitespace around operator
2126: D400 First line should end with '.', not ','
2126: D205 Blank line missing between one-line summary and description
2138:37: E225 missing whitespace around operator
2138:86: E225 missing whitespace around operator
2152:5: E303 too many blank lines (3)
2152: D400 First line should end with '.', not ','
2152: D205 Blank line missing between one-line summary and description
2164:37: E225 missing whitespace around operator
2164:86: E225 missing whitespace around operator
2176: D202 No blank lines allowed *after* method docstring, found 1
2176: D400 First line should end with '.', not ')'
2186:21: E126 continuation line over-indented for hanging indent
2189:26: E225 missing whitespace around operator
2225:9: E122 continuation line missing indentation or outdented
2226:9: E122 continuation line missing indentation or outdented
2227:9: E122 continuation line missing indentation or outdented
2228:9: E122 continuation line missing indentation or outdented
2229:9: E122 continuation line missing indentation or outdented
2230:9: E122 continuation line missing indentation or outdented
2231:9: E122 continuation line missing indentation or outdented
2232:9: E124 closing bracket does not match visual indentation
2235: D401 First line should be imperative: 'Print', not 'Prints'
2235: D400 First line should end with '.', not 'w'
2235: D205 Blank line missing between one-line summary and description
2257:15: E127 continuation line over-indented for visual indent
2257:109: E502 the backslash is redundant between brackets
2259:16: E127 continuation line over-indented for visual indent
2261:48: E225 missing whitespace around operator
2261:67: E225 missing whitespace around operator
2265: D401 First line should be imperative: 'Print', not 'Prints'
2265: D400 First line should end with '.', not 'w'
2265: D205 Blank line missing between one-line summary and description
2287:72: E221 multiple spaces before operator
2288:16: E127 continuation line over-indented for visual indent
2288:82: E502 the backslash is redundant between brackets
2288:44: E225 missing whitespace around operator
2288:63: E225 missing whitespace around operator
2292:81: E221 multiple spaces before operator
2293:20: E126 continuation line over-indented for hanging indent
2293:86: E502 the backslash is redundant between brackets
2293:48: E225 missing whitespace around operator
2293:67: E225 missing whitespace around operator
2297:79: E221 multiple spaces before operator
2298:20: E126 continuation line over-indented for hanging indent
2298:86: E502 the backslash is redundant between brackets
2298:48: E225 missing whitespace around operator
2298:67: E225 missing whitespace around operator
2302:16: E127 continuation line over-indented for visual indent
2306: D401 First line should be imperative: 'Print', not 'Prints'
2306: D400 First line should end with '.', not 'e'
2306: D205 Blank line missing between one-line summary and description
2333:15: E271 multiple spaces after keyword
2335: D202 No blank lines allowed *after* method docstring, found 1
2335: D400 First line should end with '.', not 'e'
2335: D205 Blank line missing between one-line summary and description
2373: D400 First line should end with '.', not 'r'
2415:78: E251 unexpected spaces around keyword / parameter equals
2415:80: E251 unexpected spaces around keyword / parameter equals
2416:78: E251 unexpected spaces around keyword / parameter equals
2416:80: E251 unexpected spaces around keyword / parameter equals
2417:79: E251 unexpected spaces around keyword / parameter equals
2417:81: E251 unexpected spaces around keyword / parameter equals
2418:55: E231 missing whitespace after ','
2418:78: E251 unexpected spaces around keyword / parameter equals
2418:80: E251 unexpected spaces around keyword / parameter equals
2426:22: E222 multiple spaces after operator
2461:9: E303 too many blank lines (3)
2524:34: E126 continuation line over-indented for hanging indent
2527:102: E502 the backslash is redundant between brackets
2527:77: E225 missing whitespace around operator
2527:96: E225 missing whitespace around operator
2532:98: E502 the backslash is redundant between brackets
2532:73: E225 missing whitespace around operator
2532:92: E225 missing whitespace around operator
2556:25: E127 continuation line over-indented for visual indent
2556:37: E203 whitespace before ':'
2557:37: E203 whitespace before ':'
2558:37: E203 whitespace before ':'
2559:37: E203 whitespace before ':'
2560:37: E203 whitespace before ':'
2561:37: E203 whitespace before ':'
2566:24: E261 at least two spaces before inline comment
2571:16: E127 continuation line over-indented for visual indent
2598:52: E126 continuation line over-indented for hanging indent


3: L102 copyright year is outdated, expected 2015 but got 2014


Интерпретатор не должен ничего знать о базе. Интерпретатор также не должен иметь жёсткой связи с командами. Порядок работы другой:

1. Вы создаёте объект базы.
2. Вы создаёте команды, которые знают об объекте базы.
3. Вы собираете команды в мап и передаёте этот мап в интерпретатор.


BatchInterpreter


Завести пакет интерпретатора


@TheImmortal this breaks the flavour, tho. Can't we make it priority but lower it's base power instead? Otherwise the "teleports behind you" loses all its sense :(


Actually my first version was exactly like that and it's not much harder to integrate, really. The only reason I did this is because this specific part of the code (installdriverpackage()) is actually only used by Ubuntu (afaicu from Tim's words) and so I thought there was not much point on keeping dead code lying around that is not very relevant anyway from a general perspective.

But it's a very good point that it will probably make future rebases harder, so I think I will change it too


Shouldn't this be

```python
        # if included from roles/role/meta/main.yml
        ansible.utils.path_dwim(basedir, os.path.join('..', '..', '..', 'roles', role))
```

instead?


My Emacs simply wouldn't load anything that was deferred.


Closes #12 since this passes CI testing.


cc @bramstein FYI


const null object ?


Well, to be specific, it wasn't loading my `dot-org.el`.  I didn't research exactly why much further, as there were other things I wanted to get done.  But I would like to revisit this change, as it seems like something that would be very good to have.


Is there a PR for such a new plugin? Should not be all 3 plugins (saphana, sapnw, vm-dump-metrics) pulled together?

(I am just asking if having just the two sap* plugins wont be insufficient for gathering SAP related info; I am fine to have just those two as - being a SAP noob - I dont know what in particular could be important information in the virt commands outputs)


После коммита надо полностью проверять заявляемую функциональность:
по новым ключам доступны новые значения.


You should be able to use the knockout mapping plugin: `ko.mapping.fromJS(options.customProperties)`


Wait, can you tell me the value of isN3DS?


Yes. What about calling ``add_extension`` in the SoC design instead of this hack? The parameter to ``add_extension`` could also be shared between different boards as it uses the FMC signal names.


That is because it returns a pointer to a resource. The client would have to check the boolean AND the pointer in your proposition. It would be redondant and have the client write more code.


one reason more to have that test added


@bnoordhuis I think this is a bug we need to fix. When a stream is no longer readable, for example because read() got an error Windows will reset that flag, thus making uv_is_readable return false, and also making uv_read_start return ENOTCONN.

There is also the case that on Windows you cannot call uv_read_start multiple times because you get EALREADY, you need to stop first.

I'll take a look at what's different and how we'd want to make it consistent cross platform.


Fixed by 0d522a157b5a5ef8e5d44b3c662fb40d845cb275, also closed #18


Hello, it seems to me that you are not testing existence of the file for lfn. Would you like to add that or should I merge right away?


I do think these other operators could be removed too

* The operator `(?)` is particularly problematic since it will collide with definitions from other frameworks.

* I've commented before that I don't think `<--` is necessary over a plain call to `Send` (I'm even more of that opinion now I've realized what a huge variety of cloud queues there are, and how abstractions over them are not necessarily going to implement `ISendPort`)

* That leaves `<||>` which I think is better replaced by a `Cloud.Parallel2` though I don't mind that one so much.


Boolean operations of `Flavor<T>` must have args `REP<T>` and `REP<T_>`.
Backend test of boolean operations contained calls like
`Flavor<double>::disjoint(REP<float>,REP<double>)`.
Such calles were redirected to
`Flavor<double>::disjoint(REP<double>,REP<double>)` by `std::pair` promotion.
This pull request fixes backend bool tests.

Possibly this is an argument that REP<T> should be a custom class
`template<typename T> class representation { T left; T right; }`
instead of `std::pair<T,T>`.


Förstår inte datamodellen. Ska kundens samtliga uppgifter verkligen sparas för varje tröjköp?

Tröja - Kund - Köp. Känns som att Köp borde ligga mellan Tröja och Kund på något sätt.


Empty data-bind


Consistency with using "expertId" instead of "userId"


Allrighty, thanks for the update.


Isn't this handled below?


I think of it as a bus crossbar, similar to what one would do for a traditional bus like Wishbone.
Traditional bus xbar: connect several standard masters to several standard peripherals.
LASMI xbar: connect several standard masters to several standard bank machines organized in controllers.
So it should belong in bus, not in core.


find . is necessary if you want relative paths in find output.

all the vars must be quoted to avoid problems if they contain spaces. but SRC is hardcoded, so it doesnt contains spaces or can be / by "misstake"

the rest of things has been fixed in git. feel free to review


isN3DS = 10


I considered the following:
opening_pos != -1 and closing_pos != -1: matching parentheses in pattern
closing_pos = -1: opening_pos has been looked for in pattern[:-1], so if opening_pos = -1 we cannot distinguish the usual case with no parentheses from the case in which an opening parenthesis is at the last position.
opening_pos = -1: we do know that the parentheses are not matching or not existent dependend on closing_pos


I will deploy all.
Need some more time
On 12 Mar 2015 21:18, "Ajit Pasi" <notifications@github.com> wrote:

> Do you have only two files in your entire application? I would like you to
> commit all the files you have here.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Sonampasi/placement-website-/commit/453b5721e9965335f6be2676b4cde09d9d79a819#commitcomment-10167223>
> .
>


Nice


ok


well written :)


Looks good!


wait, if `(closing_pos = -1) != (opening_pos = -1)` (thats an xor, so this represents both of the last two cases you named) don't we want to warn the user that we got an invalid number of parens?


yes. Usually there cannot be something that is not a file and not a dir so the check is futile. So the elif can be replaced by an else in theory. Anyway, we said it doesn't hurt to leave the check there. It's just really hard to test in a meaningful way.

Note that symlinks count as directories.


Ok, following what they told me upstream, i changed how we handle this M_PI undef hack, could you try to rebuild and tell me if that works ?


1) Чат так и не позволил мне написать сообщение. Требовал ввести имя.
2) Убери этих странных Person сбоку:) они только путают
3) Желательно выделить кк-то окно диалога - а то очень мрачно и непонятно


If ic_nr is always <= NR_IRQS this looks fine.


是先看一下这个：
https://github.com/yanyiwu/nodejieba/issues/16

请升级成 v0.2.9 看看是否还有问题。

然后就是建议有问题请到issue那边讨论。


@Godin Good point. I add that to my todo list.


This sort of hints at a recurring problem: units are being `Destroy()'d without first being declared Dead, meaning something is calling `Unit:Destroy()` at a wrong time.

I'm reluctant for us to shadow the problem by changing this invariant. Later during this function it will expect the unit to not be destroyed again, so we could potentially hit this error again.


@gengdaoping nodejieba的问题可以反馈给作者，我解答不了


Anyway, if we would check all cases: how would you continue?
 * throw and exception and fail
 * warn and continue with the pattern as it is
 * warn and change the pattern
     * remove the unmatched parenthesis
     * add an opening parenthesis to the beginning or a closing parenthesis to the end to match the unmatched one?


C'est quoi ce vieux truc foireux? x)


Once again this is seemingly an issue with bad state of the unit.

I would much prefer to fix the problem rather than mitigating it every place we find symptoms of it.


I think I'd throw, wasn't it something like errors shouldn't pass silently?


you actually don't need this row, as the socket.Receive already close the existing message and re initialize it. This row will actually exhaust the buffer pooling if enabled because you don't close the msg.

You should move this row to after new Msg();


I think I'm in favor of removing that check.


I think that whole function is dead code: AFAIK, it got replaced by the [mktaglist.py](https://github.com/wrye-bash/wrye-bash/blob/dev/scripts/mktaglist.py) script.


```
    Errors should never pass silently.
    Unless explicitly silenced.
    In the face of ambiguity, refuse the temptation to guess.
```


I think Tim wants us to throw.


sure it can be made optional! (but if defined and doesn't exist then should still throw an exception)


NO, I demonstrated that your check returns True and False once each in two cases that should fail.

my code works without needing the check because:
"()()" -> `closing_pos = pattern.find(closing_delimiter)` -> closing pos = 1
opening_pos = `pattern[:closing_pos].rfind(opening_delimiter)` = `pattern[:1].rfind(opening_delimiter)` = `"(".rfind(opening_delimiter)` -> opening_pos = 0


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


1: M111 unrecognized component name: general


Relevant for https://github.com/hbz/lobid/issues/39.


3: L102 copyright year is outdated, expected 2015 but got 2014


1: D290 White spaces around docstring should be trimmed.
1: D400 First line should end with '.', not 's'
5: L102 copyright year is outdated, expected 2015 but got 2014
25:1: E402 module level import not at top of file
28:1: E402 module level import not at top of file
29:1: I101 Imported names are in the wrong order. Should be collect_user_info, get_email, get_user_info, isGuestUser
29:1: I100 Imports statements are in the wrong order. from invenio.legacy.webuser should be before from invenio.utils.url
29:1: E402 module level import not at top of file
30:1: E402 module level import not at top of file
31:1: E402 module level import not at top of file
32:1: I101 Imported names are in the wrong order. Should be CFG_BASE_URL, CFG_CERN_SITE, CFG_SITE_LANG, CFG_SITE_NAME, CFG_SITE_NAME_INTL, CFG_SITE_RECORD, CFG_SITE_SECURE_URL, CFG_SITE_SUPPORT_EMAIL, CFG_SITE_URL, CFG_WEBCOMMENT_ALLOW_COMMENTS, CFG_WEBCOMMENT_ALLOW_REVIEWS, CFG_WEBCOMMENT_AUTHOR_DELETE_COMMENT_OPTION, CFG_WEBCOMMENT_MAX_ATTACHED_FILES, CFG_WEBCOMMENT_MAX_ATTACHMENT_SIZE, CFG_WEBCOMMENT_NB_REPORTS_BEFORE_SEND_EMAIL_TO_ADMIN, CFG_WEBCOMMENT_USE_RICH_TEXT_EDITOR
32:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.utils.mail
32:1: E402 module level import not at top of file
33:28: E126 continuation line over-indented for hanging indent
48:1: I101 Imported names are in the wrong order. Should be create_html_select, get_html_text_editor
48:1: E402 module level import not at top of file
49:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.utils.html
49:1: E402 module level import not at top of file
50:1: E402 module level import not at top of file
51:1: I100 Imports statements are in the wrong order. from invenio.modules.access.engine should be before from invenio.modules.formatter
51:1: E402 module level import not at top of file
52:1: I101 Imported names are in the wrong order. Should be acc_get_role_id, acc_get_user_roles_from_user_info
52:1: I100 Imports statements are in the wrong order. from invenio.modules.access.control should be before from invenio.modules.access.engine
52:1: E402 module level import not at top of file
53:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibrecord should be before from invenio.modules.access.control
53:1: E402 module level import not at top of file
55:1: E302 expected 2 blank lines, found 1
55: D203 Expected 1 blank line *before* class docstring, found 0
55: D400 First line should end with '.', not 'l'
58: D202 No blank lines allowed *after* method docstring, found 1
58: D400 First line should end with '.', not 'd'
58: D205 Blank line missing between one-line summary and description
93:13: F841 local variable 'last_comment_round_name' is assigned to but never used
99:139: E221 multiple spaces before operator
102:85: E231 missing whitespace after ','
102:87: E221 multiple spaces before operator
141:34: E127 continuation line over-indented for visual indent
153:13: E128 continuation line under-indented for visual indent
155:33: E203 whitespace before ':'
160:36: E225 missing whitespace around operator
161:168: E502 the backslash is redundant between brackets
161:57: E225 missing whitespace around operator
162:67: E127 continuation line over-indented for visual indent
165:13: E124 closing bracket does not match visual indentation
179:14: E127 continuation line over-indented for visual indent
181:14: E124 closing bracket does not match visual indentation
185: D401 First line should be imperative: 'Display', not 'Displays'
185: D205 Blank line missing between one-line summary and description
210: D400 First line should end with '.', not 'd'
210: D205 Blank line missing between one-line summary and description
245:26: E201 whitespace after '{'
245:45: E203 whitespace before ':'
245:22: E222 multiple spaces after operator
246:46: E203 whitespace before ':'
247:44: E203 whitespace before ':'
248:44: E203 whitespace before ':'
249:44: E203 whitespace before ':'
249:62: E261 at least two spaces before inline comment
249:63: E262 inline comment should start with '# '
250:44: E203 whitespace before ':'
250:62: E261 at least two spaces before inline comment
250:63: E262 inline comment should start with '# '
251:25: E124 closing bracket does not match visual indentation
261:13: F841 local variable 'last_comment_round_name' is assigned to but never used
295:106: E231 missing whitespace after ':'
295:143: E231 missing whitespace after ':'
296:32: E222 multiple spaces after operator
317:37: E225 missing whitespace around operator
337:13: E122 continuation line missing indentation or outdented
337:14: E201 whitespace after '{'
337:40: E203 whitespace before ':'
338:40: E203 whitespace before ':'
339:40: E203 whitespace before ':'
340:40: E203 whitespace before ':'
341:40: E203 whitespace before ':'
342:40: E203 whitespace before ':'
343:40: E203 whitespace before ':'
344:40: E203 whitespace before ':'
345:41: E203 whitespace before ':'
346:60: E225 missing whitespace around operator
347:40: E203 whitespace before ':'
348:13: E124 closing bracket does not match visual indentation
360:28: E128 continuation line under-indented for visual indent
361:28: E128 continuation line under-indented for visual indent
364: D400 First line should end with '.', not 'n'
364: D205 Blank line missing between one-line summary and description
403:35: E128 continuation line under-indented for visual indent
404:35: E126 continuation line over-indented for hanging indent
409:81: E225 missing whitespace around operator
409:100: E225 missing whitespace around operator
411:83: E225 missing whitespace around operator
434:105: E225 missing whitespace around operator
436:106: E225 missing whitespace around operator
442:110: E225 missing whitespace around operator
453:111: E271 multiple spaces after keyword
462:37: E126 continuation line over-indented for hanging indent
489:17: E127 continuation line over-indented for visual indent
489:33: E203 whitespace before ':'
490:33: E203 whitespace before ':'
491:33: E203 whitespace before ':'
501: D400 First line should end with '.', not 'n'
501: D205 Blank line missing between one-line summary and description
534:107: E231 missing whitespace after ':'
535:9: E266 too many leading '#' for block comment
569:94: E225 missing whitespace around operator
575:99: E225 missing whitespace around operator
590:31: E203 whitespace before ':'
591:16: E128 continuation line under-indented for visual indent
592:16: E128 continuation line under-indented for visual indent
592:31: E203 whitespace before ':'
593:16: E128 continuation line under-indented for visual indent
593:31: E203 whitespace before ':'
594:16: E128 continuation line under-indented for visual indent
595:16: E128 continuation line under-indented for visual indent
595:31: E203 whitespace before ':'
596:16: E128 continuation line under-indented for visual indent
596:31: E203 whitespace before ':'
597:16: E128 continuation line under-indented for visual indent
597:31: E203 whitespace before ':'
598:16: E124 closing bracket does not match visual indentation
601: D400 First line should end with '.', not 's'
601: D205 Blank line missing between one-line summary and description
610:55: E231 missing whitespace after ','
693:13: F841 local variable 'c_round_name' is assigned to but never used
694:13: F841 local variable 'c_restriction' is assigned to but never used
703:26: E201 whitespace after '{'
703:45: E203 whitespace before ':'
703:22: E222 multiple spaces after operator
704:46: E203 whitespace before ':'
705:44: E203 whitespace before ':'
706:44: E203 whitespace before ':'
707:44: E203 whitespace before ':'
708:44: E203 whitespace before ':'
709:44: E203 whitespace before ':'
710:44: E203 whitespace before ':'
711:44: E203 whitespace before ':'
712:44: E203 whitespace before ':'
713:25: E124 closing bracket does not match visual indentation
720:22: E201 whitespace after '{'
720:37: E203 whitespace before ':'
720:19: E222 multiple spaces after operator
721:42: E203 whitespace before ':'
722:36: E203 whitespace before ':'
723:36: E203 whitespace before ':'
725:36: E203 whitespace before ':'
726:36: E203 whitespace before ':'
727:36: E203 whitespace before ':'
728:36: E203 whitespace before ':'
732:9: E266 too many leading '#' for block comment
737:13: F841 local variable 'last_comment_round_name' is assigned to but never used
748:20: E127 continuation line over-indented for visual indent
755:35: E127 continuation line over-indented for visual indent
755:73: E221 multiple spaces before operator
764:132: E202 whitespace before ')'
765:33: E127 continuation line over-indented for visual indent
765:71: E221 multiple spaces before operator
766:140: E225 missing whitespace around operator
839:76: E261 at least two spaces before inline comment
847:275: E231 missing whitespace after ':'
848:163: E231 missing whitespace after ':'
881:38: E203 whitespace before ':'
881:62: E231 missing whitespace after ':'
883:38: E203 whitespace before ':'
883:61: E231 missing whitespace after ':'
884:38: E203 whitespace before ':'
884:63: E231 missing whitespace after ':'
886:35: E203 whitespace before ':'
893:9: E266 too many leading '#' for block comment
918:9: E266 too many leading '#' for block comment
1086:9: E122 continuation line missing indentation or outdented
1087:47: E203 whitespace before ','
1089:43: E225 missing whitespace around operator
1105: D401 First line should be imperative: 'print', not 'prints'
1105: D400 First line should end with '.', not 'm'
1113: D202 No blank lines allowed *after* method docstring, found 1
1113: D400 First line should end with '.', not 'n'
1113: D205 Blank line missing between one-line summary and description
1125:15: E221 multiple spaces before operator
1158: D400 First line should end with '.', not 'n'
1158: D205 Blank line missing between one-line summary and description
1176:15: E221 multiple spaces before operator
1178:9: E122 continuation line missing indentation or outdented
1179:9: E128 continuation line under-indented for visual indent
1180:9: E128 continuation line under-indented for visual indent
1197: D400 First line should end with '.', not 's'
1197: D205 Blank line missing between one-line summary and description
1217:22: E201 whitespace after '{'
1217:40: E203 whitespace before ':'
1218:40: E203 whitespace before ':'
1218:65: E202 whitespace before '}'
1223: D400 First line should end with '.', not 'r'
1223: D205 Blank line missing between one-line summary and description
1230:9: F841 local variable '_' is assigned to but never used
1239: D400 First line should end with '.', not 's'
1239: D205 Blank line missing between one-line summary and description
1258:22: E201 whitespace after '{'
1258:37: E203 whitespace before ':'
1258:19: E222 multiple spaces after operator
1259:42: E203 whitespace before ':'
1260:36: E203 whitespace before ':'
1261:36: E203 whitespace before ':'
1262:36: E203 whitespace before ':'
1263:36: E203 whitespace before ':'
1282:20: E222 multiple spaces after operator
1307:13: E122 continuation line missing indentation or outdented
1308:121: E502 the backslash is redundant between brackets
1309:28: E127 continuation line over-indented for visual indent
1310:100: E502 the backslash is redundant between brackets
1311:31: E127 continuation line over-indented for visual indent
1312:238: E271 multiple spaces after keyword
1321:50: E251 unexpected spaces around keyword / parameter equals
1321:52: E251 unexpected spaces around keyword / parameter equals
1356: D400 First line should end with '.', not 's'
1356: D205 Blank line missing between one-line summary and description
1374:22: E201 whitespace after '{'
1374:37: E203 whitespace before ':'
1374:19: E222 multiple spaces after operator
1375:42: E203 whitespace before ':'
1376:36: E203 whitespace before ':'
1377:36: E203 whitespace before ':'
1378:36: E203 whitespace before ':'
1379:36: E203 whitespace before ':'
1389:13: E128 continuation line under-indented for visual indent
1428:1: E128 continuation line under-indented for visual indent
1429:50: E251 unexpected spaces around keyword / parameter equals
1429:52: E251 unexpected spaces around keyword / parameter equals
1470:35: E203 whitespace before ':'
1470:42: E225 missing whitespace around operator
1471:35: E203 whitespace before ':'
1471:41: E225 missing whitespace around operator
1486: D400 First line should end with '.', not 'd'
1486: D205 Blank line missing between one-line summary and description
1493:22: E201 whitespace after '{'
1493:37: E203 whitespace before ':'
1493:19: E222 multiple spaces after operator
1494:42: E203 whitespace before ':'
1495:36: E203 whitespace before ':'
1496:36: E203 whitespace before ':'
1497:36: E203 whitespace before ':'
1498:36: E203 whitespace before ':'
1502:51: E221 multiple spaces before operator
1513:101: E222 multiple spaces after operator
1517: D401 First line should be imperative: 'Create', not 'Creates'
1517: D290 White spaces around docstring should be trimmed.
1517: D205 Blank line missing between one-line summary and description
1540:15: E221 multiple spaces before operator
1580: D400 First line should end with '.', not 'e'
1580: D200 One-line docstring should not occupy 3 lines
1606:19: E225 missing whitespace around operator
1610:36: E203 whitespace before ':'
1613:35: E203 whitespace before ':'
1614:35: E203 whitespace before ':'
1619:39: E225 missing whitespace around operator
1621: D400 First line should end with '.', not 'e'
1636:18: E225 missing whitespace around operator
1667: D400 First line should end with '.', not ')'
1667: D205 Blank line missing between one-line summary and description
1691:27: E127 continuation line over-indented for visual indent
1694:27: E127 continuation line over-indented for visual indent
1717:13: E201 whitespace after '{'
1717:25: E203 whitespace before ':'
1718:25: E203 whitespace before ':'
1719:25: E203 whitespace before ':'
1720:25: E203 whitespace before ':'
1722:26: E203 whitespace before ':'
1723:25: E203 whitespace before ':'
1724:25: E203 whitespace before ':'
1725:25: E203 whitespace before ':'
1755: D401 First line should be imperative: 'output', not 'outputs'
1755: D290 White spaces around docstring should be trimmed.
1755: D400 First line should end with '.', not 'd'
1759: D401 First line should be imperative: 'prepare', not 'prepares'
1759: D290 White spaces around docstring should be trimmed.
1759: D400 First line should end with '.', not 'r'
1774: D401 First line should be imperative: 'output', not 'outputs'
1774: D290 White spaces around docstring should be trimmed.
1774: D400 First line should end with '.', not 'w'
1789:34: E203 whitespace before ':'
1797: D400 First line should end with '.', not 't'
1797: D205 Blank line missing between one-line summary and description
1804:9: F841 local variable '_' is assigned to but never used
1843:17: E128 continuation line under-indented for visual indent
1843:50: E225 missing whitespace around operator
1843:69: E225 missing whitespace around operator
1844:17: E128 continuation line under-indented for visual indent
1844:36: E203 whitespace before ','
1844:23: E231 missing whitespace after ':'
1845:17: E128 continuation line under-indented for visual indent
1845:49: E203 whitespace before ','
1846:17: E128 continuation line under-indented for visual indent
1847:17: E128 continuation line under-indented for visual indent
1853:17: E128 continuation line under-indented for visual indent
1853:50: E225 missing whitespace around operator
1853:69: E225 missing whitespace around operator
1854:17: E128 continuation line under-indented for visual indent
1854:36: E203 whitespace before ','
1854:23: E231 missing whitespace after ':'
1855:17: E128 continuation line under-indented for visual indent
1856:17: E128 continuation line under-indented for visual indent
1861: D400 First line should end with '.', not 't'
1861: D205 Blank line missing between one-line summary and description
1867:9: F841 local variable '_' is assigned to but never used
1901:49: E225 missing whitespace around operator
1901:68: E225 missing whitespace around operator
1902:54: E272 multiple spaces before keyword
1904:49: E225 missing whitespace around operator
1904:68: E225 missing whitespace around operator
1905:54: E272 multiple spaces before keyword
1911:13: E128 continuation line under-indented for visual indent
1911:39: E203 whitespace before ','
1912:13: E128 continuation line under-indented for visual indent
1913:13: E128 continuation line under-indented for visual indent
1914:13: E128 continuation line under-indented for visual indent
1915:13: E128 continuation line under-indented for visual indent
1916:13: E128 continuation line under-indented for visual indent
1921: D400 First line should end with '.', not 't'
1921: D205 Blank line missing between one-line summary and description
1971:73: E261 at least two spaces before inline comment
1971:73: E262 inline comment should start with '# '
1973:81: E261 at least two spaces before inline comment
1973:81: E262 inline comment should start with '# '
1974:81: E261 at least two spaces before inline comment
1974:81: E262 inline comment should start with '# '
1975:81: E261 at least two spaces before inline comment
1975:81: E262 inline comment should start with '# '
1976:81: E261 at least two spaces before inline comment
1976:81: E262 inline comment should start with '# '
1977:81: E261 at least two spaces before inline comment
1977:81: E262 inline comment should start with '# '
1979:81: E261 at least two spaces before inline comment
1979:81: E262 inline comment should start with '# '
1980:81: E261 at least two spaces before inline comment
1980:81: E262 inline comment should start with '# '
1981:81: E261 at least two spaces before inline comment
1981:81: E262 inline comment should start with '# '
1982:81: E261 at least two spaces before inline comment
1982:81: E262 inline comment should start with '# '
1985:76: E261 at least two spaces before inline comment
1985:76: E262 inline comment should start with '# '
1987:84: E261 at least two spaces before inline comment
1987:84: E262 inline comment should start with '# '
1988:84: E261 at least two spaces before inline comment
1988:84: E262 inline comment should start with '# '
1989:84: E261 at least two spaces before inline comment
1989:84: E262 inline comment should start with '# '
1990:84: E261 at least two spaces before inline comment
1990:84: E262 inline comment should start with '# '
1991:84: E261 at least two spaces before inline comment
1991:84: E262 inline comment should start with '# '
1993:84: E262 inline comment should start with '# '
1994:84: E262 inline comment should start with '# '
1995:84: E262 inline comment should start with '# '
1996:84: E262 inline comment should start with '# '
1997:84: E262 inline comment should start with '# '
1999:84: E261 at least two spaces before inline comment
2002:65: E261 at least two spaces before inline comment
2002:66: E262 inline comment should start with '# '
2003:65: E261 at least two spaces before inline comment
2003:66: E262 inline comment should start with '# '
2004:66: E261 at least two spaces before inline comment
2004:66: E262 inline comment should start with '# '
2011:75: E261 at least two spaces before inline comment
2012:75: E261 at least two spaces before inline comment
2013:75: E261 at least two spaces before inline comment
2014:70: E261 at least two spaces before inline comment
2029:15: E128 continuation line under-indented for visual indent
2030:15: E128 continuation line under-indented for visual indent
2031:15: E128 continuation line under-indented for visual indent
2032:23: E211 whitespace before '('
2045:13: E122 continuation line missing indentation or outdented
2046:13: E122 continuation line missing indentation or outdented
2047:13: E122 continuation line missing indentation or outdented
2051:13: E122 continuation line missing indentation or outdented
2052:13: E122 continuation line missing indentation or outdented
2053:13: E122 continuation line missing indentation or outdented
2073:36: E225 missing whitespace around operator
2075:36: E225 missing whitespace around operator
2102: D400 First line should end with '.', not ','
2102: D205 Blank line missing between one-line summary and description
2114:37: E225 missing whitespace around operator
2114:86: E225 missing whitespace around operator
2126: D400 First line should end with '.', not ','
2126: D205 Blank line missing between one-line summary and description
2138:37: E225 missing whitespace around operator
2138:86: E225 missing whitespace around operator
2152:5: E303 too many blank lines (3)
2152: D400 First line should end with '.', not ','
2152: D205 Blank line missing between one-line summary and description
2164:37: E225 missing whitespace around operator
2164:86: E225 missing whitespace around operator
2176: D202 No blank lines allowed *after* method docstring, found 1
2176: D400 First line should end with '.', not ')'
2186:21: E126 continuation line over-indented for hanging indent
2189:26: E225 missing whitespace around operator
2225:9: E122 continuation line missing indentation or outdented
2226:9: E122 continuation line missing indentation or outdented
2227:9: E122 continuation line missing indentation or outdented
2228:9: E122 continuation line missing indentation or outdented
2229:9: E122 continuation line missing indentation or outdented
2230:9: E122 continuation line missing indentation or outdented
2231:9: E122 continuation line missing indentation or outdented
2232:9: E124 closing bracket does not match visual indentation
2235: D401 First line should be imperative: 'Print', not 'Prints'
2235: D400 First line should end with '.', not 'w'
2235: D205 Blank line missing between one-line summary and description
2257:15: E127 continuation line over-indented for visual indent
2257:109: E502 the backslash is redundant between brackets
2259:16: E127 continuation line over-indented for visual indent
2261:48: E225 missing whitespace around operator
2261:67: E225 missing whitespace around operator
2265: D401 First line should be imperative: 'Print', not 'Prints'
2265: D400 First line should end with '.', not 'w'
2265: D205 Blank line missing between one-line summary and description
2287:72: E221 multiple spaces before operator
2288:16: E127 continuation line over-indented for visual indent
2288:82: E502 the backslash is redundant between brackets
2288:44: E225 missing whitespace around operator
2288:63: E225 missing whitespace around operator
2292:81: E221 multiple spaces before operator
2293:20: E126 continuation line over-indented for hanging indent
2293:86: E502 the backslash is redundant between brackets
2293:48: E225 missing whitespace around operator
2293:67: E225 missing whitespace around operator
2297:79: E221 multiple spaces before operator
2298:20: E126 continuation line over-indented for hanging indent
2298:86: E502 the backslash is redundant between brackets
2298:48: E225 missing whitespace around operator
2298:67: E225 missing whitespace around operator
2302:16: E127 continuation line over-indented for visual indent
2306: D401 First line should be imperative: 'Print', not 'Prints'
2306: D400 First line should end with '.', not 'e'
2306: D205 Blank line missing between one-line summary and description
2333:15: E271 multiple spaces after keyword
2335: D202 No blank lines allowed *after* method docstring, found 1
2335: D400 First line should end with '.', not 'e'
2335: D205 Blank line missing between one-line summary and description
2373: D400 First line should end with '.', not 'r'
2415:78: E251 unexpected spaces around keyword / parameter equals
2415:80: E251 unexpected spaces around keyword / parameter equals
2416:78: E251 unexpected spaces around keyword / parameter equals
2416:80: E251 unexpected spaces around keyword / parameter equals
2417:79: E251 unexpected spaces around keyword / parameter equals
2417:81: E251 unexpected spaces around keyword / parameter equals
2418:55: E231 missing whitespace after ','
2418:78: E251 unexpected spaces around keyword / parameter equals
2418:80: E251 unexpected spaces around keyword / parameter equals
2426:22: E222 multiple spaces after operator
2461:9: E303 too many blank lines (3)
2524:34: E126 continuation line over-indented for hanging indent
2527:102: E502 the backslash is redundant between brackets
2527:77: E225 missing whitespace around operator
2527:96: E225 missing whitespace around operator
2532:98: E502 the backslash is redundant between brackets
2532:73: E225 missing whitespace around operator
2532:92: E225 missing whitespace around operator
2556:25: E127 continuation line over-indented for visual indent
2556:37: E203 whitespace before ':'
2557:37: E203 whitespace before ':'
2558:37: E203 whitespace before ':'
2559:37: E203 whitespace before ':'
2560:37: E203 whitespace before ':'
2561:37: E203 whitespace before ':'
2566:24: E261 at least two spaces before inline comment
2571:16: E127 continuation line over-indented for visual indent
2598:52: E126 continuation line over-indented for hanging indent


3: L102 copyright year is outdated, expected 2015 but got 2013


Incorrect javadoc, should have remained "Gets a set..."


oh yes youre right, overread a part


Maybe add "see in file sh/mind-tools-create-workspace-linux.sh" or report in the README the commands to export these environment variables. Personally, I need to add my login/password in proxy_url (proxy_url=<login>:<password>@<proxyname>:<port>.


agreed


Sorry for the delay.
Attached you'll find a screenshot.
Sometimes the query get aborted, but when it is ok, it returns a whole admin page.

Any ideas?

![screenshot 2015-03-13 12 31 14](https://cloud.githubusercontent.com/assets/4488122/6636891/ea18ccae-c97c-11e4-8110-5be06470e990.png)


@benjello The test "arrco_tranche_a_employeur" still doesn't pass since it has a dummy value of "1234".
The calculate returns "0", is it the right value?


Let's make reminder totally optional.

Also, I'll sanitize the reminder to remove all leading and trailing whitespaces.


fixed #10


I think you should add "cd sh".
The name of the script is not correct (mind-tools-install-release-full-linux.sh).


:-)

i'd be happy to take a pull request to bump the major version number and make the project Java8 only.


@cbenz: 0 is the right value

On Fri, Mar 13, 2015 at 11:32 AM Christophe Benz <notifications@github.com>
wrote:

> @benjello <https://github.com/benjello> The test
> "arrco_tranche_a_employeur" still doesn't pass since it has a dummy value
> of "1234".
> The calculate returns "0", is it the right value?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/benjello/openfisca-france/commit/686a7272c7c37a3ce4f815df59848e743aa29bac#commitcomment-10182646>
> .
>


Will int(flags, 16) skip over the leading '0x'?


Все окец вроде, проследи чтобы работало.


ok

On 13/03/2015 11:07, Kevin Rocard wrote:
> That is because it returns a pointer to a resource. The client would have to
> check the boolean AND the pointer in your proposition. It would be redondant and
> have the client write more code.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/krocard/parameter-framework/commit/25fceca3a49446b59ae3040f1fe0125727cc866d#commitcomment-10182256>.
>

--
David Wagner

PEG->IPG->EIG->cAVS (Audio CoE)->Toulouse MiddleWare IP Creation

complex != complicated
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number:  302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.


I guess it must do, given that this tests it!


The name of the script is not correct (mind-tools-install-release-full-linux.sh).


RIP ulf :(


Looks good to me - thanks.


Hi, I've added some tests to `test/clang-tests.el`. Could you take a look and give me your opinion, please? I had to disable the tests `company-clang-full-parse-c-mode` and `company-clang-full-parse-c++-mode` due to build system failures, and to force a push, but locally they build fine. Still trying to understand why...

`company-clang-full-parse-c++-mode` fails on [EMACS=emacs-snapshot] (https://travis-ci.org/company-mode/company-mode/jobs/54216263), but `company-clang-full-parse-c-mode` passes.

`company-clang-full-parse-c-mode` fails on [EMACS=emacs24] (https://travis-ci.org/company-mode/company-mode/jobs/54216262), but `company-clang-full-parse-c++-mode` passes.

**There is a major problem regarding the ability to disambiguate structs' members**. The candidate doesn't provide enough information to accomplish the task. A way to handle the issue is to exploit the "prefix" Clang uses as context to build the completions list (this is not the prefix of the candidate, but what the user wants to complete). There is no presence of that prefix in Clang's output, nor it is stored by company. Below there is a description of this situation.
```
$ cat > example.c << EOF
// example.c
struct test_my_struct_x {
  /** This is alfa from struct x */
  int alfa;
}
  /** This is struct x */
  test_struct_x;

struct test_my_struct_a {
  /** This is alfa from struct a */
  int alfa;
}
  /** This is struct a */
  test_struct_a;

struct {
  /** This is alfa from anonymous struct y */
  int alfa;
}
  /** This is anonymous struct y */
  test_anonymous_struct_y;

struct {
  /** This is alfa from anonymous struct b */
  int alfa;
}
  /** This is anonymous struct b */
  test_anonymous_struct_b;

void test() {
  // This context is at line 32, column 27.
  test_anonymous_struct_b.
}
EOF
$ cat example.c | clang -fsyntax-only -Xclang -code-completion-macros -x c -Xclang -code-completion-at=-:32:27 -
COMPLETION: alfa : [#int#]alfa
$ cat example.c | clang -fno-color-diagnostics -fsyntax-only -w -Xclang -ast-dump -Xclang -ast-dump-filter -Xclang alfa -x c -
Dumping test_my_struct_x::alfa:
FieldDecl 0x31e7970 <<stdin>:4:3, col:7> col:7 alfa 'int'
`-FullComment 0x3224dd0 <line:3:6, col:33>
  `-ParagraphComment 0x3224da0 <col:6, col:33>
    `-TextComment 0x3224d70 <col:6, col:33> Text=" This is alfa from struct x "

Dumping test_my_struct_a::alfa:
FieldDecl 0x31e7b90 <<stdin>:11:3, col:7> col:7 alfa 'int'
`-FullComment 0x3224ea0 <line:10:6, col:33>
  `-ParagraphComment 0x3224e70 <col:6, col:33>
    `-TextComment 0x3224e40 <col:6, col:33> Text=" This is alfa from struct a "

Dumping (anonymous struct)::alfa:
FieldDecl 0x32248a0 <<stdin>:18:3, col:7> col:7 alfa 'int'
`-FullComment 0x3224f70 <line:17:6, col:43>
  `-ParagraphComment 0x3224f40 <col:6, col:43>
    `-TextComment 0x3224f10 <col:6, col:43> Text=" This is alfa from anonymous struct y "

Dumping (anonymous struct)::alfa:
FieldDecl 0x3224ac0 <<stdin>:25:3, col:7> col:7 alfa 'int'
`-FullComment 0x3225040 <line:24:6, col:43>
  `-ParagraphComment 0x3225010 <col:6, col:43>
    `-TextComment 0x3224fe0 <col:6, col:43> Text=" This is alfa from anonymous struct b "

```
The AST is dumped using `alfa` as filter, which is the prefix of the candidate. The user was typing `test_anonymous_struct_b.`, and pressed \<F1> while on the candidate `alfa` in the popup. The candidate doesn't provide sufficient info to disambiguate `alfa` between different structs.

Part of what the user was typing, `test_anonymous_struct_b`, could be used as context to indirectly disambiguate `alfa`:
```
$ cat example.c | clang -fno-color-diagnostics -fsyntax-only -w -Xclang -ast-dump -Xclang -ast-dump-filter -Xclang test_anonymous_struct_b -x c -
Dumping test_anonymous_struct_b:
VarDecl 0x2808bb0 <<stdin>:23:1, line:28:3> col:3 used test_anonymous_struct_b 'struct (anonymous struct at <stdin>:23:1)':'struct (anonymous at <stdin>:23:1)'
`-FullComment 0x2808df0 <line:27:6, col:33>
  `-ParagraphComment 0x2808dc0 <col:6, col:33>
    `-TextComment 0x2808d90 <col:6, col:33> Text=" This is anonymous struct b "

```
Since `test_anonymous_struct_b` is defined by an anonymous struct, we have to locate the anonymous struct to identify the proper documentation. Solving this problem should lead to develop a "locate feature" to read comments directly from the files/buffer.


:heart:


refs #96


@Nateowami Ah, nice, I have recently been looking into Jasmine actually! That could come in quite useful.
And why haven't I been getting notifications on your activity!? My RSS plugin hasn't been updating I guess. :C

I'm thinking about rewriting my version of Backloader, as there are annoying little issues everywhere which drive me crazy, and it's just poorly written.  Any suggestions? Would you like me to contribute to your version? (I would add a configurable list with wildcard matching)

Also, we should probably continue this in an email. :P


'file://' worked in my end. Looking forward to your release


when using mpi keep in mind to uncomment NUMBER_SIMULATIONS in settings.h


If we had something like a filewriter on github pages, it would be easy to only load the latest release once and cache it locally in a file...


neat idea


JobScheduler is in kernel, so it's not available. We could move it. Then those who want to create page cache instances would have to provide it with a JobScheduler, though. Bit annoying, but I guess we can live with that.


matching?


Ну зачем это делать?
Ведь можно просто загрузить скрипты в конце html, и просто вызвать в конце скрипта функцию run(). Чисто и красиво.

А в ней уже прописать инициализацию всего что надо. Или даже просто в теле скрипта.


No, good spot


What is the reason for this commit, please?
Empty array as a parameter will be unsupported?


NewDir


@zenati Not sure if it's the best thing. Shouldn't we fix the config (or maybe the model ?) instead of handling such a weird case ?


Or should the developers only test and not create a build?


test


`homebrew-` redundant here. But let's decide if we actually want this function still.


should work now


This was useful information.
I don't see why the situations aren't realistic.
I have just had a problem because I didn't use models properly in a migration.
My migration failed when it was run with newer code that validated a field, which was not present for that migration.


It looks like your editor's fill-column may be set too low, resulting in spurious wrapping changes as here.  (In addition to the non-spurious intended change, I mean.)

I don't think you use Emacs, but the Emacs analogy - in case it helps - is that its default is 72, but I've configured it to be 79 for all my Calico work.


Если сделала новую страничку, не нужно хранить старую.


How can I apply this patch to existing `superagent 1.0.0` library?


Can you change it to something like libreplace*.so etc so it works with both old and new versions?


What about a `setNewValue(double)`?


Лучше использовать классы с понятными именами - если проект состоит не из одной странички, а из пары десятков, это можнет оказаться очень неудобным.


Storing steps outside the object does nothing about protecting from circ. refs, and documentation fro `remaining` method only confuses users: they might think that the example below (bad sample) should be working, while it's a leak no matter where we store coderefs:
```perl
use Mojo::Base -strict;
use Mojo::IOLoop::Delay;

sub leak {
  my $d = Mojo::IOLoop::Delay->new;
  $d->steps(sub { say "$d" });

  Mojo::IOLoop->reset;
  Mojo::IOLoop->one_tick;
}

leak();
```

So HUF in this case only slows down a code and can be overwritten with a simple line `has remaining => sub {[]};`  with the same effect.

What do u think about that?


все стили выносим в отдельный файл!


обрабатываем события в js.


@vala config looks like:
`component :newsletter_subscriptions,      :crud, model_type: NewsletterSubscription, namespaced: true`

You mean this?:
`component :newsletter_subscriptions,      :crud, model_type: NewsletterSubscription, namespaced: "true"`

Or changing the column `namespaced` form bool to int/string?


It's quite buggy, see https://github.com/nette/database/commit/d5aa567f2b524418af7daf83f68bde9879704b3a


These could be implemented in the API because there's no reason I can see that would be implementation specific.


ah wait I messed up....

there cannot be an else here. The code above is correct. Only yield a file if files is True and only yield a dir when dirs is True. The alternative would be:

```python
if files:
    if os.path.isfile(p):
        yield p
else:
    if os.path.isdir(p):
        yield p
```

to be honest, I'm not sure why coverage always criticizes a branch miss in the code though.
os.path.isdir(p) | dirs is True | case
------------- | ------------- | ------
True | True | usual case when glob-matching only dirs for every dir
True  | False | usual case when glob-matching only files for every dir
False | False | should be the case for every file if files is False and dirs is False
False | True | usual case when glob-matching only dirs for every file (although python ignores this case)


No, I think the config's DSL is OK. But why do we get a string here ? That's the thing we should fix. Don't you think so ?


dihhhhhhhhhh


Хороший тон подгружать скрипты в конце документа - тогда они выполнятся после загрузки DOM


Particularmente discordo dessa abordagem em particular.
Se o texto original é maior realmente deve ser mantido, mas o preenchimento acredito que deva respeitar o limite imposto pelo tamanho.

Supondo que um arquivo com esse conteúdo de exemplo:
```
abc
defghi
jklm
nopqrstuvxz
```

e queira preencher com ``` 0123456789 ``` até o limite de 10 caracteres a direita, o que eu espero é:
```
abc0123456
defghi0123
jklm012345
nopqrstuvxz
```

mas irei obter:
```
abc0123456789
defghi0123456789
jklm0123456789
nopqrstuvxz
```

Realmente acho também que não é um caso comum, mas possível, e nessa perspectiva acho que podemos repensar essa abordagem.


at http://localhost:3000/posts/new/ it can be chosen the wall_id and commit a post


Then the next year :)


well I guess I will find a solution withoug `#pragma: nocover`


После выхода и смены имени вся история стерлась. и смысл тогда в истории?


Exactly. I'm reading comments out of order here, I think :)


Just realized that you have also been working on that feature :(


Ketal ?


Thanks for your corrections :+1:


1: M111 unrecognized component name: general