To be more precise :
(*) Better menu button left/right alignment
=> in your changes I see mainly first child and last child but where is the menu button left/right fix ?

(*) Better first/last menu item alignment (padding)
=> is it for regular menu ? or side or both ?

(*) Better sidenav nav margin-top consistency in both resp and
not resp modes.


Actually the link referenced here is to solve a subtly different issue.


This should also be a paragraph instead of a div


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

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


strong tag


This will cause the banner to go out of the screen and to create a horizontal scroll-bar when the banner is displayed.
The fix is to set the width to 98% as the 1% left and right padding's are added to the width.


C'est aussi ce qu'il me semblait mais apparemment seul jQuery est définit, pas $ (ou alors j'ai pas bien testé). Après ici, c'est surtout un fallback, au cas où. Je peux le virer.


Most apps don't need to implement this method because local class references are destroyed with the activity and your activity should perform most cleanup during `onPause()` and `onStop()`. However, if your activity includes background threads that you created during `onCreate()` or other long-running resources that could potentially leak memory if not properly closed, you should kill them during `onDestroy()`.

```java
@Override
public void onDestroy() {
    super.onDestroy();  // Always call the superclass

    // Stop method tracing that the activity started during onCreate()
    android.os.Debug.stopMethodTracing();
}
```


This is quoting keywords and not other identifiers. `QualifiedName` is a dot-separated list of identifiers and identifiers appear without quotes unless they are keywords. For example:

```
  SELECT a FROM c
```

`a` and `c` are identifiers. This can also be written as:

```
  SELECT "a" FROM "c"
```

And if one of my column names is a keyword it can be written like:

```
  SELECT "select" FROM c
```

If you don't put double quotes around `select` it is treated as a keyword which causes a parse error.


Try removing mono-gmcs and see if that resolves the issue.


replace all these div for "btn-liserv-status" with paragraph


OK, I'll remove __props__ = ("format", "kmap")


s/s/se/


Fix parameter names. Like: (NSString*)withName --> (NSString*)name


caption-bold it's okay since the list is disabled, but change the class to our existing class called "text-strong"


Ah, did not know that.

Mm, okay that makes sense, I see that behavior now. But in that case, just removing the "\n" output at the end of each output causes that diff to return to `0` status. Which makes sense.
But then that makes `diff <echo blah blah blah) <(echo blah blah blah | ./mimic); echo $?` (i.e. same, without `\-n` flag) have a non-zero return code. I think that is fine though because `echo` default adding a new line is really just an implementation choice of theirs. I did look at the flags and didn't find anything particularly of interest over removing the new-line to `cout`.


I'll send a PR to fix.


there is a regression bug here, you have remove the creation of the dest using the sanitised netloc and replaced it with a function that breaks windows downloads...
a quick fix would be to take L539-L542 and put them into selt._extrn_path function.


Ok don't waste time on this Rocco.
I'll merge what I understand and we'll fix the rest afterwards if needed :)


Yeah, there's a check later to make sure it doesn't loop infinitely to catch this.  You'd have to do each molecule individually.


Weird, I've never had this problem. I don't have the trailing double slashes and I'm getting full path storage automatically for my "undo" dir (with `%` substitutions) and also for my "view" dir (with `=+` subs), and the "swap" dir doesn't  collide because Vim automatically picks the next available extension (`.swp`, `.swo`, `.swm` etc).

Funnily enough, I've never actually _seen_ anything in the "backup" dir, because Vim removes the backups after a successful overwrite (ie. due to `'backup'` and `'writebackup'`).


mkdir -p

so it will not fail if they already exist


It's looking really good!

I have a few suggestions:

- if `fixedSize` never changes, you might as well just put it in the template rather than as a computed property in the component.

- Instead of passing `Discourse.SiteSettings` to your loader, try `this.siteSettings` -- we inject site settings into components and prefer not to use constants like `Discourse` in new code.

- In your template, you can do `<div id={{divId}}` without the quotes around `{{divId}}`. I know it's a small detail but it helps :)

As to where to go next, a good step would be to think about how to remove the hardcoded configuration options such as `/6355419/Travel/Europe/France/Paris` and allow users to input them. I'm actually going to write a new tutorial on how to add site settings to a plugin soon to help you along with this!


tested and working


Wow !! Amazing calculations !! I love it !

I've Python 2.7.6 .. is it enough ??

I'll try my best to use your guide ! - If i still don't understand, i'll write here again.. Thank u so much !


Could you possibly give a detailed example showing controller, form and everything how this class works and say you have 5 post variables as an example?


oh, I had this backwards. Thanks.


TeamCity DNN JavaScript Libraries :: CI [Build 37](http://teamcity.engagesoftware.com/viewLog.html?buildId=305&buildTypeId=DnnJavaScriptLibraries_Ci) is now running


TeamCity DNN JavaScript Libraries :: CI [Build 38](http://teamcity.engagesoftware.com/viewLog.html?buildId=306&buildTypeId=DnnJavaScriptLibraries_Ci) is now running


TeamCity DNN JavaScript Libraries :: CI [Build 37](http://teamcity.engagesoftware.com/viewLog.html?buildId=305&buildTypeId=DnnJavaScriptLibraries_Ci) outcome was **SUCCESS**
Summary: Running Build time: 0:0:19


TeamCity DNN JavaScript Libraries :: CI [Build 38](http://teamcity.engagesoftware.com/viewLog.html?buildId=306&buildTypeId=DnnJavaScriptLibraries_Ci) outcome was **SUCCESS**
Summary: Running Build time: 0:0:9


No problem. I will soon be an SQL expert. :)


My memory is hazy, but iirc after some changes for another bugfix I got exceptions for cases where the orphan size was higher than the normal size.
Allowing orphan size to be higher than the regular size would make calculation more difficult because page number could decrease for more than one page. This looks like an esotheric use case, which I doubt would need to be supported. I think it was also not giving the results it needed.
Analysing the traceback I see that the assertion has an error, it should also allow equal size of orphan and size


When we switch from wiki to the other platform we discussed during the last meeting, can't we just do "find-replace" ?? =D


Just saw you updated the repo with a new commit that fixes the problem I was talking about.
Now it does prompt for an alternative version.


Will do!


1: M111 unrecognized component name: legacy


Hei @pei-jung that seems like a bug in LiferayPortlet class.

The method sendRedirect adds an attribute in the session to make sure that the redirect used in the method is the one that will be used.

I'll take a look at it and let you know.


25:1: I201 Missing newline before sections or imports.
27:1: I100 Imports statements are in the wrong order. from invenio.ext.arxiv should be before import pkg_resources
28:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, make_test_suite, run_test_suite


25:1: I201 Missing newline before sections or imports.
27:1: I100 Imports statements are in the wrong order. from invenio.ext.crossref should be before import pkg_resources
28:1: I101 Imported names are in the wrong order. Should be InvenioTestCase, make_test_suite, run_test_suite


28:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from sqlalchemy.exc


58:1: I100 Imports statements are in the wrong order. from ..errors should be before from ..models


39:1: I100 Imports statements are in the wrong order. from ..errors should be before from ..forms


1: D400 First line should end with a period (not 'd')
1: D205 1 blank line required between summary line and description (found 0)
35:1: E402 module level import not at top of file
36:1: E402 module level import not at top of file
37:1: F401 'urlparse' imported but unused
37:1: E402 module level import not at top of file
38:1: I100 Imports statements are in the wrong order. import socket should be before import urlparse
38:1: F401 'socket' imported but unused
38:1: E402 module level import not at top of file
39:1: I100 Imports statements are in the wrong order. import smtplib should be before import socket
39:1: F401 'smtplib' imported but unused
39:1: E402 module level import not at top of file
40:1: I100 Imports statements are in the wrong order. import re should be before import smtplib
40:1: E402 module level import not at top of file
41:1: I100 Imports statements are in the wrong order. import random should be before import re
41:1: F401 'random' imported but unused
41:1: E402 module level import not at top of file
42:1: I100 Imports statements are in the wrong order. import datetime should be before import random
42:1: E402 module level import not at top of file
44:1: F401 'Request' imported but unused
44:1: E402 module level import not at top of file
45:1: I201 Missing newline before sections or imports.
45:1: F401 'iteritems' imported but unused
45:1: E402 module level import not at top of file
46:1: I100 Imports statements are in the wrong order. from socket should be before from six
46:1: I201 Missing newline before sections or imports.
46:1: F401 'gaierror' imported but unused
46:1: E402 module level import not at top of file
47:1: I100 Imports statements are in the wrong order. import os should be before from socket
47:1: E402 module level import not at top of file
48:1: I100 Imports statements are in the wrong order. import binascii should be before import os
48:1: E402 module level import not at top of file
49:1: E402 module level import not at top of file
51:1: E402 module level import not at top of file
52:1: I101 Imported names are in the wrong order. Should be CFG_ACCESS_CONTROL_LEVEL_ACCOUNTS, CFG_ACCESS_CONTROL_LEVEL_GUESTS, CFG_ACCESS_CONTROL_LEVEL_SITE, CFG_ACCESS_CONTROL_LIMIT_REGISTRATION_TO_DOMAIN, CFG_ACCESS_CONTROL_NOTIFY_ADMIN_ABOUT_NEW_ACCOUNTS, CFG_ACCESS_CONTROL_NOTIFY_USER_ABOUT_NEW_ACCOUNT, CFG_BIBAUTHORID_ENABLED, CFG_CERN_SITE, CFG_INSPIRE_SITE, CFG_SITE_ADMIN_EMAIL, 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_WEBSESSION_ADDRESS_ACTIVATION_EXPIRE_IN_DAYS
52:1: F401 'CFG_WEBSESSION_ADDRESS_ACTIVATION_EXPIRE_IN_DAYS' imported but unused
52:1: F401 'CFG_SITE_NAME_INTL' imported but unused
52:1: F401 'CFG_SITE_RECORD' imported but unused
52:1: F401 'CFG_BIBAUTHORID_ENABLED' imported but unused
52:1: F401 'CFG_INSPIRE_SITE' imported but unused
52:1: F401 'CFG_SITE_SECURE_URL' imported but unused
52:1: E402 module level import not at top of file
53:6: E126 continuation line over-indented for hanging indent
76:1: E402 module level import not at top of file
77:1: E402 module level import not at top of file
80:1: I101 Imported names are in the wrong order. Should be gettext_set_language, wash_language, wash_languages
80:1: I100 Imports statements are in the wrong order. from invenio.base.i18n should be before from invenio.utils.serializers
80:1: F401 'wash_language' imported but unused
80:1: F401 'wash_languages' imported but unused
80:1: E402 module level import not at top of file
81:1: E402 module level import not at top of file
82:1: E402 module level import not at top of file
83:1: E402 module level import not at top of file
84:1: E402 module level import not at top of file
86:1: E402 module level import not at top of file
97:1: I100 Imports statements are in the wrong order. from invenio.modules.access.local_config should be before from sqlalchemy.exc
97:1: E402 module level import not at top of file
110:1: E302 expected 2 blank lines, found 1
110: D400 First line should end with a period (not 's')
110: D208 Docstring is over-indented
126:1: E302 expected 2 blank lines, found 1
126: D202 No blank lines allowed after function docstring (found 1)
173:5: E303 too many blank lines (2)
189:1: E302 expected 2 blank lines, found 1
189: D205 1 blank line required between summary line and description (found 0)
189: D208 Docstring is over-indented
205:42: E701 multiple statements on one line (colon)
206:42: E701 multiple statements on one line (colon)
213:22: E261 at least two spaces before inline comment
243:1: I100 Imports statements are in the wrong order. from invenio.ext.login should be before from invenio.modules.access.local_config
243:1: E402 module level import not at top of file
244:1: F999 redefinition of unused 'getUid' from line 189
244:1: E731 do not assign a lambda expression, use a def
247: D200 One-line docstring should fit on one line with quotes (found 2)
256:1: E302 expected 2 blank lines, found 1
256: D200 One-line docstring should fit on one line with quotes (found 3)
262:1: E302 expected 2 blank lines, found 1
262: D200 One-line docstring should fit on one line with quotes (found 3)
268:1: E302 expected 2 blank lines, found 1
268:40: E251 unexpected spaces around keyword / parameter equals
268:42: E251 unexpected spaces around keyword / parameter equals
268: D205 1 blank line required between summary line and description (found 0)
275:1: E302 expected 2 blank lines, found 1
275: D200 One-line docstring should fit on one line with quotes (found 3)
281:1: E302 expected 2 blank lines, found 1
289:1: E302 expected 2 blank lines, found 1
289: D205 1 blank line required between summary line and description (found 0)
310:1: E302 expected 2 blank lines, found 1
310: D209 Multi-line docstring closing quotes should be on a separate line
310: D205 1 blank line required between summary line and description (found 0)
323:1: E302 expected 2 blank lines, found 1
323: D400 First line should end with a period (not 't')
323: D208 Docstring is over-indented
339:1: E302 expected 2 blank lines, found 1
345:1: E302 expected 2 blank lines, found 1
355:1: E302 expected 2 blank lines, found 1
360:1: E302 expected 2 blank lines, found 1
368:1: E302 expected 2 blank lines, found 1
368: D205 1 blank line required between summary line and description (found 0)
368: D208 Docstring is over-indented
383:1: E302 expected 2 blank lines, found 1
383: D205 1 blank line required between summary line and description (found 0)
383: D208 Docstring is over-indented
398:1: E302 expected 2 blank lines, found 1
398: D209 Multi-line docstring closing quotes should be on a separate line
398: D400 First line should end with a period (not 'e')
398: D205 1 blank line required between summary line and description (found 0)
417: D202 No blank lines allowed after function docstring (found 1)
417: D400 First line should end with a period (not 'd')
417: D205 1 blank line required between summary line and description (found 0)
417: D208 Docstring is over-indented
418:9: E128 continuation line under-indented for visual indent
443:5: F841 local variable '_' is assigned to but never used
462:18: E261 at least two spaces before inline comment
464:74: E261 at least two spaces before inline comment
468:26: E261 at least two spaces before inline comment
470:26: E261 at least two spaces before inline comment
473:5: E303 too many blank lines (2)
490:23: E261 at least two spaces before inline comment
491:21: F821 undefined name 'uid'
494:1: E302 expected 2 blank lines, found 1
494: D400 First line should end with a period (not 'd')
494: D205 1 blank line required between summary line and description (found 0)
511:1: E302 expected 2 blank lines, found 1
521: D202 No blank lines allowed after function docstring (found 1)
521: D400 First line should end with a period (not 'r')
521: D205 1 blank line required between summary line and description (found 0)
537:1: E302 expected 2 blank lines, found 1
537: D202 No blank lines allowed after function docstring (found 1)
537: D400 First line should end with a period (not '1')
537: D200 One-line docstring should fit on one line with quotes (found 2)
549: D205 1 blank line required between summary line and description (found 0)
559:1: E302 expected 2 blank lines, found 1
573:1: E302 expected 2 blank lines, found 1
573: D209 Multi-line docstring closing quotes should be on a separate line
573: D400 First line should end with a period (not 'e')
573: D205 1 blank line required between summary line and description (found 0)
582:1: E302 expected 2 blank lines, found 1
582: D205 1 blank line required between summary line and description (found 0)
592:11: E127 continuation line over-indented for visual indent
597:1: E302 expected 2 blank lines, found 1
597: D209 Multi-line docstring closing quotes should be on a separate line
597: D400 First line should end with a period (not 'e')
597: D205 1 blank line required between summary line and description (found 0)
606:1: E302 expected 2 blank lines, found 1
606: D209 Multi-line docstring closing quotes should be on a separate line
606: D205 1 blank line required between summary line and description (found 0)
629:1: E302 expected 2 blank lines, found 1
629: D400 First line should end with a period (not ')')
629: D205 1 blank line required between summary line and description (found 0)
643:1: E302 expected 2 blank lines, found 1
643: D400 First line should end with a period (not ')')
643: D205 1 blank line required between summary line and description (found 0)
667:1: E302 expected 2 blank lines, found 1
667: D103 Missing docstring in public function
672:42: E261 at least two spaces before inline comment
674:1: E302 expected 2 blank lines, found 1
674: D103 Missing docstring in public function
680: D400 First line should end with a period (not 'y')
680: D205 1 blank line required between summary line and description (found 0)
717: D202 No blank lines allowed after function docstring (found 1)
740: D202 No blank lines allowed after function docstring (found 1)


1: D400 First line should end with a period (not 'k')
3: L102 copyright year is outdated, expected 2015 but got 2014
22:1: I100 Imports statements are in the wrong order. import os should be before import sys
24:1: I100 Imports statements are in the wrong order. import cgi should be before import re
29:1: I201 Missing newline before sections or imports.
30:1: I100 Imports statements are in the wrong order. from six should be before from six.moves.urllib.parse
31:1: I100 Imports statements are in the wrong order. from wsgiref.util should be before from six
31:1: I201 Missing newline before sections or imports.
34:1: I101 Imported names are in the wrong order. Should be DONE, HTTP_INTERNAL_SERVER_ERROR, HTTP_NOT_FOUND, HTTP_STATUS_MAP, OK, SERVER_RETURN
34:1: F401 'HTTP_INTERNAL_SERVER_ERROR' imported but unused
37:1: I101 Imported names are in the wrong order. Should be CFG_DEVEL_SITE, CFG_SITE_LANG, CFG_SITE_SECURE_URL, CFG_SITE_URL, CFG_WEBDIR, CFG_WEBSTYLE_HTTP_STATUS_ALERT_LIST, CFG_WEBSTYLE_REVERSE_PROXY_IPS
37:1: I100 Imports statements are in the wrong order. from invenio.config should be before from invenio.utils.apache
44:1: I101 Imported names are in the wrong order. Should be after_this_request, request, session
44:1: I100 Imports statements are in the wrong order. from flask should be before from invenio.utils.datastructures
58:5: E266 too many leading '#' for block comment
65: D103 Missing docstring in public function
71: D203 1 blank line required before class docstring (found 0)
71: D204 1 blank line required after class docstring (found 0)
71: D205 1 blank line required between summary line and description (found 0)
76: D102 Missing docstring in public method
81:1: I101 Imported names are in the wrong order. Should be BaseResponse, CommonResponseDescriptorsMixin, ResponseStreamMixin
81:1: E402 module level import not at top of file
85: D203 1 blank line required before class docstring (found 0)
85: D400 First line should end with a period (not '`')
85: D205 1 blank line required between summary line and description (found 0)
93: D203 1 blank line required before class docstring (found 0)
93: D204 1 blank line required after class docstring (found 0)
93: D205 1 blank line required between summary line and description (found 0)
100: D102 Missing docstring in public method
115:9: E266 too many leading '#' for block comment
126:20: E261 at least two spaces before inline comment
126:21: E262 inline comment should start with '# '
135: D102 Missing docstring in public method
138: D210 No whitespaces allowed surrounding docstring text
138: D401 First line should be in imperative mood ('Return', not 'Returns')
149: D102 Missing docstring in public method
152: D102 Missing docstring in public method
155: D102 Missing docstring in public method
158: D102 Missing docstring in public method
167: D102 Missing docstring in public method
185:21: E266 too many leading '#' for block comment
187:46: E261 at least two spaces before inline comment
187:47: E262 inline comment should start with '# '
188:25: E116 unexpected indentation (comment)
188:25: E266 too many leading '#' for block comment
193: D102 Missing docstring in public method
200: D102 Missing docstring in public method
203: D102 Missing docstring in public method
211: D102 Missing docstring in public method
214: D102 Missing docstring in public method
217: D102 Missing docstring in public method
223: D102 Missing docstring in public method
226: D102 Missing docstring in public method
229: D102 Missing docstring in public method
232: D102 Missing docstring in public method
235: D102 Missing docstring in public method
237:16: E126 continuation line over-indented for hanging indent
251:98: E502 the backslash is redundant between brackets
252:98: E502 the backslash is redundant between brackets
253:100: E502 the backslash is redundant between brackets
259: D102 Missing docstring in public method
264: D102 Missing docstring in public method
267: D102 Missing docstring in public method
270: D102 Missing docstring in public method
273: D102 Missing docstring in public method
278: D102 Missing docstring in public method
310:17: E266 too many leading '#' for block comment
316: D102 Missing docstring in public method
322: D102 Missing docstring in public method
325: D102 Missing docstring in public method
328: D102 Missing docstring in public method
331: D102 Missing docstring in public method
337: D102 Missing docstring in public method
343: D102 Missing docstring in public method
346: D102 Missing docstring in public method
349: D102 Missing docstring in public method
353: D102 Missing docstring in public method
358: D102 Missing docstring in public method
361: D102 Missing docstring in public method
365:13: E266 too many leading '#' for block comment
366:13: E266 too many leading '#' for block comment
367:13: E266 too many leading '#' for block comment
368:13: E266 too many leading '#' for block comment
371: D102 Missing docstring in public method
374: D102 Missing docstring in public method
377: D102 Missing docstring in public method
382: D102 Missing docstring in public method
385: D102 Missing docstring in public method
388: D102 Missing docstring in public method
391: D102 Missing docstring in public method
398:13: B901 blind except: statement
402: D400 First line should end with a period (not 't')
402: D205 1 blank line required between summary line and description (found 0)
414: D102 Missing docstring in public method
441:1: E302 expected 2 blank lines, found 1
441: D400 First line should end with a period (not 'e')
441: D205 1 blank line required between summary line and description (found 0)
452:13: E266 too many leading '#' for block comment
454:43: E261 at least two spaces before inline comment
454:44: E262 inline comment should start with '# '
459:1: E302 expected 2 blank lines, found 1
459: D200 One-line docstring should fit on one line with quotes (found 3)
463:5: E266 too many leading '#' for block comment
474:5: E266 too many leading '#' for block comment
490:47: E128 continuation line under-indented for visual indent
501:9: E266 too many leading '#' for block comment
515:9: E266 too many leading '#' for block comment
516:9: E266 too many leading '#' for block comment
521: D401 First line should be in imperative mood ('Return', not 'Returns')
521: D200 One-line docstring should fit on one line with quotes (found 3)
534:1: E302 expected 2 blank lines, found 1
534: D401 First line should be in imperative mood ('Return', not 'Returns')
534: D205 1 blank line required between summary line and description (found 0)
547:1: E302 expected 2 blank lines, found 1
547: D401 First line should be in imperative mood ('Check', not 'Checks')
547: D205 1 blank line required between summary line and description (found 0)
572:1: E302 expected 2 blank lines, found 1
572: D200 One-line docstring should fit on one line with quotes (found 3)
584:9: E266 too many leading '#' for block comment
587:13: E266 too many leading '#' for block comment
588:32: W602 deprecated form of raising exception
589:9: E266 too many leading '#' for block comment
590:9: E266 too many leading '#' for block comment
591:9: E266 too many leading '#' for block comment
594:13: E266 too many leading '#' for block comment
595:13: E266 too many leading '#' for block comment
596:13: E266 too many leading '#' for block comment
597:13: E266 too many leading '#' for block comment
598:13: E266 too many leading '#' for block comment
602:17: E266 too many leading '#' for block comment
603:17: E266 too many leading '#' for block comment
604:17: E266 too many leading '#' for block comment
618:26: E127 continuation line over-indented for visual indent
650:28: W602 deprecated form of raising exception


1: D400 First line should end with a period (not 'e')
24:1: E402 module level import not at top of file
25:1: I101 Imported names are in the wrong order. Should be datetime_format, rlike, run_sql
25:1: I201 Missing newline before sections or imports.
25:1: E402 module level import not at top of file
26:1: E402 module level import not at top of file
27:1: I101 Imported names are in the wrong order. Should be CFG_WEBMESSAGE_DAYS_BEFORE_DELETE_ORPHANS, CFG_WEBMESSAGE_MAX_NB_OF_MESSAGES, CFG_WEBMESSAGE_ROLES_WITHOUT_QUOTA, CFG_WEBMESSAGE_STATUS_CODE
27:1: E402 module level import not at top of file
32:1: I101 Imported names are in the wrong order. Should be convert_datestruct_to_datetext, datetext_default
32:1: E402 module level import not at top of file
33:31: E126 continuation line over-indented for hanging indent
35:1: E402 module level import not at top of file
38: D401 First line should be in imperative mood ('Check', not 'Checks')
38: D400 First line should end with a period (not 'e')
38: D205 1 blank line required between summary line and description (found 0)
45:10: E221 multiple spaces before operator
53:1: E302 expected 2 blank lines, found 1
53: D400 First line should end with a period (not 's')
53: D205 1 blank line required between summary line and description (found 0)
78:21: E127 continuation line over-indented for visual indent
79:21: E127 continuation line over-indented for visual indent
80:20: E127 continuation line over-indented for visual indent
96:1: E302 expected 2 blank lines, found 1
96: D202 No blank lines allowed after function docstring (found 1)
96: D205 1 blank line required between summary line and description (found 0)
117:1: E302 expected 2 blank lines, found 1
117: D210 No whitespaces allowed surrounding docstring text
117: D400 First line should end with a period (not 'r')
117: D205 1 blank line required between summary line and description (found 0)
133:1: E302 expected 2 blank lines, found 1
133: D210 No whitespaces allowed surrounding docstring text
133: D400 First line should end with a period (not 'd')
133: D205 1 blank line required between summary line and description (found 0)
150: D400 First line should end with a period (not 'l')
150: D205 1 blank line required between summary line and description (found 0)
169:26: E502 the backslash is redundant between brackets
170:21: E127 continuation line over-indented for visual indent
170:61: E502 the backslash is redundant between brackets
183:1: E302 expected 2 blank lines, found 1
183: D400 First line should end with a period (not 'd')
183: D205 1 blank line required between summary line and description (found 0)
199:1: E302 expected 2 blank lines, found 1
199: D400 First line should end with a period (not 'x')
199: D205 1 blank line required between summary line and description (found 0)
216:1: E302 expected 2 blank lines, found 1
216: D401 First line should be in imperative mood ('Check', not 'Checks')
216: D400 First line should end with a period (not ',')
216: D205 1 blank line required between summary line and description (found 0)
247:1: E302 expected 2 blank lines, found 1
247: D400 First line should end with a period (not ')')
247: D205 1 blank line required between summary line and description (found 0)
268:1: E302 expected 2 blank lines, found 1
268: D400 First line should end with a period (not 's')
268: D205 1 blank line required between summary line and description (found 0)
280:18: E225 missing whitespace around operator
290:9: E301 expected 1 blank line, found 0
290: D210 No whitespaces allowed surrounding docstring text
290: D401 First line should be in imperative mood ('take', not 'takes')
290: D400 First line should end with a period (not 's')
296:1: E302 expected 2 blank lines, found 1
296: D400 First line should end with a period (not 's')
296: D205 1 blank line required between summary line and description (found 0)
320:1: E302 expected 2 blank lines, found 1
320: D400 First line should end with a period (not 's')
320: D205 1 blank line required between summary line and description (found 0)
332:19: E225 missing whitespace around operator
342:9: E301 expected 1 blank line, found 0
342: D210 No whitespaces allowed surrounding docstring text
342: D401 First line should be in imperative mood ('take', not 'takes')
342: D400 First line should end with a period (not 's')
349: D400 First line should end with a period (not 's')
349: D205 1 blank line required between summary line and description (found 0)
371:9: E301 expected 1 blank line, found 0
371: D210 No whitespaces allowed surrounding docstring text
371: D400 First line should end with a period (not 's')
377:1: E302 expected 2 blank lines, found 1
377: D205 1 blank line required between summary line and description (found 0)
399:1: E302 expected 2 blank lines, found 1
399: D210 No whitespaces allowed surrounding docstring text
399: D401 First line should be in imperative mood ('check', not 'checks')
399: D400 First line should end with a period (not '1')
407:1: E302 expected 2 blank lines, found 1
407: D401 First line should be in imperative mood ('Create', not 'Creates')
407: D205 1 blank line required between summary line and description (found 0)
443:1: E302 expected 2 blank lines, found 1
443: D400 First line should end with a period (not 's')
443: D205 1 blank line required between summary line and description (found 0)
460:9: E301 expected 1 blank line, found 0
460: D210 No whitespaces allowed surrounding docstring text
460: D401 First line should be in imperative mood ('not(i', not 'not(is')
460: D400 First line should end with a period (not ')')
475: D400 First line should end with a period (not 'e')
475: D205 1 blank line required between summary line and description (found 0)
493:1: E302 expected 2 blank lines, found 1
493: D401 First line should be in imperative mood ('Update', not 'Updates')
493: D400 First line should end with a period (not 'd')
493: D205 1 blank line required between summary line and description (found 0)
499:10: E222 multiple spaces after operator
513:12: E225 missing whitespace around operator
526:1: E302 expected 2 blank lines, found 1
526: D400 First line should end with a period (not 'n')
532:37: E222 multiple spaces after operator
538:1: E302 expected 2 blank lines, found 1
538: D400 First line should end with a period (not 'e')
538: D200 One-line docstring should fit on one line with quotes (found 2)
545:75: E222 multiple spaces after operator
563:1: E302 expected 2 blank lines, found 1
563: D400 First line should end with a period (not 't')
563: D205 1 blank line required between summary line and description (found 0)
570:1: E302 expected 2 blank lines, found 1
570: D210 No whitespaces allowed surrounding docstring text
570: D401 First line should be in imperative mood ('Clean', not 'Cleans')
570: D400 First line should end with a period (not 'e')
595:5: E301 expected 1 blank line, found 0
626:1: W391 blank line at end of file


26:1: I201 Missing newline before sections or imports.
27:1: I100 Imports statements are in the wrong order. import dateutil.parser should be before import dictdiffer
27:1: I201 Missing newline before sections or imports.
29:1: I100 Imports statements are in the wrong order. from tempfile should be before import dateutil.parser
30:1: I100 Imports statements are in the wrong order. from functools should be before from tempfile
31:1: I101 Imported names are in the wrong order. Should be abort, current_app, request
31:1: I201 Missing newline before sections or imports.
32:1: I201 Missing newline before sections or imports.
33:1: I100 Imports statements are in the wrong order. from functools should be before from flask_login
33:1: I201 Missing newline before sections or imports.
36:1: I100 Imports statements are in the wrong order. from invenio.modules.editor.models should be before from invenio_records.api
36:1: I201 Missing newline before sections or imports.
37:1: I101 Imported names are in the wrong order. Should be Agent, Deposition, DepositionDraftCacheManager
37:1: I100 Imports statements are in the wrong order. from invenio.modules.deposit.models should be before from invenio.modules.editor.models
39:1: I100 Imports statements are in the wrong order. from invenio.ext.logging should be before from invenio.modules.deposit.models
42:1: I101 Imported names are in the wrong order. Should be deposition_record, make_record, record_to_draft
42:1: I201 Missing newline before sections or imports.
44:1: I100 Imports statements are in the wrong order. from invenio.legacy.bibdocfile.api should be before from .helpers
45:1: I201 Missing newline before sections or imports.
474: D103 Missing docstring in public function
481:19: E261 at least two spaces before inline comment
492:34: E261 at least two spaces before inline comment
498: D103 Missing docstring in public function
505:19: E261 at least two spaces before inline comment
505:20: E262 inline comment should start with '# '


33:1: I100 Imports statements are in the wrong order. from time should be before from invenio.utils.date
38: D205 1 blank line required between summary line and description (found 0)
48:1: E302 expected 2 blank lines, found 1
48: D205 1 blank line required between summary line and description (found 0)
56:12: E127 continuation line over-indented for visual indent
61: D205 1 blank line required between summary line and description (found 0)
70:42: E225 missing whitespace around operator
72:5: B901 blind except: statement
73:42: E225 missing whitespace around operator
74:45: E225 missing whitespace around operator
76:1: E302 expected 2 blank lines, found 1
76: D401 First line should be in imperative mood ('Check', not 'Checks')
76: D400 First line should end with a period (not 'e')
76: D205 1 blank line required between summary line and description (found 0)
84:12: E127 continuation line over-indented for visual indent
85:12: E127 continuation line over-indented for visual indent
87:1: E302 expected 2 blank lines, found 1
87: D205 1 blank line required between summary line and description (found 0)
94:42: E502 the backslash is redundant between brackets
94:11: E271 multiple spaces after keyword
95:13: E126 continuation line over-indented for hanging indent
96:13: E127 continuation line over-indented for visual indent
97:13: E127 continuation line over-indented for visual indent
99:1: E302 expected 2 blank lines, found 1
99: D205 1 blank line required between summary line and description (found 0)
114:12: E127 continuation line over-indented for visual indent
115:12: E127 continuation line over-indented for visual indent
117:1: E302 expected 2 blank lines, found 1
117: D210 No whitespaces allowed surrounding docstring text
117: D400 First line should end with a period (not 'r')
117: D205 1 blank line required between summary line and description (found 0)
125:12: E127 continuation line over-indented for visual indent
126:12: E127 continuation line over-indented for visual indent
127:12: E127 continuation line over-indented for visual indent
129:1: E302 expected 2 blank lines, found 1
129: D210 No whitespaces allowed surrounding docstring text
129: D400 First line should end with a period (not 'd')
129: D205 1 blank line required between summary line and description (found 0)
135:12: E127 continuation line over-indented for visual indent
136:12: E127 continuation line over-indented for visual indent
137:12: E127 continuation line over-indented for visual indent
139:1: E302 expected 2 blank lines, found 1
139: D400 First line should end with a period (not 'l')
139: D205 1 blank line required between summary line and description (found 0)
154:12: E127 continuation line over-indented for visual indent
155:12: E127 continuation line over-indented for visual indent
156:12: E127 continuation line over-indented for visual indent
158:1: E302 expected 2 blank lines, found 1
158: D400 First line should end with a period (not 'd')
158: D205 1 blank line required between summary line and description (found 0)
165:12: E127 continuation line over-indented for visual indent
166:12: E127 continuation line over-indented for visual indent
166:44: E225 missing whitespace around operator
167:12: E127 continuation line over-indented for visual indent
169:1: E302 expected 2 blank lines, found 1
169: D400 First line should end with a period (not 'x')
169: D205 1 blank line required between summary line and description (found 0)
179:20: E127 continuation line over-indented for visual indent
183:1: E302 expected 2 blank lines, found 1
183: D401 First line should be in imperative mood ('Check', not 'Checks')
183: D400 First line should end with a period (not ',')
183: D205 1 blank line required between summary line and description (found 0)
194:16: E127 continuation line over-indented for visual indent
195:16: E127 continuation line over-indented for visual indent
196:16: E127 continuation line over-indented for visual indent
196:63: E225 missing whitespace around operator
197:16: E127 continuation line over-indented for visual indent
199:65: E502 the backslash is redundant between brackets
200:12: E128 continuation line under-indented for visual indent
201:12: E127 continuation line over-indented for visual indent
203:1: E302 expected 2 blank lines, found 1
203: D400 First line should end with a period (not ')')
203: D205 1 blank line required between summary line and description (found 0)
211:15: E128 continuation line under-indented for visual indent
211:62: E502 the backslash is redundant between brackets
212:15: E128 continuation line under-indented for visual indent
212:55: E225 missing whitespace around operator
213:51: E225 missing whitespace around operator
215:19: E127 continuation line over-indented for visual indent
215:59: E225 missing whitespace around operator
216:55: E225 missing whitespace around operator
217:19: E127 continuation line over-indented for visual indent
222:1: E302 expected 2 blank lines, found 1
222: D400 First line should end with a period (not 's')
222: D205 1 blank line required between summary line and description (found 0)
234:18: E225 missing whitespace around operator
244:9: E301 expected 1 blank line, found 0
244: D210 No whitespaces allowed surrounding docstring text
244: D401 First line should be in imperative mood ('take', not 'takes')
244: D400 First line should end with a period (not 's')
250:1: E302 expected 2 blank lines, found 1
250: D400 First line should end with a period (not 's')
250: D205 1 blank line required between summary line and description (found 0)
274:1: E302 expected 2 blank lines, found 1
274: D400 First line should end with a period (not 's')
274: D205 1 blank line required between summary line and description (found 0)
286:19: E225 missing whitespace around operator
296:9: E301 expected 1 blank line, found 0
296: D210 No whitespaces allowed surrounding docstring text
296: D401 First line should be in imperative mood ('take', not 'takes')
296: D400 First line should end with a period (not 's')
303: D400 First line should end with a period (not 's')
303: D205 1 blank line required between summary line and description (found 0)
325:9: E301 expected 1 blank line, found 0
325: D210 No whitespaces allowed surrounding docstring text
325: D400 First line should end with a period (not 's')
331:1: E302 expected 2 blank lines, found 1
331: D205 1 blank line required between summary line and description (found 0)
353:1: E302 expected 2 blank lines, found 1
353: D210 No whitespaces allowed surrounding docstring text
353: D401 First line should be in imperative mood ('check', not 'checks')
353: D400 First line should end with a period (not '1')
361:1: E302 expected 2 blank lines, found 1
361: D401 First line should be in imperative mood ('Create', not 'Creates')
361: D205 1 blank line required between summary line and description (found 0)
397:1: E302 expected 2 blank lines, found 1
397: D400 First line should end with a period (not 's')
397: D205 1 blank line required between summary line and description (found 0)
414:9: E301 expected 1 blank line, found 0
414: D210 No whitespaces allowed surrounding docstring text
414: D401 First line should be in imperative mood ('not(i', not 'not(is')
414: D400 First line should end with a period (not ')')
429: D400 First line should end with a period (not 'e')
429: D205 1 blank line required between summary line and description (found 0)
448: D401 First line should be in imperative mood ('Update', not 'Updates')
448: D400 First line should end with a period (not 'd')
448: D205 1 blank line required between summary line and description (found 0)
454:5: F841 local variable 'now' is assigned to but never used
454:10: E222 multiple spaces after operator
460:9: E122 continuation line missing indentation or outdented
460:34: E225 missing whitespace around operator
461:9: E122 continuation line missing indentation or outdented
462:9: E122 continuation line missing indentation or outdented
462:33: E225 missing whitespace around operator
463:9: E122 continuation line missing indentation or outdented
468:38: E225 missing whitespace around operator
477: D400 First line should end with a period (not 'n')
488:1: E302 expected 2 blank lines, found 1
488: D400 First line should end with a period (not 'e')
488: D200 One-line docstring should fit on one line with quotes (found 2)
513:1: E302 expected 2 blank lines, found 1
513: D400 First line should end with a period (not 't')
513: D205 1 blank line required between summary line and description (found 0)
520:1: E302 expected 2 blank lines, found 1
520: D210 No whitespaces allowed surrounding docstring text
520: D401 First line should be in imperative mood ('Clean', not 'Cleans')
520: D400 First line should end with a period (not 'e')
545:5: E301 expected 1 blank line, found 0
576:1: W391 blank line at end of file


checked!


before save layers?


@kendrakeith DWMR (done with my review). This is good. Concise and that's a goal of the highest value. Press on!


TeamCity MonoGame :: Develop (Win) [Build 3.5.0.354](http://teamcity.monogame.net/viewLog.html?buildId=8787&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 522, ignored: 6 Build time: 00:26:04


Yeah, it was weird and pretty annoying especially because after I ran something like `:Gmove` it would give me this warning, actually move the file, but not update the buffer--so I was still editing the file in its old location.


How often do you hit this?


Thank you, thank you so much!!


I did that to be consistent with function get_info_markup().
The variable is called n_episodes_to_watch in lines 255-259 of src/SeriesFinale/series.py.


Thank you very much @satoon101 ! I'm busy today, but I'll test this tomorrow, and if it works like you said, I'll update EasyPlayer to use PostHooks asap :)


This part break things in https://github.com/CiscoCloud/haproxy-consul : the haproxy template rely on this taskId.

See : https://github.com/CiscoCloud/haproxy-consul/issues/9


By the way, we don't put 'structured' either.


Without the matcher change I couldn't get to the action eg an action exported as 'items' won't match '/items/123', logs as undefined instead of [Function]. I pass the matcher through as i've already split the url params up, saves doing it again in the backend code.

Might be a better way to do this perhaps.


prevented keyboard navigation when accessibility isn't enabled


add had back the methods you removed.


I should have used all(deferreds) here for the multiple fetches :) Did in a follow up, but will probably wait till 1.1. to avoid unnecessary churn in here.


First of all, sorry didn't notice I included the your commit about the control.js changes (added : customizer new control visibility callback ) in the whole PR
Then:
(*) Better sidenav nav margin-top consistency in both resp and not resp modes
the nav (the menu itself) when responsive (media query < 979px) has a margin top of 10px. This affects both the regular and the sidenav menu for that viewport. I just put the same margin for all the viewports for the sidenav menu.

(*) Better first/last menu item alignment (padding)
=> is it for regular menu ? or side or both ?
This affects the regular menu first and last items depending on where is placed (vertical alignment with socials, when on the left, and with the tagline, when on the right). It affects just the regular 'cause ".pull-menu-left .navbar" affects just the rugular, since ".pull-menu-left" is a class of the header and not of the sidenav.

(*) Better menu button left/right alignment
 Affects, with the same criteria as above, the menu button div (in the header), which is therefore aligned as above

For the latest two, reasons are:
1) I didn't aligned the menu div
2) your alignment firs/last regular menu item rule was based on the logo left/right, while it should be on the regular menu (regular) position which is logo position unrelated


do you intend to publish it on rubygems.org ?


Ah, now that you mention `:Gmove` that reminds me that I _do_ sometimes see these annoying errors when using `:Rename` and `:Move` etc. Sweet.


Nikeo said:
> Ok don't waste time on this Rocco.
> I'll merge what I understand and we'll fix the rest afterwards if needed :)

Sorry, too late :D


@kevinglover typo in separated


This warning should be qualified so that people know to use Duration.Inf to avoid interruption.


@trankin from what i can tell this change is just removing a space in front of UMBRACO_MACRO, without this change, all tests still pass and all my local tests work as well. Can you tell me what this space change fixes? We've already shipped 7.2.8 with these macro fixes (and others) but this single space change didn't make it in there since I didn't actually notice the change until now. If this is fixing an untested issue, i just need to know what it is so i can write the test for it. Thanks.


Nice, this reads much cleaner now.


The patch looks fine, but could you fix your email address in the git commit:

Author: rjimgal <rjimenez@MALLM-RJIMENEZ.local>


No this happens just by opening the app without any user interaction. My main content container underneath the body element has absolute positioning, just in case that might matter. It is not my design but some widgets from jquery mobile and polymer will do that.


I don't think you need this, as you get it for free. See `:h ;undodir'`.


ok fixed in dev. thanks


exact.


- hides input behind img tag otherwise visible when label is set to transparent.


Hmmm...is there any way to tell what atoms in the given atomgroup are in the same molecule as ``ref`` *a priori*? Otherwise one might have a lot of looping in the case one selects all waters and wants to make them whole. Also, the exception raised (``ValueError`` on line 314) doesn't really say why this happened.

Perhaps make it clearer in the docs as well that this will only make the molecule that includes the ``reference_atom`` whole?


The style edit here was written by @Sesta with commit bc040c73cac35af8553e1f0f3d6f0e40b368852b. Somehow in doing a rebase to squash some non-consecutive commits together, this commit got mixed in and authorship was lost within the direct history tree.

Sorry about that, and I'll do my best to make sure it doesn't happen again (like never squashing non-consecutive commits again.)


It's definitely good to do this kind of error procesing, but this is actually only going to check the last request you ran.


Last night the windows installer installed an OpenCL_ICD.dll. Was this the fix which copied this file? Or is this copying the system opencl dll?


Hi,
this function seems unused. Why is it there?


I initially did this:
```
layers.saveLayers({
  complete: function() {
    layers.trigger('reset');
  }
});
```
But since `saveLayers` is a bit slow, visual feedback is very slow too...


fixed in dev thanks !


Just add r7 to the clobber list; don't delete the ':'. Also, remove the trailing space.


- visibility:hidden removed from theme gmcq.less https://github.com/adaptlearning/adapt-contrib-vanilla/pull/135


LGTM :)


Everyone's got their own process for writing tests. I've been saved enough times by writing them as I implement that I try to be pretty good about it.


@jensens @vangheem Can one of you allow submitting bugs to this package?


In my opinion, keeping it goes along with the idea of saying explicitly what I mean to happen.
While I would assume that for most programs, to reach the end is to have not encountered an error, but I could imagine up ones that aren't so for whatever reason. I think it is more clear like this. If a function has a value type, it feels wrong not to explicitly return a value of the corresponding type.
This perception could easily be a function of how unused I am to having this `int main()` function, but I feel that I am speaking fairly objectively here.


Ah, good call. I just assumed that all of these directory settings would operate in the same way. Silly me.


Sounds good.


Overall things are looking good - Good job!


Add " on the begging or \ before apostrophe to avoid building issue


Ah, for CRUDy urls. You're right that we don't want to have the `/` in the matcher group.

How about this?
```javascript
let matcher = /\/([^?\/]+)\/?(.+)?/.exec(req.url);
...
action(req, matcher[2] && matcher[2].split('/'))
```
So a url of `/items/123/foo/456` results in the `items` action being called with `req` and `['123', 'foo', '456']`.

Test that an PR it if you agree.


develop (Myoldmopar) - Win64-Windows-7-VisualStudio-12: OK (1241 of 1241 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)


It is copying the OpenCL.dll from cpp-ethereum/extdep/windows/x64/bin. And it is prebuilt OpenCL ICD loader. But that's not the place where it happens.


True. We originally had it extending FriendableUser, but figured this would be simpler. I'd have to make decisions about removing some duplicate attributes and computed properties. Though, I imagine eventually we'll want FriendableUser to extend User and then make those decisions.


BUT DECISIONS ARE HARD (especially when you don't have tests)


저장할때의 데이터로서 필요합니다!!
사실 info가 대부분 getter setter만 처리할때가 많아서 이부분이 꼭 필요한지에대해서는 고민해볼 가치가 있을 것같습니다


I thought one of our linters doesn't like unexported types to have public methods. Are we ignoring that already?


add javadoc , including @since


Ah, yeah, I see what you mean. I think quitting with an `EXIT_FAILURE` makes more sense then.
With piping in mind, I'm also going to get rid of the `cout`s like I'm going to do for the other exercises. The instructions can be left to the documentation.


加了這條我就不能去其他頁面了…


the return parameters are worth a comment.


We call that fragment in mda, so there's `AtomGroup.fragments` and `Atom.fragment`, it does a similar thing walking along bonds.

If `reference_atom` isn't in atomgroup it'll raise a ValueError; the algorithm keeps going until everyone has been seen, so if it can't walk to someone, it'll loop infinitely, hence the counter... which does need a better message


넵 반영하겠습니다


rename to configurationInstance... getter as well


bindir should be RAILS_ROOT or not?


make final


Nothing is complaining about this. Perhaps it is because `dbool` itself is unexported.


make package


TeamCity DNN JavaScript Libraries :: CI [Build 39](http://teamcity.engagesoftware.com/viewLog.html?buildId=307&buildTypeId=DnnJavaScriptLibraries_Ci) is now running


TeamCity DNN JavaScript Libraries :: CI [Build 39](http://teamcity.engagesoftware.com/viewLog.html?buildId=307&buildTypeId=DnnJavaScriptLibraries_Ci) outcome was **SUCCESS**
Summary: Running Build time: 0:0:9


Well spotted! Will update in a second.


Maquinaaa, mola ese codigo!!
en java es bastante mas simple creo recordar, pero era del estilo al final le haces un tratamiento a la variable que sea... pero maquinon. Encuanto tenga algo de tiempo voy a mirar a meter el video como te he dicho, que se pueda poner abajo a la derecha y que vaya aparte, eso igual ajax puede venirnos bn..

paZ you! jajaja


Ok Rocco, thanks for your lights. very useful.
Changed applied in dev except for margin top.
I've added a rule when tagline-off, otherwise it's a bit too much margin when not responsive. (=> even if not consistent I agree)
Thanks !


ah, I think the check only fails if that unexported type is returned by a publicly accessible method.


add more detail... what's an implicit configuration?... what are the requirements for a Configuration model to be elegible for implicitness, etc...


Yeah. Done.

```
	// Bool returns the Datum as a bool or an error if the Datum cannot be
	// converted to a bool.
	Bool() (dbool, error)
```


Can you use "ruby symbol" notation like that? INRE: `friend.get(:id)`?


Actually, looking more closely, I should be using ``statement.execute()`` rather than ``statement.executeQuery()``.  ``statement.executeQuery()`` will fail if the query in question doesn't actually return a ResultSet (i.e. a SELECT).  There is no reason to limit a validation to SELECT.


if an instance has already been created -> if it's not possible to create an implicit configuration. If this method is called is because the ExtensionManager already knows that one has not been created


But yeah, this is way better! :+1:


TeamCity DNN JavaScript Libraries :: CI [Build 40](http://teamcity.engagesoftware.com/viewLog.html?buildId=308&buildTypeId=DnnJavaScriptLibraries_Ci) is now running


add more detail to the javadoc... find a balance with the class javadoc


TeamCity DNN JavaScript Libraries :: CI [Build 40](http://teamcity.engagesoftware.com/viewLog.html?buildId=308&buildTypeId=DnnJavaScriptLibraries_Ci) outcome was **SUCCESS**
Summary: Running Build time: 0:0:8


I used that class to indent that text and add padding-bottom


looks ok. if the new API already exists in M44, it even makes sense to land this before the roll so the diff of the patch moving Crosswalk to M45 is smaller.


Apologies. In any case, it is undefined behavior to input an invalid program, so I will do my above command (albeit for different reasoning)


Лучше через промежуточную переменную:
auto up = tree_el->up();
assert(up)
if (up->up())
...

Иначе дважды вызывается lock(), первый раз проверяется его результат, а второй раз результат используется.
При некоторых условиях (удаление в параллельном потоке, например), результат первого вызова может не совпадать с результатом второго.

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


I'd call this `tycon` instead of `unappTp`. That's the naming convention elsewhere.


I just noticed the use of `browse_note_url(note)` in the RSS builder, which seems to be a proper interface. But the URL changes from www.openstreetmap.org to api.openstreetmap.org then, which itself redirects to the former again.
Or should I use the following to preserve the default domain? `browse_note_url(note, :host => SERVER_URL)`


Indeed - I will re-push this.


Ha, conflating my languages. My b.


done.


Totally! This was the result of :pizza: code.


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

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


The issue "automotive mode should always be used" is already solved (in mkgmap or a later version of Basecamp) so it does not make much difference anymore. I've noticed the routing in bicycle mode is even slightly better and faster. The only thing that differs is that toll road avoidance is not available on most units in bicycle mode. With toll road avoidance on, routing will be on 0x02 line types (=bicycle routes). You can only use this in automotive mode in some units.


Why? static is needed.


update the docstring as this case don't exist anymore.


There is a __ne__(self, other) method after __props__ = () at class TrueDot(gofr.op.Op)
Should we remove it ?


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


This is test code, so I thought it ok and maybe even good to leave the statuses hardcoded.  I'm ok with changing this line to use `statuses.new` here as long as we change the other hardcoded statuses in this file as well.


develop (Myoldmopar) - i386-Windows-7-VisualStudio-12: OK (1241 of 1241 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)


Actually, I'm wondering if it's feasible.

My point : either the method ´website_publish_button´ is calling ´open_website_url´ and opens a website url, either it is changing the value of website_published.

What do you think ?


Maybe you could add a warning in log if the issue is on a common rule.


> If reference_atom isn't in atomgroup it'll raise a ValueError;

Alright, but I'm concerned about the case where ``reference_atom`` is in the AtomGroup, but that the AtomGroup contains many fragments. Can we do the check that the AtomGroup contains only a single fragment efficiently before changing any of the atom positions? That is, before the main loop?


Аналогично, ИМХО лучше сохранить up()->up() в переменной чтобы в if и присвоении было гарантированно одно и тоже.


sweet! +1


hhhh


The button works, but the background color does not show up. How should it be written to have a white background?


With what input could this line be reached ? From my understanding it can't be reached.. There's a similar line in ```with-radix-char``` that I think we can remove ? The "math.parser" tests still pass without it


please send a pull request!


That won't work. All non-required variables have to be set to null, otherwise you get:

error: variable connectionTtl not initialized in the default constructor

etc, etc.


@aslagle how do you feel about moving these fields directly onto the Meteor.Accounts object? I was hoping to keep the Account object as bare-bones as possible so that we could treat our UserProfiles just like our other models but if this is how it's always done in Meteor that's fine by me.  We might also be able to use Astronomy with the Meteor.Accounts object also.


Yes, this is already done elsewhere in the parent class. No need to duplicate it.


> AVA
> —
> | 1 | 2 | 3 |
> | --- | --- | --- |
> | 4 | 5 | 6 |


Ага, вот один из потенциальных источников проблем.
Надо проверить все присвоения где `up()` слева: `...up() = ...`.
Я бы заменил из по синтаксису, чтобы легче было найти в будущем.
Например, на `...set_up(...)`.


> Is there any evidence, that Python requires an absolute path here?

Python internally needs to find out where its files are located. I think I saw in the Python C code that it first tries to derive the location from argv[0] (the filename of the executable) and if that fails then it tries other approaches.

argv[0] should be always absolute path but on windows it is not. I think I made it to be always absolute path.

This findings were valid for python 2.x. I guess for Python 3 it is similar.


Merge


@MethodGrab looking forward to 4x then lol


Is there a JIRA ticket to implement this FIXME ? Or will it be done very soon ?


- remove broken when statement (@focus-outline is set by default in vanilla).
- remove outline:none for keyboard navigation - even for sighted users who navigate via keyboard will need some form of indication to where they are. Focus is set by browser default.


hmm, we could yes, but it would require calculating the fragments, which would essentially do the walk without changing positions first, then compare the walk against the atomgroup and check that all of atomgroup is within the walk.  I'll look at how quick walking is compared to the rest of the algorithm.

You're right in that this is destructive and rolling back is impossible.


> This fails when running the executable on Linux (de_DE.UTF-8) in a path with non-ascii-characters, e.g.umlauts. Why are you converting argv[0] without considering locale, while for the other args, you are considering locale?

This might be a bug.


Unit Tests failure not related to changes.


Part of this ticket. New commit to come.


Hi Wido,

Just remove the final modifier and it will work. Putting forward final enforces that the attribute has to be initialised.

Cheers,
Wilder

Sent from my iPhone

On 16 Jul 2015, at 17:39, Wido den Hollander <notifications@github.com<mailto:notifications@github.com>> wrote:

That won't work. All non-required variables have to be set to null, otherwise you get:

error: variable connectionTtl not initialized in the default constructor

etc, etc.

—
Reply to this email directly or view it on GitHub<https://github.com/wido/cloudstack/commit/2f1f4698b2da03805dacba89816b623d92f0fd2e#commitcomment-12206523>.


You can do something like this:

 <----- add all your padding/alignment styles here ---->

                    All members (15 members)

                     Mailing list address:
                     section_id@his.harvard.edu

The code above is easier to read and the styles already come from native html elements.


There is related code to this at https://github.com/articlemetrics/lagotto/blob/master/app/models/concerns/resolvable.rb#L259 (`id = id.gsub(/(http|https):\/+(\w+)/, '\1://\2')`, not sure it is worth consolidating. But `sanitize_work_id` should also handle `https`.


Maybe, You can use @Singleton annotation, It is another feature of groovy


Bump on npm?


davy's key is not 100%


Вот это уже ошибка.
Слева независимый `shared_ptr`, так как из `up()` он возвращается по значению, а не по ссылке.
Т.е. это присвоение не меняет поле `tree_el->right()->u`.
Должно быть `tree_el->right()->week_up() = tree_el->up();` или `tree_el->right()->set_up(tree_el->up());`


@CheckForNull is missing


If I'm correct the exception be thrown on the 64th index command regardless of the index name, effectively preventing index updates of nodes with more than 63 properties in one go.


I am a little confused about the description in merge function of skew heap.
Please discuss with me at your covenience. ><


I do think the "generally" is needed here. Exceptions to the rule do exist.


Problem is you're not guaranteed a [2], eg i hit '/podcasts' and log

```
 [ '/podcasts',
  'podcasts',
  undefined,
  index: 0,
  input: '/podcasts' ]
```
whereas .split gives
```
[ '', 'podcasts' ]
```
and would automatically add the other segments.


I don't know how I feel about the period, but the whole change makes the paragraph feel like the end result is another process, instead of a set of deliverables.


LGTM


Or you could also have used Optional :)


Okay, thanks @sergiogonzalez!


What if instead of adding them to the sign up form, we made the "fill out your profile" page the first page you go to after you register. Maybe even make it so you can't go to other pages until you've filled in the required fields.

If we want it in this form, I think we'll have to keep them in the profile of the accounts object, or else not use the useraccounts package at all. We could look into how Astronomy works with the Accounts object.


I'm afraid this warning will be displayed too many times and during a lot of releases (lang plugins still use 4.5 LTS). I will display this logs with DEBUG level.


i hit it several times in the last days.. (and each day launching the client maybe 20 times)


Did you mean to have a paragraph with the same class. I need the left padding to line up the text with the button above.


:birthday:


In Renewal server, it's okay...My server hold 72 players after update without problems,
But some peoples related that you need

fix scr files 'scr/char/char_mapif.c'

Find or Go To Line '737'

        if (operation == 2) {
            timediff = RFIFOL(fd, 32);
            val1 = RFIFOL(fd, 36);
        } else if (operation == 7)
            sex = RFIFOB(fd, 32);
        RFIFOSKIP(fd,44);

Replace
        if (operation == 2) {
            timediff = RFIFOL(fd, 32);
            val1 = RFIFOL(fd, 36);
        } else if (operation == 6){
            timediff = RFIFOL(fd, 32);
            val1 = RFIFOL(fd, 36);
        } else if (operation == 7)
            sex = RFIFOB(fd, 32);
        RFIFOSKIP(fd,44);

Save and recompile


please add a boolean hasCake;

(joking)


I still need that class to indent this caption.


I think maybe not required because ``next-digit`` doesn't call the quot if we are at the end of the string.


@mintisan 咱们开头需要稍微统一下，具体格式请参考 zh/doc/README.md，需要包含：原文；翻译；校订 三个方面，以便更好地确保内容质量，增加责任感，再一个方面也是对大家工作的认可。


Look at my comment above with the code snippet.


I like the idea of separating the extended profile info from the initial registration.


Right. Hence the `matcher[2] &&` to not call `split('/')` on `undefined`. Does it give an error?

Okay, how about:
```javascript
let matcher = req.url.split('/');
...
action(req, matcher.slice(2)); // to avoid passing the name of the action to itself
```

Better?


That's a typo :) Could you please change these to `gamsvr` so that your solution could be tested automatically?


Good catch. Thanks


Yeah, I think we might need to find a better label than 'author alert'. How about 'browser alert'? We're tied to the browser for the functionality; might as well make a virtue of it. :smile:


oops, yeah you're right. If you want to open a Pull-Request all you need to do is click the edit button on github


Hi Julien,

may I use this Darwin build for my project (https://github.com/drwetter/testssl.sh) too?

Cheers, Dirk


should those be toNumber as well for consistency?


很好嘛


Can you point me to part 2? I looked in dialer and incallui but didn't see it. I could be blind of course, wouldn't be the first time


C# and VB declaration are different, so common analyzer does not seem to work. For example, TryGetDeclarationBody returns nothing for VB SubStatement. I will handle VB separately but I will check if there is any way to have common analyzer.


This is hilarious.


Removed (fixed?) in 33a62c7f9de7e9b6200943609db56697e070d753.


@CheckForNull is already declared in inherited method !


This class doesn't have any raw pointers! I fixed all the other missing initializations though. Thanks for catching them.


In a perfect world, it would be nice to see the following:

* Following of style guidelines (no long lines, proper spacing, etc.)
* Outlined and implemented error constants (easier to throw and improves readability)

Otherwise code, looks great and the functionality it gladly welcome.


Just a question in order for all of us to use the same convention : should we use 'sut' or 'underTest' ?


The Google doc states there should be 3 methods for tracking events:
track(str)
track(object)
track(str, object)


Done! https://github.com/angular-class/angular2-webpack-starter/pull/30
Hope this helps :)


@ntdb Before I go wild with removing hardcoded interface messages from the React components, please let me know if this is the right approach.


t'embête pas à faire un commit juste pour le virer, c'était juste pour bien comprendre la modif.


i _think_ this is racy, which is why i didn't do it in the first place.


Sure thing! But you may want to build a newer version from @PeterMosmans 's repo.


>> Wow !! Amazing calculations !!

Nothing unusual... I was too sleepy to notice, that this task can be solved via system of equation - and this obviously should easily than described method:

1) 4.15=((0.01*1-0.1966)**2 - 0.0387)/a + b
2) 3.829=((0.01*0.5-0.1966)**2 - 0.0387)/a + b


Makes perfect sense @maennel. @boydjohnson - do you see more refined assertion?


Could you make it Glowstone, not GlowStone? It is bugging me every time I see your readme :laughing:.

Also, if it is ok with you, could you link to the Glowstone++ organization?


:+1: nice one


# [Pausing and Resuming an Activity](https://developer.android.com/training/basics/activity-lifecycle/pausing.html)

During normal app use, the foreground activity is sometimes obstructed by other visual components that cause the activity to pause. For example, when a semi-transparent activity opens (such as one in the style of a dialog), the previous activity pauses. As long as the activity is still partially visible but currently not the activity in focus, it remains paused. However, once the activity is fully-obstructed and not visible, it stops

As your activity enters the paused state, the system calls the `onPause()` method on your Activity, which allows you to stop ongoing actions that should not continue while paused (such as a video) or persist any information that should be permanently saved in case the user continues to leave your app.

## Pause Your Activity

When the system calls `onPause()` for your activity, it technically means your activity is still partially visible, but most often is an indication that the user is leaving the activity and it will soon enter the Stopped state. You should usually use the `onPause()` callback to:

- Stop animations or other ongoing actions that could consume CPU.
- Commit unsaved changes, but only if users expect such changes to be permanently saved when they leave (such as a draft email).
- Release system resources, such as broadcast receivers, handles to sensors (like GPS), or any resources that may affect battery life while your activity is paused and the user does not need them.

```java
@Override
public void onPause()
{
    super.onPause();  // Always call the superclass method first

    // Release the Camera because we don't need it when paused
    // and other activities might need to use it.
    if (camera != null)
    {
        camera.release()
        camera = null;
    }
}
```

However, you should avoid performing CPU-intensive work during `onPause()`, such as writing to a database, because it can slow the visible transition to the next activity (you should instead perform heavy-load shutdown operations during `onStop()`).

__Note:__ When your activity is paused, the Activity instance is kept resident in memory and is recalled when the activity resumes. You don’t need to re-initialize components that were created during any of the callback methods leading up to the Resumed state.

## Resume Your Activity

Be aware that the system calls this method every time your activity comes into the foreground, including when it's created for the first time. As such, you should implement `onResume()` to initialize components that you release during `onPause()` and perform any other initializations that must occur each time the activity enters the Resumed state (such as begin animations and initialize components only used while the activity has user focus).

```java
@Override
public void onResume()
{
    super.onResume();  // Always call the superclass method first

    // Get the Camera instance as the activity achieves full user focus
    if (camera == null) {
        initializeCamera(); // Local method to handle camera init
    }
}
```


@ragesoss Looks good to me, go nuts!


Sure! :D


any reason not to use a single `errors.New` thing here?


Please check if you used the newest configuration file as indicated. Specifically, the config file you used has removed the ```.gz``` suffix  in the input field
```
path_img = "./data/t10k-images-idx3-ubyte"
path_label = "./data/t10k-labels-idx1-ubyte"
```

We removed support for gz for easier portability support under windows, so there could be problem when gz file is readed as image files.


好像原来转换有点问题，把加粗显示转没了，咱们可以考虑在每个术语前加个 * 号缩进下？


Yep this is good, just sends out the params. Will PR.


cool :+1:


```underTest``` ! I will fix all other tests.


I do not understand this commit : only comments have been added. Is there something under dev ?


What is the connection between this commit and your problem?
Commit changes code of the char server. You have received crash of the map server.


this should be `continue`, not `break`


Is there a specific reason for the pop() here? To me it looks like we sometimes loose information here, i.e. in the case where we have an unsupported timezone information (the name of the timezone is normally kept in vevent['DTEND'].params['TZID']).


@untitaker see above


JTAG/ JTAG 调试器 / ?


Bad commit. This ticket was unfortunately merge with the other one :-(


@madebymunsters DWMR. These were done just right. Good good.


Am 07/16/2015 um 05:59 PM schrieb Julien Vehent:
> Sure thing! But you may want to build a newer version from @PeterMosmans <https://github.com/PeterMosmans> 's repo.

Thx!

Sure, wish I could -- I don't own a OS X machine and there's no cross compiler (without Apple tools for which you need to own
hardware) to my knowledge ;-(


Hmm, true.  I hadn't considered the existence of `ostree_repo_is_system()`.  That function was always a bit weird because it's probably only used in that one case of the remote config, but it is public.


Actually, it always prompted for a different version, the issue was present only when installing more than one. You can use the `--yes` parameter to automatically select the latest available version.

I'm working now on a `--restart-shell` parameter to reload GNOME Shell after finish installing all the extensions.


Only more reason to accept the pull request ;)

No, but you are right, it doesn't necessarily need to be a SELECT. And we dont really need the resultset.


Ok, great. It will work well with amazon then.


convert from lambda to async lambda changes of types, which is a rude edit, so I don't think we need to handle here.


Should this be `this.isIncluded`?


Good idea
Done at b1e946540ae2dfab434a14424bdb3328a8d28954

Thanks :smile:


# [Stopping and Restarting an Activity](https://developer.android.com/training/basics/activity-lifecycle/stopping.html)

Properly stopping and restarting your activity is an important process in the activity lifecycle that ensures your users perceive that your app is always alive and doesn't lose their progress. There are a few of key scenarios in which your activity is stopped and restarted:

- The user opens the Recent Apps window and switches from your app to another app. The activity in your app that's currently in the foreground is stopped. If the user returns to your app from the Home screen launcher icon or the Recent Apps window, the activity restarts.
- The user performs an action in your app that starts a new activity. The current activity is stopped when the second activity is created. If the user then presses the Back button, the first activity is restarted.
- The user receives a phone call while using your app on his or her phone.

When your activity is stopped, the `Activity` object is kept resident in memory and is recalled when the activity resumes. You don’t need to re-initialize components that were created during any of the callback methods leading up to the Resumed state. The system also keeps track of the current state for each `View` in the layout, so if the user entered text into an `EditText` widget, that content is retained so you don't need to save and restore it.

__Note:__ Even if the system destroys your activity while it's stopped, it still retains the state of the `View` objects (such as text in an `EditText`) in a `Bundle` (a blob of key-value pairs) and restores them if the user navigates back to the same instance of the activity.


Where the madness began!


Ok


@mjura Is this right?  I cannot find any reference to SLE-Cloud-PTF anywhere else?


@mjura @jdsn @bmwiedemann ping ...


ok


Random bug found while testing this...


ok, now I understand better !


Oh, you are right. Thanks for catching this one.


yep - though the fact that this didn't cause problems suggests maybe it was short-circuiting somewhere else. wd be interesting to know if we ever reach that line and `this.isIncluded` is `true`


tester commentnya dulu


this breaks FT_AgendaLabBeamSyncTest


...probably. I haven't had much opportunity to test it in all configurations, but it's working well for me.

In the meantime, you can use it from github like this:

gem 'neo-asset_sync', github: 'paulrnash/asset_sync', branch: 'development'

This is a stable branch I've been using in my project for a few weeks. Seems to work well. My primary goal was to fix the fog problems that caused all ~40 gems of fog to get pulled in. Then I started looking around at picking up some stale PRs from the main project, but switched focus back to my actual project for the moment.


I didn't realize that we wouldn't extract all valuable information here. I did this because it seems way cleaner to extract the date and later insert it back in. This avoids accidentally creating multiple DTENDs, but preserves those if they exist (stupid icalendar...).


Salah Nih


Olá, Parabéns pelo script.
Só notei uma coisa:
Na variável File só consegui executar com está alteração
file = open(raw_input('[+] - Digite o caminho do arquivo com os IPs:'))
Abraços


@mfonville,

I think there is a missing case in add_sources.sh.  There are two API9-ARM-Universal packages:

[010 armeabi](http://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-7-8-87-2077814-010-android-apk-download/) and [030 armeabi**-v7a**](http://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-7-8-87-2077814-030-android-apk-download/)

The script makes 010 a 030 (/sources/arm/priv-app/com.google.android.gms/9/nodpi/7887030.apk)

Thoughts?


I suppose you can change this to only get the dtend, but we'll have to use `vevent['DTEND']` instead of `add`.


I don't understand the value "SEED_SAW" as the seed. can you explain this?


Adding in a flag to protect against an infinite loop for a watch on a single file.  Whenever the watched file would be accessed an event would trigger for the initial access and for every access on the backup and there on.
Flipping the bit to signal the next event was caused by the backup access and reset.


its just a shortcut for [ImmaFreedom] and the mod tag


Commenting here so we don't forget about this items:

1.  In BlockLocationServiceImpl, we need to be careful about using departure and arrival time interchangeably - https://github.com/CUTR-at-USF/onebusaway-application-modules/blob/develop-psta2/onebusaway-transit-data-federation/src/main/java/org/onebusaway/transit_data_federation/impl/realtime/BlockLocationServiceImpl.java#L563.  We get either departure or arrival time from the real-time info, but then always use arrival time in the below logic:

~~~
  for (BlockStopTimeEntry blockStopTime : blockConfig.getStopTimes()) {
            StopTimeEntry stopTime = blockStopTime.getStopTime();
            StopEntry stop = stopTime.getStop();
            if (stopId.equals(stop.getId())) {
              int arrivalTime = stopTime.getArrivalTime();
              int deviation = (int) ((predictedTime - blockInstance.getServiceDate()) / 1000 - arrivalTime);
              scheduleDeviations.put(arrivalTime, (double) deviation);
            }
          }
~~~

We should use `stopTime.getDepartureTime();` if we're using the real-time departure time.  Otherwise, the indexes in the scheduleDeviations arrays won't match.

2.  Similar issue in `getBestScheduleDeviation()` (https://github.com/CUTR-at-USF/onebusaway-application-modules/blob/develop-psta2/onebusaway-transit-data-federation/src/main/java/org/onebusaway/transit_data_federation/impl/ArrivalAndDepartureServiceImpl.java#L809) - we always use arrival time in the following block - we should use departure time in the case of using departure time:

~~~
if (scheduleDeviations != null && !scheduleDeviations.isEmpty()) {
      int arrivalTime = instance.getBlockStopTime().getStopTime().getArrivalTime();
      return (int) InterpolationLibrary.interpolate(
          scheduleDeviations.getScheduleTimes(),
          scheduleDeviations.getScheduleDeviationMus(), arrivalTime,
          EOutOfRangeStrategy.LAST_VALUE);
    } else if (blockLocation.isScheduleDeviationSet()) {
      return (int) blockLocation.getScheduleDeviation();
    } else {
      return 0;
    }
~~~


@nnethercote: The memory usage of the layer tree, like that of the BufferMap, will either be allocated from GPU memory or the heap. It's also likely that in the future the layer tree will contain memory from both the GPU and the heap. I'm happy to explain this in the documentation for the method.

Do you think that in the future, the memory Reporter will be able to distinguish between different types of allocated memory?


i mean can use /cleanup. this is not /sys this is /cleanup


So, we have a better error message now, but because we have an inner conditional that is more expansive than our outer one, it looks like there is a logic error here, and that the outer conditional should include more cases.  This isn't what we want here, because this block is here to check if something accidentally gets through our outer `if`.  That is, it's to catch a logic error that may be introduced by refactoring.

I'd been shying away from this since we haven't talked about macros, but really an `assert` is what you want.  Go ahead and include `<cassert>` and use `assert(false);` in this `else` block, and maybe a comment explaining.


Yay simplify!
:+1:


- redundant code removed. No need to repeat less from the component unless it's likely to be editable in the theme.
- focus fix should be in the component itself not the theme. Instead this was overriding the components fix and pushing the narrative controls out.


Why remove the limit? Putting any odd number like -53647 breaks SW.


Looks great, the code is much more understandable than the original.


Even `print` won't help here, right?  The stack after a `print` should be exactly the same as before a `print`.


> I'll add that depending on how often the function is called, returning a boolean asap will be less time wasting. :)

Yeah I completely agree. I'll change it then, better do things the most simple way without trying to code ahead what *might* become useful or not :)


ah, oks. I just stumbled upon stash so I thought maybe we could try to list all here. But if there are many more, it makes total sense to leave the not-super-important ones out.


This looks like the MIT license to me: https://github.com/npct/pct/blob/master/LICENSE . Explain or revert this line please!


ok. I'll actually fix the start and end times with unsupported here as well.


# [Recreating an Activity](https://developer.android.com/training/basics/activity-lifecycle/recreating.html)

If the system destroys the activity due to system constraints (rather than normal app behavior), then although the actual Activity instance is gone, the system remembers that it existed such that if the user navigates back to it, the system creates a new instance of the activity using a set of saved data that describes the state of the activity when it was destroyed. The saved data that the system uses to restore the previous state is called the "instance state" and is a collection of key-value pairs stored in a `Bundle` object.

__Caution:__ Your activity will be destroyed and recreated each time the user rotates the screen. When the screen changes orientation, the system destroys and recreates the foreground activity because the screen configuration has changed and your activity might need to load alternative resources (such as the layout).

To save additional data about the activity state, you must override the `onSaveInstanceState()` callback method. The system calls this method when the user is leaving your activity and passes it the `Bundle` object that will be saved in the event that your activity is destroyed unexpectedly. If the system must recreate the activity instance later, it passes the same Bundle object to both the `onRestoreInstanceState()` and `onCreate()` methods.

## Save Your Activity State

```java
static final String STATE_SCORE = "playerScore";
static final String STATE_LEVEL = "playerLevel";
...

@Override
public void onSaveInstanceState(Bundle savedInstanceState)
{
    // Save the user's current game state
    savedInstanceState.putInt(STATE_SCORE, this.currentScore);
    savedInstanceState.putInt(STATE_LEVEL, this.currentLevel);

    // Always call the superclass so it can save the view hierarchy state
    super.onSaveInstanceState(savedInstanceState);
}
```

## Restore Your Activity State

```java
public void onRestoreInstanceState(Bundle savedInstanceState)
{
    // Always call the superclass so it can restore the view hierarchy
    super.onRestoreInstanceState(savedInstanceState);

    // Restore state members from saved instance
    this.currentScore = savedInstanceState.getInt(STATE_SCORE);
    this.currentLevel = savedInstanceState.getInt(STATE_LEVEL);
}
```


Same with comments before, but in this case it may be more readable to keep it in, because the `main` function is large enough and has many failure cases that leaving it out here may be confusing.


There's a commit hook to prevent these spec files from getting out of sync with the actual dependencies. It's recommended to install the hook on all loggregator development machines with https://github.com/cloudfoundry/loggregator/blob/develop/bin/install-git-hooks.


Please revert. Why? James is putting this all into a docx and the refs do not compile into docx.


TeamCity MonoGame :: Develop (Win) [Build 3.5.0.355](http://teamcity.monogame.net/viewLog.html?buildId=8791&buildTypeId=MonoGame_DevelopWin&guest=1) is now running


Good


This test is good and necessary, but below your error message seems to contradict it.


@rallytime that was a bad idea, actually. The collector detaches itself in a background as a standalone program and runs in a lowest priority. At that time no `__salt__` around...

I am preparing new PR supporting Debian/Ubuntu, so this will be fixed. Here JFYI. :smile:


This makes it much, much clearer.


Yala ship it!


Yeah, I saw this and fixed it in the PR: https://github.com/apigee/smartdocs-templates/pull/9/files


This line breaks when parsing a config file which specifies multiple witnesses due to duplicate keys. I think we need to either relax the parser's validation checks, or store logging config in a different file.


@DiamondBond @hoholee12
I have in mind a hardcore (for me sure lol) rebuild of SH-OTA & I will need your help.
My idea is convert SH-OTA in a separate script which will be in his own folder in /data & will different config files for every script or a config file with config of all script (this better)... Else, SH-OTA script will be updated if we released a new version.
The users only need add a few lines in their scripts to link to SH-OTA method :)
I don't want this now, first want completed 2.1 & after think the version of this future project (v3.0 surely...).


o/


[MidoNet], please


>And since we stopped iterating, that means …

Very useful.  Explains why this case is necessary and walks through the logic of the solution.


I'm making this a 'kable' table for combatibility with docx format.


hope this is the one used in v1.1 and not something else ? Note @rom-stratoscale  asks us to use the one in v1.1, so don't get forward or backward unless this is done in v1.1


Yes, that would be the bext way to implement it. At the moment the implementation is kinda dumb, so perhaps falling back automatically in the daemon would be the best thing to do anyway.


Good work: more clear.


done !


No. This when is exhaustive. Next time we will get a compile-time error.


Awesome!!!


https://github.com/Stratoscale/rootfs-star/blob/v1.1/solvent.manifest#L30
f51915216784ca062f1cd01d6d892907ceb9f5e4 <> f79aaf9914b5ed865423d0b9957937c027a0cadf

(even if it's for testing rootfs, let's strive to use the same)


Correction: Apache is version 2.2.22 - not 2.22
Add: on Ubuntu 12.04.1 LTS


If I set `Hosts ""`, or `Hosts ","` in the file, it will not work, and not warn me either.


Nice, thanks! Only some tiny change requests to the PR :)


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

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


Just don't upload the 010 armeabi version, we don't do anything with that version (it is only for very old devices, all devices of last years have already armv7). We can safely assume that all devices that have kitkat also do have armeabi-v7a.

If you had uploaded it by acccident (I cannot see/check it) just remove it from that commit by amending it :)

This is also a note to all other @opengapps/packagers about this situation/package.


Hey!
I strongly recommend to disable the MDP/MSMFB driver entirely, and try to boot recovery. MMC drivers might cause issues too, but after disabling them you might have to fix additional compile errors.
I debugged my bringup for Huawei by adding a LCD reset code (GPIO reset) to platform code. Then I was able to see whether the code reached somewhere (you only need to make sure GPIO driver has been brought up, otherwise it's no help). It's also possible to trigger a restart, but it's not as reliable on some devices.

Wish you luck!


Typo mate - watch out!


Ok, this looks fine


I noticed that Chrome versions are defined in advance of their final (non-developer) releases. You might consider doing the same for Firefox since it has a published calendar and its UA string has remained stable. See https://wiki.mozilla.org/RapidRelease/Calendar#Future_branch_dates. Seems safe to add FF up to 42. Just my $0.02.

For what its worth, here's an example from FF 42 (aka "Nightly").

Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:42.0) Gecko/20100101 Firefox/42.0

David


Yes, this was something I meant to do but never actually got to do it. I'd call it `FileSystemLoader`, though (although I agree that's not something very important).


We've been doing that for both Chrome and Firefox but sometimes the inflation of version numbers is faster than expected.


1712-AvailabilityManagers (kbenne) - i386-Windows-7-VisualStudio-12: Tests Failed

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


We have to get away from the idea that tests, or even apparent behavior, establish program correctness.  Because the program is short, we can work through it line-by-line and see what it's doing.  Starting from line 17:

```cpp
auto input = ""s;
while (getline(cin, input)) {
  cout << input; // without newline added
}
```

`getline` tries to read in a line.  If it reaches a `'\n'` or EOF, it succeeds and assigns `input` to what it read, dropping the `'\n'` if applicable.  The body of the while loop then prints out `input`, which doesn't have a newline.  In the case of `getline` being terminated by a `'\n'`, this is incorrect, because the newline isn't echoed.  In the case of an EOF, this is correct, because there was no newline to echo.

Let's put the `"\n"s` back.  `getline` tries to read in a line.  If it reaches a `'\n'` or EOF, it succeeds and assigns `input` to what it read, dropping the `'\n'` if applicable.  The body of the while loop then prints out `input`, which doesn't have a newline, and then a newline.  In the case of `getline` being terminated by a `'\n'`, this is correct, because the input did have a newline.  In the case of an EOF, this is incorrect, because we are echoing an extra newline that wasn't in our input.

So based on this reasoning about our program, where does the problem lie?


Why this change?  Using cheri_ functions/macros seems better than __builtin_cheri variants


ahhh this is so beautiful!


This looks like `autopep8` has done some work here. I guess it's fine.


@kmcostel This will only work for addr.json; still in progress?


To merge this change we need to add some infrastructure to cheritest so this can be marked XFAIL when no swap is configured.


Cool diagram, just wondering if it's really needed to convey the points?


Muito obrigado cara, isso foi mais pra impedir que qualquer um execute o script kkk a pessoa tem que ter uma noção básica do que ta acontecendo :)
Espero que tenha te ajudo o artigo

-----Mensagem Original-----
De: "wil06we" <notifications@github.com>
Enviada em: 16/07/2015 13:15
Para: "mthbernardes/MassAttack" <MassAttack@noreply.github.com>
Cc: "Matheus Bernardes" <mthbernardes@gmail.com>
Assunto: Re: [MassAttack] Create massattack.py (04452b5)

Olá, Parabéns pelo script.
Só notei uma coisa:
Na variável File só consegui executar com está alteração
file = open(raw_input('[+] - Digite o caminho do arquivo com os IPs:'))
Abraços
—
Reply to this email directly or view it on GitHub.


hmm what is that value: 3.7395 ?


1712-AvailabilityManagers (kbenne) - Win64-Windows-7-VisualStudio-12: Tests Failed

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


Hey, You seem to have overwritten the previous change to require a more liberal phantomjs range... could you re-apply that commit if it wasn't intentional?
Thanks!


So saddened and so sorry that I've just learned of Jim's passing.  I'm not part of the Ruby community, as I knew Jim before he became so well known for his contributions there.  I studied and worked in the Cincinnati area during the 90's, so I got to know Jim as a leader when the Cincinnati Linux User's Group first started and than also as a teacher during the infancy of my software development career.  He was such a great lecturer and a genuinely nice guy.  I most remember him sharing a story from an earlier time in his career when he was doing development supporting the rocket launch complexes at NASA Kennedy Space Center or Cape Canaveral Air Force Station (forget which).  That story only added to my already burgeoning desire to work in space flight, which I had to honor of doing in support of NASA Johnson Space Center here in Houston for over a decade.  But having moved away from Cincinnati, I had fallen out of touch with Jim and didn't realize his passing until today when something led me to look him up and see what he was doing.

Rest in peace, Jim.  You had such an impact on so many, and I'll certainly always remember the impact you had on my education an on my career.


This commit is great!


Well fantastic. Now I've got to figure out how to stop PHPStorm from using my home dir... Ty PHPStorm 9!


@adarshk directly return without if else


4973_heatpump_defrost_bug (nmerket) - x86_64-MacOS-10.9-clang: OK (1750 of 1751 tests passed)

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


I use mac where write that


quality assurance)


@abel-stratoscale  i asked motty he suggesxted tio take the master


TeamCity MonoGame :: Develop (Win) [Build 3.5.0.355](http://teamcity.monogame.net/viewLog.html?buildId=8791&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 516, ignored: 6 Build time: 00:21:54


@abel-stratoscale  all tests passes .. why not doing it ?


thanks... I will give a try and give you feedback :)


Ok, I agree with this change. Indeed the job reference is bad, thanks for cleaning this up.


EvansHVACObjects (evanweaver) - i386-Windows-7-VisualStudio-12: Tests Failed

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


Just any known start value.


add more text


@LorenzMeier I think this should be specified. Actually for us LPOS_vx, y, z are not directly relevant, but they might for other people.
What we definitely missed as a control state is the smoothened airspeed output from the estimator, i.e. sqrt((vx-wind_x)^2+(vy-wind_y)^2+vz^2). We can discuss it quickly tomorrow.


ok, so i can also use to start with calc. 50% = 3.80V (i want to round it down from 3.82V)


Could ypu please rename the patch to not use 9999? Maybe 4.90 (dont know which is current version in cmake file) or without version.


See, this is why I don't like making a lot of protected methods/attributes. If other parts of the code are going to use it, it feels quite hackish.


Looks good!


@DefinitlyEvil What's the IP of the demo server?


nope


EvansHVACObjects (evanweaver) - Win64-Windows-7-VisualStudio-12: Tests Failed

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


This feels like it would be better kept as a public method.


I see, this seems OK for now.


:v abandoned??


We probably shouldn't mention GCC here since any future compilers will be affected.

It should be possible to pull in the libspl and libzfs private headers relative #includes in `libzfs_core.h` (`#include "libspl/xxx.h"`) to avoid the extra include paths. That way consumers can consistently use `#include <libzfs_core.h>`. (Or if we wish to partition it off, it's not too late to introduce `<zfs/libzfs_core.h>`, since there are no public interfaces yet.)


teste


1712-AvailabilityManagers (kbenne) - x86_64-MacOS-10.9-clang: Tests Failed

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